oh very cool, nice progress 🎉 id put this in user control. id not make it the default and certainly not have it always on, but there is real reason an informed user might choose to ignore it

cool, I'll just push a new test dataset then! Also, I put all of those on process_low, which are cpus = { 2 * task.attempt } memory = { 12.GB * task.attempt } time = { 4.h * task.attempt } Since I haven't used all of them, I'm not sure if that's the most appropriate label to pick? BUSTED MEME and FUBAR I've used and am fairly confident they would run with those resources without problem for most alignments, not sure about the others. Also for GARD I'm toying between process_medium + process_long and process_high + process_long? I've had analyses take quite a while to run. withLabel:process_medium { cpus = { 6 * task.attempt } memory = { 36.GB * task.attempt } time = { 8.h * task.attempt } } withLabel:process_high { cpus = { 12 * task.attempt } memory = { 72.GB * task.attempt } time = { 16.h * task.attempt } } withLabel:process_long { time = { 20.h * task.attempt } } Do you have an opinion or advice on that?

id probably do something like: GARD -> process_high + process_long BUSTED -> process_high + process_long ABSREL -> process_medium FUBAR -> process_medium MEME -> process_medium FEL -> process_low SLAC -> process_low BGM -> process_low

no, no mpi at all, I'm not sure how to implement it within a module 🤔 github.com/nf-core/modules/…/hyphy I'll update the process labels with your recommendation after I'm done with GARD

this seemed to work for us, as local modules github.com/veg/CAPHEINE/…/hyphympi