Skip to content

Make st_archive archive CAM+DART output files #1301

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

Open
kdraeder opened this issue Apr 22, 2025 · 1 comment
Open

Make st_archive archive CAM+DART output files #1301

kdraeder opened this issue Apr 22, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@kdraeder
Copy link

kdraeder commented Apr 22, 2025

What is the feature/what would you like to discuss?

Doing data assimilation with CESM+DART generates many new types of output files,
which st-archive should archive, assuming they are named according to CESM conventions.
Many of the new files will be handled by the esp component code, but others are
more closely associated with the geophysical components and should be archived
with their files. We've chosen new file names in such a way that this can be done
with very small changes to
$component/cime_config/config_archive.xml
cime/CIME/XML/archive_base.py
A second small change is to make st-archive handle compressed files (*.gz).
This has no effect on model calculations or existing output.

The changes have been tested in cesm3.0_alphabranch and pushed to my github CAM fork,
except for the ChangeLog, which wants a PR # (or Issue # ).
I'll include more details in the PR, after someone tells me to proceed.
Or I can provide them here.

I don't seem to have permission to select features; Labels, Projects, ...

Is there anyone in particular you want to be part of this conversation?

No response

Will this change (regression test) answers?

No

Will you be implementing this enhancement yourself?

Yes

@kdraeder kdraeder added the enhancement New feature or request label Apr 22, 2025
@cacraigucar cacraigucar self-assigned this Apr 23, 2025
@cacraigucar
Copy link
Collaborator

@kdraeder - Feel free to open a PR to cam_development. We will then perform a review and can work on bringing it into CAM. If you feel comfortable giving me write permission to your fork, I can make the edits we'll need to make directly in your fork. Otherwise, I can open a separate PR which merges your branch into my fork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: To Do
Development

No branches or pull requests

2 participants