Re: [Paraview] Suggestion for STL import

gt; Cc: paraview@paraview.org Subject: Re: [Paraview] Suggestion for STL import Eugene, I am pretty sure the community will be interested in this! While I'll need to look into the reader to understand, to get things going, do you have a sample dataset to demonstrate the issue? Utkarsh On Tue,

Re: [Paraview] Suggestion for STL import

Eugene, BTW, the reader does support not merging points. I'll check if ParaView exposes that option, if not, it should. That'll speed this up too. Utkarsh On Tue, Jul 5, 2016 at 12:04 PM, Utkarsh Ayachit < utkarsh.ayac...@kitware.com> wrote: > Eugene, > > I am pretty sure the community will be

Re: [Paraview] Suggestion for STL import

Eugene, I am pretty sure the community will be interested in this! While I'll need to look into the reader to understand, to get things going, do you have a sample dataset to demonstrate the issue? Utkarsh On Tue, Jul 5, 2016 at 10:28 AM, Eugene de Villiers wrote: >

[Paraview] Suggestion for STL import

Hi, When importing STL format geometry or similar, where connectivity information is not implicit in the data structure, it appears that the connectivity is reconstructed via an octree search. This is very inefficient when surfaces with large differences in edge length are imported – we have