-
Notifications
You must be signed in to change notification settings - Fork 397
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
Feature/update cesm driver namelist defaults #800
Feature/update cesm driver namelist defaults #800
Conversation
dgergel
commented
May 24, 2018
•
edited
Loading
edited
- closes default namelist settings for CESM driver need to be updated #799
- tests passed
- new tests added
- science test figures
- ran uncrustify prior to final commit
- ReleaseNotes entry
…odes, default output variables and default output filename
docs/Development/ReleaseNotes.md
Outdated
@@ -54,55 +54,59 @@ This is a minor update from VIC 5.0.1. The VIC 5.1.0 includes new features, such | |||
- Fixed bug that prevented using the correct local domain grid cells in `cesm_put_data.c` | |||
- Changed reference temperature units from Celsius to Kelvin in `cesm_put_data.c` | |||
|
|||
1. [GH#695](https://github.com/UW-Hydro/VIC/pull/695) | |||
2. [GH#695](https://github.com/UW-Hydro/VIC/pull/695) |
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.
markdown automatically numbers this so the 1. was intentional here.
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.
As @jhamman says. Leave the 1
for all the numbered entries. The 1
just indicates that markdown should format this as an enumerated list and will take care of the actual numbering. It is much easier to leave that to markdown in case the list ever gets updated.
@@ -91,7 +91,8 @@ def copy_to_rundir(grid_config, caseid, rundir, casedocs): | |||
|
|||
# copy file | |||
copy_clean_vic_config(grid_config[filekey], dst_file, | |||
header=header, rundir=rundir, **grid_config) | |||
header=header, rundir=rundir, | |||
caseid=caseid, **grid_config) |
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.
indentation error here.
OUT_FORMAT NETCDF4_CLASSIC | ||
OUTVAR OUT_PREC | ||
HISTFREQ END |
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.
for both of these streams, I think you probably want the HISTFREQ
frequency to be nmonths 1
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.
What would HISTFREQ END
do?
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.
Write one file with all history timesteps in it at the final timestep. This is probably not what you want.
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.
Updated as suggested
OUTVAR OUT_SURF_TEMP | ||
OUTVAR OUT_SWNET | ||
OUTVAR OUT_LWNET | ||
OUTVAR OUT_GRND_FLUX |
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.
suggest adding frozen soil variables. You and @bartnijssen should probably iterate together on which variables you think would be potentially useful.
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.
Having something that let's us identify active layer depth would be useful, but now sure whether that would be part of every run. Same for all these met variables. Can we split out the radiation variables (down and up rather than just net).
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.
That's what I was thinking too. From knowing how much outputting data for 10 thermal nodes increases the size of the output files, I think we should add that when we need it and not make it the default. I'll split out the radiation variables and remove some of the met ones
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.
Remember this is just a monthly output file so the cost of writing out 3d vars is much less than it would otherwise be. My thought is that you should write out more variables, unless you have reason to think the data volumes will be out of control or that it is negatively impacting runtimes.
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.
I added soil node temperature to the monthly output files as well as eliminating some of the met vars and splitting out the radiation vars. @bartnijssen and @jhamman - what do you think of the updated ones?
docs/Development/ReleaseNotes.md
Outdated
@@ -54,55 +54,59 @@ This is a minor update from VIC 5.0.1. The VIC 5.1.0 includes new features, such | |||
- Fixed bug that prevented using the correct local domain grid cells in `cesm_put_data.c` | |||
- Changed reference temperature units from Celsius to Kelvin in `cesm_put_data.c` | |||
|
|||
1. [GH#695](https://github.com/UW-Hydro/VIC/pull/695) | |||
2. [GH#695](https://github.com/UW-Hydro/VIC/pull/695) |
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.
As @jhamman says. Leave the 1
for all the numbered entries. The 1
just indicates that markdown should format this as an enumerated list and will take care of the actual numbering. It is much easier to leave that to markdown in case the list ever gets updated.
OUT_FORMAT NETCDF4_CLASSIC | ||
OUTVAR OUT_PREC | ||
HISTFREQ END |
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.
What would HISTFREQ END
do?
OUTVAR OUT_SURF_TEMP | ||
OUTVAR OUT_SWNET | ||
OUTVAR OUT_LWNET | ||
OUTVAR OUT_GRND_FLUX |
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.
Having something that let's us identify active layer depth would be useful, but now sure whether that would be part of every run. Same for all these met variables. Can we split out the radiation variables (down and up rather than just net).
…_cesm_driver_global_param_defaults
@bartnijssen @jhamman just noticed this didn't get merged before - can one of you go ahead and merge it? |
@@ -91,7 +91,8 @@ def copy_to_rundir(grid_config, caseid, rundir, casedocs): | |||
|
|||
# copy file | |||
copy_clean_vic_config(grid_config[filekey], dst_file, | |||
header=header, rundir=rundir, **grid_config) | |||
header=header, rundir=rundir, | |||
caseid=caseid, **grid_config) |
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.
can you fix the indentation of this line?
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.
Done.
@@ -91,7 +91,8 @@ def copy_to_rundir(grid_config, caseid, rundir, casedocs): | |||
|
|||
# copy file | |||
copy_clean_vic_config(grid_config[filekey], dst_file, | |||
header=header, rundir=rundir, **grid_config) | |||
header=header, rundir=rundir, | |||
caseid=caseid, **grid_config) |
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 still looks funny 😉
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.
Ugh it didn't look weird on my end; I think it's fine now