Git Product home page Git Product logo

fms-idealized's Introduction

                              === Idealized GCMs ===

General structure:

                                   fms_default_public
                                          |
                      ------------------------------------------
                      |                   |                    |
                 idealized               exp                analysis
                      |                   |                    |    
             (DO NOT MODIFY src)          |            
                                          |
                   ----------------------------------------------
                   |                      |                     | 
                 exp1                   exp2                  exp3...
                                          |
           ------------------------------------------------------------------
           |                              |                                 |
         input                           run                             srcmods
           |                              |                                 |
   namelists, diag table             run_scripts         put here any modification to the source code;
                                                       it will automatically replace any sources in src

Experiments (exp1, exp2 ...) may differ by source code, and all modifications to the source code are located in the srcmods directory within the specific experiment. Once in that directory they overwrite any source code in the model directory (e.g. ~/fms_default_public/idealized/src/). Every experiment can have several runs, which share the same source code. Runs typically differ in namelist parameters.

Once an experiment is run, two more directories will be created on the level of fms_default_public:

1. fms_tmp: A temporary directory where the experiment will run and computations will be executed. All model output will be automatically exported to fms_output once the experiment is done. Note that for speed some of the computation uses a local /scratch on the compute nodes. Unless a job is resubmitted immediately, this directory can be deleted once the run is over. For future restarts, a restart file archive (.cpio) is copied to fms_output. 

2. fms_output: Contains three directories:
2.1. history: 4xday and 1x10days output of the model (output frequency and diagnostics can be adjusted at exp?/input/diag_table).
2.2. logfiles: logfiles from each output stage.
2.3. restart: restart files for each output stage.

General instructions for setting up an experiment (adjustments for specific computer configurations will be needed).

1. cd ~/fms_default_public/exp
2. Create a duplicate directory of the default experiments. e.g.: cp -rp default_idealized test_moist_1.
3. Copy any modifications to the source code into the srcmods directory of the new experiment.
4. Adjust if needed any namelists or diag_tables in the run or input directories within the new experiment tree.
5. Make sure the correct mkmf file for your specific compiler is used (e.g. ~/fms_default_public/idealized/bin/mkmf.template.ifc). For mppnccombine, which combines output files from separate processors, a GNU C++ (gcc) compiler is used.
6. Submit job with the script in the exp?/run/ directory (e.g. qsub < run_test)

The directory tree analysis contains code for computing various kinds of averages (isentropic, sigma coordinate, etc.) of flow fields simulated in an experiment.

Farid Ait Chaalal, Ian Eisenman, Yohai Kaspi, Xavier Levine, Tim Merlis, April 2011--October 2012




fms-idealized's People

Contributors

rcjwills avatar tapios avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.