wiki:access/JEDIAtNCI

Version 4 (modified by Jin Lee, 19 months ago) (diff)

--

JEDI at NCI

In early 2020 UKMO formally commenced and committed substantial resources to the Next-Generation OPS (NG-OPS) and Next-Generation DA (NG-DA) projects. Both projects rely heavily on JEDI with UKMO concentrating development on components that it requires to implement its specific data assimilation schemes and observation processing. Their aim is to have JEDI-based DA system which is comparable to the current operational system ready by mid-2023 (the Bureau has not had access to the final project plans as of May 2020).

At time of this writing (May 2020) the Bureau's position is uncertain as to how to respond to the development. Anticipating that the Bureau will commit commensurate resources to JEDI-based NG-OPS and NG-DA projects the Data Assimilation Team has begun familiarisation with various components of JEDI itself. This is to enable early adopters to explore opportunities to collaborate with their UKMO colleagues so that when the Bureau formally decides to participate in the NG projects as a part of a partnership-wide effort we are ready to make contributions very quickly.

In this wiki page and the links in it we attempt to record various JEDI-related work undertaken by DA Team members.

Software stack for running JEDI applications

JEDI applications depend on a large number of software packages. The group of packages needed to run various JEDI applications is referred to as jedi-stack. The scripts used to build the packages are host in one of the JCSDA github repositories,

Jin LEE and Wenming LU did the initial build and installation of jedi-stack on Gadi. Building of the sotware packages is documented in a site-spefic document (????). The installation step is documented in jedi-stack github issue #93. Some of the the decisions made at the time of the initial build/installation were provisional and there is an ample room for improvement. We list below some of these decisions which are not documented in the github issue.

  • The tcl modulefiles do not have tag names. This is ????

Running JEDI subsystems

First obtain a github account. However, this will not allow you to access all the private repositories.

JEDI Academy temporary account.

Set up your environment by starting jedi-stack,

unset PYTHONPATH
OPT
module use
module loads

You might like to put the commands above in your start-up script. Note that jedi-stack has its own set of Python packages (exclusively Python3).

Try building and running ufo-bundle (In JEDI a group of packages is referred to as a bundle)

Documentation

ToDo?.Upload various documents under ~access/public_html/jedi/doc