Copertina

Salvato in:
Dettagli Bibliografici
Autori principali: Doutriaux, Charles, Taylor, Karl E., Mauzey, Chris, Nadeau, Denis, Durack, Paul J.
Natura: Recurso digital
Lingua:
Pubblicazione: Zenodo 2025
Accesso online:https://doi.org/10.5281/zenodo.16760850
Tags: Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
_version_ 1866902337498382336
author Doutriaux, Charles
Taylor, Karl E.
Mauzey, Chris
Nadeau, Denis
Durack, Paul J.
author_facet Doutriaux, Charles
Taylor, Karl E.
Mauzey, Chris
Nadeau, Denis
Durack, Paul J.
contents <p>Update CMOR3 with CF CRS container variable; Numerous edge case fixes, license reformulation for CMIP7</p> <p>Features</p> <ul> <li>Added the function <code>cmor_set_crs</code> used for creating a CF Coordinate Reference System (CRS) container variable. This is similar to the container variable created by <code>cmor_set_grid_mapping</code> but is named <code>crs</code> instead of the grid mapping name and supports text value attributes.</li> <li>The <code>license</code> attribute can now be generated from a template in the CV file. It requires the user to provide a <code>license_id</code> in their input JSON, which determines what license type and URL will be used when generating the license string. The attributes <code>license_id</code>, <code>license_type</code>, and <code>license_url</code> are not included in the global attributes of a file unless they are listed in the CV's <code>required_global_attributes</code> list.</li> </ul> <p>Bugfixes</p> <ul> <li>Removed erroneous warning message that says zero time steps were written for a time axis if <code>cmor_write</code> was used to write all time steps without setting the ntimes_passed parameter.</li> <li>Invalid JSON in user input or tables will be caught and throw an error instead of silently causing segmentation faults.</li> <li>The minimum supported CMOR version in the header of tables will now be compared as separate major and minor integers against the current CMOR version instead of as a float.</li> </ul> <p>Changes</p> <ul> <li>Time axis intervals will now be checked when passing time values with <code>cmor_write</code>.</li> <li>To use zstandard compression, the user must disable deflation with <code>cmor_set_deflate</code> and then provide a valid zstandard compression level within the range [-131072, 22] using <code>cmor_set_zstandard</code>. Performing only one of the two actions will result in no zstandard compression being applied.</li> <li><code>cmor_write</code> will throw an error if variable or zfactor data contains NaN values.</li> <li>Calendars in the <a href="http://cfconventions.org/Data/cf-conventions/cf-conventions-1.12/cf-conventions.html#calendar">CF 1.12 release</a> that are not supported by CMOR (i.e <code>utc</code>, <code>tai</code>, <code>all_leap</code>, and <code>366_day</code>) will throw an error message asking users to use another, more common calendar.</li> <li><code>cmor_time_varying_grid_coordinate</code> has been deprecated, and will be removed in a future release.</li> </ul> <p>Closed Issues</p> <ul> <li><a href="https://github.com/PCMDI/cmor/issues/697">warning on timesteps written (#697)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/774">Adding/augmenting functions to write a CF Coordinate Reference System (CRS) "container variable" (#774)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/791">Time interval not checked when adding time steps with cmor_write (#791)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/795">CMOR 3.10 issue with CV structure (#795)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/798">Correct unexpected behavior of cmor.set_deflate(0,0,0) (#798)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/802">Correct unexpected behavior of cmor.variable accepting missing_value argument that doesn't match the data array provided (#802)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/803">Correct segfault due to poorly defined <em>project</em>_CV.json file (#803)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/811">Update license_id entry - CMOR 3.10 changes break test (#811)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/813">Update calendar support to match full CF 1.12 list (#813)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/814">Test that use <code>cmor_time_varying_grid_coordinate</code> incorrectly use it with <code>cmor_write</code> (#814)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/816">license_id warning truncation bug; and license CV behavior tweaks (#816)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/818">Catch poorly formatted table and user_input .json files - generate error pointing to errored file (#818)</a></li> </ul> <p><a href="https://github.com/PCMDI/cmor/releases/tag/3.11.0">GitHub</a></p>
format Recurso digital
id zenodo_https___doi_org_10_5281_zenodo_16760850
institution Zenodo
language
publishDate 2025
publisher Zenodo
record_format zenodo
spellingShingle CMOR v3.0 Users Guide (Climate Model Output Rewriter; CMOR3)
Doutriaux, Charles
Taylor, Karl E.
Mauzey, Chris
Nadeau, Denis
Durack, Paul J.
<p>Update CMOR3 with CF CRS container variable; Numerous edge case fixes, license reformulation for CMIP7</p> <p>Features</p> <ul> <li>Added the function <code>cmor_set_crs</code> used for creating a CF Coordinate Reference System (CRS) container variable. This is similar to the container variable created by <code>cmor_set_grid_mapping</code> but is named <code>crs</code> instead of the grid mapping name and supports text value attributes.</li> <li>The <code>license</code> attribute can now be generated from a template in the CV file. It requires the user to provide a <code>license_id</code> in their input JSON, which determines what license type and URL will be used when generating the license string. The attributes <code>license_id</code>, <code>license_type</code>, and <code>license_url</code> are not included in the global attributes of a file unless they are listed in the CV's <code>required_global_attributes</code> list.</li> </ul> <p>Bugfixes</p> <ul> <li>Removed erroneous warning message that says zero time steps were written for a time axis if <code>cmor_write</code> was used to write all time steps without setting the ntimes_passed parameter.</li> <li>Invalid JSON in user input or tables will be caught and throw an error instead of silently causing segmentation faults.</li> <li>The minimum supported CMOR version in the header of tables will now be compared as separate major and minor integers against the current CMOR version instead of as a float.</li> </ul> <p>Changes</p> <ul> <li>Time axis intervals will now be checked when passing time values with <code>cmor_write</code>.</li> <li>To use zstandard compression, the user must disable deflation with <code>cmor_set_deflate</code> and then provide a valid zstandard compression level within the range [-131072, 22] using <code>cmor_set_zstandard</code>. Performing only one of the two actions will result in no zstandard compression being applied.</li> <li><code>cmor_write</code> will throw an error if variable or zfactor data contains NaN values.</li> <li>Calendars in the <a href="http://cfconventions.org/Data/cf-conventions/cf-conventions-1.12/cf-conventions.html#calendar">CF 1.12 release</a> that are not supported by CMOR (i.e <code>utc</code>, <code>tai</code>, <code>all_leap</code>, and <code>366_day</code>) will throw an error message asking users to use another, more common calendar.</li> <li><code>cmor_time_varying_grid_coordinate</code> has been deprecated, and will be removed in a future release.</li> </ul> <p>Closed Issues</p> <ul> <li><a href="https://github.com/PCMDI/cmor/issues/697">warning on timesteps written (#697)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/774">Adding/augmenting functions to write a CF Coordinate Reference System (CRS) "container variable" (#774)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/791">Time interval not checked when adding time steps with cmor_write (#791)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/795">CMOR 3.10 issue with CV structure (#795)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/798">Correct unexpected behavior of cmor.set_deflate(0,0,0) (#798)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/802">Correct unexpected behavior of cmor.variable accepting missing_value argument that doesn't match the data array provided (#802)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/803">Correct segfault due to poorly defined <em>project</em>_CV.json file (#803)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/811">Update license_id entry - CMOR 3.10 changes break test (#811)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/813">Update calendar support to match full CF 1.12 list (#813)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/814">Test that use <code>cmor_time_varying_grid_coordinate</code> incorrectly use it with <code>cmor_write</code> (#814)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/816">license_id warning truncation bug; and license CV behavior tweaks (#816)</a></li> <li><a href="https://github.com/PCMDI/cmor/issues/818">Catch poorly formatted table and user_input .json files - generate error pointing to errored file (#818)</a></li> </ul> <p><a href="https://github.com/PCMDI/cmor/releases/tag/3.11.0">GitHub</a></p>
title CMOR v3.0 Users Guide (Climate Model Output Rewriter; CMOR3)
url https://doi.org/10.5281/zenodo.16760850

Documenti analoghi