Repository navigation
Fix InterProScan ignoring staged database #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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -35,9 +35,9 @@ params { | |||||||
|
|
||||||||
| // Functional annotation | ||||||||
| skip_interproscan = false | ||||||||
| interproscan_db_url = "https://ftp.ebi.ac.uk/pub/software/unix/iprscan/5/5.72-103.0/interproscan-5.72-103.0-64-bit.tar.gz" | ||||||||
| interproscan_db_url = "https://ftp.ebi.ac.uk/pub/software/unix/iprscan/5/5.59-91.0/interproscan-5.59-91.0-64-bit.tar.gz" | ||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This default now has to track the InterProScan version in the module's container, and nothing enforces that. The next
Suggested change
The same coupling applies to
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sadly (luckily?) there are no more interproscan bioconda (+containers) updates for the foreseeable future. Interproscan has become its own Nextflow pipeline now (non nf-core). Updating the nf-core module would mean completely moving the underlying software, and would require NExtflow packaging into biconda which is kinda unusual (for now). |
||||||||
| interproscan_db = null | ||||||||
| interproscan_applications = 'Hamap,PANTHER,PIRSF,TIGRFAM,sfld' | ||||||||
| interproscan_applications = 'Hamap,PANTHER,TIGRFAM,sfld' | ||||||||
| interproscan_enableprecalc = false | ||||||||
| skip_kofamscan = false | ||||||||
| kofamscan_profiles_url = "https://www.genome.jp/ftp/db/kofam/profiles.tar.gz" | ||||||||
|
|
||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -36,6 +36,10 @@ workflow FUNCTIONAL_ANNOTATION { | |
| .first() | ||
| } | ||
|
|
||
| // A full release untars to the whole install; INTERPROSCAN needs its inner data/ folder | ||
| ch_interproscan_db = ch_interproscan_db | ||
| .map { database -> database.resolve('data').isDirectory() ? database.resolve('data') : database } | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The branch this adds is never taken in CI, so the layout #114 reported has no test.
Repacking the test tarball with a wrapper directory (
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks. Will exercise this in case the module starts misbehaving another time |
||
|
|
||
| INTERPROSCAN( ch_fasta, ch_interproscan_db ) | ||
| ch_interproscan_tsv = INTERPROSCAN.out.tsv | ||
| } | ||
|
|
||
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.
With
Hamapdropped here and intest_full.config, the defaultinterproscan_applications(Hamap,PANTHER,PIRSF,TIGRFAM,sfld) is no longer covered by any test — and thehamap/2023_05files in the test tarball are now dead weight. Regenerating the test data withhamap/2021_04instead would let the test profiles keep usingHamapand stay closer to what a default run does. Same follow-up as the wrapper-directory point on the subworkflow.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.
Agreed, the default set has no coverage now. Regenerating the test data with
hamap/2021_04(together with the wrapper-directory repack from the subworkflow thread) is a test-datasets change, so I will leave it for a follow-up rather than this bugfix release.