Re: [Paraview] OSPRay ignores transparency

[Nenad Vujicic]

Oh, I understand.

Thanks Dave!

Nenad.

On Tue, Jan 23, 2018 at 6:27 PM, David E DeMarle <dave.dema...@kitware.com>
wrote:

> It is a known bug in VTK's interface to OSPRay such that opacity is
> ignored in some cases dependent on some of the other color controls.
> https://gitlab.kitware.com/paraview/paraview/issues/17873
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065=gmail=g>
> Clifton Park, NY 12065
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065=gmail=g>
> -8662
> Phone: 518-881-4909 <(518)%20881-4909>
>
> On Tue, Jan 23, 2018 at 12:00 PM, Nenad Vujicic <nena...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I tried both ParaView v5.4 and current v5.5 binaries, Windows x64, but,
>> when I set a surface object opacity to e.g. 0.5, then enable OSPRay,
>> surfaces goes back to fully opaque. Is transparency currently ignored?
>>
>> Thanks,
>> Nenad.
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] OSPRay ignores transparency

[Nenad Vujicic]

Hello everyone,

I tried both ParaView v5.4 and current v5.5 binaries, Windows x64, but,
when I set a surface object opacity to e.g. 0.5, then enable OSPRay,
surfaces goes back to fully opaque. Is transparency currently ignored?

Thanks,
Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] ParaView: Qt runtime errors

[Nenad Vujicic]

Hello everyone,

I'm experiencing one strange situation with some of my ParaView plugin
exporters. When I create the scene, go to File->Export Scene, select output
filename and file-format, push OK and then it creates output file, but it
also reports some QT runtime errors in Output Window:

QWindowsWindow::setGeometry: Unable to set geometry 229x100+1024+492 on
QWindgetWindow/'QDialogClassWindow'. Resulting Geometry: 229x99+1025+592
(frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 178x99,
maximum size: 16777215x16777215).

I get this error 2 times reported.

I first noticed this on my custom build, but, when I tried Kitware's
binaries (the latest one: ParaView-5.4.1-Qt5-OpenGL2-MPI-Windows-64bit), I
also got these errors. Here is list of my steps:

1. Create Sphere source and apply Elevation Filter onto it,
2. File->Export, select WEBGL Files (*.webgl) file type and push OK button.

I tested on Windows 10 Pro x64, but, also, have confirmation it occurs
under Windows 7 x64. Btw, it also occurs on ParaView v5.4.0.

Does anyone have any idea?

Best regards,
Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.3: Generating textures from scalars and lookup table

[Nenad Vujicic]

> >> >* Does anyone have idea how to solve generating textures problem?
*> >> >* I continued to decompose the problem and I'm curious, is
interpolation of
*> >* scalars before mapping performed (when OpenGL2 is selected) by shaders
*> >* (on-the-fly, during display) or is an intermediate texture generated?
*> >
> 2xN is a good texture. That is what you should get for both the old and new
> backends (N covers the  scalar range, the 2 covers normal versus NaN, it is
> a 2D map because of how normal scalar values should properly interpolate to
> NaN).

> ...

Ken, thank you very much for your help. I think I solved my problem of
simulating InterpolateScalarsBeforeMapping (and getting sharp edges)
by re-creating larger colormap (4x1K) from generated one.

Thanks very much once again to everyone for helping!


Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.3: Generating textures from scalars and lookup table

[Nenad Vujicic]

Hello everyone,

Does anyone have idea how to solve generating textures problem?

I continued to decompose the problem and I'm curious, is interpolation of
scalars before mapping performed (when OpenGL2 is selected) by shaders
(on-the-fly, during display) or is an intermediate texture generated?

Also, in OpenGL case, vtkPainter was available. This is missing in OpenGL2.
Where has this functionality moved to or is it missing?

Nenad.

On Tue, Apr 25, 2017 at 11:59 AM, Nenad Vujicic <nena...@gmail.com> wrote:

> David,
>
> Thank you very much for your response! I tried what you suggested and it
> worked, but, I'm getting bad texture, i.e. I get texture 2xN, where N is
> number of segments in colormap and the exported texture mapped object looks
> like I turned OFF InterpolateScalarsBeforeMapping flag. I would like to
> simulate InterpolateScalarsBeforeMapping behavior by baking entire
> texture first and exporting it. You can easily see difference if you create
> Wavelet source, turn ON Surface representation, select RTData array for
> coloring and set Number Of Table Values (in Color Map Editor) to e.g. 5.
>
> What I did in background is: I patched vtkCompositePolyDataMapper2Internal
> and vtkCompositePolyDataMapper2, so I'm able to access appropriate block
> mapper and get rid of old colormap texture, coordinates, colors, call
> MapScalars(), dump created ColorMapTexture to .vti file (everything
> performed on block-mapper).
>
> Do you have some idea where I made mistake?
>
> Thanks in advance!
>
> Nenad.
>
>
> On Thu, Apr 13, 2017 at 2:33 PM, David E DeMarle <dave.dema...@kitware.com
> > wrote:
>
>> Hi Nenand,
>>
>> You might try vtkMapper::GetColorMapColors/C
>> olorCoordinates/ColorTextureMap. I'm using this in the OSPRay renderer
>> for example.
>>
>> Out of curiosity is this for the p2f3d exporter plugin?
>>
>> cheers
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> R Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909 <(518)%20881-4909>
>>
>> On Tue, Apr 11, 2017 at 6:34 AM, Nenad Vujicic <nena...@gmail.com> wrote:
>>
>>> Hello everyone,
>>>
>>> I've just started building my ParaView exporter plugin using ParaView
>>> v5.3 with OpenGL2 selected for backend rendering
>>> (PARAVIEW_RENDERING_BACKEND), however, I'm having troubles with generating
>>> textures from scalars used for coloring the meshes. What I'm actually doing
>>> here is that I'm generating texture from currently selected array and
>>> lookup-table and I export texture mapped object instead of exporting object
>>> plus scalars and colormap or colors. Previously (with OpenGL used for
>>> backend rendering), I was deriving class from vtkScalarsToColorsPainter
>>> class for this purpose, however, now, this class is not used anymore with
>>> OpenGL2.
>>>
>>> Does anyone have idea how to solve this problem?
>>>
>>> Thanks in advance,
>>> Nenad.
>>>
>>> ___
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.3: Generating textures from scalars and lookup table

[Nenad Vujicic]

David,

Thank you very much for your response! I tried what you suggested and it
worked, but, I'm getting bad texture, i.e. I get texture 2xN, where N is
number of segments in colormap and the exported texture mapped object looks
like I turned OFF InterpolateScalarsBeforeMapping flag. I would like to
simulate InterpolateScalarsBeforeMapping behavior by baking entire texture
first and exporting it. You can easily see difference if you create Wavelet
source, turn ON Surface representation, select RTData array for coloring
and set Number Of Table Values (in Color Map Editor) to e.g. 5.

What I did in background is: I patched vtkCompositePolyDataMapper2Internal
and vtkCompositePolyDataMapper2, so I'm able to access appropriate block
mapper and get rid of old colormap texture, coordinates, colors, call
MapScalars(), dump created ColorMapTexture to .vti file (everything
performed on block-mapper).

Do you have some idea where I made mistake?

Thanks in advance!

Nenad.


On Thu, Apr 13, 2017 at 2:33 PM, David E DeMarle <dave.dema...@kitware.com>
wrote:

> Hi Nenand,
>
> You might try vtkMapper::GetColorMapColors/ColorCoordinates/ColorTextureMap.
> I'm using this in the OSPRay renderer for example.
>
> Out of curiosity is this for the p2f3d exporter plugin?
>
> cheers
>
>
> David E DeMarle
> Kitware, Inc.
> R Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909 <(518)%20881-4909>
>
> On Tue, Apr 11, 2017 at 6:34 AM, Nenad Vujicic <nena...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I've just started building my ParaView exporter plugin using ParaView
>> v5.3 with OpenGL2 selected for backend rendering
>> (PARAVIEW_RENDERING_BACKEND), however, I'm having troubles with generating
>> textures from scalars used for coloring the meshes. What I'm actually doing
>> here is that I'm generating texture from currently selected array and
>> lookup-table and I export texture mapped object instead of exporting object
>> plus scalars and colormap or colors. Previously (with OpenGL used for
>> backend rendering), I was deriving class from vtkScalarsToColorsPainter
>> class for this purpose, however, now, this class is not used anymore with
>> OpenGL2.
>>
>> Does anyone have idea how to solve this problem?
>>
>> Thanks in advance,
>> Nenad.
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] ParaView v5.3: Generating textures from scalars and lookup table

[Nenad Vujicic]

Hello everyone,

I've just started building my ParaView exporter plugin using ParaView v5.3
with OpenGL2 selected for backend rendering (PARAVIEW_RENDERING_BACKEND),
however, I'm having troubles with generating textures from scalars used for
coloring the meshes. What I'm actually doing here is that I'm generating
texture from currently selected array and lookup-table and I export texture
mapped object instead of exporting object plus scalars and colormap or
colors. Previously (with OpenGL used for backend rendering), I was deriving
class from vtkScalarsToColorsPainter class for this purpose, however, now,
this class is not used anymore with OpenGL2.

Does anyone have idea how to solve this problem?

Thanks in advance,
Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.2 problems with PLY files with point clouds

[Nenad Vujicic]

Cory,

Thank you for response. Bil has already solved it (crashing problem, on
January 25th, 2017) and pushed it to repository, so it became part of
ParaView v5.3.0 release.

Thanks,
Nenad.

On Tue, Apr 4, 2017 at 2:44 AM, Cory Quammen <cory.quam...@kitware.com>
wrote:

> Nenad,
>
> Sorry, this has been sitting in my inbox for a while now.
>
> I tried reading the PLY file you cited [1] with ParaView 5.3. It seems
> to read the points just fine.
>
> What might be confusing is that since there is no cell data, the
> points are not rendered in the default "Surface" representation. In
> the Properties panel, set the "Representation" type to 3D Glyphs, the
> Glyph Type to Sphere, and the Radius to 0.05. You'll see the points as
> pictured in the attached image.
>
> HTH,
> Cory
>
> [1] https://courses.cs.washington.edu/courses/cse558/01sp/
> software/scanalyze/points.html
>
> On Mon, Jan 16, 2017 at 9:20 AM, Nenad Vujicic <nena...@gmail.com> wrote:
> > Hello everyone,
> >
> > I found several PLY files which crashed my ParaView based application. I
> > inspected vtkPLYReader.cxx and found (Ln 128-140) that it doesn't even
> > support loading PLY files with points.
> >
> > Example of such PLY file:
> > https://courses.cs.washington.edu/courses/cse558/01sp/
> software/scanalyze/points.html
> > Example of software which successfully opens such PLY file: CloudCompare
> -
> > http://www.danielgm.net/cc/
> >
> > Do you maybe have in plan adding support for such PLY files? Has someone
> > perhaps already implemented such feature and is willing to share it?
> >
> > Thanks in advance,
> > Nenad.
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color

[Nenad Vujicic]

Utkarsh,

Thank you very much! I made mistake by casting vtkScalarsToColors to
vtkLookupTable always, without inspecting of other branches! When I put
conditional checking if it is maybe
vtkPVDiscretizableColorTransferFunction, it started working! Thank you very
much for your help!

Nenad.

On Wed, Feb 22, 2017 at 2:12 AM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Where are you getting the vtkLookupTable from? ParaView doesn't use
> vtkLookupTable directly, is uses vtkPVDiscretizableColorTransferFunction
> <http://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/classvtkPVDiscretizableColorTransferFunction.html>
>  .
>
> Utkarsh
>
> On Tue, Feb 21, 2017 at 11:42 AM, Nenad Vujicic <nena...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I'm trying to inspect values of "UseBelowRangeColor" and
>> "UseAboveRangeColor" flags from my ParaView exporter plugin by:
>>
>> 1. Retrieving vtkCompositePolyDataMapper2 from currently active view and
>> rendering window, then,
>> 2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor()
>> and GetUseBelowRangeColor(),
>>
>> However, first call (for checking using above range color) always passes
>> and returns some big number and second one (for checking using below range
>> color) always crashes, regardless whether flags are turned ON / OFF in
>> ParaView UI.
>>
>> Any suggestions about this or ideas how I could pick up these values in
>> different way?
>>
>> Thanks in advance!
>> Nenad.
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color

[Nenad Vujicic]

Hello everyone,

I'm trying to inspect values of "UseBelowRangeColor" and
"UseAboveRangeColor" flags from my ParaView exporter plugin by:

1. Retrieving vtkCompositePolyDataMapper2 from currently active view and
rendering window, then,
2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor() and
GetUseBelowRangeColor(),

However, first call (for checking using above range color) always passes
and returns some big number and second one (for checking using below range
color) always crashes, regardless whether flags are turned ON / OFF in
ParaView UI.

Any suggestions about this or ideas how I could pick up these values in
different way?

Thanks in advance!
Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Release dates of ParaView v5.1.1

[Nenad Vujicic]

Utkarsh,

Thank you very much :-) I wish you good luck!

Nenad.

On Fri, Jul 22, 2016 at 10:00 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Hopefully next week. A never ending stream of  "oh can i sneak in this
> one fix..." that keeps coming my way, but I am not going to  entertain
> any requests past today.
>
> Utkarsh
>
> On Fri, Jul 22, 2016 at 3:49 PM, Nenad Vujicic <nena...@gmail.com> wrote:
> > Hello everyone,
> >
> > Can anyone estimate when ParaView v5.1.1 will arrive?
> >
> > Btw, is there some page with ParaView roadmap? I found only
> > http://www.paraview.org/Bug/roadmap_page.php, but, it seems to me a
> little
> > bit messed up :-).
> >
> > Thanks in advance!
> >
> > Nenad.
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Release dates of ParaView v5.1.1

[Nenad Vujicic]

Hello everyone,

Can anyone estimate when ParaView v5.1.1 will arrive?

Btw, is there some page with ParaView roadmap? I found only
http://www.paraview.org/Bug/roadmap_page.php, but, it seems to me a little
bit messed up :-).

Thanks in advance!

Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] How to convert scalars to colors (and texture) with OpenGL2 turned ON

[Nenad Vujicic]

Hello everyone,

I work on ParaView exporter plugin and I bumped on one problem when OpenGL2
was introduced as default value for PARAVIEW_RENDERING_BACKEND (v5.1). When
I used OpenGL, I converted scalars to colors and generated textures, which
I used for coloring meshes in format to which I export, using class derived
from vtkScalarsToColorsPainter. However, now, when I turn ON OpenGL2, I'm
not able to access this class and even if I access, it relies on some
header files which are generated during build (but only if OpenGL is
selected).

Luckily, OpenGL still exists as an option and I can use it for now. But, I
would like to know:

1. Is it possible somehow to generate colors and texture from scalars when
OpenGL2 is used (similar technique like with vtkScalarsToColorsPainter
class with OpenGL)?

2. If it is not possible, is it planned in future to add support for
something like this for OpenGL2 case?

3. Is it planned to drop support for OpenGL option at some time in future
and approximately when (if known)?

Thanks in advance!

Nenad.

p.s. I build entire ParaViewSuperbuild using VS2013, x64 under Windows 10
Pro with approximately same options like on your dashboards (
https://open.cdash.org/index.php?project=ParaView), at the moment (but,
very soon will work on CentOS v7 x64 too).
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView v5 vs2008 or vs20013?

[Nenad Vujicic]

Utkarsh,

As always, your comments were successful :-).

Thank you very much!!

Nenad.

On Sat, Apr 9, 2016 at 3:51 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com
> wrote:

> Nenad,
>
> 1. The ParaView binaries for 5.0/5.0.1 are built using Visual Studio
> 12 2013 (MSVC 18.0.31101.0).
> 2. For Windows, we only test ParaVIew superbuild using "Ninja"
> generator, and not VS IDE. Thus, run the CMake GUI from an appropriate
> Visual Studio Command prompt and choose the Ninja generator. You'll
> need to install Ninja (https://ninja-build.org/) before doing that.
> 3. Enable Qt4 if you want to build GUI, and not Qt5 yet.
>
> Here are the CMakeCache files for out 64 bit MPI [1] and NO-MPI builds [2].
>
> Hope that helps,
> Utkarsh
>
> [1] https://open.cdash.org/viewNotes.php?buildid=4313885##note4
> [2] https://open.cdash.org/viewNotes.php?buildid=4313982##note4
>
> On Sat, Apr 9, 2016 at 9:15 AM, Nenad Vujicic <nena...@gmail.com> wrote:
> > Hello everyone,
> >
> > Which Visual Studio and CMake were used for preparing ParaView v5
> binaries
> > from http://www.paraview.org/download/ ? I tried to build
> ParaViewSuperbuild
> > using VS2013 / VS2012 and CMake 2.8.11.2 / 3.4.1, but, didn't have
> success.
> > Here is what I did:
> >
> > 1) Downloaded currently the latest Superbuild sources (from master
> branch),
> > 2) create build inside of Superbuild, run cmake-gui ..,
> > 3) I turned OFF using ParaView git sources, turned ON most of packages
> under
> > ENABLE (except mpi, manta, libxml2, etc) and hit Configure / Generate, I
> > used system Qt v4 (everything is x64),
> > 4) Opened generated solution from VS IDE, tried first to build zlib
> project
> > and nothing happened, only reported:
> >
> > 1>-- Rebuild All started: Project: zlib, Configuration: Release x64
> > --
> > 1>  Building Custom Rule C:/Projects/PVdev/Superbuild/CMakeLists.txt
> > 1>  CMake does not need to re-run because
> > C:\Projects\PVdev\Superbuild\build\CMakeFiles\generate.stamp is
> up-to-date.
> > 1>  Creating directories for 'zlib'
> > 1>  No download step for 'zlib'
> > 1>  No update step for 'zlib'
> > 1>  No patch step for 'zlib'
> > 1>  No configure step for 'zlib'
> > 1>  No build step for 'zlib'
> > 1>  No install step for 'zlib'
> > 1>  Completed 'zlib'
> > == Rebuild All: 1 succeeded, 0 failed, 0 skipped ==
> >
> > 5) Btw, if I turn on mpi during cmake phase, I get a lot of errors (like
> > missing MPI_CXX_COMPILER) during Configuring. I cannot even come to
> > generating building files.
> >
> > Can someone shed more light on building process of PV v5, please?
> >
> > Thanks in advance,
> > Nenad.
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] ParaView v5 vs2008 or vs20013?

[Nenad Vujicic]

Hello everyone,

Which Visual Studio and CMake were used for preparing ParaView v5 binaries
from http://www.paraview.org/download/  ?
I tried to build ParaViewSuperbuild using VS2013 / VS2012 and CMake
2.8.11.2 / 3.4.1, but, didn't have success. Here is what I did:

1) Downloaded currently the latest Superbuild sources (from master branch),
2) create build inside of Superbuild, run cmake-gui ..,
3) I turned OFF using ParaView git sources, turned ON most of packages
under ENABLE (except mpi, manta, libxml2, etc) and hit Configure /
Generate, I used system Qt v4 (everything is x64),
4) Opened generated solution from VS IDE, tried first to build zlib project
and nothing happened, only reported:

1>-- Rebuild All started: Project: zlib, Configuration: Release x64
--
1>  Building Custom Rule C:/Projects/PVdev/Superbuild/CMakeLists.txt
1>  CMake does not need to re-run because
C:\Projects\PVdev\Superbuild\build\CMakeFiles\generate.stamp is up-to-date.
1>  Creating directories for 'zlib'
1>  No download step for 'zlib'
1>  No update step for 'zlib'
1>  No patch step for 'zlib'
1>  No configure step for 'zlib'
1>  No build step for 'zlib'
1>  No install step for 'zlib'
1>  Completed 'zlib'
== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==

5) Btw, if I turn on mpi during cmake phase, I get a lot of errors (like
missing MPI_CXX_COMPILER) during Configuring. I cannot even come to
generating building files.

Can someone shed more light on building process of PV v5, please?

Thanks in advance,
Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Dear Utkarsh,

I'm sorry for delay, I was out of home for a while.

Yes, I think this will help. Thank you very much for your help!

Nenad.

On Sat, May 30, 2015 at 4:10 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Nenad,

 DataLabelRepresentation is a subproxy of the GeometryRepresentation and that
 has been the case since as long as I remember. That means that when you
 iterate over representations in the view, you'll never see a separate
 DataLabelRepresentation proxy. Each source proxy has a GetSelectionOutput
 method that you can use to get the source proxy which is doing the
 extracting tasks to extract selected points. To see if the source proxy
 has a selection set, you can use the vtkSMSourceProxy::GetSelectionInput()
 method.

 Hope that helps.
 Utkarsh

 On Fri, May 22, 2015 at 7:15 AM Nenad Vujicic nena...@gmail.com wrote:

 Utkarsh,

 Thank you very much for answers about creating and initializing
 DataLabelRepresentation. Now my source plugin works perfectly.

 But, my exporting plugin (my first message) is still unable to export
 labels which I get when try selecting several points. Here is what I
 do:

 1. Create Sphere and apply Elevation filter on it (I turn OFF 3d widget),
 2. I select several points and in Selection Manager I select Elevation
 for Point Labels,
 3. In following code snippet I get only 2 message boxes (one of Sphere
 and one for Elevation - both GeometryRepresentation),, but, there is
 no DataLabelRepresentation.
 4. I know how to extract labels parameters at this level (Selection*
 parameters from representation), but not set of points over which are
 generated labels,

 // for all sources
 for(i = 0; i  sources.size(); i++)
 {
 // get source
 pqPipelineSource* source = sources.at(i);

 // for every source's output port, process it
 for(output_port = 0; output_port 
 source-getNumberOfOutputPorts(); output_port++)
 {
 // traverse all representations
 for(j = 0; j  source-getRepresentations(output_port,
 active_view).count(); j++)
 {
   QMessageBox::about(NULL, ,
 GetCurrentSourceRepresentationSMName());
 }
 }
 }

 Should I try to catch
 pqSelectionManager::selectionChanged(pqOutputPort*) to get data
 structure over which are points which I can compare with data
 structures extracted from vtkRenderWindow to generate labels?

 Thanks for help in advance!

 Nenad.

 On Mon, May 18, 2015 at 3:49 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
  - Strange 1: I don't have anymore instance in
  DataLabelRepresentation for Elevation pipeline source (btw, during
  this traversing I get only one actor),
 
  I don't follow. DataLableRepresentation is indeed created for every
  representation shown in the render view.
 
 
  - Strange 2: When I traverse vtkRenderer's actors, I get 2 actors
  (sphere mesh and actor with selected points), but, I'm unable to
  connect selection label properties (which are tied with Elevation
  pipeline source actor - sphere mesh) and mesh with selected points /
  cells.
 
  Remember that label actors are added to the 2D / non-composited
  renderer, not the same as the 3D renderer. Which renderer are you
  looking at?
 
  Q1: How to identify actor from vtkRenderer which contains selection
  points / cells and get selection properties from this actor or
 
  Q2: How to identify actor from pqPipeline source on which are selected
  points and how from appropriate representations to get actor which
  contains selected points / cells?
 
  Neither of these are really supported. Look at
  vtkSelectionRepresentation. If you can think of ways of tagging the
  actors added by the representations used internally by this class, I
  am all ears.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Utkarsh,

 - Strange 1: I don't have anymore instance in
 DataLabelRepresentation for Elevation pipeline source (btw, during
 this traversing I get only one actor),

 I don't follow. DataLableRepresentation is indeed created for every
 representation shown in the render view.

It seems it is not. When I execute my code snipped (passed down) I get
only 2 sources (good), every source with 1 output port (good) and for
every output port only one GeometryRepresentation (bad). No traces of
DataLabelRepresentation. Btw, my test case is:

1. Create Sphere source with default parameters,
2. Apply Elevation filter on it and turn off its 3d widget line,
3. Select several points on Elevation1 sphere and execute code snippet.

Here is my code snippet:

-- START OF CODE SNIPPET --

// pass through all pipeline sources and pass all its representations
for all output ports
for(i = 0; i  sources.size(); i++)
{
// get pipeline source
pqPipelineSource* source = sources.at(i);

QMessageBox::about(NULL, 1, source-getSMName());

// for every output port, traverse all its representations
for(output_port = 0; output_port 
source-getNumberOfOutputPorts(); output_port++)
{
 QMessageBox::about(NULL, 2, source-getSMName() +
QString(_port_) + QString::number(output_port));

 // traverse all representations for this
 for(j = 0; j  source-getRepresentations(output_port,
active_view).count(); j++)
 {
 // get representation
 // I got active_view with
pqApplicationCore::instance()-getServerManagerModel()-getNumberOfItemspqView*
 pqDataRepresentation* current_representation =
source-getRepresentations(output_port, active_view)[j];

 QMessageBox::about(NULL, 3, current_representation-getSMName());
  }
}
}

-- END OF CODE SNIPPET --

Thank you very much for your response!


Nenad.

p.s. sorry for duplicated messages in your inbox:-).





On Mon, May 18, 2015 at 3:49 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 - Strange 1: I don't have anymore instance in
 DataLabelRepresentation for Elevation pipeline source (btw, during
 this traversing I get only one actor),

 I don't follow. DataLableRepresentation is indeed created for every
 representation shown in the render view.


 - Strange 2: When I traverse vtkRenderer's actors, I get 2 actors
 (sphere mesh and actor with selected points), but, I'm unable to
 connect selection label properties (which are tied with Elevation
 pipeline source actor - sphere mesh) and mesh with selected points /
 cells.

 Remember that label actors are added to the 2D / non-composited
 renderer, not the same as the 3D renderer. Which renderer are you
 looking at?

 Q1: How to identify actor from vtkRenderer which contains selection
 points / cells and get selection properties from this actor or

 Q2: How to identify actor from pqPipeline source on which are selected
 points and how from appropriate representations to get actor which
 contains selected points / cells?

 Neither of these are really supported. Look at
 vtkSelectionRepresentation. If you can think of ways of tagging the
 actors added by the representations used internally by this class, I
 am all ears.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Utkarsh,

I'm sorry for confusing:-(.

I want to say DataRepresentationCreated is never called! When I create
instance of my pipeline source with this source code, I get only 3
messages: Source Created, and 2 times Representation Added after
pushing Apply button.

Nenad.

On Wed, May 20, 2015 at 3:50 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Nenad,

 Okay I must be missing something very obvious here, but I am totally
 lost here. EventHandlers.cpp confused more than it clarified things
 for me :).

 Just focusing on EventHandlers.cpp for now.

 Are you saying EventHandlers::DataRepresentationCreated() isn't called
 when a new DataLabelRepresentation is created at line #136?

 Utkarsh
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Utkarsh,

You are right, view is really NULL!! Ok, when I catch signals fired
I'll wait appropriate view is created and then they creating
representation.

Thanks!

On Wed, May 20, 2015 at 5:12 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Step into createDataRepresentation in a debugger. You'll see one of
 the arguments is NULL. I suspect its the view. The view isn't setup
 yet. Try making the slot connection to a queued connection that way
 ParaView gets the change to setup the representation object.

 On Wed, May 20, 2015 at 11:07 AM, Nenad Vujicic nena...@gmail.com wrote:
 Utkarsh,

 Thank you very much for help, but, it still doesn't work. At Ln 118 it
 fails and reports in Output Window 'Missing required attribute.' and
 returns NULL.

 Thanks for any help!

 Nenad.

 On Wed, May 20, 2015 at 4:10 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 I want to say DataRepresentationCreated is never called! When I create
 instance of my pipeline source with this source code, I get only 3
 messages: Source Created, and 2 times Representation Added after
 pushing Apply button.

 Ah ok. That's because pqObjectBuilder no longer creates the standard
 representations for ParaView. A better signal to observe is
 pqServerManagerModel::representationAdded(). You're already observer
 sourceAdded from the ServerManagerModel. You'll need to qobject_cast
 to pqDataRepresentation* in your slot, for same effect as before.

 Utkarsh
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Hello again,

I have one another problem with the latest PV sources (v4.3.1, I used
VS2008 x64 built with most of extra packages from super-build enabled)
and creating labels. Again everything worked fine on v4.0 (and I think
v4.2), but now, not anymore .. Here is what I tried:

1. I created a source plugin which outputs on output port 0 set of
points and on output port 1 set of lines.
2. I registered handlers to catch signals sourceAdded(),
sourceCreated(), representationAdded(), representationRemoved() etc,
3. In handler for RepresentationAdded, when representation for output
port 0 (set of points) is created, I previously created
DataLabelRepresentation and initialized, but now it just reports data
representation is reported and does nothing..
4. Now, I tried to set some parameters of representation subproxy by:

// set representation's properties
pqSMAdaptor::setElementProperty(mptrPointsRepresentation-getProxy()-GetProperty(SelectionVisibility),
true);
pqSMAdaptor::setElementProperty(mptrPointsRepresentation-getProxy()-GetProperty(SelectionPointLabelVisibility),
true);
pqSMAdaptor::setMultipleElementProperty(mptrPointsRepresentation-getProxy()-GetProperty(SelectionPointLabelColor),
rPointLabelColor);
pqSMAdaptor::setElementProperty(mptPointsRepresentation-getProxy()-GetProperty(SelectionPointLabelFontSize),
iPointLabelSize);
pqSMAdaptor::setElementProperty(mptrPointsRepresentation-getProxy()-GetProperty(SelectionPointLabelFormat),
strPointLabelFormat);
pqSMAdaptor::setElementProperty(mptrPointsRepresentation-getProxy()-GetProperty(SelectionPointLabelJustification),
iPointLabelJustification);

// update underlying VTK objects
mptrPointsRepresentation-getProxy()-UpdateVTKObjects();

But, it still doesn't work.

Btw, when I create sphere, apply elevation and select some points
(with started tracing), I don't see any of these parameters turned ON.
I don't see anything about selected points .. Also, I noticed
selections are not preserved in state files.

Thanks in advance for any help!

Nenad.


On Wed, May 13, 2015 at 2:21 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 It has been a long time ParaView sources worked excellent with my
 patches and the plugin (3D exporter). However, I'm having troubles
 with the latest version (v4.3.1) to export labels which are shown over
 selected points (both per point and per cell). This was my approach
 which worked with v4.0.1 (100% sure) and v4.2 (I think, but, I'm not
 definitely sure):

 1. I traverse all visible pipeline sources and for all their
 representations in currently active view do next,
 2. For every representation, I check if it is DataLabelRepresentation
 and if it is I save PointLabelVisibility, PointFieldDataArrayName, etc
 properties ..
 3. From other representations, I get vtkLODActor for which I bind my
 labels properties,
 4. In exporting code, I get current view, traverse its actors and
 export them, however, there is one problem now. Let me give an
 example:

 - If I have Sphere on which I applied Elevation filter and
 selected several points with turned on labels (with e.g. Elevation
 selected as array),

 - Strange 1: I don't have anymore instance in
 DataLabelRepresentation for Elevation pipeline source (btw, during
 this traversing I get only one actor),
 - Strange 2: When I traverse vtkRenderer's actors, I get 2 actors
 (sphere mesh and actor with selected points), but, I'm unable to
 connect selection label properties (which are tied with Elevation
 pipeline source actor - sphere mesh) and mesh with selected points /
 cells.

 Q1: How to identify actor from vtkRenderer which contains selection
 points / cells and get selection properties from this actor or

 Q2: How to identify actor from pqPipeline source on which are selected
 points and how from appropriate representations to get actor which
 contains selected points / cells?

 Thanks everyone for possible answers!

 Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Troubles with exporting selection labels from current ParaView render view

[Nenad Vujicic]

Hello everyone,

It has been a long time ParaView sources worked excellent with my
patches and the plugin (3D exporter). However, I'm having troubles
with the latest version (v4.3.1) to export labels which are shown over
selected points (both per point and per cell). This was my approach
which worked with v4.0.1 (100% sure) and v4.2 (I think, but, I'm not
definitely sure):

1. I traverse all visible pipeline sources and for all their
representations in currently active view do next,
2. For every representation, I check if it is DataLabelRepresentation
and if it is I save PointLabelVisibility, PointFieldDataArrayName, etc
properties ..
3. From other representations, I get vtkLODActor for which I bind my
labels properties,
4. In exporting code, I get current view, traverse its actors and
export them, however, there is one problem now. Let me give an
example:

- If I have Sphere on which I applied Elevation filter and
selected several points with turned on labels (with e.g. Elevation
selected as array),

- Strange 1: I don't have anymore instance in
DataLabelRepresentation for Elevation pipeline source (btw, during
this traversing I get only one actor),
- Strange 2: When I traverse vtkRenderer's actors, I get 2 actors
(sphere mesh and actor with selected points), but, I'm unable to
connect selection label properties (which are tied with Elevation
pipeline source actor - sphere mesh) and mesh with selected points /
cells.

Q1: How to identify actor from vtkRenderer which contains selection
points / cells and get selection properties from this actor or

Q2: How to identify actor from pqPipeline source on which are selected
points and how from appropriate representations to get actor which
contains selected points / cells?

Thanks everyone for possible answers!

Nenad.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaView 3.98.1: Problems with Space Navigator

[Nenad Vujicic]

Dear Dave,

Thank you very much for the patch's link.

I've just tried it with v3.98.1 release sources and after I made very small
change in it, SpaceNavigator started working perfectly! Patch referenced
NeedsAnalog (vtkVRSpaceNavigatorGrabWorldStyle.cxx Ln 55) and AnalogName
properties (vtkVRSpaceNavigatorGrabWorldStyle.cxx Ln 71-78) which are not
available anymore directly. After I masked off these lines, everything
started working great.

I posted review to http://review.source.kitware.com/#/c/8374/ too. I
haven't tested with current master repository sources, but I believe they
should work fine too (after above changes are applied), because there were
no larger changes as I saw.

Thanks,
Nenad.



On Thu, Apr 4, 2013 at 10:25 PM, David Lonie david.lo...@kitware.com
wrote:

 I just remembered this patch where Cory had rewritten the GrabWorld
 style for the space navigator:

 http://review.source.kitware.com/#/c/8374/

 Nenad: If you get a chance to try it, please let us know (better yet,
 make an account on the review board and leave feedback there, if you
 have time. Otherwise an email to the list will do).

 Cory: I +1'd these patch, but they seem to have been forgotten. Are
 you still interested in contributing them? Can you rebase them against
 current master and see if they still work?

 Dave

 On Wed, Apr 3, 2013 at 3:11 PM, Nenad Vujicic nena...@gmail.com wrote:
  Dear Dave, Aashish,
 
  Thank you very much for your help!
 
  I put logging calls to routines of above 2 classes (vtkVRGrabWorldStyle
and
  pqVRPNConnection) and I started catching messages on both places. Now,
looks
  like the problem is that current interaction styles don't like my device
  (most likely because of reason Aashish mentioned). I'll dig into these
  classes and try to fix them or create new interaction style. Then,
someone
  from the team will submit the patch.
 
  Thanks again for your help!
 
  Best regards,
  Nenad.
 
 
 
 
  On Wed, Apr 3, 2013 at 3:10 PM, Aashish Chaudhary
  aashish.chaudh...@kitware.com wrote:
 
  One another possibility could be is that SN does not really offer
tracker
  and we are expecting tracker data so the code
  somewhere is broke.
 
  Can you create a new interactor style and just listen for buttons and
  analogs?
 
 
 
 
  On Wed, Apr 3, 2013 at 8:38 AM, David Lonie david.lo...@kitware.com
  wrote:
 
  On Wed, Apr 3, 2013 at 7:58 AM, Nenad Vujicic nena...@gmail.com
wrote:
   Dear Dave,
  
   Thank you for your ideas. Unfortunately, there are no errors /
warnings
   emitted during startup or while running ParaView. Also, I tried
several
   times with restarting ParaView and always checked if listening is
   started
   (i.e. Start button is disabled and Stop is enabled). I even turned
off
   my
   firewall, but nothing helped.
  
   Btw, when I put some logging calls to pqVRStarter.cxx Ln 56
(beginning
   of
   pqVREventPlayer::playEvent() routine), I didn't get any message
(during
   my
   trying to work with 3d mouse). Of course, pqVREventPlayer class
   definition
   is enabled (because PARAVIEW_USE_VRPN is turned ON). Did I maybe
need
   to
   enable some special flag during compilation of Qt to get this event
   playing
   working or this is used only during automated testing?
 
  That was only for automated testing. If you want to debug this, try
  putting some debugging messages in
 
  vtkVRGrabWorldStyle.cxx: HandleTracker() and HandleButton()
  pqVRPNConnection.cxx: newButtonValue() and new TrackerValue()
 
  The first one is the style where the events from the vrpn are
  translated into camera events, and the second file will check that the
  events are coming in from VRPN correctly.
 
  Did ParaView/VRPN work on this machine in the past? AFAIK no one else
  has tried this on Windows 8 yet.
 
  Dave
 
  ___
  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
 
 
 
 
  --
  | Aashish Chaudhary
  | RD Engineer
  | Kitware Inc.
  | www.kitware.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

Re: [Paraview] ParaView 3.98.1: Problems with Space Navigator

[Nenad Vujicic]

Dear Dave, Aashish,

Thank you very much for your help!

I put logging calls to routines of above 2 classes (vtkVRGrabWorldStyle and
pqVRPNConnection) and I started catching messages on both places. Now,
looks like the problem is that current interaction styles don't like my
device (most likely because of reason Aashish mentioned). I'll dig into
these classes and try to fix them or create new interaction style. Then,
someone from the team will submit the patch.

Thanks again for your help!

Best regards,
Nenad.




On Wed, Apr 3, 2013 at 3:10 PM, Aashish Chaudhary 
aashish.chaudh...@kitware.com wrote:

 One another possibility could be is that SN does not really offer tracker
 and we are expecting tracker data so the code
 somewhere is broke.

 Can you create a new interactor style and just listen for buttons and
 analogs?




 On Wed, Apr 3, 2013 at 8:38 AM, David Lonie david.lo...@kitware.comwrote:

 On Wed, Apr 3, 2013 at 7:58 AM, Nenad Vujicic nena...@gmail.com wrote:
  Dear Dave,
 
  Thank you for your ideas. Unfortunately, there are no errors / warnings
  emitted during startup or while running ParaView. Also, I tried several
  times with restarting ParaView and always checked if listening is
 started
  (i.e. Start button is disabled and Stop is enabled). I even turned off
 my
  firewall, but nothing helped.
 
  Btw, when I put some logging calls to pqVRStarter.cxx Ln 56 (beginning
 of
  pqVREventPlayer::playEvent() routine), I didn't get any message (during
 my
  trying to work with 3d mouse). Of course, pqVREventPlayer class
 definition
  is enabled (because PARAVIEW_USE_VRPN is turned ON). Did I maybe need to
  enable some special flag during compilation of Qt to get this event
 playing
  working or this is used only during automated testing?

 That was only for automated testing. If you want to debug this, try
 putting some debugging messages in

 vtkVRGrabWorldStyle.cxx: HandleTracker() and HandleButton()
 pqVRPNConnection.cxx: newButtonValue() and new TrackerValue()

 The first one is the style where the events from the vrpn are
 translated into camera events, and the second file will check that the
 events are coming in from VRPN correctly.

 Did ParaView/VRPN work on this machine in the past? AFAIK no one else
 has tried this on Windows 8 yet.

 Dave

 ___
 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




 --
 | Aashish Chaudhary
 | RD Engineer
 | Kitware Inc.
 | www.kitware.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] ParaView 3.98.1: Problems with Space Navigator

[Nenad Vujicic]

Dear Dave, Aashish,

Thank you very much for your responses.

I'm sorry, I tried dummy buttons with both v3.98.1 and current master
ParaView sources, but they didn't help me. Also, I'm still able to select
visibility with grab world style from ParaView's UI (in master sources).
Btw, my 3d mouse has 2 buttons (
http://www.3dconnexion.com/products/spacenavigator.html). Here is one of
snippets from state file I tried:

VRConnectionManager
   VRPNConnection name=vrconnection address=device0@localhost
  Button id=0 name=MyRightButton/
  Button id=1 name=MyLeftButton/
  Button id=2 name=MyDummyButton/
  Analog id=0 name=MyAnalog/
  Tracker id=0 name=MyTracker/
/VRPNConnection
  /VRConnectionManager
  VRInteractorStyles
Style class=vtkVRGrabWorldStyle proxyName=RenderView1 proxy=269
property=ModelTransformMatrix
  Button role=Reset world name=vrconnection.MyLeftButton/
  Button role=Rotate world name=vrconnection.MyRightButton/
  Button role=Translate world name=vrconnection.MyDummyButton/
  Tracker role=Tracker name=vrconnection.MyTracker/
   /Style
/VRInteractorStyles

Do you have some other idea?

Thanks,
Nenad.



On Tue, Apr 2, 2013 at 4:06 PM, Aashish Chaudhary 
aashish.chaudh...@kitware.com wrote:

 Also,

 This does not look right:

  Style class=vtkVRGrabWorldStyle proxy=2125 property=Visibility

 Can you try current master of ParaView and re-create the interactions
config? It should not allow you to select visibility with grab world style.

 - Aashish



 On Tue, Apr 2, 2013 at 10:01 AM, David Lonie david.lo...@kitware.com
wrote:

 On Mon, Apr 1, 2013 at 3:35 PM, Nenad Vujicic nena...@gmail.com wrote:
  Hello everyone!
 
  I'm trying to make my Space Navigator working in ParaView v3.98.1 on my
  Windows 8 machine. I built sources without problems (using VS2012,
with qt
  4.8.4, python 2.7.3, boost 1.53.0, OpenMPI 1.6.2, VRPN 07_30 - all
rebuilt
  in x64 mode) with turned on PARAVIEW_USE_VRPN and
  PARAVIEW_BUILD_PLUGIN_VRPlugin (+ flags for enabling shared libraries,
  python, mpi, visit bridge, etc). But, I'm unable to make it working
from Qt
  client. Here are my running steps:
 
  1. I start vrpn_server in background (with enabled line with my
device).
  When I test it with vrpn_print_devices, everything works OK - whenever
I
  touch my device, vrpn client prints some values,
  2. I start ParaView's Qt client, load VR plugin, create Cone sourse,
define
  VR connection and Interactions and push Start button,
  3. I click on Cone source or built in: node in Pipeline Browser and
touch
  my Space Navigator but nothing changes (except vrpn_server reports
  connection is established). Actually, for some actions like pushing
button
  (on 3d mouse) I get several instances of following warning in Output
Window:
 
  Generic Warning: In
  ..\..\..\..\ParaViewCore\ServerManager\Core\vtkSMPropertyHelper.cxx,
line
  439
 
  Call not supported for the current property type.
 
  I get same behavior when I save options from my VR Panel to state file
and
  load it. Here is VR content from state file:
 
  VRConnectionManager
  VRPNConnection name=vrconnection address=device0@localhost
Button id=0 name=MyRightButton/
Tracker id=0 name=MyTracker/
  /VRPNConnection
/VRConnectionManager
VRInteractorStyles
  Style class=vtkVRGrabWorldStyle proxy=2125
property=Visibility
Button role=Reset world name=vrconnection.MyRightButton/
Button role=Rotate world name=vrconnection.MyRightButton/
Button role=Translate world
name=vrconnection.MyRightButton/
Tracker role=Tracker name=vrconnection.MyTracker/
  /Style
/VRInteractorStyles
 
  I hope I made some small mistake:-). Can anyone suggest where could be
the
  problem?

 It's a bit odd to map all of the actions to the same button. Does your
 input device only have a single button? The GrabWorldStyle requires a
 button press to rotate or translate the view, but that same button is
 also resetting any modifications it makes (since Reset world is
 mapped to MyRightButton along with translate/rotate). These should
 each be set to unique buttons.

 Try using other buttons for reset/translate/rotate world. You can add
 dummy buttons to the VR config if needed, just set the button's id
 number higher than your device supports.

 Hope this helps,

 Dave
 ___
 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




 --
 | Aashish Chaudhary
 | RD Engineer
 | Kitware Inc.
 | www.kitware.com
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep

Re: [Paraview] ParaView 3.98.1: Problems with Space Navigator

[Nenad Vujicic]

Dear Dave,

It doesn't happen anything, like I didn't touch my 3d mouse. Btw, here is
what is outputted on standard output when I execute 'vrpn_print_devices
device0@localhost':

on left button pressed:

Button device0@localhost, number 1 was just pressed
Button device0@localhost, number 1 was just released

on right button pressed:

Button device0@localhost, number 0 was just pressed
Button device0@localhost, number 0 was just released

on touching tracker:

Analog device0@localhost:

0.00, 0.00, 0.00, 0.00, 0.00, 0.00 (6 chans)
(several above lines with different values)

Thanks,
Nenad.



On Tue, Apr 2, 2013 at 6:43 PM, David Lonie david.lo...@kitware.com wrote:

 On Tue, Apr 2, 2013 at 12:39 PM, Nenad Vujicic nena...@gmail.com wrote:
  Dear Dave, Aashish,
 
  Thank you very much for your responses.
 
  I'm sorry, I tried dummy buttons with both v3.98.1 and current master
  ParaView sources, but they didn't help me. Also, I'm still able to
select
  visibility with grab world style from ParaView's UI (in master sources).
  Btw, my 3d mouse has 2 buttons
  (http://www.3dconnexion.com/products/spacenavigator.html). Here is one
of
  snippets from state file I tried:
 
 
  VRConnectionManager
 VRPNConnection name=vrconnection address=device0@localhost
Button id=0 name=MyRightButton/
Button id=1 name=MyLeftButton/
Button id=2 name=MyDummyButton/
Analog id=0 name=MyAnalog/
 
Tracker id=0 name=MyTracker/
  /VRPNConnection
/VRConnectionManager
VRInteractorStyles
  Style class=vtkVRGrabWorldStyle proxyName=RenderView1
proxy=269
  property=ModelTransformMatrix
Button role=Reset world name=vrconnection.MyLeftButton/
 
Button role=Rotate world name=vrconnection.MyRightButton/
Button role=Translate world name=vrconnection.MyDummyButton/
 
Tracker role=Tracker name=vrconnection.MyTracker/
 /Style
  /VRInteractorStyles
 
  Do you have some other idea?

 What happens when you press the right button and move the tracker?
 Does the scene move at all, or are you still just seeing the error
 messages in the log?

 Dave
___
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] ParaView 3.98.1: Problems with Space Navigator

[Nenad Vujicic]

Hello everyone!

I'm trying to make my Space Navigator working in ParaView v3.98.1 on my
Windows 8 machine. I built sources without problems (using VS2012, with qt
4.8.4, python 2.7.3, boost 1.53.0, OpenMPI 1.6.2, VRPN 07_30 - all rebuilt
in x64 mode) with turned on PARAVIEW_USE_VRPN and
PARAVIEW_BUILD_PLUGIN_VRPlugin (+ flags for enabling shared libraries,
python, mpi, visit bridge, etc). But, I'm unable to make it working from Qt
client. Here are my running steps:

1. I start vrpn_server in background (with enabled line with my device).
When I test it with vrpn_print_devices, everything works OK - whenever I
touch my device, vrpn client prints some values,
2. I start ParaView's Qt client, load VR plugin, create Cone sourse, define
VR connection and Interactions and push Start button,
3. I click on Cone source or built in: node in Pipeline Browser and touch
my Space Navigator but nothing changes (except vrpn_server reports
connection is established). Actually, for some actions like pushing button
(on 3d mouse) I get several instances of following warning in Output Window:

Generic Warning: In
..\..\..\..\ParaViewCore\ServerManager\Core\vtkSMPropertyHelper.cxx, line
439

Call not supported for the current property type.

I get same behavior when I save options from my VR Panel to state file and
load it. Here is VR content from state file:

VRConnectionManager
VRPNConnection name=vrconnection address=device0@localhost
  Button id=0 name=MyRightButton/
  Tracker id=0 name=MyTracker/
/VRPNConnection
  /VRConnectionManager
  VRInteractorStyles
Style class=vtkVRGrabWorldStyle proxy=2125 property=Visibility
  Button role=Reset world name=vrconnection.MyRightButton/
  Button role=Rotate world name=vrconnection.MyRightButton/
  Button role=Translate world name=vrconnection.MyRightButton/
  Tracker role=Tracker name=vrconnection.MyTracker/
/Style
  /VRInteractorStyles

I hope I made some small mistake:-). Can anyone suggest where could be the
problem?

Thanks,
Nenad.
___
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] Linking errors when building ParaView v3.98.0 with VS2008

[Nenad Vujicic]

Hello everyone,

I tried to build release sources ParaView v3.98.0 in x64 mode with
VS2008 SP1, built Python 2.7.3 x64, built Qt 4.8.3 x64, built OpenMPI
v1.6.3 x64 and got some linking errors. All other projects were built
fine and everything works fine so far, except pvpython subsystem. Do
You have some idea how I could solve these issues?

Here are linking errors:

2-- Build started: Project: vtkPVClientServerCoreCorePythonD,
Configuration: Release x64 --
2Linking...
2   Creating library
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreCorePython27D-pv3.98.lib
and object 
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreCorePython27D-pv3.98.exp
2vtkPVClientServerCoreCorePythonInit.obj : error LNK2019: unresolved
external symbol PyVTKAddFile_vtkPVPythonOptions referenced in function
void __cdecl real_initvtkPVClientServerCoreCorePython(char const *)
(?real_initvtkPVClientServerCoreCorePython@@YAXPEBD@Z)
2C:\Projects\PVdev\ParaView-3.98.0\build\bin\Release\vtkPVClientServerCoreCorePython27D-pv3.98.dll
: fatal error LNK1120: 1 unresolved externals
2Build log was saved at
file://c:\Projects\PVdev\ParaView-3.98.0\build\ParaViewCore\ClientServerCore\Core\vtkPVClientServerCoreCorePythonD.dir\Release\BuildLog.htm
2vtkPVClientServerCoreCorePythonD - 2 error(s), 0 warning(s)
3-- Build started: Project: vtkPVServerImplementationCorePythonD,
Configuration: Release x64 --
4-- Build started: Project:
vtkPVClientServerCoreRenderingPythonD, Configuration: Release x64
--
3Linking...
3   Creating library
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVServerImplementationCorePython27D-pv3.98.lib
and object 
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVServerImplementationCorePython27D-pv3.98.exp
4Linking...
3vtkSIDoubleVectorPropertyPython.obj : error LNK2019: unresolved
external symbol PyVTKClass_vtkSIVectorPropertyTemplate_IdENew
referenced in function PyVTKClass_vtkSIDoubleVectorPropertyNew
3vtkSIIdTypeVectorPropertyPython.obj : error LNK2019: unresolved
external symbol
PyVTKClass_vtkSIVectorPropertyTemplate_I9vtkIdTypebENew referenced in
function PyVTKClass_vtkSIIdTypeVectorPropertyNew
3vtkSIIntVectorPropertyPython.obj : error LNK2019: unresolved
external symbol PyVTKClass_vtkSIVectorPropertyTemplate_IiENew
referenced in function PyVTKClass_vtkSIIntVectorPropertyNew
3C:\Projects\PVdev\ParaView-3.98.0\build\bin\Release\vtkPVServerImplementationCorePython27D-pv3.98.dll
: fatal error LNK1120: 3 unresolved externals
4   Creating library
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreRenderingPython27D-pv3.98.lib
and object 
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreRenderingPython27D-pv3.98.exp

...

12-- Build started: Project: vtkPVClientServerCoreCorePython,
Configuration: Release x64 --
12Linking...
12   Creating library
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreCorePython.lib
and object 
C:\Projects\PVdev\ParaView-3.98.0\build\lib\Release\vtkPVClientServerCoreCorePython.exp
12vtkPVClientServerCoreCorePythonInit.obj : error LNK2019: unresolved
external symbol PyVTKAddFile_vtkPVPythonOptions referenced in function
void __cdecl real_initvtkPVClientServerCoreCorePython(char const *)
(?real_initvtkPVClientServerCoreCorePython@@YAXPEBD@Z)
12C:\Projects\PVdev\ParaView-3.98.0\build\bin\Release\vtkPVClientServerCoreCorePython.pyd
: fatal error LNK1120: 1 unresolved externals

Thanks,
Nenad.
___
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] Problems with visibility of 3D Widgets when switching between views

[Nenad Vujicic]

Dear Utkarsh,

Thank You very much for Your help. I hope Sebastien will have some idea.

Btw, in a meantime, I discovered one interesting detail. If I set
pipeline source (with widget) as currently active source
(SetActiveSource(...) in pvpython) before I execute code I mentioned
in first message (btw, it should be my_source.SMProxy.InvokeEvent() x
2, instead of active_objects.source.SMProxy.InvokeEvent() x 2 in first
message), everything will work OK. Of course, all this happens after I
switch between different views. Looks like there are some resetting in
pipeline when user switches between views.

Best regards,
Nenad.

On Wed, Aug 29, 2012 at 3:40 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Sebastien may have some insight here since they do something similar
 for the WebGL exporter. He's on vacation this week, but I can ping him
 once he gets back.

 Utkarsh

 On Tue, Aug 28, 2012 at 6:33 PM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 Thank You very much for Your response.

 It checks actor's visibility at vtkVRMLExporter.cxx Ln 262, but actors
 are visible because of some reasons. I'm sorry, looks like the problem
 is much deeper. I tried even by playing from pvpython by executing:

 active_objects.source.SMProxy.InvokeEvent('UserEvent', 'ShowWidget')
 active_objects.source.SMProxy.InvokeEvent('UserEvent', 'HideWidget')

 but it didn't work. I also experimented by counting number of actors
 in interactive renderer object. After switching between views, it
 contains ~13 actors, while after manually turning on and off widget's
 visibility in Display panel it has ~9 (in this state exporter exports
 correct scene - without 3d widgets). So, only way to refresh data in
 current view is to manually turn ON and after it to turn OFF check box
 on Display panel, which controls widget's visibility.

 Btw, I have much more sophisticated exporter plugin and in which I
 have the same problem. It works in similar way as VRMLExporter, so I
 reported this with VRMLExporter test-case.

 Thanks,
 Nenad.


 On Wed, Aug 29, 2012 at 12:08 AM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 Nenad,

 vtkVRMLExporter will be the starting point where I'd start digging in.
 I am guessing somewhere where it iterates over all actors it's not
 checking for visibility of 3D widgets or something.

 On Tue, Aug 28, 2012 at 5:45 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone!

 I have problems with visibility of 3D widgets when I have several
 views opened in one ParaView Qt client and I switch between them. I
 experience this behavior on both Windows and Linux. Here is how to
 reproduce it:

 0) Start ParaView Qt client,
 1) Create Sphere source and press Apply button,
 2) Create Slice filter, turn off Show Plane option and press Apply button,
 3) Create new layout item by pushing '+' and select Spreadsheet View,
 4) Go on Render View by pressing Layout 1 item,
 5) Export 3D scene from currently active render view to VRML file
 (File-Export),
 6) Reopen ParaView Qt client and load previously exported VRML file.

 Looks like VRML exporter exports 3D widget's geometry and topology
 too, although its turned off. This also occurs with other sources /
 filters with 3D widgets (PointSource, Clip, etc.).

 Can someone suggest how I could fix this bug, by changing exporter's
 or ParaView's sources, or at least approximate place in sources where
 I could take a look for a bug?

 Thanks,
 Nenad.
 ___
 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] Problems with visibility of 3D Widgets when switching between views

[Nenad Vujicic]

Hello everyone!

I have problems with visibility of 3D widgets when I have several
views opened in one ParaView Qt client and I switch between them. I
experience this behavior on both Windows and Linux. Here is how to
reproduce it:

0) Start ParaView Qt client,
1) Create Sphere source and press Apply button,
2) Create Slice filter, turn off Show Plane option and press Apply button,
3) Create new layout item by pushing '+' and select Spreadsheet View,
4) Go on Render View by pressing Layout 1 item,
5) Export 3D scene from currently active render view to VRML file
(File-Export),
6) Reopen ParaView Qt client and load previously exported VRML file.

Looks like VRML exporter exports 3D widget's geometry and topology
too, although its turned off. This also occurs with other sources /
filters with 3D widgets (PointSource, Clip, etc.).

Can someone suggest how I could fix this bug, by changing exporter's
or ParaView's sources, or at least approximate place in sources where
I could take a look for a bug?

Thanks,
Nenad.
___
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] Problems with visibility of 3D Widgets when switching between views

[Nenad Vujicic]

Dear Utkarsh,

Thank You very much for Your response.

It checks actor's visibility at vtkVRMLExporter.cxx Ln 262, but actors
are visible because of some reasons. I'm sorry, looks like the problem
is much deeper. I tried even by playing from pvpython by executing:

active_objects.source.SMProxy.InvokeEvent('UserEvent', 'ShowWidget')
active_objects.source.SMProxy.InvokeEvent('UserEvent', 'HideWidget')

but it didn't work. I also experimented by counting number of actors
in interactive renderer object. After switching between views, it
contains ~13 actors, while after manually turning on and off widget's
visibility in Display panel it has ~9 (in this state exporter exports
correct scene - without 3d widgets). So, only way to refresh data in
current view is to manually turn ON and after it to turn OFF check box
on Display panel, which controls widget's visibility.

Btw, I have much more sophisticated exporter plugin and in which I
have the same problem. It works in similar way as VRMLExporter, so I
reported this with VRMLExporter test-case.

Thanks,
Nenad.


On Wed, Aug 29, 2012 at 12:08 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Nenad,

 vtkVRMLExporter will be the starting point where I'd start digging in.
 I am guessing somewhere where it iterates over all actors it's not
 checking for visibility of 3D widgets or something.

 On Tue, Aug 28, 2012 at 5:45 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone!

 I have problems with visibility of 3D widgets when I have several
 views opened in one ParaView Qt client and I switch between them. I
 experience this behavior on both Windows and Linux. Here is how to
 reproduce it:

 0) Start ParaView Qt client,
 1) Create Sphere source and press Apply button,
 2) Create Slice filter, turn off Show Plane option and press Apply button,
 3) Create new layout item by pushing '+' and select Spreadsheet View,
 4) Go on Render View by pressing Layout 1 item,
 5) Export 3D scene from currently active render view to VRML file
 (File-Export),
 6) Reopen ParaView Qt client and load previously exported VRML file.

 Looks like VRML exporter exports 3D widget's geometry and topology
 too, although its turned off. This also occurs with other sources /
 filters with 3D widgets (PointSource, Clip, etc.).

 Can someone suggest how I could fix this bug, by changing exporter's
 or ParaView's sources, or at least approximate place in sources where
 I could take a look for a bug?

 Thanks,
 Nenad.
 ___
 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] Release dates for ParaView v3.16 / v4

[Nenad Vujicic]

Hello everyone,

Can anyone estimate when next ParaView release will arrive? From
several previous release dates, I believe it should be somewhere in
September / October, am I right?

Best regards,
Nenad.
___
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] Problems with displaying labels floating over data points

[Nenad Vujicic]

Hello Utkarsh,

Thank You very much for Your help! It works great when created as
Python macro. I probably messed up something in my C++ code.

Best regards,
Nenad.

On Thu, May 10, 2012 at 2:28 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Creating a DataLabelRepresentation should have worked. Here's a Python
 script that illustrates the same:

 from paraview.simple import *
 s = Sphere()
 r = Show()
 v = Render()
 l = servermanager.rendering.DataLabelRepresentation()
 l.Input = s
 l.PointLabelVisibility = 1
 l.PointLabelMode = IDs
 v.Representations.append(l)
 Render()

 Utkarsh

 On Wed, May 9, 2012 at 5:53 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 I have a set of points over which I would like to have floating labels
 rendered from values defined in per-point attribute array. If I select
 these points and turn on Point Labels, on Selection Inspector
 docking panel, I get exactly what I need, but, I would like to have
 these labels not bound to currently selected points.

 I figured out that these labels are drawn using
 vtkDataLabelRepresentation class, but I was unable to apply this
 representation to points I extracted from plugin. My idea was to
 create a filter, which will extract all points I'm interested in, and
 to catch adding new representation
 object to Server Manager and current view and replace it with
 pqDataRepresentation which points to vtkDataLabelRepresentation.
 Unfortunately, it didn't work. I also tried with patching
 vtkPVCompositeRepresentation to have always turned on these labels,
 but it failed too.

 Does anyone have idea how I could add these labels?

 Thanks to everyone!

 Nenad.
 ___
 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] Cube Axes labels problems in current ParaView sources

[Nenad Vujicic]

Hello everyone,

The problem is finally solved. List of steps for adding widget to Cube
Axes Editor Dialog which controls cube axes behavior:

1) Add behavior to vtkCubeAxesRepresentation class and property which
controls it,
2) Add property to
ParaViewCore/ServerImplementation/Resources/views_and_representations.xml
for CubeAxesRepresentation proxy,
3) Add widget to pqCubeAxesEditorDialog.ui and register it with
PropertyManager in pqCubeAxesEditorDialog.cxx.

Thank You all for help!

Best regards,
Nenad.
___
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] Cube Axes labels problems in current ParaView sources

[Nenad Vujicic]

Hello everyone,

Looks like this was very easy patch (3 lines of code):-). I made it by
adding setting X, Y and Z axes ranges of used vtkCubeAxesActor object
to data ranges at the end of
vtkCubeAxesRepresentation::UpdateBounds(). Aashish, thank You very
much on Your hint! However, I hit another problem. I wanted to add
check box on Edit Cube Axes Properties dialog which should control
which behavior will be used (generate tick labels from original or
scaled / transformed data). However, I couldn't connect it with code I
added in vtkCubeAxesRepresentation class. I couldn't even retrieve
UnscaledTicks property of passed representation in
pqCubeAxesEditorDialog::setRepresentationProxy() routine.

Is adding of 'bool UnscaledTicks' to vtkCubeAxesRepresentation class
enough to have UnscaledTicks property or there is some additional
code I should call? Also, am I on good way of connecting my check-box
with vtkCubeAxesRepresentation? Any comment is highly appreciated:-)!

Best regards,
Nenad.

On Wed, Oct 26, 2011 at 5:57 PM, Aashish Chaudhary
aashish.chaudh...@kitware.com wrote:
 Hi Nenad,

 I looked into the code and the behavior you are seeing is correct. So it is
 not a bug but I think what you are asking is quite logicial.

 Probably I need to put some logic in vtkCubeAxesRepresentation.  I will drop
 another email once I have it working.

 Best,



 On Tue, Oct 18, 2011 at 2:04 PM, Aashish Chaudhary
 aashish.chaudh...@kitware.com wrote:

 Hi Nenad,

 I looked into some but then got distracted. I will try to have a
 solution this week.

 Sorry about the delay.

 Thanks,


 On Tue, Oct 18, 2011 at 6:31 AM, Nenad Vujicic nena...@gmail.com wrote:
  Hello everyone,
 
  Does anyone have idea how to fix vtkCubeAxesActor.cxx so it doesn't
  scale axes ticks too? Also, is this expected behavior or a bug?
 
  Best regards,
  Nenad.
 
  On Mon, Oct 3, 2011 at 7:21 PM, Nenad Vujicic nena...@gmail.com wrote:
  Dear Aashish,
 
  On Mon, Oct 3, 2011 at 6:34 PM, Aashish Chaudhary
  aashish.chaudh...@kitware.com wrote:
  Hi Nenand,
  ...
  I can have a look at it but it may take one or two days before I get
  to it.  How soon you need this?
 
 
 
  Thank You very much for Your response! I'm not in big rush, so it can
  wait few days.
 
  Best regards,
  Nenad.
 
  ___
  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
 



 --
 | Aashish Chaudhary
 | RD Engineer
 | Kitware Inc.
 | www.kitware.com




 --
 | Aashish Chaudhary
 | RD Engineer
 | Kitware Inc.
 | www.kitware.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] Cube Axes labels problems in current ParaView sources

[Nenad Vujicic]

Hello everyone,

Does anyone have idea how to fix vtkCubeAxesActor.cxx so it doesn't
scale axes ticks too? Also, is this expected behavior or a bug?

Best regards,
Nenad.

On Mon, Oct 3, 2011 at 7:21 PM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Aashish,

 On Mon, Oct 3, 2011 at 6:34 PM, Aashish Chaudhary
 aashish.chaudh...@kitware.com wrote:
 Hi Nenand,
 ...
 I can have a look at it but it may take one or two days before I get
 to it.  How soon you need this?



 Thank You very much for Your response! I'm not in big rush, so it can
 wait few days.

 Best regards,
 Nenad.

___
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] Cube Axes labels problems in current ParaView sources

[Nenad Vujicic]

Hello everyone,

I have problems with Cube Axes labels in ParaView v3.10.1 (and SVN
sources). I load file with terrain mesh, turn on Show Cube Axes (on
Display tab of Object Inspector) and everything is displayed great.
However, if I scale (either using transformation controls on display
tab or with Transform Filter) along Z axis, Z axis labels will be
scaled too (numerically)! In this way labels (in my case elevation)
will be incorrect. Is this correct behavior? Also, in Edit Cube Axes
Properties dialog, when I select Custom Bounds, again both axes and
axes labels are changed.

I looked at vtkCubeAxesActor.cxx and it seems it generates entire axes
mesh (both axes/ticks and labels) from previously calculated
boundaries. Can anyone suggest some easy way to patch it, so only axes
/ ticks are scaled (i.e. without multiplying labels values)?

Thanks in advance!

Best regards,
Nenad.
___
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] Cube Axes labels problems in current ParaView sources

[Nenad Vujicic]

Dear Aashish,

On Mon, Oct 3, 2011 at 6:34 PM, Aashish Chaudhary
aashish.chaudh...@kitware.com wrote:
 Hi Nenand,
 ...
 I can have a look at it but it may take one or two days before I get
 to it.  How soon you need this?



Thank You very much for Your response! I'm not in big rush, so it can
wait few days.

Best regards,
Nenad.
___
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] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Dear Utkarsh,

Yes, it works perfectly with ParaView v3.8.* release sources. The
reason is in vtkScalarsToColorsPainter class which produces 256x1
texture in ParaView v3.8.*, while in ParaView 3.10.* (and current SVN
sources) it produces 256x2 texture. In v3.10.* case, in first row
(bottom-up) are texels with colors copied from lookup table, while in
second row (or first in top-down view) all texels are (64, 0, 0) -
dark red.

Best regards,
Nenad.

On Mon, May 23, 2011 at 3:02 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Interesting, I wonder how that could have worked with older version of
 ParaView then. Did that piece of code change recently?

 Utkarsh

 On Sun, May 22, 2011 at 2:43 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Just to announce - the problem is solved! It seems the problem was in
 plugin's sources when setting texture coordinates data. So, if in
 vtkMyExporter.cpp I remove

 tex_coord_data-SetNumberOfComponents(1);

 or set number of components to 2, correct texture will be generated!

 Thanks everyone on Your help!

 Best regards,
 Nenad.

 On Fri, May 13, 2011 at 11:49 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Does anyone have idea where could be the problem in uploaded sources?

 Thanks,
 Nenad.

 On Tue, May 10, 2011 at 12:13 PM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 Thank You very much, but unfortunately, adding manually copying of
 parameters didn't solve all problems. I updated test plug-in with
 manually copying, converting scalars to texture, applying texture to
 actor and showing resulting actor in vtkRenderWindow. You can find
 updated sources at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 If You load again disk_out_ref.ex2, select H2 and try to export to
 .my, You'll see in separate vtkRenderWindow same object with applied
 generated
 texture which looks very bad. Again, it works fine in v3.8.1. I
 believe I'm not initializing new actors properly? Do You have some
 idea how to fix it?

 Thanks,
 Nenad.


 On Mon, May 9, 2011 at 10:02 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 The problem is pretty straight forward. Looks like
 vtkMapper::ShallowCopy(..) does not copy the state of
 InterpolateScalarsBeforeMapping. I will commit a fix for that for next
 release. Until then, you'll have to manually copy ivars that you care
 about.

 Utkarsh

 On Sun, May 8, 2011 at 10:25 AM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 I uploaded test plugin that shows my problem at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 After I build and load the plugin from Qt client, I load
 disk_out_ref.ex2, select H2 for mapping scalars, check Interpolate
 Scalars on Display tab in Object inspector and go on File-Export
 (select .my file). I get 6 message boxes which report 0, 0, 0, 0, 0, 1
 (instead of 0, 0, 0, 0, 1, 1) as values for
 vtkMapper::InterpolateScalarsBeforeMapping. So, here is first
 question: How to create multiple vtkActor objects from
 vtkCompositePolyDataMapper2's input? I thought that vtkMyExporter.cpp
 Ln 138-162 should be fine, but uploaded sources shows different.

 Thanks,
 Nenad.

 On Fri, May 6, 2011 at 2:29 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 Nenad,

 There;s nothing much different about the vtkCompositePolyDataMapper or
 vtkPolyDataMapper as far as the state of the
 InterpolateScalarsBeforeMapping flag goes. I cannot see how that
 variable can return false if it is indeed set to true as you are
 saying. Can you share the plugin?

 Utkarsh

 On Thu, May 5, 2011 at 6:03 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Perhaps I was a bit unclear in my previous messages. Here are more
 details about the problem and test case.

 I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
 2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
 options (just turned on BUILD_SHARED_LIBS, MPI and Python). I derived
 new class from vtkExporter, vtkMyExporter, and in
 vtkMyExporter::WriteData() I call code specified down. The problem is
 in QMessage line, which reports always 0, even when this flag is
 turned on. Same is happening with most of other parameters.

 I believe that learning how to decompose composite ptrActor into
 several actors with vtkPolyDataMapper mapper and vtkPolyData data will
 solve all other problems (which occur when generating texture from
 scalars). At the moment, I'm interested only in actors which use
 vtkCompositePolyDataMapper2 mappers. As input I use disk_out_ref.ex2
 with selected H2 (or any other channel) for mapping colors. Does
 anyone have any idea how this can be done? Btw, this worked perfectly
 under ParaView v.3.8.1 and with RenderWindow created using VTK 5.4.2
 (where I create vtkCompositePolyDataMapper2 and populate it manually).

 Thank You very much for Your help!

 Best regards,
 Nenad.

 

 1) Get interactive renderer 'InteractiveRenderer' from

Re: [Paraview] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Hello everyone,

Just to announce - the problem is solved! It seems the problem was in
plugin's sources when setting texture coordinates data. So, if in
vtkMyExporter.cpp I remove

tex_coord_data-SetNumberOfComponents(1);

or set number of components to 2, correct texture will be generated!

Thanks everyone on Your help!

Best regards,
Nenad.

On Fri, May 13, 2011 at 11:49 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Does anyone have idea where could be the problem in uploaded sources?

 Thanks,
 Nenad.

 On Tue, May 10, 2011 at 12:13 PM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 Thank You very much, but unfortunately, adding manually copying of
 parameters didn't solve all problems. I updated test plug-in with
 manually copying, converting scalars to texture, applying texture to
 actor and showing resulting actor in vtkRenderWindow. You can find
 updated sources at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 If You load again disk_out_ref.ex2, select H2 and try to export to
 .my, You'll see in separate vtkRenderWindow same object with applied
 generated
 texture which looks very bad. Again, it works fine in v3.8.1. I
 believe I'm not initializing new actors properly? Do You have some
 idea how to fix it?

 Thanks,
 Nenad.


 On Mon, May 9, 2011 at 10:02 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 The problem is pretty straight forward. Looks like
 vtkMapper::ShallowCopy(..) does not copy the state of
 InterpolateScalarsBeforeMapping. I will commit a fix for that for next
 release. Until then, you'll have to manually copy ivars that you care
 about.

 Utkarsh

 On Sun, May 8, 2011 at 10:25 AM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 I uploaded test plugin that shows my problem at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 After I build and load the plugin from Qt client, I load
 disk_out_ref.ex2, select H2 for mapping scalars, check Interpolate
 Scalars on Display tab in Object inspector and go on File-Export
 (select .my file). I get 6 message boxes which report 0, 0, 0, 0, 0, 1
 (instead of 0, 0, 0, 0, 1, 1) as values for
 vtkMapper::InterpolateScalarsBeforeMapping. So, here is first
 question: How to create multiple vtkActor objects from
 vtkCompositePolyDataMapper2's input? I thought that vtkMyExporter.cpp
 Ln 138-162 should be fine, but uploaded sources shows different.

 Thanks,
 Nenad.

 On Fri, May 6, 2011 at 2:29 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 Nenad,

 There;s nothing much different about the vtkCompositePolyDataMapper or
 vtkPolyDataMapper as far as the state of the
 InterpolateScalarsBeforeMapping flag goes. I cannot see how that
 variable can return false if it is indeed set to true as you are
 saying. Can you share the plugin?

 Utkarsh

 On Thu, May 5, 2011 at 6:03 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Perhaps I was a bit unclear in my previous messages. Here are more
 details about the problem and test case.

 I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
 2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
 options (just turned on BUILD_SHARED_LIBS, MPI and Python). I derived
 new class from vtkExporter, vtkMyExporter, and in
 vtkMyExporter::WriteData() I call code specified down. The problem is
 in QMessage line, which reports always 0, even when this flag is
 turned on. Same is happening with most of other parameters.

 I believe that learning how to decompose composite ptrActor into
 several actors with vtkPolyDataMapper mapper and vtkPolyData data will
 solve all other problems (which occur when generating texture from
 scalars). At the moment, I'm interested only in actors which use
 vtkCompositePolyDataMapper2 mappers. As input I use disk_out_ref.ex2
 with selected H2 (or any other channel) for mapping colors. Does
 anyone have any idea how this can be done? Btw, this worked perfectly
 under ParaView v.3.8.1 and with RenderWindow created using VTK 5.4.2
 (where I create vtkCompositePolyDataMapper2 and populate it manually).

 Thank You very much for Your help!

 Best regards,
 Nenad.

 

 1) Get interactive renderer 'InteractiveRenderer' from
 vtkMyExporter::RenderWindow
 2) For every actor 'ptrActor' (3D actors only) in InteractiveRenderer do:

    vtkCompositeDataIterator* actor_iterator;
    vtkCompositePolyDataMapper2* composite_mapper = NULL;

    // get actor's mapper
    vtkMapper* mapper = ptrActor-GetMapper();
    if(mapper == NULL)
        return true; // discard

    // get mapper's input
    vtkCompositeDataSet* composite_input_data =
 dynamic_castvtkCompositeDataSet*(mapper-GetInputDataObject(0, 0));
    if(composite_input_data != NULL)
    {
        // get actor's composite mapper
        composite_mapper = 
 dynamic_castvtkCompositePolyDataMapper2*(mapper);
        if(composite_mapper == NULL)
            return false;

        // in case input data is composite object

Re: [Paraview] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Hello everyone,

Does anyone have idea where could be the problem in uploaded sources?

Thanks,
Nenad.

On Tue, May 10, 2011 at 12:13 PM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 Thank You very much, but unfortunately, adding manually copying of
 parameters didn't solve all problems. I updated test plug-in with
 manually copying, converting scalars to texture, applying texture to
 actor and showing resulting actor in vtkRenderWindow. You can find
 updated sources at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 If You load again disk_out_ref.ex2, select H2 and try to export to
 .my, You'll see in separate vtkRenderWindow same object with applied
 generated
 texture which looks very bad. Again, it works fine in v3.8.1. I
 believe I'm not initializing new actors properly? Do You have some
 idea how to fix it?

 Thanks,
 Nenad.


 On Mon, May 9, 2011 at 10:02 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 The problem is pretty straight forward. Looks like
 vtkMapper::ShallowCopy(..) does not copy the state of
 InterpolateScalarsBeforeMapping. I will commit a fix for that for next
 release. Until then, you'll have to manually copy ivars that you care
 about.

 Utkarsh

 On Sun, May 8, 2011 at 10:25 AM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 I uploaded test plugin that shows my problem at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 After I build and load the plugin from Qt client, I load
 disk_out_ref.ex2, select H2 for mapping scalars, check Interpolate
 Scalars on Display tab in Object inspector and go on File-Export
 (select .my file). I get 6 message boxes which report 0, 0, 0, 0, 0, 1
 (instead of 0, 0, 0, 0, 1, 1) as values for
 vtkMapper::InterpolateScalarsBeforeMapping. So, here is first
 question: How to create multiple vtkActor objects from
 vtkCompositePolyDataMapper2's input? I thought that vtkMyExporter.cpp
 Ln 138-162 should be fine, but uploaded sources shows different.

 Thanks,
 Nenad.

 On Fri, May 6, 2011 at 2:29 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 Nenad,

 There;s nothing much different about the vtkCompositePolyDataMapper or
 vtkPolyDataMapper as far as the state of the
 InterpolateScalarsBeforeMapping flag goes. I cannot see how that
 variable can return false if it is indeed set to true as you are
 saying. Can you share the plugin?

 Utkarsh

 On Thu, May 5, 2011 at 6:03 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Perhaps I was a bit unclear in my previous messages. Here are more
 details about the problem and test case.

 I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
 2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
 options (just turned on BUILD_SHARED_LIBS, MPI and Python). I derived
 new class from vtkExporter, vtkMyExporter, and in
 vtkMyExporter::WriteData() I call code specified down. The problem is
 in QMessage line, which reports always 0, even when this flag is
 turned on. Same is happening with most of other parameters.

 I believe that learning how to decompose composite ptrActor into
 several actors with vtkPolyDataMapper mapper and vtkPolyData data will
 solve all other problems (which occur when generating texture from
 scalars). At the moment, I'm interested only in actors which use
 vtkCompositePolyDataMapper2 mappers. As input I use disk_out_ref.ex2
 with selected H2 (or any other channel) for mapping colors. Does
 anyone have any idea how this can be done? Btw, this worked perfectly
 under ParaView v.3.8.1 and with RenderWindow created using VTK 5.4.2
 (where I create vtkCompositePolyDataMapper2 and populate it manually).

 Thank You very much for Your help!

 Best regards,
 Nenad.

 

 1) Get interactive renderer 'InteractiveRenderer' from
 vtkMyExporter::RenderWindow
 2) For every actor 'ptrActor' (3D actors only) in InteractiveRenderer do:

    vtkCompositeDataIterator* actor_iterator;
    vtkCompositePolyDataMapper2* composite_mapper = NULL;

    // get actor's mapper
    vtkMapper* mapper = ptrActor-GetMapper();
    if(mapper == NULL)
        return true; // discard

    // get mapper's input
    vtkCompositeDataSet* composite_input_data =
 dynamic_castvtkCompositeDataSet*(mapper-GetInputDataObject(0, 0));
    if(composite_input_data != NULL)
    {
        // get actor's composite mapper
        composite_mapper = 
 dynamic_castvtkCompositePolyDataMapper2*(mapper);
        if(composite_mapper == NULL)
            return false;

        // in case input data is composite object, get iterator for 
 traversing
        actor_iterator = composite_input_data-NewIterator();

        // initialize iterator for traversing
        actor_iterator-InitTraversal();
        actor_iterator-GoToFirstItem();
    }
    else
        actor_iterator = NULL;

    // export all components of input actor
    for(;;)
    {
        vtkSmartPointervtkActor actor;

        // if input data is composite object, create actor

Re: [Paraview] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Dear Utkarsh,

Thank You very much, but unfortunately, adding manually copying of
parameters didn't solve all problems. I updated test plug-in with
manually copying, converting scalars to texture, applying texture to
actor and showing resulting actor in vtkRenderWindow. You can find
updated sources at
http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

If You load again disk_out_ref.ex2, select H2 and try to export to
.my, You'll see in separate vtkRenderWindow same object with applied
generated
texture which looks very bad. Again, it works fine in v3.8.1. I
believe I'm not initializing new actors properly? Do You have some
idea how to fix it?

Thanks,
Nenad.


On Mon, May 9, 2011 at 10:02 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 The problem is pretty straight forward. Looks like
 vtkMapper::ShallowCopy(..) does not copy the state of
 InterpolateScalarsBeforeMapping. I will commit a fix for that for next
 release. Until then, you'll have to manually copy ivars that you care
 about.

 Utkarsh

 On Sun, May 8, 2011 at 10:25 AM, Nenad Vujicic nena...@gmail.com wrote:
 Dear Utkarsh,

 I uploaded test plugin that shows my problem at
 http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

 After I build and load the plugin from Qt client, I load
 disk_out_ref.ex2, select H2 for mapping scalars, check Interpolate
 Scalars on Display tab in Object inspector and go on File-Export
 (select .my file). I get 6 message boxes which report 0, 0, 0, 0, 0, 1
 (instead of 0, 0, 0, 0, 1, 1) as values for
 vtkMapper::InterpolateScalarsBeforeMapping. So, here is first
 question: How to create multiple vtkActor objects from
 vtkCompositePolyDataMapper2's input? I thought that vtkMyExporter.cpp
 Ln 138-162 should be fine, but uploaded sources shows different.

 Thanks,
 Nenad.

 On Fri, May 6, 2011 at 2:29 PM, Utkarsh Ayachit
 utkarsh.ayac...@kitware.com wrote:
 Nenad,

 There;s nothing much different about the vtkCompositePolyDataMapper or
 vtkPolyDataMapper as far as the state of the
 InterpolateScalarsBeforeMapping flag goes. I cannot see how that
 variable can return false if it is indeed set to true as you are
 saying. Can you share the plugin?

 Utkarsh

 On Thu, May 5, 2011 at 6:03 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Perhaps I was a bit unclear in my previous messages. Here are more
 details about the problem and test case.

 I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
 2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
 options (just turned on BUILD_SHARED_LIBS, MPI and Python). I derived
 new class from vtkExporter, vtkMyExporter, and in
 vtkMyExporter::WriteData() I call code specified down. The problem is
 in QMessage line, which reports always 0, even when this flag is
 turned on. Same is happening with most of other parameters.

 I believe that learning how to decompose composite ptrActor into
 several actors with vtkPolyDataMapper mapper and vtkPolyData data will
 solve all other problems (which occur when generating texture from
 scalars). At the moment, I'm interested only in actors which use
 vtkCompositePolyDataMapper2 mappers. As input I use disk_out_ref.ex2
 with selected H2 (or any other channel) for mapping colors. Does
 anyone have any idea how this can be done? Btw, this worked perfectly
 under ParaView v.3.8.1 and with RenderWindow created using VTK 5.4.2
 (where I create vtkCompositePolyDataMapper2 and populate it manually).

 Thank You very much for Your help!

 Best regards,
 Nenad.

 

 1) Get interactive renderer 'InteractiveRenderer' from
 vtkMyExporter::RenderWindow
 2) For every actor 'ptrActor' (3D actors only) in InteractiveRenderer do:

    vtkCompositeDataIterator* actor_iterator;
    vtkCompositePolyDataMapper2* composite_mapper = NULL;

    // get actor's mapper
    vtkMapper* mapper = ptrActor-GetMapper();
    if(mapper == NULL)
        return true; // discard

    // get mapper's input
    vtkCompositeDataSet* composite_input_data =
 dynamic_castvtkCompositeDataSet*(mapper-GetInputDataObject(0, 0));
    if(composite_input_data != NULL)
    {
        // get actor's composite mapper
        composite_mapper = 
 dynamic_castvtkCompositePolyDataMapper2*(mapper);
        if(composite_mapper == NULL)
            return false;

        // in case input data is composite object, get iterator for 
 traversing
        actor_iterator = composite_input_data-NewIterator();

        // initialize iterator for traversing
        actor_iterator-InitTraversal();
        actor_iterator-GoToFirstItem();
    }
    else
        actor_iterator = NULL;

    // export all components of input actor
    for(;;)
    {
        vtkSmartPointervtkActor actor;

        // if input data is composite object, create actor with
 current component as data, otherwise use entire actor (I do this
 because I need actor with vtkPolyDataMapper and vtkPolyData data for
 vtkScalarsToColorsPainter)
        if(actor_iterator

Re: [Paraview] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Dear Utkarsh,

I uploaded test plugin that shows my problem at
http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.

After I build and load the plugin from Qt client, I load
disk_out_ref.ex2, select H2 for mapping scalars, check Interpolate
Scalars on Display tab in Object inspector and go on File-Export
(select .my file). I get 6 message boxes which report 0, 0, 0, 0, 0, 1
(instead of 0, 0, 0, 0, 1, 1) as values for
vtkMapper::InterpolateScalarsBeforeMapping. So, here is first
question: How to create multiple vtkActor objects from
vtkCompositePolyDataMapper2's input? I thought that vtkMyExporter.cpp
Ln 138-162 should be fine, but uploaded sources shows different.

Thanks,
Nenad.

On Fri, May 6, 2011 at 2:29 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Nenad,

 There;s nothing much different about the vtkCompositePolyDataMapper or
 vtkPolyDataMapper as far as the state of the
 InterpolateScalarsBeforeMapping flag goes. I cannot see how that
 variable can return false if it is indeed set to true as you are
 saying. Can you share the plugin?

 Utkarsh

 On Thu, May 5, 2011 at 6:03 PM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 Perhaps I was a bit unclear in my previous messages. Here are more
 details about the problem and test case.

 I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
 2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
 options (just turned on BUILD_SHARED_LIBS, MPI and Python). I derived
 new class from vtkExporter, vtkMyExporter, and in
 vtkMyExporter::WriteData() I call code specified down. The problem is
 in QMessage line, which reports always 0, even when this flag is
 turned on. Same is happening with most of other parameters.

 I believe that learning how to decompose composite ptrActor into
 several actors with vtkPolyDataMapper mapper and vtkPolyData data will
 solve all other problems (which occur when generating texture from
 scalars). At the moment, I'm interested only in actors which use
 vtkCompositePolyDataMapper2 mappers. As input I use disk_out_ref.ex2
 with selected H2 (or any other channel) for mapping colors. Does
 anyone have any idea how this can be done? Btw, this worked perfectly
 under ParaView v.3.8.1 and with RenderWindow created using VTK 5.4.2
 (where I create vtkCompositePolyDataMapper2 and populate it manually).

 Thank You very much for Your help!

 Best regards,
 Nenad.

 

 1) Get interactive renderer 'InteractiveRenderer' from
 vtkMyExporter::RenderWindow
 2) For every actor 'ptrActor' (3D actors only) in InteractiveRenderer do:

    vtkCompositeDataIterator* actor_iterator;
    vtkCompositePolyDataMapper2* composite_mapper = NULL;

    // get actor's mapper
    vtkMapper* mapper = ptrActor-GetMapper();
    if(mapper == NULL)
        return true; // discard

    // get mapper's input
    vtkCompositeDataSet* composite_input_data =
 dynamic_castvtkCompositeDataSet*(mapper-GetInputDataObject(0, 0));
    if(composite_input_data != NULL)
    {
        // get actor's composite mapper
        composite_mapper = dynamic_castvtkCompositePolyDataMapper2*(mapper);
        if(composite_mapper == NULL)
            return false;

        // in case input data is composite object, get iterator for traversing
        actor_iterator = composite_input_data-NewIterator();

        // initialize iterator for traversing
        actor_iterator-InitTraversal();
        actor_iterator-GoToFirstItem();
    }
    else
        actor_iterator = NULL;

    // export all components of input actor
    for(;;)
    {
        vtkSmartPointervtkActor actor;

        // if input data is composite object, create actor with
 current component as data, otherwise use entire actor (I do this
 because I need actor with vtkPolyDataMapper and vtkPolyData data for
 vtkScalarsToColorsPainter)
        if(actor_iterator != NULL)
        {
            // check if there are no more components
            if(actor_iterator-IsDoneWithTraversal())
                break;

            // get next component
            vtkDataObject* data_object = 
 actor_iterator-GetCurrentDataObject();
            if(dynamic_castvtkPolyData*(data_object) != NULL)
            {
                // get poly data
                vtkPolyData* poly_data =
 dynamic_castvtkPolyData*(data_object);

                // create new temporary poly data mapper
                vtkSmartPointervtkPolyDataMapper poly_data_mapper =
 vtkSmartPointervtkPolyDataMapper::New();

                // copy mapper's parameters
                poly_data_mapper-ShallowCopy(composite_mapper);

                // set mapper's input
                poly_data_mapper-SetInput(poly_data);

                // create new actor
                actor = vtkSmartPointervtkActor::New();

                // copy actor parameters
                actor-ShallowCopy(ptrActor);

                // set actor's mapper
                actor-SetMapper(poly_data_mapper

Re: [Paraview] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

 trying to achieve?

 Utkarsh

 On Wed, May 4, 2011 at 8:31 AM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 I'm having some problems with porting my ParaView exporter plug-in to
 v3.10, because ParaView started using vtkCompositeDataSet internally
 instead of keeping components merged. The problem is in performing
 transformation of scalars to texture using vtkScalarsToColorsPainter
 class. Here is approximately my code (questions come after
 pseudo-code):

 for every actor in currently active renderer:
  for every component of composite data object (I retrieve
 vtkDataObject* with vtkCompositeDataIterator::GetCurrentDataObject()
 call)

    // prepare new actor which defines component
    dynamic cast vtkDataObject* data_object to vtkPolyData* poly_data;
    create new vtkPolyDataMapper* pdm;
    pdm-ShallowCopy(composite_mapper);
    pdm-SetInput(poly_data);
    allocate new actor and do actor-ShallowCopy(ptrActor) //
 ptrActor) is selected actor from currently active renderer - line 1
    actor-SetMapper(pdm);

    // perform converting from scalars to texture
    ConvertScalarsToColors(actor);

 Routine ConvertScalarsToColors(vtkActor*) is defined in following way:

 L1 get actor's poly_data and mapper references,
 L2 create s2c - instance of MyVtkScalarsToColorsPainter (derived from
 vtkScalarsToColorsPainter for allowing setting its protected
 attributes),
 L3 initialize s2c parameters from mapper and poly_data
 L4 if s2c-CanUseTextureMapForColoring(poly_data) returns true,
 s2c-PrepareForRendering(), get texture and texture coordinates and
 sets them to passed actor

 Q1: First problem is in L3 when setting s2c parameters. Original
 mapper has turned on InterpolateScalarsBeforeMapping flag, but new one
 doesn't have it. How to safely copy properties of
 vtkCompositePolyDataMapper2 to vtkPolyDataMapper or I shouldn't do it?

 Q2: Even if I override above problem by turning on manually
 InterpolateScalarsBeforeMapping, I get very bad texture on output. It
 looks like scalars were not interpolated before mapping, sometimes
 even more distorted..

 The same code works with v3.8 perfectly. I also tried to apply
 vtkCompositeDataGeometryFilter to composite data object and to apply
 ConvertScalarsToColors() to result (even without creating new actor),
 but without success. Strange thing is that when I try this with
 manually created VTK scene (out of ParaView) it works perfectly and
 texture looks great!

 I would appreciate any help!

 Best regards,
 Nenad.
 ___
 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] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Hello everyone,

I'm having some problems with porting my ParaView exporter plug-in to
v3.10, because ParaView started using vtkCompositeDataSet internally
instead of keeping components merged. The problem is in performing
transformation of scalars to texture using vtkScalarsToColorsPainter
class. Here is approximately my code (questions come after
pseudo-code):

for every actor in currently active renderer:
  for every component of composite data object (I retrieve
vtkDataObject* with vtkCompositeDataIterator::GetCurrentDataObject()
call)

// prepare new actor which defines component
dynamic cast vtkDataObject* data_object to vtkPolyData* poly_data;
create new vtkPolyDataMapper* pdm;
pdm-ShallowCopy(composite_mapper);
pdm-SetInput(poly_data);
allocate new actor and do actor-ShallowCopy(ptrActor) //
ptrActor) is selected actor from currently active renderer - line 1
actor-SetMapper(pdm);

// perform converting from scalars to texture
ConvertScalarsToColors(actor);

Routine ConvertScalarsToColors(vtkActor*) is defined in following way:

L1 get actor's poly_data and mapper references,
L2 create s2c - instance of MyVtkScalarsToColorsPainter (derived from
vtkScalarsToColorsPainter for allowing setting its protected
attributes),
L3 initialize s2c parameters from mapper and poly_data
L4 if s2c-CanUseTextureMapForColoring(poly_data) returns true,
s2c-PrepareForRendering(), get texture and texture coordinates and
sets them to passed actor

Q1: First problem is in L3 when setting s2c parameters. Original
mapper has turned on InterpolateScalarsBeforeMapping flag, but new one
doesn't have it. How to safely copy properties of
vtkCompositePolyDataMapper2 to vtkPolyDataMapper or I shouldn't do it?

Q2: Even if I override above problem by turning on manually
InterpolateScalarsBeforeMapping, I get very bad texture on output. It
looks like scalars were not interpolated before mapping, sometimes
even more distorted..

The same code works with v3.8 perfectly. I also tried to apply
vtkCompositeDataGeometryFilter to composite data object and to apply
ConvertScalarsToColors() to result (even without creating new actor),
but without success. Strange thing is that when I try this with
manually created VTK scene (out of ParaView) it works perfectly and
texture looks great!

I would appreciate any help!

Best regards,
Nenad.
___
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] Problems with 'interpolate scalars before mapping' in v3.10

[Nenad Vujicic]

Dear Utkarsh,

Thank You very much on Your answer.

Yes, my plug-in is exporter, which means I define it in class derived
from vtkExporter. It extracts all possible scene information from
vtkExporter::RenderWindow object (in both Qt-client and python-client
modes) and writes these data to very special format using proprietary
software. Because output format is a bit specific, I have to convert
scalar values to texture first and then to export the texture, I
cannot output interpolated scalars or colors.

Like in my pseudo-code, I first take currently active renderer (from
vtkExporter::RenderWindow) and collect geometry / topology /
other_info from it using my pseudo-code. After this step, I write
collected data to my format using other software without problems.
However, I have problems with transforming scalars to texture. Btw,
I'm sure collected data is fine, because I can preview it using other
software.. Also, it works perfect under v3.8.*.

Do You have any idea?

Thanks,
Nenad.


On Wed, May 4, 2011 at 3:04 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Nenad,

 I am not sure I understand where this code is being put. You say it's
 an exporter? Meaning it exports to something like a vrml/x3d file? But
 that doesn't seem right since you say you are using the
 PolyDataMapper.

 What is this plugin trying to achieve?

 Utkarsh

 On Wed, May 4, 2011 at 8:31 AM, Nenad Vujicic nena...@gmail.com wrote:
 Hello everyone,

 I'm having some problems with porting my ParaView exporter plug-in to
 v3.10, because ParaView started using vtkCompositeDataSet internally
 instead of keeping components merged. The problem is in performing
 transformation of scalars to texture using vtkScalarsToColorsPainter
 class. Here is approximately my code (questions come after
 pseudo-code):

 for every actor in currently active renderer:
  for every component of composite data object (I retrieve
 vtkDataObject* with vtkCompositeDataIterator::GetCurrentDataObject()
 call)

    // prepare new actor which defines component
    dynamic cast vtkDataObject* data_object to vtkPolyData* poly_data;
    create new vtkPolyDataMapper* pdm;
    pdm-ShallowCopy(composite_mapper);
    pdm-SetInput(poly_data);
    allocate new actor and do actor-ShallowCopy(ptrActor) //
 ptrActor) is selected actor from currently active renderer - line 1
    actor-SetMapper(pdm);

    // perform converting from scalars to texture
    ConvertScalarsToColors(actor);

 Routine ConvertScalarsToColors(vtkActor*) is defined in following way:

 L1 get actor's poly_data and mapper references,
 L2 create s2c - instance of MyVtkScalarsToColorsPainter (derived from
 vtkScalarsToColorsPainter for allowing setting its protected
 attributes),
 L3 initialize s2c parameters from mapper and poly_data
 L4 if s2c-CanUseTextureMapForColoring(poly_data) returns true,
 s2c-PrepareForRendering(), get texture and texture coordinates and
 sets them to passed actor

 Q1: First problem is in L3 when setting s2c parameters. Original
 mapper has turned on InterpolateScalarsBeforeMapping flag, but new one
 doesn't have it. How to safely copy properties of
 vtkCompositePolyDataMapper2 to vtkPolyDataMapper or I shouldn't do it?

 Q2: Even if I override above problem by turning on manually
 InterpolateScalarsBeforeMapping, I get very bad texture on output. It
 looks like scalars were not interpolated before mapping, sometimes
 even more distorted..

 The same code works with v3.8 perfectly. I also tried to apply
 vtkCompositeDataGeometryFilter to composite data object and to apply
 ConvertScalarsToColors() to result (even without creating new actor),
 but without success. Strange thing is that when I try this with
 manually created VTK scene (out of ParaView) it works perfectly and
 texture looks great!

 I would appreciate any help!

 Best regards,
 Nenad.
 ___
 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] Possible bug in v3.10 when multiple readers available

[Nenad Vujicic]

Hello everyone,

I had problems when loading files for which there are more then one
readers available. When I looked at
Qt/ApplicationComponents/pqLoadDataReaction.cxx I noticed in
pqLoadDataReaction::DetermineFileReader() Ln 187, pqSelectReaderDialog
is shown only when there are more then 3 available readers! Shouldn't
it be shown when there are more then 1 available reader, i.e.

if(list-GetLength()  3)

be replaced with

if(list-GetLength()  1)?

Thanks,
Nenad.
___
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] ParaView v3.9.0: problems with exporter plug-in

[Nenad Vujicic]

Hello everyone,

Because of Xdmf problems inside of v3.8.1, I tried to use my exporter
plug-in with current v3.9.0 sources. I downloaded sources from Git
repository and compiled them with Visual Studio 2008 SP1, Python 2.7
and OpenMPI 1.4.3. Unfortunately, in exported scene I got only center
of rotation axes and orientation axes.

After closer inspection, I made very short snipped that shows the
problem. In class derived from vtkExporter, in function WriteData() I
override, I call following sequence:

   - for every renderer in RenderWindow
 - for every actor in renderer // only 3d actors
   - mapper = actor.GetMapper()
   - if(mapper != NULL)
 - mappers_input = mapper.GetInput()
 - print mappers_input // PROBLEM: NULL for whatever I add to
pipeline, instead of 2 axes meshes

At the moment, I read 3 renderers, the first renderer has 5 actors (2
for center of rotation axes mesh and 3 LOD actors), the second 0 and
the third has 9 actors (all for orientation axes mesh). The problem is
in 3 LOD actors for which I get vtkCompositePolyDataMapper2 objects as
mappers, but which return NULL on GetInput() always! In v3.8.x I used
same mechanism to get vtkPolyData and other data sets from which I
would later extract scene's properties.

Am I doing something wrong or exporter's part still requires some work
before v3.9.0 is released? Btw, similar occurs when I try to export
scene to VRML - only center of rotation axes mesh is exported.

Thanks,
Nenad.
___
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] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7

[Nenad Vujicic]

Hello everyone,

 4   Creating library
 E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.lib and object
 E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.exp
 4MPI.obj : error LNK2019: unresolved external symbol
 __imp__lt_dladvise_destroy referenced in function _dlopen_mpi_lib
 4MPI.obj : error LNK2019: unresolved external symbol
 __imp__lt_dlopenadvise referenced in function _dlopen_mpi_lib
 ...
 4E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.dll : fatal
 error LNK1120: 8 unresolved externals

Has anyone succeeded to recreate and solve above linking problems
under Windows when using Python / OpenMPI with ParaView 3.8.1?

Best regards,
Nenad.
___
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] How to add plug-in's parameters to ParaView state file

[Nenad Vujicic]

Dear Utkarsh,

On Mon, Jan 3, 2011 at 2:30 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 Every time SaveState is called in the ParaView GUI, pqApplicationCore
 singleton fires a signal stateSaved(vtkPVXMLElement*). Your code can
 handle this signal to add new child XML elements to the root.
 Similarly, there's a stateLoadeded(...) signal that gets fired that
 you can handle to load the custom elements from the state xml.


Thank You very much on Your suggestion. It works perfectly. Is there
also some easy solution when working with pvpython and pvbatch clients
or I should add Python parsing code to servermanager.py
(servermanager::LoadState())?

Thanks,
Nenad.
___
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 add plug-in's parameters to ParaView state file

[Nenad Vujicic]

Hello everyone,

I have developed exporter plug-in for ParaView with 50+ input
parameters. At the moment, I'm setting parameters from dialog I start
on menu action and preserve their values between ParaView sessions by
using QSettings object. Is it possible to save these values in
ParaView state files without changing ParaView main sources?

Thanks,
Nenad.
___
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] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7

[Nenad Vujicic]

Dear Dave,

On Mon, Nov 29, 2010 at 4:45 PM, Dave Partyka dave.part...@kitware.com wrote:
 Hi Nenad, Sorry for not replying, Utkarsh just pointed your email out to me.
 Let me give this a try to see if I can recreate the problem.


Thank You very much for Your help. It seems I made little mistake in
previous message - everything builds fine under Linux, there is a
problem only under Windows. I'm sorry for this mistake. Here is a list
of steps I make under Windows:

1. Download OpenMPI 1.4.3. (from www.open-mpi.org) and ParaView 3.8.1 sources
2. I recompile OpenMPI with standard options in release mode:
  - mkdir build, cd build, cmake -DCMAKE_BUILD_TYPE:STRING=Release ..,
open .sln file and build solution in Release mode
3. I create OpenMPI NSIS package (cpack -G NSIS --config
CPackConfig.cmake) and install it
4. I recompile ParaView sources with BUILD_SHARED_LIBS,
PARAVIEW_USE_MPI and PARAVIEW_ENABLE_PYTHON options turned on:
  - mkdir build, cd build, cmake-gui .., open .sln file and build
solution in Release mode
  - After the first configure, I set above 3 options, after the second
I update following options:
  + MPI_EXTRA_LIBRARY
??libmpi.lib;??libmpi_cxx.lib;??libopen-pal.lib;??libopen-rte.lib
  * instead of ?? is full path to .lib file
  + MPI_INCLUDE_PATH C:/Program Files/OpenMPI_v1.4.3-win32/include
  + MPI_LIBRARY C:/Program Files/OpenMPI_v1.4.3-win32/lib/libmpi_cxx.lib

I have Vista SP2, Visual Studio 2008 SP1 and Python 2.7 installed on
problematic machine. Tell me if You need more informations.

Best regards,
Nenad.
___
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] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7

[Nenad Vujicic]

Hello everyone,

I tried to compile ParaView 3.8.1 with BUILD_SHARED_LIBS,
PARAVIEW_USE_MPI and PARAVIEW_ENABLE_PYTHON options turned on, but I
get following linking errors:

4   Creating library
E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.lib and object
E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.exp
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dladvise_destroy referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dlopenadvise referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dladvise_global referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dladvise_ext referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dladvise_init referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlinit
referenced in function _dlopen_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlexit
referenced in function _dlclose_mpi_lib
4MPI.obj : error LNK2019: unresolved external symbol
__imp__lt_dlclose referenced in function _dlclose_mpi_lib
4E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.dll : fatal
error LNK1120: 8 unresolved externals

I use Visual Studio 2008 SP1, CMake 2.8 and OpenMPI 1.4.3 (compiled
with default options in Release mode). Same errors I get when trying
to compile under CentOS 5.3 (with precompiled OpenMPI 1.4.3 sources)
too. Other projects are compiled well in both cases. Does anyone knows
how to solve this problem? I believe the solution is in setting
appropriate building options for OpenMPI, but I'm not sure what to do.

Thanks,
Nenad.
___
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 include ParaView documentation to NSIS package

[Nenad Vujicic]

Hello all,

I downloaded ParaView 3.8 sources, compiled them using VS 2008 with
default options (+ turned on BUILD_SHARED_LIBS,
PARAVIEW_ENABLE_PYTHON, BUILD_DOCUMENTATION and
DOCUMENTATION_HTML_HELP) and created NSIS installer (using 'cpack -G
NSIS --config Applications/ParaView/CPackParaViewConfig.cmake').
Unfortunately, ParaView documentation is missing in created ParaView
installer.

I also tried under CentOS 5, but got same results - missing
documentation. How to include ParaView documentation into my
installer?

Thanks,
Nenad.
___
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