[MITgcm-devel] Seaice wind-stress diagnostics

[Jean-Michel Campin]

Hi Dimitris and Martin,

OK, I see your point, and this could have been the reason to have SIuwind & SIvwind
diagnostics in pkf/seaice. But currently, uwind and vwind are only defined in pkg/exf
(EXF_FIELDS.h) and it seems more logical to use pkg/exf diagnostics to output
these fields. Also the description of SIu/vwind might let user think that
"SEAICE 10-m wind speed" is something different from just EXFu/vwind.

However, regarding the other diagnostics (SIfu,SIfv,SIqnet,SIqsw,SIempmr),
the old seaice forcing option is not the reason since they have been connected
to main model forcing fields (FFIELDS.h) since early on (Oct 2006, seaice_do_diags.F).

Cheers,
Jean-Michel

On Tue, May 09, 2017 at 09:00:09PM +0000, Menemenlis, Dimitris (329C) wrote:
> Hi Martin and Jean-Michel, in the distant past, pkg/seaice could be used independently of pkg/exf.
> It had its own bulk formulae ??? and actually some of the bells and whistles of pkg/exf, e.g., the
> ability to force with yearly atmospheric fields, were first implemented in pkg/seaice before being
> ported to pkg/exf.  So I think that???s the historical reason for duplicate diagnostics.
> 
> Dimitris
> 
> On May 9, 2017, at 1:04 AM, Martin Losch <Martin.Losch at awi.de<mailto:Martin.Losch at awi.de>> wrote:
> 
> Hi Jean-Michel,
> 
> thanks for doing this. I guess there used to be a reason for these diagnostics, back when exf was not entirely required for running seaice, but that???s really before I ever had a look at the code.
> As far as I remember there were very subtle differences in the heat and fw-flux diagnostics to oceFWflx and oceQnet etc, but I cannot remember them, so they can probably also be retired.
> 
> Martin
> 

> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel