[Developers] when to schedule steering methods

[Thomas Radke]

Hi,

Erik and I recently discussed the question of when would be the best 
time in the schedule tree to call a methods which allows users to 
interactively steer parameters (as are implemented in Cactus's webserver 
thorns CactusConnect/HTTPS and AstroGrid/HTTPS).
Currently the webserver's worker routine is scheduled at POSTSTEP which 
means that a parameter value may change after the evolution but before 
the analysis. Erik argues that this is somewhat inconsistent; a 
parameter change should become active only after an iteration has 
finished completely. I "countered" by saying that users might want to 
change I/O parameters before analysis so that they can turn on/off 
certain analysis routines if they'd want to.

What's other people's opinion on that ?

Iff we decide to schedule steering methods at the very end of an 
iteration, we'd need to introduce a new schedule bin, such as STEER.

-- 
Cheers, Thomas.