On 5/1/17 4:42 PM, Matthew Knepley wrote:
On Mon, May 1, 2017 at 4:27 PM, Scott Dossa > wrote:
Hi All,
Matt:
Thank you! Using the application context is a good approach to pass
the vector information. Can you also direct me to which
On Mon, May 1, 2017 at 4:27 PM, Scott Dossa wrote:
> Hi All,
>
> Matt:
> Thank you! Using the application context is a good approach to pass the
> vector information. Can you also direct me to which command allows TSSolve
> to be only called for one timestep / start at the
Hi All,
Matt:
Thank you! Using the application context is a good approach to pass the
vector information. Can you also direct me to which command allows TSSolve
to be only called for one timestep / start at the correct timestep? When
TSSolve() is called, it always resets to timestep 0.
Barry:
Scott - Are you doing some kind of pressure projection method?
PETSc-developers - should this functionality be directly added to TS since
it comes up fairly often?
Barry
> On May 1, 2017, at 3:24 PM, Matthew Knepley wrote:
>
> On Mon, May 1, 2017 at 3:13 PM,
On Mon, May 1, 2017 at 3:13 PM, Scott Dossa wrote:
> Hi All,
>
> I'm looking to pass a vector between a KSP and TS routine. The KSP routine
> must be called before each timestep, and the solution vector is needed for
> the TS routine. Normally, TSSolve() runs over all
Hi All,
I'm looking to pass a vector between a KSP and TS routine. The KSP routine
must be called before each timestep, and the solution vector is needed for
the TS routine. Normally, TSSolve() runs over all timesteps, but in my
case, I'd like to be able to add a routine before each timestep.