Agenda ESMValTool Workshop May 13-15 Oberpfaffenhofen, Germany.

[bettina-gier]

Heyo @ESMValGroup/esmvaltool-developmentteam,

the next Workshop in Oberpfaffenhofen is approaching fast, and it is time to collect topics for the agenda! If you have anything you would like to discuss in the workshop, drop a comment down below. Please also let us know whether you would be fine organizing and chairing a session and/or preparing a contribution for a session. We hope to see many of you there!

Preliminary Agenda points:

Tuesday May 13:

• User Engagement Team Meeting
• Discussion about the tutorial

Wednesday May 14:

Thursday May 15:

Unassigned:

Technical Advancements

• Technical DevOPs Update (V)
• More flexible fix functions, see Rethinking fix_file ESMValCore#2129 and Allow fix_file to return dataset objects ESMValCore#2579

Future directions

• Suitability of the REF to monitor/evaluate native model output (in our use case ICON data on Levante). How would this look like? How difficult would it be to set this up? Can it be extended with arbitrary diagnostics?

[valeriupredoi]

Tina, please pen me down for my usual Technical DevOps Update (the one that is so boring it's got Health&Safety Hazard signs all over it), also I can chair/armchair/chaiselong/stuhl/stool etc 🍻

[rswamina]

I request that we have any User Engagement Team meetings and tutorial discussions for the 13th of May. Thanks!

[hb326]

Registration for the workshop is open now!
See #218.

[schlunma]

Topics I would like to talk about:

• More flexible fix functions, see Rethinking fix_file ESMValCore#2129 and Allow fix_file to return dataset objects ESMValCore#2579
• Suitability of the REF to monitor/evaluate native model output (in our use case ICON data on Levante). How would this look like? How difficult would it be to set this up? Can it be extended with arbitrary diagnostics?

[bouweandela]

Suitability of the REF to monitor/evaluate native model output

The REF could be very suitable for this: it takes existing recipes and uses the list of available input files from its database to generate recipes that use newly added data and analyses those and it will include a system for viewing the results too.

Can it be extended with arbitrary diagnostics?

Yes, by creating a new diagnostics package, similar to https://github.com/Climate-REF/climate-ref/tree/main/packages/ref-metrics-esmvaltool.

[jlenh]

Quite interested in the REF to monitor/evaluate native model output topic and extension with other diagnostics!

[ehogan]

Would it be possible for me to provide an update on the Recipe Test Workflow (RTW), please? 😊

[bouweandela]

It would be nice to brainstorm about deploying the RTW somewhere so we can use it for regular testing too

[valeriupredoi]

that ⬆️

[hb326]

@ESMValGroup/esmvaltool-developmentteam: Last chance to add something to the workshop agenda!!
We will close the collection of ideas on Wednesday next week (April 30th), and start putting the agenda together.
So please put your ideas down here!

[bouweandela]

It would be nice to present what the REF can currently do, which ESMValTool diagnostics have been integrated, and see if we can improve those, e.g.:

• Ensure all figures look good and have meaningful captions when run through the REF
• Update the recipes so they use obs4MIPs data when available
• Check that the integration of the recipes into the REF was done right, e.g. are we selecting the right timeranges to analyze

[schlunma]

One more topic I'd like to discuss (since we have a project deliverable that needs this): Support for intake, zarr, and HEALPix.

[bouweandela]

See ESMValGroup/ESMValCore#2584 for the plan and ESMValGroup/ESMValCore#2690 for some work in progress

[katjaweigel]

I'll not attend ESMValTool Workshop this time :( to learn something about HEALPix in that week (and because @bettina-gier was even more eager to meet you all again, so we decided that she has to be at the ESMValTool workshop and I will look at high res model HEALPix data).

[bouweandela]

Here is a nice presentation from EGU25 related to regridding to/from HEALPix that @valeriupredoi shared with us: https://github.com/IAOCEA/regridding-ecosystem-overview

[bouweandela]

It would be nice to talk about how we can keep our installation methods up to date and gather feedback on potentially switching from conda/mamba to pixi. I created this issue to provide some background information: ESMValGroup/ESMValTool#3997

[flicj191]

Could revisit documentation with emphasis on ESMValCore and ESMValTool. ESMValGroup/ESMValTool#3860 and example ESMValGroup/ESMValTool#3914 (comment) for smaller steps. Probably shorter than previous discussions.

[axel-lauer]

@ESMValGroup/esmvaltool-developmentteam, the first draft agenda for the next ESMValTool workshop is now available for your comments and feedback!

Agenda ESMValTool Community Workshop 2025 (hybrid meeting)

Version 5 May 2025

(all times are given in CEST)

13 May 2025 - Day 1 (Tuesday)

9.30 am – 9.45 am Introduction, welcome and workshop agenda (Birgit)
9.45 am – 10.30 am Updates and technical developments

• Technical Updates (V)
• Update on the Recipe Test Workflow (RTW) (Emma)

10.30 am – 10.45 am Coffee break
10.45 am – 11.30 am User Engagemeent Team updates (Ranjini)

• Updates on User Engagement Team activities (Ranjini)
• Revisit documentation with emphasis on ESMValCore and ESMValTool (see Documentation separation ESMValTool and ESMValCore ESMValTool#3860 and Separate ESMValTool and ESMValCore documentation ESMValTool#3914 (comment)) (Felicity)

11.30 am – 12.15 pm Future Technical advancements (Bouwe, Manuel, Tina)

• More flexible fix functions (see Rethinking fix_file ESMValCore#2129)
• Allow fix_file to return Cube and CubeList objects (Allow fix_file to return dataset objects ESMValCore#2579)
• Support for intake, zarr, and HEALPix (Tina)

12.15 pm – 01.15 pm Lunch break
01.15 pm – 01.30 pm Introduction of possible coding sessions
01.30 pm – 03.30 pm Coding session (all)
01.30 pm Parallel session: User Engagement Team Meeting
03.30 pm – 04.00 pm Coffee break
04.00 pm – 05.00 pm Summary and wrap up of day 1 & discussion (Birgit)

14 May 2025 - Day 2 (Wednesday)

9.30 am – 9.45 am Introduction day 2 and workshop agenda (Alistair)
9.45 am – 10.30 am Rapid Evaluation Framework (REF)

• Overview: currently status and ESMValTool diagnostics that have been integrated (Bouwe)
• Discussion on improvements and further development (Bouwe)
  • Ensure all figures look good and have meaningful captions when run through the REF
  • Update the recipes so they use obs4MIPs data when available
  • Check that the integration of the recipes into the REF was done right, e.g. are we selecting the right time ranges to analyze

10.30 am – 10.45 am Coffee break
10.45 am – 11.15 am Rapid Evaluation Framework (REF) – continued
11.15 am – 12.00 pm open slot
12.00 pm – 01.00 pm Lunch break
01.00 pm – 01.10 pm Preparation for coding sessions
01.10 pm – 03.00 pm Coding session (all)
01.10 pm Parallel session (Alistair): Horizon SERV call (HORIZON-INFRA-2025-01-SERV-02) ESMValTool - tasks in the ENES-RI proposal (Alistair)
03.00 pm – 03.30 pm Coffee break
03.30 pm – 04.00 pm Coding session (all)
04.30 pm – 05.00 pm Summary and wrap up of day 2 & discussion (Alistair)
06.30 pm Workshop dinner

15 May 2025 - Day 3 (Thursday)

9.30 am – 9.40 am Introduction day 3 and workshop agenda (Birgit)
9.40 am – 10.30 am Future directions

• Suitability of the REF to monitor/evaluate native model output (e.g. ICON output on Levante): How would this look like? How difficult would it be to set this up? Can it be extended with arbitrary diagnostics? (Manuel)
• Keeping our installation methods up to date and gather feedback on potentially switching from conda/mamba to pixi (see Installing ESMValTool and dependencies - a look at the future ESMValTool#3997) (Bouwe)
• Workflow and support for developing IPCC AR7 diagnostics (Lisa)

10.30 am – 10.45 am Coffee break
10.45 am – 11.15 am Future directions - continued
11.15 am – 12.00 pm General discussion and open floor
12.00 pm – 01.00 pm Lunch break
01.00 pm – 01.10 pm Preparation for coding sessions (V)
01.10 pm – 03.00 pm Coding session (all)
03.30 pm – 04.00 pm Coffee break
04.00 pm – 05.00 pm Summary and wrap up of day 3, future workshops & discussion (Alistair + Birgit)

[rswamina]

@axel-lauer - I had requested that we discuss User Engagement/tutorial business on 13th (see above). I am not attending the workshop on 14th and 15th. Please can you move the tutorial session ato 13th? If this is hard, I will ask @LisaBock to update and share anything I have with her. Let me know.

[axel-lauer]

No problem, I moved the tutorial session to the first day. There will be probably a bit more shuffling around anyways...

[jlenh]

Hello! Here are some open PRs ready for review. Feel free to ping me if you need a review too :)
(I will update this list as I progress in finalizing some other open draft PRs)

---

• REF Climate drivers of fire diagnostic:
• ESMValTool dev branch w/ diagnostics for burnt area, fire weather control, fuel load/continuity PR
  Disclaimer: There is some overflow happening during processing which produces values of 1 everywhere for some outputs. This will be soon solved w/ the updated offline optimization model files necessary for this diagnostic, but the code will not change in itself. The Earth will not fully burn, no worries.
  Provenance was forgotten, to be added this week!
  @malininae will look at it later this week.

---

• Surface trace gas diagnostic: requires the following pull requests to be merged
• ESMValCore dev branch w/ preprocessor surface extraction from 3D atmospheric variables PR. Review by @schlunma.
• ESMValCore dev branch w/ custom entry for surface N2O variable PR. In this PR, I do not know the root of the warning/errors during the doc building. Review by @schlunma.
• ESMValTool dev branch w/ downloader/cmorizer for NOAA GML data PR reviewing @bettina-gier

[jlenh]

Thanks a lot @schlunma and @bettina-gier 😎

[bettina-gier]

Would also be good if we could tackle the ORAS5 cmorizer on the fly PR review
ESMValGroup/ESMValCore#2422