Overview of Øyvinds simulations #108
Replies: 2 comments
-
|
@DirkOlivie @oyvindseland @gold2718 - my understanding is that the branch Is this a correct assumption? Other than the new directories ( |
Beta Was this translation helpful? Give feedback.
-
|
While not critical for the release the interface between MG and the alternative activation formulation, Betancourt and Nenes will be moved closer to the existing activation interface. The calls and definitions will be moved from the subroutine dropmixnuc to subroutine activate_modal, both within the ndrop module. This will create a cleaner interface; making it possible to run both activation schemes in the same simulation in order to output diagnostics; The tendency / flux calculations for droplet number made for BN is simplified compared to the existing activation. Moving the interface into activate_modal will make it easier to homogenize the calculations. Just copying the existing BN formulation into dropmixnuc before changing the flux formulation should give bit-identical results for both choices of activation scheme. |
Beta Was this translation helpful? Give feedback.
-
NIRD STORAGE : /projects/NS2345K/oyvinds/cases
BETZY CASE-DIRECTORY : /cluster/projects/nn2345k/oyvinds/NorESM_Forces/cases
CIMEROOT-DIRECTORY : /cluster/projects/nn2345k/oyvinds/NorESM_Forces/NorESM
User_nl_cam
User_nl_clm
CaseDocs/atm_in
Obtaining the code and viewing the differences
Overview of code changes
Details
bld/build-namelist
bld/config_files/definition.xml
Adding trop_mam_oslo_sec
bld/configure
... -chem <name> Build CAM with specified prognostic chemistry package [ trop_mam3 | trop_mam4 | trop_mam7 | trop_mozart | trop_strat_mam4_vbs | trop_strat_mam4_vbsext | waccm_ma | waccm_mad | waccm_mad_mam4 | waccm_ma_mam4 | waccm_ma_sulfur | waccm_sc | waccm_sc_mam4 | waccm_tsmlt_mam4 | [OLD] terminator | trop_mam_oslo | none ]. [NEW] terminator | trop_mam_oslo | trop_mam_oslo_sec | none ]. ... [NEW] if ($chem_pkg =~ '_oslo_sec') { [NEW] $chem_cppdefs = ' -DOSLO_AERO -DDIRIND' [NEW] } ... [NEW] if ($chem =~/_oslo_sec/) { [NEW] print $fh "$camsrcdir/cam/src/chemistry/oslo_aero_sec\n"; [NEW] print $fh "$camsrcdir/cam/src/chemistry/oslo_aero\n"; [NEW] print $fh "$camsrcdir/cam/src/physics/cam_oslo\n"; [NEW] } [NEW] elsif ($chem =~/_oslo/) { ...bld/namelist_files/namelist_defaults_cam.xml
** default emission files in case of trop_mam_oslo-sec : dms_oslo_emis_file, ... (15 files) [POSSIBLY NOT NEEDED]**
bld/namelist_files/namelist_definition.xml
[SECTIONAL AEROSOL]
[SECONDARY ICE]
bld/namelist_files/use_cases/ssp245_cam6_noresm.xml
This file did not exist (only ssp245_cam6_noresm_frc2.xml existed). Only the emission files differ.
cime_config/config_component.xml
Allow SEC as identifier
General description
Which chemistry scheme to use?
<span style="color:red"> Remark 1 : Also the setup without SEC used SEC-namelist ! </span>
<span style="color:red"> Remark 2 : PTAEROSEC? or PTAERO%SEC </span>
Which namelist to use?
Which boundary conditions to use (for Oyvinds FORCeS simulations)?
<span style="color:red"> Remark 1 : standard compsets now also use FORCeS-derived boundary conditions. Desired? </span>
[NEW FOR SECTIONAL SCHEME]
[NEW FORCES COMPSETS 2015-2019]
[NEW FOR SECONDARY ICE]
cime_config/config_compsets.xml
New compsets
[SECTIONAL MODEL]
[FORCeS fSST SSP245]
[SECTIONAL MODEL NF1850]
[SECTIONAL MODEL NF1850]
[SST file for fSST SSP245 - FORCeS COMPSET]
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/SourceMods/src.cam/preprocessorDefinitions.h
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/shell_commands
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/user_nl_cam
[TUNING]
cime_config/usermods_dirs/NorESM_Forces_lowoutput/user_nl_cam
[TUNING]
src/NorESM/clubb_intr.F90
Remark New - should be compared with ./src/physics/cam/clubb_intr.F90
[HOFER CHANGE]
src/NorESM/micro_mg2_0.F90
[SECONDARY ICE, HOFER, ICE DELIMITER]
module micro_mg2_0 ... [SECONDARY ICE CHANGES] [NEW] use module_random_forests ... subroutine micro_mg_init(...) ... [NEW] IF (FIRST_RAFSIP) THEN [NEW] CALL forestbrhm( jbt,max_nodes1,leftchild1,rightchild1,splitfeat1,nrnodes1,thresh1,out11,out12,out13) [NEW] CALL forestbr( jbt,max_nodes2,leftchild2,rightchild2,splitfeat2,nrnodes2,thresh2,out21) [NEW] CALL forestall( jbt,max_nodes3,leftchild3,rightchild3,splitfeat3,nrnodes3,thresh3,out31,out32,out33,out34,out35) [NEW] CALL forestbrds( jbt,max_nodes4,leftchild4,rightchild4,splitfeat4,nrnodes4,thresh4,out41,out42,out43) [NEW] CALL forestbrwarm(jbt,max_nodes5,leftchild5,rightchild5,splitfeat5,nrnodes5,thresh5,out51) [NEW] FIRST_RAFSIP = .FALSE. [NEW] ENDIF end subroutine micro_mg_init subroutine micro_mg_tend (...) ... ! RaFSIP additional parameters ! GS/PG [NEW] logical :: rafsip_on [NEW] !Inputs to SIP parameterization [NEW] real(r8) :: IWC(mgncol,nlev) ! TOTAL ICE WATER CONTENT IN KG/KG INPUT TO RaFSIP [NEW] real(r8) :: RIMC(mgncol,nlev) ! TOTAL CLOUD DROPLET RIMING IN KG/KG/S INPUT TO RaFSIP [NEW] real(r8) :: RIMR(mgncol,nlev) ! TOTAL RAINDROP RIMING IN KG/KG/S INPUT TO RaFSIP [NEW] real(r8) :: TEMPK(mgncol,nlev) ! TEMPERATURE IN K INPUT TO RaFSIP [NEW] real(r8) :: RHI(mgncol,nlev) ! RELATIVE HUMIDITY WRT ICE INPUT TO RaFSIP [NEW] real(r8) :: LWC(mgncol,nlev) ! TOTAL LIQUID WATER CONTENT IN KG/KG INPUT TO RaFSIP [NEW] !Outputs [NEW] real(r8) :: BR_RATE(mgncol,nlev) ! SIP RATE DUE TO COLLISIONAL BREAK-UP [NEW] real(r8) :: DS_RATE(mgncol,nlev) ! SIP RATE DUE TO DROPLET-SHATTERING [NEW] real(r8) :: HM_RATE(mgncol,nlev) ! SIP RATE DUE TO HALLETT-MOSSOP [NEW] real(r8) :: SIP_RATE(mgncol,nlev) ! TOTAL SIP rate predicted by the RaFSIP (kg-1 s-1) [NEW] real(r8) :: QIRSIP(mgncol,nlev) ! MASS TRASFERRED FROM RAINDROPS TO CLOUD ICE DUE TO HM OR DS [NEW] real(r8) :: QICSIP(mgncol,nlev) ! MASS TRASFERRED FROM CLOUD DROPLETS TO CLOUD ICE DUE TO THE DS [NEW] real(r8) :: relhumi(mgncol,nlev)src/chemistry/oslo_aero/NdParam.f [NENES - COMPLETELY NEW]
[ACTIVATION]
src/chemistry/oslo_aero/hetfrz_classnuc_oslo.F90 [MODIFICATIONS BY !jks]
<span style="color:red"> Remark 1 : what is this belonging to? </span>
src/chemistry/oslo_aero/module_random_forests.F90 [NEW - SECONDARY ICE]
[SECONDARY ICE]
src/chemistry/oslo_aero/ndrop.F90
[ACTIVATION]
src/chemistry/oslo_aero/oslo_aerosols_intr.F90
<span style="color:red"> Remark 1 : why is the initialisation of dens_aer removed? </span>
<span style="color:red"> Remark 2 : why is l_ss_a2, l_ss_a3 and l_so4_a2 treatet seperately? </span>
[DRY DEPOSITION BUG] rad_aer(1:ncol,top_lev:) = 0.5_r8*dgncur_awet(1:ncol,top_lev:,m) & [OLD] *exp(1.5_r8*(logSigma)) [NEW] *exp(1.5_r8*(logSigma**2)) ... rad_aer(1:ncol,top_lev:) = 0.5_r8*dgncur_awet_processmode(1:ncol,top_lev:,processModeMap(mm)) [OLD] *exp(1.5_r8*(logSigma)) [NEW] *exp(1.5_r8*(logSigma**2)) end subroutine oslo_aero_dry_intrsrc/chemistry/oslo_aero/parametr.inc [NEW - ACTIVATION NENES]
src/chemistry/oslo_aero_sec/LOG_SECTIONAL_IMP.md
src/chemistry/oslo_aero_sec/aero_model.F90 [SECTIONAL SCHEME]
src/chemistry/oslo_aero_sec/aero_sectional.F90 [SECTIONAL SCHEME - COMPLETELY NEW]
[SECTIONAL]
src/chemistry/oslo_aero_sec/aeronucl.F90 [SECTIONAL SCHEME]
[SECTIONAL]
src/chemistry/oslo_aero_sec/condtend.F90
[SECTIONAL SCHEME]
src/chemistry/oslo_aero_sec/koagsub.F90 [A LOT OF CHANGES]
[SECTIONAL]
src/chemistry/oslo_aero_sec/ndrop.F90
<span style="color:red"> Equal to : src/chemistry/oslo_aero/ndrop.F90 : maybe not needed?</span>
src/chemistry/oslo_aero_sec/oxi_diurnal_var.F90 : [SECTIONAL AEROSOL SCHEME]
<span style="color:red"> Shall we have this always active? </span>
New chemical scheme
List of new files
src/chemistry/pp_trop_mam_oslo_sec/chem_mech.in
Isoprene yields have been lowered.
<span style="color:red"> Remark : shall we lower yield in all chemistry schemes? </span>
src/control/runtime_opts.F90
src/physics/cosp2/optics/cosp_optics.F90
Hopp til innhold
Bruk E-post for Meteorologisk institutt med skjermlesere
1 av 44
NorESM2.1
Dirk Jan Leo Olivie
Vedlegg
18:22 (for 2 timer siden)
til meg, Mariana, Øyvind
Oversett e-posten
Slå av for: engelsk
Hi Mariana, Steve and Øyvind,
I have made an overview of the characteristics of the FORCeS branch of Øyvind in the attached file.
The file is an *.md file, and I visualize it with (vs)code.
I hope this is useful, but I don't know what the best way to share this file would be? (Should I make a repository with just this file in?)
Best regards,
Dirk
--
##################################
Dr. D.J.L. Olivié
Norwegian Meteorological Institute,
Research and Development.
P.O. Box 43, Blindern,
N-0313 Oslo, Norway
Phone:
Mobile: +47 90576952
e-mail: dirk.olivie@met.no
###################################
Ett vedlegg
• Gjennomsøkt av Gmail
Steve Goldhaber stevenng@met.no
19:05 (for 1 time siden)
til Dirk, Mariana, Øyvind
GitHub has a feature for items such as this called the Gist.
I can turn this into a Gist if you want or you can go to https://gist.github.com/ and create your own.
You can then add a link to the Gist as an item in one or more NorESM2.1 issues.
For that matter, there should probably be an issue for bringing in this code so perhaps just copy the MarkDown to a new issue and label it with the NorESM2.1 milestone.
--Steve
FORCeS SIMULATIONS
Overview of Øyvinds simulations
NIRD STORAGE : /projects/NS2345K/oyvinds/cases
BETZY CASE-DIRECTORY : /cluster/projects/nn2345k/oyvinds/NorESM_Forces/cases
CIMEROOT-DIRECTORY : /cluster/projects/nn2345k/oyvinds/NorESM_Forces/NorESM
User_nl_cam
User_nl_clm
CaseDocs/atm_in
Obtaining the code and viewing the differences
Overview of code changes
Details
bld/build-namelist
bld/config_files/definition.xml
Adding trop_mam_oslo_sec
bld/configure
... -chem <name> Build CAM with specified prognostic chemistry package [ trop_mam3 | trop_mam4 | trop_mam7 | trop_mozart | trop_strat_mam4_vbs | trop_strat_mam4_vbsext | waccm_ma | waccm_mad | waccm_mad_mam4 | waccm_ma_mam4 | waccm_ma_sulfur | waccm_sc | waccm_sc_mam4 | waccm_tsmlt_mam4 | [OLD] terminator | trop_mam_oslo | none ]. [NEW] terminator | trop_mam_oslo | trop_mam_oslo_sec | none ]. ... [NEW] if ($chem_pkg =~ '_oslo_sec') { [NEW] $chem_cppdefs = ' -DOSLO_AERO -DDIRIND' [NEW] } ... [NEW] if ($chem =~/_oslo_sec/) { [NEW] print $fh "$camsrcdir/cam/src/chemistry/oslo_aero_sec\n"; [NEW] print $fh "$camsrcdir/cam/src/chemistry/oslo_aero\n"; [NEW] print $fh "$camsrcdir/cam/src/physics/cam_oslo\n"; [NEW] } [NEW] elsif ($chem =~/_oslo/) { ...bld/namelist_files/namelist_defaults_cam.xml
** default emission files in case of trop_mam_oslo-sec : dms_oslo_emis_file, ... (15 files) [POSSIBLY NOT NEEDED]**
bld/namelist_files/namelist_definition.xml
[SECTIONAL AEROSOL]
[SECONDARY ICE]
bld/namelist_files/use_cases/ssp245_cam6_noresm.xml
This file did not exist (only ssp245_cam6_noresm_frc2.xml existed). Only the emission files differ.
cime_config/config_component.xml
Allow SEC as identifier
General description
Which chemistry scheme to use?
Remark 1 : Also the setup without SEC used SEC-namelist !
Remark 2 : PTAEROSEC? or PTAERO%SEC
Which namelist to use?
Which boundary conditions to use (for Oyvinds FORCeS simulations)?
Remark 1 : standard compsets now also use FORCeS-derived boundary conditions. Desired?
[NEW FOR SECTIONAL SCHEME]
[NEW FORCES COMPSETS 2015-2019]
[NEW FOR SECONDARY ICE]
cime_config/config_compsets.xml
New compsets
[SECTIONAL MODEL]
[FORCeS fSST SSP245]
[SECTIONAL MODEL NF1850]
[SECTIONAL MODEL NF1850]
[SST file for fSST SSP245 - FORCeS COMPSET]
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/SourceMods/src.cam/preprocessorDefinitions.h
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/shell_commands
cime_config/usermods_dirs/NorESM_Forces_aer_cosp/user_nl_cam
[TUNING]
cime_config/usermods_dirs/NorESM_Forces_lowoutput/user_nl_cam
[TUNING]
src/NorESM/clubb_intr.F90
Remark New - should be compared with ./src/physics/cam/clubb_intr.F90
[HOFER CHANGE]
src/NorESM/micro_mg2_0.F90
[SECONDARY ICE, HOFER, ICE DELIMITER]
module micro_mg2_0 ... [SECONDARY ICE CHANGES] [NEW] use module_random_forests ... subroutine micro_mg_init(...) ... [NEW] IF (FIRST_RAFSIP) THEN [NEW] CALL forestbrhm( jbt,max_nodes1,leftchild1,rightchild1,splitfeat1,nrnodes1,thresh1,out11,out12,out13) [NEW] CALL forestbr( jbt,max_nodes2,leftchild2,rightchild2,splitfeat2,nrnodes2,thresh2,out21) [NEW] CALL forestall( jbt,max_nodes3,leftchild3,rightchild3,splitfeat3,nrnodes3,thresh3,out31,out32,out33,out34,out35) [NEW] CALL forestbrds( jbt,max_nodes4,leftchild4,rightchild4,splitfeat4,nrnodes4,thresh4,out41,out42,out43) [NEW] CALL forestbrwarm(jbt,max_nodes5,leftchild5,rightchild5,splitfeat5,nrnodes5,thresh5,out51) [NEW] FIRST_RAFSIP = .FALSE. [NEW] ENDIF end subroutine micro_mg_init subroutine micro_mg_tend (...) ... ! RaFSIP additional parameters ! GS/PG [NEW] logical :: rafsip_on [NEW] !Inputs to SIP parameterization [NEW] real(r8) :: IWC(mgncol,nlev) ! TOTAL ICE WATER CONTENT IN KG/KG INPUT TO RaFSIP [NEW] real(r8) :: RIMC(mgncol,nlev) ! TOTAL CLOUD DROPLET RIMING IN KG/KG/S INPUT TO RaFSIP [NEW] real(r8) :: RIMR(mgncol,nlev) ! TOTAL RAINDROP RIMING IN KG/KG/S INPUT TO RaFSIP [NEW] real(r8) :: TEMPK(mgncol,nlev) ! TEMPERATURE IN K INPUT TO RaFSIP [NEW] real(r8) :: RHI(mgncol,nlev) ! RELATIVE HUMIDITY WRT ICE INPUT TO RaFSIP [NEW] real(r8) :: LWC(mgncol,nlev) ! TOTAL LIQUID WATER CONTENT IN KG/KG INPUT TO RaFSIP [NEW] !Outputs [NEW] real(r8) :: BR_RATE(mgncol,nlev) ! SIP RATE DUE TO COLLISIONAL BREAK-UP [NEW] real(r8) :: DS_RATE(mgncol,nlev) ! SIP RATE DUE TO DROPLET-SHATTERING [NEW] real(r8) :: HM_RATE(mgncol,nlev) ! SIP RATE DUE TO HALLETT-MOSSOP [NEW] real(r8) :: SIP_RATE(mgncol,nlev) ! TOTAL SIP rate predicted by the RaFSIP (kg-1 s-1) [NEW] real(r8) :: QIRSIP(mgncol,nlev) ! MASS TRASFERRED FROM RAINDROPS TO CLOUD ICE DUE TO HM OR DS [NEW] real(r8) :: QICSIP(mgncol,nlev) ! MASS TRASFERRED FROM CLOUD DROPLETS TO CLOUD ICE DUE TO THE DS [NEW] real(r8) :: relhumi(mgncol,nlev)src/chemistry/oslo_aero/NdParam.f [NENES - COMPLETELY NEW]
[ACTIVATION]
src/chemistry/oslo_aero/hetfrz_classnuc_oslo.F90 [MODIFICATIONS BY !jks]
Remark 1 : what is this belonging to?
src/chemistry/oslo_aero/module_random_forests.F90 [NEW - SECONDARY ICE]
[SECONDARY ICE]
src/chemistry/oslo_aero/ndrop.F90
[ACTIVATION]
src/chemistry/oslo_aero/oslo_aerosols_intr.F90
Remark 1 : why is the initialisation of dens_aer removed?
Remark 2 : why is l_ss_a2, l_ss_a3 and l_so4_a2 treatet seperately?
[DRY DEPOSITION BUG] rad_aer(1:ncol,top_lev:) = 0.5_r8*dgncur_awet(1:ncol,top_lev:,m) & [OLD] *exp(1.5_r8*(logSigma)) [NEW] *exp(1.5_r8*(logSigma**2)) ... rad_aer(1:ncol,top_lev:) = 0.5_r8*dgncur_awet_processmode(1:ncol,top_lev:,processModeMap(mm)) [OLD] *exp(1.5_r8*(logSigma)) [NEW] *exp(1.5_r8*(logSigma**2)) end subroutine oslo_aero_dry_intrsrc/chemistry/oslo_aero/parametr.inc [NEW - ACTIVATION NENES]
src/chemistry/oslo_aero_sec/LOG_SECTIONAL_IMP.md
src/chemistry/oslo_aero_sec/aero_model.F90 [SECTIONAL SCHEME]
src/chemistry/oslo_aero_sec/aero_sectional.F90 [SECTIONAL SCHEME - COMPLETELY NEW]
[SECTIONAL]
src/chemistry/oslo_aero_sec/aeronucl.F90 [SECTIONAL SCHEME]
[SECTIONAL]
src/chemistry/oslo_aero_sec/condtend.F90
[SECTIONAL SCHEME]
src/chemistry/oslo_aero_sec/koagsub.F90 [A LOT OF CHANGES]
[SECTIONAL]
src/chemistry/oslo_aero_sec/ndrop.F90
Equal to : src/chemistry/oslo_aero/ndrop.F90 : maybe not needed?
src/chemistry/oslo_aero_sec/oxi_diurnal_var.F90 : [SECTIONAL AEROSOL SCHEME]
Shall we have this always active?
New chemical scheme
List of new files
src/chemistry/pp_trop_mam_oslo_sec/chem_mech.in
Isoprene yields have been lowered.
Remark : shall we lower yield in all chemistry schemes?
src/control/runtime_opts.F90
src/physics/cosp2/optics/cosp_optics.F90
version_forces.v1.1.md
Viser version_forces.v1.1.md.
Beta Was this translation helpful? Give feedback.
All reactions