<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></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?<div class=""><br class=""></div><div class=""> Barry</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 3, 2020, at 9:53 AM, Jed Brown <<a href="mailto:jed@jedbrown.org" class="">jed@jedbrown.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="caret-color: rgb(0, 0, 0); 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: none;" class="">Use the xml format (not the legacy format) by naming your file.vtu instead of file.vtk</div><div style="caret-color: rgb(0, 0, 0); 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: none;" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); 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: none;" class="">On Thu, Sep 3, 2020, at 8:17 AM, Berend van Wachem wrote:<br class=""></div><blockquote type="cite" id="qt" style="font-family: Helvetica; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="">Dear PETSc,<br class=""></div><div class=""><br class=""></div><div class="">What is the best way to write data from a DMPLEX vector to file, so it <br class=""></div><div class="">can be viewed with paraview?<br class=""></div><div class="">I've found that the standard VTK format works for a serial job, but if <br class=""></div><div class="">there is more than 1 processor, the geometry data gets messed up.<br class=""></div><div class="">I've attached a small working example for a cylinder and the visualised <br class=""></div><div class="">geometry with paraview for 1 processors and 4 processors.<br class=""></div><div class="">Any pointers or "best practice" very much appreciated.<br class=""></div><div class=""><br class=""></div><div class="">Best regards,<br class=""></div><div class=""><br class=""></div><div class="">Berend.<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><b class="">Attachments:</b><br class=""></div><ul class=""><li class="">visualisemesh-1proc.png<br class=""></li><li class="">visualisemesh-4proc.png<br class=""></li><li class="">visualizemesh.c</li></ul></blockquote></div></blockquote></div><br class=""></div></body></html>