Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ParameterUnitsDescription
nIter01

Index of the first iteration.  If these variables are set to nonzero values, the model will look for a ''pickup'' file pickup.0000nIter0 to restart the integration.

nTimeSteps1Number of time steps that you want the MITgcm simulation to run.

deltaTClock

sThe model ''clock'' timestep.  This determines the IO frequencies and is used in tagging output.
deltaTmomsTimestep for momentum equations.  This can be set to the same value as deltaTclock.
deltaTtracersTimestep for tracer equations.  This can be set to the same value as deltaTclock.
deltaTfreesurf
sTimestep for free surface equations.  This can be set to the same value as deltaTclock.

pChkptFreq

s

Control the output frequency (in seconds) of permanent checkpoint files.  See MITgcm manual section 1.5.1.

chkptFreq

sControl the output frequency (in seconds) of rolling checkpoint files.  See MITgcm manual section 1.5.1.
taveFreqs

Controls the frequency (in seconds) of saving time-averaged diagnostic quantities.

dumpFreqsControls the frequency (in seconds) with which the instantaneous state of the model is saved.
monitorFreqs

Sets the the interval between diagnostics written out to the text stdout stream (i.e. to the terminal or the files STDOUT.*). It supplies statistics on model variables (max,mean,etc.) and also checks the CFL values. It can be quite expensive and so should not be done every time-step but perhaps every 10-50 timesteps.

   

data.debug_run

The data.debug_run file is used to submit a 10-hour MITgcm simulation.  The time stepping settings are as follows.

...

As you can see, we set the basic timestep (deltaTclock) to 3600 seconds = 1 hour, and then run for 10 timesteps = 10 hours total.  Diagnostics (taveFreq, dumpFreq, monitorFreq) are saved out at the end of the run (after 360000 seconds). 

...

Submitting a MITgcm debugging run

To submit a 10-hour debugging run (on 13 CPUs), type the following commands:

Code Block
#### To run a 10-hr debug Hg simulation #######
cd MITgcm_code/                         # Switch to main code directory
setcpus 13 hg   
                       # Pcks the proper SIZE.h and data.exch2 file for 13 CPUs
cd verification/global_hg_llc90/run     # Change to the Hg run directory
sbatch run.mitgcm.13np.1month           # SubmitSets the runproper todata SLURMand data.exch ####files; Tosubmits runjob
a
debug #### 10-hr debug PFOS simulation #######
cd MITgcm_code/                         # Switch to main code directory
setcpus 13 pfos               
         # Picks the proper SIZE.h and data.exch2 file for 13 CPUs
cd verification/pfos/run                # Change to the HgPFOS run directory
sbatch run.mitgcm.13np.1month           # SubmitSets the proper data runand to SLURM

#### To run adata.exch files; submits job

#### 10-hr debug PCB simulation #######
cd MITgcm_code/                         # Switch to main code directory
setcpus 13 pcb      cd verification/pfos/run                # Change to the PCB run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

Submitting a MITgcm 1-month run

To submit a 1-month MITgcm run (on 13 CPUs), type the following commands:

Code Block
#### 1-month Hg simulation ###
cd MITgcm_code/                         # Switch to main code directory
cd verification/global_hg_llc90/run     # Change to the Hg run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

#### 1-month PFOS simulation ###
cd MITgcm_code/                         # Switch to main code directory
cd verification/pfos/run                # Change to the PFOS run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

#### 1-month PCB simulation ###
cd MITgcm_code/                         # Switch to main code directory
cd verification/pfos/run                # Change to the PCB run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

 

Submitting a MITgcm 20 year run

To submit a 20-year MITgcm simulation (on 96 CPUs), type the following commands:

Code Block
#### To run a debug Hg simulation ###
cd MITgcm_code/                         # Switch to main code directory
cd verification/global_hg_llc90/run     # Change to the Hg run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

#### To run a debug PFOS simulation ###
cd MITgcm_code/                         # Switch to main code directory
cd verification/pfos/run                # Change to the PFOS run directory
sbatch run.mitgcm.13np.1month           # Sets the proper data and data.exch files; submits job

#### To run a debug PCB simulation ###
cd MITgcm_code/                    # Picks the proper SIZE.h and# data.exch2Switch fileto formain 13code CPUsdirectory
cd verification/pfospcb/run                 # Change to the HgPCB run directory
sbatch run.mitgcm.13np96np.1month20yr             # SubmitSets the run to SLURM

 

Submitting a MITgcm 1-month run

Hello

Submitting a MITgcm 20 year run

...

proper data and data.exch files; submits job

 

Other runs

Previous | Up | Next

...