[MITgcm-devel] seaice_get_dynforcing.F: CDAIR SEAICE_drag and OCEAN_drag

[Jean-Michel Campin]

Hi Dimitris,

Changing default value can be a source of problems for users.

But if we change all the experiments that uses pkg/seaice with the 
default SEAICE_drag to have explicitly: SEAICE_drag = 0.0011, 
it will incite new users to use a better value for this parameter.
It could also push old users to revisit their choice (if/when
they update their code and check what has changed).

Now if you really want to change the default, changing the seaice
experiment will need to be done anyway, so it could be a first good step.

Cheers,
Jean-Michel

On Mon, Jan 06, 2014 at 10:36:48PM +0000, Menemenlis, Dimitris (3248) wrote:
> Hi Gael, An's adjusted drag coefficient parameters from Table 2 in
> http://ecco2.org/manuscripts/2011/NguyenJGR2011.pdf
> and also from
> http://mitgcm.org/viewvc/MITgcm/MITgcm_contrib/arctic/cs_18km/input/data.seaice
> are:
> 
>       SEAICE_waterDrag   = 5.5627,
>       SEAICE_drag        = 0.00114,
> 
> instead of default values:
> 
>       SEAICE_waterDrag   = 5.5    _d 0
>       SEAICE_drag        = 0.002  _d 0
> 
> So your recollection is correct.
> I would leave SEAICE_waterDrag alone, both because the change is small
> and because it is the default AOMIP value.  But we could change the default
> SEAICE_drag to 0.0011 or 0.00114, since it would be more in line with
> the AOMIP range of values between .0011 and .0013.
> 
> Dimitris Menemenlis
> 
> On Jan 6, 2014, at 11:43 AM, Gael Forget wrote:
> 
> > Two related questions :
> > - Are the default pkg/seaice drag parameters "correct" for simulations forced by 
> >  wind vectors as opposed to wind stress? I think I recall An arguing that the default 
> >  SEAICE_drag could be in error by a factor of 2 in this case (but maybe I recall wrong).
> > - In general, has anyone done a careful comparison of wind stress results from 
> >  exf versus seaice? I understand that interpretation of the differences could be 
> >  tricky but maybe such a comparison would still be informative.
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel