[MITgcm-support] Negative salinities

[Martin Losch]

Sergio,

no use in defining this CPP-flag, it will not solve your problem. This 
routine raises a flag/warning, if it finds one or more negative 
salinity values in the current horizontal slab and resets the negative 
values to zero.
But if you have salinities of +/-1.5e+139, your problem is likely to be 
something completely different. If this happens after one or two time 
steps, I am guessing, that there are some memory issues, such as a 
double precision field is read into a single precision variable or vice 
versa (for example, your forcing fields).

Martin

On Saturday, May 22, 2004, at 02:47 AM, Sergio Jaramillo wrote:

> Dear MITgcm support,
>
> I just noticed that the salinity field that I get from my runs is 
> going negative like -1.5e+139!. Why could this be? I only input 
> sRef=32*35, and I do all the stratification using the temperature 
> profile. I also have set sBeta=0.  Also I didn't have this problem 
> before , when I used an older version of the model (like a year ago, 
> v1.15 according to find_rho.F ).
>
> Finally I find this in find_rho.F:
>
> #ifdef CHECK_SALINITY_FOR_NEGATIVE_VALUES
>      CALL LOOK_FOR_NEG_SALINITY( bi, bj, iMin, iMax, jMin, jMax,  k,
>     &     sFld, myThid )
> #endif
>
> Should I define this in CPP_OPTIONS.h?
>
>
> Thanks a lot,
>
> Sergio Jaramillo
> UBC
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
>
Martin Losch // mailto:mlosch at awi-bremerhaven.de
Alfred-Wegener-Institut für Polar- und Meeresforschung
Postfach 120161, 27515 Bremerhaven, Germany
Tel./Fax: ++49(471)4831-1872/1797
http://www.awi-bremerhaven.de/People/show?mlosch