Getting Started

The PRISM activities are organised around five PRISM areas of expertise (PAEs). Anyone interested in contributing to these networks of experts is welcome and should get in touch with the PAE contacts listed on the PAE page.

To get started directly with the different PRISM tools described on the Software page, one can follow the procedures described here:

The OASIS3 coupler, the PRISM Standard Compiling Environment and the PRISM Standard Running Environment

The OASIS4 coupler

Integration and Modelling Tools

 


The OASIS3 coupler, the PRISM Standard Compiling Environment and the PRISM Standard Running Environment

The best way to find out about these tools is to download, compile and run the PRISM toy coupled model, TOYCLIM. This will give you a practical experience with the OASIS3 coupler, the Standard Compiling Environment (SCE), and the Standard Running Environment (SRE). The TOYCLIM coupled model is composed of 3 "toy'' component models, mimicking an atmosphere model (toyatm), an ocean model (toyoce), and a chemistry model (toyche). These "toy'' component models are "empty" in the sense that they do not model any real physics or dynamics. However, the coupled combination of these 3 "toy'' component models through OASIS3 coupling software is realistic as the coupling algorithm linking the toy component models, the size and the grid of the 2D coupling fields, and the operations performed by OASIS3 on the coupling fields are realistic. The TOYCLIM coupled model uses the PRISM SCE and SRE.

More information can be found:

 

To download, compile and run the PRISM toy coupled model, TOYCLIM, you have to:

  • Compile OASIS3 and TOYCLIM component models, toyatm, toyoce, toyche, using the PRISM Standard Compiling Environment (for more details, see section 8.1 of OASIS3 documentation and SCE documentation PDF Document):
    1. Go into the directory prism/util/compile/frames

    2. Create the include files for your platform if they do not already exist in directory prism/util/compile/frames/include_<node> where <node> is the name of the platform. The platforms currently included are:


    3. Vendor/Hardware name

      OS / Architechture NodeName Institute
      i686 / Linux / armc28  Environnement Canada
      Cray    baltic1  
      SGI /  IRIX64 /  MIPS dcm13 SGI, Munich
      SGI /  IRIX64 / MIPS dcm23  SGI, Munich
      SGI / Altix 3000 IA64SGI /  dcm25 SGI, Munich
      SGI / IRIX64 / MIPS elnino CERFACS, Toulouse
      IBM /  AIX / Power4 hpca ECMWF, Reading
      NEC / SX-6 SUPER-UX / SX ds DKRZ, Hamburg
      NEC / SX-6 SUPER-UX / SX mercure IPSL, Paris
      SGI / Origin 3800  IRIX64 / MIPS p1 KNMI, De Bilt
      Fujitsu / HPCline Linux / Opteron Cluster total1 F.S.E.  Toulouse 
      Fujitsu / VPP5000  UXPV / VPP xbar Meteo France, Toulouse


    4. Generate a compile scrip for OASIS3 and for each of the component models using the script Create_COMP_cpl_models.ksh:
    5. prompt> Create_COMP_cpl_models.ksh toyclim "ID" "node" "mp"

      The argument "ID" (optional) gives a tag/version/experiment ID, if desired; the argument "node" gives the node name of compile server (needed if different from the node name of the platform on which the script is executed) ; the parameter "mp" specifies the message passing used, which determines how the models are launched (MPI2 or MPI1).

    6. The scripts to compile OASIS3 and the 3 toy component models can now be launched explicitly in their respective directory:
      • COMP_oasis3_<mp>.<node> in directory prism/src/mod/oasis3
      • COMP_toyatm_<ID>.<node> in directory prism/src/mod/toyatm
      • COMP_toyoce_<ID>.<node> in directory prism/src/mod/toyoce
      • COMP_toyche_<ID>.<node> in directory prism/src/mod/toyche

    The result should be executables "oasis3.<mp>.x", "toyatm.<mp>.x", "toyoce.<mp>.x", and "toyche.<mp>.x" in the prism/bin directory.

    1. Go to the directory prism/util/running/frames

    2. Create the include files for your platform if they do not already exist in directory prism/util/running/frames/include_<node>, where <node> is the name of the platform. See above for the platform currently included.

    3. Run the script Create_TASKS.frm to generate a setup file for your TOYCLIM experiment:
    4. prompt> Create_TASKS.frm toyclim <expid>

      where <expid> is your experiment name.

    5. The TOYCLIM default configuration of the experiment can be modified (see section 8.2 of OASIS3 documentation PDF Document). To simply run with the default set-up, run the script Create_TASKS.frm toyclim a second time:
    6. prompt> Create_TASKS.frm toyclim <expid>

    7. Once the setup is done, all appropriate files and the script to start the experiment are available in the directory prism/experiment/<expid>. Go into the directory prism/experiment/<expid>/scripts and submit the runscript RUN_toyclim_<expid>.

    Running TOYCLIM with the default parameters will result in a 30-day experiment executed as five 6-day runs. The final results obtained in the directory prism/experiment/<expid>/work should match the ones in prism/data/toyclim/outdata. Intermediate results are also saved in different sub-directories in prism/experiment/<expid>.

     

The OASIS4 coupler

The OASIS4 coupler is the new fully parallel coupler developed in the PRISM framework. Currently, the community of OASIS4 users is officially restricted to the GEMS community (3D coupling between atmosphere and atmospheric chemistry models), to SMHI (regional coupling), and to IFM-GEOMAR (using OASIS4 with pseudo models to interpolate high resolution data onto high resolution model grids). After the current testing period, OASIS4 will be released to a larger community.

 

Integration and Modelling Tools

There is a collection of software including specific tools for individual model development such as for job configuration, compilation, running and monitoring jobs, and corporate infrastructure tools, which comprise a complete web services system for multiple user environments. See details on the PAE environments page.



If you are interested in any software, or have any questions or feedback, please get in touch by emailing us at


 

[ Top ]

Site Hits: