Monthly ESMValTool meeting - August 2020

[bouweandela]

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

Monday August 3 at 14:00 CEST (13:00 BST).

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

@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: #1670 (comment)

[bouweandela]

@ESMValGroup/esmvaltool-developmentteam The meeting will take place on Monday August 3 at 14:00 CEST (13:00 BST).

[bouweandela]

Thanks for attending everyone!

Here is a summary with some news:

• @katjaweigel Submitted the new paper on diagnostics for extreme events, regional and impact evaluation
• @SarahAlidoost Reported that there has been a lot of progress on the new tutorial (source repository) in tutorial sprints that many members of the @ESMValGroup/esmvaltool-developmentteam joined and that it is now ready to be used
• @sloosvel Mentioned that many new users are now up and running with ESMValTool at BSC and they plan to use the tutorial mentioned above when they give another course this autumn
• @nielsdrost Announced that we now have a machine at DKRZ for running automatic tests of recipes and diagnostics and hope to set it up for usage in the next month How to test diagnostic scripts #316
• @valeriupredoi mentioned he was making good progress on testing multiple OSs and Python versions with GitHub Actions Installation and testing of esmvalcore package ESMValCore#731
• @mattiarighi said that all recipes were tested successfully Final test for v2.0.0 release #1697 (apart from two which were fixed in the meeting recipe_ocean_example.yml and recipe_ocean_bgc.yml broken #1742)
• @bouweandela Mentioned that we will release v2.0.0 later today
• @bascrezee said it would be nice if releases would be announced to the wider community and that he hoped the new testing infrastructure would also be able to catch issues like Anomaly calculation for OBS got broken early march.  ESMValCore#710 before users run into them
• @bouweandela said that we will discuss the release strategy and schedule with the core development team in the first week of September and hope to publish the result on the website