You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggest adding the following optional arguments to shr_abort_abort: esmf_log_write, line, and file. line and file allow sending down the line and file for the originating error and would be used with errmsg in shr_log_mod. emsf_log_write would add a call to ESMF_LogWrite, that would look something like this...
logical:: esmf_log
if ( present(esmf_log_write) )then
esmf_log = esmf_log_write
else
esmf_log =.false.end ifif ( esmf_log ) then
rc = ESMF_FAILURE
call ESMF_LogWrite(trim(string), &
ESMF_LOGMSG_ERROR, line=line, file=file)
end if
This means error checking would require that if esmf_log_write is .true. that line and file are also present. And we should probably require that BOTH file and line are sent as well in order to use errMsg. So they either need to all three be present, or both line and file be present.
Suggest adding the following optional arguments to shr_abort_abort: esmf_log_write, line, and file. line and file allow sending down the line and file for the originating error and would be used with errmsg in shr_log_mod. emsf_log_write would add a call to ESMF_LogWrite, that would look something like this...
This means error checking would require that if esmf_log_write is .true. that line and file are also present. And we should probably require that BOTH file and line are sent as well in order to use errMsg. So they either need to all three be present, or both line and file be present.
This discussion started in ESCOMP/CMEPS#527 (comment)
The text was updated successfully, but these errors were encountered: