Mapping of state variables to GeoVal space

hello, everyone,

I have got one naive question about JEDI: It seems that in JEDI, every obs type calls a required subset of read-in state variables, as well as specific derived state variables; then these variables are interpolated into “geoval” space. It is not clear to me is what settings/codes define the mapping of these variables for each obs type in JEDI? This info seems crucial to understand the process and for implementation of new variables used with obs operators.
Thanks for your explanation of this!

Hi. The JEDI Core Algorithm team currently has a weekly online (Google Meet) drop-in meeting on Thursdays at 10 a.m. Mountain Time. Would it be possible for you to come to that? I think that might be a more efficient way for us to understand your question and help you. Here is the information:

Drop-in for JEDI-Algorithms Q&A
Thursday, March 14 · 10:00 – 11:00am
Time zone: America/Denver
Google Meet joining info
Video call link:
Or dial: ‪(US) +1 980-239-7447‬ PIN: ‪564 845 436‬#
More phone numbers:

Yes, this is great!! I will be at the meeting.

The problem I encountered was that I added a code/function to do the variable change for a new derived variable y in “Model2Geoval”, but this did not go through and JEDI still looked for this new derived variable from I/O read-in state variables. I think I still have missed something.

I think a flow chart showing the detailed steps on how to add a derived state variable for use with UFO operators would be very helpful, similar to “how to add an obs operator or a model”.

My code modifications and error output info are in:

Thank you!