[[PageOutline]]
Last edited [[Timestamp]]

[[BR]]

'''Author''' : Olivier Le Galloudec 

'''ticket''' : #844

'''Branch''' : https://forge.ipsl.jussieu.fr/nemo/browser/branches/2011/dev_r2787_MERCATOR2_tidalharm
----

=== Description ===

Tidal harmonic package 
----
=== Testing ===
Testing could consider (where appropriate) other configurations in addition to NVTK].

||NVTK Tested||!'''YES!'''||
||Other model configurations||!'''YES!'''||
||Processor configurations tested||[ 1*1,4*4,2*8 ]||
||If adding new functionality please confirm that the [[BR]]New code doesn't change results when it is switched off [[BR]]and !''works!'' when switched on||!'''YES'''||

(Answering UNSURE is likely to generate further questions from reviewers.)

'Please add further summary details here'

 Tests done on IBM power 6:

    * reproductiblity: ORCA2_LIM with time splitting and tidal potential forcing: compare 2*8 and 4*4 configurations: results are identical ( for 75 time steps, with key_mpp_rep ) 


    * restartability: The restart capability is not implemented.

 Tests on theoric ssh:
 I impose a sea surface heigh in input to the diagnostic with a known decomposition in harmonic
 and the output is the exact solution. 

=== Bit Comparability ===
||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES !'''||
||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?||!'''YES!'''||
||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES!'''||

If you answered !'''NO!''' to any of the above, please provide further details:

 * Which routine(s) are causing the difference?
 * Why the changes are not protected by a logical switch or new section-version
 * What is needed to achieve regression with the previous model release (e.g. a regression branch, hand-edits etc). If this is not possible, explain why not.
 * What do you expect to see occur in the test harness jobs?
 * Which diagnostics have you altered and why have they changed?Please add details here........

----
=== System Changes ===
||Does your change alter namelists?||!'''YES !'''||
||Does your change require a change in compiler options?||!'''NO !'''||

If any of these apply, please document the changes required here.......

----
=== Resources ===

----
=== IPR issues ===
||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES !'''||

If No:

 * Identify the collaboration agreement details
 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........

=== Tidal Harmonic analyse on ORCA2_LIM ===

Configuration: ORCA2_LIM standard + time splitting + tidal potential forcing
Experience:
 *  1 year of simulation

We compare to TPXO 7.1 ATLAS [http://volkov.oce.orst.edu/tides/atlas.html].

We can see the figure for the tidal composante M2 (real and imaginary part).
[[Image(ORCA2_M2_x_elev.gif)]] [[Image(TPXO_7.1_M2_x_elev.gif)]]
[[Image(ORCA2_M2_y_elev.gif)]] [[Image(TPXO_7.1_M2_y_elev.gif)]]