Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.

To run GEM one needs appropriate executables (also called "absolutes") as well as a set of scripts and configuration files.
You will find some examples at the end of this page.

Volet
borderWidth5
You need to follow all of the instructions below! You cannot skip any parts!
I strongly suggest to use copy->paste!!! There are dots and spaces that are easy to miss when typing the commands by hand.


Sommaire

Initial setup

1) Set up SSM environment

...

For GEM 4.8.lts12 set:
    version='v_4.8.lts12.u'
For GEM 5.0 set:
    version='v_5.0-u1.rc1'
For GEM 5.1.1 set:
    version='v_5.1.1-u1'

Create a directory for all your extra or modified model scripts with:

    mkdir -p ~/modeles/GEMDM/${version}/bin

For now copy all scripts from my directory into yours, for example with:

    cp -p ~winger/modeles/GEMDM/${version}/bin_latest_version/* ~/modeles/GEMDM/${version}/bin

You are done now with the general model setup.

Ancre
config_files
config_files
The configuration files

...

You can do this by executing one of the following aliases, depending on the model version you want to run:

      4812      # for GEM 4.8.lts12
      500        # for GEM 5.0
      511        # for GEM 5.1.1

Among others, these commands also sets the environment variables $gemdyn and $rpnphy which contain the directory name under which you can find all models dynamic resp. physics routines

...

  1. Go into your config directory (the directory in which you have your config files - see above).

  2. Launch the model with one of the following two commands:

    a)  Um_lance

    This is the basic way to submit the model. It can be used when running the model on our UQAM server as well as for short (one job) simulations on clusters of The Alliance. If your simulation consists of more than one month the model will run one job per month. At the end of each month/job the next month will get submitted automatically => which can lead to multiple long queued times on clusters of The Alliance.
    If you are using the little example config files from above you should use 'Um_lance' to submit the example simulation.

    b)  Chunk_lance

    To avoid extra queued times 'Chunk_lance' will execute as many months as it can in the given wall time of the job (BACKEND_time_mod). At the end of each job the next job will get submitted automatically. While 'Chunk_lance' can be used for all types of simulations it is especially useful for longer simulations.

    If the model crashes and you want to resubmit it to continue the simulation, all you have to do is go back into you config file directory, set the model environment, and execute 'Chunk_lance' again.

    If ever you want to restart a simulation from the very beginning, you can do so by executing:

          Chunk_lance  -start

    You can find more information about Chunk_lance on our wiki by clicking 'here'.

...

To check if your simulation is running use the command:
            qs

If ever you need to kill a simulation you can do that with:

    qdel JobID

You can find more information on the following wiki:
   Batch jobs
   Check on batch jobs

...