Nextflow ProteinFunction: support for SQLite db #1152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ENSVAR-6567
Extend ProteinFunction nextflow pipeline to be able to write to a SQLite db. It introduces the following params -
params.offline
- if set, no ensembl database connection would be made (and not storing data in MySQL db)params.sqlite
- if set, a SQLite db would be created with the results. (if params.offline is set params.sqlite is automatically set too, otherwise there would be no output)params.sqlite_dir
- directory location where sqlite db should be stored. By default it is theparam.outdir
. The db name is set to${params.species}_PolyPhen_SIFT.db
params.sqlite_db
- give full path of the SQLite db with name. Alternative way to give db name.Test:
Test the generated SQLite db ($PWD/temp/felis_catus_PolyPhen_SIFT.db) against what we have in Ensembl database.