[Paraview] --stereo-type for passive stereo 3D display on LG's new Cinema 3D TV or monitor

2011-06-29 Thread ChoiJiwoong



Hi,

 

Does anyone have any idea how to correctly set the
stereo-type to displaying ParaView on LG’s new passive stereo Cinema 3D TV or
monitor, which uses Film Patterned Retarder (FPR) technique?

Thank you,

 

J


  ___
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] Image Padding : extent problem again

2011-06-29 Thread Jérôme
Thanks for the info, Dominik. Issue monitored -- looking forward to testing!

Jerome

2011/6/29 Dominik Szczerba 

> I was informed that a feature will be added in the next release to at
> option correctly interpret extents at the price of potential
> additional IO.
>
> http://paraview.org/Bug/view.php?id=12298
>
> Dominik
>
> On Wed, Jun 29, 2011 at 8:53 PM, Jérôme  wrote:
> > Hi,
> >
> > A related thread can be found here:
> >http://www.mail-archive.com/paraview@paraview.org/msg02225.html
> > where I also gave some links to previous threads.
> >
> > Briefly, the problem is not that simple to solved: ParaView has rules
> about
> > how data are organized in order to achieve efficient parallel
> visualization
> > for a whole pipeline (ParaView gurus, tell if I am wrong!). You will have
> to
> > play with extent translators, as it had been discussed in a related
> thread.
> >
> > As it is not a bug, but a normal consequence of the basic purpose of
> > ParaView, I didn't submit a feature request. I also didn't try the
> "Extent
> > translator" hack used in a provided plugin (sorry I cannot remember which
> > one, but you will find it in the mailing list archives).
> >
> > Best regards,
> > Jerome
> >
> > 2011/6/29 Burlen Loring 
> >>
> >> Which filter is exhibiting this issue?
> >>
> >> One potential source for such behavior could be that the filter in
> >> question is not updating the WHOLE_EXTENT key in its RequestInformation
> >> implementation, and/or not updating UPDATE_EXTENT correctly in its
> >> REQUEST_DATA implementation. As a result ParView is using the original
> >> extents. But I'd have to look to verify this hypothesis. If you could
> help
> >> me set up the condition I would be willing to take  look.
> >>
> >> Burlen
> >>
> >> On 06/29/2011 10:52 AM, Tinning, Michael (UK) wrote:
> >>
> >> I found this thread from about a year ago... I'm keen to find out if
> there
> >> was any progress on it.
> >>
> >> The problem is that on image-to-image type filters where the extent of
> the
> >> output is greater than the extent of the input, the output image is
> cropped.
> >>
> >> For example, if I have an input of extent [0 60 0 360 0 0] and an output
> >> of extent [0 90 0 60 0 0] the output will be cropped to [0 60 0 60 0 0].
> >> The output extent is unchanged; only the visualization in ParaView is
> >> cropped.
> >>
> >> I am using ParaView 3.10.1
> >>
> >> Thanks,
> >>
> >> Michael
> >> 
> >> This email and any attachments are confidential to the intended
> >> recipient and may also be privileged. If you are not the intended
> >> recipient please delete it from your system and notify the sender.
> >> You should not copy it or use it for any purpose nor disclose or
> >> distribute its contents to any other person.
> >> 
> >>
> >>
> >> ___
> >> 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
> >>
> >
> >
> > ___
> > 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] Merging Coincident Faces

2011-06-29 Thread Dominik Szczerba
It's very easy to customize the existing vtkCleanUnstructuredGrid to
also merge coincident faces, I did it.

Dominik

On Wed, Jun 29, 2011 at 4:50 PM, Randall Hand  wrote:
> I'm working with an Xdmf dataset in ParaView 3.10.1 that has multiple
> unstructured-grid blocks with overlap regions, however doens't seem to
> actually have "ghost" cells.  This means when I extract an isosurface, I
> wind up with perfectly overlapping faces.
>
> I can use the Clean filter to eliminate coincident points, but but
> coincident faces.  As an example, if I use the "Select Cells Through"
> option to select 2 triangles on an overlapping border, I get 4 points
> (normal for 2 triangles) but 5 cells, with perfect overlap.  The results
> from an ASCII VTK File saved to disk:
>
> vtk output
> ASCII
> DATASET POLYDATA
> POINTS 4 float
> 1.37916 0.965356 0.21928
> 1.37129 0.964077 0.218481
> 1.37613 0.958331 0.219823
> 1.36947 0.958944 0.21948
> POLYGONS 5 20
> 3 0 1 2
> 3 2 1 3
> 3 0 1 2
> 3 2 1 3
> 3 2 1 3
>
> Is there any filter in ParaView capable of fixing this? Or does it have
> to be an arduously slow Python script to run in a Programmable Filter?
>
> --
> Randall Hand
> http://www.vizworld.com
>
> ___
> 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] Image Padding : extent problem again

2011-06-29 Thread Dominik Szczerba
I was informed that a feature will be added in the next release to at
option correctly interpret extents at the price of potential
additional IO.

http://paraview.org/Bug/view.php?id=12298

Dominik

On Wed, Jun 29, 2011 at 8:53 PM, Jérôme  wrote:
> Hi,
>
> A related thread can be found here:
>    http://www.mail-archive.com/paraview@paraview.org/msg02225.html
> where I also gave some links to previous threads.
>
> Briefly, the problem is not that simple to solved: ParaView has rules about
> how data are organized in order to achieve efficient parallel visualization
> for a whole pipeline (ParaView gurus, tell if I am wrong!). You will have to
> play with extent translators, as it had been discussed in a related thread.
>
> As it is not a bug, but a normal consequence of the basic purpose of
> ParaView, I didn't submit a feature request. I also didn't try the "Extent
> translator" hack used in a provided plugin (sorry I cannot remember which
> one, but you will find it in the mailing list archives).
>
> Best regards,
> Jerome
>
> 2011/6/29 Burlen Loring 
>>
>> Which filter is exhibiting this issue?
>>
>> One potential source for such behavior could be that the filter in
>> question is not updating the WHOLE_EXTENT key in its RequestInformation
>> implementation, and/or not updating UPDATE_EXTENT correctly in its
>> REQUEST_DATA implementation. As a result ParView is using the original
>> extents. But I'd have to look to verify this hypothesis. If you could help
>> me set up the condition I would be willing to take  look.
>>
>> Burlen
>>
>> On 06/29/2011 10:52 AM, Tinning, Michael (UK) wrote:
>>
>> I found this thread from about a year ago... I'm keen to find out if there
>> was any progress on it.
>>
>> The problem is that on image-to-image type filters where the extent of the
>> output is greater than the extent of the input, the output image is cropped.
>>
>> For example, if I have an input of extent [0 60 0 360 0 0] and an output
>> of extent [0 90 0 60 0 0] the output will be cropped to [0 60 0 60 0 0].
>> The output extent is unchanged; only the visualization in ParaView is
>> cropped.
>>
>> I am using ParaView 3.10.1
>>
>> Thanks,
>>
>> Michael
>> 
>> This email and any attachments are confidential to the intended
>> recipient and may also be privileged. If you are not the intended
>> recipient please delete it from your system and notify the sender.
>> You should not copy it or use it for any purpose nor disclose or
>> distribute its contents to any other person.
>> 
>>
>>
>> ___
>> 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
>>
>
>
> ___
> 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] Merging Coincident Faces

2011-06-29 Thread Berk Geveci
The short answer is no. No such filter exists in ParaView or VTK.

However, this can be done efficiently (no for loops within Python) if
you have ParaView compiled with a Python that has NumPy. All official
3.10 binaries should have this.

Here is the recipe:

- Load data
- Apply programmable filter with the following to assign unique ids to cells:

output.ShallowCopy(inputs[0].VTKObject)
array = numpy.arange(0, output.GetNumberOfCells(), dtype=numpy.int32)
output.CellData.append(array, 'ids')

- Apply Cell Centers

- Apply Clean to merge duplicate cell centers

- Apply programmable filter (input 0 = reader, input 1 = Clean),
output type: unstructured grid, script:

from paraview import vtk
filter = vtk.vtkExtractSelection()
sel = vtk.vtkSelection()
selNode = vtk.vtkSelectionNode()
selNode.SetFieldType(vtk.vtkSelectionNode.CELL)
selNode.SetContentType(vtk.vtkSelectionNode.INDICES)
selNode.SetSelectionList(inputs[1].PointData['ids'].VTKObject)
selNode.GetSelectionList()
sel.AddNode(selNode)
filter.SetInput(1, sel)
filter.SetInput(0, inputs[0].VTKObject)
filter.Update()
output.ShallowCopy(filter.GetOutput())

This should produce an unstructured grid of 2D cells that are unique.
Works only in serial. In parallel, you need to reduce the polydata to
1 node using All to N.

-berk

On Wed, Jun 29, 2011 at 10:50 AM, Randall Hand  wrote:
> I'm working with an Xdmf dataset in ParaView 3.10.1 that has multiple
> unstructured-grid blocks with overlap regions, however doens't seem to
> actually have "ghost" cells.  This means when I extract an isosurface, I
> wind up with perfectly overlapping faces.
>
> I can use the Clean filter to eliminate coincident points, but but
> coincident faces.  As an example, if I use the "Select Cells Through"
> option to select 2 triangles on an overlapping border, I get 4 points
> (normal for 2 triangles) but 5 cells, with perfect overlap.  The results
> from an ASCII VTK File saved to disk:
>
> vtk output
> ASCII
> DATASET POLYDATA
> POINTS 4 float
> 1.37916 0.965356 0.21928
> 1.37129 0.964077 0.218481
> 1.37613 0.958331 0.219823
> 1.36947 0.958944 0.21948
> POLYGONS 5 20
> 3 0 1 2
> 3 2 1 3
> 3 0 1 2
> 3 2 1 3
> 3 2 1 3
>
> Is there any filter in ParaView capable of fixing this? Or does it have
> to be an arduously slow Python script to run in a Programmable Filter?
>
> --
> Randall Hand
> http://www.vizworld.com
>
> ___
> 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] Image Padding : extent problem again

2011-06-29 Thread Jérôme
Hi,

A related thread can be found here:
   http://www.mail-archive.com/paraview@paraview.org/msg02225.html
where I also gave some links to previous threads.

Briefly, the problem is not that simple to solved: ParaView has rules about
how data are organized in order to achieve efficient parallel visualization
for a whole pipeline (ParaView gurus, tell if I am wrong!). You will have to
play with extent translators, as it had been discussed in a related thread.

As it is not a bug, but a normal consequence of the basic purpose of
ParaView, I didn't submit a feature request. I also didn't try the "Extent
translator" hack used in a provided plugin (sorry I cannot remember which
one, but you will find it in the mailing list archives).

Best regards,
Jerome

2011/6/29 Burlen Loring 

> **
> Which filter is exhibiting this issue?
>
> One potential source for such behavior could be that the filter in question
> is not updating the WHOLE_EXTENT key in its RequestInformation
> implementation, and/or not updating UPDATE_EXTENT correctly in its
> REQUEST_DATA implementation. As a result ParView is using the original
> extents. But I'd have to look to verify this hypothesis. If you could help
> me set up the condition I would be willing to take  look.
>
> Burlen
>
>
> On 06/29/2011 10:52 AM, Tinning, Michael (UK) wrote:
>
> I found this thread from about a year ago... I'm keen to find out if there
> was any progress on it.
>
> The problem is that on image-to-image type filters where the extent of the
> output is greater than the extent of the input, the output image is cropped.
>
> For example, if I have an input of extent [0 60 0 360 0 0] and an output of
> extent [0 90 0 60 0 0] the output will be cropped to [0 60 0 60 0 0].  The
> output extent is unchanged; only the visualization in ParaView is cropped.
>
> I am using ParaView 3.10.1
>
> Thanks,
>
> Michael
>
> 
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> 
>
>
> ___
> 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
>
>
___
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] Delayed Set of WHOLE_EXTENT

2011-06-29 Thread Dennis McWherter
Is there a safe/proper way to update the WHOLE_EXTENT from a filter without
knowing the extent at the initial call of RequestInformation()? That is, I
may need a way to override such information in subsequent RequestData calls
(if it would be safe to do so).

The basic design to my problem is that the extent information is located
within a drop-down in the GUI loaded by the plugin. That said, I will not
have the extent information until after the user has selected an option from
the drop-down (hypothetically, my second call to RequestData just before
displaying the object).

If it is not possible to resolve this issue in such a manner, is there a
better way to accomplish this task?

Regards,
Dennis McWherter
___
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] Image Padding : extent problem again

2011-06-29 Thread Burlen Loring

Which filter is exhibiting this issue?

One potential source for such behavior could be that the filter in 
question is not updating the WHOLE_EXTENT key in its RequestInformation 
implementation, and/or not updating UPDATE_EXTENT correctly in its 
REQUEST_DATA implementation. As a result ParView is using the original 
extents. But I'd have to look to verify this hypothesis. If you could 
help me set up the condition I would be willing to take  look.


Burlen

On 06/29/2011 10:52 AM, Tinning, Michael (UK) wrote:
I found this thread from about a year ago... I'm keen to find out if 
there was any progress on it.
The problem is that on image-to-image type filters where the extent of 
the output is greater than the extent of the input, the output image 
is cropped.
For example, if I have an input of extent [0 60 0 360 0 0] and an 
output of extent [0 90 0 60 0 0] the output will be cropped to [0 60 0 
60 0 0].  The output extent is unchanged; only the visualization in 
ParaView is cropped.

I am using ParaView 3.10.1
Thanks,
Michael


This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.



___
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] Image Padding : extent problem again

2011-06-29 Thread Tinning, Michael (UK)
I found this thread from about a year ago... I'm keen to find out if
there was any progress on it.
 
The problem is that on image-to-image type filters where the extent of
the output is greater than the extent of the input, the output image is
cropped.
 
For example, if I have an input of extent [0 60 0 360 0 0] and an output
of extent [0 90 0 60 0 0] the output will be cropped to [0 60 0 60 0 0].
The output extent is unchanged; only the visualization in ParaView is
cropped.
 
I am using ParaView 3.10.1
 
Thanks,
 
Michael


This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.


___
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] Make install still does not work in 3.10.1

2011-06-29 Thread Utkarsh Ayachit
Bastian,

Make install should work. If you can elaborate on the issues you are
having, we can track it down. Also note everyone has different
expectations with "make install", some want the 3rd party dependencies
such as Qt, installed, others don't. It starts getting confusing
pretty quickly. So, if I am not mistaken, the default "make install"
doesn't make any attempts to install libraries not built by ParaView
itself. However it provides mechanisms to import additional cmake
files with custom rules to install any dependencies.

Utkarsh

On Wed, Jun 29, 2011 at 1:13 PM, bastil2...@yahoo.de
 wrote:
> Hi all,
>
> I still have the same issue with 3.10.1 which I already had in 3.10.0:
>
> http://www.mail-archive.com/paraview@paraview.org/msg11218.html
>
> Am I the only one with such problems? I want to get this solved - what
> can I do? Shall I submit a bug?
>
> Regards Bastian
> ___
> 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] Make install still does not work in 3.10.1

2011-06-29 Thread Scott, W Alan
I think I have seen something like this.  Make sure that a different version of 
qt isn't found earlier in your path or LD_LIBRARY_PATH.  This includes installs 
of other applications...

Hope that helps,

Alan

-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On 
Behalf Of bastil2...@yahoo.de
Sent: Wednesday, June 29, 2011 11:13 AM
To: 'ParaView'
Subject: [Paraview] Make install still does not work in 3.10.1

Hi all,

I still have the same issue with 3.10.1 which I already had in 3.10.0:

http://www.mail-archive.com/paraview@paraview.org/msg11218.html

Am I the only one with such problems? I want to get this solved - what
can I do? Shall I submit a bug?

Regards Bastian
___
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] Make install still does not work in 3.10.1

2011-06-29 Thread bastil2...@yahoo.de
Hi all,

I still have the same issue with 3.10.1 which I already had in 3.10.0:

http://www.mail-archive.com/paraview@paraview.org/msg11218.html

Am I the only one with such problems? I want to get this solved - what
can I do? Shall I submit a bug?

Regards Bastian
___
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] anti aliasing

2011-06-29 Thread Moreland, Kenneth
For what it's worth, real-time anti-aliasing rendering has been turned off in 
ParaView because it wrecks havoc with many of the features involving rendering 
including picking, parallel rendering, transparency rendering, and tiled large 
image screen shots.  Like Vincent suggested, if you need a high-quality screen 
shot, make one that is larger than you need (ParaView can generate arbitrarily 
large screen shots) and then shrink it to the size you want using an 
appropriate smoothing filter (most simple image viewing programs have this 
feature).  If the aliasing is really bothering you while you are using 
ParaView, get a larger display and sit farther back. ;)

-Ken

     Kenneth Moreland
***  Sandia National Laboratories
***
*** *** ***  email: kmo...@sandia.gov
**  ***  **  phone: (505) 844-8919
***  web:   http://www.cs.unm.edu/~kmorel

From: Vincent Faucher mailto:vincent.fauc...@cea.fr>>
Date: Wed, 29 Jun 2011 15:07:54 +0200
To: mailto:paraview@paraview.org>>
Subject: Re: [Paraview] anti aliasing

Hi,

I don't know how to activate anti-aliasing directly in image file output 
process, but a way to achieve it is to render with an increase resolution 
(let's say double ligns and columns, i.e. x4 on pixel numbers) and after to 
externally resize the image files.

Anti-aliasing done by the resizing process, which can be automated with many 
free softwares, generally produces good results.

Regards, Vincent

Le 29/06/2011 14:55, Mattias Chevalier a écrit :
Hello,
I would like to use anti-aliasing on my scenes that I create in ParaView and 
output as image files. I have included 3D-models (.stl triangulated surfaces) 
in the scenes but they look rather poor in certain camera positions without 
anti-aliasing. I haven't found out how to activate this in ParaView though.

/Mattias




___
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

--
[cid:part1.07060008.07060402@cea.fr]


Vincent FAUCHER

Laboratoire d'études de dynamique

CEA Saclay, DEN/DANS/DM2S/SEMT/DYN

F-91191 GIF SUR YVETTE, FRANCE

Tel : +33.1.69.08.40.18

vincent.fauc...@cea.fr








Ce message électronique et tous les fichiers attachés qu'il contient sont 
confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils 
sont adressés. Si vous avez reçu ce message par erreur, merci d'en avertir 
immédiatement son émetteur et de ne pas en conserver de copie.

This e-mail and any files transmitted with it are confidential and intended 
solely for the use of the individual to whom they are addressed. If you have 
received this e-mail in error please inform the sender immediately, without 
keeping any copy thereof.

___ 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] clipped scene with GPU rendering on NVIDIA tesla C1060

2011-06-29 Thread Burlen Loring

Hi Pratik,

I have had some similar issues when my desktop screen resolution was 
higher than the server display resolution. Do you know what the display 
resolution is set to on the server side? I was able to check the server 
side resolution using xrandr command. The issue was fixed by increasing 
the server display resolution in the xorg.conf. This could be one 
possibility for what you are seeing.


Burlen

On 06/29/2011 07:42 AM, pratik wrote:

Hi everyone,
This is my configuration(PV v.3.10.1):
Server: desktop with 4 NVIDIA tesla C1060 cards; Client is a laptop.
To make use of GPU rendering, i start an Xserver on a free display 
like so(i cannot use the :0 display, also i cannot use $DISPLAY. if i 
use the $DISPLAY option, the server disconnects as soon as i load data 
from paraview):


startx -- :14

and my .xinitrc contains

exec xdm

so that xdm executes on the Xserver that is started.
once this is done, i simply run

mpirun -np 4 pvserver -display localhost:14.0
OR
pvserver -display localhost:14.0


Everything goes fine, client connects to server etc. But when the 
actual visualization is done, a strip at the top (roughly 1/3 of 
screen) is blanked(see the attached image). A curious thing that i 
observed was that when i change the orientation, rotate the object 
etc, the LOD actor seems to render properly(meaning that i can see the 
whole picture), but after i let it settle then this clipping takes 
place. Only a few weeks back the rendering seemed to have happened 
perfectly, so i don't know why it is suddenly behaving this way now.


Thanks  in advance for the help.

-pratik


___
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] python shell move data from client to server

2011-06-29 Thread pat marion
If you use the python programmable filter, you can create it & set the
filter routine (python code) via a python macro on the GUI.  If the data you
are trying to manipulate on the GUI is small, you could encode it in a
string and set it in the body of the python programmable filter.

Pat

On Wed, Jun 29, 2011 at 9:49 AM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Nope, moving data from client to server in the way you describe is not
> supported in ParaView. For what you are trying to do, you should
> really implement a filter (with multiple inputs, if needed) to do the
> data-manipulation on the server-side itself.
>
> Utkarsh
>
> On Wed, Jun 29, 2011 at 5:23 AM, Florian Beck  wrote:
> > Hi,
> >
> > I want to create a DataObjectGenerator with an unstructered Grid. And
> when later I want to modify the grid. My try looks as follows:
> >
> >
> > # create the DataObjectGenerator
> > DataObjectGenerator1 = DataObjectGenerator()
> > DataObjectGenerator1.Program ='UG1'
> >
> > # read some coord from over objects
> > ...
> >
> > # to manipulate the grid fetch it
> > mysource = FindSource("DataObjectGenerator1")
> > output = servermanger.Fetch(mysource)
> > # clean old data
> > output.Initialize()
> >
> > # create some points and  triangle cells
> > pts = pts.vtkPoints()
> > ...
> > output.SetPoints(pts)
> > ...
> > pointIds = vtk.vtkIdList()
> > ...
> > output.InsertNextCell(5,pointIds)
> > ...
> > # print the ugrid object
> > print output
> > mysource.UpdatePipeline()
> > Render()
> >
> > My problem is after i manipulate the ugrid on the client side there, i
> can't move it to the server side??? Is there a solution to connect the
> manipulated ugrid at server side with my DataObjectGenerator ?  I know there
> are the programmable source, but i need data from other objects to
> manipulate the grid and i want to use my python script as macro.
> >
> > regards flo
> > --
> > NEU: FreePhone - kostenlos mobil telefonieren!
> > Jetzt informieren: http://www.gmx.net/de/go/freephone
> >
> >
> > --
> > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
> > ___
> > 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
>
___
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] How to Programatically add Items to drop down list?

2011-06-29 Thread janaki prasad
Hi,
I am writing a new vtk source and I need to programmatically populate a drop
down list in the object-inspector/Properties from RequestInformation(). Are
there any examples/code snippets that I could look at to help me do this?
I defined the static drop down list this way so far,

-
-




 
 This property indicates which transform mode will be used.
 
 


Thanks,
Janaki Duggirala
___
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] FW: FW: Coloured isosurfaces when running MPI

2011-06-29 Thread Philipp Schlatter

Thanks a lot for the help!
Concerning the suggested workaround, I have a follow-up question: How  
would one get the Gouraud shading of the isocontours working? In my case I  
will get properly coloured isocontours, but they seem to have uniform  
shade for each triangle as opposed to an interpolated shade.


Thanks,
philipp

On Wed, 29 Jun 2011 14:34:34 +0200, Karl König  wrote:


Hi Philipp,

It seems you have hit a bug in the Contour filter occurring with > 1
pvserver process and rectilinear grid input. I can reproduce the issue
you reported as such:

Load ParaView, connect to > 1 pvserver processes
Open Data/RectGrid2.vtk (e.g. from git://vtk.org/VTKData.git)
Calculator filter, operation: "coordsX",
Result Array Name: "Result", Apply
Contour filter, Contour by "scalars", Compute Normals,
Isosurface Value 0.5, Apply
Representation "Surface", Color by "Result"

With 1 pvserver process the surface coloring is indeed a single smooth
gradient while with more than 1 pvserver process the gradient starts
anew at half the X range. If applying an additional "Process ID Scalars"
filter, one can confirm that the "reset" happens at a process boundary.

Converting the rectilinear grid to an unstructured grid prior to
applying the contour filter may serve as as a workaround. The filters
"Clean to Grid", "Tetrahedralize" and "Tesselate" all do that trick
(they are listed with increasing memory footprint). So, I recommend
using "Clean to Grid" somewhere before applying the contour filter in
the parallel case.

Karl



Philipp Schlatter wrote, On 29.06.2011 11:50:

Hi!
Thanks for the answer. Let me give some comments to your questions:
- I am using the distributed 3.10.1 binaries (32 bit), and I tried it on
a Ubuntu 11.04 system (older dualcore T60p)
- I used now the sample dataset Data/RectGrid2.vtk. Using the calculator
operation "CoordsX", I can reproduce the behaviour I was originally
describing. I simply use the Contour filter ("Compute Scalars" did not
change the behaviour). I have uploaded 3 more screenshots:


http://www.mech.kth.se/~pschlatt/files/Screenshot3.png
is the intended result, obtained using a single core (no Auto-MPI etc.)

http://www.mech.kth.se/~pschlatt/files/Screenshot2.png
is the result obtained with Auto-MPI, running on my two cores.

http://www.mech.kth.se/~pschlatt/files/Screenshot1.png
is the result obtained with explicitly initiating paraview and pvserver
using a total of 16 MPI ranks.

I tried all/most of the rendering options (LOD etc.), however it did not
help. Also, I have run on 64 bit version at the computer centre (with
older versions though), and the same problem appears there too.

I am really puzzled by the fact that you could not reproduce the
problem. Could there be some setting that is for some reason wrong in my
setup?

Best regards,
Philipp


On Tue, 28 Jun 2011 18:36:25 +0200, Karl König  wrote:


Hi Philipp,

A couple of questions:
* Are you using the distributed 3.10.1 binaries or did you compile PV
3.10.1 from source yourself?
* Can you reproduce the behavior with the sample dataset
Data/RectGrid2.vtk (part of both git://vtk.org/VTKData.git and
http://www.paraview.org/files/v3.10/ParaViewData-3.10.1.zip)? That's
also a "Rectilinear Grid". Using the Calculator operation "1 +
coordsX*coordsY" followed by a Contour filter with "Compute Scalars"
checked and 10 auto-chosen values, I got identical results with 1 and  
16

cores (using PV 3.10.1 Linux 64-bit binaries and Windows 64-bit
binaries, relying on Auto-MPI ("Settings" - "Use Multi-Core") for the  
16

core case)

Karl


Philipp Schlatter wrote, On 28.06.2011 17:50:

Dear all,
Unfortunately, I am still struggling with running MPI and producing
coloured
isosurfaces. A screenshot exemplifying the problem can be found at
http://www.mech.kth.se/~pschlatt/files/Screenshot.png; note that the
colour
scheme based on the x-coordinate is just to show the problem, but in
reality
I am using some scalar data coming from file.

Anyway, I wanted to ask you whether any of you has had similar  
problems,

i.e. colouring isosurfaces when running MPI. It seems to me that the
data
field used to colour the surfaces is only created on one MPI rank and
then
used by all other ranks, instead of computed for each rank  
independently

based on the local data. Can anyone confirm that behaviour?

This problem makes it at the moment impossible for me to visualise a
certain
very large data set as I need to use MPI to distribute the data due to
memory limitation.

Thanks a lot for any help!

Philipp

-Original Message-
From: Philipp Schlatter [mailto:pschl...@mech.kth.se]
Sent: den 20 juni 2011 22:55
To: 'Utkarsh Ayachit'
Cc: paraview@paraview.org
Subject: RE: [Paraview] FW: Coloured isosurfaces when running MPI

Dear Utkarsh,
Thanks a lot for your answer. The type of my data is "Rectilinear  
Grid"

(turbulence data on a regular grid). The test case that I use to
reproduce
the data leads to a size of the contours (from the statistics

[Paraview] VTK File (PolyLines+Arrays) Crashes ParaView 3.10.1 when Rotated

2011-06-29 Thread Dennis McWherter
Hello,

I have generated a Legacy VTK file using VTK's Python wrapper. This file
crashes ParaView 3.10.1 (Windows 7) when attempting to rotate it in
ParaView's viewport, however, it seems that I can appropriately apply
filters and such. However, this data did work properly on ParaView 3.8.1.

If anyone can help in inspecting the file for potential bugs, it can be
found here (~55MB):
https://netfiles.uiuc.edu/xythoswfs/webview/_xy-22178502_2

ParaView crashes in vtkQuadricClustering::AddEdges at this line:

points->GetPoint(ptIds[0], pt0);

ptIds is NULL.

The data itself is a PolyData object with PolyLines and arrays. I presume
there may be a bad/missing data structure within the data, can any ParaView
expert shed some light on the issue?

Regards,
Dennis McWherter
___
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] Merging Coincident Faces

2011-06-29 Thread Randall Hand
I'm working with an Xdmf dataset in ParaView 3.10.1 that has multiple
unstructured-grid blocks with overlap regions, however doens't seem to
actually have "ghost" cells.  This means when I extract an isosurface, I
wind up with perfectly overlapping faces.

I can use the Clean filter to eliminate coincident points, but but
coincident faces.  As an example, if I use the "Select Cells Through"
option to select 2 triangles on an overlapping border, I get 4 points
(normal for 2 triangles) but 5 cells, with perfect overlap.  The results
from an ASCII VTK File saved to disk:

vtk output
ASCII
DATASET POLYDATA
POINTS 4 float
1.37916 0.965356 0.21928
1.37129 0.964077 0.218481
1.37613 0.958331 0.219823
1.36947 0.958944 0.21948
POLYGONS 5 20
3 0 1 2
3 2 1 3
3 0 1 2
3 2 1 3
3 2 1 3

Is there any filter in ParaView capable of fixing this? Or does it have
to be an arduously slow Python script to run in a Programmable Filter? 

-- 
Randall Hand
http://www.vizworld.com

___
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] python shell move data from client to server

2011-06-29 Thread Utkarsh Ayachit
Nope, moving data from client to server in the way you describe is not
supported in ParaView. For what you are trying to do, you should
really implement a filter (with multiple inputs, if needed) to do the
data-manipulation on the server-side itself.

Utkarsh

On Wed, Jun 29, 2011 at 5:23 AM, Florian Beck  wrote:
> Hi,
>
> I want to create a DataObjectGenerator with an unstructered Grid. And when 
> later I want to modify the grid. My try looks as follows:
>
>
> # create the DataObjectGenerator
> DataObjectGenerator1 = DataObjectGenerator()
> DataObjectGenerator1.Program ='UG1'
>
> # read some coord from over objects
> ...
>
> # to manipulate the grid fetch it
> mysource = FindSource("DataObjectGenerator1")
> output = servermanger.Fetch(mysource)
> # clean old data
> output.Initialize()
>
> # create some points and  triangle cells
> pts = pts.vtkPoints()
> ...
> output.SetPoints(pts)
> ...
> pointIds = vtk.vtkIdList()
> ...
> output.InsertNextCell(5,pointIds)
> ...
> # print the ugrid object
> print output
> mysource.UpdatePipeline()
> Render()
>
> My problem is after i manipulate the ugrid on the client side there, i can't 
> move it to the server side??? Is there a solution to connect the manipulated 
> ugrid at server side with my DataObjectGenerator ?  I know there are the 
> programmable source, but i need data from other objects to manipulate the 
> grid and i want to use my python script as macro.
>
> regards flo
> --
> NEU: FreePhone - kostenlos mobil telefonieren!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>
>
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
> ___
> 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] anti aliasing

2011-06-29 Thread Vincent Faucher


  
  
Hi,

I don't know how to activate anti-aliasing directly in image file
output process, but a way to achieve it is to render with an
increase resolution (let's say double ligns and columns, i.e. x4 on
pixel numbers) and after to externally resize the image files.

Anti-aliasing done by the resizing process, which can be automated
with many free softwares, generally produces good results.

Regards, Vincent

Le 29/06/2011 14:55, Mattias Chevalier a écrit :
Hello,
  I would like to use anti-aliasing on my scenes that I create
in ParaView and output as image files. I have included 3D-models
(.stl triangulated surfaces) in the scenes but they look rather
poor in certain camera positions without anti-aliasing. I
haven't found out how to activate this in ParaView though.
  
  
  /Mattias
  
  
  
  
  

___
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



-- 
  

  

  

  
  
Vincent
  FAUCHER
Laboratoire d'études de
dynamique
CEA Saclay,
  DEN/DANS/DM2S/SEMT/DYN
F-91191 GIF SUR
  YVETTE, FRANCE
Tel : +33.1.69.08.40.18
vincent.fauc...@cea.fr
  

  

  
  
  
  
  
  
  
  Ce message électronique et
  tous les fichiers attachés qu'il contient sont confidentiels
  et destinés exclusivement à l'usage de la personne à laquelle
  ils sont adressés. Si vous avez reçu ce message par erreur,
  merci d'en avertir immédiatement son émetteur et de ne pas en
  conserver de copie.
  This e-mail and any files
  transmitted with it are confidential and intended solely for
  the use of the individual to whom they are addressed. If you
  have received this e-mail in error please inform the sender
  immediately, without keeping any copy thereof.


  

___
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] anti aliasing

2011-06-29 Thread Mattias Chevalier
Hello,
I would like to use anti-aliasing on my scenes that I create in ParaView and
output as image files. I have included 3D-models (.stl triangulated
surfaces) in the scenes but they look rather poor in certain camera
positions without anti-aliasing. I haven't found out how to activate this in
ParaView though.

/Mattias
___
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] FW: FW: Coloured isosurfaces when running MPI

2011-06-29 Thread Karl König
Hi Philipp,

It seems you have hit a bug in the Contour filter occurring with > 1
pvserver process and rectilinear grid input. I can reproduce the issue
you reported as such:

Load ParaView, connect to > 1 pvserver processes
Open Data/RectGrid2.vtk (e.g. from git://vtk.org/VTKData.git)
Calculator filter, operation: "coordsX",
Result Array Name: "Result", Apply
Contour filter, Contour by "scalars", Compute Normals,
Isosurface Value 0.5, Apply
Representation "Surface", Color by "Result"

With 1 pvserver process the surface coloring is indeed a single smooth
gradient while with more than 1 pvserver process the gradient starts
anew at half the X range. If applying an additional "Process ID Scalars"
filter, one can confirm that the "reset" happens at a process boundary.

Converting the rectilinear grid to an unstructured grid prior to
applying the contour filter may serve as as a workaround. The filters
"Clean to Grid", "Tetrahedralize" and "Tesselate" all do that trick
(they are listed with increasing memory footprint). So, I recommend
using "Clean to Grid" somewhere before applying the contour filter in
the parallel case.

Karl



Philipp Schlatter wrote, On 29.06.2011 11:50:
> Hi!
> Thanks for the answer. Let me give some comments to your questions:
> - I am using the distributed 3.10.1 binaries (32 bit), and I tried it on
> a Ubuntu 11.04 system (older dualcore T60p)
> - I used now the sample dataset Data/RectGrid2.vtk. Using the calculator
> operation "CoordsX", I can reproduce the behaviour I was originally
> describing. I simply use the Contour filter ("Compute Scalars" did not
> change the behaviour). I have uploaded 3 more screenshots:
> 
> 
> http://www.mech.kth.se/~pschlatt/files/Screenshot3.png
> is the intended result, obtained using a single core (no Auto-MPI etc.)
> 
> http://www.mech.kth.se/~pschlatt/files/Screenshot2.png
> is the result obtained with Auto-MPI, running on my two cores.
> 
> http://www.mech.kth.se/~pschlatt/files/Screenshot1.png
> is the result obtained with explicitly initiating paraview and pvserver
> using a total of 16 MPI ranks.
> 
> I tried all/most of the rendering options (LOD etc.), however it did not
> help. Also, I have run on 64 bit version at the computer centre (with
> older versions though), and the same problem appears there too.
> 
> I am really puzzled by the fact that you could not reproduce the
> problem. Could there be some setting that is for some reason wrong in my
> setup?
> 
> Best regards,
> Philipp
> 
> 
> On Tue, 28 Jun 2011 18:36:25 +0200, Karl König  wrote:
> 
>> Hi Philipp,
>>
>> A couple of questions:
>> * Are you using the distributed 3.10.1 binaries or did you compile PV
>> 3.10.1 from source yourself?
>> * Can you reproduce the behavior with the sample dataset
>> Data/RectGrid2.vtk (part of both git://vtk.org/VTKData.git and
>> http://www.paraview.org/files/v3.10/ParaViewData-3.10.1.zip)? That's
>> also a "Rectilinear Grid". Using the Calculator operation "1 +
>> coordsX*coordsY" followed by a Contour filter with "Compute Scalars"
>> checked and 10 auto-chosen values, I got identical results with 1 and 16
>> cores (using PV 3.10.1 Linux 64-bit binaries and Windows 64-bit
>> binaries, relying on Auto-MPI ("Settings" - "Use Multi-Core") for the 16
>> core case)
>>
>> Karl
>>
>>
>> Philipp Schlatter wrote, On 28.06.2011 17:50:
>>> Dear all,
>>> Unfortunately, I am still struggling with running MPI and producing
>>> coloured
>>> isosurfaces. A screenshot exemplifying the problem can be found at
>>> http://www.mech.kth.se/~pschlatt/files/Screenshot.png; note that the
>>> colour
>>> scheme based on the x-coordinate is just to show the problem, but in
>>> reality
>>> I am using some scalar data coming from file.
>>>
>>> Anyway, I wanted to ask you whether any of you has had similar problems,
>>> i.e. colouring isosurfaces when running MPI. It seems to me that the
>>> data
>>> field used to colour the surfaces is only created on one MPI rank and
>>> then
>>> used by all other ranks, instead of computed for each rank independently
>>> based on the local data. Can anyone confirm that behaviour?
>>>
>>> This problem makes it at the moment impossible for me to visualise a
>>> certain
>>> very large data set as I need to use MPI to distribute the data due to
>>> memory limitation.
>>>
>>> Thanks a lot for any help!
>>>
>>> Philipp
>>>
>>> -Original Message-
>>> From: Philipp Schlatter [mailto:pschl...@mech.kth.se]
>>> Sent: den 20 juni 2011 22:55
>>> To: 'Utkarsh Ayachit'
>>> Cc: paraview@paraview.org
>>> Subject: RE: [Paraview] FW: Coloured isosurfaces when running MPI
>>>
>>> Dear Utkarsh,
>>> Thanks a lot for your answer. The type of my data is "Rectilinear Grid"
>>> (turbulence data on a regular grid). The test case that I use to
>>> reproduce
>>> the data leads to a size of the contours (from the statistics inspector)
>>> 230316 cells, and a memory of 15 MB. I have turned off all the remote
>>> render
>>> thresholds etc. and the problem 

Re: [Paraview] GUI

2011-06-29 Thread Utkarsh Ayachit
Posting back to the list just to close the thread :).

Utkarsh

2011/6/29 papa ndéné NDIAYE :
> ok, sorry I found out I just didn't look carefully enough at all the create
> filter methods for pqObjectBuilder.
>
> thank you again.
>
> 2011/6/29 papa ndéné NDIAYE 
>>
>> great thanks Utkarsh,  I now understand how the indexes work there.
>> but I still don't know how to build my extractblock filter.
>> I mean to set the "Indices" property of the extractblock filter without
>> using the GUI.
>> I know we can get properties from vtkSMProxy::GetProperty
>> but I don't find a way to set them.
>>
>> I thank you in advance
>>
>> Papa
>>
>> 2011/6/29 Utkarsh Ayachit 
>>>
>>> You can get access to the composite dataset information using the data
>>> information (vtkPVDataInformation::GetCompositeDataInformation()). To
>>> find the number of blocks 1 level deep, simply do:
>>>
>>> dataInfo->GetCompositeDataInformation()->GetNumberOfChildren().
>>>
>>> Determining the index for each of those children can be a little
>>> tricky. The index of a node is the position of that node in a
>>> pre-order traversal of that tree. So you the index of root is 0, while
>>> that of it's first child is 1. However for the second child you have
>>> to count the number of nodes in the entire subtree from Child0 and
>>> then and that to the index of Child0 i.e. ( index of left sibling +
>>> number of nodes in sub-tree rooted at left sibling).
>>>
>>> vtkPVCompositeDataInformation itself provides access to the data
>>> information of the child nodes, so using that you can traverse the
>>> entire composite data tree structure. You can also use
>>> vtkPVCompositeDataInformationIterator to traverse the tree.
>>> vtkPVCompositeDataInformationIterator provides a GetFlatIndex() API to
>>> obtain the index for any particular node.
>>>
>>> Utkarsh
>>>
>>> 2011/6/28 papa ndéné NDIAYE :
>>> > Hi all,
>>> >
>>> > I have a reader that produces a multiblock dataset and
>>> > want to add a GUI plug-in that applies the extract block filter
>>> > just changing the index to have all blocks (one level deep) extracted
>>> > in
>>> > different objects.
>>> > I think about a loop calling the createfilter method of the builder
>>> > with
>>> > "extractblock".
>>> > do you know how to get the number of blocks and how to set the index of
>>> > the
>>> > block i want to extract without using the GUI?
>>> >
>>> > thanks!!
>>> >
>>> > ___
>>> > 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] FW: FW: Coloured isosurfaces when running MPI

2011-06-29 Thread Philipp Schlatter

Hi!
Thanks for the answer. Let me give some comments to your questions:
- I am using the distributed 3.10.1 binaries (32 bit), and I tried it on a  
Ubuntu 11.04 system (older dualcore T60p)
- I used now the sample dataset Data/RectGrid2.vtk. Using the calculator  
operation "CoordsX", I can reproduce the behaviour I was originally  
describing. I simply use the Contour filter ("Compute Scalars" did not  
change the behaviour). I have uploaded 3 more screenshots:



http://www.mech.kth.se/~pschlatt/files/Screenshot3.png
is the intended result, obtained using a single core (no Auto-MPI etc.)

http://www.mech.kth.se/~pschlatt/files/Screenshot2.png
is the result obtained with Auto-MPI, running on my two cores.

http://www.mech.kth.se/~pschlatt/files/Screenshot1.png
is the result obtained with explicitly initiating paraview and pvserver  
using a total of 16 MPI ranks.


I tried all/most of the rendering options (LOD etc.), however it did not  
help. Also, I have run on 64 bit version at the computer centre (with  
older versions though), and the same problem appears there too.


I am really puzzled by the fact that you could not reproduce the problem.  
Could there be some setting that is for some reason wrong in my setup?


Best regards,
Philipp


On Tue, 28 Jun 2011 18:36:25 +0200, Karl König  wrote:


Hi Philipp,

A couple of questions:
* Are you using the distributed 3.10.1 binaries or did you compile PV
3.10.1 from source yourself?
* Can you reproduce the behavior with the sample dataset
Data/RectGrid2.vtk (part of both git://vtk.org/VTKData.git and
http://www.paraview.org/files/v3.10/ParaViewData-3.10.1.zip)? That's
also a "Rectilinear Grid". Using the Calculator operation "1 +
coordsX*coordsY" followed by a Contour filter with "Compute Scalars"
checked and 10 auto-chosen values, I got identical results with 1 and 16
cores (using PV 3.10.1 Linux 64-bit binaries and Windows 64-bit
binaries, relying on Auto-MPI ("Settings" - "Use Multi-Core") for the 16
core case)

Karl


Philipp Schlatter wrote, On 28.06.2011 17:50:

Dear all,
Unfortunately, I am still struggling with running MPI and producing  
coloured

isosurfaces. A screenshot exemplifying the problem can be found at
http://www.mech.kth.se/~pschlatt/files/Screenshot.png; note that the  
colour
scheme based on the x-coordinate is just to show the problem, but in  
reality

I am using some scalar data coming from file.

Anyway, I wanted to ask you whether any of you has had similar problems,
i.e. colouring isosurfaces when running MPI. It seems to me that the  
data
field used to colour the surfaces is only created on one MPI rank and  
then

used by all other ranks, instead of computed for each rank independently
based on the local data. Can anyone confirm that behaviour?

This problem makes it at the moment impossible for me to visualise a  
certain

very large data set as I need to use MPI to distribute the data due to
memory limitation.

Thanks a lot for any help!

Philipp

-Original Message-
From: Philipp Schlatter [mailto:pschl...@mech.kth.se]
Sent: den 20 juni 2011 22:55
To: 'Utkarsh Ayachit'
Cc: paraview@paraview.org
Subject: RE: [Paraview] FW: Coloured isosurfaces when running MPI

Dear Utkarsh,
Thanks a lot for your answer. The type of my data is "Rectilinear Grid"
(turbulence data on a regular grid). The test case that I use to  
reproduce

the data leads to a size of the contours (from the statistics inspector)
230316 cells, and a memory of 15 MB. I have turned off all the remote  
render
thresholds etc. and the problem persists. Thus it is likely that it is  
the

contour filter that causes the miscolouring.

I have just reroduced the problem using the latest version 3.10.1 (Linux
32-bit); and I generated a screenshot on
http://www.mech.kth.se/~pschlatt/files/Screenshot.png.

The test is simple; I read in a rectilinear grid with a few velocity
components. Then I compute a new scalar field, essentially being the
x-corrdinate. Then I plot an isocontour, and colour it with the result  
of
the calculator. I would expect a continuous colour going from blue to  
red

spread over the whole x extent, however - according to the number of
processors used (in that case 16) - I get a repetitive pattern. By some  
more
experimenting it becomes clear that for some reason the colouring is  
done

based on the scalar value on the first processor only.

Running on 1 processor everything is fine.

I am of course happy to provide the respective data files, if this could
help.

Thanks for any help!
Best regards,
Philipp


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: den 20 juni 2011 16:59
To: Philipp Schlatter
Cc: paraview@paraview.org
Subject: Re: [Paraview] FW: Coloured isosurfaces when running MPI

That's very peculiar. What datatype are you contouring? (With the reader
selected in the pipeline browser, go to the information tab, what does  
the

"Type" field say?) Also after generating the iso-surfac

[Paraview] python shell move data from client to server

2011-06-29 Thread Florian Beck
Hi, 

I want to create a DataObjectGenerator with an unstructered Grid. And when 
later I want to modify the grid. My try looks as follows:


# create the DataObjectGenerator
DataObjectGenerator1 = DataObjectGenerator()
DataObjectGenerator1.Program ='UG1'

# read some coord from over objects
...

# to manipulate the grid fetch it
mysource = FindSource("DataObjectGenerator1")
output = servermanger.Fetch(mysource)
# clean old data
output.Initialize()

# create some points and  triangle cells
pts = pts.vtkPoints()
...
output.SetPoints(pts)
...
pointIds = vtk.vtkIdList()
...
output.InsertNextCell(5,pointIds)
...
# print the ugrid object
print output
mysource.UpdatePipeline()
Render()

My problem is after i manipulate the ugrid on the client side there, i can't 
move it to the server side??? Is there a solution to connect the manipulated 
ugrid at server side with my DataObjectGenerator ?  I know there are the 
programmable source, but i need data from other objects to manipulate the grid 
and i want to use my python script as macro.

regards flo
-- 
NEU: FreePhone - kostenlos mobil telefonieren!  
Jetzt informieren: http://www.gmx.net/de/go/freephone


-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
___
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] writing a bunch of polyhedrons

2011-06-29 Thread Tomislav Maric
Hi everyone, 

I have a list of polyhedrons which have arbitrary shape, and I would like to 
write them all down 
into a single .vtk file. I am using the POLYDATA data set. Right now, my option 
is:

init global points
init global faces

for all polyhedra:
    get local points
    get local faces
    add local points to global points
    map+add local faces to global faces

open the file for writing
write the .vtk header for POLYDATA 

for all points:
    write the points

for all faces:
    write the polygons

Is it possible to make this more effective? Right now I am duplicating my 
information when copying/mapping
to global lists. If I want to write into this file without copying the 
polyhedron data, I will still need
a memory buffer to store the file from the insertion point on, and it would be 
needed twice for each 
polyhedron:

file::seek up

write the points

file::seek down

write the faces

and at the end, I would need to insert the 

POINTS nPoints dataType

and 

POLYGONS n size

at apropriate places. 

Any advice would be appreciated! :)

Thanks!
___
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

2011-06-29 Thread papa ndéné NDIAYE
great thanks Utkarsh,  I now understand how the indexes work there.
but I still don't know how to build my extractblock filter.
I mean to set the "Indices" property of the extractblock filter without
using the GUI.
I know we can get properties from vtkSMProxy::GetProperty
but I don't find a way to set them.

I thank you in advance

Papa

2011/6/29 Utkarsh Ayachit 

> You can get access to the composite dataset information using the data
> information (vtkPVDataInformation::GetCompositeDataInformation()). To
> find the number of blocks 1 level deep, simply do:
>
> dataInfo->GetCompositeDataInformation()->GetNumberOfChildren().
>
> Determining the index for each of those children can be a little
> tricky. The index of a node is the position of that node in a
> pre-order traversal of that tree. So you the index of root is 0, while
> that of it's first child is 1. However for the second child you have
> to count the number of nodes in the entire subtree from Child0 and
> then and that to the index of Child0 i.e. ( index of left sibling +
> number of nodes in sub-tree rooted at left sibling).
>
> vtkPVCompositeDataInformation itself provides access to the data
> information of the child nodes, so using that you can traverse the
> entire composite data tree structure. You can also use
> vtkPVCompositeDataInformationIterator to traverse the tree.
> vtkPVCompositeDataInformationIterator provides a GetFlatIndex() API to
> obtain the index for any particular node.
>
> Utkarsh
>
> 2011/6/28 papa ndéné NDIAYE :
> > Hi all,
> >
> > I have a reader that produces a multiblock dataset and
> > want to add a GUI plug-in that applies the extract block filter
> > just changing the index to have all blocks (one level deep) extracted in
> > different objects.
> > I think about a loop calling the createfilter method of the builder with
> > "extractblock".
> > do you know how to get the number of blocks and how to set the index of
> the
> > block i want to extract without using the GUI?
> >
> > thanks!!
> >
> > ___
> > 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