The nested simulation aborts abnormally on the first day of operation.

[lxy616161]

Your name

lxy

Your affiliation

UCAS

What happened? What did you expect to happen?

Hello！
When running the CO₂ nested simulation, it aborted abnormally at the data reading stage on Day 1, with no error messages shown in the log file. It appears to terminate unexpectedly when reading the RH variable, and I am unable to troubleshoot and resolve this issue on my own. I sincerely request your technical assistance and would be very grateful for your help. Thank you!

What are the steps to reproduce the bug?

I intended to perform the CO₂ simulation starting from June 2020. First, I configured the global and nested simulations for this period according to the user manual, and obtained the background condition data by running the global simulation. However, the above issue occurred when I ran the nested simulation.

Please attach any relevant configuration and log files.

GC.log
geoschem_config.yml
HEMCO_Config.txt

What GEOS-Chem version were you using?

14.6.3

What environment were you running GEOS-Chem on?

Personal computer

What compiler and version were you using?

gcc 10.2.0

Will you be addressing this bug yourself?

Yes, but I will need some help

In what configuration were you running GEOS-Chem?

GCClassic

What simulation were you running?

Carbon

As what resolution were you running GEOS-Chem?

0.25×0.3125

What meterology fields did you use?

GEOS-FP

Additional information

No response

[yantosca]

Thanks for writing @lxy616161. I am wondering if you ran out of memory in your simulation. You mentioned that you are using a personal computer. Do you know how much memory is available? Even though you are using the GEOS-Chem CO2 simulation, at very high resolution you could still potentially exceed the memory available on the system.

[yantosca]

You can also try the following commands to see if the system killed your job. One of these might yield some information.

$ dmesg | grep -i "killed process"
$ dmesg | grep -i "out of memory"
$ journalctl -k | grep -i "oom"
$ journalctl -k | grep -i "killed process"
$ grep -i "out of memory" /var/log/messages
$ grep -i "oom" /var/log/syslog