Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

[SOLVED] CALWRF for WRF 4.6?

anelito

New member
Hi,

which version of CALWRF should be used to convert the WRF outputs from WRF 4.6 into useful inputs for CALMET?

I tested the linux version of CALWRF_v2.0.1 and CALWRF_v2.0.3.

I am attaching my inp and lst file as well as the link to my wrfout file:

Thanks in advance,
A
 
Last edited:
Would you please clarify what us calmet? Also, I don't think we have the utility to convert wrfout file as inout for calmet.
 
My WRF-4.6 outputs are already read by CALWRF. Checking our wrfout files with ncdump we saw that truelat2 and stand_lon had values of 1e20!!! The problem is that we made our namelist.wps with www.wrfdomainwizard.net with the MERCATOR projection and since this projection does not use these two parameters, it excludes them from the namelist. Well, we included them, we ran WRF with these parameters in the namelist and CALWRF can now read our wrfout files.

Thanks,
 
My WRF-4.6 outputs are already read by CALWRF. Checking our wrfout files with ncdump we saw that truelat2 and stand_lon had values of 1e20!!! The problem is that we made our namelist.wps with www.wrfdomainwizard.net with the MERCATOR projection and since this projection does not use these two parameters, it excludes them from the namelist. Well, we included them, we ran WRF with these parameters in the namelist and CALWRF can now read our wrfout files.

Thanks,
Hi there - I'm seeing a similar issue for wrfouts that are LCC where calwrf ends immediately stating that "This is not a wrfout file" after "Processing GLOBAL ATTRIBUTES". Did you need to recompile calwrf, or are you using the provided binary?
 
Hi there - I'm seeing a similar issue for wrfouts that are LCC where calwrf ends immediately stating that "This is not a wrfout file" after "Processing GLOBAL ATTRIBUTES". Did you need to recompile calwrf, or are you using the provided binary?
Hi,
I don't get that error. I used the provided binary for windows and a recompiled for linux that a colleague shared with me. I don't know how he recompiled it for Linux.
Both for version CALWRF_v2.0.3
 
I found the issue. There was a check in the calwrf.f code to evaluate the WRF output header. With my output being a newer version than the header check was aware of, I commented out these lines, recompiled, and it seems to work now.

Code:
      if(INDEX(value_chr,'OUTPUT FROM WRF V2') == 0)then
         if(INDEX(value_chr,'OUTPUT FROM WRF V3') == 0)then
            !! diagnostics only available for wrfout data
            print*,"This is not a wrfout file "
            print*,"No 3D.DAT will be created"
            stop
         endif
      endif
 
I found the issue. There was a check in the calwrf.f code to evaluate the WRF output header. With my output being a newer version than the header check was aware of, I commented out these lines, recompiled, and it seems to work now.

Code:
      if(INDEX(value_chr,'OUTPUT FROM WRF V2') == 0)then
         if(INDEX(value_chr,'OUTPUT FROM WRF V3') == 0)then
            !! diagnostics only available for wrfout data
            print*,"This is not a wrfout file "
            print*,"No 3D.DAT will be created"
            stop
         endif
      endif
Please, What is your OS? Linux or windows? What is your CALWRF version? Which FORTRAN are you using for recompile?
 
Top