Re: Bug in mozbc Execution

41 views
Skip to first unread message

Mary Barth

unread,
Sep 29, 2024, 8:07:08 PM9/29/24
to Gao, Da, wrf-chem-mozbc, acomdi...@ucar.edu, Wang, Jian
Hello Da,

First, I would like to remind you that there is a Google email group for wrf-chem-mozbc questions. I have cc'd that group. It is very important to send your questions to this email group so that more experts can help answer it. 

Second, I am not aware of mozbc not being able to process data with longitude > 300 deg. If others are, then I hope to hear from them. 
In the meantime, it would be good to share the mozbc namelist with the group to confirm that you have set up the tool correctly. 

Thanks!
Mary

^--^--^--^--^--^--^--^--^--^--^--^--^--^--^-^--^--^--^-^--^
Mary Barth 
Senior Scientist   
phone: 303-497-8186    email: bar...@ucar.edu

NSF - National Center for Atmospheric Research
P.O. Box 3000
Boulder, CO 80307

^--^--^--^--^--^--^--^--^--^--^--^--^--^--^-^--^--^--^-^--^



On Sat, Sep 28, 2024 at 2:04 PM Gao, Da <d...@wustl.edu> wrote:
Dear Professor,


I encountered an issue while running mozbc to provide initial and boundary conditions for WRF-Chem. It appears that WACCM data can only be processed within the longitude range of 0 to 300 degrees. When the longitude exceeds 300 degrees, the program crashes with the following error message:


forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source             
mozbc              000000000044C1A4  for__signal_handl     Unknown  Unknown
libpthread-2.17.s  00007FAEDC7995D0  Unknown               Unknown  Unknown
mozbc              000000000042125B  Unknown               Unknown  Unknown
mozbc              0000000000439964  Unknown               Unknown  Unknown
mozbc              00000000004097DE  Unknown               Unknown  Unknown
libc-2.17.so       00007FAEDC3DF3D5  __libc_start_main     Unknown  Unknown
mozbc              00000000004096E9  Unknown               Unknown  Unknown



Could you please confirm whether this is a known bug in mozbc, or if I might have made a mistake in my setup? Any guidance on how to resolve this issue would be greatly appreciated.



Thank you for your assistance.


Best,


Da Gao

Reply all
Reply to author
Forward
0 new messages