- recipe biopax-validator
Validates BioPAX data against the specification and best practice rules
- Homepage:
- Developer docs:
- License:
MIT / MIT
- Recipe:
- Links:
The BioPAX Validator checks BioPAX Level 3 data for syntactic errors and for violations of BioPAX best practice rules, and reports the result as XML, HTML or BioPAX. It can run fully offline, loading the required OBO ontologies locally, or delegate validation to the remote BioPAX Validator service.
- package biopax-validator#
-
- Versions:
6.0.0-0- Depends:
on openjdk>=17
- Additional platforms:
Installation#
You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). Below, we show how to install with either pixi or conda (for micromamba and mamba, commands are essentially the same as with conda).
Pixi#
With pixi installed and the Bioconda channel set up (see Usage), to install globally, run:
pixi global install biopax-validator
to add into an existing workspace instead, run:
pixi add biopax-validator
In the latter case, make sure to first add bioconda and conda-forge to the channels considered by the workspace:
pixi workspace channel add conda-forge
pixi workspace channel add bioconda
Conda#
With conda installed and the Bioconda channel set up (see Usage), to install into an existing and activated environment, run:
conda install biopax-validator
Alternatively, to install into a new environment, run:
conda create -n envname biopax-validator
with envname being the name of the desired environment.
Container#
Alternatively, every Bioconda package is available as a container image for usage with your preferred container runtime. For e.g. docker, run:
docker pull quay.io/biocontainers/biopax-validator:<tag>
(see biopax-validator/tags for valid values for <tag>).
Integrated deployment#
Finally, note that many scientific workflow management systems directly integrate both conda and container based software deployment. Thus, workflow steps can be often directly annotated to use the package, leading to automatic deployment by the respective workflow management system, thereby improving reproducibility and transparency. Check the documentation of your workflow management system to find out about the integration.
Download stats
.. Create all the necessary plots for each package by loading all the correct specs and data. Important points on the place and implementation of this script block: 1. It is here, and not in a separate HTML file, as it needs to have the `package.name` rendered in for each package. 2. All packages are handled in one `window.onload` function, as multiple instances of this throughout a (rendered) HTML just overwrite each other.Notes#
Two wrapper scripts are installed on $PATH. "biopax-validator" validates offline and loads the required ontologies locally. "biopax-validator-client" sends the data to the remote BioPAX Validator service. JVM options are passed through the JAVA_OPTS environment variable, e.g. JAVA_OPTS="-Xmx4g" biopax-validator input.owl --output=report.html Upstream recommends at least 2 GB of heap. Startup takes about a minute while the ontologies are loaded. Example input files are installed in $CONDA_PREFIX/share/biopax-validator-<version>/sampleData.
Link to this page#
Render an badge with the following MarkDown:
[](http://bioconda.github.io/recipes/biopax-validator/README.html)