tlakhankar / CCNY-WRF-Research

CCNY Research on PR and Maine under the supervision of Dr. Tarendra Lakhankar.
2 stars 0 forks source link

32nd Day for LDASIN GFSANL files (FORCING) #21

Closed AIdrisy0139 closed 5 years ago

AIdrisy0139 commented 5 years ago

Explanation of Problem

Due to GFSANL's different model cycle when running files for the end of July 2019 through the ESMF script it outputs a file for JULY 32nd, a day that does not exist.

Input Files

gfsanl_4_20190731_0000_006.grb2
gfsanl_4_20190731_0600_006.grb2
gfsanl_4_20190731_1200_006.grb2
gfsanl_4_20190731_1800_006.grb2
gfsanl_4_20190801_0000_006.grb2
gfsanl_4_20190801_0600_006.grb2
gfsanl_4_20190801_1200_006.grb2
gfsanl_4_20190801_1800_006.grb2
gfsanl_4_20190802_0000_006.grb2
gfsanl_4_20190802_0600_006.grb2
gfsanl_4_20190802_1200_006.grb2
gfsanl_4_20190802_1800_006.grb2

Output Files

2019073106.LDASIN_DOMAIN1
2019073112.LDASIN_DOMAIN1
2019073118.LDASIN_DOMAIN1
2019073200.LDASIN_DOMAIN1  <------
2019080106.LDASIN_DOMAIN1
2019080112.LDASIN_DOMAIN1
2019080118.LDASIN_DOMAIN1
2019080200.LDASIN_DOMAIN1
2019080206.LDASIN_DOMAIN1
2019080212.LDASIN_DOMAIN1
2019080218.LDASIN_DOMAIN1
2019080300.LDASIN_DOMAIN1

The Error

The primary issue is this errant file leads to WRF crashing before it can enter the month of AUGUST

Here is the tail of the Diag file when running the files above in the ./FORCING directory

 finished call drive_CHANNEL
 *****yw******end drive_CHANNEL
 Timing: Channel Routing  accumulated time--   20.2560005
 Beginning Aggregation...
 Agg Mass Bal:
 WB_AGG!InfxsDiff   1.02035701E-05
 WB_AGG!Infxs1   1.42490491E-02
 WB_AGG!Infxs2   1.42592527E-02
 WB_AGG!SMCDiff  0.277408600
 WB_AGG!SMC1   506.125671
 WB_AGG!SMC2   551.290649
 WB_AGG!SICE2   44.8875694
 WB_AGG!Residual  0.277418792
 Finished Aggregation...
 current time is 2019-07-31_18:00:00
 output hydrology at time : 2019-07-31_18:00:00
 before call output_chrt
 end calling output functions
 accumulated time (s):    80.812500000000000
 ***DATE=2019-07-31_18:00:00    Timing:  41.28 Cumulative:       81.07  SFLX:   0.02
 no forcing data found./FORCING/2019080100.LDASIN_DOMAIN1  
AIdrisy0139 commented 5 years ago

The Workaround

The solution is to simply rename the errant file, for i.e. 2019073200.LDASIN_DOMAIN1 to what WRF-HYDRO would be looking for, i.e 2019080100.LDASIN_DOMAIN1

The Long term Fix

Possibly have a BASH or PYTHON script go through the ./FORCING directory to and rename such files?