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
{{ message }}
Repository navigation
Logistical improvements to fsurdat/landuse files #2337
changed the title [-]Add version number to fsurdat/landuse files[/-][+]Add version number to fsurdat/landuse files and other logistical improvements[/+]on Mar 14, 2024
In addition to including version metadata to fsurdat/landuse files, we want to add useful content to the landuse.timeseries variable input_pftdata_filename.
Also it seems potentially helpful to write a separate landuse...log file, distinct from the surfdata...log.
I'm grouping these logistical needs together under this post 5.2 issue for now, and we can separate if necessary when we work on them.
We are adding the version to ctsm5.3.0 datasets, but we won't fix input_pftdata_filename until later. So that won't be in the ctsm5.3 datasets, but will be good to get in the code so that they will be correct in future datasets (such as ctsm6.1.)
changed the title [-]Add version number to fsurdat/landuse files and other logistical improvements[/-][+]Logistical improvements to fsurdat/landuse files[/+]on Sep 3, 2025
Activity
[-]Add version number to fsurdat/landuse files[/-][+]Add version number to fsurdat/landuse files and other logistical improvements[/+]slevis-lmwg commentedon Mar 14, 2024
In addition to including version metadata to fsurdat/landuse files, we want to add useful content to the landuse.timeseries variable
input_pftdata_filename.Also it seems potentially helpful to write a separate landuse...log file, distinct from the surfdata...log.
I'm grouping these logistical needs together under this post 5.2 issue for now, and we can separate if necessary when we work on them.
ekluzek commentedon Sep 9, 2024
We are adding the version to ctsm5.3.0 datasets, but we won't fix input_pftdata_filename until later. So that won't be in the ctsm5.3 datasets, but will be good to get in the code so that they will be correct in future datasets (such as ctsm6.1.)
ekluzek commentedon Jun 24, 2025
Since, this is the last round of datasets going into the cesm3.0 release I think this is important to have in ctsm5.4.
[-]Add version number to fsurdat/landuse files and other logistical improvements[/-][+]Logistical improvements to fsurdat/landuse files[/+]