Re: [wrf-hydro_users] Digest for wrf-hydro_users@ucar.edu - 3 updates in 2 topics

[Yongxin Zhang]

Hi Martin,

     I will take a look at your regridding scripts to make sure that the regridding is correct but I still could not access your Google Drive folders. I just sent a request to you for access to the folders.

Thanks,

Yongxin

On Thu, Jun 26, 2025 at 5:13 AM <wrf-hyd...@ucar.edu> wrote:

wrf-hyd...@ucar.edu

Google Groups

Topic digest
View all topics

• Request for Help with “Problems finding dimension 'west_east'” Error in WRF-Hydro - 2 Updates
• Upside down & unknown projection/CRS & large-value backwater of streamflow in CHRTOUT_GRID1 output - 1 Update

Request for Help with “Problems finding dimension 'west_east'” Error in WRF-Hydro

Fatemeh Shirkhanloo <fate...@pdx.edu>: Jun 25 04:57PM -0700 Dear WRF-Hydro Team,   I hope you are doing well.   I am trying to run WRF-Hydro in offline mode for a test case I recreated based on the Croton example. However, I am facing the following error when running the model: *NetCDF: Not a valid ID ***** READ_HRLDAS_HDRINFO: Problems finding dimension 'west_east'*     I have double-checked my forcing files (LDASIN), domain files (geo_em.d01.nc and Fulldom_hires.nc), and namelists, and everything seems correct in terms of dimensions and structure. The LDASIN files include south_north, west_east, Time, and other expected variables. The geo grid also seems fine.   Despite this, the model crashes with this error.   I would appreciate your guidance on how to troubleshoot it.   Best regards, Fatemeh

Arezoo RafieeiNasab <are...@ucar.edu>: Jun 25 07:14PM -0700 Hi Fatemeh,   Most of the time this error suggests one of the files in the namelists is not pointing to the right file or right path. Could you please double check the paths in the namelists?   Thanks! Arezoo   On Wed, Jun 25, 2025 at 4:57 PM Fatemeh Shirkhanloo <fate...@pdx.edu> wrote:     -- Arezoo Rafieei Nasab, Ph.D. NCAR/RAL Project Scientist II

Back to top

Upside down & unknown projection/CRS & large-value backwater of streamflow in CHRTOUT_GRID1 output

Martin Nguyen <martinng...@gmail.com>: Jun 26 10:13AM +1200 Hi Aubrey,   Thank you very much for your email. As the files are large to be attached, I have shared all the necessary files to run a simulation i <https://drive.google.com/drive/folders/1rKtDJ61PD9rPOJLvl49I4-Xp52iRKnan?usp=sharing>n vers_002_consistentsetup <https://drive.google.com/drive/folders/1rKtDJ61PD9rPOJLvl49I4-Xp52iRKnan?usp=sharing>. I also converted the LDASIN back to the original form which is the WRF model output and provided the "before-after" regridding results. I also provided the errors (results) I got when running simulation with this version under 'Errors_of_running_simulation'. Please note that I did not include the forecast points (csv) in this simulation version, but I attached it anyway, just in case.   Please let me know if you cannot access to the folder I shared.   Building Routing stack: <python Build_Routing_Stack.py -i C:\Users\mng42\wrf_wps\example_nz_040_mataura\geo_em.d01.nc -b False -r True -d C:\Users\mng42\wrf_wps\example_nz_040_mataura\mataura_4326.tif -R 4 -t 2000 -o C:\Users\mng42\wrf_wps\example_nz_040_mataura\output\mataura_test_001.zip>   Kind regards   Martin Nguyen

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to wrf-hydro_use...@ucar.edu.

[Martin Nguyen]

Hi Yongxin,

Thank you very much for your email. I have just granted the access to the shared folder. Please let me know if you can still not access it.

Kind regards

Martin Nguyen

--
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 visit https://groups.google.com/a/ucar.edu/d/msgid/wrf-hydro_users/CAEA-d79qYCeWtx0uEk6EioFiyxLDuabygtE-0DY%3DSKuuHc3gJQ%40mail.gmail.com.

[Yongxin Zhang]

Hi Martin,

     Thanks for granting me access to your folder. I will take a look at the scripts and will let you know if I have any suggestions.

Thanks,

Yongxin

[Martin Nguyen]

Hi Yongxin,

Thank you very much for your follow-up email.

Kind regards

Martin Nguyen

--

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 visit https://groups.google.com/a/ucar.edu/d/msgid/wrf-hydro_users/CAEA-d7999iMDuZvoQgQ-x%2B%2BXEEuVgYNGpKT6A6xdv4Wsz3vWTg%40mail.gmail.com.

[Yongxin Zhang]

Hi Martin,

     I checked your WRF files before and after regridding and also your scripts for creating the weight file and for doing the regridded. I don't see any issues with the script for creating the weight file but I do have a few issues/concerns regarding the precipitation variable names and units in the script for doing the regridding. My concerns are:

1) variable name: The standard WRF output generally has two variables for precipitation, RAINC (convective precipitation; convective cloud scheme is generally not turned on when spatial resolution is high) and RAINNC (not-convective or grid-scale precipitation; cloud microphysics scheme is generally not turned on when spatial resolution is coarse) so the total precipitation should be the sum of two, RAINC + RAINNC. I noticed that your script regridded and output them separately although in your case RAINC was zero everywhere.

2) hourly vs. accumulated values: In WRF output, RAINC and RAINNC are accumulated values from the start of model initialization while in WRF-Hydro we use hourly precipitation values (or customized frequency depending on the input files). To get the hourly precipitation, we can simply make the difference between the current hour and the previous hour. Your script does not consider this so the precipitation values are all accumulated values. 

3) In WRF-Hydro, the standard precipitation name is "RAINRATE" in units of mm/s (we can also use "precip" in units of mm in the case for supplemental precipitation files). This is hard-coded in the model unless you have changed the precipitation name to either RAINC or RAINNC in the model code. If you have not changed the precipitation name in the model code, your model run won't have any precipitation.

4) As I mentioned in 3), the unit of precipitation in WRF-Hydro is mm/s which can be obtained by dividing the hourly precipitation by 3600. I don't see this dividing in your script.

      I can make changes in your script to accomodate all these but I will need to know if you have already changed the model code to use RAINC/RAINNC and accumulated values.

Thanks!

Yongxin

[Martin Nguyen]

Hi Yongxin,

Thank you so much for your reply. I really appreciate it.

I think I did not change any model code (WRF-Hydro code) to use RAINC/RAINNC and accumulated values as I did not do anything relating to this. I changed the WRF-Hydro code to read the name from "wrfout_d0{x}_YYYY-MM-DD_HH:MM:SS" to "wrfout_d0{x}_YYYY-MM-DD_HH_MM_SS" and then recompile. The other relevant thing I did was to state the "Forcing input variable names" and forcing type "FORC_TYP = 3"  in namelist.hrldas as below (you can check again in vers_002_consistentsetup). 

For the regridding, I just followed as the example included here with selection "WRF* (not for Windows machine" without changing anything. As I checked, the outputs from the example and what I have were the same. They all include GLW, LAI, lat, lon, PSFC, Q2, RAINC, RAINNC, SWDOWN, T2, Time, U10, V10, and VEGRFA. Hence, I thought I was on the right track but I am not so sure about this.

So I think I did not change any code. And yea please help me with the script to accomodate all those points you mentioned.

Thank you very much.

Kind regards

Martin Nguyen

NAMELIST.HRLDAS #################################################

! Forcing input variable names

forcing_name_T = "T2"

forcing_name_Q = "Q2"

forcing_name_U = "U10"

forcing_name_V = "V10"

forcing_name_P = "PSFC"

forcing_name_LW = "GLW"

forcing_name_SW = "SWDOWN"

forcing_name_PR = "RAINNC"

/

&WRF_HYDRO_OFFLINE

! Specification of forcing data:  1=HRLDAS-hr format, 2=HRLDAS-min format, 3=WRF,

!    4=Idealized, 5=Idealized w/ spec. precip.,

!    6=HRLDAS-hr format w/ spec. precip., 7=WRF w/ spec. precip.,

!    9=Channel-only forcing, see hydro.namelist output_channelBucket_influxes

!    10=Channel+Bucket only forcing, see hydro.namelist output_channelBucket_influxes

FORC_TYP = 3

#################################################

[Yongxin Zhang]

Hi Martin,

     Many thanks for your reply. I think that now I understand what you were doing. I will do some tests and will try to figure out whether or not we will need to make any changes in the regridding script. 

Thanks,

Yongxin

[Martin Nguyen]

Hi Yongxin,

Thank you very much for your follow-up email.

Kind regards

Martin Nguyen

[aubrey]

Hi Martin:

Just another reminder that you cannot simply change the wrfout filenames to LDASIN filenames and switch FORC_TYP options. The WRF read option is expecting an accumulated precip while the LDASIN read option is expecting a precip rate or depth over the timestep.

Thanks!

Aubrey

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

--
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_users+unsubscribe@ucar.edu.

[Martin Nguyen]

Hi Aubrey,

Thank you very much for your email. In the vers_002_consistentsetup, I already changed the name back to the WRF output format ("wrfout_d01_2020-02-01_00_00_00", I also changed ":" to "_" and recompile) and used FORC_TYP=3 (I no longer changed the name to LDASIN and used FORC_TYP=1 anymore). However, as I said before, the WRF-Hydro (version 0.5.4) on my side cannot run this type. I have added the "errors_when_using_WRFoutput_as_FORCING" in that shared folder and attached the run.log here for reference.

Please let me know if you need further information.

Kind regards

Martin Nguyen

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

--
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.