If you provide TSMonitorStep or something along those lines, I do believe this could be solved. And the interface should also hold for future modifications where somebody comes up with a custom adaptor to modify time steps based on physics restrictions/a-priori error estimates/adaptive posteriori errors etc.. I have used the TSSetTimeStep with a post-step monitor function before but I feel knowing the current and previous step solutions would be relevant arguments for the user to decide an optimal step. My 2 cents. Vijay On Mon, Apr 18, 2011 at 2:15 PM, Jed Brown <[email protected]> wrote:

On Mon, Apr 18, 2011 at 21:06, Jeremy Riousset <[email protected]> wrote:

...

What difference between this and the use of TSSetTimeStep?

Where would you like to call TSSetTimeStep() from? It doesn't make much sense to call it from inside residual evaluation, for example. So you can register a post-step function that looks at whatever it wants and calls TSSetTimeStep().