[MITgcm-devel] exf runoff and seaice

Dimitris Menemenlis menemenlis at sbcglobal.net
Thu May 17 15:09:19 EDT 2007


> it means that if I don't set ALLOW_RUNOFF, I would be able to read
> the runoff file (because the loading part is with define ALLOW_SEAICE),
> will be able to store it (again, because define ALLOW_SEAICE in EXF_FIELDS.h),
> it will not be correct, since the date_array will not be set,
> the exf_monitor will print something, but I have no idea of what forcing 
> I will get at the end (will not be part of sflux in exf_getforcing.F,
> might come back in seaice_growth.F ?, and if I use pkg/thsice ? )

I agree, this is a mess.  Proceeding the way you suggested in previous e-mail is 
better.

> As I wrote earlier, I would like to have a test experiment with
> seaice+thsice checked in, before removing this SEAICE_EXTERNAL_FORCING
> option. And I am not yet done, this was the suject of my last remark.
> I will remove the define ALLOW_SEAICE in pkg/exf, and I guess will have 
> to fix what this breaks in pkg/seaice.

OK.  Shouldn't break anything (I think) if you add a check for ALLOW_RUNOFF in 
seaice_check.F.

D.




More information about the MITgcm-devel mailing list