Monthly ESMValtool meeting November

[bouweandela]

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

Thursday, November 5th at 13:00 CET (12:00 GMT).

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

@ESMValGroup/esmvaltool-developmentteam

Format and agenda

• 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 link the GitHub issue to this issue so it's 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 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: #1813 (comment)

[bjlittle]

@bouweandela It would be great to get some feedback on esmvaltool testing of the iris release candidate v3.0.0rc0, see #1854 👍

[bouweandela]

Were working on it in issue ESMValGroup/ESMValCore#378 and pr ESMValGroup/ESMValCore#819, the first results look promising.

[bouweandela]

Thanks for attending @ESMValGroup/esmvaltool-developmentteam!

Here is a summary with some news:

• @axel-lauer has created an agenda for the upcoming workshop (virtual, november 24-26) here: ESMValTool workshop on November 24-26, 2020 #1866 (comment), please comment in the issue if you would like to add something and invite all (potential) ESMValTool enthusiasts you know to join the workshop!
• @bjlittle and @stephenworsley from the iris development team joined us, they expect to release iris 3.0 mid november, see here for the latest features, that we'll hopefully be able to use soon in the ESMValTool too. They plan to make about 3 releases a year (and more frequent bugfix releases) after this release, possibly staggered in time with the ESMValTool releases (release schedule).
• @zklaus is working on a lazy regridding package for grids with 2D lat/lon coordinates that can be used with iris iris-esmf-regrid, based on the same idea as iris-ugrid that and @stephenworsley is working on. This will allow us to process much larger ocean datasets and might offer some speed improvements too.
• @bjlittle @zklaus it might be good to also be aware of these fancy grids that @remi-kazeroni @koldunovn are looking into Working with unstructured ocean AWI-CM data ESMValCore#751
• @valeriupredoi stressed that it is vitally important to have scientists on board when building new features in software and suggested that @ledm join the discussion on improving iris so it supports the ocean data use case better
• @bouweandela Mentioned that it would be good to look through the ESMValCore preprocessor functions to see if there are additional points for improving support for 2D lat/lon coordinates in iris
• @ledm Stressed the importance of support for ancillary variables and cell measures, that will much better in iris 3.0 and then needs to be integrated in the ESMValCore for proper support
• @valeriupredoi came up with the idea to have regular meetings with the three different teams (science lead, technical lead, and user engagement) we will have starting next year in addition to the general monthly meeting, to make sure the content of the meetings is relevant and fun for all participants
• @stefsmeets Mentioned that good progress with made with using the iris 3.0 release candidate with ESMValTool [PI] Test ESMValTool with Iris 3.0.0rc0 #1854
• @rswamina mentioned she has a deadline in two weeks from now and would like some help with certain issues. @rswamina Could you mention them here to see you can find some help?
• @Peter9192 @SarahAlidoost @nielsdrost @JaroCamphuijsen @stefsmeets and @bouweandela are organizing a one day ESMValTool tutorial next week for the EUCP project.
• @bjoernbroetz Announced that he will be leaving the ESMValTool project, we will miss you @bjoernbroetz and hope to have 🍻 with you next time there is a workshop in Bavaria!
• @mwjury Joined the meeting and now he knows what we look like 🥳
• @valeriupredoi Released version 2.1 of the ESMValCore and ESMValTool 🎉
• @nielsdrost Announced that we now have a bot for testing pull requests containing recipes and diagnostics, see here for an example: Add mapplot diagnostic to ClimWIP #1864 (comment). We're still testing the bot, so requesting a run of a recipe is restricted to just a few people, but once we have more confidence that it works we plan to make requesting a run available for all members of the @ESMValGroup/esmvaltool-developmentteam.

The list of updates above has been compiled from memory, so please forgive me if I forgot anything and feel free to add it yourself.

[rswamina]

As per @bouweandela 's request I mention here the issue I had with processing pi-control runs for ocean data variables. This is documented (initial problem, what is currently being done with iris and some possible workarounds ) in (ESMValGroup/ESMValCore#775) if anyone wants to know more.