WRF v4 pre-processors, wrfchemi_causing troubles

726 views
Skip to first unread message

rohan kumar

unread,
Mar 29, 2021, 10:14:52 AM3/29/21
to wrf-chem
Hi,

I am using WRF-chem 4.1.2, but while running the wrf.exe, I am getting the following error. 

 Error trying to read metadata
File name that is causing troubles = wrfchemi_d01_2012-06-01_00:00:00
 You can try 1) ensure that the input file was created with WRF v4 pre-processors, or
 2) use force_use_old_data=T in the time_control record of the namelist.input file
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     332
 ---- ERROR: The input file appears to be from a pre-v4 version of WRF initialization routines
-------------------------------------------


I am attaching the namelist and error log.

I would be grateful for your help as I am struggling with this since last week. Thank you

Best Regards
Rohan Kumar
log.txt
namelist.txt

Alexander Frie

unread,
Mar 29, 2021, 10:22:03 AM3/29/21
to rohank...@gmail.com, wrf-chem
Hello Rohan,

The error suggests your input data was not sourced from the most recent version of WPS.  Adding the "force_use_old_data=T" to the nmaelist, or using a more updated version of WPS should solve your issue.

Cheers,

Alex

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


--
_________________________
Alexander Frie, PhD
Postdoctoral Associate
Department of Soil, Water, and Climate
University of Minnesota

rohan kumar

unread,
Mar 29, 2021, 10:34:01 AM3/29/21
to wrf-chem, frie...@umn.edu, wrf-chem, rohan kumar

Hello Alex,

Thanks for the prompt reply.  I am using WPS4.1  and also tried  "force_use_old_data=T", but it failed with the following error.

Error trying to read metadata
 Input data is acceptable to use: wrfchemi_d01_2012-06-01_00:00:00
 Input data is acceptable to use: wrfbdy_d01
Timing for processing lateral boundary for domain        1:    0.04962 elapsed seconds
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS =   2
 Tile Strategy is not specified. Assuming 1D-Y
WRF TILE   1 IS      1 IE     52 JS      1 JE     30
WRF TILE   2 IS      1 IE     52 JS     31 JE     59
WRF NUMBER OF TILES =   2
Timing for processing lateral boundary for domain        1:    0.04267 elapsed seconds
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS =   2
 Tile Strategy is not specified. Assuming 1D-Y
WRF TILE   1 IS      1 IE     52 JS      1 JE     30
WRF TILE   2 IS      1 IE     52 JS     31 JE     59
WRF NUMBER OF TILES =   2
forrtl: severe (174): SIGSEGV, segmentation fault occurred

I have used the ulimit option but failed again.  The error is around the wrfchemi file, but I am kind of blank about it. Any suggestion will be helpful. Thanks

Regards
Rohan Kumar

Paul Goddard

unread,
Mar 29, 2021, 10:39:49 AM3/29/21
to frie...@umn.edu, rohank...@gmail.com, wrf-chem
Hi Rohan and Alex,

I just want to comment that I am also having the same issue as Rohan  with WRF-chem.  Here is a link to my Forum post:  https://forum.wrfforum.com/viewtopic.php?f=6&t=11825&sid=250b82cf7a8e3452db7a298899517410

I am going to post an update with more details.  I have been troubleshooting for a couple weeks.  I am quite sure I am using the most up-to-date preprocessors and I am now using the geostatic data v4 (I was using v3).   And like Rohan, I cannot execute the run without switching the namelist option to "force_use_old_data=.true."   -- even though I can run real.exe with "force_use_old_data=.false"

I'll pass along the link to my post to the forum later today, if a working solution does not come of this post.

Cheers,
Paul

rohan kumar

unread,
Mar 29, 2021, 11:08:13 AM3/29/21
to wrf-chem, godd...@gmail.com, rohan kumar, wrf-chem, frie...@umn.edu
Hi Paul,

Thanks, I will also try to troubleshoot. Any update would be useful.

Best Regards
Rohan Kumar 

Paul Goddard

unread,
Mar 29, 2021, 12:56:08 PM3/29/21
to rohan kumar, wrf-chem, frie...@umn.edu
Reply all
Reply to author
Forward
0 new messages