Feedstock license: BSD-3-Clause
Home: https://github.com/Becksteinlab/imdclient
Package license: MIT
Summary: Receiver for IMD v2 and v3 data from simulation engines like Gromacs, LAMMPS, and NAMD
Development: https://github.com/Becksteinlab/imdclient
Documentation: https://imdclient.readthedocs.io/en/latest/protocol_v3.html
IMD (Interactive Molecular Dynamics) is a protocol for communicating molecular simulation data through a socket. It allows for two-way communication via IMD, a simulation engine sends data to a receiver and the receiver can send forces and certain requests back to the simulation engine. Version numbers in IMD are monotonically increasing integers. IMDv3, the protocol version described in this document, builds upon IMDv2, which is implemented at the time of writing in NAMD, VMD, GROMACS, and LAMMPS. IMDv2 is itself a modification of the original IMD protocol published in 2001.
| All platforms: |
|
| Name | Downloads | Version | Platforms |
|---|---|---|---|
Installing imdclient 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, imdclient can be installed with conda:
conda install imdclient
or with mamba:
mamba install imdclient
It is possible to list all of the versions of imdclient available on your platform with conda:
conda search imdclient --channel conda-forge
or with mamba:
mamba search imdclient --channel conda-forge
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search imdclient --channel conda-forge
# List packages depending on `imdclient`:
mamba repoquery whoneeds imdclient --channel conda-forge
# List dependencies of `imdclient`:
mamba repoquery depends imdclient --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 imdclient 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/imdclient-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.