Troubleshooting floating point error in cesm.log for adding new diagnostics and tracers

[shiannder]

Hi,

I am running with CESM 2.2 compset G1850ECOIAF.

I have made several large changes based on the "Add a diagnostic" and "Add a tracer" guides for adding tracers related to ciso variables (below) for dissolved organic carbon 13 isotope and 14 radiocarbon for semi labile and refractory. Essentially, I want to convert DO13Ctot into DO13C and DO13Cr; DO14Ctot into DO14C and DO14Cr for semi labile and refractory ciso parts.

• CISO_DOC_d13C
• CISO_DOCr_d13C
• CISO_DOC_d14C
• CISO_DOCr_d14C
• CISO_DO13C_prod
• CISO_DO13Cr_prod
• CISO_DO13C_remin
• CISO_DO13Cr_remin
• do13c
• do13cr
• do14c
• do14cr
• do13c_ind
• do13cr_ind
• do14c_ind
• do14cr_ind
• CISO_DOC_d13C
• CISO_DOCr_d13C
• CISO_DOC_d14C
• CISO_DOCr_d14C

I made a new initial condition file with isotope carbon values stored in user_nl_pop:

• init_ecosys_init_file = '/mnt/lustre/letscher/jsl1063/initcond/cisodocsl/jsl180_ciso_ecosys_jan_IC_gx3v7_20180308.nc'

My current model run (jsl.188) with "./xmlchange DEBUG=TRUE" reports back "Caught signal 8 (Floating point exception: floating-point divide by zero)" in the cesm.log.26371.250311-103711 file. My question is how can I find the location of this floating point error?

cesm and ocn logs in "/mnt/lustre/letscher/jsl1063/jsl.188/run"

Let me know if you have any questions. I can attach a pdf of my methods. In it has tracked code changes in github.

Thank you,
James