I am running MCIPv4.5 for 25 hours, from previous day 00 UTC to next day 00 UTC.
The mcip fails for following 2 cases:
CASE 1. When ‘SIMULATION_START_DATE’ isn’t the same for previous and next day wrf outputs. Ex. wrfout_d01_2016-05-29_00:00:00 and wrfout_d01_2016-05-30_00:00:00 files, the mcip.exe encounters with an error in subroutine: CHKWRFHDR (see below). Please note the WRF outputs are for the same domain, it re-started at different times.
*** SUBROUTINE: CHKWRFHDR
*** WRF FILES DO NOT SEEM TO BE FROM SAME DOMAIN
*** VARIABLE = SIMULATION_START_DATE
*** FIRST FILE = /t1/LADCO_WRF2016/wrfout_4km/wrfout_d01_2016-05-29_00:00:00
*** VALUE IN FIRST FILE = 2016-04-29-00:00:00
*** NEW FILE = /t1/LADCO_WRF2016/wrfout_4km/wrfout_d01_2016-05-30_00:00:00
*** VALUE IN NEW FILE = 2016-05-29-00:00:00
*** ERROR ABORT in subroutine CHKWRFHDR ABNORMAL TERMINATION IN CHKWRFHDR Date and time 0:00:00 May 30, 2016 (2016151:000000)
I tried setting IOAPI_CHECK_HEADERS off and on in run_mcip.csh, but no effect, nothing changed. How to overpass this inconsistent SIMULATION_START_DATE issue when running mcip.exe?
CASE 2. THE mcip fails with an error message of “MCIP output must start after meteorology start time” when running mcip for a day (ex. 2016-07-11_00:00:00) that WRF output has the same SIMULATION_START_DATE (ex. 2016-07-11_00:00:00).
*** SUBROUTINE: SETGRIDDEFS
*** MCIP output must start after meteorology start time
*** User-defined MCIP start date = 2016-07-11-00:00:00.0000
*** Input meteorology start date = 2016-07-11-00:00:00.0000
*** ERROR ABORT in subroutine SETGRIDDEFS ABNORMAL TERMINATION IN SETGRIDDEFS Date and time 0:00:00 July 11, 2016 (2016193:000000)
!!— Error occurs in mcip.exe for wrfout_4km on 20160711
Please help me resolving these 2 errors I face with MCIPv4.5.
Tsengel Nergui, LADCO