Re: [Paraview] basics of paraview client server programming

[Peter Debuchev]

Excellent, thank you!

2016-06-06 19:01 GMT+02:00 Utkarsh Ayachit :

> Attached.
>
> On Mon, Jun 6, 2016 at 12:59 PM, Peter Debuchev 
> wrote:
> > Dear Utkarsh,
> > thank you for your offer to search the old ParaView Guide v3
> client-server
> > programming chapter. May I ask whether your search has been successful?
> Even
> > a scan of the pages from the relevant chapter would be nice, if you are
> > authorized to share it.
> >
> > I have read all your links, and they are great to get an idea about the
> > changes that are going on. However, I would need a well structured
> > book-chapter which builds the story from the basic requirements to a
> full,
> > simple application. The information in the links is so spread that
> > everything seems to depend on everything else, and nowhere is it clear
> what
> > are ideas for the future, what is under current development, and what has
> > been deprecated again.
> > I would really like to read again the chapter from ParaView Guide v3,
> which
> > I remember gave me perfect insight into Paraview years ago. Even if it is
> > rather out of date, it would give me a solid basis to better understand
> the
> > current developments.
> >
> > Peter
> >
> > 2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit  >:
> >>
> >> Alas, there's nothing up-to-date. I've been meaning to write a blog
> >> series covering various aspect of ParaView internals, but it's hard to
> >> find some downtime to get that going. I'll try to see if I can find
> >> the old PDF for the ParaView Guide v3 and share the old chapter
> >> (although obsolete, but basic design may still be relevant). The
> >> ParaView developers Wiki
> >> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
> >> articles that we wrote with coming up with the design for some of the
> >> core components. The implementations generally differ slightly from
> >> the design and may have names/APIs changed since, but nonetheless may
> >> be helpful in understanding how things came about. Specifically,
> >>
> >> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
> >> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> >> [3]
> http://www.paraview.org/ParaView/index.php/Views_And_Representations
> >> [4]
> >>
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
> >>
> >> Utkarsh
> >>
> >> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva 
> wrote:
> >> > +1 for that. I'm very interested to know if there's such book or
> >> > document.
> >> >
> >> > When I started developing a plug-in for ParaView I found this
> >> > presentation
> >> > almost by accident. Maybe it can help you. Apparently it was used in a
> >> > conference/workshop (VIS08?) to describe briefly the proxy system, and
> >> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
> >> > for
> >> > details (see slide 30). Unfortunately the version 3 of the Guide I
> >> > couldn't
> >> > find.
> >> >
> >> > Ellon
> >> >
> >> >
> >> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> >> >
> >> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> >> > vtkProxies etc. are set up to interact with a pvserver or with a
> custom
> >> > server application?
> >> > I am not talking about short demos that show how to create and
> display a
> >> > sphere using pvpython. What I am looking for is a book chapter or
> >> > similar
> >> > explaining the principles behind vtkSMSessions, vtkProcies etc.
> >> >
> >> > Does anybody remember, which of the VTK or ITK or Paraview books
> >> > included
> >> > such chapters?
> >> >
> >> > Peter
> >> >
> >> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev :
> >> >>
> >> >> Dear Paraview programmers,
> >> >> I am looking for some information about the basic principles of
> >> >> Paraviews
> >> >> client-server model, the setup of client proxies and the
> communication
> >> >> design.
> >> >>
> >> >> I think that I have seen a chapter with a short introduction on these
> >> >> topics some years ago. It was in one of the VTK books or in the
> >> >> Paraview
> >> >> User's Guide. Now I cannot find this chapter again. Has it been
> removed
> >> >> in
> >> >> the latest edition of these books? Or is it described in a different
> >> >> book
> >> >> which I don't remember?
> >> >>
> >> >> Peter
> >> >
> >> >
> >> >
> >> >
> >> > ___
> >> > 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] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

[Utkarsh Ayachit]

Here's a MR for update superbuild that builds OSMesa 11.2.2. I've only
updated OSMesa. I'll tackle mesa-glx next.

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/114

Utkarsh

On Mon, Jun 6, 2016 at 12:31 PM, Utkarsh Ayachit
 wrote:
> I am working on updating superbuild today. Just hold on. I'll email
> once I have it working.
>
> On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
> ARL (US)  wrote:
>> CLASSIFICATION: UNCLASSIFIED
>>
>> Utkarsh,
>>
>> I have rebuilt osmesa using mesa 11.2.2 but
>> it ParaView rebuilt with the new version is giving
>> me the same error as before, complaining that the
>> GL version 2.1 with gpu_shader4 extension is not
>> Supported.
>>
>> I think I know  why  this is occurring and I wondered if you
>> could confirm this for me.
>>
>> I configured mesa with these parameters
>>
>> ./configure \
>> --disable-xvmc \
>> --disable-glx \
>> --disable-dri \
>> --with-dri-drivers= \
>> --with-gallium-drivers=swrast \
>> --enable-texture-float \
>> --disable-egl \
>> --with-egl-platforms= \
>> --enable-gallium-osmesa \
>> --enable-gallium-llvm=yes \
>> --prefix=
>>
>> but, I did not have a version of llvm available
>> and the configure script then set
>>
>> Llvm = no
>>
>> From my reading of this webpage
>>
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>>
>> It seems that without gallium-llvm,
>> the version of OpenGL built reverts to an older version,
>> which I believe is why I am still getting the error.
>>
>> Would you agree with this?
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~
>> Joseph G. Hennessey Ph.D., Lockheed Martin
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>>
>> -Original Message-
>> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>> Sent: Thursday, June 02, 2016 4:19 PM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> 
>> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
>> ; Su, Simon M CIV USARMY RDECOM ARL (US)
>> ; ParaView 
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>> (UNCLASSIFIED)
>>
>> All active links contained in this email were disabled.  Please verify the
>> identity of the sender, and confirm the authenticity of all links contained
>> within the message prior to copying and pasting the address to a Web browser.
>>
>>
>>
>>
>> 
>>
>>> And I have tried replacing the library
>>> lib/paraview-5.0/libOSMesa.so.7
>>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>>> giving the same error
>>
>> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
>> OSMesaCreateContextAttribs() which is needed to create correct OpenGL 
>> context.
>> The API is used at compile time if appropriate osmesa.h is being used.
>>
>> You can try to update Projects/unix/osmesa.cmake in the superbuild source to
>> use the configure arguments you used, and also change versions.cmake in the
>> same repo to point to change the osmesa source tar ball to be 11.2. Now the
>> superbuid will build 11.2 instead and it should then have the new API
>> available.
>>
>> [1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>>
>>
>> CLASSIFICATION: UNCLASSIFIED
___
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] basics of paraview client server programming

[Peter Debuchev]

Dear Utkarsh,
thank you for your offer to search the old ParaView Guide v3 client-server
programming chapter. May I ask whether your search has been successful?
Even a scan of the pages from the relevant chapter would be nice, if you
are authorized to share it.

I have read all your links, and they are great to get an idea about the
changes that are going on. However, I would need a well structured
book-chapter which builds the story from the basic requirements to a full,
simple application. The information in the links is so spread that
everything seems to depend on everything else, and nowhere is it clear what
are ideas for the future, what is under current development, and what has
been deprecated again.
I would really like to read again the chapter from ParaView Guide v3, which
I remember gave me perfect insight into Paraview years ago. Even if it is
rather out of date, it would give me a solid basis to better understand the
current developments.

Peter

2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit :

> Alas, there's nothing up-to-date. I've been meaning to write a blog
> series covering various aspect of ParaView internals, but it's hard to
> find some downtime to get that going. I'll try to see if I can find
> the old PDF for the ParaView Guide v3 and share the old chapter
> (although obsolete, but basic design may still be relevant). The
> ParaView developers Wiki
> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
> articles that we wrote with coming up with the design for some of the
> core components. The implementations generally differ slightly from
> the design and may have names/APIs changed since, but nonetheless may
> be helpful in understanding how things came about. Specifically,
>
> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> [3] http://www.paraview.org/ParaView/index.php/Views_And_Representations
> [4]
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
>
> Utkarsh
>
> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva  wrote:
> > +1 for that. I'm very interested to know if there's such book or
> document.
> >
> > When I started developing a plug-in for ParaView I found this
> presentation
> > almost by accident. Maybe it can help you. Apparently it was used in a
> > conference/workshop (VIS08?) to describe briefly the proxy system, and
> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
> for
> > details (see slide 30). Unfortunately the version 3 of the Guide I
> couldn't
> > find.
> >
> > Ellon
> >
> >
> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> >
> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> > vtkProxies etc. are set up to interact with a pvserver or with a custom
> > server application?
> > I am not talking about short demos that show how to create and display a
> > sphere using pvpython. What I am looking for is a book chapter or similar
> > explaining the principles behind vtkSMSessions, vtkProcies etc.
> >
> > Does anybody remember, which of the VTK or ITK or Paraview books included
> > such chapters?
> >
> > Peter
> >
> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev :
> >>
> >> Dear Paraview programmers,
> >> I am looking for some information about the basic principles of
> Paraviews
> >> client-server model, the setup of client proxies and the communication
> >> design.
> >>
> >> I think that I have seen a chapter with a short introduction on these
> >> topics some years ago. It was in one of the VTK books or in the Paraview
> >> User's Guide. Now I cannot find this chapter again. Has it been removed
> in
> >> the latest edition of these books? Or is it described in a different
> book
> >> which I don't remember?
> >>
> >> Peter
> >
> >
> >
> >
> > ___
> > 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
> >
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects 

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

[Utkarsh Ayachit]

I am working on updating superbuild today. Just hold on. I'll email
once I have it working.

On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
ARL (US)  wrote:
> CLASSIFICATION: UNCLASSIFIED
>
> Utkarsh,
>
> I have rebuilt osmesa using mesa 11.2.2 but
> it ParaView rebuilt with the new version is giving
> me the same error as before, complaining that the
> GL version 2.1 with gpu_shader4 extension is not
> Supported.
>
> I think I know  why  this is occurring and I wondered if you
> could confirm this for me.
>
> I configured mesa with these parameters
>
> ./configure \
> --disable-xvmc \
> --disable-glx \
> --disable-dri \
> --with-dri-drivers= \
> --with-gallium-drivers=swrast \
> --enable-texture-float \
> --disable-egl \
> --with-egl-platforms= \
> --enable-gallium-osmesa \
> --enable-gallium-llvm=yes \
> --prefix=
>
> but, I did not have a version of llvm available
> and the configure script then set
>
> Llvm = no
>
> From my reading of this webpage
>
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>
> It seems that without gallium-llvm,
> the version of OpenGL built reverts to an older version,
> which I believe is why I am still getting the error.
>
> Would you agree with this?
>
> Thanks,
>
> Joe
>
> ~~~
> Joseph G. Hennessey Ph.D., Lockheed Martin
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, June 02, 2016 4:19 PM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> 
> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> ; Su, Simon M CIV USARMY RDECOM ARL (US)
> ; ParaView 
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
> (UNCLASSIFIED)
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web browser.
>
>
>
>
> 
>
>> And I have tried replacing the library
>> lib/paraview-5.0/libOSMesa.so.7
>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>> giving the same error
>
> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
> OSMesaCreateContextAttribs() which is needed to create correct OpenGL context.
> The API is used at compile time if appropriate osmesa.h is being used.
>
> You can try to update Projects/unix/osmesa.cmake in the superbuild source to
> use the configure arguments you used, and also change versions.cmake in the
> same repo to point to change the osmesa source tar ball to be 11.2. Now the
> superbuid will build 11.2 instead and it should then have the new API
> available.
>
> [1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>
>
> CLASSIFICATION: UNCLASSIFIED
___
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] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

[Hennessey, Joseph G CTR USARMY RDECOM ARL (US)]

CLASSIFICATION: UNCLASSIFIED

Utkarsh,

I have rebuilt osmesa using mesa 11.2.2 but
it ParaView rebuilt with the new version is giving
me the same error as before, complaining that the
GL version 2.1 with gpu_shader4 extension is not
Supported.

I think I know  why  this is occurring and I wondered if you
could confirm this for me.

I configured mesa with these parameters

./configure \
--disable-xvmc \
--disable-glx \
--disable-dri \
--with-dri-drivers= \
--with-gallium-drivers=swrast \
--enable-texture-float \
--disable-egl \
--with-egl-platforms= \
--enable-gallium-osmesa \
--enable-gallium-llvm=yes \
--prefix=

but, I did not have a version of llvm available
and the configure script then set

Llvm = no

>From my reading of this webpage

http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D

It seems that without gallium-llvm,
the version of OpenGL built reverts to an older version,
which I believe is why I am still getting the error.

Would you agree with this?

Thanks,

Joe

~~~
Joseph G. Hennessey Ph.D., Lockheed Martin
Army Research Lab
DOD Supercomputing Resource Center


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Thursday, June 02, 2016 4:19 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 

Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
; Su, Simon M CIV USARMY RDECOM ARL (US) 
; ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader 
(UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify the 
identity of the sender, and confirm the authenticity of all links contained 
within the message prior to copying and pasting the address to a Web browser.






> And I have tried replacing the library
> lib/paraview-5.0/libOSMesa.so.7
> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
> giving the same error

Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
OSMesaCreateContextAttribs() which is needed to create correct OpenGL context. 
The API is used at compile time if appropriate osmesa.h is being used.

You can try to update Projects/unix/osmesa.cmake in the superbuild source to 
use the configure arguments you used, and also change versions.cmake in the 
same repo to point to change the osmesa source tar ball to be 11.2. Now the 
superbuid will build 11.2 instead and it should then have the new API 
available.

[1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html


CLASSIFICATION: UNCLASSIFIED


smime.p7s
Description: S/MIME cryptographic signature
___
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] antialiasing in export scene, vector graphics, font selection

[David Lonie]

On Fri, Jun 3, 2016 at 5:03 PM, Mark Lohry  wrote:

> 1) Assuming "export scene" is the preferred way to output images, how do I
> get anti-aliasing of the produced image? I see no option for it. Failing
> that -- if I choose to not rasterize the image, I'm losing some color
> information whereas the save screenshot function correctly outputs the
> color (see attached figures).
>

The raster-format exports tend to just grab the image directly from the
OpenGL framebuffer, but unfortunately anti-aliased rendering is not
currently enabled in ParaView as it interferes with some of the other
rendering passes. There is some work-in-progress on adding DPI options to
paraview exports that will help with this issue in a future release.

I'm not sure what's going on with the color in the vector export. The GL2PS
library used to generate the vector graphics files is somewhat fickle with
some coloring methods, you may be able to play with the rendering settings
to get that to come out right. I know that, for instance, the "Interpolate
Colors Before Mapping" option will often cause issues.

Right now your best bet for getting an anti-aliased export from ParaView is
to emulate SSAA by making a screenshot with a custom resolution. By setting
the resolution in File > Save Screenshot to a larger resolution than your
desired image size and then shrinking the image externally you should get a
smoother result.


>
> 2) In the color legend font properties, only Arial, Courier, and Times are
> available. Is there a way to use some other font from my system?
>

This is currently not possible in ParaView. There is support for custom
fonts in VTK (the library that drives ParaView's rendering), but it has not
been exposed in ParaView.

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

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

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