-
Notifications
You must be signed in to change notification settings - Fork 324
b4b-dev: Allow file paths with length 512 #3042
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
b4b-dev: Allow file paths with length 512 #3042
Conversation
…aramfile in the case directory" This reverts commit 0e6eed5.
d04e2dd
to
b5a043e
Compare
Awesome. Hopefully, this can happen without a hitch. I ran into problems last time I worked on this once we got to 256. But, tons have changed since then and I hope this will just work now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome. Thanks for working on this and bringing it in. I'm glad we can lengthen our filenames lengths and you got it to work without problems.
I also didn't realize we had a fname_len variable that we should've been using all along, and you made that change. I also like your rename of it to FL, similar to other shr_kind renames.
@ekluzek Unfortunately I run into this error in the
I can't figure out how to increase the maximum string length in the perl, so I'll need your help here. |
@samsrabin I pushed a change that should resolve the problem. The character lengths in the namelist_definition_ctsm.xml file for the filenames just needed to be updated. I didn't do anything beyond making the changes that I saw. So you'll need to test and validate, and make sure I didn't screw up syntax or miss something. |
Description of changes
Changes some input file paths to be of length
SHR_KIND_CX
(512) instead ofSHR_KIND_CL
(256). Also deletes some unuseduse
s ofSHR_KIND_CL
that were annoying during this work.Specific notes
Contributors other than yourself, if any: None
CTSM Issues Fixed:
Are answers expected to change (and if so in what way)? No
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? No
Testing performed, if any:
ERS_D_Ld20.5x5_amazon.I2000Clm50FatesRs.derecho_gnu.clm-FatesColdSeedDisp
passes (as of 404b3ca)aux_clm
passes (as of 1e488d8)