currently Cactus ignores, almost silently (there is a L2 warning "Non-steerable parameter 'ADMBase::initial_lapse' is not set from the parameter file but recovered from the checkpoint file"), any attempt to steer non-steerable parameters during checkpoint recovery. I wonder if it would be better to abort or at least make this a Lev1 warning. The comments in cckt_Warnlevel.h say:
#define CCTK_WARN_ABORT 0 /* abort the Cactus run */ #define CCTK_WARN_ALERT 1 /* the results of this run will be wrong, */ /* and this will surprise the user, */ /* but we can still continue the run */ #define CCTK_WARN_COMPLAIN 2 /* the user should know about this, */ /* but the problem is not terribly */ /* surprising */ #define CCTK_WARN_PICKY 3 /* this is for small problems that can */ /* probably be ignored, but that careful */ /* people may want to know about */ #define CCTK_WARN_DEBUG 4 /* these messages are probably useful */ /* only for debugging purposes */
since having a parameter being ignored is indeed surprising for most users :-) .