Re: [Paraview] Paraview crashes with netCDF

[Adam Dershowitz]

Thanks.

I actually just created a ticket also, a few minutes after you did:
https://gitlab.kitware.com/paraview/paraview/issues/17174

I’ll close mine since it is redundant with yours.


-- Adam


From: "Moreland, Kenneth" 
Date: Monday, February 13, 2017 at 4:01 PM
To: Dershowitz Adam , "ParaView@paraview.org" 

Subject: Re: [Paraview] Paraview crashes with netCDF

Adam,

Was able to replicate your problem. It looks like there are minor issues with 
both gdalwarp and ParaView that together are causing the crash.

The first problem is that gdalwarp is not writing the units attribute correctly 
when outputting the coordinates in feet. Instead, the units are set to an empty 
string. This seems wrong. The attribute should be set to “ft” or “feet”. When 
you use gdalwarp to write units of meters, it correctly writes this attribute 
as “m”. This is probably a bug, but it shouldn’t cause ParaView to crash.

So you probably already see where this is going. NetCDF attributes of empty 
strings are odd, and the ParaView reader probably has never encountered one 
before. Lo and behold in this case the reader tries to pull a pointer out of an 
empty std::string, and std::string throws an exception.

I’ve raised a bug for ParaView 
(https://gitlab.kitware.com/paraview/paraview/issues/17173)
 and will look into fixing this. I’ll leave it up to you whether you want to 
contact the GDAL developers about the issue with gdalwarp.

-Ken

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Adam 
Dershowitz
Sent: Monday, February 13, 2017 9:20 AM
To: ParaView@paraview.org
Subject: [EXTERNAL] Re: [Paraview] Paraview crashes with netCDF

I found a bit more information.  When pareview crashes, here is part of the 
crash log:

Application Specific Information:
terminating with uncaught exception of type std::out_of_range: basic_string
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fffcb43add6 __pthread_kill + 
10
1   libsystem_pthread.dylib  0x7fffcb526787 pthread_kill + 90
2   libsystem_c.dylib   0x7fffcb3a0420 abort + 129
3   libc++abi.dylib   0x7fffc9efb85a abort_message + 266
4   libc++abi.dylib   0x7fffc9f20c37 
default_terminate_handler() + 243
5   libobjc.A.dylib 0x7fffcaa2af33 _objc_terminate() + 124
6   libc++abi.dylib   0x7fffc9f1dd69 std::__terminate(void 
(*)()) + 8
7   libc++abi.dylib   0x7fffc9f1d9f2 __cxa_rethrow + 99
8   QtCore 0x00010db17d2d 
QEventLoop::exec(QFlags) + 845
9   QtCore 0x00010db1ad97 
QCoreApplication::exec() + 199
10  org.paraview.ParaView 0x00010b083fd2 main + 386
11  libdyld.dylib   0x7fffcb30c255 start + 1

Any idea why that happens with one feet, but not meters in an otherwise 
identical file?

-- Adam


From: Dershowitz Adam 
>
Date: Tuesday, February 7, 2017 at 11:58 AM
To: "ParaView@paraview.org" 
>
Subject: Paraview crashes with netCDF

I have a geotiff file that I want to view in Paraview.  But, Paraview seems to 
not show the correct offset (0,0 instead of respected the offset).  The work 
around I have been trying is to warp it to the correct location using gdalwarp 
and to export it as a netCDF.  Then Paraview should be able to show it 
correctly.
But, I have run into a crash.
If I do this:
gdalwarp  -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc

then I try to open test.nc in Paraview immediately crashes.

While, instead if do this:

gdalwarp  -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc

then it opens fine.  The difference between these two files is that EPSG 3652 
uses feet (which is better for me, for this particular project) while 3651 uses 
meters.  Both appear to be valid NetCDF files.  I’ve tried both readers “CAM 
NetCDF (Unstructured)” and “NetCDF files generic and CF conventions” with the 
same results.

I’m running Paraview 5.2.0 64-bit on Mac OS 10.12.3.  But, I have seen 
identical results on an older Mac with a prior OS.  I had also tried an older 
version of Paraview with the same result.

Any ideas why this consistently crashes Paraview, or what to do about it?  
Using netCDF was already a work around, and I willing to try others to view 
these files.  The offset and scale are important because I then need to put in 
other data that is in the correct location and units.

The files are 

[Paraview] Automating contour isosurface values in parallel Catalyst Python script

[Yvan Fournier]

Hello,

I'm in the process of migrating some VTK scripts in the Code_Saturne (code-
saturne.org) test suite to Catalyst Python scripts, and am having some
difficulty automating some cases using contour plots:

For time-dependent data, I do not know the value ranges in advance, and would
like to query them so as to build an Isosurface values array spanning that
range.

I can manage to access the point and cell data arrays and ther ranges, but
printing the ranges in parallel, it seems I have local values only, while I need
a global range.

I searched for examples in the documentation, on the Wiki, ..., and found an
example for MinMax, but don't seem to ba able to access the correct type of
Proxy under Catalyst (the default servermanager is not connected in the usual
way.

For scalar bar color look-up tables, I can manage with
"coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in the
coprocessing script, but for a more general case such as thar needed for contour
plots, I've been running around in circles in the last hours trying to find and
adapt a relevant example.

Does anyone have a suggestion ? Thanks in advance,

Yvan Fournier
___
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 crashes with netCDF

[Moreland, Kenneth]

Adam,

Was able to replicate your problem. It looks like there are minor issues with 
both gdalwarp and ParaView that together are causing the crash.

The first problem is that gdalwarp is not writing the units attribute correctly 
when outputting the coordinates in feet. Instead, the units are set to an empty 
string. This seems wrong. The attribute should be set to “ft” or “feet”. When 
you use gdalwarp to write units of meters, it correctly writes this attribute 
as “m”. This is probably a bug, but it shouldn’t cause ParaView to crash.

So you probably already see where this is going. NetCDF attributes of empty 
strings are odd, and the ParaView reader probably has never encountered one 
before. Lo and behold in this case the reader tries to pull a pointer out of an 
empty std::string, and std::string throws an exception.

I’ve raised a bug for ParaView 
(https://gitlab.kitware.com/paraview/paraview/issues/17173) and will look into 
fixing this. I’ll leave it up to you whether you want to contact the GDAL 
developers about the issue with gdalwarp.

-Ken

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Adam 
Dershowitz
Sent: Monday, February 13, 2017 9:20 AM
To: ParaView@paraview.org
Subject: [EXTERNAL] Re: [Paraview] Paraview crashes with netCDF

I found a bit more information.  When pareview crashes, here is part of the 
crash log:

Application Specific Information:
terminating with uncaught exception of type std::out_of_range: basic_string
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fffcb43add6 __pthread_kill + 
10
1   libsystem_pthread.dylib  0x7fffcb526787 pthread_kill + 90
2   libsystem_c.dylib   0x7fffcb3a0420 abort + 129
3   libc++abi.dylib   0x7fffc9efb85a abort_message + 266
4   libc++abi.dylib   0x7fffc9f20c37 
default_terminate_handler() + 243
5   libobjc.A.dylib 0x7fffcaa2af33 _objc_terminate() + 124
6   libc++abi.dylib   0x7fffc9f1dd69 std::__terminate(void 
(*)()) + 8
7   libc++abi.dylib   0x7fffc9f1d9f2 __cxa_rethrow + 99
8   QtCore 0x00010db17d2d 
QEventLoop::exec(QFlags) + 845
9   QtCore 0x00010db1ad97 
QCoreApplication::exec() + 199
10  org.paraview.ParaView 0x00010b083fd2 main + 386
11  libdyld.dylib   0x7fffcb30c255 start + 1

Any idea why that happens with one feet, but not meters in an otherwise 
identical file?

-- Adam


From: Dershowitz Adam 
>
Date: Tuesday, February 7, 2017 at 11:58 AM
To: "ParaView@paraview.org" 
>
Subject: Paraview crashes with netCDF

I have a geotiff file that I want to view in Paraview.  But, Paraview seems to 
not show the correct offset (0,0 instead of respected the offset).  The work 
around I have been trying is to warp it to the correct location using gdalwarp 
and to export it as a netCDF.  Then Paraview should be able to show it 
correctly.
But, I have run into a crash.
If I do this:
gdalwarp  -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc

then I try to open test.nc in Paraview immediately crashes.

While, instead if do this:

gdalwarp  -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc

then it opens fine.  The difference between these two files is that EPSG 3652 
uses feet (which is better for me, for this particular project) while 3651 uses 
meters.  Both appear to be valid NetCDF files.  I’ve tried both readers “CAM 
NetCDF (Unstructured)” and “NetCDF files generic and CF conventions” with the 
same results.

I’m running Paraview 5.2.0 64-bit on Mac OS 10.12.3.  But, I have seen 
identical results on an older Mac with a prior OS.  I had also tried an older 
version of Paraview with the same result.

Any ideas why this consistently crashes Paraview, or what to do about it?  
Using netCDF was already a work around, and I willing to try others to view 
these files.  The offset and scale are important because I then need to put in 
other data that is in the correct location and units.

The files are too big for me to send to the mailing list, so I have not posted 
them.

Thanks,

-- Adam

___
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 5.3.0 Release Candidate 1 binaries are available for download

[Cory Quammen]

There are a couple known issues in ParaView 5.3.0-RC1 that we plan to
address in the next release candidate:

* The Mac OS X binary was built and packaged with Qt4 instead of Qt5
* On Mac OS X, the included BDATReader, BDATSeriesReader, and
GLGPUVortexFilter will not load (Issue 17170)
* On Mac OS X, a crash occurs when adding a source when Auto MPI is
enabled (Issue 17171)
* Enabling the OSPRay renderer sometimes results in a crash. (Issue 17172)

- Cory

On Mon, Feb 13, 2017 at 11:49 AM, Cory Quammen  wrote:
> Folks,
>
> Binaries and source code zip files and tar balls for ParaView 5.3.0
> Release Candidate 1 are now available for download from
>
> http://www.paraview.org/download/
>
> Please let us know if you run into any problems with this release candidate.
>
> Sincerely,
> Cory
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.



-- 
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] (no subject)

[Ben Boeckel]

On Mon, Feb 13, 2017 at 14:16:03 -0500, Bishwajit Dutta wrote:
> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download=b10bd3f7136ef809f1df7ad5c94c553f=MD5
> ("Couldn't connect to server")
> 
> http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f
> ("Couldn't connect to server")

This indicates that you can't contact the host. Does it work if you
change the URLs to use `https` in CMake/vtkExternalData.cmake?

> Also I wanted to run a paraview python script with CPU acceleration. Will
> this compilation generate
> pvpython and can I pass it  --mesa-llvm for running the script (I assume by
> default it will use GPU acceleration as I have NVIDIA GPU on my system)?

5.0.0 did not have support for that flag (I think). That flag also
assumes certain things about the way ParaView was built (namely that
Mesa is available under `lib/paraview-5.x/mesa`).

--Ben
___
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] (no subject) 5.0.0 Compilation issue

[Bishwajit Dutta]

Adding subject

On Mon, Feb 13, 2017 at 2:16 PM, Bishwajit Dutta  wrote:

> Hi All,
>
> I am trying to compile Paraview 5.0.0 on Ubuntu 14.04 but I am running
> into the below compilation issue. My machine is connected to the network (I
> tested it).
> Is there something wrong with the kitware URLs?
>
> logs--
>
> CMake Error at /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.
> 0.0-source/CMake/ExternalData.cmake:749 (message):
>   Object MD5=b10bd3f7136ef809f1df7ad5c94c553f not found at:
>
> http://midas3.kitware.com/midas/api/rest?method=midas.
> bitstream.download=b10bd3f7136ef809f1df7ad5c94c553f=MD5
> ("Couldn't connect to server")
> http://www.paraview.org/files/ExternalData/MD5/
> b10bd3f7136ef809f1df7ad5c94c553f ("Couldn't connect to server")
> Call Stack (most recent call first):
>   /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.
> 0.0-source/CMake/ExternalData.cmake:771 (_ExternalData_download_object)
>
>
> make[2]: *** [ExternalData/Testing/Data/Baseline/pqCoreBasicApp.png.md5-stamp]
> Error 1
> make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2
> make: *** [all] Erro
>
> -
>
> Also I wanted to run a paraview python script with CPU acceleration. Will
> this compilation generate
> pvpython and can I pass it  --mesa-llvm for running the script (I assume
> by default it will use GPU acceleration as I have NVIDIA GPU on my system)?
>
>
> Thank you for this.
>
> BR,
> Bishwajit
>
> ___
> 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] (no subject)

[Bishwajit Dutta]

Hi All,

I am trying to compile Paraview 5.0.0 on Ubuntu 14.04 but I am running into
the below compilation issue. My machine is connected to the network (I
tested it).
Is there something wrong with the kitware URLs?

logs--

CMake Error at
/home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.0.0-source/CMake/ExternalData.cmake:749
(message):
  Object MD5=b10bd3f7136ef809f1df7ad5c94c553f not found at:


http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download=b10bd3f7136ef809f1df7ad5c94c553f=MD5
("Couldn't connect to server")

http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f
("Couldn't connect to server")
Call Stack (most recent call first):

/home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.0.0-source/CMake/ExternalData.cmake:771
(_ExternalData_download_object)


make[2]: ***
[ExternalData/Testing/Data/Baseline/pqCoreBasicApp.png.md5-stamp] Error 1
make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2
make: *** [all] Erro

-

Also I wanted to run a paraview python script with CPU acceleration. Will
this compilation generate
pvpython and can I pass it  --mesa-llvm for running the script (I assume by
default it will use GPU acceleration as I have NVIDIA GPU on my system)?


Thank you for this.

BR,
Bishwajit
___
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] Object rendering problem on Windows 7 with Paraview 5.2

[Cory Quammen]

Awesome, thanks for the follow up, Bill.

On Mon, Feb 13, 2017 at 12:36 PM, Bill Greene  wrote:
> Thanks for the suggestions! I downloaded the drivers directly from ATI
> instead of letting Windows do the update and that appears to have
> fixed the problem I was seeing in Paraview 5.2.
>
> Thanks again for the help!
>
> Bill
>
> On Mon, Feb 13, 2017 at 11:54 AM, Ken Martin  wrote:
>> That card should be fine. I have seen this type of bug before and updating
>> the driver has fixed it. Specifically updating the driver to the latest from
>> ATI (sometimes computer vendors stop updating their copies).  Another way to
>> check what the problem is, is to stick a polydata normals filter in the
>> pipeline and then see if it works.
>>
>> Thanks
>> Ken
>>
>>
>> On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen 
>> wrote:
>>>
>>> Hi Bill,
>>>
>>> Let's keep the discussion on the mailing list so others can benefit
>>> from and contribute to the conversation.
>>>
>>> Ken,
>>>
>>> Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa
>>> 2010, I believe. It looks like it can support OpenGL 3.2 with Shader
>>> 4.1. I'm wondering if there is maybe a subtle shader compilation issue
>>> on the ATI hardware?
>>>
>>> Thanks,
>>> Cory
>>>
>>>
>>>
>>> On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene 
>>> wrote:
>>> > Thanks for getting back to me so quickly!
>>> >
>>> > The graphics device is an ATI Radeon HD 4200.
>>> >
>>> > Nothing is written to the Paraview "Output Messages" window.
>>> > Is there someplace else I should look?
>>> >
>>> > Bill
>>> >
>>> > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen
>>> >  wrote:
>>> >> Hi Bill,
>>> >>
>>> >> It sounds like the rendering backend isn't fully supported on your
>>> >> graphics card/driver combo. What kind of card is it? Are you getting
>>> >> any error messages?
>>> >>
>>> >> Thanks,
>>> >> Cory
>>> >>
>>> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene 
>>> >> wrote:
>>> >>> I have been using Paraview 4 on my windows 7 computer for quite a
>>> >>> while
>>> >>> now but wanted to upgrade to Paraview 5.
>>> >>>
>>> >>> Installation appeared to work fine but when I display a model I am
>>> >>> seeing
>>> >>> a rendering problem that I don't see in Paraview 4. If
>>> >>> Representation=Surface
>>> >>> and Coloring=Solid Color, the object is black regardless of how the
>>> >>> color is defined. If Rep=Surface with Edges, the edges do appear over
>>> >>> the
>>> >>> black object. If I select one of the results vectors under Coloring,
>>> >>> the
>>> >>> color bar is displayed and looks correct; but the object remains
>>> >>> black.
>>> >>>
>>> >>> I know that the graphics card in the computer is somewhat old ( the
>>> >>> drivers
>>> >>> are the latest for the device) but have no idea if that is related to
>>> >>> the problem
>>> >>> I'm seeing.
>>> >>>
>>> >>> I'm wondering if others have encountered this problem or if there is
>>> >>> some setting I
>>> >>> can change to avoid it.
>>> >>>
>>> >>> Thanks,
>>> >>>
>>> >>> Bill Greene
>>> >>> ___
>>> >>> 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.
>>>
>>>
>>>
>>> --
>>> Cory Quammen
>>> Staff R Engineer
>>> Kitware, Inc.
>>
>>
>>
>>
>> --
>> Ken Martin PhD
>> Chairman & CFO
>> Kitware Inc.
>> 28 Corporate Drive
>> Clifton Park NY 12065
>> 518 371 3971
>>
>> This communication, including all attachments, contains confidential and
>> legally privileged information, and it is intended only for the use of the
>> addressee.  Access to this email by anyone else is unauthorized. If you are
>> not the intended recipient, any disclosure, copying, distribution or any
>> action taken in reliance on it is prohibited and may be unlawful. If you
>> received this communication in error please notify us immediately and
>> destroy the original message.  Thank you.



-- 
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] Object rendering problem on Windows 7 with Paraview 5.2

[Bill Greene]

Thanks for the suggestions! I downloaded the drivers directly from ATI
instead of letting Windows do the update and that appears to have
fixed the problem I was seeing in Paraview 5.2.

Thanks again for the help!

Bill

On Mon, Feb 13, 2017 at 11:54 AM, Ken Martin  wrote:
> That card should be fine. I have seen this type of bug before and updating
> the driver has fixed it. Specifically updating the driver to the latest from
> ATI (sometimes computer vendors stop updating their copies).  Another way to
> check what the problem is, is to stick a polydata normals filter in the
> pipeline and then see if it works.
>
> Thanks
> Ken
>
>
> On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen 
> wrote:
>>
>> Hi Bill,
>>
>> Let's keep the discussion on the mailing list so others can benefit
>> from and contribute to the conversation.
>>
>> Ken,
>>
>> Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa
>> 2010, I believe. It looks like it can support OpenGL 3.2 with Shader
>> 4.1. I'm wondering if there is maybe a subtle shader compilation issue
>> on the ATI hardware?
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene 
>> wrote:
>> > Thanks for getting back to me so quickly!
>> >
>> > The graphics device is an ATI Radeon HD 4200.
>> >
>> > Nothing is written to the Paraview "Output Messages" window.
>> > Is there someplace else I should look?
>> >
>> > Bill
>> >
>> > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen
>> >  wrote:
>> >> Hi Bill,
>> >>
>> >> It sounds like the rendering backend isn't fully supported on your
>> >> graphics card/driver combo. What kind of card is it? Are you getting
>> >> any error messages?
>> >>
>> >> Thanks,
>> >> Cory
>> >>
>> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene 
>> >> wrote:
>> >>> I have been using Paraview 4 on my windows 7 computer for quite a
>> >>> while
>> >>> now but wanted to upgrade to Paraview 5.
>> >>>
>> >>> Installation appeared to work fine but when I display a model I am
>> >>> seeing
>> >>> a rendering problem that I don't see in Paraview 4. If
>> >>> Representation=Surface
>> >>> and Coloring=Solid Color, the object is black regardless of how the
>> >>> color is defined. If Rep=Surface with Edges, the edges do appear over
>> >>> the
>> >>> black object. If I select one of the results vectors under Coloring,
>> >>> the
>> >>> color bar is displayed and looks correct; but the object remains
>> >>> black.
>> >>>
>> >>> I know that the graphics card in the computer is somewhat old ( the
>> >>> drivers
>> >>> are the latest for the device) but have no idea if that is related to
>> >>> the problem
>> >>> I'm seeing.
>> >>>
>> >>> I'm wondering if others have encountered this problem or if there is
>> >>> some setting I
>> >>> can change to avoid it.
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Bill Greene
>> >>> ___
>> >>> 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.
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R Engineer
>> Kitware, Inc.
>
>
>
>
> --
> Ken Martin PhD
> Chairman & CFO
> Kitware Inc.
> 28 Corporate Drive
> Clifton Park NY 12065
> 518 371 3971
>
> This communication, including all attachments, contains confidential and
> legally privileged information, and it is intended only for the use of the
> addressee.  Access to this email by anyone else is unauthorized. If you are
> not the intended recipient, any disclosure, copying, distribution or any
> action taken in reliance on it is prohibited and may be unlawful. If you
> received this communication in error please notify us immediately and
> destroy the original message.  Thank you.
___
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] Object rendering problem on Windows 7 with Paraview 5.2

[Ken Martin]

That card should be fine. I have seen this type of bug before and updating
the driver has fixed it. Specifically updating the driver to the latest
from ATI (sometimes computer vendors stop updating their copies).  Another
way to check what the problem is, is to stick a polydata normals filter in
the pipeline and then see if it works.

Thanks
Ken


On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen 
wrote:

> Hi Bill,
>
> Let's keep the discussion on the mailing list so others can benefit
> from and contribute to the conversation.
>
> Ken,
>
> Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa
> 2010, I believe. It looks like it can support OpenGL 3.2 with Shader
> 4.1. I'm wondering if there is maybe a subtle shader compilation issue
> on the ATI hardware?
>
> Thanks,
> Cory
>
>
>
> On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene 
> wrote:
> > Thanks for getting back to me so quickly!
> >
> > The graphics device is an ATI Radeon HD 4200.
> >
> > Nothing is written to the Paraview "Output Messages" window.
> > Is there someplace else I should look?
> >
> > Bill
> >
> > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen 
> wrote:
> >> Hi Bill,
> >>
> >> It sounds like the rendering backend isn't fully supported on your
> >> graphics card/driver combo. What kind of card is it? Are you getting
> >> any error messages?
> >>
> >> Thanks,
> >> Cory
> >>
> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene 
> wrote:
> >>> I have been using Paraview 4 on my windows 7 computer for quite a while
> >>> now but wanted to upgrade to Paraview 5.
> >>>
> >>> Installation appeared to work fine but when I display a model I am
> seeing
> >>> a rendering problem that I don't see in Paraview 4. If
> Representation=Surface
> >>> and Coloring=Solid Color, the object is black regardless of how the
> >>> color is defined. If Rep=Surface with Edges, the edges do appear over
> the
> >>> black object. If I select one of the results vectors under Coloring,
> the
> >>> color bar is displayed and looks correct; but the object remains black.
> >>>
> >>> I know that the graphics card in the computer is somewhat old ( the
> drivers
> >>> are the latest for the device) but have no idea if that is related to
> >>> the problem
> >>> I'm seeing.
> >>>
> >>> I'm wondering if others have encountered this problem or if there is
> >>> some setting I
> >>> can change to avoid it.
> >>>
> >>> Thanks,
> >>>
> >>> Bill Greene
> >>> ___
> >>> 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.
>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>



-- 
Ken Martin PhD
Chairman & CFO
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971

This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.
___
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 5.3.0 Release Candidate 1 binaries are available for download

[Cory Quammen]

Folks,

Binaries and source code zip files and tar balls for ParaView 5.3.0
Release Candidate 1 are now available for download from

http://www.paraview.org/download/

Please let us know if you run into any problems with this release candidate.

Sincerely,
Cory

-- 
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] Object rendering problem on Windows 7 with Paraview 5.2

[Cory Quammen]

Hi Bill,

Let's keep the discussion on the mailing list so others can benefit
from and contribute to the conversation.

Ken,

Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa
2010, I believe. It looks like it can support OpenGL 3.2 with Shader
4.1. I'm wondering if there is maybe a subtle shader compilation issue
on the ATI hardware?

Thanks,
Cory



On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene  wrote:
> Thanks for getting back to me so quickly!
>
> The graphics device is an ATI Radeon HD 4200.
>
> Nothing is written to the Paraview "Output Messages" window.
> Is there someplace else I should look?
>
> Bill
>
> On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen  
> wrote:
>> Hi Bill,
>>
>> It sounds like the rendering backend isn't fully supported on your
>> graphics card/driver combo. What kind of card is it? Are you getting
>> any error messages?
>>
>> Thanks,
>> Cory
>>
>> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene  wrote:
>>> I have been using Paraview 4 on my windows 7 computer for quite a while
>>> now but wanted to upgrade to Paraview 5.
>>>
>>> Installation appeared to work fine but when I display a model I am seeing
>>> a rendering problem that I don't see in Paraview 4. If 
>>> Representation=Surface
>>> and Coloring=Solid Color, the object is black regardless of how the
>>> color is defined. If Rep=Surface with Edges, the edges do appear over the
>>> black object. If I select one of the results vectors under Coloring, the
>>> color bar is displayed and looks correct; but the object remains black.
>>>
>>> I know that the graphics card in the computer is somewhat old ( the drivers
>>> are the latest for the device) but have no idea if that is related to
>>> the problem
>>> I'm seeing.
>>>
>>> I'm wondering if others have encountered this problem or if there is
>>> some setting I
>>> can change to avoid it.
>>>
>>> Thanks,
>>>
>>> Bill Greene
>>> ___
>>> 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.



-- 
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] Cataylst pipeline not updating

[Andy Bauer]

Hi Tim,

It's possible that there's something funky going on when the data set being
passed through parts of the pipeline are empty. I'm hoping for the easy fix
with passing in the time since I've know that has caused unexpected
behavior before. If that doesn't solve your issue then I'll probably have
to do something similar and run it locally to see what's going on.

Cheers,
Andy

On Mon, Feb 13, 2017 at 11:06 AM, Gallagher, Timothy P <
tim.gallag...@gatech.edu> wrote:

> The RequestDataDescription is the same as the default output from the
> script generator, so I didn't include it. The DoCoProcessing gets called
> every time step and the volumeIntegrals data is updated and written
> correctly every delta_t, so I'm confident in that part.
>
>
> I will add the calls you suggested and re-run. It takes some time for it
> to evolve to the point something will happen -- I don't have it saving data
> frequently enough to run a quick test, I was expecting the pipeline to save
> it for me!
>
>
> The other thing that occurred to me -- is there something about the
> Contour filter that turns it off/disables it when the pipeline is built and
> there is no surface at that contour level?
>
>
> Thanks,
>
>
> Tim
>
>
> --
> *From:* Andy Bauer 
> *Sent:* Monday, February 13, 2017 10:56 AM
> *To:* Gallagher, Timothy P
> *Cc:* paraview@paraview.org
> *Subject:* Re: [Paraview] Cataylst pipeline not updating
>
> Hi Tim,
>
> Try adding in the current time to the UpdatePipeline() calls, e.g.
> *.UpdatePipeline(datadescription.GetCurrentTime())
>
> It's tough to tell with RequestDataDescription() missing but I assume that
> DoCoProcessing() is getting called when you want, correct?
>
> Let me know if that doesn't solve the problem.
>
> Best,
> Andy
>
> On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P <
> tim.gallag...@gatech.edu> wrote:
>
>> Back with another question!
>>
>>
>> I have a pipeline that has 1 input and 4 outputs. The simplest is a
>> IntegrateVariables filter hooked up to the input. Another branch of the
>> pipeline goes through several PythonCalculator filters and a
>> CellDataToPointData filter and then arrives at the three outputs:
>>
>>
>> 1. The CD2PD filter is connected to a Contour filter with a single level,
>> X. This is then connected to an IntegrateVariables filter (used to compute
>> the area of the Contour) and a Writer.
>>
>> 2. The CD2PD filter is also connected to another Contour filter with a
>> single level Y. This is connected to an IntegrateVariables and Writer just
>> as in 1.
>>
>> 3. The CD2PD filter is sliced two times with each slice in a different
>> render view to save images.
>>
>>
>> I have the coprocessor running every delta_t seconds. The initial
>> IntegrateVariables filter is updated with UpdatePipeline and then the
>> values are saved to disk. This works every step, no issues.
>>
>>
>> I then call UpdatePipeline on both of the Contour and both of the
>> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the
>> IntegrateVariables exceeds a threshold, and if it does, I save the
>> Contour's to disk as a VTK file. This is not working correctly.
>>
>>
>> If I start the simulation from a point where the Contour's exist in the
>> flow already, then everything works great and the Area field changes in
>> time and it saves the Contour's.
>>
>>
>> However, if the simulation starts without the Contours already in the
>> flow, the Area fields stay zero forever. It's as if the pipeline isn't
>> updating or something. I have attached the DoCoProcessing function used. I
>> don't see anything immediately obvious that would prevent it from updating
>> or getting the correct values for the Area.
>>
>>
>> Am I missing something about how the pipeline or contour filters update?
>>
>>
>> Thanks,
>>
>>
>> Tim
>>
>> ___
>> 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 crashes with netCDF

[Adam Dershowitz]

I found a bit more information.  When pareview crashes, here is part of the 
crash log:

Application Specific Information:
terminating with uncaught exception of type std::out_of_range: basic_string
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x7fffcb43add6 __pthread_kill + 
10
1   libsystem_pthread.dylib  0x7fffcb526787 pthread_kill + 90
2   libsystem_c.dylib   0x7fffcb3a0420 abort + 129
3   libc++abi.dylib   0x7fffc9efb85a abort_message + 266
4   libc++abi.dylib   0x7fffc9f20c37 
default_terminate_handler() + 243
5   libobjc.A.dylib 0x7fffcaa2af33 _objc_terminate() + 124
6   libc++abi.dylib   0x7fffc9f1dd69 std::__terminate(void 
(*)()) + 8
7   libc++abi.dylib   0x7fffc9f1d9f2 __cxa_rethrow + 99
8   QtCore 0x00010db17d2d 
QEventLoop::exec(QFlags) + 845
9   QtCore 0x00010db1ad97 
QCoreApplication::exec() + 199
10  org.paraview.ParaView 0x00010b083fd2 main + 386
11  libdyld.dylib   0x7fffcb30c255 start + 1

Any idea why that happens with one feet, but not meters in an otherwise 
identical file?

-- Adam


From: Dershowitz Adam 
Date: Tuesday, February 7, 2017 at 11:58 AM
To: "ParaView@paraview.org" 
Subject: Paraview crashes with netCDF

I have a geotiff file that I want to view in Paraview.  But, Paraview seems to 
not show the correct offset (0,0 instead of respected the offset).  The work 
around I have been trying is to warp it to the correct location using gdalwarp 
and to export it as a netCDF.  Then Paraview should be able to show it 
correctly.
But, I have run into a crash.
If I do this:
gdalwarp  -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc

then I try to open test.nc in Paraview immediately crashes.

While, instead if do this:

gdalwarp  -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc

then it opens fine.  The difference between these two files is that EPSG 3652 
uses feet (which is better for me, for this particular project) while 3651 uses 
meters.  Both appear to be valid NetCDF files.  I’ve tried both readers “CAM 
NetCDF (Unstructured)” and “NetCDF files generic and CF conventions” with the 
same results.

I’m running Paraview 5.2.0 64-bit on Mac OS 10.12.3.  But, I have seen 
identical results on an older Mac with a prior OS.  I had also tried an older 
version of Paraview with the same result.

Any ideas why this consistently crashes Paraview, or what to do about it?  
Using netCDF was already a work around, and I willing to try others to view 
these files.  The offset and scale are important because I then need to put in 
other data that is in the correct location and units.

The files are too big for me to send to the mailing list, so I have not posted 
them.

Thanks,

-- Adam

___
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] Object rendering problem on Windows 7 with Paraview 5.2

[Cory Quammen]

Hi Bill,

It sounds like the rendering backend isn't fully supported on your
graphics card/driver combo. What kind of card is it? Are you getting
any error messages?

Thanks,
Cory

On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene  wrote:
> I have been using Paraview 4 on my windows 7 computer for quite a while
> now but wanted to upgrade to Paraview 5.
>
> Installation appeared to work fine but when I display a model I am seeing
> a rendering problem that I don't see in Paraview 4. If Representation=Surface
> and Coloring=Solid Color, the object is black regardless of how the
> color is defined. If Rep=Surface with Edges, the edges do appear over the
> black object. If I select one of the results vectors under Coloring, the
> color bar is displayed and looks correct; but the object remains black.
>
> I know that the graphics card in the computer is somewhat old ( the drivers
> are the latest for the device) but have no idea if that is related to
> the problem
> I'm seeing.
>
> I'm wondering if others have encountered this problem or if there is
> some setting I
> can change to avoid it.
>
> Thanks,
>
> Bill Greene
> ___
> 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

[Paraview] Object rendering problem on Windows 7 with Paraview 5.2

[Bill Greene]

I have been using Paraview 4 on my windows 7 computer for quite a while
now but wanted to upgrade to Paraview 5.

Installation appeared to work fine but when I display a model I am seeing
a rendering problem that I don't see in Paraview 4. If Representation=Surface
and Coloring=Solid Color, the object is black regardless of how the
color is defined. If Rep=Surface with Edges, the edges do appear over the
black object. If I select one of the results vectors under Coloring, the
color bar is displayed and looks correct; but the object remains black.

I know that the graphics card in the computer is somewhat old ( the drivers
are the latest for the device) but have no idea if that is related to
the problem
I'm seeing.

I'm wondering if others have encountered this problem or if there is
some setting I
can change to avoid it.

Thanks,

Bill Greene
___
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] Cataylst pipeline not updating

[Gallagher, Timothy P]

The RequestDataDescription is the same as the default output from the script 
generator, so I didn't include it. The DoCoProcessing gets called every time 
step and the volumeIntegrals data is updated and written correctly every 
delta_t, so I'm confident in that part.


I will add the calls you suggested and re-run. It takes some time for it to 
evolve to the point something will happen -- I don't have it saving data 
frequently enough to run a quick test, I was expecting the pipeline to save it 
for me!


The other thing that occurred to me -- is there something about the Contour 
filter that turns it off/disables it when the pipeline is built and there is no 
surface at that contour level?


Thanks,


Tim



From: Andy Bauer 
Sent: Monday, February 13, 2017 10:56 AM
To: Gallagher, Timothy P
Cc: paraview@paraview.org
Subject: Re: [Paraview] Cataylst pipeline not updating

Hi Tim,

Try adding in the current time to the UpdatePipeline() calls, e.g. 
*.UpdatePipeline(datadescription.GetCurrentTime())

It's tough to tell with RequestDataDescription() missing but I assume that 
DoCoProcessing() is getting called when you want, correct?

Let me know if that doesn't solve the problem.

Best,
Andy

On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P 
> wrote:

Back with another question!


I have a pipeline that has 1 input and 4 outputs. The simplest is a 
IntegrateVariables filter hooked up to the input. Another branch of the 
pipeline goes through several PythonCalculator filters and a 
CellDataToPointData filter and then arrives at the three outputs:


1. The CD2PD filter is connected to a Contour filter with a single level, X. 
This is then connected to an IntegrateVariables filter (used to compute the 
area of the Contour) and a Writer.

2. The CD2PD filter is also connected to another Contour filter with a single 
level Y. This is connected to an IntegrateVariables and Writer just as in 1.

3. The CD2PD filter is sliced two times with each slice in a different render 
view to save images.


I have the coprocessor running every delta_t seconds. The initial 
IntegrateVariables filter is updated with UpdatePipeline and then the values 
are saved to disk. This works every step, no issues.


I then call UpdatePipeline on both of the Contour and both of the 
IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the 
IntegrateVariables exceeds a threshold, and if it does, I save the Contour's to 
disk as a VTK file. This is not working correctly.


If I start the simulation from a point where the Contour's exist in the flow 
already, then everything works great and the Area field changes in time and it 
saves the Contour's.


However, if the simulation starts without the Contours already in the flow, the 
Area fields stay zero forever. It's as if the pipeline isn't updating or 
something. I have attached the DoCoProcessing function used. I don't see 
anything immediately obvious that would prevent it from updating or getting the 
correct values for the Area.


Am I missing something about how the pipeline or contour filters update?


Thanks,


Tim

___
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] Cataylst pipeline not updating

[Andy Bauer]

Oops, datadescription.GetTime() instead of datadescription.GetCurrentTime().

On Mon, Feb 13, 2017 at 10:56 AM, Andy Bauer  wrote:

> Hi Tim,
>
> Try adding in the current time to the UpdatePipeline() calls, e.g.
> *.UpdatePipeline(datadescription.GetCurrentTime())
>
> It's tough to tell with RequestDataDescription() missing but I assume that
> DoCoProcessing() is getting called when you want, correct?
>
> Let me know if that doesn't solve the problem.
>
> Best,
> Andy
>
> On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P <
> tim.gallag...@gatech.edu> wrote:
>
>> Back with another question!
>>
>>
>> I have a pipeline that has 1 input and 4 outputs. The simplest is a
>> IntegrateVariables filter hooked up to the input. Another branch of the
>> pipeline goes through several PythonCalculator filters and a
>> CellDataToPointData filter and then arrives at the three outputs:
>>
>>
>> 1. The CD2PD filter is connected to a Contour filter with a single level,
>> X. This is then connected to an IntegrateVariables filter (used to compute
>> the area of the Contour) and a Writer.
>>
>> 2. The CD2PD filter is also connected to another Contour filter with a
>> single level Y. This is connected to an IntegrateVariables and Writer just
>> as in 1.
>>
>> 3. The CD2PD filter is sliced two times with each slice in a different
>> render view to save images.
>>
>>
>> I have the coprocessor running every delta_t seconds. The initial
>> IntegrateVariables filter is updated with UpdatePipeline and then the
>> values are saved to disk. This works every step, no issues.
>>
>>
>> I then call UpdatePipeline on both of the Contour and both of the
>> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the
>> IntegrateVariables exceeds a threshold, and if it does, I save the
>> Contour's to disk as a VTK file. This is not working correctly.
>>
>>
>> If I start the simulation from a point where the Contour's exist in the
>> flow already, then everything works great and the Area field changes in
>> time and it saves the Contour's.
>>
>>
>> However, if the simulation starts without the Contours already in the
>> flow, the Area fields stay zero forever. It's as if the pipeline isn't
>> updating or something. I have attached the DoCoProcessing function used. I
>> don't see anything immediately obvious that would prevent it from updating
>> or getting the correct values for the Area.
>>
>>
>> Am I missing something about how the pipeline or contour filters update?
>>
>>
>> Thanks,
>>
>>
>> Tim
>>
>> ___
>> 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] Cataylst pipeline not updating

[Andy Bauer]

Hi Tim,

Try adding in the current time to the UpdatePipeline() calls, e.g.
*.UpdatePipeline(datadescription.GetCurrentTime())

It's tough to tell with RequestDataDescription() missing but I assume that
DoCoProcessing() is getting called when you want, correct?

Let me know if that doesn't solve the problem.

Best,
Andy

On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P <
tim.gallag...@gatech.edu> wrote:

> Back with another question!
>
>
> I have a pipeline that has 1 input and 4 outputs. The simplest is a
> IntegrateVariables filter hooked up to the input. Another branch of the
> pipeline goes through several PythonCalculator filters and a
> CellDataToPointData filter and then arrives at the three outputs:
>
>
> 1. The CD2PD filter is connected to a Contour filter with a single level,
> X. This is then connected to an IntegrateVariables filter (used to compute
> the area of the Contour) and a Writer.
>
> 2. The CD2PD filter is also connected to another Contour filter with a
> single level Y. This is connected to an IntegrateVariables and Writer just
> as in 1.
>
> 3. The CD2PD filter is sliced two times with each slice in a different
> render view to save images.
>
>
> I have the coprocessor running every delta_t seconds. The initial
> IntegrateVariables filter is updated with UpdatePipeline and then the
> values are saved to disk. This works every step, no issues.
>
>
> I then call UpdatePipeline on both of the Contour and both of the
> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the
> IntegrateVariables exceeds a threshold, and if it does, I save the
> Contour's to disk as a VTK file. This is not working correctly.
>
>
> If I start the simulation from a point where the Contour's exist in the
> flow already, then everything works great and the Area field changes in
> time and it saves the Contour's.
>
>
> However, if the simulation starts without the Contours already in the
> flow, the Area fields stay zero forever. It's as if the pipeline isn't
> updating or something. I have attached the DoCoProcessing function used. I
> don't see anything immediately obvious that would prevent it from updating
> or getting the correct values for the Area.
>
>
> Am I missing something about how the pipeline or contour filters update?
>
>
> Thanks,
>
>
> Tim
>
> ___
> 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] PVSB 5.2: missing modules and plugins after "make install"

[Ben Boeckel]

On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote:
> Will updating to the current superbuild master address the missing
> plugins issue Michel is seeing? It looks like there have been some
> minor changes on plugin handling in linux since
> 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16.

Yes, it's possible. If you look at the output of the packaging step,
there is probably some set of system libraries being pulled into the
package which should not be there.

--Ben
___
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] XDMF makes paraview crash with JOIN

[Burns, Andrew J CTR USARMY RDECOM ARL (US)]

In Xdmf3's reader, the assignment of variables occurs in 
XdmfArray::populateItem. The evaluation of the function occurs in XdmfFunction 
"|" denotes XdmfFunction::chunk (effectively concatenate). From there it should 
be a bunch of XdmfArray::insert calls.

Xdmf3's source in Paraview is under Paraview/VTK/ThirdParty/xdmf3.

Andrew Burns
Software Engineer | Parsons
Phone: 410-306-0409
ARL DSRC
andrew.j.burns35@mail.mil

-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Frederic 
Perez
Sent: Saturday, February 11, 2017 6:03 PM
To: paraview@paraview.org
Subject: Re: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN

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.  






Hi,

I have been looking closely into this problem in the past few days, and I have 
never been able to make the Xdmf3 reader to JOIN any HDF5 data. Neither with 
the JOIN() syntax nor with the "$0|$1" one. At least to populate an Attribute's 
DataItem. The Xdmf2 reader works until 10 elements are joined.

To go further in this investigation, could someone point me to the source code 
of the Xdmf3 reader, specifically where the "joining"
takes place?

Cheers
Fred


2017-02-08 23:24 GMT+01:00 Frederic Perez :
> I must have done something wrong in my previous attempt with Xdmf3, 
> because it no longer crashes. Note that it works even without your 
> suggestion, as the JOIN() syntax works.
>
> Now the problem is that, when I click "Apply", I get the following error:
> "Failed to locate selected scalars. Will use image scalars by default 
> No scalar values found for texture input!"
>
> Note that the same exact file works with Xdmf instead of Xdmf3.
>
> Fred
>
>
> 2017-02-08 22:54 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US)
> :
>> I think that is because Xdmf3 uses different syntax for concatenation. Try 
>> using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader.
>>
>> -Andrew Burns
>>
>> -Original Message-
>> From: Frederic Perez [Caution-mailto:fredericper...@gmail.com]
>> Sent: Wednesday, February 08, 2017 4:50 PM
>> To: Burns, Andrew J CTR USARMY RDECOM ARL (US) 
>> 
>> Cc: paraview@paraview.org
>> Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash 
>> with JOIN
>>
>> I tried both, but Xdmf3 makes ParaView crash even earlier (directly after 
>> opening the file) while Xdmf2 makes it crash upon "Apply".
>>
>> Fred
>>
>> 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US)
>> :
>>> Are you using the Xdmf2 or Xdmf3 reader?
>>>
>>> Andrew Burns
>>> Software Engineer | Parsons
>>> Phone: 410-306-0409
>>> ARL DSRC
>>> andrew.j.burns35@mail.mil
>>>
>>> -Original Message-
>>> From: ParaView [Caution-mailto:paraview-boun...@paraview.org] On 
>>> Behalf Of Frederic Perez
>>> Sent: Wednesday, February 08, 2017 3:39 PM
>>> To: paraview@paraview.org
>>> Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with 
>>> JOIN
>>>
>>> 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.
>>>
>>>
>>>
>>>
>>> 
>>>
>>> Hi all,
>>>
>>> I have successfully used the JOIN Function for the XDMF reader to 
>>> concatenate the data from several HDF5 files.
>>>
>>> 
>>> 
>>> 
>>> >> TopologyType="2DCoRectMesh" Dimensions="21 10"/>
>>> 
>>> >> Dimensions="2">0.0 0.0
>>> >> Dimensions="2">0.3 0.06
>>> 
>>> 
>>> >> Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10">
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/02/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/07/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/12/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/17/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/22/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/27/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/32/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/37/By
>>> >> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/42/By
>>> >> Precision="8" Dimensions="21"
>>> 

Re: [Paraview] what is the difference between OpenGL rendering backend and OpenGL2 rendering backend when they communicate with the X Window System?

[Ken Martin]

OPenGL 4.4 is plenty and that card should support the new backend. My first
thought would be to try updating the nvidia driver as it is pretty old.



On Mon, Feb 13, 2017 at 5:23 AM, 张驭洲  wrote:

>
>
> Hello,
>
> For a long time I have a problem using ParaView 5.2.0 in the client-server
> mode. However, at the same time, I can use ParaView 4.4.0 in this mode on
> the same machine. Recently I have built several different versions of
> ParaView, including 4.3.1, 4.4.0, 5.1.2, 5.2.0, on the same machine and
> with almost the same compilation options (the only difference among the
> buildings is the rendering backend), and I found that when built with
> OpenGL rendering backend, all the versions, including 5.1.2 and 5.2.0, can
> work normally, in both standalone mode and client-server mode. But when
> 5.1.2 and 5.2.0 are built with OpenGL2 rendering backend, they can't work.
> The machine is a node of a HPC system, so I connect to it via realVNC. If I
> start the paraview execuble by typing ./paraview, I get this output:
>
> Segmentation fault (core dumped)
>
> If I connect to the node via ssh, and type ./paraview , then I get:
>
> paraview: c annot connect to X server
>
> I know this is because I didn't start the X for the paraview, this test is
> just for comparison.
>
> If I connect to the node via ssh, and type ./paraview -display :0 , then I
> get:
>
> X Error: GLXBadContext 144
>   Extension:135 (Uknown extension)
>   Minor opcode: 5 (Unknown request)
>   Resource id:  0x36001bc
> ERROR: In 
> /root/Desktop/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 629
> vtkXOpenGLRenderWindow (0x339c550): GLEW could not be initialized.
>
>
> Segmentation fault (core dumped)
>
> If I connect to the node via ssh, and type ./pvserver and connect to it
> from the paraview GUI on my PC, then I get:
>
> Display is not accessible on the server side.
>
> Remote rendering will be disabled.
>
>
> This means if I dont't use the rendering feature on the node, other
> features of the ParaView can be used normally.
>
>
> If I connect to the node via ssh, and type ./pvserver -display :0, and
> connect to it from the paraview GUI on my PC, then I get lots of errors on
> the client side, like this:
>
> ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-
> linux-shared-release_opengl2_qt4_superbuild/source-
> paraview/VTK/Common/System/vtkSocket.cxx, line 572
> vtkClientSocket (0x1973c70): Socket error in call to send. Broken pipe.
>
> And on the server side, the errors are:
>
> X Error of failed request:  GLXBadContext
>   Major opcode of failed request:  135 (GLX)
>   Minor opcode of failed request:  5 (X_GLXMakeCurrent)
>   Serial number of failed request:  28
>   Current serial number in output stream:  28
>
> From all the tests, I think it's reasonable to guess that the problem lies
> in the X Window system and the OpenGL2 rendering backend. The operation
> system of the node is CentOS 6.3 and the X Window System was installed
> using "yum groupinstall". The GPU on the node is Tesla C2050 and the driver
> version is 331.67. The output from "glxinfo | grep OpenGL" is as follow:
>
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Tesla C2050/PCIe/SSE2
> OpenGL version string: 4.4.0 NVIDIA 331.67
> OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
> OpenGL extensions:
>
> Is there anything wrong with the setting? Why does ParaView with OpenGL
> rendering backend work on it but that with OpenGL2 not work?
>
> Any help or reply is highly appreciated!
>
> -Zhang
>
>
>
>
>
>
>
> ___
> 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
>
>


-- 
Ken Martin PhD
Chairman & CFO
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971

This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.
___
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

[Paraview] Cataylst pipeline not updating

[Gallagher, Timothy P]

Back with another question!


I have a pipeline that has 1 input and 4 outputs. The simplest is a 
IntegrateVariables filter hooked up to the input. Another branch of the 
pipeline goes through several PythonCalculator filters and a 
CellDataToPointData filter and then arrives at the three outputs:


1. The CD2PD filter is connected to a Contour filter with a single level, X. 
This is then connected to an IntegrateVariables filter (used to compute the 
area of the Contour) and a Writer.

2. The CD2PD filter is also connected to another Contour filter with a single 
level Y. This is connected to an IntegrateVariables and Writer just as in 1.

3. The CD2PD filter is sliced two times with each slice in a different render 
view to save images.


I have the coprocessor running every delta_t seconds. The initial 
IntegrateVariables filter is updated with UpdatePipeline and then the values 
are saved to disk. This works every step, no issues.


I then call UpdatePipeline on both of the Contour and both of the 
IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the 
IntegrateVariables exceeds a threshold, and if it does, I save the Contour's to 
disk as a VTK file. This is not working correctly.


If I start the simulation from a point where the Contour's exist in the flow 
already, then everything works great and the Area field changes in time and it 
saves the Contour's.


However, if the simulation starts without the Contours already in the flow, the 
Area fields stay zero forever. It's as if the pipeline isn't updating or 
something. I have attached the DoCoProcessing function used. I don't see 
anything immediately obvious that would prevent it from updating or getting the 
correct values for the Area.


Am I missing something about how the pipeline or contour filters update?


Thanks,


Tim

#  Processing method 
def WriteDataFile(comm, object, filename, curTime, CellData=True):
  object.UpdatePipeline()

  if CellData:
data = object.CellData
  else:
data = object.PointData

  if comm.Get_rank() == 0:
with  open(filename, 'a+') as fid:
  # Rewind the file to see if it is empty or not
  fid.seek(0)
  if len(fid.read(1)) == 0:
# The file is empty, we need to create the header
outputStr = '# Time '
for var in data.keys():
  outputStr += '%s  ' % var
outputStr += '\n'
fid.write(outputStr)

  outputStr = '%15.7e ' % curTime
  for var in data.keys():
value = data[var].GetRange()[0]
outputStr += '%15.7e' % value
  outputStr += '\n'
  fid.write(outputStr)

def DoCoProcessing(datadescription):
"Callback to do co-processing for current timestep"
global coprocessor
global lastTime
global deltaT
global comm
global paths

# Update the coprocessor by providing it the newly generated simulation data.
# If the pipeline hasn't been setup yet, this will setup the pipeline.
coprocessor.UpdateProducers(datadescription)

curTime = datadescription.GetTime()
timestep = datadescription.GetTimeStep()

if curTime >= lastTime + deltaT:
  lastTime = curTime

  coprocessor.Pipeline.volumeIntegrals.UpdatePipeline()

  WriteDataFile(comm, coprocessor.Pipeline.volumeIntegrals,
paths['outdir']+'/post/volumeIntegrals.dat',
curTime,
CellData = True)

  # Check if we need to write images and the first flameArea datasets to disk
  coprocessor.Pipeline.flameArea.UpdatePipeline()
  area = np.zeros(1)

  if comm.Get_rank() == 0:
try:
  area[0] = coprocessor.Pipeline.flameArea.CellData['Area'].GetRange()[0]
except AttributeError:
  area[0] = 0.0
  else:
area[0] = 0.0

  comm.Bcast(area, root=0)
  if area[0] > 1e-9:
# Write image capture (Last arg: rescale lookup table), if appropriate.
coprocessor.WriteImages(datadescription, rescale_lookuptable=False)

# Write out the surface and the area
coprocessor.Pipeline.flameSurfaceWriter.FileName = paths['outdir']+'/post/flameSurface_%07i.vtm' % timestep
coprocessor.Pipeline.flameSurfaceWriter.UpdatePipeline(curTime)

WriteDataFile(comm, coprocessor.Pipeline.flameArea,
  paths['outdir']+'/post/flameArea.dat',
  curTime,
  CellData = False)


  # Check for the second flame surface
  coprocessor.Pipeline.flameArea2.UpdatePipeline()
  area = np.zeros(1)

  if comm.Get_rank() == 0:
try:
  area[0] = coprocessor.Pipeline.flameArea2.CellData['Area'].GetRange()[0]
except AttributeError:
  area[0] = 0.0
  else:
area[0] = 0.0

  comm.Bcast(area, root=0)
  if area[0] > 1e-9:
# Write image capture (Last arg: rescale lookup table), if appropriate.

[Paraview] what is the difference between OpenGL rendering backend and OpenGL2 rendering backend when they communicate with the X Window System?

[张驭洲]

Hello,

For a long time I have a problem using ParaView 5.2.0 in the client-server 
mode. However, at the same time, I can use ParaView 4.4.0 in this mode on the 
same machine. Recently I have built several different versions of ParaView, 
including 4.3.1, 4.4.0, 5.1.2, 5.2.0, on the same machine and with almost the 
same compilation options (the only difference among the buildings is the 
rendering backend), and I found that when built with OpenGL rendering backend, 
all the versions, including 5.1.2 and 5.2.0, can work normally, in both 
standalone mode and client-server mode. But when 5.1.2 and 5.2.0 are built with 
OpenGL2 rendering backend, they can't work. The machine is a node of a HPC 
system, so I connect to it via realVNC. If I start the paraview execuble by 
typing ./paraview, I get this output:

Segmentation fault (core dumped)

If I connect to the node via ssh, and type ./paraview , then I get:

paraview: cannot connect to X server

I know this is because I didn't start the X for the paraview, this test is just 
for comparison.

If I connect to the node via ssh, and type ./paraview -display :0 , then I get:

X Error: GLXBadContext 144
  Extension:135 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x36001bc
ERROR: In 
/root/Desktop/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, 
line 629
vtkXOpenGLRenderWindow (0x339c550): GLEW could not be initialized.


Segmentation fault (core dumped)

If I connect to the node via ssh, and type ./pvserver and connect to it from 
the paraview GUI on my PC, then I get:



Display is not accessible on the server side.

Remote rendering will be disabled.




This means if I dont't use the rendering feature on the node, other features of 
the ParaView can be used normally.





If I connect to the node via ssh, and type ./pvserver -display :0, and connect 
to it from the paraview GUI on my PC, then I get lots of errors on the client 
side, like this:


ERROR: In 
/home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSocket.cxx,
 line 572
vtkClientSocket (0x1973c70): Socket error in call to send. Broken pipe.

And on the server side, the errors are:

X Error of failed request:  GLXBadContext
  Major opcode of failed request:  135 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  28
  Current serial number in output stream:  28

>From all the tests, I think it's reasonable to guess that the problem lies in 
>the X Window system and the OpenGL2 rendering backend. The operation system of 
>the node is CentOS 6.3 and the X Window System was installed using "yum 
>groupinstall". The GPU on the node is Tesla C2050 and the driver version is 
>331.67. The output from "glxinfo | grep OpenGL" is as follow:

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Tesla C2050/PCIe/SSE2
OpenGL version string: 4.4.0 NVIDIA 331.67
OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
OpenGL extensions:

Is there anything wrong with the setting? Why does ParaView with OpenGL 
rendering backend work on it but that with OpenGL2 not work?

Any help or reply is highly appreciated!

-Zhang






___
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] Web3D 2017 ACM conference - Papers Deadline Extended to 27 Feb 2017

[MOUTON Christophe]

Dear All,

Sorry for multiple postings.
The deadline for scientific and technical communications to Web3D 2017 is 
extended to 27th February 2017.
Scientific, medical visualization with VR and/or thanks/on the web are 
tremendous topics!
Submissions of Papers, posters and proposals for workshops and tutorials are 
very welcomed!

Kind regards
Christophe



CALL FOR PAPERS, POSTERS, TUTORIALS AND WORKSHOPS

Papers and Posters Deadline Extended to 27 Feb 2017



Web3D 2017:  22nd International Conference on 3D Web Technology
Sponsored by ACM SIGGRAPH in Co-operation with Web3D Consortium

Date: 5-7 June 2017
Location: Queensland University of Technology, Brisbane, Australia
Website: http://web3d2017.org

The 22nd International Conference on 3D Web Technology (Web3D 2017) continues 
to address an extensive range of research, development, and practice related to 
Web-based 3D Graphics.

2017 will be a historic year for 3D on the Web. We are seeing the explosion of 
WebVR and the potential of WebAR just around the corner. With WebGL now widely 
supported by default in modern browsers, tools such as X3D, X3DOM, Cobweb, 
three.js, glTF, and A-Frame VR are allowing nearly anyone to create Web3D 
content. Commercial game engines such as Unity and Unreal are starting to offer 
ways to export and publish directly to Web3D.

The conference will explore topics including: research on simulation and 
training using Web3D, enabling technology of web-aware, interactive 3D graphics 
from mobile devices up to high-end immersive environments, and the use of 
ubiquitous multimedia across a wide range of applications and environments. For 
example:

·Virtual Reality (VR)

·Mixed Augmented Reality (MAR)

·Cultural and Natural Heritage

·Medical, Telemedicine (eHealth)

·Transportation and Geospatial

·Industry Applications

·Archival Digital Publications

·Human Animation, Motion Capture

·3D Printing and 3D Scanning


•  CAD and Advanced Manufacturing

•  Education and E-learning

•  Collaboration and Annotation

•  Tourism and Accessibility

•  Gaming and Entertainment

•  Creativity and Digital Art

•  Public Sector (Open Government)

•  Open Web Platform Integration

•  Novel Capabilities




For the 2017 conference edition, we welcome works addressing the emerging 
opportunities and research of portable, integrated information spaces over the 
web including, but not limited to:

·Emerging WebVR and WebAR capabilities.

·Scalable, interoperable representations and modeling methods for 
complex geometry, structure, and behaviors.

·3D similarity search and matching, 3D search interfaces, sketch-based 
approaches.

·Visualization and exploration of 3D object repositories.

·Scientific and medical visualization, medical simulation and training.

·3D content creation, analysis tools and pipelines, and 3D 
classification.

·Annotation, metadata, hyperlinking and Semantic Web for 3D objects and 
scenes.

·Generative and example-based shape modeling and optimization.

·3D scanning, 3D reconstruction 3D digitization, and 3D printing.

·Streaming and rendering of large-scale models, animations, and virtual 
worlds.

·Progressive 3D compression and model optimization.

·Collaborative operation and distributed virtual environments.

·Web-wide human-computer interaction and 3D User Interfaces.

·3D City Models, Building Information Modeling & Geo-visualization.

·Mixed and Augmented Reality (MAR) including standardization aspects.

·Web3D and associated APIs, toolkits, and frameworks.

·Novel Web3D interaction paradigms for mobile/handheld applications.

·Web based interaction techniques including gesture, pen and voice.

·Agents, animated humanoids, and complex reactive characters.

·Motion capture for composition and streaming of behaviors and 
expressions.

·Web3D for social networking.

·Script algorithms and programming for lightweight Web3D.

·Network transmission over mobile Internet.

·Server-side 3D engines and cloud-based gaming.

·Architecture support by large Web3D applications for CAD tools and 
solid modelers.

·Data analysis and intelligent algorithms for big Web3D data.

·Interactive Web 3D applications in all applications and sectors.

Papers Submission Instructions:  Deadline extended - 27 February 2017

Authors are invited to submit full papers (up to 9 pages, including figures and 
references) or short papers (up to 4 pages, including figures and references) 
in PDF format via the Submission Site: 
http://web3d2017.web3d.org/submissions/papers

Papers must be formatted using the document templates for conferences sponsored 
by ACM SIGGRAPH (see