Changes between Version 7 and Version 8 of ticket/0937

Timestamp:

2012-10-25T13:57:54+02:00 (12 years ago)

Author:

cbricaud

Comment:

--

ticket/0937

@@ -1 +1 @@
 [[PageOutline]] Last edited [[Timestamp]]
 
-'''Author''' : AUTHOR_NAME
+'''Author''' : Clément Bricaud, Jérôme Chanut, Guillaume Reffray
 
 '''ticket''' : #937
@@ -14 +14 @@
  * '''The improvement of the "bdy" package'''. This is a continuation of the progressive transition to a single open boundary package in NEMO:
 
-   * New schemes are available: tracers/velocities' relaxation, Neumann boundary conditions. 
-   * Inverse barometer can be added to open boundary data
-   * Open boundaries tidal harmonic data can be read from 2d data files (ie given on global data domain). This is aimed to ease model re-localisation.
-   * Various corrections in particular with user defined analytical segments: new definition of segments is more restrictive than in previous version to avoid errors in segments locations and crossings. This prevents, for instance, from updating some boundary points twice in case of overlapping FRS zone as it was the case in previous version. We allowed for structured (2d, ie normal/tangential directions to bdy) open boundary data in that case to ease open boundary data extraction from an other model simulation, visualization,...
+ * New schemes are available: tracers/velocities' relaxation, Neumann boundary conditions.
+ * Inverse barometer can be added to open boundary data
+ * Open boundaries tidal harmonic data can be read from 2d data files (ie given on global data domain). This is aimed to ease model re-localisation.
+ * Various corrections in particular with user defined analytical segments: new definition of segments is more restrictive than in previous version to avoid errors in segments locations and crossings. This prevents, for instance, from updating some boundary points twice in case of overlapping FRS zone as it was the case in previous version. We allowed for structured (2d, ie normal/tangential directions to bdy) open boundary data in that case to ease open boundary data extraction from an other model simulation, visualization,...
 
 ----
@@ -36 +36 @@
 
 === Bit Comparability ===
-|| Does this change preserve answers in your tested standard configurations (to the last bit) ? || !'''NO !''' ||
+|| Does this change preserve answers in your tested standard configurations (to the last bit) ? || NO ||
 || Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || !'''YES!''' ||
 || Is this change expected to preserve answers in all possible model configurations? || !'''NO!''' ||