Skip to content
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

Convective gustiness impacts added to ocean surface flux #540 #540

Closed
megandevlan opened this issue Mar 15, 2022 · 17 comments
Closed

Convective gustiness impacts added to ocean surface flux #540 #540

megandevlan opened this issue Mar 15, 2022 · 17 comments
Assignees

Comments

@megandevlan
Copy link

Related to CMEPS issue #267, we're exploring how to add the effects of convective gustiness into the calculation of surface fluxes over oceans. The code mods so far are all contained within CMEPS (esmFldsExchange_cesm_mod.F90, med_phases_aofluxes_mod.F90, and shr_flux_mod.F90) but the impacts of the addition also influence the atmosphere and might require some tuning.

We've tested this with 32L (ten year F2010 runs, diagnostics here: gust_32L_diag), and over a shorter period with 58L (gust_58L_diag). For reference, there are also comparisons to observations in the parent directory.

@adamrher
Copy link

It looks to me like a slight increase in ITCZ precip rates; more significant in the L32 run and barely discernible in L58. Does the L58 run use ZM2? @swrneale have you looked at impacts on MJO?

@swrneale
Copy link
Collaborator

The impact is quite rightly greatest in weak wind regimes beneath the ITCZ and in the Western Pacific during Summer time where LHFLX is underestimated. This is our first cut with L58. I don't understand why the impact is weaker than L32, which has many desirable impacts I think. Let us take a look at everything. We certainly aren't suggesting this will go in tomorrow of course!

@megandevlan
Copy link
Author

@adamrher Yep, good eye! we'll need to dive into this more, the 58L diagnostics are hot off the press and definitely deserve more focused attention. I think a few more years might be helpful - the JJA signal in precip rate for the 32L for example looks nice and consistent, the 58L with fewer years is still a little noisy in the West Pacific.
I was under the impression that ZM2 is used... I branched from cam_development in mid-January but didn't make any changes, are those incorporated yet? (Sorry for my lack of familiarity with this)

@adamrher
Copy link

@megandevlan what is cam tag (I usually just look at the latest entry in doc/ChangeLog)?

@megandevlan
Copy link
Author

That's what I've been looking for, thanks Adam!! cam6_3_045

@adamrher
Copy link

That's a great tag! To invoke ZM2, you just need to ./xmlchange CAM_CONFIG_OPTS='-phys cam_dev' --append. This will also reorder the physics ... the reordered physics + ZM2 should be used when running L58. Apologies if you already know this; just want to be explicit about this as you continue to explore this gustiness param.

@megandevlan
Copy link
Author

Thanks, Adam! This level of explicitness is really helpful, I had neglected the -phys option so indeed the above 58L runs are wonky. Thanks for helping uncover this!

@megandevlan
Copy link
Author

Just as a quick update - we now have diagnostics for a 58L SE run with the cam_dev physics here (and each vs obs in the parent directory as before). A lot more analysis still needed to understand this fully but the patterns of change are somewhat more similar to the 32L case now, as Rich has suggested - somewhat of an increase in JJA precip over the West Pacific, and fairly consistent LHFLX changes globally in that season as well.

@gold2718 gold2718 moved this to To Do in CAM Development Apr 28, 2022
@cacraigucar cacraigucar changed the title Convective gustiness impacts added to ocean surface flux Convective gustiness impacts added to ocean surface flux #540 May 2, 2022
@megandevlan
Copy link
Author

It's been a long time since opening this, but the gust mods are finally ready to be added to cam-dev; I'm opening a PR request now.

@adamrher
Copy link

Just a heads up, you might need some SE support for making a cdeps namelists (gust) conditional on the physics type in CAM (we only want this on for cam_dev/cam7).

@megandevlan
Copy link
Author

Yep, hadn't thought about that one! Not entirely clear how to do that, so will definitely need SE help.

@cacraigucar
Copy link
Collaborator

I have just added the CoupledEval3 tag to this since it sounds like it is wanted for the release.

Yes, we SEs can help with the namelists. We will need to know how to set the defaults. It sounds like it will only be needed for cam_dev/CAM7. Should it be on by default or not for cam_dev/CAM7? If it will be on by default, I assume it changes answers and it will need some science runs to validate answers so that Peter (and Adam maybe) can say that it is okay to go into current cam_development. If it will be off by default, then not so critical to have science runs, but still very helpful to document what it is doing.

@PeterHjortLauritzen
Copy link
Collaborator

Yes we want this on by default in cam_dev/CAM7

@megandevlan
Copy link
Author

Exciting update! ESCOMP/CMEPS#422 is in CMEPS with a flag to check that this can only be activated when using cam_dev physics right now thanks to @jedwards4b. So the CAM side should be pretty straightforward from here (fingers crossed)

@adamrher
Copy link

adamrher commented Dec 21, 2023

Thanks! Not clear to me tho if this is just a check ('you can only run gust's w/ CAM%DEV, else error out'), or if it's setting gust=T if CAM%DEV is invoked. We don't need a conflict check, we need it to set gusts=T if CAM%DEV is invoked.

@jedwards4b
Copy link

What is there is only a conflict check. If you want it on when camdev is invoked then you need another change.

@jedwards4b
Copy link

ESCOMP/CMEPS#424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

8 participants