*** ERROR ABORT in subroutine CONVCLD_ACM on PE 000
NEGATIVE RAIN…PROBABLY BAD MET DATA… inMET_CRO_2D
PM3EXIT: DTBUF 0:00:00 June 27, 2017
Date and time 0:00:00 June 27, 2017 (2017178:000000)
I have never seen this error before, and i check the MET_CRO_2D file, there was no negative value for the ‘RN’ variable in MET file.
I would be grateful if anyone can help me with this issue.
setenv NEW_START TRUE #> Set to FALSE for model restart
set START_DATE = “2017-06-25” #> beginning date (July 1, 2016)
set END_DATE = “2017-07-01” #> ending date (July 14, 2016)
#> Set Timestepping Parameters
set STTIME = 010000 #> beginning GMT time (HHMMSS)
set NSTEPS = 1440000 #> time duration (HHMMSS) for this run
set TSTEP = 010000 #> output time step interval (HHMMSS)
I`ve changed the start time and rerun the CCTM for several times,but same errror was occured after 46hours.
I edit the line in concld_prop_acm.F, convcld_acm.F and rescld.F file which cantain the filed of ‘NEGATIVE RAIN…PROBABLY BAD MET DATA’ as bellow:
IF ( MINVAL( RAIN ) .LT. 0.0 ) THEN
XMSG = ‘NEGATIVE RAIN…PROBABLY BAD MET DATA… in’ // MET_CRO_2D
! CALL M3EXIT ( PNAME, MDATE, MTIME, XMSG, XSTAT1 )
WRITE(,) RAIN
WRITE(,) ‘JUNRI’
END IF
As i expected the run was not aborted ,however i found lots of negative value of RN and RC in log file, please find the abnormal data in the attached file.
Hi Zunyir,
I have the same problem when NSTEPS > 480000 (or RUNLEN ==48 ,next day 23:00 ) ,Now I set NSTEPS=240000. It working.
It crash by “concld_prop_acm.F”,I already check RN and RC,they all positive.
PGI 19.4.
Cheers,
janhon
I compiled the coupled WRF-CMAQv(4.1.1-5.3) model with the EMIS_DEFN.F and centralized_io_module.F file you provied. But the two-way run aborted with the following error:
d01 2017-07-03_00:00:00 --> CALL DIAGNOSTICS PACKAGE: NWP DIAGNOSTICS
d01 2017-07-03_00:00:00 call HALO_RK_E
d01 2017-07-03_00:00:00 calling inc/HALO_EM_E_5_inline.inc
d01 2017-07-03_00:00:00 call HALO_RK_MOIST
d01 2017-07-03_00:00:00 calling inc/HALO_EM_MOIST_E_5_inline.inc
d01 2017-07-03_00:00:00 call end of solve_em
WRF Version V4.1.1
WRF Version 4.100000
Hybrid option number 2
Hybrid vertical coordinate (T/F) T
PX MODIS (T/F) T
>>--->> WARNING in subroutine retrieve_time_dep_gridde
2017183:001200 n/a for DENSA_J from MET_CRO_3D (2017182:000000 by 1200)
M3WARN: DTBUF 0:12:00 July 2, 2017
*** ERROR ABORT in subroutine retrieve_time_de on PE 000
Could not extract MET_CRO_3D file
Date and time 0:12:00 July 2, 2017 (2017183:001200)
I`ve changed the start time and sync time step rerun the two-way model for several times, same errror was occured after 47 hours. So i wonder shoud i compile two-way model with the "official” code? or any other problem with this simulation?