[MITgcm-devel] switching seaice_obcs from legacy to devel

[Gael Forget]

Dimitris,

> Hi Gael, I have following questions regarding
> lab_sea/input.salt_plume/data.seaice
> 
> 1) Do we need to keep following lines, instead of using default values:
It is to you, I concur with Jean Michel. Btw I thought the 
idea was simply to switch to non-legacy. That does not
require an extensive revision of runtime parameters, but
I guess you decided to do that at the same time.

> 2) How does "SEAICE_salinityTracer = .TRUE.," work?
See labsea / salt_plume to which Jean Michel did activate it.
The code that gets activated by this switch is in seaice_tracer_phys.F
> Will it recognize HSALT boundary conditions?
I suppose you mean obcs. I did not add open boundary code for 
the seaice tracers. Unless somebody else did, the answer is no. 
I dont think there is an 'on the fly' conversion of HSALT 
pickups either in case that matters.

Cheers,
Gael

> 
> Thanks
> 
> Dimitris Menemenlis
> 
> On Dec 16, 2012, at 4:03 PM, Jean-Michel Campin wrote:
> 
>> Hi Dimitris,
>> 
>> Thanks for taking care of this.
>> Just one comment:
>>> (1) using the same data.seaice parameters as lab_sea/input.salt_plume and
>> if you see some parameters to change/improve in lab_sea/input.salt_plume set-up,
>> we could also decide to update this set-up, so that you will start
>> seaice_obcs with something better.
>> 
>> Cheers,
>> Jean-Michel
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel