-
Notifications
You must be signed in to change notification settings - Fork 13
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
Merge drv_flds_in in driver from different components #324
Comments
Here's what I have to fix this... [yongi:~/cime/scripts/Tools] erik% git diff preview_namelists +my
foreach my $model (@modelsorder) { |
Erik, If you are going to provide the fix wouldn't it be better to open a pull On Thu, Dec 3, 2015 at 11:31 AM, Erik Kluzek [email protected]
Jim Edwards CESM Software Engineer |
This merge updates the ACME template files to put the batch directives in the proper location for other batch systems that haven't been added to the ACME machines yet (such as moab). Test suite: Test baseline: Test namelist changes: Test status: [bit for bit, roundoff, climate changing] User interface changes?: Code review: douglasjacobsen * wilke/template/directives: moved batchdirectives to top of the template
This corresponds to the following bug in CLM:
http://bugs.cgd.ucar.edu/show_bug.cgi?id=2252
In order to make the system robust in dealing with drv_flds_in (which can be created by CAM or CLM) drv_flds_in needs to be deleted from the RUN directory if it exists before the calls to the component buildnml. As it works now, CLM leaves the previous version of the file in place and doesn't replace it even if user_nl_clm was changed appropriately. But, we can't have CLM clobber the file, in case CAM was the one that created it -- in that case we want CAM to override what CLM does.
There's also talk about converting the handling of drv_flds_in so that components only append to the end of it. But, in that paradigm deleting the file before components add to it makes the most sense, rather than leaving the previous incarnation of the file around. So this change works in both cases.
The text was updated successfully, but these errors were encountered: