Conda distribution

[Golui]

As per #494, PySDM should get a release for the Anaconda ecosystem. While I'm not an expert, I can at least create a barebones configuration file.

With my limited of package distribution via conda-forge, there are several issues with this at the moment:

• Since all the dependencies need to be in the Anaconda ecosystem, as @slayoo already mentioned in conda-forge package for installation of non-Python dependencies? #494, ThrustRTC and CURandRTC do not have (recent) releases for Anaconda.
• A similar issue exists with chempy - while it does have an old Anaconda distribution, it is on a relatively unpopular channel (bjodah). This means that the install command is unintuitive, and the issue is not immediately obvious. This would not be a problem if this issue gets resolved.

To build the Anaconda package:

cd PySDM
conda-build . -c conda-forge -c bjodah
# activate your virtual environment
# for example: conda activate PySDMEnvironment
conda install --use-local PySDM=1.4 -c conda-forge -c bjodah

As a side note, here you can find the documentation for the meta.yaml file.

[slayoo]

Thank you!

[slayoo]

Thanks to @fynv, the ThrustRTC package is now updated: https://anaconda.org/fyplus/thrustrtc

[slayoo]

one only thing I would find essential before merging is to have the added meta.yaml file somehow included in the CI workflow - I guess one way would be to create a new Github Actions script with something along:

pip install conda
cd PySDM
conda-build . -c conda-forge -c bjodah
conda activate PySDMEnvironment
conda install --use-local PySDM=1.4 -c conda-forge -c bjodah

does it make sense?

BTW, @Golui what is the rationale to have the 1.4 tag above and the git rev in the meta file?

[Golui]

one only thing I would find essential before merging is to have the added meta.yaml file somehow included in the CI workflow - I guess one way would be to create a new Github Actions script with something along:

pip install conda
cd PySDM
conda-build . -c conda-forge -c bjodah
conda activate PySDMEnvironment
conda install --use-local PySDM=1.4 -c conda-forge -c bjodah

does it make sense?

BTW, @Golui what is the rationale to have the 1.4 tag above and the git rev in the meta file?

Apologies for the late reply @slayoo.

To my understanding, conda pulls the repository when installing the package. The git rev points to the commit tagged "v1.4" in the repository, matching the latest official release. You can, I believe, use a different option to just use the tag in the config.

The "meta.yml" that conda-build uses isn't strictly speaking a YAML file; the file is put through a template engine to create the real configuration. The version on the top is just defining a variable that can be used in the meta file.

[slayoo]

Let's close this and the PR for now. If there is any reason why conda users should not just open anaconda prompt and do pip install PySDM, please reopen