[MITgcm-support] Bug in seaice code since checkpoint67s?
Christoph Voelker
christoph.voelker at awi.de
Tue Oct 13 11:11:42 EDT 2020
Dear all,
I think I have discovered a problem with the current seaice code. I try
to run a global MITgcm setup with a salinity tracer contained in seaice.
I do so by setting
#define ALLOW_SITRACER
in SEAICE_OPTIONS.h. Otherwise I have no changed seaice code in my code
directory. I was able to execute the model then with the additional
tracer in previous code versions, but since I recently updated my code I
get an error message
* 253 Invalid operation PROG=seaice_growth ELN=6491(4003ee940)
and the model crashes. I have tried to reproduce the error again with
older code versions (to make sure that it is not something that is
within my code directory), by checking out older code, then going
through the canonical three steps in compilation, and running. I did
this for checkpoints 67m and 67r without any problem, but when I
switched to checkpoint67s I got the error message and crash again.
So it seems something has happened between checkpoint67r and 67s that
makes the model to crash when you switch on the seaice-tracer code. I
will try to understand that myself, but maybe some of you who know the
code better than me can directly say what the problem could be..
Cheers, Christoph
PS: I actually stumbled across this because I have a code version
(started by Razib Vhuiyan) that adds iron in dust as another tracer to
seaice; originally I encountered the error with this code after updating
and doing some other changes. So I first thought the problem would be on
my side, but I think I can now exclude that, because I now tested
without any code additions from my side.
--
Christoph Voelker
Alfred Wegener Institute
Helmholtz Centre for Polar and Marine Research
Am Handelshafen 12
27570 Bremerhaven, Germany
e: Christoph.Voelker at awi.de
t: +49 471 4831 1848
More information about the MITgcm-support
mailing list