WRF-Hydro Run Error

[Dani]

Dear All,

I am currently trying to run a new setup for the WRF-Hydro model. However, I keep receiving the same error and I am unsure as to the cause of it. Though I speculate it's related to my routing stack files since I couldn't make a raster layer out the Fulldom_hires.nc and the model stopped running when it started reading the said file. Still I'm unsure since this is the first time I've ever encountered this error as opposed to my previous model setup runs. Also, I don't know if it has something to do with the way I setup my domain (Geogrid files), but I set it up with the following options:

parent_grid_ratio = 1, 3, 3, 3, 3,

dx = 9000,

dy =  9000, 

I used the 4th domain, which is at approximately 333m. Then I used this domain for my routing grids as well with the following options:

input geogrid = geo_em.d04.nc

regridding (nest) factor = 5

Number of routing grid cells to define stream = 100

I've also attached the log file during my run.

If you have any suggestions or any idea as to the cause of the error, please let me know.

Gratefully yours,

Dani

[dhanraj]

Hi Dani

I am trying to run WRF-Hydro model for a new setup. I also got the same error as yours. Fulldom_hires.nc file looks fine.

Options I setup are as follows

parent_grid_ratio = 1, 4

dx = 12000,

dy =  12000, 

I used the 2nd domain, which is at 3000m. Then I used this domain for my routing grids as well with the following options:

input geogrid = geo_em.d02.nc

regridding (nest) factor = 10

Number of routing grid cells to define stream = 50

If you have any idea about how to resolve the error and why it showing this error, please let me know.

Regards,

Dhanraj

[Danica loqueloque]

Hi Dhanraj,

In my case, I changed my set up in such a way that the nested grids are in whole numbers. However, it also turned out that my met forcing was not formatted correctly according to the WRF-Hydro model specifications. In this case, I included the "RAINRATE" variable even with my supplied precipitation input. I also removed all the .nc extensions of my met forcing. 

In your case, you might want to consider checking your inputs to make sure they are formatted correctly. If that doesn't work, then maybe you could look into changing the setup of your domain? Maybe you could try nesting your domain to 1,2,2. Essentially, this will result in the same resolution that you have at 3-km grid resolution. Then you could try to run the geo_em.d03.nc in ArcGIS to get the high-resolution routing grids. After that, you could try running the model again, hopefully without errors. 

Best of luck,

Dani

Best of luck,

Dani

--
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/e12dee2d-4eeb-467a-88f7-5feacb523e3d%40ucar.edu.

[Katelyn FitzGerald]

If the model is failing on the Fulldom_hires.nc read, you might also check the routing grid resolution and aggregation factor settings in the hydro.namelist.  It's easy to overlook these when switching between domains.  

In your case it sounds like they should be the following:

! Specify the grid spacing of the terrain routing grid...(meters) DXRT = 300.0 ! Specify the integer multiple between the land model grid and the terrain routing grid...(integer) AGGFACTRT = 10

[dhanraj]

Thank You, Dani and Katelyn for your reply.

Routing grid resolution and aggregation factor settings in the hydro.namelist are 300 and 10. The error comes after the output of the 1-day of model run.

When I run the regridding script I got the output with warnings as follows.

warning:VarVarWrite: Dimension names for dimension number (0) don't match, assigning name of rhs dimension to lhs, use "(/../)" if this change is not desired

warning:["Execute.c":8637]:Execute: Error occurred at or near line 123 in file GLDAS2WRFHydro_regrid.ncl

Is this warning is related to the error in the model run? If yes then how to overcome it?

Regards,

Dhanraj

On Saturday, January 5, 2019 at 6:33:16 PM UTC+5:30, Dani wrote:

[Katelyn FitzGerald]

The warnings from the regridding scripts shouldn't be an issue.  These have to do with overwriting variable metadata and the script(s) could be updated to avoid these warnings, but it won't impact the outputs.

If the simulation ran successfully for a day prior to failing, it's likely something different from what Dani was running into.  

If you have the log files (standard error / output + diag.0000) from a simulation that used a binary / executable compiled with the environment variable for logging diagnostic information turned on (HYDRO_D = 1) those might be helpful for troubleshooting.  I'd suggest maybe opening a new post with more information (e.g. code version, log files, namelists).  

Best,

Katelyn

[dhanraj]

Thanks for the reply, 

I think the error is due to forcing data.

I am attaching diag_hydro.00000 content as follows.

t0OutputFlag:            1

 read forcing data at 2017-05-01_00:00:00./FORCING/2017050103.LDASIN_DOMAIN1

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

 input of SHDFAC with LAI

         258           1 SHDFAC=   0.00000000     VAI=   0.00000000     TV=   290.000000     TG=  -214.897888

 LWDN=  -9999.00000     FIRA=   9816.32617     SNOWH=   0.00000000

 FATAL ERROR: STOP in Noah-MP

Hope, I am able to explain the problem correctly.

Regards,

Dhanraj

On Saturday, January 5, 2019 at 6:33:16 PM UTC+5:30, Dani wrote:

[Katelyn FitzGerald]

Yeah, this error is likely because the source GLDAS dataset contains missing values over water that have propagated through to your forcing files.  You'll want to fill these missing values prior to running WRF-Hydro.