Re: [Paraview] pvserver not rendering when built with osmesa (MPI disabled)
Hi Jeff, Which version of paraview source code are you compiling, and which version of osmesa are you using? Pat On Wed, Nov 24, 2010 at 6:16 PM, Jeff Mauldin wrote: > I am trying to run a paraview server (pvserver) on a multinode machine > using osmesa to do offscreen rendering (and then viewed from a client on > another machine). > > I have been successful in compiling pvserver with osmesa. However, when I > try to use pvserver, it hangs. Specifically, I start a paraview client on > machine A (bentley) and ask for a reverse-connection connection to a > pvserver which I will start manually on machine B. I go to machine B and > start pvserver (in reverse connect, with machine A specified as the client > host). > > The connection is successful insofar as the output on the terminal I > started pvserver on on machine B says > > Connected to client. > > However, no rendering occurs on the paraview client on Machine A. > > quite a bit of digging later (including putting some printf calls into > pvserver on machine B), I've figured out where the hang is: > > In > > vtkPVSynchronizedRenderWindows::SynchronizeBounds > we are in case RENDER_SERVER and we freeze during either the > c_rs_controller->Send > or > c_rs_controller->Receive > call. > > A bit of the call stack is: > > vtkPVSynchronizedRenderWindows::SynchronizeBounds > vtkPVRenderView::GatherBoundsInformation > vtkPVRenderView::Render > > I belive this is the first render attempt made by pvserver. > > I had compiled pvserver without MPI and am currently trying to recompile it > with MPI. > > > > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] GUI bug: Error message when moving the cursor on the menu bar
Do you have any Windows Accessibility features enabled in the Windows
control panel, or are you using a tablet?
Pat
On Fri, Nov 26, 2010 at 8:49 AM, Richard GRENON wrote:
> Hello everybody.
>
> Here I am again, but for a very annoying bug in the GUI of the PV 3.8.1
> Windows 32 bits version:
> When I click on a menu item, for instance the "Filter" item, its list of
> options appears. That's OK! Now if I don't make a choice in this options
> list and I move the cursor above the next item ("Tools") or the previous
> item ("Sources") without clicking again, the options list of the new item
> appears, but the "Output messages" window is shown with this error message:
>
> QAccessibleWidget::rect: This implementation does not support subelements!
>> (ID X unknown for QMenuBar)
>>
>
> where X is a number depending of the item where the cursor is.
>
> If I click on "Filters" and if I move the mouse over "Tools", "Macros", and
> "Help", I get three error messages with X being 6, 7 and 8 respectively.
>
> This very annoying bug is on PV 3.8.1 Windows Vista 32 bits Premium Home
> edition. Each item on the main menu bar is concerned.
>
> There is no such problem with PV 3.8.1 Linux 64 bits.
>
> Regards
>
> --
> Richard GRENON
> ONERA
> Departement d'Aerodynamique Appliquee - DAAP/ACI
> 8 rue des Vertugadins
> 92190 MEUDON - FRANCE
> phone : +33 1 46 73 42 17
> fax : +33 1 46 73 41 46
> mailto:richard.gre...@onera.fr
> http://www.onera.fr
>
> ___
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
[Paraview] GUI bug: Error message when moving the cursor on the menu bar
Hello everybody.
Here I am again, but for a very annoying bug in the GUI of the PV 3.8.1
Windows 32 bits version:
When I click on a menu item, for instance the "Filter" item, its list
of options appears. That's OK! Now if I don't make a choice in this
options list and I move the cursor above the next item ("Tools") or the
previous item ("Sources") without clicking again, the options list of
the new item appears, but the "Output messages" window is shown with
this error message:
QAccessibleWidget::rect: This implementation does not support
subelements! (ID X unknown for QMenuBar)
where X is a number depending of the item where the cursor is.
If I click on "Filters" and if I move the mouse over "Tools", "Macros",
and "Help", I get three error messages with X being 6, 7 and 8 respectively.
This very annoying bug is on PV 3.8.1 Windows Vista 32 bits Premium Home
edition. Each item on the main menu bar is concerned.
There is no such problem with PV 3.8.1 Linux 64 bits.
Regards
--
Richard GRENON
ONERA
Departement d'Aerodynamique Appliquee - DAAP/ACI
8 rue des Vertugadins
92190 MEUDON - FRANCE
phone : +33 1 46 73 42 17
fax : +33 1 46 73 41 46
mailto:richard.gre...@onera.fr
http://www.onera.fr
___
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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] camera position
Hello everyone, Who knows how can I know current camera position in ParaView? You may click on the "Adjust Camera" button which is the rightmost button of the left group of buttons in the bar above the 3D window. It opens the "Adjust Camera" window where you can see and save the current camera parameters. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] camera position
First set your camera up. Next, open Tools->Python Shell and type: camera = GetActiveCamera() All your current camera settings will be accessable in 'camera'. The member functions to access the specific values can be listed using dir(camera). Adriano === Adriano Gagliardi MEng PhD Business Sector Leader Computational Aerodynamics Aircraft Research Association Ltd. Manton Lane Bedford Tel: 01234 32 4644 E-mail: agaglia...@ara.co.uk Url: www.ara.co.uk -Original Message- From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On Behalf Of Xueli Wang Sent: 26 November 2010 11:50 To: paraview@paraview.org Subject: [Paraview] camera position Hello everyone, Who knows how can I know current camera position in ParaView? Thanks! Xueli Wang ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ** This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ** ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Normals consistency on a Multi-block dataset of surfaces
Richard GRENON wrote: Hello all. Could someone tell me if there is a simple way to get Normals consistency over a multi-block dataset that contains only structured surfaces grids? Here is my problem: I have a multi-zone Tecplot file that contains the skin of the right part of an aircraft, so the skin is NOT closed in the symmetry plane. The skin is a collection of structured IxJ ordered surface grids. The orientation of the surface grids are not consistent, some grids having normals pointing outward, other grids having normals pointing inward, and I need all normals pointing the same direction for Surface Flow integration. The Tecplot reader gives a multi-block dataset and I am using these filters for rendering: Tecplot reader->Extract Surface->Generate Surface Normals The Generate Surface Normals filter is used with Consistency property on (the default). Also rendering with light is OK, adding the NormalGlyph filter shows that normals are still inconsistent, each surface grid keeping its orientation, and using the Surface Flow filter with any vector gives bad results. Thank you in advance for any suggestion. Best regards. Shame on me! I have found the (very simple) Solution! Just add the "Merge Blocks" filter between the Tecplot reader and the "Extract Surface" filter, and it gives an unstructured grid. Now the Consistency property of the "Generate Normals" is taken into account and "Surface flow" gives good results. I hope that this will help other people. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] camera position
Hello everyone, Who knows how can I know current camera position in ParaView? Thanks! Xueli Wang ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Problem with Transform filter
Paul, I've just checked that out and, by applying the filter twice after each vector creation it works now. That has completely caught me out. I assumed (not a good thing clearly) that the filter would transform the entire data-set, but at least it explains why only a single vector was getting converted to a float. Thanks again for pointing this out. Regards, Adriano === Adriano Gagliardi MEng PhD Business Sector Leader Computational Aerodynamics Aircraft Research Association Ltd. Manton Lane Bedford Tel: 01234 32 4644 E-mail: agaglia...@ara.co.uk Url: www.ara.co.uk _ From: Paul Edwards [mailto:paul.m.edwa...@gmail.com] Sent: 26 November 2010 08:39 To: agaglia...@ara.co.uk Cc: paraview@paraview.org Subject: Re: [Paraview] Problem with Transform filter When you use the transform filter it will also transform the "active" vectors, i.e. rotating the model will rotate the vectors too. Note: this is very confusing if you have multiple vectors as it is not immediately obvious which one is getting transformed (as only one is "active"). Regards, Paul On 25 Nov 2010 10:44, "Adriano Gagliardi" wrote: Dear All, I've come across some strange behaviour using the transform filter. I have two pipelines that are near identical. Infact, the only difference is the point at which a transform about a single axis is applied. The process is as follows: 1 Read Data 2 Extract Blocks 3 Extract Surface 4 Generate Surface Normals 5 Calculator (create vector, var*Normals) 6 Calculator (create vector from scalars) 7 Integrate data If I apply the transform at any point before step 6, I get one set of integrated values. If I apply it after step 6, then my x components of the first vector & z component of the second vector are completely different (even different signs), but the others still agree well. I noticed that the transform filter was actually converting the value computed in item 6 from a double to a float, so I changed this last night and recompiled. I also changed the vtkPolyDataNormals to use doubles instead of floats. However, neither of these changes has helped the issue. I fail to see why the timing of applying the transform for this case should influence the results so. Have I missed something? Regards, Adriano === Adriano Gagliardi MEng PhD Business Sector Leader Computational Aerodynamics Aircraft Research Association Ltd. Manton Lane Bedford Tel: 01234 32 4644 E-mail: agaglia...@ara.co.uk Url: www.ara.co.uk ** This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ** ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ** This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ** ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Normals consistency on a Multi-block dataset of surfaces
Hello all. Could someone tell me if there is a simple way to get Normals consistency over a multi-block dataset that contains only structured surfaces grids? Here is my problem: I have a multi-zone Tecplot file that contains the skin of the right part of an aircraft, so the skin is NOT closed in the symmetry plane. The skin is a collection of structured IxJ ordered surface grids. The orientation of the surface grids are not consistent, some grids having normals pointing outward, other grids having normals pointing inward, and I need all normals pointing the same direction for Surface Flow integration. The Tecplot reader gives a multi-block dataset and I am using these filters for rendering: Tecplot reader->Extract Surface->Generate Surface Normals The Generate Surface Normals filter is used with Consistency property on (the default). Also rendering with light is OK, adding the NormalGlyph filter shows that normals are still inconsistent, each surface grid keeping its orientation, and using the Surface Flow filter with any vector gives bad results. Thank you in advance for any suggestion. Best regards. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] some tables cannot be located using paraview.simple python api
I found the problem ... In fact, the th z table is refering to Velocity in
my case)... and the for the non-working cases, range are between [0, 0]
And it seems to give problems as this table is used by Glyph2
On Fri, Nov 26, 2010 at 10:11 AM, Laurent Vanboquestal <
laurent.vanboques...@gmail.com> wrote:
> Hello,
>
> I got this message "Could not locate array z in the input" executing code
> coming from Python Trace using Paraview 3.8.1
>
> Any Idea?
>
> The weird things is that my sample code is working fine with some pvd file
> (using vtu files), but not with some others
> However, I can open the "non-working" one with paraview
>
> The code executed is coming from the Python trace of Paraview 3.8.1
> Is there a workaround for this kind of issues?
>
> python test_view2.py
> vtkPVDReader : [ ...]
> vtkPVArrayCalculator : [ ...]
> vtkPVArrayCalculator : [ ...]
> vtkThreshold : [ ...]
>
> Traceback (most recent call last):
> File "test_view2.py", line 297, in
>my_representation7.ColorArrayName = 'z'
> File
> "/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
> line 204, in __setattr__
>setter(self, value)
> File
> "/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
> line 2364, in setProperty
>return self.SetPropertyWithName(propName, value)
> File
> "/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
> line 253, in SetPropertyWithName
>prop.SetData(arg)
> File
> "/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
> line 684, in SetData
>raise ValueError("Could not locate array %s in the input." % arr)
> ValueError: Could not locate array z in the input.
>
> Do you have any idea or workaround to avoid this?
>
> Thanks a lot for your help,
>
> Best Regards,
>
> Laurent
>
> On Tue, Aug 31, 2010 at 4:25 PM, pat marion wrote:
>
>> Laurent sent me the data off list. I took a look at it and determined the
>> problem is something that has already been corrected since the 3.8 release.
>> Here is the problem and how to fix it for those users with v3.8:
>>
>> clip = Clip(...)
>> ...code constructs representations and sets display properties...
>> clip.ClipType.Origin = [...]
>> clip.ClipType.Normal = [...]
>>
>> What is happening is the clip filter is constructed, some properties are
>> set in the constructor, but the properties defining the clip plane are not
>> set until the end of the python script. It is fixed by just moving the code
>> to just after the constructor:
>>
>> clip = Clip(...)
>> clip.ClipType.Origin = [...]
>> clip.ClipType.Normal = [...]
>> ...code constructs representations and sets display properties...
>>
>> This issue will occur for the clip, cut, glyph, and possibly other
>> filters. It was fixed on April 30 with git commit d9119f6be4b10 and exists
>> in the release branch as well.
>>
>> Pat
>>
>>
>>
>> On Tue, Aug 31, 2010 at 3:18 AM, Laurent Vanboquestal <
>> laurent.vanboques...@gmail.com> wrote:
>>
>>> Hello Pat,
>>>
>>> It has been generated using the "trace state button" The generated
>>> code is huge (about 900 lines of python code),
>>>
>>> Regards,
>>>
>>> Laurent
>>>
>>>
>>> On Mon, Aug 30, 2010 at 5:59 PM, pat marion wrote:
>>>
How are you generating the python trace? Is it recorded using the
start/stop trace buttons, or using the trace state button? Is it possible
to attach the python trace script and/or the dataset?
Pat
On Mon, Aug 30, 2010 at 10:28 AM, Laurent Vanboquestal <
laurent.vanboques...@gmail.com> wrote:
> Hi all,
>
> I got some problems with the generated python code using paraview 3.8
> (Python Trace State).
>
> Using paraview GUI, I can load my pvsm file and when selecting "Glyph2"
> in the pipeline browser, I
> can set values like 'Solid Color', 'cellNormal', 'Velocity_Bis', ...
>
> However, when executing the generated code using pvpython, I got this
> error:
>
> vtkPVDReader : [ ...]
> vtkPVArrayCalculator : [ ...]
> vtkPVArrayCalculator : [ ...]
> vtkWarpVector : [ ...]
> vtkPVClipDataSet : [ ...]
> vtkPVArrowSource : [ ...]
> vtkPVGlyphFilter : [ ...]
> Traceback (most recent call last):
> File "p5.py", line 365, in
> DataRepresentation13.ColorArrayName = 'Velocity_bis'
> File
> "/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
> line 204, in __setattr__
> File
> "/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
> line 2361, in setProperty
> File
> "/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/
[Paraview] Some tables cannot be located using paraview.simple python api
Hello,
I got this message "Could not locate array z in the input" executing code
coming from Python Trace using Paraview 3.8.1
Any Idea?
The weird things is that my sample code is working fine with some pvd file
(using vtu files), but not with some others
However, I can open the "non-working" one with paraview
The code executed is coming from the Python trace of Paraview 3.8.1
Is there a workaround for this kind of issues?
python test_view2.py
vtkPVDReader : [ ...]
vtkPVArrayCalculator : [ ...]
vtkPVArrayCalculator : [ ...]
vtkThreshold : [ ...]
Traceback (most recent call last):
File "test_view2.py", line 297, in
my_representation7.ColorArrayName = 'z'
File
"/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
line 204, in __setattr__
setter(self, value)
File
"/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
line 2364, in setProperty
return self.SetPropertyWithName(propName, value)
File
"/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
line 253, in SetPropertyWithName
prop.SetData(arg)
File
"/usr/local/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/site-packages/paraview/servermanager.py",
line 684, in SetData
raise ValueError("Could not locate array %s in the input." % arr)
ValueError: Could not locate array z in the input.
Do you have any idea or workaround to avoid this?
Thanks a lot for your help,
Best Regards,
Laurent
On Tue, Aug 31, 2010 at 4:25 PM, pat marion wrote:
> Laurent sent me the data off list. I took a look at it and determined the
> problem is something that has already been corrected since the 3.8 release.
> Here is the problem and how to fix it for those users with v3.8:
>
> clip = Clip(...)
> ...code constructs representations and sets display properties...
> clip.ClipType.Origin = [...]
> clip.ClipType.Normal = [...]
>
> What is happening is the clip filter is constructed, some properties are
> set in the constructor, but the properties defining the clip plane are not
> set until the end of the python script. It is fixed by just moving the code
> to just after the constructor:
>
> clip = Clip(...)
> clip.ClipType.Origin = [...]
> clip.ClipType.Normal = [...]
> ...code constructs representations and sets display properties...
>
> This issue will occur for the clip, cut, glyph, and possibly other
> filters. It was fixed on April 30 with git commit d9119f6be4b10 and exists
> in the release branch as well.
>
> Pat
>
>
>
> On Tue, Aug 31, 2010 at 3:18 AM, Laurent Vanboquestal <
> laurent.vanboques...@gmail.com> wrote:
>
>> Hello Pat,
>>
>> It has been generated using the "trace state button" The generated
>> code is huge (about 900 lines of python code),
>>
>> Regards,
>>
>> Laurent
>>
>>
>> On Mon, Aug 30, 2010 at 5:59 PM, pat marion wrote:
>>
>>> How are you generating the python trace? Is it recorded using the
>>> start/stop trace buttons, or using the trace state button? Is it possible
>>> to attach the python trace script and/or the dataset?
>>>
>>> Pat
>>>
>>> On Mon, Aug 30, 2010 at 10:28 AM, Laurent Vanboquestal <
>>> laurent.vanboques...@gmail.com> wrote:
>>>
Hi all,
I got some problems with the generated python code using paraview 3.8
(Python Trace State).
Using paraview GUI, I can load my pvsm file and when selecting "Glyph2"
in the pipeline browser, I
can set values like 'Solid Color', 'cellNormal', 'Velocity_Bis', ...
However, when executing the generated code using pvpython, I got this
error:
vtkPVDReader : [ ...]
vtkPVArrayCalculator : [ ...]
vtkPVArrayCalculator : [ ...]
vtkWarpVector : [ ...]
vtkPVClipDataSet : [ ...]
vtkPVArrowSource : [ ...]
vtkPVGlyphFilter : [ ...]
Traceback (most recent call last):
File "p5.py", line 365, in
DataRepresentation13.ColorArrayName = 'Velocity_bis'
File
"/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
line 204, in __setattr__
File
"/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
line 2361, in setProperty
File
"/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
line 253, in SetPropertyWithName
File
"/home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/ParaViewBin/Utilities/VTKPythonWrapping/paraview/servermanager.py",
line 681, in SetData
ValueError: Could not locate array Velocity_bis in the input.
Any idea? Or advice to tackle this issue?
Best Regards,
Laurent
___
Re: [Paraview] Problem with Transform filter
When you use the transform filter it will also transform the "active" vectors, i.e. rotating the model will rotate the vectors too. Note: this is very confusing if you have multiple vectors as it is not immediately obvious which one is getting transformed (as only one is "active"). Regards, Paul On 25 Nov 2010 10:44, "Adriano Gagliardi" wrote: Dear All, I've come across some strange behaviour using the transform filter. I have two pipelines that are near identical. Infact, the only difference is the point at which a transform about a single axis is applied. The process is as follows: 1 Read Data 2 Extract Blocks 3 Extract Surface 4 Generate Surface Normals 5 Calculator (create vector, var*Normals) 6 Calculator (create vector from scalars) 7 Integrate data If I apply the transform at any point before step 6, I get one set of integrated values. If I apply it after step 6, then my x components of the first vector & z component of the second vector are completely different (even different signs), but the others still agree well. I noticed that the transform filter was actually converting the value computed in item 6 from a double to a float, so I changed this last night and recompiled. I also changed the vtkPolyDataNormals to use doubles instead of floats. However, neither of these changes has helped the issue. I fail to see why the timing of applying the transform for this case should influence the results so. Have I missed something? Regards, Adriano === Adriano Gagliardi MEng PhD Business Sector Leader Computational Aerodynamics Aircraft Research Association Ltd. Manton Lane Bedford Tel: 01234 32 4644 E-mail: agaglia...@ara.co.uk Url: www.ara.co.uk ** This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ** ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
