-
Notifications
You must be signed in to change notification settings - Fork 7
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
Develop #160
Conversation
Cleanup sendsketch to prokka
Rename ctmrnas profile and add new section to changelog
Add ctmr_gandalf profile
Add ctmr_gandalf profile to available options
Make shovill.log part of the default output files from shovill
Reduce the search scope for MultiQC
Update docker file to accomodate kraken
I think we're very close to completing this now! Has anyone encountered any odd error messages that were not handled gracefully? I'll make one last check to see if version numbers of correct everywhere. |
Sorry for putting all these commit directly on the develop branch, I started with a very small change, but found lots of minor things I wanted to improve across the documentation. |
As comes to mind, some errors that affect the end user may be:
|
This is mentioned in the docs, in this section: https://bactpipe.readthedocs.io/en/develop/running.html#running-bactpipe Additionally, if running a cluster profile that requires a project name, BACTpipe throws an error message. E.g. if the Rackham profile is selected but no Example:
BACTpipe prints a warning about it, and it is mentioned in the docs and implied in the command line help. Example:
Not sure about this one. We do have this line here, but not sure if that is actually enforced or what kind of error message is printed if an old version is used: https://github.com/ctmrbio/BACTpipe/blob/develop/nextflow.config#L8
This issue is still open I think and has been pushed to our next release: #148
This is kind of fixed, but still has a minor bug (the workflow completed "without errors" even if it failed 😄 ...
|
I'm happy with how this works now. Let me know if you think otherwise. We can merge later today or tomorrow unless there is anything else. |
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.
I'm happy with the changes for this release as well 👍
I am also happy with the way this looks and behaves, so I reaffirm my previous approval of this merge. |
I guess we should then merge this to master so that we get all those changes included?