Changes between Initial Version and Version 1 of FpCtbtoOverview


Ignore:
Timestamp:
Mar 27, 2015, 5:20:54 PM (9 years ago)
Author:
dearn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FpCtbtoOverview

    v1 v1  
     1
     2== CTBTO Project Wiki Page ==
     3
     4=== Update: 2015-03-18 ===
     5
     6This project is carried out in collaboration by the following partners:
     7
     8 * Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO)
     9 * Geophysical Institute at the University of Alaska Fairbanks (UAF)  ([http://www.gi.alaska.edu/])
     10 * Zentralanstalt für Meteorologie und Geodynamik (ZAMG) ([http://www.zamg.ac.at/]), Vienna
     11 * Angewandte Wissenschaft Software und Technologie (AWST) GmbH ([http://www.awst.at/]), also in Vienna
     12
     13The '''aim''' of the project is to''' enhance the FLEXPART modeling system for CTBTO operations''', and to contribute the enhancements into the mainstream FLEXPART distribution for the benefit of others.  This should enable CTBTO to benefit from new science and techniques used in future FLEXPART versions, while insuring that their own enhancements remain part of the distribution.
     14
     15The scope of the project includes the following functionality areas:
     16
     17 1. Allow GRIB input data to be pre-processed before FLEXPART runs
     18 2. Allow reading of both NCEP and ECMWF GRIB files using the same executable
     19 3. Allow dynamic allocation of simulation grid and particles
     20 4. Add configuration option for outputting same units in backward runs as in forward runs
     21 5. Support reading ECMWF GRIB files in various sub-formats
     22 6. Add Makefiles for ifort
     23
     24Work is currently ongoing on the second functionality-area above. More specifically, this entails:
     25
     26 * Unifying the GRIB reading routines in FLEXPART so that one executable may use either NCEP or ECMWF met files.
     27 * Building a simple, initial regression testing system by which modifications to FLEXPART can be validated for consistency in output and performance
     28 * Setting up a private developmental repository and ticketing system for the project in a way that developmental releases (a CTBTO-developmental branch) can be made accessible to the mainstream flexpart.eu community for evaluation and integration into the main branch
     29 * Planning and providing a presentation on the project  at the FLEXPART Developers meeting to be held in Vienna during EGU week.
     30
     31Updates on the project will be described in this public wikipage and will also be introduced in the ticketing system for easy follow up from FLEXPART developers and the community.
     32
     33
     34
     35
     36