Hello, <div><br></div><div>i played around with those parameters, but it didn't seem to change anything...</div><div>what strikes me as most strange is that the first refinement level has points at z<0, but the largest grid has not...</div>
<div><br></div><div>so when using the clip operator, there is still some blanks where the points of the largest grid should be..i dont get why the points for the largest grid are not output there whereas they are for the other grids..</div>
<div>using the threshold operator works, but as you said more for debugging, and contour plots are not possible either/show the same discontinuities...</div><div><br></div><div>i am using visit 2.4.2, were there improvements relevant to this issues that would make it worth upgrading to 2.6?</div>
<div><br></div><div><br></div><div>best wishes,</div><div><br></div><div>Vassili<br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 2:32 PM, Roland Haas <span dir="ltr"><<a href="mailto:roland.haas@physics.gatech.edu" target="_blank">roland.haas@physics.gatech.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Vasilios,<br>
<div class="im"><br>
> sorry for the messages before, hopefully the mail is now small enough, but<br>
> i thought that adding a plot might explain better what i mean..<br>
</div>Plots are welcome. EMail sizes is not terribly important, we all have<br>
fast connections :-)<br>
<div class="im"><br>
> IOHDF5::one_file_per_group = no<br>
> IOHDF5::output_symmetry_points = no<br>
> IOHDF5::out3D_ghosts = no<br>
> IOHDF5::output_ghost_points = no<br>
> IOHDF5::out3D_outer_ghosts = no<br>
> IOHDF5::output_boundary_points = no<br>
> IOHDF5::output_buffer_points = no<br>
<br>
</div><div class="im">> are the specific parameters for cell-centered hdf5 output or other thorns<br>
> that could take care of that?<br>
</div>I will give you somewhat of the opposite advise that Erik just did.<br>
Certainly what Erik suggested is not a bad idea to get rid of some of th<br>
symmetry plane junk. The other option is to add a "Clip" operator (maybe<br>
with an origin of 1e-3 rather than 0) to the plot.<br>
<br>
Also I would try to successively change the "no"s above to "yes", in<br>
particular the one for ghost zones since new versions of VisIt do indeed<br>
use ghost zones for smooth transitions between blocks. With vertex<br>
centering this might show up as a white line, with cell centering<br>
possibly as the offset in data that you see at around point (15,8).<br>
<br>
Note that found the best way to get trustworthy plots for debugging out<br>
of VisIt is to add a "Threshold" operator selecting its point mesh<br>
option, then making the point size in a pseudocolor plot a bit larger.<br>
This gives you one dot per grid point with no strange interpolation in<br>
between.<br>
<br>
Yours,<br>
Roland<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
My email is as private as my paper mail. I therefore support encrypting<br>
and signing email messages. Get my PGP key from <a href="http://keys.gnupg.net" target="_blank">http://keys.gnupg.net</a>.<br>
<br>
</font></span><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>