[MITgcm-devel] ocean_emissivity consistency

[Menemenlis, Dimitris (3248)]

Just thinking aloud: I wonder whether parameters that are common to more than one package, e.g., albedos, drag coefficients, emissivities, latent heats, should (eventually) all acquire default values from model/src/set_defaults.F?

More than once I have seen folks adjust parameters in packages where they never get used, e.g., ocean albedo in pkg/seaice when it is really obtained from pkg/exf.

If you agree that this is a problem, we could start this set_default.F behavior with emissivity, and then slowly propagate to other variables ...

Dimitris Menemenlis

On Dec 19, 2011, at 8:25 AM, Jean-Michel Campin wrote:

> Hi Martin,
> 
> I know this long-wave surface thing can be mis-leading 
> (in AIM, I think there is only one surface emissivity, and 
> when using thsice, not sure that we check if everything is
> consistent, but all can be set as run-time params and made
> consistent).
> Since this has been in place for long time, I propose to wait 
> a little bit for others feedback on this issue.
> But it would be good to fix this at some point.
> 
> Cheers,
> Jean-Michel