The next monthly ESMValTool meeting will be in June. The result of the poll is that it will be on
Wednesday June 3 at 12:00 CET (11:00 BST).
The duration will be one hour. Join the zoom meeting here.
@ESMValGroup/esmvaltool-developmentteam
Format and agenda
Notes from the previous meeting can be found here: https://github.com/ESMValGroup/ESMValTool/issues/1609#issuecomment-624658525
Topics for discussion proposed in this issue:
I would like to propose to put the release schedule of v2.0 on the agenda. It would be helpful to decide on things that are critical yet still missing and thus blocking release of v2.0 as well as to collect other items that could also go into a later release, e.g. v2.0.1.
As an input to the discussion on the final release, I went through all the issues and sort them in two projects: v2.0 release and v2.1 release.
Same is done for ESMValCore: v2.0 and v2.1.
It would be good if someone could do the same for ESMValCore.
@ESMValGroup/esmvaltool-coreteam
@ESMValGroup/esmvaltool-developmentteam The meeting will take place on Wednesday June 3 at 12:00 CET (11:00 BST).
I would also like to make a decision on #1653 in the meeting.
We should also make a decision on #496.
we should defo talk about releasing 2.0 soon :bullettrain_side:
We should also make a decision on #496.
Happy to provide input to that discussion if it would be useful
We should also make a decision on #496.
Happy to provide input to that discussion if it would be useful
Thanks @duncanwp. @jgriesfeller you might like to join the call too!
Please can someone give me the meeting password (by mail if you don't want to post it here)?
Just a minute, I'll try to figure out what it is, apparently zoom added passwords to all meetings recently
The password is 8iyQMx
Topic: Station data
Time: Jun 3, 2020 01:00 PM Amsterdam
Join Zoom Meeting
https://us02web.zoom.us/j/82443796765?pwd=b3QrT3EwS0FQRERzNUdRTkFZblpWQT09
Meeting ID: 824 4379 6765
Password: 7mhyp2
Topic: Tutorial
Time: Jun 3, 2020 01:00 PM Amsterdam
Join Zoom Meeting
https://us02web.zoom.us/j/84127203139?pwd=TWx5dkJnRTJCaldTYkhodENwdDdEUT09
Meeting ID: 841 2720 3139
Password: 2CQN1e
These are the relavent CF Conventions: http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#appendix-examples-discrete-geometries
"The host has another meeting in progress" :-(
Solved that by making @SarahAlidoost the host for the Tutorial meeting, you should now be able to join one of both meetings.
Solved that by making @SarahAlidoost the host for the Tutorial meeting, you should now be able to join one of both meetings.
Still does not work for me.
@nielsdrost Reported he was able to join after installing the zoom application.
it's not gonna install itself, is it now :rofl:
Thanks for attending everyone!
Here is a short summary
We would like to release v2 soon. @bouweandela will make a doodle to set up a meeting with @ESMValGroup/esmvaltool-coreteam. Before the meeting, please apply the appropriate milestone to issues you think you can complete before the due date https://github.com/ESMValGroup/ESMValCore/milestone/3 and https://github.com/ESMValGroup/ESMValTool/milestone/3. A tentative due date proposed by @mattiarighi is July 15, 2020, but this is open for discussion of course. Missing the deadline shouldn't be a problem if we make releases regularly. The projects https://github.com/ESMValGroup/ESMValTool/projects/4 and https://github.com/ESMValGroup/ESMValCore/projects/2 created by @mattiarighi could probably be a good starting point for selecting issues (though covering everything there seems a bit optimistic).
We will leave the issue about squash merges #1653 open for another week and if no-one objects within that time, we will start using them.
The way forward with the station data (#496, #1655) will be to try using CIS tools to build a CMORizer script, possibly starting from pull request #1656. CIS tools allows reading the data into a form that follows the CF conventions, so some additional renaming of variables/coordinates/units will probably be needed to get it CMOR/CMIP6 data request compliant. CIS tools also has a feature for collocating station data with model data, this could possibly be implemented as a preprocessor function once the data is available in a CMORized form.
@ledm @SarahAlidoost and @Peter9192 made good progress on planning the tutorial
yeah cheers for organizing and leading these calls @bouweandela - they are pretty useful indeed! :beer:
@bouweandela says I should indicate my availability here so here goes: available for all sorts of things including work on ESMValTool, marriage (with reservations), talking about Formula 1 and history over Zoom beers, and not available for other things including travelling outside Reading, talking to people that don't trust science, and socializing with an angry cat. Is this good enough? :grin:
@bouweandela says I should indicate my availability here so here goes: available for all sorts of things including work on ESMValTool, marriage (with reservations), talking about Formula 1 and history over Zoom beers, and not available for other things including travelling outside Reading, talking to people that don't trust science, and socializing with an angry cat. Is this good enough?
Yes! Also consider filling in the Doodle for this month's meeting here: https://github.com/ESMValGroup/ESMValTool/issues/1670
I did :beer:
Most helpful comment
Thanks for attending everyone!
Here is a short summary
We would like to release v2 soon. @bouweandela will make a doodle to set up a meeting with @ESMValGroup/esmvaltool-coreteam. Before the meeting, please apply the appropriate milestone to issues you think you can complete before the due date https://github.com/ESMValGroup/ESMValCore/milestone/3 and https://github.com/ESMValGroup/ESMValTool/milestone/3. A tentative due date proposed by @mattiarighi is July 15, 2020, but this is open for discussion of course. Missing the deadline shouldn't be a problem if we make releases regularly. The projects https://github.com/ESMValGroup/ESMValTool/projects/4 and https://github.com/ESMValGroup/ESMValCore/projects/2 created by @mattiarighi could probably be a good starting point for selecting issues (though covering everything there seems a bit optimistic).
We will leave the issue about squash merges #1653 open for another week and if no-one objects within that time, we will start using them.
The way forward with the station data (#496, #1655) will be to try using CIS tools to build a CMORizer script, possibly starting from pull request #1656. CIS tools allows reading the data into a form that follows the CF conventions, so some additional renaming of variables/coordinates/units will probably be needed to get it CMOR/CMIP6 data request compliant. CIS tools also has a feature for collocating station data with model data, this could possibly be implemented as a preprocessor function once the data is available in a CMORized form.
@ledm @SarahAlidoost and @Peter9192 made good progress on planning the tutorial