<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>I'd have deleted the legacy vtk many years ago, but Matt says he uses it.</div><div><br></div><div>On Thu, Sep 3, 2020, at 9:45 AM, Barry Smith wrote:<br></div><blockquote type="cite" id="qt" style="overflow-wrap:break-word;"><div class="qt-"><br></div><div> 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?<br></div><div class="qt-"><br></div><div class="qt-"> Barry<br></div><div class="qt-"><div><br></div><div><div><br></div><blockquote type="cite" class="qt-"><div class="qt-">On Sep 3, 2020, at 9:53 AM, Jed Brown <<a href="mailto:jed@jedbrown.org" class="qt-">jed@jedbrown.org</a>> wrote:<br></div><div><br></div><div class="qt-"><div style="font-family:Helvetica;font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial;" class="qt-">Use the xml format (not the legacy format) by naming your file.vtu instead of file.vtk<br></div><div style="font-family:Helvetica;font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial;" class="qt-"><br></div><div style="font-family:Helvetica;font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial;" class="qt-">On Thu, Sep 3, 2020, at 8:17 AM, Berend van Wachem wrote:<br></div><blockquote type="cite" id="qt-qt" style="font-family:Helvetica;font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-size-adjust:auto;-webkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-style:initial;text-decoration-color:initial;" class="qt-"><div class="qt-">Dear PETSc,<br></div><div class="qt-"><br></div><div class="qt-">What is the best way to write data from a DMPLEX vector to file, so it <br></div><div class="qt-">can be viewed with paraview?<br></div><div class="qt-">I've found that the standard VTK format works for a serial job, but if <br></div><div class="qt-">there is more than 1 processor, the geometry data gets messed up.<br></div><div class="qt-">I've attached a small working example for a cylinder and the visualised <br></div><div class="qt-">geometry with paraview for 1 processors and 4 processors.<br></div><div class="qt-">Any pointers or "best practice" very much appreciated.<br></div><div class="qt-"><br></div><div class="qt-">Best regards,<br></div><div class="qt-"><br></div><div class="qt-">Berend.<br></div><div class="qt-"><br></div><div class="qt-"><br></div><div class="qt-"><br></div><div class="qt-"><br></div><div class="qt-"><b class="qt-">Attachments:</b><br></div><ul class="qt-"><li class="qt-">visualisemesh-1proc.png<br></li><li class="qt-">visualisemesh-4proc.png<br></li><li class="qt-">visualizemesh.c<br></li></ul></blockquote></div></blockquote></div></div></blockquote></body></html>