Skip to content
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 fix file staging and versioning. #581

Open
christinaholtNOAA opened this issue Feb 6, 2023 · 3 comments
Open

Handle fix file staging and versioning. #581

christinaholtNOAA opened this issue Feb 6, 2023 · 3 comments
Assignees

Comments

@christinaholtNOAA
Copy link
Collaborator

christinaholtNOAA commented Feb 6, 2023

The RRFS_dev1 solution to stage the appropriate version of fix files relies on commit hooks and staging files on disk and/or HPSS. We need a solution for how to ensure fix files are appropriately staged that is machine independent and a standard practice.

The preferred method is to store them in a globally accessible, centralized location. Versioning should follow a standard versioning control method that can handle large files -- svn or git with LFS. The files should be staged on supported platforms from the central location, for ease of use. SRW should know where to get them and where to put them for an experiment.

The fix files required for RRFS involve the pre-generated grid files for supported grids, the GSI fix files, and the global FV3 fix files.

@christinaholtNOAA christinaholtNOAA converted this from a draft issue Feb 6, 2023
@christinaholtNOAA
Copy link
Collaborator Author

Eddy has been handling this -- there's a document for status and what's moved. Should be good for Jet/Hera. Still need to add a PR for the Bay Area grid.

@christinaholtNOAA
Copy link
Collaborator Author

This is ongoing work for the duration RRFS merge project. There's nothing to be addressed currently.

@gspetro-NOAA
Copy link
Collaborator

@christinaholtNOAA Is this something your team is working on, or is this something EPIC should be handling?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants