[MITgcm-devel] tracForcingOutAB

[Manfredi Manizza]

Hi,

this is the error I have now :

(PID.TID 0001.0001) *** ERROR *** SEAICE_CHECK: Need T,S forcing out of AB 
(tracForcingOutAB=1)

I have hard time to understand what means. Did I say that already ? 
Aplogies if so.

I tried to change tracForcingOutAB to 0 or 1 this in data
but the error is the same.

At the moment I am using this set of parms from M. Mazloff in 
data.seaice.

I will have a look at the points from Martin and JM.

Thanks !
Manfredi

&SEAICE_PARM01
#- old default for useFluxForm and DIFF1:
        SEAICEwriteState = .TRUE.,
        SEAICE_initialHEFF = 0.0,
        SEAICE_deltaTtherm = 900.,
        SEAICEuseFlooding  = .TRUE.,
        SEAICE_EPS         = 1.E-8,
        SIsalFRAC          = 0.3,
  AreaFile ='/nobackupp1/mmanizza/input/AREA.ini.SOSE.bin',
  HeffFile ='/nobackupp1/mmanizza/input/HEFF.ini.SOSE.bin',
        SEAICE_area_floor = 1.E-5,
        SEAICE_area_reg = 0.15,
        SEAICE_hice_reg = 0.10,
        IMAX_TICE = 6,
        SEAICE_availHeatFrac = 0.8,
        SEAICEuseDYNAMICS  =.FALSE.,
#       SEAICE_deltaTdyn   = 900.,
        SEAICEadvScheme   = 2,
        SEAICEadvSalt     = .TRUE.
        SEAICEadvAge      = .FALSE.,
        SEAICEadvSnow     = .TRUE.,
        SEAICEdiffKhArea  = 10.,
        SEAICEdiffKhHeff  = 10.,
        DIFF1 = 4.E-3,



On Thu, 25 Aug 2011, Jean-Michel Campin wrote:

> Hi Manfredi,
>
> The MITgcm code is tested and this feature (i.e., forcing_In_AB=F)
> is well tested in several test-exp.
> Furthermore, setting of this parameter (tracForcingOutAB) is not very
> subtile, so it's unlikely that recent changes in the MITgcm code has
> something to do with this problem.
>
> For those reasons, I would be more likely to give more details about
> this type of issue if this was on MITgcm-support list (general type
> of question, general type of answer).
>
> In short, I would have answered to support list that
> the 1rst thing to check, from my point of view (and here I slightly
> disagree with Martin, because I would not add print statement until
> all the usual check & debug options have been tried), should be
> 1) clean built
> 2) any source code you added (in one of the "-mods=" dir)
>
> Cheers,
> Jean-Michel
>
> On Thu, Aug 25, 2011 at 09:26:40AM +0200, Martin Losch wrote:
>> Manfredi,
>>
>> I do not have any idea, the only place where tracForcingOutAB is set is in ini_parms.F
>> I would check:
>> - what does the STDOUT say (from config_summary)
>> - what's the value of tracForcingOutAB is before you enter seaice_readparms/seaice_check (needs extra print statements) to figure out where it is reset to 0.
>>
>> and I guess you can set this variable explicitly in "data"
>>
>> Martin
>>
>> On Aug 24, 2011, at 8:58 PM, Manfredi Manizza wrote:
>>
>>>
>>> Martin,
>>>
>>> Nothing, I just made a mistake with using that email
>>> for the reply to MITgcm developers. Anyway, do you have an
>>> idea about the problem stated in the email ?
>>>
>>> Ciao
>>> Manfredi
>>>
>>>
>>>
>>>
>>> On Wed, 24 Aug 2011, Martin Losch wrote:
>>>
>>>> Hi Manfredi,
>>>>
>>>> honestly, what does this question (that I cannot answer), have to do with the subject "google search"?
>>>>
>>>> Martin
>>>>
>>>> On Aug 24, 2011, at 1:37 AM, Manfredi Manizza wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I am running a job starting from obs using Matt's Southern Ocean Set-up and it crashes on this :
>>>>>
>>>>>
>>>>> C--   SEAICE needs forcing_In_AB FALSE
>>>>>     IF (tracForcingOutAB.NE.1) THEN
>>>>>        WRITE(msgBuf,'(2A)') 'SEAICE_CHECK:',
>>>>>    &         ' Need T,S forcing out of AB (tracForcingOutAB=1)'
>>>>>        CALL PRINT_ERROR( msgBuf, myThid )
>>>>>        STOP 'ABNORMAL END: S/R SEAICE_CHECK'
>>>>>     ENDIF
>>>>>
>>>>> forcing_In_AB was set to FALSE my data file....
>>>>>
>>>>> Why then it's complaining ?
>>>>>
>>>>> Thanks in advance
>>>>> Manfredi
>>>>
>>
>>
>> _______________________________________________
>> 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
>