- recipe vpt
Command line tool for highly parallelized processing of Vizgen data
- Homepage:
- License:
Apache-2.0
- Recipe:
- package vpt¶
-
- Versions:
1.3.0-0- Depends:
on boto3
>=1.17on dask-core
>=2023.2.0on distributed
>=2023.2.0on fastparquet
on fsspec
on gcsfs
on geopandas
>=0.13.2on h5py
>=3.7.0on ipykernel
on jinja2
on leidenalg
>=0.10.1on matplotlib-base
<=3.7.0on numpy
>=1.24.3on pandas
>=2.0.3on plotly
>=5.17.0on pretty_html_table
>=0.9.16on pyarrow
>=8.0.0on python
>=3.9,<3.11on python-dotenv
>=0.20.0on python-kaleido
on pytorch
>=2.0.0,!=2.0.1,!=2.1.0on pyvips
>=2.2.1on rasterio
>=1.3.0on s3fs
on scanpy
on scipy
>=1.8.1on shapely
>=2.0.0on vpt-core
>=1.2.0on vpt-segmentation-packing
>=1.0.0on wrapt_timeout_decorator
>=1.5.1
- 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 vpt
to add into an existing workspace instead, run:
pixi add vpt
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 vpt
Alternatively, to install into a new environment, run:
conda create -n envname vpt
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/vpt:<tag>
(see vpt/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¶
Link to this page¶
Render an badge with the following MarkDown:
[](http://bioconda.github.io/recipes/vpt/README.html)