General update (Francois H.)

JEDI Infra (Evan)

[Dom]: Spack-Stack 1.8 has been released. It is installed on Discover and parallel clusters. On S4, it is holding back until the system upgrade. For EMC people, there is a problem on Orion and Hercules. You will not be able to use 1.8 for JEDI until the Intel compiler libraries fixed.

[Francois H.]: Have a follow-up question which is you've described a problem with So Intel? Is the spec stack 18 available with new on these systems or not at all?

[Dom]: Yeah.

[Steve V.]: Are there any issues with Macos and is all the documentation updated for building on the Mac?

[Dom]: Steve submitted a PR to fix all that and I was specifically for Sonoma with Xcode 15. It is definitely not supported at the latest MacOS, Sequoia. I think it calls Xcode 16, so stay away from that.

[Evan]: Sonoma is the best platform for using Spack-Stack.

[Dom]: Add one more thing. We are targeting end of the year to go back to the 3-month cycle. Spack-Stack 1.9 will be released at the end of this year, every one feels free to update or skip one version.

JEDI Algo (Clementine)

[Steve V.]

[Hernan]: Are the new system on names are going to be hard coded or set dictionary in YAML file?

[Steve V.]: They will be hard coded, because they spread across multiple repos.

Hernan expressed his concern about it is too rigid and wonder if there is an easy to manage, like a central dictionary can access and propagate.

[Steve V.]: The idea is once we get these strings in, even though they are hard coded. They will be very specific all over the places. Hopefully we can simply edit it in the future.

JEDI Model Interface (Francois H.)

OBS (Hui)

[Ricardo]: How does JEDI handle the different versions of Spectral coefficient files in CRTM?

[Ben R.]: It is related to workflow, we want to control it by the YAML file explicitly.

[Ben J.]: Additional context for that. One of the points of confusion was the inconsistencies in the CRTM. Sometimes we have file named V2, but the sensor ID in the file is different. We are trying to slowly get rid of this and just make it where the file name and the sensor ID internally are the same. As we are transitioning toward NetCDF only, we hope some of the issues will go away a little bit. We are trying to make sure everything is consistent with expected behavior. Hopefully this will help smooth over some of the confusion we have had to deal with in the past.

CRTM (Ben J.) 

Ricardo and Ben J. have some discussions about the skin temperature increments. Ricardo feels the T-skin increments looks reasonable in GSI but weird in JEDI. Ben J. mention there is a lot of challenges in this topic, if somebody would like to start a discussion topic on it, he would be happy to contribute. Ricardo said there is one already and he will update and add more information on that.

COMPO (Jerome)

SOCA (Hamideh)

Ben J. asked for clarification about the meaning of composite operator. Greg added that is to be able to perform two different operators on a set of simulated variables, in which case some variables are using one, operator and some are using the other. And Greg mentioned that Mike Cook may be able to provide solution on this.

[Kriti]

Francois H. added that a PR is in and it is one step closer for you to put in the mask with more generic way. We can get that work quite soon.

EMC (Dan)

Tom asked about the distribution work is during IO or in memory. Dan responded that is in memory. Francois added that what decouple the file structure and tied to how many nodes are doing IO. Dan added, switching to HDF5 structure in IODA speed up massively and the work is getting there.

GMAO (Ron, Ricardo, Doruk)

[Ricardo]

[Doruk]

Ron mentioned Virgnia Bouchard’s work on aerosols but she was not in the meeting, so Jerome provided brief update on her work

[Jerome]

Ricardo added that GMAO is starting to do some comparison to the present system. Jerome added that we should decide on a long-term direction for aerosols. Some discussion about the B

Met Office (Phil U.)

Navy (Sarah)

ROMS (Hernan)

Tom: