search

geoschem / geos-chem

GEOS-Chem "Science Codebase" repository. Contains GEOS-Chem science routines, run directory generation scripts, and interface code. This repository is used as a submodule within the GCClassic and GCHP wrappers, as well as in other modeling contexts (external ESMs).
http://geos-chem.org
Other
167 stars 162 forks source link

Typo in v14.4.1 default setCommonRunSettings.rc, MassFlux_Entry variable #2498

Open andrew-scott-white opened 2 weeks ago

andrew-scott-white commented 2 weeks ago

Your name

Andrew Scott White

Your affiliation

MIT

What happened? What did you expect to happen?

When attempting to run a stretched grid simulation in GCHP v14.4.1, I encountered the following message: "ERROR: Do not use stretched grid when using mass flux inputs. Create a winds run directory for stretched grid simulations." I was not using mass fluxes. It seems the MassFlux_Entry flag is mislabeled when called in the first if statement after the grep "MFXC" ExtData.rc. The variable should be ${MassFlux_Entry} not ${MassFluxEntry}, as shown by my cursor in the attached image. When this typo is corrected, I no longer receive the error.

What are the steps to reproduce the bug?

I encountered this bug when running a stretched grid simulation using full chemistry, standard simulation, MERRA-2. Specifically, it is a c48 grid with stretch factor 2, lat/lon of 40.0/264.0, and default HEMCO/ExtData files.

Please attach any relevant configuration and log files.

setCommonRunSettingsError

What GEOS-Chem version were you using?

14.4.1

What environment were you running GEOS-Chem on?

Local cluster

What compiler and version were you using?

gcc 7.3.1

Will you be addressing this bug yourself?

No

In what configuration were you running GEOS-Chem?

GCHP

What simulation were you running?

Full chemistry

As what resolution were you running GEOS-Chem?

c48

What meterology fields did you use?

MERRA-2

Additional information

No response

yantosca commented 2 weeks ago

Thanks for writing @andrew-scott-white. This was fixed in PR #2363, which went into 14.4.2.