Closed nuno-agostinho closed 7 months ago
Improves on https://github.com/Ensembl/ensembl-vep/pull/1599
genesplicer
$PATH
which
binary
training
If genesplicer is exported in the $PATH variable, like in VEP Docker/Singularity (https://github.com/Ensembl/ensembl-vep/pull/1599), there is no need to explicitly call it:
vep --id rs1348242192 --database --force --plugin GeneSplicer,training=${human_data}
This means that the only mandatory argument now is the training data.
Hi @olaaustine, I updated the PR with your suggestions. Thanks!
Merged into release/112 and main.
Improves on https://github.com/Ensembl/ensembl-vep/pull/1599
Changelog
genesplicer
command instead of a pathgenesplicer
is exported in the$PATH
variable (like in VEP Docker)genesplicer
is internally obtained viawhich
binary
withgenesplicer
as defaulttraining
with no defaultTesting
If
genesplicer
is exported in the$PATH
variable, like in VEP Docker/Singularity (https://github.com/Ensembl/ensembl-vep/pull/1599), there is no need to explicitly call it:This means that the only mandatory argument now is the training data.