[MITgcm-devel] [MITgcm-cvs] MITgcm/doc CVS Commit

Jean-Michel Campin jmc at ocean.mit.edu
Mon Jun 15 18:45:13 EDT 2015


Hi Martin,

I've seen that you updated the primary lab_sea output (results/output.txt), 
but not the salt_plume one (results/output.salt_plume.txt) ; however, when 
I run testreport (-match 13) on baudelaire, the agreement for this secondary 
test has drop to only 12 identical digits for cg2d so it will not pass.

Should we update also this output ?

Cheers,
Jean-Michel

On Mon, Jun 15, 2015 at 11:48:41AM -0400, Martin Losch wrote:
> Update of /u/gcmpack/MITgcm/doc
> In directory forge:/tmp/cvs-serv1351/doc
> 
> Modified Files:
> 	tag-index 
> Log Message:
> document the following changes
> o pkg/seaice: modify seaice_lsr.F in order to improve the gradient 
>   computations; for SEAICE_VECTORIZE_LSR
>   - move the loops over which the tridiagonal solvers (seaice_lsr_tridiagu/v)
>     sweep to the outside, 
>   - remove store directives and add "CADJ loop sequential" directives
>     in analogy to model/src/solve_tridiagonal.F
>   - replace many "#ifdef SEAICE_VECTORIZE_LSR_ZEBRA" by variable loop
>     boundaries to yield more readable code. This has also the charming side
>     effect that your can use SEAICE_VECTORIZE_LSR_ZEBRA without 
>     SEAICE_VECTORIZE_LSR (i.e. adjoint without recomputations in 
>     seaice_lsr_tridiagu/v now requires either of these flags, vectorization
>     still requires SEAICE_VECTORIZE_LSR with SEAICE_VECTORIZE_LSR_ZEBRA as
>     an additional option)
>   The tridiagonal solvers are now completely analoguous to solve_tridiagonal.F
>   but the adjoint gradients (which are affected by this change) still explode.
>   - Rename SEAICE_VECTORIZE_LSR_ZEBRA to SEAICE_LSR_ZEBRA and define it
>     in lab_sea forward experiment (changes results -> updated)
> 
>   - updating adjoint experiment will follow
> 
> 
> _______________________________________________
> MITgcm-cvs mailing list
> MITgcm-cvs at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-cvs



More information about the MITgcm-devel mailing list