New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Custom Query – NEMO

Custom Query (2547 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 48 of 2547)

Ticket Resolution Summary Owner Reporter
#2029 wontfix SI3-01(2018WP)_topographic_meltponds vancop vancop
Description

Context

finish the last third of melt pond work ...

Implementation plan

...

#2184 duplicate VP_rheology vancop vancop
Description

VP rheology fo immerse

Summary

Action ${ACTION_NAME} Subject
PI(S) Principal investigator(s)
Digest Brief description with motivations and main tasks
Dependencies
Branch NEMO/branches/$YEAR/dev_r{REV}_{ACTION_NAME}
Previewer(s)
Reviewer(s)
Wiki wiki:${YEAR}WP/...

Abstract

This section should be completed before starting to develop the code, in order to find agreement with the previewer(s) on the method beforehand.

Description

Describe the goal of development, and the methodology.
Add reference documents or publications if relevant.

Implementation

Describe flow chart of the changes in the code.
List the .F90 files and modules to be changed.
Detailed list of new variables (including namelists) to be defined, give for each the chosen name (following coding rules) and definition.

Reference manual and web pages updates

Using part 1 and 2, define the summary of changes to be done in reference manuals (tex files), guide (rst files) and in the content of web pages.

Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.

#2185 duplicate VP_rheology vancop vancop
Description

BE CAREFUL !!! Due to dynamic behaviour of this ticket creation page, it is highly recommend to set first all other fields before writing the ticket description below. If you have lost your draft after an unwanted reload, you can click on the link 'Restore Form' in the contextual menu upper right to recover it. Remove these lines after reading.

Summary

Action ${ACTION_NAME} Subject
PI(S) Principal investigator(s)
Digest Brief description with motivations and main tasks
Dependencies
Branch NEMO/branches/$YEAR/dev_r{REV}_{ACTION_NAME}
Previewer(s)
Reviewer(s)
Wiki wiki:${YEAR}WP/...

Abstract

This section should be completed before starting to develop the code, in order to find agreement with the previewer(s) on the method beforehand.

Description

Describe the goal of development, and the methodology.
Add reference documents or publications if relevant.

Implementation

Describe flow chart of the changes in the code.
List the .F90 files and modules to be changed.
Detailed list of new variables (including namelists) to be defined, give for each the chosen name (following coding rules) and definition.

Reference manual and web pages updates

Using part 1 and 2, define the summary of changes to be done in reference manuals (tex files), guide (rst files) and in the content of web pages.

Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.

Note: See TracQuery for help on using queries.