GEOS-5

Running the GEOS-5 SBU Benchmark: Difference between revisions

← Older edit
→Benchmark Run: Edit for new portable BCs
 
(4 intermediate revisions by the same user not shown)
Line 106: Line 106:
These effectively let you change whatever you want - useful for debugging, etc. For example, you can set your timers in ~/.esma_base.mk.
These effectively let you change whatever you want - useful for debugging, etc. For example, you can set your timers in ~/.esma_base.mk.


-->


==Test Build with One-Day Run==
==Test Build with One-Day Run==
Line 112: Line 111:
To make sure all works, we will first try setting up a simple one-day experiment.
To make sure all works, we will first try setting up a simple one-day experiment.


===Learn to love tcsh===
One preliminary note is that GEOS-5 is, in many ways, a collection of csh/tcsh scripts. If things start going wrong, the answer can often be "change your shell to tcsh and try". Yes, it's not bash/fish/zsh, but it is what it is. I don't think it's entirely necessary for just this automated work, but it could happen.


===Setting up a one-day experiment===
===Setting up a one-day experiment===
Line 255: Line 251:


At this point, you should be able to <tt>sbatch gcm_run.j</tt> and the model should run a day.
At this point, you should be able to <tt>sbatch gcm_run.j</tt> and the model should run a day.
-->


==Benchmark Run==
==Benchmark Run==


The full benchmark run is a run of 5-days using a portable version of the GEOS-5 boundary conditions. This will use space and cores. For effective benchmarking of I/O, it's recommended to run on less congested than nobackup.
The full benchmark run is a run of 5-days using a portable version of the GEOS-5 boundary conditions. This will use space and cores. For effective benchmarking of I/O, it's recommended to run on less congested than nobackup.
===Learn to love tcsh===
One preliminary note is that GEOS-5 is, in many ways, a collection of csh/tcsh scripts. If things start going wrong, the answer can often be "change your shell to tcsh and try". Yes, it's not bash/fish/zsh, but it is what it is. I don't think it's entirely necessary for just this automated work, but it could happen.


===Setting up benchmark experiment===
===Setting up benchmark experiment===
Line 274: Line 276:
To create the experiment, run create_expt.py and choose a C720 horizontal resolution with climatological GOCART:
To create the experiment, run create_expt.py and choose a C720 horizontal resolution with climatological GOCART:


  $ $PORTBCS/scripts/create_expt.py benchmark-GEOSadas-5_16-5-5day-c720-Portable --horz c720 --ocean o3 --gocart C --account <ACCOUNTID> --expdir <root-for-experiment>
  $ $PORTBCS/scripts/create_expt.py benchmark-GEOSadas-5_16-5-5day-c720 --horz c720 --ocean o3 --gocart C --account <ACCOUNTID> --expdir <root-for-experiment>
  Found c720 horizontal resolution in experiment name
  Found c720 horizontal resolution in experiment name
  Using c720 horizontal resolution
  Using c720 horizontal resolution
Line 287: Line 289:
   Running gcm_setup...done.
   Running gcm_setup...done.
   
   
  Experiment is located in directory: <root-for-experiment>/benchmark-GEOSadas-5_16-5-5day-c720-OpsHistory
  Experiment is located in directory: <root-for-experiment>/benchmark-GEOSadas-5_16-5-5day-c720


Again, if you don't pass in an account-id, you'll get the default of g0620 (the developer's account).
Again, if you don't pass in an account-id, you'll get the default of g0620 (the developer's account).
Retrieved from "https://geos5.org/wiki/index.php?title=Running_the_GEOS-5_SBU_Benchmark"