No Forcing Data Found

[Kendall]

Hello,

I am having an issue when using GLDAS data for the Step 5 of running WRF-Hydro in Standalone mode. After running

mpirun -np 2 ./wrf_hydro.exe

The error message that shows up in the diag_hydro.00000 is:

t0OutputFlag:            1

no forcing data found./FORCING/2017010103.LDASIN_DOMAIN1

The job is stopped due to the fatal error. In read_hydro_forcing_mpp1() - no forcing data found

I am not sure what is causing this issue as in my FORCING folder, I have the following files:

2007010100.LDASIN_DOMAIN1 - 2007010421.LDASIN_DOMAIN1

These files in this FORCING folder were generated using the regridding scripts for GLDAS.

In my namelist.hrldas, I have changed the FORCING_TIMESTEP, NOAH_TIMESTEP, OUTPUT_TIMESTEP to be 10800 seconds as it matches the 3 hour timestep from the GLDAS data. In addition, in the hydro.namelist, I had changed out_dt to 180 minutes as it is equivalent to the timestep in the namelist.hrldas.

I have attached the namelist.hrldas and hydro.namelist below if more information is needed:

namelist.hrldas

https://pastebin.com/9941wSb3

hydro.namelist

https://pastebin.com/Qgsu897B

Where am I going wrong? If there is something fundamental that I am misunderstanding or skipped in the technical description of WRF-Hydro, please point me to the proper areas in the technical description.

[Katelyn FitzGerald]

Hi Kendall,

It looks like there's a discrepancy between the dates for your simulation in the namelist.hrldas (2017) and the forcing data you have available (2007).

--
You received this message because you are subscribed to the Google Groups "wrf-hydro_users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wrf-hydro_use...@ucar.edu.
To view this discussion on the web visit https://groups.google.com/a/ucar.edu/d/msgid/wrf-hydro_users/e7426e4a-379c-44fc-866a-e516390a46d6%40ucar.edu.

--

Katelyn FitzGerald

Associate Scientist III

NCAR Research Applications Laboratory

Office: 303-497-2779

[Kendall]

Hi Katelyn,

Thank you! I oversaw that and now that issue is fixed. However, this has brought up another issue.

After running mpirun -np 2 ./wrf_hydro.exe I get the following error:

Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_DIVIDE_BY_ZERO IEEE_OVERFLOW_FLAG IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
STOP wrf_abort

In my diag_hydro00000 file it gives me the following error:

t0OutputFlag:            1

read forcing data at 2007-01-01_00:00:00./FORCING/2007010103.LDASIN_DOMAIN1

emitted longwave <0; skin T may be wrong due to inconsistent

input of SHDFAC with LAI

 4          10 SHDFAC=   0.00000000     VAI=   0.00000000     TV=   290.000000     TG=   135.130722

LWDN=  -9999.00000     FIRA=   9717.36914     SNOWH=   0.00000000

FATAL ERROR: STOP in Noah-MP

I'm unsure on why this error comes up, if you have a suggestion, please let me know.

On Wednesday, July 31, 2019 at 1:04:04 PM UTC-4, Katelyn FitzGerald wrote:

Hi Kendall,

It looks like there's a discrepancy between the dates for your simulation in the namelist.hrldas (2017) and the forcing data you have available (2007).

On Wed, Jul 31, 2019 at 12:06 AM Kendall <molask...@gmail.com> wrote:

Hello,

I am having an issue when using GLDAS data for the Step 5 of running WRF-Hydro in Standalone mode. After running

mpirun -np 2 ./wrf_hydro.exe

The error message that shows up in the diag_hydro.00000 is:

t0OutputFlag:            1

no forcing data found./FORCING/2017010103.LDASIN_DOMAIN1

The job is stopped due to the fatal error. In read_hydro_forcing_mpp1() - no forcing data found

I am not sure what is causing this issue as in my FORCING folder, I have the following files:

2007010100.LDASIN_DOMAIN1 - 2007010421.LDASIN_DOMAIN1

These files in this FORCING folder were generated using the regridding scripts for GLDAS.

In my namelist.hrldas, I have changed the FORCING_TIMESTEP, NOAH_TIMESTEP, OUTPUT_TIMESTEP to be 10800 seconds as it matches the 3 hour timestep from the GLDAS data. In addition, in the hydro.namelist, I had changed out_dt to 180 minutes as it is equivalent to the timestep in the namelist.hrldas.

I have attached the namelist.hrldas and hydro.namelist below if more information is needed:

namelist.hrldas

https://pastebin.com/9941wSb3

hydro.namelist

https://pastebin.com/Qgsu897B

Where am I going wrong? If there is something fundamental that I am misunderstanding or skipped in the technical description of WRF-Hydro, please point me to the proper areas in the technical description.

--
You received this message because you are subscribed to the Google Groups "wrf-hydro_users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wrf-hyd...@ucar.edu.

To view this discussion on the web visit https://groups.google.com/a/ucar.edu/d/msgid/wrf-hydro_users/e7426e4a-379c-44fc-866a-e516390a46d6%40ucar.edu.

[Katelyn FitzGerald]

It looks like Noah-MP is crashing because of missing values in your forcing data (longwave radiation in particular).  -9999 is the default FillValue.  

[Kendall]

Is the missing values in the forcing data exist because of the GLDAS dataset or by some external factor (regridding script)? Is there a solution to this?

[Katelyn FitzGerald]

I'd suggest checking for missing and/or fill values in the forcing files you've generated as a first step in troubleshooting.  Particularly if your domain is near oceans and/or large water bodies it's possible that there are missing values in the source (GLDAS) dataset that are being applied to your domain.  In that case you'll need to either find a way to fill these gaps and/or use a different dataset.  However, it may be that something else is going on with your forcing data and/or simulation.  Regardless of the issue, you'll want to diagnose exactly what the problem is first (if and where the missing/fill values are in the *LDASIN* files, if there are missing/fill values in the source data that you are using, etc.).  

As a side note, the regridding packages are provided as examples for how to generate meteorological forcing data in the proper format for WRF-Hydro.  Each source dataset (ones we provide examples for and otherwise) has its own history, attributes, limitations, etc.  Regardless of how forcing files are generated, it's important to understand these source datasets and how WRF-Hydro is using forcing data.  We do our best to keep these packages updated and documented, but there can be changes to source datasets, dataset availability, etc. and our ability to support these is limited (that said, the hope is that through this forum more experienced users and developers might be able to point folks in the right direction).  

Hope this helps.