[Users] Graphical display of timer data

[Gabrielle Allen]

Ian — this was the aim of the project that Dylan undertook back in the day — the idea was that the simulation could actually dynamically choose parameters, e.g. instead of saying checkpoint every 1000 time steps, you would set a parameter to say that checkpointing should be no more than 10% of run time; or the code would be able to spot that an analysis method was taking 10x as much time and rachet back how often it was invoked — so both would need to be able to output with warnings, but also take intelligent action based on that (and this is something that I still think Cactus can do quite uniquely).

> On May 23, 2017, at 10:17 AM, Ian Hinder <ian.hinder at aei.mpg.de> wrote:
> 
> 
> On 23 May 2017, at 16:16, Gabrielle Allen <gaballen at gmail.com <mailto:gaballen at gmail.com>> wrote:
> 
>> 
>> The only interfaces I know about were through the web browsers. Dylan Stark did some work with this at CCT before
>> 
>> https://link.springer.com/chapter/10.1007/978-3-540-68111-3_124 <https://link.springer.com/chapter/10.1007/978-3-540-68111-3_124>
>> 
>> I always thought that it would be very helpful to have something that didn’t just report all the data but could tell you something in plain English about how to interpret the information.
> 
> I also thought about having something that ran "live" with the simulation, that was aware of how much time different things "should" take, maybe from parameters.  For example, you might get a warning that output was taking more than 30% of the simulation time, or horizon finding, or something like that.  
> 
> -- 
> Ian Hinder
> http://members.aei.mpg.de/ianhin <http://members.aei.mpg.de/ianhin>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/users/attachments/20170523/b6a894f3/attachment.html