Version 110 (modified by smasson, 10 years ago) (diff)

NEMO TRAC wiki

  1. 2011 Work plan
    1. 2011 actions by stream :
    2. 2011 actions by institution :
    3. Validation
    4. Ideas for the future:
  2. 2010 Work plan
  3. 2009 milestones
  4. Error: Page DownloadNEMOpage does not exist
    Error: Page NEMOConfigurationDataBase does not exist
    Error: Page libIGCM does not exist
    Error: Page libIGCM_nemo_v_3_3 does not exist
  5. NEMO Development activities
    1. Overview of NEMO development process

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 ?

November 2020
MoTuWeThFrSaSu
1
23
#2560Context 2 related bugs in GLS en not set at the bed for Neumann bdy ... GLS Neumann Boundary Condition not Set and Velocity average to T point requires 0.5 factor (systeam)
#2561 This ticket only concerns SI3 users who are willing to debug or test the ... Running SI3 without dynamics (ln_icedyn=F) fails (systeam)
4
#2564 Issue When running ORCA2 with tracer damping and without temporal ... ORCA2 tracer damping hand edits in dtatsd.F90 can be cumulatively applied (systeam)
5678
91011
#2568 On line 249 of all_functions.sh ... Bug in set_namelist in all_functions.sh in SETTE (ayoung)
1213
#2571Context While SETTE correctly labels results from tests of modified ... SETTE fails to detect modified reference configurations in working copies (smueller)
1415
16
#2572Context Two issues have arisen with the trunk whilst using the SETTE ... Issues with trunk when testing beyond SETTE (ORCA2_ICE_PISCES) (acc)
171819
#2573Context In SI3, the number of snow layers is limited to 1 for pratical ... SI3: number of snow layers is limited to 1 (systeam)
#2574Context When ssh is non linear (ln_linssh = F) ssh is initialized by both ... ssh initialization by dom_init routines when non linear (techene)
202122
23
#2579Context Compiler arch: %NCDF_HOME ... PGI compiler does allow read values from namelist using buffers (systeam)
24
#2580Context Default configurations with enabled icebergs (ln_icebergs = ... Missing iceberg restart in default configurations (systeam)
2526
#2583Context on new Meteo-France HPC, new storage quotas are very limited on ... add the possibility to run SETTE tests outside NEMO cfgs directory (gsamson)
272829
30

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