#1141: Carpet shouldn't stop the "CCTK_ total time" timer at Shutdown ---------------------+------------------------------------------------------ Reporter: knarf | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: ET_2013_05 Component: Carpet | Version: development version Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by knarf):
Double starting/stopping will not pose a serious problem to the code. From the definitions of the warning levels:
{{{ #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 */ }}}
Now, it all depends on how you define 'results of this run'. Most users will consider the timers to be a side product, not part of the main 'results'. CCTK_WARN_PICKY sounds best to me, but then that is still shown using simfactory defaults, thus I suggested CCTK_WARN_DEBUG (4).