<p>Hi Berk,</p><p>I will try to have this working and let you know my progress.<br></p><p>Thank you very much!</p><p>Fucang</p><br><div class="gmail_quote">On Sat, Nov 8, 2008 at 8:48 PM, Berk Geveci <span dir="ltr"><<a href="mailto:berk.geveci@kitware.com">berk.geveci@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 Fucang,<br>
<br>
After you get this working, with our help, we should work together to<br>
write a wiki page that describes how more filter parameters can be<br>
exposed in ParaView. Last week, I had the idea of starting a series of<br>
recipes pages for the ParaView community to share knowledge. This<br>
would be a good start.<br>
<br>
-berk<br>
<br>
On Sat, Nov 8, 2008 at 7:34 AM, David E DeMarle<br>
<div><div class="Wj3C7c"><<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>> wrote:<br>
> Sure enough, according to the paraview plugins wiki you don't even<br>
> need the CMakeLists.txt (and thus to compile). Just write the XML file<br>
> that defines your new proxy and use the plugin manager to load it.<br>
><br>
> cool,<br>
> Dave<br>
><br>
> On Fri, Nov 7, 2008 at 8:21 PM, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:<br>
>> Unless I remember it wrong, there is also a way of simply loading the<br>
>> server manager xml instead of a plugin.<br>
>><br>
>> On Fri, Nov 7, 2008 at 9:11 AM, David E DeMarle<br>
>> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>> wrote:<br>
>>> You can of course modify the paraview source and recompile.<br>
>>> Specifically what you would do is edit the XML element that defines<br>
>>> the proxy for that filter in Servers/ServerManager/filter.xml in order<br>
>>> to add additional property definitions to let paraview expose those<br>
>>> missing filter methods.<br>
>>><br>
>>> An alternative way to do it is to write a plugin, consisting of a<br>
>>> small CMakeLists.txt file and a small XML file and recompile only<br>
>>> that. The XML file makes an alternative proxy for the same filter.<br>
>>><br>
>>> The benefit of the second option is quicker compile time and better<br>
>>> isolation of the modifications you are making to ParaView.<br>
>>><br>
>>> cheers,<br>
>>> Dave DeMarle<br>
>>><br>
>>> On Fri, Nov 7, 2008 at 2:31 AM, Jia Fucang <<a href="mailto:jiafucang@gmail.com">jiafucang@gmail.com</a>> wrote:<br>
>>>> Hi, everyone,<br>
>>>><br>
>>>> I often use Paraview for visualization of medical object geometry models<br>
>>>> and do some filtering. But I noticed that Paraview does not offer many<br>
>>>> parameters setup by user, like VTK filters. For example,<br>
>>>> SmoothPolyDataFilter,<br>
>>>> it can be used like<br>
>>>> vtkSmoothPolyDataFilter *smoother = vtkSmoothPolyDataFilter::New();<br>
>>>> smoother->SetInput(surface->GetOutput());<br>
>>>><br>
>>>> smoother->SetRelaxationFactor(0.1);<br>
>>>> smoother->SetFeatureAngle(60);<br>
>>>> smoother->FeatureEdgeSmoothingOff();<br>
>>>> smoother->BoundarySmoothingOff();<br>
>>>><br>
>>>> smoother->SetNumberOfIterations(50);<br>
>>>> smoother->SetConvergence(0);<br>
>>>><br>
>>>> Paraview 3.4.0 only display "Number of Iterations" and "Convergence" for<br>
>>>> user to setup. This often does not provide good effect like the C++ one.<br>
>>>><br>
>>>> Another example is<br>
>>>> vtkDecimatePro *decimate = vtkDecimatePro::New();<br>
>>>> decimate->SetInput(smoother->GetOutput());<br>
>>>><br>
>>>> decimate->SplittingOff();<br>
>>>> decimate->SetErrorIsAbsolute(5);<br>
>>>> decimate->SetDegree(10);<br>
>>>> decimate->SetMaximumError(0.005);<br>
>>>><br>
>>>> decimate->SetTargetReduction(0.8);<br>
>>>> decimate->PreserveTopologyOn();<br>
>>>> decimate->SetFeatureAngle(30);<br>
>>>> decimate->BoundaryVertexDeletionOff();<br>
>>>><br>
>>>><br>
>>>> Corresponding filter in Paraview 3.4.0 only have following options to setup:<br>
>>>> Target Reduction, Preserve Topology, Feature Angle and BoundVertex<br>
>>>> Deletion.<br>
>>>><br>
>>>> I know that too much options may confuse user. I wonder if there are some<br>
>>>> setup to<br>
>>>> use more options. Or should I revise ParaView source code to recompile a<br>
>>>> binary one.<br>
>>>><br>
>>>> Thank you very much!<br>
>>>><br>
>>>> Best,<br>
>>>> Fucang<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> ParaView mailing list<br>
>>>> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
>>>> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> David E DeMarle<br>
>>> Kitware, Inc.<br>
>>> R&D Engineer<br>
>>> 28 Corporate Drive<br>
>>> Clifton Park, NY 12065-8662<br>
>>> Phone: 518-371-3971 x109<br>
>>> _______________________________________________<br>
>>> ParaView mailing list<br>
>>> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
>>> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>>><br>
>><br>
><br>
><br>
><br>
> --<br>
> David E DeMarle<br>
> Kitware, Inc.<br>
> R&D Engineer<br>
> 28 Corporate Drive<br>
> Clifton Park, NY 12065-8662<br>
> Phone: 518-371-3971 x109<br>
><br>
</div></div></blockquote></div><br>