[MITgcm-support] coupling issues

[Jeffery R Scott]

This is correct -- coupled configuration is only for the thermodynamic  
sea ice.
Jean-Michel and I have had discussions about how to get seaice  
dynamics working in the aim coupled configuration, and something I  
need for the atm2d coupled configuration, so there's some hope on this  
front.

Jeff



On Apr 10, 2015, at 6:21 AM, Martin Losch wrote:

> As far as I know, pkg/seaice cannot be used in the coupled  
> configuration. You’ll have to stick to the “non-dynamic” thsice.
>
> M.
>
>> On 10 Apr 2015, at 11:09, Alexandre Pohl  
>> <alexandre.pohl at lsce.ipsl.fr> wrote:
>>
>> Dear all,
>>
>> I am trying to set a coupled ocean-atmosphere configuration of the  
>> MITgcm, and I am now getting stuck due to several coupling issues.
>>
>> The first one concerns the pkg/seaice. I wanted to use it in  
>> conjunction with the pkg/thsice at first, but I am now wondering if  
>> using the pkg/seaice is simply possible in a coupled setup or not.  
>> Which strikes me, is the fact that using the pkg/seaice requires  
>> activating the pkg/exf, which seems to have been constructed to  
>> force the OGCM. I saw a few flags in EXF_OPTIONS.h, that have to be  
>> defined when pkg/aim_v23 is used, or when the pkg/seaice is  
>> activated. But what should I do if both are used? Is there any way  
>> to use the pkg/seaice without using any external surface forcing  
>> file, i.e. using only variables computed by aim_v23?
>>
>> Another coupling issue concerns the pkg/dic. I would like to allow  
>> CO2 exchanges between the ocean and the atmosphere, and I  
>> consequently thought the flag 'ALLOW_AIM_CO2' had to be defined  
>> within AIM_OPTIONS.h. While compiling the code goes well with this  
>> flag turned on, execution shortly ends without any explicit error  
>> message. I get a compiler 'namelist' error, with no additional  
>> information. Has anyone else experienced this before? Is there a  
>> workaround? Note that with the flag turned off, the code works well.
>>
>> Finally, I noticed something strange in my outputs. Although SOLC  
>> is set to 342 W/m2 in 'phy_const.h', the output diagnostic FSOL  
>> gives an annual globally-averaged value of 344.5 W/m2 (value  
>> directly computed on the non-interpolated CS grid). After a quick  
>> look at the code, it seems right to me that FSOL varies in time due  
>> to orbital variations, but I cannot figure out why the annual mean  
>> value differs from SOLC...
>>
>> Any help would be welcome, should it concern one or the other of  
>> these issues.
>> Thanks in advance,
>>
>> Alexandre Pohl
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support