CDO

hi nils!

there are errors during the package update process that are non-reproducible on a local machine. Hence the delay

cheers
ralf

Hi Ralf,

I understand that there are errors during the packaging (https://code.mpimet.mpg.de/boards/2/topics/16287). Since it has been more than 6 months, it would be nice to point everyone to an alternative for the time being.
That is why suggested to do one of the following:
a) Mark the current Conda version as deprecated until updates resume.
b) Place notes at https://anaconda.org/conda-forge/cdo and the Anaconda wiki entry to use Spack as an alternative.

This way, everyone is aware of the problem and can use the newest version of CDO (with all the bug-fixes).

Cheers,

Nils

Hi there

I know this is not prioritary for CDO-developers - and I understand not all the release can reach conda-forge - but it would be great conda release if a new release can be provided in the near future.

We are really loving using CDO via conda since it simplifies a lot of deployment issues, we are still using 2.5.0 but it would be great to have 2.6.0.

Hi Paolo!

the plan is: release 2.6.1 will get a conda package (in about 2 weeks). the problem is with certain operators, which create wrong results when build as a conda package. Conda uses a target for compilation that provides maximum portability but lacks certain level of precision, which can be problematic for certain algorithms.

sry for the delay. I did not want to publish a conda package which potentially gives incorrect results - hence the delay

cheers
ralf

Thanks Ralf, the explanation makes a lot of sense, and I see your concerns.
I will be then waiting for the new release, fingers crossed it will work smoothly!

if you are in a pinch and need something locally, you can check the package manager spack. I keep the CDO package up-to-date. But it requires a different level of will to install things compared to a pre-build conda version. And you can hardly ship software environments as easy.