PhEval Runner for AMELIE
This is the AMELIE plugin for PhEval. With this plugin, you can leverage the gene prioritisation tool, AMELIE, to run the PhEval pipeline seamlessly. The setup process for running the full PhEval Makefile pipeline differs from setting up for a single run. The Makefile pipeline creates directory structures for corpora and configurations to handle multiple run configurations. Detailed instructions on setting up the appropriate directory layout, including the input directory and test data directory, can be found here.
Installation
Clone the pheval.amelie repo and set up the poetry environment:
git clone https://github.com/yaseminbridges/pheval.amelie.git
cd pheval.amelie
poetry shell
poetry install
Alternatively, install with pip:
pip install pheval_amelie
Configuring a single run
Setting up the input directory
A config.yaml should be located in the input directory and formatted like so:
tool: AMELIE
tool_version: 3.1.0
variant_analysis: False
gene_analysis: True
disease_analysis: False
tool_specific_configuration_options:
The bare minimum fields are filled to give an idea on the requirements, as AMELIE is gene prioritisation tool, only gene_analysis should be set to True in the config. An example config has been provided pheval.amelie/config.yaml.
The overall structure of the input directory should look something like so:
.
└── config.yaml
Setting up the testdata directory
The AMELIE plugin for PhEval accepts phenopackets and gzipped VCF files as an input for running AMELIE.
The testdata directory should include a subdirectory named phenopackets and a subdirectory named vcf:
├── testdata_dir
├── phenopackets
└── vcf
Run command
Once the testdata and input directories are correctly configured for the run, the pheval run command can be executed.
pheval run --input-dir /path/to/input_dir \
--testdata-dir /path/to/testdata_dir \
--runner ameliephevalrunner \
--output-dir /path/to/output_dir \
--version 3.1.0
Docs
https://yaseminbridges.github.io/pheval.amelie/
Acknowledgements
This cookiecutter project was developed from the pheval-runner-template template and will be kept up-to-date using cruft.
Metadata
Release files for pheval-amelie 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pheval_amelie-0.1.0.tar.gz | 11.2 kB | Without provenance | Details for pheval_amelie-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pheval_amelie-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pheval_amelie-0.1.0-py3-none-any.whl |
Total release size: 24.4 kB
Release files / pheval_amelie-0.1.0.tar.gz
| Download URL | pheval_amelie-0.1.0.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b69b6478cbf11d43f269b7d20b0d36392b5cd2bef264a1572fc81bf097de4dee
|
|
BLAKE2b-256 checksum How to use checksums |
b564744e3b6f371edc54a8cc994b3e13fd29e5973cdd7b6ab147d54e7aab7cc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.20
|
Release files / pheval_amelie-0.1.0-py3-none-any.whl
| Download URL | pheval_amelie-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b2dcb38272185fc0b9f1095ef4a4e74c1a2ebf6f7686c802d6632e9899ed134
|
|
BLAKE2b-256 checksum How to use checksums |
7444d755b0c59241a0c6b8abd15a495ee9062c996827f54ff9f4cf4638648df5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.20
|
Security for pheval-amelie 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.