-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle IPSL-CM6 #1153
Handle IPSL-CM6 #1153
Conversation
* First attempte * Do not require start and end years, add them later * Correct condition * Avoid key error in fx variables * Consider two possible paths * Fix function name * Fix variable name * Avoid duplicates in filename * Add test for startdate expansion * Add test for the replace tags method * Rename tag * Add documentation * Allow to load subexps per timerange or as a whole * Fix condition * Remove 'all_years' functionality * Fix conditions * Fix flake * Remove whitespace Co-authored-by: Javier Vegas-Regidor <javier.vegas@bsc.es>
…grid (#507) Co-authored-by: Bouwe Andela <b.andela@esciencecenter.nl> Co-authored-by: Stef Smeets <s.smeets@esciencecenter.nl>
* sos and siconc fixed * tests added * test fixed * fix flake8 * fix flake8 * fix codacy issue
* pin cf-units * pin cf-units * fix test * fix test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question: how can I access to a data sample so I can properly test it?
An example of multi-variable file for IPSL-CM6 is available here (on my Google Drive) |
@alistairsellar : you may wish to know that this PR exists |
Quick side note on the slow loading: I am just talking to some iris developers and it seems they are hitting the exact same problem, also while dealing with an XIOS generated multi-variable output file for the next model generation. There doesn't seem to be an issue about it yet, but I forwarded your example file and will try to add the issue here when it becomes available. |
I reported the problem quite early as an Iris Issue, and provided the file plus a notebook showing the problem by profiling an Iris run, and provided a follow up in my original issue on this subject, which basically says that even with a recent fix in Iris V3.0.2, the load is still slow (figures availabe on demand). Do you mean that the Iris developers have some new idea here ? |
Following discussion with @abooton @zklaus , we've been looking into another possible Iris improvement : to avoid translating data-variables which are not wanted in a load. I rather struggled to understand exactly what you need to load here, but I'm assuming may be just a single data-variable, |
Commit #896764b bring this PR in line with PR #1124 at commit 50afc8b. I may complement this PR at short notice if needed, including switching to the option of supporting IPSL-CM6 through a dedicated project. I will fix codacy tests diags after the merge of #1124 in main, because a number of them are due to the anticipation on fix.extra_facets existence |
That would be good, otherwise you will not be able to use the IPSL model data at the same time as any of the other data supported by the native6 project. |
For now, I just reduced the number of changes by reverting to the previous formatting in unrelated sections. As you can see from the diff, this is much easier to digest. Note that I don't claim that this formatting is better in any way. It just makes it easier to distinguish substantive changes, that we need to proofread, from the rest. The main things for this were:
I will now do a proper review of the documentation changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, finished the doc review. Only minor comments.
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
Co-authored-by: Klaus Zimmermann <klaus.zimmermann@smhi.se>
I made a small improvement to the formatting. I also have one more question: The atmospheric variables are now separated according to CMIP vs IPSL names. Does this not apply to the other realms? Also, there are a number of very long |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine
…Core into Handle_IPSL_CM6
The review comments were addressed and we @bouweandela and I discussed offline how to move forward.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I have moved the discussion on Iris loading times and CDO to the new issue #1180. Let's continue there. |
By the way : thanks a lot for the support on this PR and the related issue ; nice to have that yet in V3.2 |
Description
Related to issue #1143. Allow to handle IPSL-CM6 data formats and file naming conventions.
Composed of :
The feature won't actually work without #1124 , but the proposed PR is compatible with the main branch before #1124 merge, in order to allow for immediate merge, and so to avoid bottlenecks. #1124 allows for finding the right file and the right variable in file when using ISPL-CM6 data.
Some documentation on the handling of native models has been introduced.
Performance in loading variables from IPSL's multi-variable datafiles with Iris is poor, even with the Iris 3.0.2 fix on that subject. This is why pre-selecting using CDO in a fix_data method is implemented. However, because CDO licence (GPL v2) is not compatible with ESMValTool licence policy, this feature is not activated by default, and no explicit dependency is introduced. The feature can be activated through a variable mappings file (see #1124), at those sites which accept to be dependent on CDO.
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.