-
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
b.cesm3_cam058_mom_e.B1850MOM.ne30_L32_t061.cam6_cice5.017 #145
Comments
Can you explain where
|
@JulioTBacmeister or @PeterHjortLauritzen: Which topo do you want to use in that run? Out of the box I am getting:
It seems a bit archaic. We decided we don't want to use the no-leaky topo in this run. But do we want to use a more recent version of the topo just before introducing the no-leaky topo. For instance:
|
@adamrher:
|
Thanks @justin-richling. It is great. |
ADF diags for 0017 (as of 7:00 MDT) vs: This case is finishing up shortly |
Sounds good, I'll take note! |
I am trying to determine the values we want to use for the 018. Basically, 018 = 017 + some tuning to make the cloud thicker and get RESTOM closer to balance. 017 is still short and it is hard to determine where RESTOM will end up. But it is clear it is too large. I think we are going to need to modify both gamma_coef and c_14.
@JulioTBacmeister and @adamrher: thoughts? |
@cecilehannay Are there any other differences between 11 and 12, besides clubb_gamma and clubb_c14? Both have the same CICE version? |
I think it's a good plan, if the only difference between 11 and 12 is those two clubb parameters. we could alternatively leave those alone, and switch off the trapezoidal rule. Or is that what the last simulation was --and it's too hard a kick to the cloud forcing? |
I thought about this but I was concerned it would get us too far. In 016 versus 014, the change in RESTOM from the ADF table is -2.2 W/m2, although I am not sure on which years the climos were computed in that table. (@justin-richling ?) I would rather have RESTOM a bit positive than a bit negative. It is why I am suggesting adjusting gamma_coef and c14. |
OK. I'm wondering if we should maybe leave gamma alone, and instead increase C8. If you recall all the way back Jiang Zhu's talk on the Eocene simulations in April (here), C8 is an alternative way to impact the skewness. clubb_gamma hits it really hard because it controls a PDF parameter - the width of the w' distribution. But C8 does it through a more natural way, in that it is the damping coefficient on the prognostic w'^3 equation. Increasing C8 will reduce skewness, which will increase cloud thickness. Vince seems more comfortable with this approach versus clubb gamma. Jiang increase C8=4.2->5.2. Maybe we should do a separate experiment ... run 17 but with C8=5.2? |
Trying out a couple of different clubb parameters sounds like a good idea
to me
…On Fri, Jul 29, 2022 at 4:32 PM Adam Herrington ***@***.***> wrote:
OK. I'm wondering if we should maybe leave gamma alone, and instead
increase C8. If you recall all the way back Jiang Zhu's talk on the Eocene
simulations in April (here
<https://drive.google.com/file/d/11bCewR7HdpQeLPlUGPY512CC314H_wEz/view>),
C8 is an alternative way to impact the w' field. clubb_gamma hits it really
hard because it controls a PDF parameter - the width of the w'
distribution. But C8 does it through a more natural way, in that it is the
damping coefficient on the prognostic w' equation. C8 controls the damping
on coefficeint in the w' equation, and so you can reduce the skewness by
cranking it up, which will increase cloud thickness.
Vince seems more comfortable with this approach versus clubb gamma. Jiang
increase C8=4.2->5.2. Maybe we should do a separate experiment ... run 17
plus C8=5.2?
—
Reply to this email directly, view it on GitHub
<#145 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGLMTQEVCZMQMNX4AMUT43VWRLWPANCNFSM543DUVAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I can set 018 with
and 019 with
Then we would look during the week end how the RESTOM look in these. |
sounds like a plan. And for 19, gamma/c14 are using their run 17 values. |
@cecilehannay It looks like for 014 the years were 0001-0014 and 016 were 0001-0040 |
Description:
Same as #144 but with the se_dycore
We are using the same clubb tuning parameters as in 016 (#144).
The dycore se parameters are set the same way as 009 (#136)
ncdata and topo are set to:
Case directory:
Locally (if still available):
/glade/p/cesmdata/cseg/runs/cesm2_0/b.cesm3_cam058_mom_e.B1850MOM.ne30_L32_t061.cam6_cice5.017
On github:
https://github.com/NCAR/amwg_dev/tree/b.cesm3_cam058_mom_e.B1850MOM.ne30_L32_t061.cam6_cice5.017
Sandbox:
Locally (if still available):
/glade/work/hannay/cesm_tags/cesm3_cam6_3_058_MOM_e
On github:
hash: 8f70c08
Diagnostics:
AMWG diags (if available)
https://webext.cgd.ucar.edu/B1850MOM/b.cesm3_cam058_mom_e.B1850MOM.ne30_L32_t061.cam6_cice5.017/atm/
Contacts:
@JulioTBacmeister, @cecilehannay
The text was updated successfully, but these errors were encountered: