Feedstock license: BSD-3-Clause
Home: https://lhapdf.hepforge.org/
Package license: GPL-3.0-only
Summary: LHAPDF is a general purpose C++ interpolator, used for evaluating PDFs from discretised data files.
Development: https://gitlab.com/hepcedar/lhapdf
Documentation: https://lhapdf.hepforge.org
LHAPDF is a library implementing a standard to represent Parton Distribution Functions (PDFs) which is ubiquitous in the field of High Energy Physics. PDFs, which describe the structure of the proton, are an essential ingredient for experimental and phenomenological studies at the Large Hadron Collider (LHC). LHAPDF allows PDF fitting collaborations to distribute their results in a format that is interoperable with tools requiring PDFs as input, such as Monte Carlo Event generations. The LHAPDF project maintains a remote repository of PDFs, which can be installed with tools that accompany the library. Please make sure to cite the following paper if you use LHAPDF6 "LHAPDF6: parton density access in the LHC precision era" Eur.Phys.J. C75 (2015) 3, 132 http://arxiv.org/abs/1412.7420
Name | Downloads | Version | Platforms |
---|---|---|---|
Installing lhapdf
from the conda-forge
channel can be achieved by adding conda-forge
to your channels with:
conda config --add channels conda-forge
conda config --set channel_priority strict
Once the conda-forge
channel has been enabled, lhapdf
can be installed with conda
:
conda install lhapdf
or with mamba
:
mamba install lhapdf
It is possible to list all of the versions of lhapdf
available on your platform with conda
:
conda search lhapdf --channel conda-forge
or with mamba
:
mamba search lhapdf --channel conda-forge
Alternatively, mamba repoquery
may provide more information:
# Search all versions available on your platform:
mamba repoquery search lhapdf --channel conda-forge
# List packages depending on `lhapdf`:
mamba repoquery whoneeds lhapdf --channel conda-forge
# List dependencies of `lhapdf`:
mamba repoquery depends lhapdf --channel conda-forge
conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.
A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml
within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender
.
For more information please check the conda-forge documentation.
feedstock - the conda recipe (raw material), supporting scripts and CI configuration.
conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml
files
and simplify the management of many feedstocks.
conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)
If you would like to improve the lhapdf recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge
channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge
channel.
Note that all branches in the conda-forge/lhapdf-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
build/number
.build/number
back to 0.