Dear list,<br><br>I forward this thread that occured on ParaView mailing list. It initiated because of an error message found in ParaView. I was trying to expose some VTK filter to ParaView, with just an XML description of the filters. The rendering process found no data to render! This is because some data array (PointData) are not named.<br>
I was able to do my stuff by plugging a vtkImageMagnitude to the source/filter output. Or by derivating the class to a vtkPVImage...Filter and overloading a function and so on...<br><br> AFAIK, this is the case with:<br>- vtkImageGaussianSource<br>
- vtkImageReslice and inherited classes<br><br>Would it be possible to give a default name to all data array involved in a DataSet? Do I have to post on vtk-developers?<br><br>Thanks for all<br><br>Jerome<br><br><div class="gmail_quote">
---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Utkarsh Ayachit</b> <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>></span><br>Date: 2009/4/20<br>
Subject: Re: [Paraview] Bug in Slice representation or in my XML ?<br>To: Jérôme <<a href="mailto:jerome.velut@gmail.com">jerome.velut@gmail.com</a>><br>Cc: "Jean M. Favre" <jfavre@cscs.ch>, ParaView <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br>
<br><br>IMHO, VTK has to be more strict to ensure that all data arrays are<br>
named, maybe even assign some default unique names to the data arrays.<br>
Some API on vtkAlgorithm breaks if arrays are not named.<br>
<font color="#888888"><br>
Utkarsh<br>
</font><div><div></div><div class="h5"><br>
On Mon, Apr 20, 2009 at 5:29 AM, Jérôme <<a href="mailto:jerome.velut@gmail.com">jerome.velut@gmail.com</a>> wrote:<br>
> Hi Jean,<br>
><br>
> - I was aware of the missing scalars->SetName("blabla") instruction. I think<br>
> I have to post it on the VTK mailing list: I find it terrible to have to<br>
> derived a VTK class like vtkImageGaussianSource to a<br>
> vtkPVImageGaussianSource, to give a CMakeList with cxx code, for the only<br>
> purpose to overload one function and to add one line. I do that by now!!<br>
> I proposed the ImageMagnitude hack in order to produce only an XML that will<br>
> expose the VTK classes without compilation.<br>
><br>
> Question to developers would be: Has ParaView to be less restrictived about<br>
> existenz of Point/Cell Data name, or has VTK to be more strict about setting<br>
> a name, in all cases, to data?<br>
><br>
> - Today I am working on a Windows XP computer. And yes, you are right, I<br>
> cannot reproduce the bug. My Fedora looks problematic then. I will wait<br>
> until may, for Fedora 11. New system, new libs, maybe new behaviours?<br>
><br>
> Many thanks for your time!<br>
><br>
> Jerome<br>
><br>
> 2009/4/20 Jean M. Favre <jfavre@cscs.ch><br>
>><br>
>> Jérôme wrote:<br>
>> > Dear list,<br>
>> > Please find attached an XML that will expose vtkImageGaussianSource and<br>
>> > vtkImageMagnitude to ParaView<br>
>> > First of all, vtkImageGaussianSource behaves like it does not produce<br>
>> > any<br>
>> > data :<br>
>> > - Add a Gaussian Source to the pipeline,<br>
>> > - Apply<br>
>> > - Then go to the information panel of the object inspector : No data<br>
>> > arrays !!<br>
>><br>
>> This behavior can be traced back to the fact that the vtkDataArray<br>
>> allocated in VTK/Filtering/vtkImageData.cxx does not name the array.<br>
>> ParaView needs all data fields to be named. Adding this single line of<br>
>> code makes wit work.<br>
>><br>
>><br>
>> scalars->SetName("scalars");<br>
>><br>
>><br>
>> For the rest of your comments concerning slicing and information, I<br>
>> cannot reproduce any of the symptoms you mentioned. Slice representation<br>
>> works fine and the Extents are not touched AFAIK.<br>
>><br>
>> Jean --<br>
>> Swiss National Supercomputing Center<br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Please keep messages on-topic and check the ParaView Wiki at:<br>
>> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
</div></div></div><br>