CESM 2.1.3 on Cannon; SnicarSnowmod.f90 error

cgolja

Colleen
New Member
Hello!


I’m building CESM 2.1.3 in the following configuration

Compset is: 1850_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD
Grid is: a%1.9x2.5_l%1.9x2.5_oi%gx1v7_r%r05_g%gland4_w%ww3a_m%gx1v7
Components in compset are: ['cam', 'clm', 'cice', 'pop', 'mosart', 'cism', 'ww3', 'sesp', 'drv', 'dart']

I can successfully build and run the model without having it fail. I'm trying to gauge how concerning build warnings are. Most of are of the formats:
warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value.
warning #6178: The return value of this FUNCTION has not been defined.

However, within my CLM build log I see the following:
remark #8291: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+7'.
write (iulog,"(a,e12.6,a,i6,a,i6)") "SNICAR ERROR: Energy conservation error of : ", energy_sum, &

Tracing this back to the original file (SnowSnicarMod.f90 (911) )

! Energy conservation check:
! Incident direct+diffuse radiation equals (absorbed+bulk_transmitted+bulk_reflected)
energy_sum = (mu_not*pi*flx_slrd_lcl(bnd_idx)) + flx_slri_lcl(bnd_idx) - (F_abs_sum + F_btm_net + F_sfc_pls)
if (abs(energy_sum) > 0.00001_r8) then
write (iulog,"(a,e12.6,a,i6,a,i6)") "SNICAR ERROR: Energy conservation error of : ", energy_sum, &
" at timestep: ", nstep, " at column: ", c_idx
call endrun(decomp_index=c_idx, clmlevel=namec, msg=errmsg(sourcefile, __LINE__))
endif

I'm unsure if I this is a warning that signals a larger issue, or if it is ignorable? (seems not good)
Thanks in advance for any insight!

Best,
Colleen
 

katec

CSEG and Liaisons
Staff member
Hi Colleen,

All of the warnings and remarks above are totally fine and expected. This model has millions of lines of code that have been written over the course of 40 years. Not all compilers are perfectly happy with every single line, and some warnings or remarks are to be expected. If it builds and runs, you are doing great! You can safely ignore FORTRAN build warnings, in general.
 
Back
Top