-
Notifications
You must be signed in to change notification settings - Fork 2
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
New FMT run with coupled tag #360
Comments
@PeterHjortLauritzen I am suggesting to also do a new FMT HIST run with the recent tuning to explore improvements in the tape recorder and GW, but use the new setting that are in the latest coupled run for the LT model. So, basically this run #347 with new tag and settings. |
@adamrher and @PeterHjortLauritzen: we decided to match "34" for that run (#361) as of yesterday it was our favorite run. Based on today's results, do we want to move to another run (maybe "37" ? i.e. #367 ) |
Or "33" as we have a FLTHIST for that one and we are planning to do a F1850. So many options... |
Following up the CAM7 discussion today, we decided that we will base this run on #353. This is the FLHIST equivalent of the coupled run "33" The run directory is at:
The difference between
|
I am also adding the variables requested by @tilmes in: #363 (comment) |
@JulioTBacmeister: incase this is useful, I am adding the list of gw parameters.
|
Dycore variables look correct! |
See: #374 |
Description of the run
To guide WACCM development I propose a new baseline with FMT using our latest coupled configuration. Details will be decided next week when @cecilehannay and @JulioTBacmeister are back. In particular, the QBO with the latest tag / configuration needs to be assessed. (the previous run used a different HB code #312)
Suffix in the casename
Suffix
Namelist modifications
Namelist
Source modifications
SourceMods
Sandbox
Requested sandbox or tag
Contact info
@PeterHjortLauritzen @cecilehannay @JulioTBacmeister @islasimpson
Any other relevant information
Enter relevant info
The text was updated successfully, but these errors were encountered: