-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom assembly options and export assembly QC #149
Conversation
Co-authored-by: Sabrina Krakau <sabrinakrakau@gmail.com>
Regarding the time limit and the missing exit code, can it be a Nextflow or slurm problem if this is not reported properly? See e.g. nextflow-io/nextflow#1354 Didn't it work in the past? |
Still, I think in general this way of allowing general custom options as strings is not ideal, we should fix those as soon as possible. |
edit: Sorry, was too fast here, sure that might be. Sometimes it works for me, sometimes it doesnt.
True, but I am not certain at this point which options might be most helpful. |
--spades_options
&--megahit_options
) to allow custom SPAdes and MEGAHIT options, this is required to adjust e.g. k-mers or presets for more challenging assembliesedit: Just figured out that MEGAHIT told
Process
megahit (groupall)terminated with an error exit status (250)
when running into RAM issues. That should be added as well. Unfortunately, time limits resulted in an empty error code, very unfortunate.edit2: Re-try MEGAHIT when exiting with code 250