Yes, I think that's the best solution. Thanks Roy On Fri, Oct 18, 2019 at 2:30 PM Stogner, Roy H <royst...@ices.utexas.edu> wrote:
> > On Fri, 18 Oct 2019, Alexander Lindsay wrote: > > > Is there a way to prevent prolongation/restriction of some System vectors > > during mesh adaptation? I see the *preserve* APIs but that doesn't look > > like it does what I would want.... Basically I am performing grid > > sequencing, obtaining initial guesses for fine grids based on solutions > of > > coarse grids. In a transient problem I have an old solution vector for > > calculating time derivatives. Restricting this vector for the initial > > coarse grid solution and then prolonging it for the fine grid solution > > loses the fine detail from the previous time step. > > I don't think we've got anything like that. Part of having a vector > attached to a System is having the system take care of making sure it > matches the system DoF partitioning. The way to keep a vector that's > *that* independent of a System is to not add it to the System in the > first place. Can you either allocate your vector separately, or > instead temporarily clone it and save the clone through your > coarsen/refine cycle? > --- > Roy > _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
