NEMO TRAC wiki

  1. 2012 Work plan
    1. 2012 actions by stream :
    2. 2012 actions by institution :
    3. Ideas for the future:
  2. 2011 Work plan
    1. 2011 actions by stream :
    2. 2011 actions by institution :
    3. Validation
    4. Ideas for the future:
  3. 2010 Work plan
  4. 2009 milestones
  5. Download NEMO code
    1. README first !!!!
    2. A - Release nemo_v3_2_1
    3. B - NEMO trunk
  6. NEMO Configuration Data Base
    1. Executive Summary
    2. 1. INTRODUCTION
    3. 2. experimental Protocol
    4. 3. output diagnostics
    5. BIBLIOGRAPHY
  7. Using libIGCM library with ORCA2_LIM
    1. Purposes
    2. Quick start guide
  8. Using libIGCM library with ORCA2_LIM for nemo_v3_3
    1. Purposes
    2. Quick start guide : downloading nemo_3_3_beta
  9. NEMO team page
    1. [ https://forge.ipsl.jussieu.fr/nemo/wiki/Developers/2010fromMergePartyToVer …
    2. WorkingFAQ
    3. WorkingPractices , see also the Working …
    4. Answering the open tickets
    5. Question for the Developer committee

Welcome to NEMO Trac

What is Trac ?

Trac is an enhanced wiki and issue tracking system for software development projects. (See  http://trac.edgewall.org/ for details) For the NEMO platform, it is used as interface to identify bug reports and follow their corrections, as well as a tool to follow easily the evolutions and differences in the NEMO source code.

Trac used by NEMO

Within NEMO, Trac is used
- to visualize some informations
- to send your inputs and suggestions
In both cases, you need to login first see top right panel of this page (same login/pw as on the NEMO web site)

  • 1 - To visualize some informations

- have a look on bug reports (after login, click on "View tickets")
- browse source and view differences between versions.
The Trac browser can be used to browse directories, change logs and specific revisions of files stored in a subversion repository.
The default behavior is to display the latest revision but another revision number can easily be selected using the form at the top of the page.
Each release can be found under tags/TAGNAME. Last release is here :  https://forge.ipsl.jussieu.fr/nemo/browser/tags/nemo_v3_2
Important: for the quite old releases (under CVS only, i.e. before SVN use - before v2.3), the Trac viewer is not available and many other options ...

  • 2 - To receive new tickets and commit announcement

Please subscribe there:  http://forge.ipsl.jussieu.fr/mailman/listinfo/nemo_ticket
This is just a notification list, Posting is not allowed on this list.

  • 3 - To send inputs and suggestions

After login, you can report any bug, or post any suggestion for further developments by creating a ticket (in Trac vocabulary) here.
If you don't have an account, please register on the NEMO website first. Your account information will then be transfered to this website in up to 30 minutes.

What's new ?

May 2012
Mo Tu We Th Fr Sa Su
1
#959 UKMO developments for OBC-BDY merge (UKMO 3 and 4) (davestorkey)
 2
#960 Bug in trdmld & trdmld_trc - time step control (NEMO team)
 3
#961 Compilation with external complex BGC models (BFM) (vichi)
#962 Bug in zgr_sco missing lbc exchanges incorrect halo zeroing (NEMO team)
 4
#963 bug in limdmp_2.F90 : wrong variable used. (NEMO team)
#964 Limitation on meaning periods when using iomput (NEMO team)
 5
6
7
8
#965 nn_rstctl=2: why check consistency between namelist and restart? (NEMO team)
 9
10
#966 GYRE using linear eos (nn_eos=1) very slow (NEMO team)
 11
12
13
14
#967 Incorrect scale factors in diagnosed mass transport and vertical eiv (agn)
 15
#968 INGV- lobc for filtered (NEMO team)
#969 new branch for atm forcing mask (NEMO team)
#970 INGV2 - new turbolent parametrization of the Neutral drag coeff. (NEMO team)
#971 INGV4 - Implementation of stokes drift in momentum eq. (NEMO team)
 16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

F.A.Q

  • What is the difference between this site and NEMO main page ?

Trac is used to interact with the evolving NEMO reference (i.e. "Developping with NEMO"), as the NEMO web site documentation focuses on the usage of the NEMO system as it is (i.e. "Using NEMO").

  • What happened to my Flyspray reports ?

Concerning the Flyspray reports (i.e. before April 2008), they can be found here:  http://www.locean-ipsl.upmc.fr/flyspray/index.php?tasks=all&project=2