[Developers] when to schedule steering methods

[Thomas Radke]

Werner Benger wrote:
> I tried to reply earlier, but that mail apparently got lost. Wanted to throw in here
> the memories of the prototype implementation of CactusNet/http , where the
> http service was separated into two scheduling parts:
> 
>   - one to accept the request and possibly switch on parameters, e.g. for
>     activating an analysis routine - this section is running before the ANALYSIS
>     routines are invoked
> 
>   - a second one to send back the results, which is similar to an output routine,
>     but globally, I think that one was at POSTSTEP, similar to what the current
>     CactusConnect/HTTPS is doing.
> 
> The reason for this splitup was to enable temporary analysis routines, for
> instance one analysis per HTTP client request, instead of having this one
> permanently being invoked even if no one is watching the output.

Hi Werner,

the steering mechanisms in CactusConnect/HTTPD and AstroGrid/HTTPS let 
you pause a simulation, then single-step to the next iteration, continue 
or terminate the run.

I guess what you had in mind can be easily achieved by temporarily 
turning on/off output for an analysis quantity in single-step mode ?

-- 
Cheers, Thomas.