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
While attempting to use UpdateParamAPI.py for the API37.1 updates, I found that the order of the cdl file was getting changed. The tool appears to run correctly based on the command line output, but diffing the output shows that the default parameter file has the variable order changed.
I ended up cloning another version of fates in a separate directory, checking out sci.1.80.4_api.37.0.0, which just prior to the last tooling update. I had to do some slight path modifications to the tooling in that repo, but calling the older tag tooling from the original fates directory resulted in the correct ordering.
On a related note, I think troubleshooting this issue would have been slightly improved by making the tooling directory it's own repo and adding it as a submodule to the fates repo. This would have allowed me to checkout older versions of the tools within the existing directory structure.
Describe the issue
While attempting to use UpdateParamAPI.py for the API37.1 updates, I found that the order of the cdl file was getting changed. The tool appears to run correctly based on the command line output, but
diff
ing the output shows that the default parameter file has the variable order changed.I ended up cloning another version of fates in a separate directory, checking out sci.1.80.4_api.37.0.0, which just prior to the last tooling update. I had to do some slight path modifications to the tooling in that repo, but calling the older tag tooling from the original fates directory resulted in the correct ordering.
Relevant log output
FATES tag
sci.1.80.14_api.37.0.0
Host land model tag
ctsm5.3.024
Machine
other HLM supported machine
Other supported machine name
lobata
The text was updated successfully, but these errors were encountered: