- Log in to post comments
Hi!
I seem to have the NSSL microphysics working with SCM/CCPP (at least tested for TWPICE), so my next question is about adding/removing predicted variables from the tracer array. Following Grant's advice, I have moved to the master branch of SCM (and CCPP) to get up to the revamped SCM code that uses the tracer.txt files. That was as of a few weeks ago, so they are a few commits behind
https://github.com/MicroTed/ccpp-physics/master-ted-nssl2m
https://github.com/MicroTed/gmtb-scm.git/master-ted-nssl2m
I have set up separate tracer.txt files for NSSL to either include or exclude the hail hydrometeor category (corresponding to separate suite names with either "NSSL" or "NSSLg" for graupel-only). I ended up making an internal flag (nssl_hail_on) that is set based on the value model%nthl that comes from the get_tracer_index subroutine. That tells the microphysics interface whether the hail variables actually exist or not, so that a separate interface isn't needed. I hope that's an appropriate strategy. (It seems that one has to be careful to set namelist imp_physics to match the suite selection, as I don't see a way to check this at runtime.)
In each case, there are two imp_physics options to predict CCN (imp_physics_nssl2mccn or 18) or not predict (imp_physics_nssl2m or 17). Both tracers.txt files include the CCN tracer. In GFS_typedefs.F90, can I turn this off at will by setting Model%ntccn = -99 if I want CCN to be "off"? Or is it easier to just let it exist and always be zero?
I still need to run SCM tests for the other cases, and I have a further question about my sensible heat flux results. (It's not clear why it is low, nor why it would increase if I subdivide the time step for the microphysics.)
-- Ted M.