cesm2.2-asdbranch_slh (Rafa Fernandez) #267
Conversation
Update documentation for CESM2.2.0. Juggled around CESM vs CESM2. The approach I took was if it applied to both CESM and CESM2, I left it as CESM. For example the section on inputdata, and version naming. If something applied to only CESM2, I changed CESM to CESM2. An example of this is the download instructions and different components. In the download instructions, I needed to update the manage_externals -S output to reflect the changes of the option components. Then included a note that this is the default and CESM2 will still run.
Document compset first letter convention Equivalent to ESCOMP#187 but for this release branch.
|
@RafaPedroFernandez @fvitt perhaps we should talk about this - Do you want this code in cesm2.2 (which is a dead branch of cesm) or do you want it in the latest development? |
Thanks Jim for your response. We'd like to implement SLH chemistry in CESM2.2. This is something we agreed with Doug Kinnison and Simone Tilmes. Note these SLH developments have only been previously used in CESM1. Note that most of the changes in *.F90 routines and configuration files were performed in the CAM repository ... but I was not able to do a pull request from my personal forked version (cam_cesm2_2_rel_09_slh). I'm not sure how to do it. Happy to talk about it with you and @fvitt at any time. |
|
It looks like @fvitt is out this week - do you want to get another CAM developer involved or wait until he returns next week? |
|
I prefer to wait until @fvitt is available as he has been our reference on many model implementations. Thanks !!! |
Description of changes
The new cesm2.2-asdbranch_slh branch contains development related to Short-Lived Halogen (SLH) chemistry in the Troposphere and Stratosphere.
Specific notes
This is my first time using git/github. Please let me know if there is something else I can do.
Contributors other than yourself, if any:
SLH Team in Madrid (PI Alfonso Saiz-Lopez); Doug Kinnison, Francis Vitt
Fixes: [Github issue #s] And brief description of each issue.
User interface changes?: [ No/Yes ]
[ If yes, describe what changed, and steps taken to ensure backward compatibility ]
Testing performed (automated tests and/or manual tests):