Difference between revisions of "Frequently asked questions about GEOS-Chem"

From Geos-chem
Jump to: navigation, search
(Can I run two GEOS-Chem jobs simultaneously?)
(Where can I get restart files for GEOS-Chem?)
 
(20 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
=== For new users ===
 
=== For new users ===
  
* [[GEOS-Chem welcome letter for new users|I am a GEOS-Chem new user.  What is expected of me?]]
+
* [https://geos-chem.seas.harvard.edu/geos-welcome I am a GEOS-Chem new user.  What is expected of me?]
* [[Minimum system requirements for GEOS-Chem|On what types of machines can I run GEOS-Chem?]]
+
* [https://geos-chem.readthedocs.io/en/latest/geos-chem-shared-docs/supplemental-guides/related-docs.html Where can I find user manuals for GEOS-Chem and related software?]
 
* [http://cloud.geos-chem.org Can I use GEOS-Chem on cloud-computing platforms?]
 
* [http://cloud.geos-chem.org Can I use GEOS-Chem on cloud-computing platforms?]
 
* [[Species in GEOS-Chem|What types of simulations can I run with GEOS-Chem?]]
 
* [[Species in GEOS-Chem|What types of simulations can I run with GEOS-Chem?]]
Line 12: Line 12:
 
* [[Overview of GMAO met data products|Which meteorological data fields can be used by GEOS-Chem?]]
 
* [[Overview of GMAO met data products|Which meteorological data fields can be used by GEOS-Chem?]]
 
* [[Submitting GEOS-Chem support requests|To whom can I direct GEOS-Chem-related questions?]]
 
* [[Submitting GEOS-Chem support requests|To whom can I direct GEOS-Chem-related questions?]]
* [http://acmg.seas.harvard.edu/geos/geos_steering_cmte.html What does the GEOS-Chem Steering Committee do?]
+
* [https://geos-chem.seas.harvard.edu/geos-steering-cmte What does the GEOS-Chem Steering Committee do?]
* [http://acmg.seas.harvard.edu/geos/geos_working_groups.html What do the GEOS-Chem Working Groups do?]
+
* [https://geos-chem.seas.harvard.edu/geos-working-groups What do the GEOS-Chem Working Groups do?]
 
* [[GEOS-Chem Support Team|What does the GEOS-Chem Support Team do?]]
 
* [[GEOS-Chem Support Team|What does the GEOS-Chem Support Team do?]]
 
* [[Subscribing_to_the_GEOS-Chem_email_lists|I see that there are several GEOS-Chem email lists.  How can I subscribe?]]
 
* [[Subscribing_to_the_GEOS-Chem_email_lists|I see that there are several GEOS-Chem email lists.  How can I subscribe?]]
 
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:45, 2 January 2019 (UTC)
 
  
 
=== Science questions ===
 
=== Science questions ===
Line 42: Line 40:
 
* [[Using Git with GEOS-Chem#Downloading a new GEOS-Chem version|How do I download the GEOS-Chem source code and run directories?]]
 
* [[Using Git with GEOS-Chem#Downloading a new GEOS-Chem version|How do I download the GEOS-Chem source code and run directories?]]
 
* [[Common GEOS-Chem error messages|What should I do when I encounter an error while running GEOS-Chem]]?
 
* [[Common GEOS-Chem error messages|What should I do when I encounter an error while running GEOS-Chem]]?
* Do you have any information about [[GEOS-Chem performance]] and [[GEOS-Chem_performance#GEOS-Chem_scalability|GEOS-Chem Scalability]]?
+
* Do you have any information about [[Guide to GEOS-Chem performance|GEOS-Chem performance]] and [[GEOS-Chem scalability]]?
 
* [[GEOS-Chem Makefile Structure|Where can I learn more about the GEOS-Chem Makefiles?]]
 
* [[GEOS-Chem Makefile Structure|Where can I learn more about the GEOS-Chem Makefiles?]]
* [[Bugs and fixes|Is there a comprehensive list of GEOS-Chem bugs and how they were fixed?]]
+
* [https://github.com/geoschem/geos-chem/issues Is there a comprehensive list of GEOS-Chem bug reports?]
* [[GEOS-Chem basics|I am new to programming.  Do you have any online resources or tutorials?]]
+
* Do you have any information on how I can [https://geos-chem.readthedocs.io/en/latest/geos-chem-shared-docs/supplemental-guides/debug-guide.html debug GEOS-Chem or HEMCO errors]?
* Are there any [[Floating point math issues|numerical issues]] that I should be aware of?
+
* Do you have any tools that would help me [[Debugging with the GEOS-Chem unit tester|debug GEOS-Chem more efficiently?]]
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:45, 2 January 2019 (UTC)
+
  
 
=== Parallelization issues ===
 
=== Parallelization issues ===
Line 56: Line 50:
 
* [[Parallelizing_GEOS-Chem#Why_is_GEOS-Chem_is_not_using_all_the_CPUs_I_requested.3F|Why is GEOS-Chem not using all the CPUs that I requested?]]
 
* [[Parallelizing_GEOS-Chem#Why_is_GEOS-Chem_is_not_using_all_the_CPUs_I_requested.3F|Why is GEOS-Chem not using all the CPUs that I requested?]]
  
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:45, 2 January 2019 (UTC)
+
=== High-Performance GEOS-Chem (GCHP) ===
  
=== GEOS-Chem HP ("high-performance") ===
+
Please see the GCHP user manual at [https://gchp.readthedocs.io <tt>gchp.readthedocs.io</tt>]for more information.
 
+
* [[GEOS-Chem HP|What is GEOS-Chem HP?]]
+
* [[GEOS-Chem_HP_Description|Can you give me an overview of GEOS-Chem HP?]]
+
* [[GEOS-Chem_HP_Software|What are the hardware and software requirements for GEOS-Chem HP?]]
+
* [[GEOS-Chem HP Dev Kit|How may I download the GEOS-Chem HP code and run directories?]]
+
* [[GEOS-Chem_HP_Compiling|How do I compile GEOS-Chem HP?]]
+
* [[GEOS-Chem_HP_Running|How do I run GEOS-Chem HP?]]
+
* [[GEOS-Chem_HP_PandE|Have users found any problems with GEOS-Chem HP?]]
+
 
+
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:41, 2 January 2019 (UTC)
+
  
 
== Where can I get restart files for GEOS-Chem? ==
 
== Where can I get restart files for GEOS-Chem? ==
  
For instructions on how to obtain a set of sample restart files that you can use to spin up your own simulations, please see [[GEOS-Chem_basics#Restart_files|the ''Restart Files'' section of our ''GEOS-Chem basics'' wiki page]].
+
For instructions on how to obtain a set of sample restart files that you can use to spin up your own simulations, [https://geos-chem.readthedocs.io/en/latest/gcc-guide/04-data/restart-files-gc.html#where-can-i-get-a-restart-file-for-my-simulation please visit this link].
  
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 16:24, 6 January 2017 (UTC)
+
== Running GEOS-Chem ==
  
== Running GEOS-Chem ==
+
Please see our ''[[Running GEOS-Chem]]'' wiki page.
  
 
=== How long does GEOS-Chem take to run? ===
 
=== How long does GEOS-Chem take to run? ===
  
It depends on your particular computing environment.  We have posted several timing results from GEOS-Chem [[GEOS-Chem_performance#7-day_time_tests|7-day time test simulations]].
+
It depends on your particular computing environment.  We have posted several timing results from GEOS-Chem [[GEOS-Chem 7-day timing tests|7-day time test simulations]].
  
 
=== GEOS-Chem seems to be running too slowly.  What can I do? ===
 
=== GEOS-Chem seems to be running too slowly.  What can I do? ===
  
You should be aware of [[GEOS-Chem Makefile Structure#Compile-time options that can slow down GEOS-Chem|several compile-time options that will slow down GEOS-Chem]].  Use these options only for debugging, but not in your production runs.
+
There are several ways to [https://geos-chem.readthedocs.io/en/latest/gcc-guide/05-run/run-speedup.html speed up a slow GEOS-Chem simulation].  
  
 
If you are archiving many diagnostic quantities are a high temporal resolution (e.g. every hour), then this will increase the run time of your simulation.  You can try saving out less diagnostic quantities, or archiving at a lower temporal resolution (e.g. every day).
 
If you are archiving many diagnostic quantities are a high temporal resolution (e.g. every hour), then this will increase the run time of your simulation.  You can try saving out less diagnostic quantities, or archiving at a lower temporal resolution (e.g. every day).
Line 90: Line 74:
 
== GEOS-Chem errors ==
 
== GEOS-Chem errors ==
  
Please also see our [[Common GEOS-Chem error messages]] wiki page.
+
Please also see our ''[[Guide to GEOS-Chem error messages]]'' and ''[https://geos-chem.readthedocs.io/en/latest/geos-chem-shared-docs/supplemental-guides/debug-guide.html Debug GEOS-Chem and HEMCO errors]'' pages.
  
 
=== GEOS-Chem died with an error.  What can I do? ===
 
=== GEOS-Chem died with an error.  What can I do? ===
  
First, you should try to understand the type of error that has occurred.  There are several different classes of errors, such as:
+
Please see ''[[Understanding the different categories of errors]]'' section of our ''[[Guide to GEOS-Chem error messages]]''.
 
+
# [[Common GEOS-Chem error messages#File_I.2FO_errors|File I/O errors]]
+
#* Errors caused by incorrect input options
+
#* Errors caused by missing data files
+
#* Errors caused by corrupted data files
+
#* [[Common GEOS-Chem error messages#Error computing F_OF_PBL|Running GEOS-Chem at the wrong resolution for the data files]]
+
# [[Common GEOS-Chem error messages#Crashes or abnormal exits|Abnormal exits]]
+
#* From the [[KPP solvers FAQ|KPP chemical solver]]
+
#* From the SMVGEAR chemical solver
+
#* From other areas of GEOS-Chem
+
# [[Common GEOS-Chem error messages#General types of errors|Technical errors]]
+
#* [[Common GEOS-Chem error messages#Segmentation faults|Segmentation faults]]
+
#* [[Common_GEOS-Chem_error_messages#Array-out-of-bounds_error|Array-out-of-bounds errors]]
+
#* Out of memory errors
+
 
+
Once you have understood the type of GEOS-Chem error that has occurred, you can take steps to fix it.  In some cases, the fixes will be simple (i.e. selecting the proper option and starting over, or replacing missing or corrupted data files, etc.).  In other cases, the error may be more difficult to diagnose (such as a [[KPP_solvers_FAQ#How_do_I_choose_the_absolute_and_relative_tolerance.3F|convergence error in the chemical solver]]).  In that case you may have to "dig in" to the code so that you can modify its behavior (e.g. modify convergence criteria, add error checks, etc.).
+
 
+
Try to isolate the error to a particular GEOS-Chem routine.  You can use a debugger such as idb or Totalview, or you can turn on the ND70 debug printout option.  (ND70 will print debug messages to the log file after key operations have been completed.)  You may also try turning off operations (e.g. wet deposition, dry deposition, chemistry) one at a time in the <tt>input.geos</tt> file to isolate the error. Once you know where the error is occurring, try to print out values for a given grid box and tracer, either in the debugger or by adding PRINT statements to the code. You will gain great insight into what is happening by using this technique.
+
 
+
Try to determine if the error is persistent (i.e. if it always occurs at the same model time/date or if it occurs at different times and dates in the simulation).  A persistent error could indicate a missing or corrupted data file, or a flaw in the scientific algorithm being used.  Non-persistent errors (i.e. those that don't happen at the same model time and date) may indicate memory errors, such as array-out-of-bounds, segmentation faults, or that the code is using more memory than is available.
+
 
+
If you still cannot determine the error from the traceback output, recompile with the <tt>BOUNDS=yes</tt> compiler option.  This will check to see if an array is being accessed incorrectly
+
 
+
Please see our [[Common GEOS-Chem error messages|Common GEOS-Chem errors wiki page]], which contains strategies for recognizing and fixing several commonly-encountered error conditions.  If you still cannot determine the source of your error, please [[Submitting GEOS-Chem support requests|contact the GEOS-Chem Support Team for assistance]].
+
 
+
=== Where does GEOS-Chem error output get printed? ===
+
 
+
GEOS-Chem, like all Unix programs, sends its output to two streams:
+
 
+
# stdout
+
# stderr
+
 
+
==== The stdout stream ====
+
 
+
Most GEOS-Chem output will go to the '''stdout''' stream, which takes I/O from the Fortran WRITE and PRINT commands. If you run GEOS-Chem by just typing the executable name at the Unix prompt:
+
 
+
geos
+
 
+
then the stdout stream will be printed to the terminal window.  You can also redirect the stdout stream to a log file with the Unix redirect command:
+
 
+
geos > log
+
 
+
We recommend that you create GEOS-Chem log files so that you can reexamine the output from your run at a later time.
+
 
+
Most GEOS-Chem errors will be printed to stdout (and hence, to the log file).  Most errors flagged by GEOS-Chem use a standard error message format, such as:
+
 
+
==============================================================
+
GEOS-CHEM ERROR: No output scheduled on last day of run!
+
STOP at IS_LAST_DAY_GOOD ("input_mod.f")
+
==============================================================
+
 
+
==== The stderr stream ====
+
 
+
The '''stderr''' stream takes I/O from various Unix system commands, including <tt>exit</tt>.  If your GEOS-Chem run died as a result of a system problem (i.e. you ran up against a system time or memory limit, you are over disk quota, etc.), then the error message will more than likely go to stderr instead of stdout.  As a result, these error messages will not be printed to the GEOS-Chem log file output.
+
 
+
If you use a queue system then the stderr output may be printed to a file.  For example, if you submit a GEOS-Chem job to the SGE queue system, and your job script is named <tt>run.geos</tt>, SGE will send the stderr output to a file named <tt>run.geos.oXXXXX</tt> (where XXXXX is the job ID #).
+
 
+
--[[User:Bmy|Bob Y.]] 15:44, 8 November 2010 (EST)
+

Latest revision as of 19:20, 10 August 2022

On this page we shall answer some commonly asked questions about GEOS-Chem.

Basic information about GEOS-Chem

For new users

Science questions

Where can I find information about ...

--Bob Yantosca (talk) 17:45, 2 January 2019 (UTC)

Technical issues

Parallelization issues

High-Performance GEOS-Chem (GCHP)

Please see the GCHP user manual at gchp.readthedocs.iofor more information.

Where can I get restart files for GEOS-Chem?

For instructions on how to obtain a set of sample restart files that you can use to spin up your own simulations, please visit this link.

Running GEOS-Chem

Please see our Running GEOS-Chem wiki page.

How long does GEOS-Chem take to run?

It depends on your particular computing environment. We have posted several timing results from GEOS-Chem 7-day time test simulations.

GEOS-Chem seems to be running too slowly. What can I do?

There are several ways to speed up a slow GEOS-Chem simulation.

If you are archiving many diagnostic quantities are a high temporal resolution (e.g. every hour), then this will increase the run time of your simulation. You can try saving out less diagnostic quantities, or archiving at a lower temporal resolution (e.g. every day).

GEOS-Chem errors

Please also see our Guide to GEOS-Chem error messages and Debug GEOS-Chem and HEMCO errors pages.

GEOS-Chem died with an error. What can I do?

Please see Understanding the different categories of errors section of our Guide to GEOS-Chem error messages.