Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In response to a question by Chris H, Mark M clarified what we mean by the "new versions" of ecbuild and eckit.   We are now using the JCSDA forks for both of these repositories.   If you are building eckit as part of your bundle and/or using an uninstalled version of ecbuild, then it is ok to just use the latest jcsda::develop branch of each.  However, to track the versions of ecbuild and eckit that are installed n in the containers and environment modules, we have begun using tagged versions of each.  These tagged versions will generally end with a patch number of the form .jcsda<x>, where <x> is a number.  For example, at the time of writing, the most recent tagged versions are 3.1.0.jcsda1 for ecbuild and 1.4.0.jcsda2 for eckit (jcsda fork).  However, there are active pull request in each of these repositories so that may change in the coming week.  If you intend to work with the tagged versions of ecbuild and eckit, navigate to the repository in question on jcsda GitHub and select the releases tab in the menu bar right above the code.  Then choose the release with the most recent jcsda patch.

...

Maryam went on to say that our changes to ecbuild now make it possible for us to store test files on any remote repository that can be accessed on the web (via curl or wget).  We're using Amazon Web Services (AWS) S3 for now but this could be changed if needed.  Maryam also mentioned that there is a new test that will check to see if the test data files are already available, and if not, it will download them from the remote repository.  If this test determines that it must download and cannot do so, then the test will fail.   So, if Maryam has submitted pull requests for ufo, ioda and fv3 repos containing this new download test.  If you are on a secure system that does not have access to external internet sites such as AWS S3, then you can upload the test files to your system separately.

Maryam also said added that there is also a current pull request in saber that does the same thing, namely storing the test files on S3 instead of on git-lfs.  But, most developers will be less impacted by this because the saber test files are only used by the saber tests but the ioda test files are used by multiple repositories.  Still, after this PR is merged, many saber tests will fail if you are using an old version of ecbuild.

...

Xin then reported that his variable bias correction implementation for amsua and iasi is complete and he confirmed with Emily that it reproduces the GSI results.  Next he plans to work on the pre-conditioning.

...