Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Retaining or changing the LUH2 raw data file naming convention #1057

Closed
glemieux opened this issue Aug 1, 2023 · 0 comments
Closed

Retaining or changing the LUH2 raw data file naming convention #1057

glemieux opened this issue Aug 1, 2023 · 0 comments

Comments

@glemieux
Copy link
Contributor

glemieux commented Aug 1, 2023

@glemieux and I discussed the risk of using the same three file names (states, transitions, management) for all cases that are present in /glade/p/cesmdata/cseg/inputdata/lnd/clm2/rawdata/LUH2. The most likely risk that comes to mind is one where we copy or move files without keeping track of the contents. We looked in a few files for metadata that may help differentiate between files but did not find enough information.

@glemieux and I recommend renaming the files according to case/scenario/version/other identifying characteristics. Doing so requires modifications to the tool, but maybe just in these few lines?

I suggested that @glemieux move forward without changing the file names for now. When the tool gets added to Erik's mksurfdata_esmf makefile, we can determine whether changing the file names adds significant complication. We may also decide to keep the file names unchanged in order to maintain "purity" relative to the original source of the data on the LUH2 website.

Originally posted by @slevis-lmwg in #1032 (comment)

@NGEET NGEET locked and limited conversation to collaborators Aug 1, 2023
@glemieux glemieux converted this issue into discussion #1058 Aug 1, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant