-
Notifications
You must be signed in to change notification settings - Fork 6
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
End to end workflow stops after PhaGCN #49
Comments
In the "end-to-end" design, if all the sequences are non-viruses judged by the PhaMer, then they should not theoretically be passed to all other tools. This is because the following methods do not have any "negative control" and may give unestimated predictions. It's like an ML/DL model usually fails to solve an out-of-distribution problem but still assigns an in-distribution label to an input. However, if all the sequences are quantified as viruses in experiments, or identified as viruses by other methods, I suppose the users should skip the PhaMer part. Or probably, I should provide a version that users can choose whether they need to run PhaMer? Looking forward to your advice. Best, |
Thanks for the explanation. I guess my main problem was that for a novel user it's hard to see that there is a problem from the log output. Maybe just add log output that tells the user that phamer detected no viruses. An option to skip phamer could also be a good idea. |
Thanks for the suggestions. I added a new log to show if no viruses were detected. Also, a new option Wish you a nice holiday. Best, |
I have a run the exits with exit code 0 (indicating success:
I guess its because
output/filtered_contigs.fa
is empty and one of theexit()
calls here or here is called.Wondering if the workflow should continue, i.e. the exits should be return statements or if there should be an
exit(1)
. I tried the PhaTYP step separately which gave me some results .. so continuing the workflow might be of interest.There seem to be more
exit()
calls in the code which might better beexit(1)
?The text was updated successfully, but these errors were encountered: