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
As of cesm3_0_beta05, NCAR has updated their use of rpointer files to include timestamps in the filename.
This change allows for easier organization of rpointer file sets and for multiple rpointer sets in a single directory.
This change to CIME requires rpointer file handling changes in all other NorESM components.
In order to make it easier to coordinate with NCAR and incorporate changes, all components should make this change.
The list of components and utilities to update is below along with the relevant NCAR tag (where known).
This is needed to get the model up-to-date and be able to use the new .rpointer filename format. This will allow close coordination with the models in the ESCOMP, ESMCI, or NGEET upstream repositories.
The text was updated successfully, but these errors were encountered:
gold2718
changed the title
Update components to be able to handle new rpointers used in cesm beta tags.
Update all components to use rpointer files with timestamps
Feb 26, 2025
As of
cesm3_0_beta05
, NCAR has updated their use of rpointer files to include timestamps in the filename.This change allows for easier organization of rpointer file sets and for multiple rpointer sets in a single directory.
This change to CIME requires rpointer file handling changes in all other NorESM components.
In order to make it easier to coordinate with NCAR and incorporate changes, all components should make this change.
The list of components and utilities to update is below along with the relevant NCAR tag (where known).
==>
Readd rpointer timestamps ESCOMP/CDEPS#317Additional context
This is needed to get the model up-to-date and be able to use the new .rpointer filename format. This will allow close coordination with the models in the ESCOMP, ESMCI, or NGEET upstream repositories.
The text was updated successfully, but these errors were encountered: