Add support for NSSL cloud microphysics scheme (CCPP) #277
Conversation
…Set default namelists and tracer config files. Also added new array otsptflag to set flags for tracer diffusion
MicroTed
requested review from
climbfuji,
grantfirl and
llpcarson
as code owners
Set otsptflag as size 'ntrac' and set values with more obvious logic.
…Set default namelists and tracer config files. Also added new array otsptflag to set flags for tracer diffusion
Set otsptflag as size 'ntrac' and set values with more obvious logic.
…Set default namelists and tracer config files. Also added new array otsptflag to set flags for tracer diffusion
Set otsptflag as size 'ntrac' and set values with more obvious logic.
…-scm into feature/nssl_micro
|
Updated to 28 Dec. 2021 working version of SCM+CCPP (newer CCPP seems to have unsupported variables) |
@MicroTed The SCM has been updated to the latest ccpp-physics/framework. This means that you should be able to update your ccpp-physics PR and this one and it should work. |
|
OK, cool, I'll try updating. The last that I worked on fv3atm (week or two ago), it seemed to be good with the then-latest CCPP, as well. |
|
This and the CCPP PR have been updated to current main |
…he GSD_v1nssl namelist/tracers settings to turn hail on so that it is tested in the system.
…n in .gitmodules, make ccpp_prebuild.py use --debug flag when cmake build type is DEBUG
couple minor changes
| imfdeepcnv = -1 | ||
| imfshalcnv = -1 | ||
| imp_physics = 17 | ||
| nssl_ccn_on = .false. |
There was a problem hiding this comment.
Is this namelist supposed to have nssl_ccn_on and nssl_hail_on = F? The other one (input_RRFS_v1_nssl_nohailnoccn.nml) already has these as F.
There was a problem hiding this comment.
Good catch, I probably forgot I had changed it during testing. Since the default for the suite is
"SCM_RRFS_v1nssl":"input_RRFS_v1nssl_nohailnoccn.nml"
Then I could either remove input_RRFS_v1nssl.nml or change it to turn on both hail and CCN as an example. Although I suppose the point of SCM is not to get the 'best' result but rather to check that the scheme is working. Generally, I'd like to set things up for the intended use/needs of SCM. Hail was turned off here because the scheme probably would not produce any, and it's not an output variable anyway.
change units for a few flags
Update feature/nssl_micro branch to latest main
Add support for NSSL cloud microphysics scheme (CCPP)
See CCPP pull request for NSSL scheme features (NCAR/ccpp-physics#761)
Related PR for FV3: NOAA-EMC/fv3atm#472
Adds suites, namelists, and tracer config files for NSSL (with/without hail/CCN)
Namelist options:
nssl_cccn - CCCN background CCN concentration. Default: 0.6e9 (per m^3 at STP)
nssl_alphah - graupel shape parameter, default = 0.
nssl_alphahl - hail shape parameter, default = 1.
nssl_hail_on - hail activation flag, default = .false.
nssl_ccn_on - CCN prediction flag, default = .true.
nssl_invertccn - store CCN as number of activated instead of number remaining, default = .true. (avoids need for specified boundary conditions)
Example test run:
./run_scm.py -c twpice -n input_GSD_v1nssl_nohailnoccn.nml -t tracers_gsd_nssl_nohail_noccn.txt -s SCM_GSD_v1nssl
Also made a change to netcdf output to set the initial date info as integers (matching the native data type). This also solves a type mismatch issue with the analysis python program. (Error passing date info as floats instead of integers.)