[Paraview] Wrong fetched data

Cory Quammen cory.quammen at kitware.com
Fri Jul 3 10:05:30 EDT 2015


Hi Filipe,

Perhaps the array at index 7 is not the array you are expecting? Could you
access the array by name instead, .e.g.,

dAxis.GetPointData().GetArray('variable_name').GetValue(150)

and see if that works better?

Thanks,
Cory

On Wed, Jul 1, 2015 at 1:44 PM, deq11009 <deq11009 at fe.up.pt> wrote:

> Hi,
>
> I am currently using Paraview 4.2, 64, in Windows. (but tried 4.3 and same
> problem happened)
>
> My case is Ensight transient. Cylinder with 3.6 million cells, two-phase
> flow.
>
> I created a python code, which I run from the shell in the GUI.
>
>
> The main parts of the code are:
>
>
> enscase = EnSightReader(CaseFileName = direcp + 'ensfinal.case')
> ...
> axis = Line()
> ...
> rAxis = ResampleWithDataset(Input = enscase , Source = axis)
> ...
> rAxis.SMProxy.UpdatePipeline(7) # enscase.SMProxy yields same problem
> rAxis.UpdatePipelineInformation()
> dAxis = servermanager.Fetch(rAxis)
>
>
>
> Now, for example:
> print dAxis.GetPointData().GetArray(7).GetValue(150)
> which gives me the value 150 of the phase array.
>
> This data is wrong. On the other hand, if I go to the GUI Pipeline and
> create a Spreadsheet, the values are the real ones (confirmed in Fluent).
>
> So, the fetched data in the python shell is, for some reason, wrong.
> What is my mistake?
>
>
> Thanks
> Filipe Direito
>
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/3f22a97e/attachment.html>


More information about the ParaView mailing list