Skip to main content

SvAnna Runner for PhEval

This is the SvAnna plugin for PhEval. With this plugin, you can leverage the structural variant prioritisation tool, SvAnna, 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.svanna repo and set up the poetry environment:

git clone https://github.com/monarch-initiative/pheval.svanna.git
cd pheval.svanna
poetry shell
poetry install

or install with PyPi:

pip install pheval.svanna

Configuring a single run:

Setting up the input directory

A config.yaml should be located in the input directory and formatted like so:

tool: svanna
tool_version: 1.0.3
variant_analysis: True
gene_analysis: False
disease_analysis: False
tool_specific_configuration_options:
  svanna_jar_executable: svanna-cli-1.0.3/svanna-cli-1.0.3.jar
  post_process:
    sort_order: descending

The bare minimum fields are filled to give an idea on the requirements, as SvAnna is variant prioritisation tool, only variant_analysis should be set to True in the config. An example config has been provided pheval.svanna/config.yaml.

The svanna_jar_executable points to the location of the Svanna jar executable in the input directory.

Setting up the testdata directory

The SvAnna plugin for PhEval accepts phenopackets and vcf files as an input.

The testdata directory should include subdirectories named phenopackets and vcf.

e.g.,

├── 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 svannaphevalrunner \
--output-dir /path/to/output_dir \
--version 1.0.3

Common errors

You may see an error that is related to the current setuptools being used:

pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected closing RIGHT_PARENTHESIS
    requests (<3,>=2.12.*) ; extra == 'parse'
             ~~~~~~~~~~^

To fix the error, setuptools needs to be downgraded to version 66:

pip uninstall setuptools
pip install -U setuptools=="66"

Metadata

Release files for pheval-svanna 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pheval-svanna 0.2.0
File Size Uploaded Provenance Actions
pheval_svanna-0.2.0.tar.gz 4.8 kB Without provenance Details for pheval_svanna-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pheval-svanna 0.2.0
File Interpreter ABI Platform Actions
pheval_svanna-0.2.0-py3-none-any.whl Python 3 none any Details for pheval_svanna-0.2.0-py3-none-any.whl

Total release size: 12.7 kB

Release files / pheval_svanna-0.2.0.tar.gz

Download URL pheval_svanna-0.2.0.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
9add60dae866028c1b66b1a105f19985d42eee47208634eb06a4002925362bde
BLAKE2b-256 checksum
How to use checksums
20d78f0967c02af511734c6fdbdce944029c9277ae8e8ba1eccc2e59771b7a59
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.9.21

Release files / pheval_svanna-0.2.0-py3-none-any.whl

Download URL pheval_svanna-0.2.0-py3-none-any.whl
Size 7.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e83f660a81b415012a467efd39a0e051889a38aee0027908d5eba08a6d42c6db
BLAKE2b-256 checksum
How to use checksums
95c73321188ae122df2742f2457ee4269d4be385e530418c9c7917e083b19f53
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.9.21

Security for pheval-svanna 0.2.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page