Livia, It seems reasonable that you should be able to save field data stored in a vtkTable. Would you mind writing up a feature request at http://www.paraview.org/Bug/view_all_bug_page.php?
Thanks, Cory On Wed, Mar 25, 2015 at 9:47 AM, <[email protected]> wrote: > Hi, > > I was using the writer from the gui in Paraview. I created a very simple > programmable source (with output type vtkTable) with a column and a field > data array, then clicked File-Save Data from the menu. > > In the case of a table, the writer window doesn’t allow to specify the > association field, so only the row values are exported to the csv file. > > By the way, I see that if I apply a TableToPoints filter, the field array > is copied to the polydata correctly (and can be exported from there), but I > haven’t experimented with this solution further yet > > Thanks > > Livia > > > > *From:* Cory Quammen [mailto:[email protected]] > *Sent:* 24 March 2015 23:32 > *To:* Barazzetti, Livia (ISTB) > *Cc:* ParaView > *Subject:* Re: [Paraview] Paraview support of FieldData in a vtkTable > > > > Livia, > > > > Which writer are you using that doesn't save the field data? > > > > Thanks, > > Cory > > > > On Sun, Mar 15, 2015 at 5:30 AM, <[email protected]> wrote: > > Hello, > > I am thinking to store some info as FieldData of a table (for example, the > parameters used for the calculation of the data in the table - possibly > they could also be changing depending on other elements of the pipeline). I > tried a toy example in Python and it seems that vtkTable supports it (I am > able to add an array and read it back). In Paraview 4.3.1, visualizing the > field data from a python annotation works, but if I open the spreadsheet > view to see the field data I get > > Warning: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Rendering\vtkMarkSelectedRows.cxx, > line 209 > > vtkMarkSelectedRows (0000000010381890): FieldAssociation type not > supported yet. Selected elements may not be shown correctly. > > > > , also the writer doen't export the field data. > > Should I go forward in using the FieldData of a table (just remembering > that before exporting I should use a Python annotation or a programmable > filter to read the field data) or it is actually not supported by paraview > and I should avoid it? (for example, the field data would not be updated as > the rest of the pipeline, or something like that)? > > Thank you > > Best regards > > Livia Barazzetti > > > > > _______________________________________________ > 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 ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc.
_______________________________________________ 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 ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
