- recipe perl-atlas-modules
A package exporting in-house perl functions and classes used in the data production of EMBL-EBI Expression Atlas data.
- Homepage:
- License:
APACHE / Apache-2.0
- Recipe:
- package perl-atlas-modules#
-
- Versions:
0.3.2-0,0.3.1-5,0.3.1-4,0.3.1-3,0.3.1-2,0.3.1-0,0.3.0-0,0.2.0-0,0.1.6-2,0.3.2-0,0.3.1-5,0.3.1-4,0.3.1-3,0.3.1-2,0.3.1-0,0.3.0-0,0.2.0-0,0.1.6-2,0.1.6-1,0.1.6-0- Depends:
on __osx>=10.13on libcxx>=19on perl>=5.32.1,<5.33.0a0 *_perl5on perl-algorithm-diffon perl-archive-extracton perl-archive-zipon perl-array-compareon perl-array-utilson perl-baseon perl-capture-tinyon perl-carpon perl-carp-clanon perl-class-accessoron perl-class-stdon perl-clone0.46.*on perl-data-compareon perl-data-dumperon perl-date-manip>=6.99,<7.0a0on perl-datetime>=1.66,<2.0a0on perl-datetime-format-strptime>=1.80,<2.0a0on perl-dbd-mysql>=5.13,<6.0a0on perl-dbd-pg>=3.20.0,<4.0a0on perl-dbion perl-devel-symdumpon perl-extutils-cbuilderon perl-extutils-config0.008.*on perl-extutils-helpers0.026.*on perl-extutils-installpaths0.012.*on perl-file-specon perl-graphviz>=2.26,<3.0a0on perl-io-scalaron perl-io-stringyon perl-ipc-cmd>=1.4,<1.5.0a0on perl-ipc-run3>=0.49,<0.50.0a0on perl-json>=4.11,<5.0a0on perl-json-parse>=0.62,<0.63.0a0on perl-list-moreutilson perl-log-log4perlon perl-lwp-protocol-https>=6.15,<7.0a0on perl-lwp-simple>=6.67,<7.0a0on perl-mailtools>=2.22,<3.0a0on perl-mime-liteon perl-module-build0.4234.*on perl-module-build-tiny0.039.*on perl-module-pluggableon perl-moose2.2207.*on perl-moosex-types>=0.51,<0.52.0a0on perl-params-coerceon perl-params-validate>=1.31,<2.0a0on perl-parse-recdescenton perl-path-tinyon perl-readonly2.05.*on perl-scalar-list-utilson perl-spiffy0.46.*on perl-sub-exporter-formethodson perl-sub-uplevelon perl-test-exceptionon perl-test-inter>=1.12,<2.0a0on perl-test-needson perl-test-nowarnings1.06.*on perl-test-podon perl-test-pod-coverage>=1.10,<2.0a0on perl-test-warnon perl-text-csvon perl-text-csv_xs>=1.61,<2.0a0on perl-text-diffon perl-tie-ixhashon perl-timedate>=2.35,<3.0a0on perl-uri5.34.*on perl-xml-parseron perl-xml-simpleon perl-xml-writeron perl-yaml
- Additional platforms:
linux-aarch64
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 perl-atlas-modules
to add into an existing workspace instead, run:
pixi add perl-atlas-modules
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 perl-atlas-modules
Alternatively, to install into a new environment, run:
conda create -n envname perl-atlas-modules
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/perl-atlas-modules:<tag>
(see perl-atlas-modules/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.Link to this page#
Render an badge with the following MarkDown:
[](http://bioconda.github.io/recipes/perl-atlas-modules/README.html)