[vtkusers] Crust Algorithm in VTK?

Paul Korir pkorir at ebi.ac.uk
Fri Sep 8 08:32:55 EDT 2017


Thanks for the very useful replies.

Paul


On 06/09/2017 15:37, Bill Lorensen wrote:
> Sorry,
>
> here is a link to the example:
> https://lorensen.github.io/VTKExamples/site/Cxx/Points/PowercrustExtractSurface/
>
>
> On Wed, Sep 6, 2017 at 8:13 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> I have made the Powercrust algorithm a vtk remote module. See this
>> example that illustrates the technique and describes how to use it as
>> a remote module.
>>
>> NOTE: Powercrust is covered by the GPL license which IS NOT compatible
>> with VTK's license. Hence, we cannot distribute it with VTK. Also,
>> commercial users should understand the implications of including this
>> software in their products.
>>
>> Enjoy,
>>
>> Bill
>>
>>
>> On Wed, Sep 6, 2017 at 5:29 AM, Paul Korir <pkorir at ebi.ac.uk> wrote:
>>> Thanks for this. I'm looking into this.
>>>
>>> Any reason for not including crust?
>>>
>>> P
>>>
>>>
>>>
>>> On 05/09/2017 14:40, Bill Lorensen wrote:
>>>> Have you tried vtkExtractSurface,
>>>>
>>>> Here is an example:
>>>> https://lorensen.github.io/VTKExamples/site/Cxx/Points/ExtractSurface/
>>>>
>>>>
>>>> On Tue, Sep 5, 2017 at 9:23 AM, Paul Korir <pkorir at ebi.ac.uk> wrote:
>>>>> Dear All,
>>>>>
>>>>> I recently came across the crust algorithm for computing a surface along
>>>>> a
>>>>> set of points. It seems to be a relatively powerful algorithm but is not
>>>>> implemented in VTK. VTK has the VTKRuledSurfaceFilter but this has major
>>>>> limitations in various topologies. The alternative is to use some plugins
>>>>> implemented for 3D Slicer but it seems like overkill to have to install
>>>>> 3D
>>>>> Slicer plus an additional plugin just to solve this problem. Obviously
>>>>> the
>>>>> better option would to implement the plugin functionality directly into
>>>>> VTK
>>>>> but obviously I cannot dictate someone's development schedule.
>>>>>
>>>>> My question is: is there something wrong with the crust algorithm that
>>>>> has
>>>>> prevented its implementation in VTK? Are there any plans for this? Is
>>>>> there
>>>>> anything better that can then be included.
>>>>>
>>>>> Thanks for shedding light on this most important of problems.
>>>>>
>>>>> --
>>>>> Paul K. Korir, PhD
>>>>> Scientific Programmer
>>>>> EMBL-EBI
>>>>> 01223494422
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the VTK FAQ at:
>>>>> http://www.vtk.org/Wiki/VTK_FAQ
>>>>>
>>>>> Search the list archives at: http://markmail.org/search/?q=vtkusers
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/vtkusers
>>>>
>>>>
>>> --
>>> Paul K. Korir, PhD
>>> Scientific Programmer
>>> EMBL-EBI
>>> 01223494422
>>>
>>
>>
>> --
>> Unpaid intern in BillsBasement at noware dot com
>
>

-- 
Paul K. Korir, PhD
Scientific Programmer
EMBL-EBI
01223494422



More information about the vtkusers mailing list