ERROR of reading emissions

[Xin Zhang]

 

Dear everyone,

I have made anthropogenic emissions and they were stored in four files:

wrfchemi_00z_d01
wrfchemi_12z_d01
wrfchemi_00z_d02
wrfchemi_12z_d02

Each of them consists of 12 hours' data which is one hour by one hour.

After running wrf.exe, I got this error:

Timing for Writing wrfout_d01_2016-07-27_18:00:00 for domain        1:    1.62784 elapsed seconds
 mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2016-07-27_18:00:00
 mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_d01_2016-07-27_18:00:00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:    2429
 med_read_wrf_chem_emissions: error opening wrfchemi_d01_2016-07-27_18:00:00

But, other people's error file is like this:

Timing for Writing wrfout_d01_2012-11-20_12:00:00 for domain        1:  196.50317 elapsed seconds
 mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_12z_d01
 HOURLY EMISSIONS UPDATE TIME        0.0       0.0
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2012-11-20_12:00:00

How can I fix this error?

Here are some parts of my namelist.input:

 io_form_auxinput5                   = 2,
 frames_per_auxinput5                = 1, 1,
 auxinput5_interval_m                = 60, 60,
 io_form_auxinput6                   = 2,
 frames_per_auxinput6                = 1, 1,
 auxinput6_inname                    = 'wrfbiochemi_d<domain>',
 io_form_auxinput7                   = 2,
 frames_per_auxinput7                = 1, 1,
 auxinput7_inname                    = 'wrffirechemi_d<domain>_<date>',
 auxinput7_interval_m                = 60, 60,

Thanks!

Xin

[Rajesh Kumar]

Hi Xin,

 

Is your io_style_emissions set to 2? If yes, set it to 1 and try again. Also, change frames_per_auxinput to 12. 

Rajesh

[Xin Zhang]

Thank you! Rajesh!

I have two questions:

1. 'io_style_emissions = 2' means that two 12-h emissions data files used. Is this applied to all emissions like biogenic emissions and biomass burning emissions? Or just anthropogenic emissions?

2. What's the meaning of 'frames_per_auxinput = 12'? I can't find explanation User's Guide.

Thank you very much!

XIn

--
You received this message because you are subscribed to the Google Groups "wrf-chem-anthro_emiss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wrf-chem-anthro_emiss+unsub...@ucar.edu.

[Rajesh Kumar]

Xin,

io_style_emissions = 1 means that that two 12-h emissions data files used. It applies only to anthropogenic emissions. The two 12-h emissions files are wrfchemi_00z_d01 and wrfchemi_12z_d01 you created using anthro_emis. 

frames_per_auxinput = 12 mens there are 12 hours of data in wrfchemi_00z_d01 and wrfchemi_12z_d01 files. 

Rajesh

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

[Xin Zhang]

Hi Rajesh,

It works, but I get this error:

Timing for Writing wrfout_d01_2016-07-27_18:00:00 for domain        1:    1.76786 elapsed seconds

 mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_12z_d01
 HOURLY EMISSIONS UPDATE TIME        0.0       0.0

mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2016-07-27_18:00:00

mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    1
**WARNING** Time in input file not being checked **WARNING**
mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    2
**WARNING** Time in input file not being checked **WARNING**
mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    3
**WARNING** Time in input file not being checked **WARNING**
mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    4
**WARNING** Time in input file not being checked **WARNING**
mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    5
**WARNING** Time in input file not being checked **WARNING**
mediation_integrate: med_read_wrf_chem_emissions: Skip emissions    6
**WARNING** Time in input file not being checked **WARNING**
**WARNING** Time in input file not being checked **WARNING**
**WARNING** Time in input file not being checked **WARNING**
Timing for processing lateral boundary for domain        1:    0.38465 elapsed seconds
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS =  24
 Tile Strategy is not specified. Assuming 1D-Y
WRF TILE   1 IS      1 IE    151 JS      1 JE      6
WRF TILE   2 IS      1 IE    151 JS      7 JE     11
WRF TILE   3 IS      1 IE    151 JS     12 JE     16
WRF TILE   4 IS      1 IE    151 JS     17 JE     21
WRF TILE   5 IS      1 IE    151 JS     22 JE     26
WRF TILE   6 IS      1 IE    151 JS     27 JE     31
WRF TILE   7 IS      1 IE    151 JS     32 JE     36
WRF TILE   8 IS      1 IE    151 JS     37 JE     41
WRF TILE   9 IS      1 IE    151 JS     42 JE     46
WRF TILE  10 IS      1 IE    151 JS     47 JE     51
WRF TILE  11 IS      1 IE    151 JS     52 JE     56
WRF TILE  12 IS      1 IE    151 JS     57 JE     61
WRF TILE  13 IS      1 IE    151 JS     62 JE     66
WRF TILE  14 IS      1 IE    151 JS     67 JE     71
WRF TILE  15 IS      1 IE    151 JS     72 JE     76
WRF TILE  16 IS      1 IE    151 JS     77 JE     81
WRF TILE  17 IS      1 IE    151 JS     82 JE     86
WRF TILE  18 IS      1 IE    151 JS     87 JE     91
WRF TILE  19 IS      1 IE    151 JS     92 JE     96
WRF TILE  20 IS      1 IE    151 JS     97 JE    101
WRF TILE  21 IS      1 IE    151 JS    102 JE    106
WRF TILE  22 IS      1 IE    151 JS    107 JE    111
WRF TILE  23 IS      1 IE    151 JS    112 JE    116
WRF TILE  24 IS      1 IE    151 JS    117 JE    121
WRF NUMBER OF TILES =  24

Is it related to my wrfchemi_12z_d01?

I attach my namelist.input and wrfchemi_12z_d01 to the e-mail.

Thanks!​

 wrfchemi_12z_d01

​

[Stacy Walters]

Xin,

This is a warning, not an error.  The warning can be ignored.

Stacy

[Xin Zhang]

Hi Stacy,

But the wrf.exe stopped after this warning.

Here's part of other people's rsl.error.0000 file:

Timing for Writing wrfout_d02_2012-11-20_12:00:00 for domain        2:  203.57651 elapsed seconds
 mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_12z_d02

 HOURLY EMISSIONS UPDATE TIME        0.0       0.0
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2012-11-20_12:00:00

**WARNING** Time in input file not being checked **WARNING**

 Tile Strategy is not specified. Assuming 1D-Y

WRF TILE   1 IS      1 IE     17 JS      1 JE     16
WRF NUMBER OF TILES =   1
 photolysis_driver: called for domain             2
Timing for main: time 2012-11-20_12:01:00 on domain   2:  238.24571 elapsed seconds
Timing for main: time 2012-11-20_12:02:00 on domain   2:   19.40930 elapsed seconds
Timing for main: time 2012-11-20_12:03:00 on domain   2:   12.61808 elapsed seconds
Timing for main: time 2012-11-20_12:03:00 on domain   1: 1111.02844 elapsed seconds
Timing for main: time 2012-11-20_12:04:00 on domain   2:   15.68230 elapsed seconds
Timing for main: time 2012-11-20_12:05:00 on domain   2:   13.69848 elapsed seconds


Xin

[ngo...@fimo.edu.vn]

 I got the same your error. Please help me whether you have fixed the error.

Thank you in advance.

[Quỳnh Trang]

Hello, if WRF stops running suddenly without any error like that, it's most likely that your computer runs out of memory, u can check this: 

http://forum.wrfforum.com/viewtopic.php?f=6&t=9834

Trang.

Vào 11:47:59 UTC+9 Thứ Ba, ngày 26 tháng 2 năm 2019, ngo...@fimo.edu.vn đã viết:

[ngo...@fimo.edu.vn]

Hello, Trang.

Thank you for your prompt response. In my opinion, it is not due to out of memory. I found that variable emission (ebu_in_CO) were all zero after I run real.exe. Maybe it is a reason why wrf.exe stopped.

I try to fixed this error, but it didn't work.

[Quỳnh Trang]

Hello Ngoc,

Regarding ebu_in_CO, you should recheck your emission data, you extract Biomass burning emission from fire_emiss tool or Prep_chem tool? According to my experience, the empty variables can not terminate wrf.exe.

Vào Th 3, 26 thg 2, 2019 vào lúc 12:33 <ngo...@fimo.edu.vn> đã viết:

[FIMO] The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

--
You received this message because you are subscribed to the Google Groups "wrf-chem-anthro_emiss" group.

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

[ngo...@fimo.edu.vn]

I checked memory while wrf.exe was running, it reached 38/126G before stopped. So I don't know that out of memory caused by error.

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

[Xin Zhang]

Hi Ngoc,

I can't remember the exact reason related to this error.

According to my experience, wrong wrfinput file or wrong hpc communication will result in this issue.

You should make sure wrfinput and wrfbdy files are correct.

If this issue happens again, you can run wrf.exe without chemistry to check whether it's related to settings of chem part.

If it works without chemistry, you can turn off the anthropogenic emissions with other chemistry settings open, for checking the anthropogenic part.

Regards,

Xin