Changes between Version 5 and Version 6 of WikiStart


Ignore:
Timestamp:
2007-04-02T11:02:44Z (18 years ago)
Author:
David Matthews
Comment:

Restored internal wiki start page

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v5 v6  
    1 = eROPP =
     1= ROPP =
    22
    3 is an external issue and bug tracking web site for the '''Radio Occultation Processing Package (ROPP)'''.
    4 The system allows for browsing through the history of source code, documentation and test folders
    5 for various versions. Tickets for feature requests, bugs or any other issues with ROPP can be
    6 created and tracked. The system is based on Trac.
     3This is the feature request, issue and bug tracking web site for the '''Radio Occultation Processing Package''' (ROPP).
     4ROPP is a sofware package designed to assist NWP users to assimilate radio occultation data from any RO mission such as
     5CHAMP, COSMIC or GRAS. The package is being developed through the EUMETSAT '''GRAS SAF'''.
     6
     7The ROPP deliverable 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_qc    : quality control routines
     11 * ropp_fm    : forward models (and associated tangent linear, adjoint & gradient code)
     12 * ropp_1dvar : 1D-Var retrieval & minimiser
     13 * ropp_test  : test harness
     14In addition there are ROPP areas for documentation, external web page content and a comprehensive test suite.
     15
     16== The ROPP Repository ==
     17
     18The repository for ROPP can be accessed via the Subversion server at the URL
     19{{{
     20svn://fcm7/ROPP_svn/...
     21}}}
     22For example, checking out the actual development versions:
     23{{{
     24svn co svn://fcm7/ROPP_svn/ropp_src/trunk ropp_src
     25svn co svn://fcm7/ROPP_svn/ropp_doc/trunk ropp_doc
     26svn co svn://fcm7/ROPP_svn/ropp_web/trunk ropp_web
     27svn co svn://fcm7/ROPP_svn/ropp_test/trunk ropp_test
     28}}}
     29will check out the source code, documentation, web presentation, and test folder. With FCM (see below), the
     30above checkout commands would be somewhat simpler:
     31{{{
     32fcm co fcm:ropp_src_tr ropp_src
     33fcm co fcm:ropp_doc_tr ropp_doc
     34fcm co fcm:ropp_web_tr ropp_web
     35fcm co fcm:ropp_test_tr ropp_test
     36}}}
    737
    838
    9 == Project Statistics ==
     39== FCM ==
     40 
     41ROPP uses FCM only for code management; the build part is based on GNU's autotools since the package is designed
     42to be portable and independent of any particular code management system.
    1043
    11 for the ROPP project (source code only) can be found [http://www.marquardt.sc/project_stats/ropp_src here].
     44Amongst the advantages of using FCM is a simpler front-end to Subversion commands (see the checkout examples above),
     45but also and graphical diff and merge utilities. In order to support ROPP, the following abbreviations/keywords
     46are implemented within the central FCM configuration:
    1247
     48{{{
     49set::repos::ropp_doc         svn://fcm7/ROPP_svn/ropp_doc
     50set::repos::ropp_doc_tr      svn://fcm7/ROPP_svn/ropp_doc/trunk
     51set::repos::ropp_doc_br      svn://fcm7/ROPP_svn/ropp_doc/branches
     52set::repos::ropp_doc_tg      svn://fcm7/ROPP_svn/ropp_doc/tags
     53set::repos::ropp_src         svn://fcm7/ROPP_svn/ropp_src
     54set::repos::ropp_src_tr      svn://fcm7/ROPP_svn/ropp_src/trunk
     55set::repos::ropp_src_br      svn://fcm7/ROPP_svn/ropp_src/branches
     56set::repos::ropp_src_tg      svn://fcm7/ROPP_svn/ropp_src/tags
     57set::repos::ropp_test        svn://fcm7/ROPP_svn/ropp_test
     58set::repos::ropp_test_tr     svn://fcm7/ROPP_svn/ropp_test/trunk
     59set::repos::ropp_test_br     svn://fcm7/ROPP_svn/ropp_test/branches
     60set::repos::ropp_test_tg     svn://fcm7/ROPP_svn/ropp_test/tags
     61set::repos::ropp_web         svn://fcm7/ROPP_svn/ropp_web
     62set::repos::ropp_web_tr      svn://fcm7/ROPP_svn/ropp_web/trunk
     63set::repos::ropp_web_br      svn://fcm7/ROPP_svn/ropp_web/branches
     64set::repos::ropp_web_tg      svn://fcm7/ROPP_svn/ropp_web/tags
    1365
    14 == About Subversion ==
    15 
    16 [http://subversion.tigris.org/ Subversion] is a version control system meant to be a replacement for CVS,
    17 and has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's,
    18 except where there's a compelling reason to do otherwise. The most important advantage over CVS is that
    19 Subversion does not only version file contents and file existence, but also directories, copies, and renames.
    20 Commits are also truly atomic; no part of a commit takes effect until the entire commit has succeeded. The most
    21 visible difference to CVS is that CVS Revision numbers are per-commit, not per-file. Tags and branches are also handled somewhat differently (rather like copying things into dedicated directories).
    22 
    23 Probably the best source about Subversion is the [http://svnbook.red-bean.com/nightly/en/index.html Subversion book]
    24 (the link points to the current development version of the documentation; pdf and other versions of the book are
    25 [http://svnbook.red-bean.com/ available here].
    26 
    27 Users without experience in version control systems like Subversion or CVS might benefit from this [http://svnbook.red-bean.com/nightly/en/svn.intro.html general introduction]; experienced CVS users will find
    28 [http://svnbook.red-bean.com/nightly/en/svn.forcvs.html Subversion for CVS users] useful.
    29 
    30 The subversion repository for ROPP can be accessed via the Subversion server at the URL
    31 {{{
    32 http://svn.marquardt.sc/svn/ropp/...
     66set::trac::ropp_doc          http://fcm7/projects/ROPP/browser/ropp_doc
     67set::trac::ropp_src          http://fcm7/projects/ROPP/browser/ropp_src
     68set::trac::ropp_test         http://fcm7/projects/ROPP/browser/ropp_test
     69set::trac::ropp_web          http://fcm7/projects/ROPP/browser/ropp_web
    3370}}}
    34 For example, checking out the actual development version of the entire source code into a subdirectory ropp_src would require
    35 {{{
    36 svn co http://svn.marquardt.sc/svn/ropp/ropp_src/trunk ropp_src
    37 }}}
    38 The commands
    39 {{{
    40 svn co http://svn.marquardt.sc/svn/ropp/ropp_doc/trunk ropp_doc
    41 svn co http://svn.marquardt.sc/svn/ropp/ropp_web/trunk ropp_web
    42 svn co http://svn.marquardt.sc/svn/ropp/ropp_test/trunk ropp_test
    43 }}}
    44 will check out the documentation, web presentation, and test folder in a similar way.
    45 
    46 == About Trac ==
    47 
    48 [http://trac.edgewall.com/ Trac] is a minimalistic approach to web-based management of
    49 software projects. Its goal is to simplify effective tracking and handling of software issues,
    50 enhancements and overall progress. All aspects of Trac have been designed with the single goal
    51 to help developers write software while staying out of the way and imposing as little as possible
    52 on a team's established process and culture.
    53 
    54 There is some [wiki:TracGuide built-in documentation], a [http://projects.edgewall.com/trac/wiki/TracFaq FAQ],
    55 and a complete list of [wiki:TitleIndex local wiki pages].
    56 
    57 
    58 
    59 == About this page ==
    60 
    61 As all Wiki pages, this page is editable, this means that you can
    62 modify the contents of this page simply by using your
    63 web-browser as soon as you are logged in. Simply click on the "Edit this page" link at the bottom
    64 of the page. WikiFormatting will give you a detailed description of
    65 available Wiki formatting commands. The [wiki:TracGuide Trac documentation]
    66 will also help you get started.
    67 
    68 It is possible to configure Trac to better fit this project, especially in regard to ''components'', ''versions'' and ''milestones''. Unfortunately, this is only possible on a system administrator level; please contact me (christian AT marquardt DOT sc) about this.
    69 
    70 
     71(See the FCM configuration file at ~fcm/FCM/work/FCM/src/etc/fcm.cfg)