<html>#2201: included walltime clock in CCTK_VWarn and CCTK_VInfo output
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>invalid</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>status:</td><td>invalid (was open)</td></tr>
</table></p>
<p>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:</p>
<p>HH:MM:SS.CC</p>
<p>for hours, minutes, seconds and fractions of seconds (which wraps around at midnight but that should be something that one can figure out).</p>
<p>Runtime in seconds would be less useful for this since one then has to check when the run actually started.</p>
<p><strong>Keyword:</strong> None</p>
<p>Comment (by Roland Haas):</p>
<p>An option for the desired output already exists.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2201/included-walltime-clock-in-cctk_vwarn-and'>https://bitbucket.org/einsteintoolkit/tickets/issues/2201/included-walltime-clock-in-cctk_vwarn-and</a></p>
</html>