Just to provide an update here, the conclusion of our internal discussion
was to backlog this on our end for now, in favor of more urgent tasks.
Perhaps we can open an issue for this on the PETSc issue tracker (or
comment on an existing issue for BDF, if it exists), and I can check in
there if/when
Sure, I was suggesting you might implement it for your one-needed
TSView_*/TSLoad_*. With a single template done we can easily add the rest.
I agree having an API to start with multiple solutions is a good idea and
would be needed for any TSView_*/TSLoad_*. so that may be the simplest
way f
>
> Are you up to trying this by adding this functionality to
> TSView_*/TSLoad_*, or should we try to fit in time to add this (needed)
> support?
I'll have to consult with the team to decide what direction we want to go.
We may want to keep our restart data in a neutral format to support other
u
David,
I think Stefano was saying the TSView/Load approach should be improved to
save the additional vector(s) and use them in the restart.
Are you up to trying this by adding this functionality to
TSView_*/TSLoad_*, or should we try to fit in time to add this (needed) support?
>
> How are you currently restarting the simulation?
I just reviewed the code, and we're not currently using the `TSView/Load`
functions. We're just manually (de)serializing displacement, velocity, and
acceleration data using a neutral format, populating PETSc `Vec`s with this
data, and associat
Note that BDF has the same issue. I think the correct way to handle this is
to support storing/loading these extra vectors via TSView()/TSLoad().
How are you currently restarting the simulation?
Il giorno gio 2 gen 2025 alle ore 19:25 David Kamensky via petsc-users <
petsc-users@mcs.anl.gov> ha sc
