Hi, Joe,<div> Berk reminded me that Andy Bauer has put in some fixes for gradient interpolation for pyramids (5a7dc931c54d868). Since your data contain pyramids, this is quite likely the fix for this bug.</div><div>Leo</div>
<div><br><div class="gmail_quote">On Fri, Oct 19, 2012 at 12:05 PM, Yuanxin Liu <span dir="ltr"><<a href="mailto:leo.liu@kitware.com" target="_blank">leo.liu@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, Joe,<div> It looks like this was indeed a bug in 3.14.1 but the bug has been fixed in the current development branch. I am not entirely sure which commit explicitly did it. </div><div> </div><div>Leo</div><div class="HOEnZb">
<div class="h5"><div><br><div class="gmail_quote">
On Fri, Oct 19, 2012 at 5:54 AM, Joe Borġ <span dir="ltr"><<a href="mailto:mail@jdborg.com" target="_blank">mail@jdborg.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br><br>I am using 3.14.1 64-bit on a single core (if I enable multi-core, it becomes very unstable).<br><br>Adding tets to this small case works, but I've got a bigger duct with a more refined mesh and adding tets don't fix the problem (make it better though).<br>
<br>See attached PVSM.<div><br clear="all"><br clear="all"><br>Regards,<br>Joseph David Borġ <br><a href="http://www.jdborg.com" target="_blank">http://www.jdborg.com</a><br>
<br><br></div><div><div><div class="gmail_quote">On 18 October 2012 19:00, Yuanxin Liu <span dir="ltr"><<a href="mailto:leo.liu@kitware.com" target="_blank">leo.liu@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
No, I did not use Tetrahedralize. <div><br></div><div>Are you using the lastest development version? Are you running paraview as a single process?</div><div><br></div><div>Do you mind saving a state file of your session and post it? </div>
<div><br></div><div>thanks!</div><div><br></div><div>Leo<div><div><br><div><br></div><div><div><div><br><div class="gmail_quote">On Thu, Oct 18, 2012 at 4:31 AM, Joe Borġ <span dir="ltr"><<a href="mailto:mail@jdborg.com" target="_blank">mail@jdborg.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Leo,<br><br>You don't seem to have used the Tetrahedralise filter? How have you got this to work without that?<br>
<br>Mine works fine after setting the fluid as input and source as the inlet, but I must first use the Tetrahedralise filter. <br clear="all"><div>
<br clear="all"><br>Regards,<br>Joseph David Borġ <br><a href="http://www.jdborg.com" target="_blank">http://www.jdborg.com</a><br>
<br><br></div><div><div><div class="gmail_quote">On 17 October 2012 18:14, Yuanxin Liu <span dir="ltr"><<a href="mailto:leo.liu@kitware.com" target="_blank">leo.liu@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi Joe,</div><div><br></div>I am not seeing exactly what you are seeing. In the attached image produced with the current master, I created a stream tracer with outlet block as the seeds and the fluid block as the input, and the streamlines seem right. <div>
<br></div><div>But I think there is a bug in how the stream tracer handles multiblock data, because if I change the stream tracer input to the whole pipe data set, instead of just the fluid block, some stream lines go straight to the void like you described.</div>
<div><br></div><div>Can you try setting up the pipeline as I did using ExtractBlock and compare with my image?</div><div><br></div><div>Leo</div><div><div><div><div></div></div><br><div class="gmail_quote">
On Wed, Oct 17, 2012 at 10:51 AM, Magician <span dir="ltr"><<a href="mailto:f_magician@mac.com" target="_blank">f_magician@mac.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Joe,<br>
<br>
<br>
"Tetrahedralize" filter is applicable.<br>
All cells are splitted into Tetrahedral ones.<br>
Try it.<br>
<span><font color="#888888"><br>
<br>
Magician<br>
</font></span><div><div><br>
<br>
On 2012/10/17, at 23:40, Joe Borġ wrote:<br>
<br>
> Thanks Magician,<br>
><br>
> Thanks for testing. What are you using to convert to tet? Is it a ParaView feature?<br>
><br>
> Leo, can the priority of the bug be raised please?<br>
><br>
><br>
> Regards,<br>
> Joseph David Borġ<br>
> <a href="http://www.jdborg.com" target="_blank">http://www.jdborg.com</a><br>
><br>
><br>
> On 17 October 2012 14:20, Magician <<a href="mailto:f_magician@mac.com" target="_blank">f_magician@mac.com</a>> wrote:<br>
> Hi Joseph,<br>
><br>
><br>
> I tried your data and got a result as yours.<br>
> Your data only includes Hex, Wedge, Tet and Pyramid,<br>
> but streamlines are stopped earlier.<br>
><br>
> Same as my polyhedral pipe sample, I applied Tetrahedralize filter<br>
> to your pipe source, and I could get valid streamlines.<br>
><br>
><br>
> Magician<br>
><br>
><br>
> > Pipe.tar.gz attached to the bug report below, in the form of an Ensight<br>
> > Case. First extract the archive and to open in Paraview, use "All files<br>
> > (*)" when browsing and select the .encas, then select "EnSight Files".<br>
> ><br>
> ><br>
> > Regards,<br>
> > Joseph David Borġ<br>
> > <a href="http://www.jdborg.com" target="_blank">http://www.jdborg.com</a><br>
> ><br>
> ><br>
> > On 12 October 2012 03:28, Yuanxin Liu <leo.liu at <a href="http://kitware.com" target="_blank">kitware.com</a>> wrote:<br>
> ><br>
> > > Hi,<br>
> > > Is it possible for you to upload the data? By the way, if the cell<br>
> > > type is polyhedron, then this is quite likely the same bug as this:<br>
> > > <a href="http://paraview.org/Bug/view.php?id=13442" target="_blank">http://paraview.org/Bug/view.php?id=13442</a><br>
> > ><br>
> > > Leo<br>
> > ><br>
> > > On Thu, Oct 11, 2012 at 6:17 AM, Joe Borġ <mail at <a href="http://jdborg.com" target="_blank">jdborg.com</a>> wrote:<br>
> > ><br>
> > >> Hi guys,<br>
> > >><br>
> > >> I've got an odd issue with the stream trace and stream trace custom<br>
> > >> source filters in Paraview (3.14.1 64bit). No matter what settings I use,<br>
> > >> the traces die off very soon and some even carry on straight (even when<br>
> > >> there's no fluid).<br>
> > >><br>
> > >> See the two screenshots I've got from Paraview.<br>
> > >><br>
> > >> <a href="http://jdborg.com/images/paraview/pv_inlet.png" target="_blank">http://jdborg.com/images/paraview/pv_inlet.png</a><br>
> > >> <a href="http://jdborg.com/images/paraview/pv_outlet.png" target="_blank">http://jdborg.com/images/paraview/pv_outlet.png</a><br>
> > >><br>
> > >><br>
> > >> Not sure if this is a setting that's easy to miss or if it's more<br>
> > >> terminal.<br>
> > >><br>
> > >> Thanks,<br>
> > >><br>
> > >><br>
> > >> Regards,<br>
> > >> Joseph David Borġ<br>
> > >> <a href="http://www.jdborg.com" target="_blank">http://www.jdborg.com</a><br>
><br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br></div></div></div></div></div></div>
</blockquote></div><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>