-
Notifications
You must be signed in to change notification settings - Fork 0
May2019Minutes
Cable Minutes - May 2019 - and this link to corresponding Minutes
1. Report on actionable from the previous meeting.
Issue with Tickets to progress and uncertainty whether they are ready or not. Should they be formally "submitted"?
We discussed the Tickets at hand and how to proceed. See further comment in 2. It was decided that we should note a list of accepted tickets to help Jhan at the end of the meetings
2. Ian Harman suggested further discussion by the committee of soil ancillaries as used both on/offline. Their origin, appropriateness, documentation.
User guide requires significant revision - concerns that it took quite a lot of detective work to determine where parameters originated from.
Especially discussed was around file input/ancillaries used.
Add citations to User Guide (to the 5.1 section) - Martin De Kauwe to look at this
Extensive discussion about what underlies the current LAI used in the gridinfo file. Ian Harman said they had updated this for CMIP6, he was going to look into whether they are actually using collection 6 MODIS. If so, is there a reason this isn't in the offline file?
Ticketing system and development guidelines need to be reviewed and documented. - Jhan
Tagged versions need to be documented - Jhan
DONE
3. Andy Pitman suggested regular report to the committee and subsequent discussion regarding the progress of JaC.
* Jhan to update
* Danny to update
Limited update: There have been no further submissions to the JULES trunk.
The next step is to upload CABLE completely (physics only) to the JULES repository.
There was also a discussion around licencing.
3. Gab to update on benchmarking progress.
Benchmarking is working - Gab gave a demonstration, but there is a systems issue when multiple files are uploaded to an experiment. Danny is working on this.
4. Review the registration process
Streamline to one step process.
Rachel is going to investigate privacy issues surrounding the collection and use of personal data.
Currently, the registration process is:
-
email cable_help with the completed registration form attached.
-
request access to CABLE software group from NCI
-
request NCI access if required
This is not overly complicated. However, in many cases, "applicants" assume that an email is all that is required. Downloading a document, "annotating" it, and attaching it seems overly cumbersome considering the only real data we need/collect is a name, email, institution and NCI ID.
Ian highlighted that at some point it might be requested of us what users are using CABLE for, which is requested on the form, however rarely completed.
Jhan suggested that perhaps registration should amount to supplying name, email, institution and NCI ID in the email to cable_help and that's it.
5. Discuss indentation, follow up from the previous meeting.
Ticket #215 has modified indentation. We need to have a follow-up discussion with Danny as he checked what the Met Office tool did...
6. Should we send committee invitation /agenda email to User list?
Yes and make note that users can add to the agenda and/or attend the meeting.
7. Any other business?
Martin proposed science meeting for 2019 - 2nd half of the year
ACCESS Science meeting 24th May add to CABLE newsletter
Add a link to newsletter archive from CABLE communication - Jhan DONE
Ticket #214 and #215 have been pushed to the trunk.
Otherwise Tickets from Previous meeting have not yet been processed.