geoschem/GCHP

How to run a GCHP simulation without Chemistry (only emission)?

Closed this issue · 2 comments

herizonarivelo commented

Name: Herizo Narivelo
Institution: Observatoire du Midi-Pyrénées - Laboratoire d'Aérologie (LA UMR 5560) - Université Toulouse III Paul Sabatier (France)

Confirm you have reviewed the following documentation

Dear all,
I am a newcomer to using the GCHP model. I used the GCHP v14.2.2 version for my study. My project is to work on a long simulation (several years) with c48 horizontal resolution but before doing these simulation, I am doing a simulation test in order to choose the well start date of my simulation. To do this, I have tried to disable/deactivate the chemistry in the configuration file (setCommonRunSettings.sh), but I seem to be taking a long time with my simulation. For one month period of simulation, it has taken approximately 1 hour of time to complete the run.
Some time ago, a simulation carried out with the previous version of Geos-chem took a few hours to complete simulation over a long period.
For the simulation with take account only the emission, I had set false the fields Chemistry, advection, Cloud, PBL_Mixing, Non_Local_Mixing, DryDep and WetDep in the "setCommonRunSettings.sh" and also set photolysis to false in geoschem_config.yml.
Is there anything I should set to false/comment in a configuration file other than the one I have set to false in setCommonRunSettings.sh?

I have attached my setCommonRunSettings.sh, geoschem_config.yml and GCHP.log for my simulation. It would be great if you could explain my problem for simulation without chemistry which take a long time to complete.

HEMCO_Config.rc.log
setCommonRunSettings.sh.log
geoschem_config.yml.log
gchp.20070701_0000z.log

Best regards,
Herizo

lizziel commented

Hi @herizonarivelo, it looks like you are doing everythinbg right. Could you try a c24 benchmark simulation using 48 cores? You can create the simulation and run without making any edits to the configuration files. The resulting timing can be compared to our benchmark run for 14.2 to see if they are comparable. It should take about 8 hours (see here).

lizziel commented

@herizonarivelo, were you able to resolve this issue?