Ants module availability in xp65 analysis3 kernels

Technical Infrastructure
, ,
21

I’ve not looked at ANTS for a while, it is now public on github with the environment definition and conda lock file that it wants to be using - GitHub - MetOffice/ANTS: A Python library for generating UM ancillary files, developed at the Met Office (the contrib code that actually generates the ancillaries is still private I think?)

There are two use cases to consider:

  • If we’re generating ancillaries for future use we should make use of the lock file to generate a conda environment, this way the ancillaries can be re-created exactly the same in the future.

  • If we’re developing ANTS code then it would make sense to install it into a larger environment with Jupyter etc.

1 Like
22

I agree with Scott, and I would add that we are planning to release new ANTS versions in a dedicated containerised environment on Gadi (similar to Scott’s ngm one).

However, the main issues remain:

  • ANTS strict dependency pinning (which makes it very hard to install in an environment together with other packages)
  • no distributions are available (meaning we have to manage distributions, for example Conda or PyPI, ourselves)

Now that ANTS, as other UKMO tools, are on GitHub, I think it will be easier to have released distributions of ANTS and other tools (e.g., mule, shumlib, ug-ants, etc.) directly connected to their respective GitHub repos and managed in collaboration with the MetOffice.

There is a related issue for mule, for which Scott also has a conda-forge package proposal in queue for review.

I think similar procedures should be put in place for ANTS.

23

Thanks @atteggiani, can you please confirm that analysis3-25.08 will remain active (currently throwing warning on load that it will soon be depreciated) until the release of the dedicated seperate ANTS environment? Can you also please confirm which other packages are planned to be included in the seperate ANTS environment?

24

I’ll defer to @rbeucher on this, as the ACCESS-NRI MED team is managing the analysis3 environments.

There hasn’t been a discussion about this yet.
When the deployment infrastructure is ready (hopefully within a month), I think this could be a good topic to discuss in a Working Group (maybe the Atmosphere one?).

1 Like
25

Hi @mlipson

We will not deprecate the environment without providing an alternative for your workflow.
As @atteggiani said, we have flagged the issue with the developers. There have been some changes recently, and we are hopeful we will be able to make the new packages available soon.

2 Likes