-
Notifications
You must be signed in to change notification settings - Fork 0
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
Merging the stable version of the pipeline for the first release #1
Conversation
This PR is against the
|
|
Fix linting problems.
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'll start dropping some comments here and there as I go deeper in the pipeline. It would be awesome if you could revive the conf/test.config and put all default parameter values needed to run a minimal end-to-end test. I can understand that this may be a bit hard due to required databases, but maybe you can even let it run through an end-to-end stub test instead of subsampling and/or linking smaller versions of the dbs. It's much much easier to follow the execution to debug it with the default nextflow output rather than with nf-test.
In any case, either if you choose to do this, or stick with nf-test test, it would be nice if there was some guidance on how to run the test in the READme. For example, for the nf-test, write how much cpu and mem are required and the command to run.
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.
Remove --genome GRCh37 from line 24 in main.nf. Replace this line with the minimal one required to run the pipeline
I think 12 CPUs and 72GB memory for current nf-test. |
I agree, but the nf-test we run is for development use as it runs only using the ebi profile in codon due to the databases issue. External users can test their installation and databases paths by running the pipeline with the provided test data. Even if they have no hits with the biome they are interested, the pipeline should finish successfully. I have added that to the README file. |
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.
Thanks, at least the parts I checked seem to be working fine ;)
Thank you for your review @vagkaratzas. I will merge now. |
As this is the first stable version, there are many commits here. The code in Python doesn't need to be intensively reviewed. Thanks in advance for taking a look :D