Monthly ESMValTool community meeting August 2022

[bouweandela]

The next monthly ESMValTool community meeting will be in August. The result of the poll is that the meeting will take place on

Friday, August 5 at 14:00 CEST (13:00 BST).

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 below. 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 are available in #33 (comment)

[ehogan]

Quick question: did a calendar invite get sent for this meeting?

[valeriupredoi]

#41

[valeriupredoi]

ah well, here's a first, I added a link to this very post 🤣

[bouweandela]

You can see the message in the mailing list archive here: https://www.listserv.dfn.de/sympa/arc/esmvaltool/2022-08/

[ehogan]

The message wasn't trapped by our quarantine, so I'm going to put it down to a glitch in the matrix 😝

[ehogan]

Hmmm, so the invite just came in 🤔

[ehogan]

Would it be possible to discuss ESMValGroup/ESMValTool#2723 at this meeting, please?

[bouweandela]

@ehogan Asked at the meeting if there are any objections to the proposal. So please share any ideas you have with her. She will start implementing this next week and do a demo at the next monthly meeting.

[ehogan]

Would it be possible for @mo-tgeddes to share the dates for the autumn workshop at this meeting, please? See #45 :)

[ehogan]

Would there be time for @mo-tgeddes to demo the CLA assistant at this meeting? :)

[bouweandela]

@axel-lauer Asked where the information on who signed it is stored

[bouweandela]

@rswamina Asked if there is an issue open about this already. @ehogan said not yet.

[ehogan]

@rswamina also asked whether the CLA would need re-signing regularly e.g. every year :)

[mo-tgeddes]

@axel-lauer Asked where the information on who signed it is stored

The data is stored in a a cosmosDB (mongoDB compatible) hosted on Microsoft Azure in Europe.
Here is where I found the information if you want to know more. : )

[mo-tgeddes]

@rswamina also asked whether the CLA would need re-signing regularly e.g. every year :)

Apologies for the delay. The CLA won't time out, you will only have to resign it if there are changes made to it. You can withdraw your signature through the CLA user interface if you need to.

[valeriupredoi]

gonna also ask who is about in August so we can get a Tech Lead call meeting too - if it's too few of us in the trenches and not on some beaches then I'll send around a Doodle for the TL call 👍

[bouweandela]

Update round summary:

• @ehogan Would like to talk about the topics before (recipe test workflow, workshop at met office, demo cla assistant)
• @rswamina Working on extracting IPCC AR6 regions, getting feedback on tutorials
• @axel-lauer Working on support for new datasets. Please have a look at the pull requests for updating the documentation on clarifying the @ESMValGroup/esmvaltool-recipe-maintainers role in Extending documentation: recipe maintainer + broken recipe policy ESMValTool#2719 and the new policy for broken recipes in Extending documentation: broken recipe policy ESMValTool#2720
• @tepmo42: developing jetstream recipe
• @bsolino: working on integrating analysis into ESMValTool
• @catherinehardacre: working on support for new datasets
• @glpotter: working on CMORizer, would like some help with the YAML
• @rswamina mentioned that @remi-kazeroni Is updating the tutorial regarding CMORizers
• @bouweandela is working on adding an esmvalcore.dataset.Dataset object that can be used to load datasets in Python without using a recipe in Support wildcards in the recipe and improve support for ancillary variables and dataset versioning ESMValCore#1609. By using this object also internally to load recipes, the maintainability of the recipe parsing code can be improved and several open issues can be solved more easily.

[bouweandela]

CMORizers

• @glpotter is having trouble making the CMORizer script find his updated MERRA2.yml file (Cmorize 3D variables for MERRA2 ESMValTool#2718).
• @bouweandela will send @glpotter the contact info of our PIs @hb326 and @alistairsellar

@catherinehardacre asked about CMORizing station data. Previous discussion on the topic was here ESMValGroup/ESMValTool#496 ESMValGroup/ESMValTool#1119. The recommendation was to put all the data in a single file. The CF-Conventions for storing station timesries data are available here, other types are also available. Documentation for creating a new CMORizer lives here.

[bouweandela]

@valeriupredoi Will organize the next @ESMValGroup/technical-lead-development-team meeting end of August

[valeriupredoi]

yep - on it, even it's well into September now 😆

[glpotter]

Thanks,I just did the pip install -e .[development] and it works now. I’ll go ahead an add the 2D and 3D variables into my MERRA2.yml. Jerry

…

On Aug 5, 2022, at 5:58 AM, Bouwe Andela ***@***.***> wrote: CMORizers @glpotter <https://github.com/glpotter> is having trouble making the CMORizer script find his updated MERRA2.yml file (ESMValGroup/ESMValTool#2718 <ESMValGroup/ESMValTool#2718>). @bouweandela <https://github.com/bouweandela> will send @glpotter <https://github.com/glpotter> the contact info of our PIs @hb326 <https://github.com/hb326> and @alistairsellar <https://github.com/alistairsellar> @catherinehardacre <https://github.com/catherinehardacre> asked about CMORizing station data. Previous discussion on the topic was here ESMValGroup/ESMValTool#496 <ESMValGroup/ESMValTool#496> ESMValGroup/ESMValTool#1119 <ESMValGroup/ESMValTool#1119>. The recommendation was to put all the data in a single file. The CF-Conventions for storing station timesries data are available here <https://cfconventions.org/cf-conventions/cf-conventions.html#time-series-data>, other types are also available. Documentation for creating a new CMORizer lives here <https://docs.esmvaltool.org/en/latest/community/dataset.html>. — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADMMZ7GMQZJP2ORXSGMCC53VXUFVTANCNFSM54RJKXBQ>. You are receiving this because you were mentioned.