[MITgcm-devel] switching seaice_obcs from legacy to devel

[Dimitris Menemenlis]

Hi Martin, from what I can gather the "standard March 2012" parameters 
(translated to latest code options) are being used in lab_sea/input.

lab_sea/input.salt_plume appears to be exercising slightly different 
options in code, so I don't want to remove them unless Gael and 
Jean-Michel concur.

Gael, I still need an answer to second question. For the seaice_obcs 
experiment, can I use "SEAICE_salinityTracer=.TRUE."?

Thanks

Dimitris Menemenlis

On 12/18/2012 12:00 AM, Martin Losch wrote:
> How about using the default parameter set that we agreed on in March 2012? <http://mitgcm.org/pipermail/mitgcm-devel/2012-March/005300.html>
>
> Martin
>
> On Dec 18, 2012, at 3:32 AM, "Menemenlis, Dimitris (3248)" <Dimitris.Menemenlis at jpl.nasa.gov> wrote:
>
>> 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:
>>
>> #- to reproduce old results with former #defined SEAICE_SOLVE4TEMP_LEGACY code
>>     useMaykutSatVapPoly = .TRUE.,
>>     postSolvTempIter    =  0,
>>   SEAICE_dryIceAlb   = 0.8756,
>>   SEAICE_wetIceAlb   = 0.7856,
>>   SEAICE_drySnowAlb  = 0.9656,
>>   SEAICE_wetSnowAlb  = 0.8256,
>>   SEAICE_strength    = 2.6780e+04,
>>   SEAICE_waterDrag   = 5.3508,
>>
>> 2) How does "SEAICE_salinityTracer = .TRUE.," work?
>> Will it recognize HSALT boundary conditions?
>>
>> 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
>
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel
>