This MR deprecates it for 3.14. We can delete it for a future release. https://gitlab.com/petsc/petsc/-/merge_requests/3142
Matthew Knepley <[email protected]> writes: > I do not use it anymore. It can be thrown away. > > Matt > > On Thu, Sep 3, 2020 at 12:20 PM Barry Smith <[email protected]> wrote: > >> >> >> On Sep 3, 2020, at 10:47 AM, Jed Brown <[email protected]> wrote: >> >> I'd have deleted the legacy vtk many years ago, but Matt says he uses it. >> >> >> So he is plotting garbage or he never uses the broken stuff so it can be >> errorred out? >> >> >> >> On Thu, Sep 3, 2020, at 9:45 AM, Barry Smith wrote: >> >> >> Shouldn't this, "just work". PETSc should not be dumping unreadable >> garbage into any files, does the broken PETSc code need to be removed, or >> error out until it can be fixed? >> >> Barry >> >> >> On Sep 3, 2020, at 9:53 AM, Jed Brown <[email protected]> wrote: >> >> Use the xml format (not the legacy format) by naming your file.vtu instead >> of file.vtk >> >> On Thu, Sep 3, 2020, at 8:17 AM, Berend van Wachem wrote: >> >> Dear PETSc, >> >> What is the best way to write data from a DMPLEX vector to file, so it >> can be viewed with paraview? >> I've found that the standard VTK format works for a serial job, but if >> there is more than 1 processor, the geometry data gets messed up. >> I've attached a small working example for a cylinder and the visualised >> geometry with paraview for 1 processors and 4 processors. >> Any pointers or "best practice" very much appreciated. >> >> Best regards, >> >> Berend. >> >> >> >> >> *Attachments:* >> >> - visualisemesh-1proc.png >> - visualisemesh-4proc.png >> - visualizemesh.c >> >> >> > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
