You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Theses were specifically for tidying up data for the WMO decadal forecasting centre and would need adapting for more general use, but it is a good way of providing an example.
Piotr hasn’t touched ocean variables in this form, so we still need to dig out the function call list for the 2D lat-lon variable production you asked about earlier in the week.
Adding something like this to the CMOR documentation or repo might be a nice way of making it a lot easier for people. If an appropriate set of notebooks could be constructed for Input4MIPs and Obs4MIPs then there might be less leaning on specific individuals for technical work/support.
M
2/8/24
Thanks M, this is excellent – just looping in C, KT and PG.
The NEMO ocean I, j mapping would be really useful if that could be found, we are hoping to find a python template that we can use to write some non-lat/lon data, and the MOHC NEMO example looks like the kind of output we wanted to target.
Thanks again for this!
P
2/8/24
FYI: P has been working on a 2D lat lon equivalent (i.e. CMIP6 Omon/tos) and will share when completed.
I would strongly recommend adapting these to act as demonstrations of how you can use CMOR in an adhoc fashion, and I think this route might well be simple enough that you could point obs4MIPs and input4MIPs contributors at them as a relatively simple DIY light weight CMORizer.
Matt
12/19/24
Hi all,
We are just checking in to see if there might be any progress with this. We don’t require anything polished – we can do that – just a clear-cut example of the few critical lines of CMOR code so that we can be confident it providing documentation for obs4MIPs data providers.
Many thanks,
PG
The text was updated successfully, but these errors were encountered:
I've transferred some emails here and hope further discussion will follow here.
2/2/24
Hi PD, cc: P
I mentioned CMORising notebooks earlier. Piotr has thrown them into gists;
https://gist.github.com/piotr-florek-mohc/071256205f9e5f055f8b523a52694a01
https://gist.github.com/piotr-florek-mohc/02b40a8b9683814027d349bff4dd5bd5
https://gist.github.com/piotr-florek-mohc/92dbc05da9722497562ec740346b76fc
https://gist.github.com/piotr-florek-mohc/896c1a67cdb437d0f9447bfd8f582a74
(one of the above is a code library).
Theses were specifically for tidying up data for the WMO decadal forecasting centre and would need adapting for more general use, but it is a good way of providing an example.
Piotr hasn’t touched ocean variables in this form, so we still need to dig out the function call list for the 2D lat-lon variable production you asked about earlier in the week.
Adding something like this to the CMOR documentation or repo might be a nice way of making it a lot easier for people. If an appropriate set of notebooks could be constructed for Input4MIPs and Obs4MIPs then there might be less leaning on specific individuals for technical work/support.
M
2/8/24
Thanks M, this is excellent – just looping in C, KT and PG.
The NEMO ocean I, j mapping would be really useful if that could be found, we are hoping to find a python template that we can use to write some non-lat/lon data, and the MOHC NEMO example looks like the kind of output we wanted to target.
Thanks again for this!
P
2/8/24
FYI: P has been working on a 2D lat lon equivalent (i.e. CMIP6 Omon/tos) and will share when completed.
I would strongly recommend adapting these to act as demonstrations of how you can use CMOR in an adhoc fashion, and I think this route might well be simple enough that you could point obs4MIPs and input4MIPs contributors at them as a relatively simple DIY light weight CMORizer.
Matt
12/19/24
Hi all,
We are just checking in to see if there might be any progress with this. We don’t require anything polished – we can do that – just a clear-cut example of the few critical lines of CMOR code so that we can be confident it providing documentation for obs4MIPs data providers.
Many thanks,
PG
The text was updated successfully, but these errors were encountered: