[pychrono] conda environment from file

[Dmitriy Ivolga]

Hello!

First of all, I want to express my gratitude to Chrono Project. I wish you luck and further achievements in its development!

My question is about the versions of PyChrono and building the environment from a file using conda. Our team uses PyChrono as a physical simulator for robot grippers. In the future we would like to publish our application in public access. But there is a question about native and automatic environment creates. We have noticed that there are differences between some versions of builds/builds of PyChrono. Also, over time older builds are removed from the list of builds available to install through conda (https://anaconda.org/projectchrono/pychrono/files) (e.g. we used to use build 2122, which cannot be installed through the command line now). Yes, we know about installing from archive, but creating environment this way is not always possible because of dependencies conflicts.

Is it possible to make preservation and support of some PyChrono builds on conda as "stable" or "long support"? I.e. different versions are published, but there is some set of "gold/stable" solutions that would be available for a long time to install through the command line and not be removed from the repository after a few months? That would make it much easier to reinstall and reuse environments within commands and to demonstrate solutions. Perhaps you can suggest a different solutions.

With regards, 

Dmitriy

[Radu Serban]

Hi Dmitry,

 

Happy to hear that you find our software useful.

 

Regarding the PyChrono conda packages, I certainly understand the need for stable versions, and we certainly plan on providing that. The reason things have been in such flux lately is that we have embarked on a CD refactoring and as such generated a lot of test packages from different branches and with different options.  Combined with the fact that we were running out of space on anaconda, we kept deleting older versions.

 

We are very close to settling on a final version of the deployment scripts and things will settle down.  Moving forward, we will keep all conda package versions we generate (periodically, using the latest development Chrono code) and label those ‘main’.  In addition, we will generate conda packages labeled ‘release’ whenever we have a new Chrono release (one is planned in the near future).

 

I hope this will address your current concerns.  If you have other suggestions, I’d be happy to hear them.

 

Best,
Radu

--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/bf7e021d-e23d-4630-bd40-02cb4656c168n%40googlegroups.com.