> On Feb 8, 2015, at 12:12 PM, Emil Constantinescu <emcon...@mcs.anl.gov> wrote: > > On 2/6/15 9:35 PM, Jed Brown wrote: >> Barry Smith <bsm...@mcs.anl.gov> writes: >>> I am not proposing removing the solution from TSSolve() argument >>> list, far from it. I am proposing removing the TSSetSolution(), >>> keeping the solution in TSSolve() as the standard approach, but >>> also allowing a callback for when the user wants the DM passed to >>> TS to be in charge of creating all the vectors. >> >> Oh, that's fine if/when you have a use case for it. > > To me TSSetSolution is semantically opposite to TSGetSolution and it's also > useful for when the users want to just use TSStep instead of TSSolve. There > is some redundancy in the case of TSSolve, but it makes the user codes > simpler.
Why would a user want to do TSStep() instead of calling TSSolve()? Barry > > Emil > >
