Feedstock license: BSD-3-Clause
Home: https://docs.metatensor.org/metatomic/latest/engines/lammps.html
Package license: GPL-2.0-only
Summary: Metatensor-enabled version of LAMMPS
Development: https://github.com/metatensor/lammps
Documentation: https://docs.metatensor.org/metatomic/latest/engines/lammps.html
Metatensor-enabled version of LAMMPS
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
Installing lammps-metatensor from the metatensor channel can be achieved by adding metatensor to your channels with:
conda config --add channels metatensor
conda config --set channel_priority strict
Once the metatensor channel has been enabled, lammps-metatensor can be installed with conda:
conda install lammps-metatensor
or with mamba:
mamba install lammps-metatensor
It is possible to list all of the versions of lammps-metatensor available on your platform with conda:
conda search lammps-metatensor --channel metatensor
or with mamba:
mamba search lammps-metatensor --channel metatensor
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search lammps-metatensor --channel metatensor
# List packages depending on `lammps-metatensor`:
mamba repoquery whoneeds lammps-metatensor --channel metatensor
# List dependencies of `lammps-metatensor`:
mamba repoquery depends lammps-metatensor --channel metatensor
If you would like to improve the lammps-metatensor 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
metatensor channel, whereupon the built conda packages will be available for
everybody to install and use from the metatensor channel.
Note that all branches in the metatensor/lammps-metatensor-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:
- If the version of a package is not being increased, please add or increase
the
build/number. - If the version of a package is being increased, please remember to return
the
build/numberback to 0.