-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix drep add assembler flag #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR. Everything looks good! Thank you for adding the option to skip running metaspades due to its extremely long run times. The only small suggestion I would make is related to the encoding of the megahit_only flag. Right now, True is being encoded as a 0 instead of a 1. If we flipped that, we wouldn't need to use the not statements when we are resolving/evaluating it later, and it would also be more clear as to what the value is supposed to represent. This can fixed later though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Thank you for adding this option to avoid running metaspades.
metamorph
Outdated
config['coassembly'] = False | ||
|
||
# Step 4b. Setup assembly mode | ||
# modes: 0 - megahit + metaspades assembly | ||
config["options"]["assembler_mode"] = "0" if sub_args.megahit_only else "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic here is opposite of what I would expect for a boolean flag. I see in the Snakefile you accounted for that, but would it be worth just sticking to booleans, or "1 for True" and "0 for false" to avoid ambiguity?
Address #24 , #25 , and #21