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

DATA CANNOT BE WRITTEN INTO WRFOUT

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

J

jalter

New member
when I change source code to output the data of the source of qsnow ,everything goes fine .
the data has been written into wrfout file . I can draw the source of qsnow
when I change code to output the source of qice ,qcloud,qhail,qgraupel just like qsnow, everything goes fine ,too
./compile and ./real.exe are successful
however , ./wrf.exe has come to wrong .


rsl.error.0000 shows that
D01 3-D analysis nudging for wind is applied and Guv= 0.3000E-03
D01 3-D analysis nudging for temperature is applied and Gt= 0.3000E-03
D01 3-D analysis nudging for water vapor mixing ratio is applied and Gq= 0.3000E-03
D01 3-D analysis nudging for temperature is turned off within the PBL.
D01 3-D analysis nudging for water vapor mixing ratio is turned off within the PBL.
D01 surface analysis nudging for wind is applied and Guv_sfc= 0.3000E-03
D01 surface analysis nudging for temperature is applied and Gt_sfc= 0.3000E-03
D01 surface analysis nudging for water vapor mixing ratio is applied and Gq_sfc= 0..3000E-03
open_hist_w : error opening wrfout_d01_2017-06-07_00:00:00 for writing. ***
Timing for Writing wrfout_d01_2017-06-07_00:00:00 for domain 1: 17.35052 elapsed seconds
d01 2017-06-07_00:00:00 Input data processed for aux input 9 for domain 1
d01 2017-06-07_00:00:00 Input data processed for aux input 10 for domain 1
Timing for processing lateral boundary for domain 1: 0.82887 elapsed seconds
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 69 JS 1 JE 40
WRF NUMBER OF TILES = 1
D01 3-D analysis nudging reads new data at time = 0.000 min.
D01 3-D analysis nudging bracketing times = 0.00 360.00 min.
D01 surface analysis nudging reads new data at time = 0.000 min.
D01 surface analysis nudging bracketing times = 0.00 360.00 min.
open_hist_w : error opening wrfout_d02_2017-06-07_00:00:00 for writing. ***
Timing for Writing wrfout_d02_2017-06-07_00:00:00 for domain 2: 17.05588 elapsed seconds
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 69 JS 1 JE 40
WRF NUMBER OF TILES = 1


why the wrfout cannot be written?

the place where the code I changed has note "edit"
View attachment module_microphysics_driver.FView attachment module_mp_milbrandt2mom.FView attachment Registry.EM_COMMON.txtView attachment solve_em.F
 
Hi...

It is possible this is a non-WRF problem.

Check the following:

(1) You aren't over your quota in space or number of files. On most systems, the "quota"
command will tell you this.

(2) The filesystem you are writing too isn't full.

(3) You have write permission on the directory you are writing too.

(4) Make sure the filenames don't already exist, but don't have write permission.

You can try setting "debug_level" in "namelist.input" to a large number, such as "9999" and
see if something more useful is provided.

Also make sure your WRF compiles supports 64-bit NETCDF files.
 
I set debug_level to 9999 ,then rsl.error.0000 shows that
Timing for wrf_ext_write_field: 0.00277 elapsed seconds
d01 2017-06-07_00:00:00 output_wrf: end, fid = 1
d01 2017-06-07_00:00:00 back from outsub in open_w_dataset
d01 2017-06-07_00:00:00 calling wrf_open_for_write_commit in open_w_dataset
d01 2017-06-07_00:00:00 module_io.F: in wrf_open_for_write_commit
d01 2017-06-07_00:00:00 Information: NOFILL being set for writing to wrfout_d01_2017-06-07_00:00:00
d01 2017-06-07_00:00:00 NetCDF error: NetCDF: One or more variable sizes violate format constraints
d01 2017-06-07_00:00:00 NetCDF error in ext_ncd_open_for_write_commit wrf_io.F90, line 1481
d01 2017-06-07_00:00:00 back from wrf_open_for_write_commit in open_w_dataset
open_hist_w : error opening wrfout_d01_2017-06-07_00:00:00 for writing. ***
d01 2017-06-07_00:00:00 output_wrf: begin, fid = 1
d01 2017-06-07_00:00:00 module_io.F: in wrf_inquire_filename
d01 2017-06-07_00:00:00 output_wrf: fid,filestate = 1 101
d01 2017-06-07_00:00:00 output_wrf: dryrun = T
d01 2017-06-07_00:00:00 OUTPUT_WRF: mminlu = USGS
d01 2017-06-07_00:00:00 DEBUG wrf_timetoa(): returning with str = [2017-06-07_00:00:00]


what does it mean ?
 
Please rebuild WRF in debug mode, i.e., ./configure -D (remember to do ./clean -a before rebuilding), then rerun the case. You can set debug_level = 0 because with the debug mode, the RSL file would tell exactly at which line in which module the code failed. That will give you helpful information to further investigate the issue.
 
Hi...

A few other things to check:

o Make sure the directory is writable.
o Make sure the file is writable, if it exists.
o Make sure you aren't over your disk quota.
o Make sure the filesystem isn't full.
 
You must log in or register to reply here.
Top