Changes between Version 9 and Version 10 of WikiStart


Ignore:
Timestamp:
2008-03-11T10:25:20Z (17 years ago)
Author:
Dave Offiler
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v9 v10  
    33This is the feature request, issue and bug tracking web site for the '''Radio Occultation Processing Package''' (ROPP).
    44ROPP is a sofware package designed to assist NWP users to assimilate radio occultation data from any RO mission such as
    5 CHAMP, COSMIC or GRAS. The package is being developed through the EUMETSAT '''GRAS SAF'''.
     5GRAS, COSMIC, CHAMP or GRACE-A. The package is being developed through the EUMETSAT '''GRAS SAF'''.
    66
    77The ROPP deliverable source code is sub-divided into '''modules''':
    8  * ropp_tools : low-level utility routines
    9  * ropp_io    : I/O support for RO data in plain text, netCDF and BUFR files
    10  * ropp_pp    : pre-processor (e.g. to derive refractivity profiles from bending angle profiles)
    11  * ropp_qc    : quality control routines
    12  * ropp_fm    : forward models (and associated tangent linear, adjoint & gradient code)
    13  * ropp_1dvar : 1D-Var retrieval & minimiser
    14  * ropp_test  : test harness
    15 Not all of these modules have been implemented for the first release (ROPP-1), but will be added for later releases.
    16 
    17 In addition there are ROPP areas for documentation, external web page content and a comprehensive Test Folder suite.
     8 * '''ropp_tools''' : low-level utility routines
     9 * '''ropp_io'''    : I/O support for RO data in netCDF and BUFR files
     10 * '''ropp_pp'''    : pre-processor (e.g. to derive refractivity profiles from bending angle profiles)
     11 * '''ropp_qc'''    : quality control routines
     12 * '''ropp_fm'''    : forward models (and associated tangent linear, adjoint & gradient code)
     13 * '''ropp_1dvar''' : 1D-Var retrieval & minimiser
     14Collectively, these modules are knowns as '''ropp_src'''. Not all of these modules have been implemented for the first release (ROPP-1), but will be added for later releases.
    1815
    1916== The ROPP Repository ==
    2017
     18The whole ROPP development system is divided into three areas:
     19 * '''ropp_src'''   : deliverable code & supporting development system
     20 * '''ropp_doc'''   : user and project documentation
     21 * '''ropp_test'''  : Test Folder (test system and its results)
     22 
    2123The repository for ROPP can be accessed via the Subversion server at the URL
    2224{{{
    23 svn://fcm7/ROPP_svn/...
     25https://svn.grassaf.org/ropp/
    2426}}}
    2527For example, checking out the latest development (trunk) versions:
    2628{{{
    27 svn co svn://fcm7/ROPP_svn/ropp_src/trunk ropp_src
    28 svn co svn://fcm7/ROPP_svn/ropp_doc/trunk ropp_doc
    29 svn co svn://fcm7/ROPP_svn/ropp_web/trunk ropp_web
    30 svn co svn://fcm7/ROPP_svn/ropp_test/trunk ropp_test
     29svn co https://svn.grassaf.org/ropp/ropp_src/trunk .
     30svn co https://svn.grassaf.org/ropp/ropp_doc/trunk .
     31svn co https://svn.grassaf.org/ropp/ropp_test/trunk .
    3132}}}
    32 will check out the source code, documentation, web presentation, and test folder, respectively.
    33 
    34 With FCM (see below), the above checkout commands would be somewhat simpler:
    35 {{{
    36 fcm co fcm:ropp_src_tr ropp_src
    37 fcm co fcm:ropp_doc_tr ropp_doc
    38 fcm co fcm:ropp_web_tr ropp_web
    39 fcm co fcm:ropp_test_tr ropp_test
    40 }}}
    41 
     33will check out the source code, documentation, and test folder, respectively to the local working directory.
    4234
    4335== Branches ==
    4436
    45 It is recommended that developments to ROPP are conducted and committed to a ''branch'' rather than directly to the latest trunk version.
    46 This allows for changes to be tested before merging the required changes back into the trunk. The trunk therefore represents the 'next release' state for ROPP.
    47 See http://www-nwp/~fcm/FCM/doc/user_guide/working_practices.html#branching for useful guidance on when, where and how to make developments in a branch.
     37It is recommended that developments to ROPP are made from, and committed to, a ''branch'' rather than directly to the latest trunk version. This allows changes to be tested before merging the required changes back into the trunk. The trunk therefore represents a stable 'next potential release' state for ROPP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.
    4838
    4939To create a branch of ropp_src from the trunk use the command:
    … …  
    6454if using a private user branch.
    6555
    66 When all the changes you require to your branch have been committed and the ROPP development team are satisfied that it will be part of the next release, these changes will be merged back into the trunk by using merge. To do this, you must first change directory to your working copy of the trunk (create one using checkout if you don't already have it). Then enter the following:
     56When all the changes you require to your branch have been committed and the ROPP Development Team are satisfied that it will be part of the next release, these changes will be merged back into the trunk by using merge. To do this, you must first change directory to your working copy of the trunk (create one using checkout if you don't already have it). Then enter the following:
    6757{{{
    6858cd ${HOME}/FCM/ropp_src
    … …  
    8272When you do this, you should see the list of updates that have been made to the trunk since you last brought in any changes (or since you branched). Again, this only results in changes to your working copy so you might want to commit them.
    8373
    84 == FCM ==
    85  
    86 ROPP uses FCM only for code management; the build part is based on GNU's autotools since the package is designed
    87 to be portable and independent of any particular code management system.
    88 
    89 The advantages of using FCM is a simpler front-end to Subversion commands (see the checkout examples above),
    90 and also the availability graphical diff and merge utilities (but noting that latest versions of TkCVS also supports SVN).
    91 
    92 In order to support ROPP, the following abbreviations/keywords are implemented within the central FCM configuration:
    93 {{{
    94 set::repos::ropp_doc         svn://fcm7/ROPP_svn/ropp_doc
    95 set::repos::ropp_doc_tr      svn://fcm7/ROPP_svn/ropp_doc/trunk
    96 set::repos::ropp_doc_br      svn://fcm7/ROPP_svn/ropp_doc/branches
    97 set::repos::ropp_doc_tg      svn://fcm7/ROPP_svn/ropp_doc/tags
    98 set::repos::ropp_src         svn://fcm7/ROPP_svn/ropp_src
    99 set::repos::ropp_src_tr      svn://fcm7/ROPP_svn/ropp_src/trunk
    100 set::repos::ropp_src_br      svn://fcm7/ROPP_svn/ropp_src/branches
    101 set::repos::ropp_src_tg      svn://fcm7/ROPP_svn/ropp_src/tags
    102 set::repos::ropp_test        svn://fcm7/ROPP_svn/ropp_test
    103 set::repos::ropp_test_tr     svn://fcm7/ROPP_svn/ropp_test/trunk
    104 set::repos::ropp_test_br     svn://fcm7/ROPP_svn/ropp_test/branches
    105 set::repos::ropp_test_tg     svn://fcm7/ROPP_svn/ropp_test/tags
    106 set::repos::ropp_web         svn://fcm7/ROPP_svn/ropp_web
    107 set::repos::ropp_web_tr      svn://fcm7/ROPP_svn/ropp_web/trunk
    108 set::repos::ropp_web_br      svn://fcm7/ROPP_svn/ropp_web/branches
    109 set::repos::ropp_web_tg      svn://fcm7/ROPP_svn/ropp_web/tags
    110 
    111 set::trac::ropp_doc          http://fcm7/projects/ROPP/browser/ropp_doc
    112 set::trac::ropp_src          http://fcm7/projects/ROPP/browser/ropp_src
    113 set::trac::ropp_test         http://fcm7/projects/ROPP/browser/ropp_test
    114 set::trac::ropp_web          http://fcm7/projects/ROPP/browser/ropp_web
    115 }}}
    116 (See the FCM configuration file at ~fcm/FCM/work/FCM/src/etc/fcm.cfg)