#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output ---------------------------------+------------------------- Reporter: Roland Haas | Type: enhancement Status: new | Priority: optional Milestone: | Component: Cactus Version: development version | Keywords: ---------------------------------+------------------------- To correlate events in Cactus with external events on a cluster (eg IO slowdown, node or network maintenance, network congestion events) it would be useful to (have the option of) including the current time in warning messages output by Cactus, eg something like:
HH:MM:SS.CC
for hours, minutes, seconds and fractions of seconds (which wraps around at midnight but that should be something that one can figure out).
Runtime in seconds would be less useful for this since one then has to check when the run actually started.
#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output --------------------------+--------------------------------- Reporter: Roland Haas | Owner: (none) Type: enhancement | Status: new Priority: optional | Milestone: Component: Cactus | Version: development version Resolution: | Keywords: --------------------------+---------------------------------
Comment (by Erik Schnetter):
The parameter setting {{{cactus::info_format = "human-readable time stamp"}}} should do this.
#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output --------------------------+--------------------------------- Reporter: Roland Haas | Owner: (none) Type: enhancement | Status: closed Priority: optional | Milestone: Component: Cactus | Version: development version Resolution: worksforme | Keywords: --------------------------+--------------------------------- Changes (by Roland Haas):
* status: new => closed * resolution: => worksforme
Comment:
Great! I had no idea that this existed. Thank you.
#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output --------------------------+--------------------------------- Reporter: Roland Haas | Owner: (none) Type: enhancement | Status: closed Priority: optional | Milestone: Component: Cactus | Version: development version Resolution: worksforme | Keywords: --------------------------+---------------------------------
Comment (by Erik Schnetter):
Should we change the default?
#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output --------------------------+--------------------------------- Reporter: Roland Haas | Owner: (none) Type: enhancement | Status: reopened Priority: optional | Milestone: Component: Cactus | Version: development version Resolution: | Keywords: --------------------------+--------------------------------- Changes (by Roland Haas):
* status: closed => reopened * resolution: worksforme =>
Comment:
Maybe.
Changing the default probably break people parsing scripts eg that look for the mass from TwoPunctures (see: https://bitbucket.org/simulationtools/simulationtools/src/7d99c8ebdc26a7cc01... and eg `StringMatchQ["a Foo", "Foo" (* Foo is pattern *)] -> False`).
Having said that though: yes, I would think that changing the default info (and warning format) might be nice but will take two releases. Namely changing the defaults to:
* Cactus::highlight_warning_messages = no * Cactus::info_format = "human-readable time stamp"
the latter is a bit verbose since it contains the full date in the form "Wed Jun 30 21:49:08 1993" which is overkill and somewhat hard to parse while we would likely be fine with the HH:MM:SS part.
trac@lists.einsteintoolkit.org