On Sun, Jul 12, 2009 at 9:09 PM, Saswata Hier-Majumder <span dir="ltr"><<a href="mailto:saswata@umd.edu">saswata@umd.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1) I did. It returns correct values for the x nodes, but fails to do so for the y nodes. Here's a sample output generated from the driven cavity problem. ( I suppressed printing the solutions for brevity).</blockquote>
<div><br>I did not realize you mean as fields (rather than as the mesh). Give me your exact calling sequence. I can output<br>parallel fields fine, so something else must be going on. If you modified the code, send that too.<br>
<br> Matt<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
2) Thanks, I'll try that.<br>
<br>
Matthew Knepley wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
1) I believe the standard VTK viewer (ASCII Viewer with VTK format) gets the<br>
coordinates<br>
right. Can you verify this?<br>
<br>
2) You should be able to split the 4- component field into 4 fields using<br>
the Split filter in VTK<br>
or whatever viewer you use (I do this in Mayavi2, but Paraview also<br>
works).<br>
<br>
Matt<br>
<br>
On Sun, Jul 12, 2009 at 10:34 AM, Saswata Hier-Majumder <<a href="mailto:saswata@umd.edu" target="_blank">saswata@umd.edu</a>>wrote:<br>
<br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Hi,<br>
I would like to generate a vtk output from a multicomponent problem. In<br>
the vtk file, I would like the DA coordinates as well as all 4 components<br>
stored separately as scalar point data.<br>
<br>
I have been using the VecView_VTK routine from<br>
/ksp/ksp/ksp/examples/tutorials/ex29.c. But the vtk output seems to contain<br>
only the local coordinates (may be because DAGetCoordinates is not<br>
collective?). Is there a way to fix this?<br>
<br>
Also, using the same routine, all components of the solution corresponding<br>
to a node are dumped together. Is there a way to extract each component<br>
separately and ouput them separately as scalar point data?<br>
<br>
Thanks<br>
<br>
--<br>
</div><a href="http://www.geol.umd.edu/%7Esaswata" target="_blank">www.geol.umd.edu/~saswata</a> <<a href="http://www.geol.umd.edu/%7Esaswata" target="_blank">http://www.geol.umd.edu/%7Esaswata</a>><br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
</blockquote><div><div></div><div class="h5">
<br>
-- <br>
<a href="http://www.geol.umd.edu/%7Esaswata" target="_blank">www.geol.umd.edu/~saswata</a><br>
<br>
</div></div><br># vtk DataFile Version 2.0<br>
ASCII<br>
DATASET STRUCTURED_POINTS<br>
DIMENSIONS 49 49 1<br>
ORIGIN 0 0 0<br>
SPACING 1 1 1<br>
<br>
POINT_DATA 2401<br>
SCALARS scalars double 3<br>
LOOKUP_TABLE default<br>
X_COORDINATES 49 double<br>
0 0.0208333 0.0416667 0.0625 0.0833333 0.104167 0.125 0.145833 0.166667 0.1875 0.208333 0.229167 0.25 0.270833 0.291667 0.3125 0.333333 0.354167 0.375 0.395833 0.416667 0.4375 0.458333 0.479167 0.5 0 0.0208333 0.0416667 0.0625 0.0833333 0.104167 0.125 0.145833 0.166667 0.1875 0.208333 0.229167 0.25 0.270833 0.291667 0.3125 0.333333 0.354167 0.375 0.395833 0.416667 0.4375 0.458333 0.479167<br>
Y_COORDINATES 49 double<br>
0 0.0208333 0.0625 0.104167 0.145833 0.1875 0.229167 0.270833 0.3125 0.354167 0.395833 0.4375 0.479167 5.27367e-317 5.23119e-317 0 5.31253e-317 0 0 0 3.41641e-312 3.26575e-311 1.14376e-311 1.54269e-311 1.94163e-311 2.34056e-311 5.29014e-311 5.27095e-317 0 0 0 1.82492e-312 1.01431e-311 1.84614e-311 1.49455e-320 3.09811e-312 1.17559e-311 2.04136e-311 0 0 0 5.23119e-317 0 0 8.06358e-313 5.3312e-317 5.33093e-317 0 5.27392e-317<br>
Z_COORDINATES 1 double<br>
0<br>
<br></blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>