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.
#864 (MERCATOR.10 — Online computing of transport across sections ¶) – NEMO

Opened 13 years ago

Closed 12 years ago

Last modified 2 years ago

#864 closed Task (fixed)

MERCATOR.10 — Online computing of transport across sections ¶

Reported by: cbricaud Owned by: cbricaud
Priority: low Milestone:
Component: OCE Version: v3.3
Severity: Keywords: 2011 OPA v3.3
Cc:

Description

add online computing of transports across sections.

svn branch:
branches/2011/dev_r2802_MERCATOR10_diadct/

Commit History (0)

(No commits)

Change History (14)

comment:1 Changed 13 years ago by cbricaud

wikipage:

wiki:ticket/864?

comment:2 Changed 13 years ago by rfurner

Currently the documentation seems to be a little lacking, it doesn't seem very clear to me and the formatting of the documentation is rather messy, with odd line indentation etc.

I think it would be good to neaten this up, and to clearly explain what the new code does, and how to use it. (i.e. A module is available to compute transport of volume, heat and salt through sections. Any number of sections can be specified, and transports for different classes can be calculated. Classes can be defined by the user as......... There are 2 parts to this code; an offline script which can be used to specify sections, and a module diadct.F90 which calculates the values of transport during model runs. To use this code the sections must be specified by........ Then the code must be built with key_diadct, and suitable namelist options picked....)

One of the issues with the code you originally sent us was that it wasn't clear what is positive transport and what is negative. Does this depend on which way the section is defined, or is is independent of whether the section goes from a to b or from b to a, it would be good to list in the documentation which way is positive. Also, have you tested the specification of the start and end points? Have all section directions (north to south, east to west, northeast to southwest, and northwest to southeast) been run with the section specified as a to b and also from b to a, and all give identical results? If not, I would consider this test fairly important to carry out as a check of the offline tools, would you have time to run them?

comment:3 Changed 12 years ago by cbricaud

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 8 years ago by nicolasmartin

  • Keywords 2011 Interfaces Stream User added

comment:5 Changed 8 years ago by nicolasmartin

  • Keywords interfaces added; Interfaces removed

comment:6 Changed 8 years ago by nicolasmartin

  • Keywords user added; User removed

comment:7 Changed 8 years ago by nicolasmartin

  • Keywords nemo_v3_3* added

comment:8 Changed 8 years ago by nicolasmartin

  • Milestone 2011 Stream 1: User Interfaces deleted

Milestone 2011 Stream 1: User Interfaces deleted

comment:9 Changed 8 years ago by nicolasmartin

  • Keywords interfaces user added; UI removed

comment:10 Changed 8 years ago by nicolasmartin

  • Keywords interfaces removed

comment:11 Changed 8 years ago by nicolasmartin

  • Keywords user removed

comment:12 Changed 7 years ago by nemo

  • Type changed from Development to Task

Remove 'Development' type

comment:13 Changed 6 years ago by nemo

  • Keywords nemo_v3_3* removed

comment:14 Changed 2 years ago by nemo

  • Keywords OPA v3.3 added
Note: See TracTickets for help on using tickets.