-
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
f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008 #614
Comments
@cecilehannay would you be willing to submit another FMTHIST run --- this 008 run, but with c8=4.4? I need to evaluate the run 116 parameters in an PD F-case to know if I can potentially increase c8 a bit more than 4.4. |
@adamrher I was hoping to replicate aspects of your simulation, but this setting fails to find the file at runtime: |
If I misspoke and this case is not @adamrher's, should I be asking my question to @JulioTBacmeister, whose name appears in the ncdata path? Sorry if I'm confused :-) |
Hi Sam, we probably should get you permissions to this campaign directory in the near future, but for now I copied the file into my scratch directory which you should have read access to:
|
Thanks, Adam. I copied the file, so you do not need to worry if it gets scrubbed. |
Purpose:
seasalt tuning with new dust
Description:
same as #611 except
Case directory:
Locally (if still available):
/glade/campaign/cesm/cesmdata/cseg/runs/cesm2_0/f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008
On github:
https://github.com/NCAR/amwg_dev/tree/f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008
Sandbox:
Locally (if still available):
/glade/work/hannay/cesm_tags/cesm3_0_alpha04a
On github:
https://github.com/ESCOMP/CAM/tree/cesm3_0_alpha04a
Diagnostics:
https://webext.cgd.ucar.edu/FMTHIST/f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008/atm/
Output:
/glade/derecho/scratch/hannay/archive/f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008/
/glade/campaign/cgd/amp/amwg/climo/f.e30_alpha04a.FMTHIST.ne30_L93_tuning.008
Contacts:
@cecilehannay @JulioTBacmeister @swrneale @tilmes
The text was updated successfully, but these errors were encountered: