Esmvaltool: Monthly ESMValtool meeting December

[bouweandela]

The next monthly ESMValTool meeting will be in December. The result of the poll is that it will be on

Monday, December 7 at 10:00 CET (09:00 GMT).

The duration will be one hour. Join the zoom meeting.

Calendar invitations to the meeting are sent to the mailing list, join it here.

@ESMValGroup/esmvaltool-developmentteam

Format and agenda

• Anyone with an interest in ESMValTool is welcome to join and ask questions
• We start the meeting by doing a round where everyone gets one minute to introduce themselves and tell what they will be working on in the next month or what they would like help with.
• Using the input from the introduction round, we can decide to talk about specific topics with the entire group or make smaller breakout groups to continue the discussion there.
• If you already know that you would like to bring up a particular topic in the meeting, you can mention the GitHub issue on the topic in a comment in this issue. That will make it easy to find for other people in the meeting and we can already start discussing there before the meeting. Just create a new GitHub issue about your topic if there is no open issue yet.
• GitHub issues are our preferred way to communicate outside the meeting and keep track of work, so any feature requests/action items/etc discussed in the meeting should ideally result in a GitHub issue.

Notes from the previous meeting can be found here: https://github.com/ESMValGroup/ESMValTool/issues/1836#issuecomment-722419443

[bouweandela]

@malininae My apologies for picking a time that was not suitable for you, this was the option where most people could make it. I hope you'll be able to join some other time!

[malininae]

@bouweandela, no worries, i'll bug you with questions on github :-)

[bsolino]

I'm working on solving issue 312 from ESMValCore, and I will be doing that on the linked PR 894.

[nielsdrost]

Thanks for attending @ESMValGroup/esmvaltool-developmentteam!

Feel free to correct this comment if you find and errors and/or omissions.

News from the community

• @bouweandela will be on holiday for the remainder of the year.
• @remi-kazeroni is Fixing some CMIP6 and/or Observational data (and is taking care of the OBS data collection now).
• @bsolino is getting started, and working on the on-the-fly cmorizer for EMAC.
• @axel-lauer is working on more advanced extract level on pre-processor (ESMValGroup/ESMValCore#892, tech review please), and cmorizing cloudsat data.
• @ruthlorenz is working on ESMValTool (CLIMWIP) together with @lukasbrunner (and @Peter9192)
• @jvegasbsc will be on holiday from tomorrow and is working on a monitoring tool.
• Jonathan (@?) is new(hi!) and involved in a PhD project from the forest and landscape community where they look into fire weather indices.
• @bettina-gier is working on cmorizers for a few datasets she needs for a few papers.
• @schlunma is implementing fixes for Cloud related variables required for a paper by himself and Axel.
• @katjaweigel got Reviews for "Paper 4" in the ESMValTool series. The reviews seem doable, but timing is an issue as the deadline is early januari. She is also working on ERA5-Land support.
• @ledm is working on IPCC reports and is finding lots of problems with ocean data, such as cell volume missing everywhere.
• @nielsdrost requested GitHub Discussions for ESMValTool. This should help with answering questions from the community.

ERA5-Land

We decided to take the discussion on ERA5-land support offline (probably involving @SarahAlidoost and @katjaweigel , and perhaps @nielsdrost and @Peter9192)

Extended checks

A recent addition of checks on certain variables has caused ESMValTool to refuse to read in a number of datasets. This is leading to problems for some recipes. We discussed how to best handle this and decided on a two-fold approach:
1) Report the problems to the model authors and get a fixed dataset, or at the very least some info on how we could fix the datasets ourselves
2) @jvegasbsc will look into creating a way of introducing a "fix" that does not actually fix anything but allows the dataset to pass the test. He'll come up with a proposal for comments. ESMValGroup/ESMValCore#882 could be a source of inspiration for this.

Project Board

We discussed using the project board a bit more, but decided to (for now) only use them during workshops.

Reviews

It is unclear how the review groups work, and how to sign up for them. We should add better documentation, e.g. by adding some info on them to the readthedocs documentation.

Community communication

We will have a GitHub discussions on the ESMValTool repo soon(TM). This will allow us to answer questions from the community more easily, and use the mailinglist purely for announcements.

@axel-lauer will send out a request to please signup for the mailinglist, and perhaps point at the Discussions platform, as soon as it is ready.