Meeting with Ouranos: Nov 2020

[agstephens]

Proposed agenda for meeting - 04/11/2020

1. Minutes and actions from previous meeting

Previous minutes: #59

Previous actions:

• AS: set up a monthly meeting in this Thursday slot.
• AS: to discuss code management procedures with the 34e team
• TJS: Add a Pull Request template for CLISOPS: Add a Pull Request template for CLISOPS clisops#70
• AS: liaise with team to get a new release published this month - in progress
• AS: discuss with 34e team how we add support for static typing: Add some static type support clisops#67 - in progress
• AS: put a "what we have learnt about dask" item on the next meeting agenda

2. Project update: c3s_34e [Ag]

3. Project updates: relevant Ouranos/CRIM projects [David/Tom?]

• of particular interest to 34e:
  • latest status of regridding work
  • latest status of NcML work

4. c3s_34e experience with Dask [Ag/Elle]

• what we have learnt about dask

5. Discussion:

• clisops plans and recent issues:
  • pending release
  • release procedure - can we converge
  • managing test datasets (for unit tests, in multiple repositories)
• xESMF and regridding issues
• other activities

6. Agree next steps and next meeting

[cehbrecht]

@fmigneault As mentioned in our meeting you wanted to try our rook WPS with weaver. Can you use the load-balanced url:

http://compute.mips.copernicus-climate.eu/wps?service=WPS&version=1.0.0&request=GetCapabilities

You can see the availability of the compute service in the GeoHealthCheck:
https://geohealthcheck.cloud.dkrz.de/resources?lang=en&tag=compute

There are example notebooks with http requests and rooki/birdy using the rook WPS:
https://nbviewer.jupyter.org/github/roocs/rooki/tree/master/notebooks/demo/

Currently the demo service is using a very limit set of demo data:
https://github.com/roocs/mini-esgf-data

[fmigneault]

@cehbrecht
I did not test the execution of processes yet, but deployment of the provider worked:
https://ogc-ades.crim.ca/ADES/providers/copernicus-rook

All path under this are as per OGC-API Processes
eg: REST "GetCapabilities" is https://ogc-ades.crim.ca/ADES/providers/copernicus-rook/processes and so on

The displayed information are dynamic, in the sense that
https://ogc-ades.crim.ca/ADES/providers/copernicus-rook/processes/subset
will call the corresponding "DescribeProcess" request on the rook WPS and generate the fields on the fly by converting the response to REST OGC API - Processes format.

[agstephens]

@fmigneault the JSON outputs are looking so much easier to read compared to old WPS XML docs. Nice! Thanks