[MITgcm-support] coupling issues

[David Ferreira]

Hi Alexandre,

FSOL is computed and diagnosed in phys_radiat.F (first subroutine), so 
it does not depend on other part of the code. Both formula are easily 
recoded in matlab, it could be useful to check what is going on.
Just to be sure you are integrating globally including the grid cell 
area from an annual mean provided by the diagnostics package?

As for ALLOW_CLOUD_3D, I use it. It was introduced to improve some of 
the radiative vertical profiles (I can't remember what exactly). It 
won't change FSOL.

cheers,
david

On 4/13/15 6:56 PM, Alexandre Pohl wrote:
> Dear David, Martin and Jeffery,
>
> Thank you very much for your quick answers. I removed the pkg/seaice 
> from my coupled setup. Concerning the execution error due to the 
> option 'ALLOW_AIM_CO2', adding the namelist 'AIM_PAR_CO2' in 
> data.aimphys solved my problem, too. So, thank you again.
>
> Here is what I got regarding the insolation issue :
> * with # undef ALLOW_INSOLATION, the mean annual globally averaged 
> incoming solar radiation is FSOL = 344.51 W/m2 instead of the expected 
> value SOLC = 342 W/m2 defined in data.aimphys.
> * surprisingly, result does not improve when the option 
> ALLOW_INSOLATION is turned on. The new value that I get is 345.38 W/m2.
> * ALLOW_CLOUD_3D has no impact on this value. By the way, should I 
> turn this option on?
>
> Do you think that the unexpected insolation value may be due to 
> another flag, that I have to switch on or off somewhere in the code? 
> Any idea?
>
> Alexandre
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20150414/92a72f8e/attachment.htm>