[Paraview] Differences between OpenGL and OpenGL2 versions of ParaView

Adam Lyon lyon at fnal.gov
Mon Aug 3 14:59:55 EDT 2015


Hi Joachim, Do you want me to send in a bug report for these problems? I
assume there's no work-around that I can do to make things work. Using
OpenGL2 is quite a bit faster, so I'm hoping a fix can come out soon.
Thanks! -- Adam

*------*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>

On Fri, Jul 31, 2015 at 10:53 AM, Adam L Lyon <lyon at fnal.gov> wrote:

> Hi Joachim - Yes, I noticed that the default color is now vtkBlockColors.
> However I changed that to the "color" vector in my data and that change was
> not honored by the program. Thanks, Adam
>
> *------*
>
> *Adam L. Lyon*
> *Scientist; Associate Division Head for Systems for Scientific
> Applications*
>
> Scientific Computing Division & Muon g-2 Experiment
> Fermi National Accelerator Laboratory
> 630 840 5522 office
> www.fnal.gov
> lyon at fnal.gov
>
> Connect with us!
> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
> <https://www.facebook.com/Fermilab>  |  Twitter
> <https://twitter.com/Fermilab>
>
> On Fri, Jul 31, 2015 at 2:41 AM, Joachim Pouderoux <
> joachim.pouderoux at kitware.com> wrote:
>
>> Adam,
>>
>> The color difference can be explained by the default coloring mode
>> introduced recently (before the git tag version you tested with).
>> Multiblocks are now automatically colored by blocks. Toggle the Color
>> Legend and see the coloring array, "vtkBlockColors" is selected wereas in
>> previous version it was Solid Color I guess.
>> Regarding the missing pieces, I can tell that with the same git version
>> and with the OpenGL backend 1 (the old), all pieces are correctly drawn.
>> What is specific is that this missing blocks (the data has like a global
>> gemetry block + all the internal pieces) are the last block if the first
>> level block hierarchy.
>>
>> Joachim
>>
>>
>> *Joachim Pouderoux*
>>
>> *PhD, Technical Expert*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2015-07-30 22:19 GMT+02:00 Adam Lyon <lyon at fnal.gov>:
>>
>>> Hi,  I'm trying to use ParaView built with OpenGL2, hoping to see some
>>> speed improvement when I interact with my visualization. Indeed for a
>>> complicated geometry I see significant speed up (e.g. ~25 fps with OpenGL2
>>> vs. 5 fps with regular ParaView). But I also see serious errors in the
>>> display. I've attached two images of our "g-2 muon storage ring" (never
>>> mind what it actually is, though it is very cool :-) ..
>>>
>>> [image: Inline image 1]
>>>
>>> The first, mostly blue image, is from regular ParaView (downloaded Mac
>>> binary 4.3.1 64 bit)  and is what the ring is supposed to look like. There
>>> is a color vector selected and I've unchecked "Map scalars" so that the
>>> colors are "true". And indeed the RGB color values in the vector are what
>>> is shown on the display.
>>>
>>>
>>> [image: Inline image 2]
>>> The next image, with a chunk on the left side missing, is from the
>>> OpenGL2 ParaView (Mac built from source 4.3.1-882-gbdceec7 64 bit)
>>> configured identically as the other ParaView. So it should look identical
>>> to the mostly blue picture. Along with the missing chunk, you see the
>>> colors look very wrong. What's even stranger is that the missing chunk is
>>> really missing - not invisible - the visualization is made of multiblock
>>> datasets, and right clicking where a structure should be only brings up the
>>> link camera option.
>>>
>>> You can try this yourself -- see
>>> https://www.dropbox.com/sh/900ocfc90v0w3r6/AACmqz8kVrGPUMnJbpxAFOzBa?dl=0
>>> . The "gm2ring.zip" file has gm2ring.vtm (with the corresponding gm2ring
>>> directory) and gm2ring.pvsm to restore my configuration.
>>>
>>> I'm looking forward to using the OpenGL2 version when it works better. I
>>> hope this helps in working out its kinks (or hoping to find out I've built
>>> or configured something incorrectly). Let me know how I can help!  Thanks!
>>> -- Adam
>>> *------*
>>>
>>> *Adam L. Lyon*
>>> *Scientist; Associate Division Head for Systems for Scientific
>>> Applications*
>>>
>>> Scientific Computing Division & Muon g-2 Experiment
>>> Fermi National Accelerator Laboratory
>>> 630 840 5522 office
>>> www.fnal.gov
>>> lyon at fnal.gov
>>>
>>> Connect with us!
>>> Newsletter <http://www.fnal.gov/pub/today/>  |  Facebook
>>> <https://www.facebook.com/Fermilab>  |  Twitter
>>> <https://twitter.com/Fermilab>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150803/12c290a4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl_good.png
Type: image/png
Size: 19431 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150803/12c290a4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gm2ringsim_opengl2_bad.png
Type: image/png
Size: 16709 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150803/12c290a4/attachment-0001.png>


More information about the ParaView mailing list