Re: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Chuck – I ran a clean build on my OS X 10.12 system and added the flag
“-DUSE_SYSTEM_png=OFF” to my top-level cmake command – and I still get the
same failure deep down inside of the ParaView build – can’t find ……
Cmake must be seeing something in the OS X 10.12 environment that’s
different from everywhere else that’s causing a misconfiguration ….




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  Chuck Atkins 
Date:  Monday, February 27, 2017 at 9:03 AM
To:  Rick Angelini 
Cc:  Rick Angelini , "paraview@paraview.org"

Subject:  Re: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12

Hi Rick, 
> When PVSB configures Paraview, it is setting the cmake flag
> VTK_USE_SYSTEM_PNG=ON and it should be OFF.

When using the superbuild, ParaView should always be using a "system" PNG.
The diggerence is whether that will be provided by the OS or the superbuild.
Either way, it's external to the paraview subproject.  Try explicitly
setting -DUSE_SYSTEM_png=OFF when configuring the superbuild.  I'll look
into why the superbuild doesn't properly handle this in the first palce but
explicitl;y setting the option should make your build work.

- Chuck




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] [Non-DoD Source] PVSB on Mac OSX 10.12

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Chuck – I’ll try to force things with the –DUSE_SYSTEM_PNG=OFF. It is my
intention to allow PVSB to build the png libraries – and it seems to work
everywhere except for OS X 10.12 …
I can see in the 10.12 build that PVSB did indeed build the png libraries,
and there are png entries in superbuild/install/lib and
superbuild/install/include – but the ParaView cmake is not picking up this
information. Why it only fails here (or works everywhere is) is the
$10,000  mystery ….





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  Chuck Atkins 
Date:  Monday, February 27, 2017 at 9:03 AM
To:  Rick Angelini 
Cc:  Rick Angelini , "paraview@paraview.org"

Subject:  Re: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12

Hi Rick, 
> When PVSB configures Paraview, it is setting the cmake flag
> VTK_USE_SYSTEM_PNG=ON and it should be OFF.

When using the superbuild, ParaView should always be using a "system" PNG.
The diggerence is whether that will be provided by the OS or the superbuild.
Either way, it's external to the paraview subproject.  Try explicitly
setting -DUSE_SYSTEM_png=OFF when configuring the superbuild.  I'll look
into why the superbuild doesn't properly handle this in the first palce but
explicitl;y setting the option should make your build work.

- Chuck




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] [Non-DoD Source] PVSB on Mac OSX 10.12

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

A build using the same cmake command completes without the
VTK_USE_SYSTEM_PNG problem on an  OSX 10.11 system. Both systems are
running the Xcode 8.2.1.   I tried both cmake 3.6.3 and 3.7.2 on the OX
10.12 system and both versions result in the same cmake configuration
problem, so it appears to be an issue specific to OS X 10.12 …

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  ParaView  on behalf of Rick Angelini

Date:  Sunday, February 26, 2017 at 2:42 PM
To:  "paraview@paraview.org" 
Subject:  [Non-DoD Source] [Paraview] PVSB on Mac OSX 10.12

I'm building PV 5.3-RC2 on a Mac OSX 10.12 and the build is getting hosed.
(the build fails while building ParaView, can't find a missing 
include file).When PVSB configures Paraview, it is setting the cmake
flag VTK_USE_SYSTEM_PNG=ON and it should be OFF. In the top level cmake,
the value is set to OFF.


292 mac> grep PNG CMakeCache.txt
VTK_USE_SYSTEM_PNG:UNINITIALIZED=OFF

If I re-run cmake in the paraview build directory and turn off
VTK_USE_SYSTEM_PNG, I get a clean build.






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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

“git pull” and “git submodule update” seem to have worked for 5.3.0-RC2.
  



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Wednesday, February 22, 2017 at 9:04 AM
To: Rick Angelini 
Cc: Cory Quammen , ParaView

Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> Cory - so I did a “git pull” and “git submodule update” in my existing
> paraview-superbuild repository directory and that 5.3.0-RC1 information
> was not in the versions.cmake file. I did a clean “git clone” and I
> then received the correct files.I’m not a git expert - so I’m not
> sure why I had to do a clean “git clone”.   I thought I “git pull” should
> have done a proper update.  I must be missing something with my
> repository update commands …..

What is the output of the following commands:

  - git config branch.master.remote
  - git remote show $output_from_previous_command
  - git remote show origin

--Ben


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Cory - so I did a “git pull” and “git submodule update” in my existing
paraview-superbuild repository directory and that 5.3.0-RC1 information
was not in the versions.cmake file. I did a clean “git clone” and I
then received the correct files.I’m not a git expert - so I’m not
sure why I had to do a clean “git clone”.   I thought I “git pull” should
have done a proper update.  I must be missing something with my
repository update commands …..

___
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Cory Quammen 
Date: Tuesday, February 21, 2017 at 1:36 PM
To: Rick Angelini 
Cc: "ben.boec...@kitware.com" , ParaView

Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

Rick,

What is the SHA-1 for last commit in your paraview-superbuild
directory? The latest commit on master is
22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake
at line 63, 5.3.0-RC1 should be listed as a version option.

Thanks,
Cory

On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US)  wrote:
> I did a “git pull” and “git submodule update” in the paraview-superbuild
> directory.   I then changed the source flag in my cmake command:
>
> -Dparaview_SOURCE_SELECTION="5.3.0-RC1”
>
> and I get this error when doing a clean build.
>
> -- Detecting CXX compile features - done
> -- Check size of void*
> -- Check size of void* - done
> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
> (message):
>   The 5.3.0-RC1 source selection for paraview does not exist.
> Call Stack (most recent call first):
>   versions.cmake:62 (superbuild_set_selectable_source)
>   superbuild/CMakeLists.txt:96 (include)
>
>
> I grepp’ed through the paraview-superbuild directory and I don’t see any
> references to 5.3.
>
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Cory Quammen 
> Date: Tuesday, February 21, 2017 at 10:07 AM
> To: Rick Angelini 
> Cc: "ben.boec...@kitware.com" , ParaView
> 
> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
>
> 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 Rick,
>
> From paraview-superbuild master (remember to run 'git submodule
> update' after updating master), you should be able to set
> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build.
>
> These directions are distilled from the README.md file in the
> superbuild directory [1]. Relevant excerpt:
>
> "3. Another option is to use a source tarball of a ParaView release.
> For that, set paraview_SOURCE_SELECTION to the version to build such
> as 5.2.0. The superbuild offers the lastest stable release as well as
> release candidate in preparation for the release. This is the best way
> to build a released version of ParaView."
>
> For each release candidate and release, we add an entry under
> paraview_SOURCE_SELECTION that you can select.
>
> Let us know if you run into problems.
>
> Thanks,
> Cory
>
> [1]
> 
>Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste
>r
> /README.md
>
> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
>> What are the instructions for using PVSB to build the 5.3- RC ?
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: Ben Boeckel 
>> Reply-To: "ben.boec...@kitware.com" 
>> Date: Wednesday, February 15, 2017 at 11:34 AM
>> To: Rick Angelini 
>> Cc: ParaView 
>> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?
>>
>> On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV
>> USARMY RDECOM ARL (US) wrote:
>>> I did a fresh pull of the ParaView superbuild repository, and now I
>>>can’t do
>>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
>>>
>>> First, I had to remove the entries for “qt” and “scipy" in the
>>> CMakeLists.txt:
>>
>> You need to run `git submodule update` to update the common-superbuild
>> bits.
>>
>>> After removing 

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I did a “git pull” and “git submodule update” in the paraview-superbuild
directory.   I then changed the source flag in my cmake command:

-Dparaview_SOURCE_SELECTION="5.3.0-RC1”

and I get this error when doing a clean build.

-- Detecting CXX compile features - done
-- Check size of void*
-- Check size of void* - done
CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
(message):
  The 5.3.0-RC1 source selection for paraview does not exist.
Call Stack (most recent call first):
  versions.cmake:62 (superbuild_set_selectable_source)
  superbuild/CMakeLists.txt:96 (include)


I grepp’ed through the paraview-superbuild directory and I don’t see any
references to 5.3.





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Cory Quammen 
Date: Tuesday, February 21, 2017 at 10:07 AM
To: Rick Angelini 
Cc: "ben.boec...@kitware.com" , ParaView

Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

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 Rick,

>From paraview-superbuild master (remember to run 'git submodule
update' after updating master), you should be able to set
paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build.

These directions are distilled from the README.md file in the
superbuild directory [1]. Relevant excerpt:

"3. Another option is to use a source tarball of a ParaView release.
For that, set paraview_SOURCE_SELECTION to the version to build such
as 5.2.0. The superbuild offers the lastest stable release as well as
release candidate in preparation for the release. This is the best way
to build a released version of ParaView."

For each release candidate and release, we add an entry under
paraview_SOURCE_SELECTION that you can select.

Let us know if you run into problems.

Thanks,
Cory

[1] 
Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master
/README.md

On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> What are the instructions for using PVSB to build the 5.3- RC ?
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Ben Boeckel 
> Reply-To: "ben.boec...@kitware.com" 
> Date: Wednesday, February 15, 2017 at 11:34 AM
> To: Rick Angelini 
> Cc: ParaView 
> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?
>
> On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV
> USARMY RDECOM ARL (US) wrote:
>> I did a fresh pull of the ParaView superbuild repository, and now I
>>can’t do
>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
>>
>> First, I had to remove the entries for “qt” and “scipy" in the
>> CMakeLists.txt:
>
> You need to run `git submodule update` to update the common-superbuild
> bits.
>
>> After removing those entries, the cmake completes and the build starts
>>and
>> passes out in qt4.
>> I’m not sure why it’s complaining about OS X 10.7 or later?)
>
> What version of Xcode are you using?
>
> --Ben
>
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
>Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
>Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

What are the instructions for using PVSB to build the 5.3- RC ?

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Wednesday, February 15, 2017 at 11:34 AM
To: Rick Angelini 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?

On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> I did a fresh pull of the ParaView superbuild repository, and now I
>can’t do
> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
> 
> First, I had to remove the entries for “qt” and “scipy" in the
> CMakeLists.txt:

You need to run `git submodule update` to update the common-superbuild
bits.

> After removing those entries, the cmake completes and the build starts
>and
> passes out in qt4.
> I’m not sure why it’s complaining about OS X 10.7 or later?)

What version of Xcode are you using?

--Ben


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Ben/Fabian

I just did another quick test and it looks like the PVSB 5.2 build on my
OS X 10.9 system that this flag was required to get the build to work:

-DCMAKE_OSX_SDK="macosx10.9”

and this one was apparently optional and not required:

-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M
acOSX.platform/Developer/SDKs/MacOSX10.9.sdk”

Thanks for your help.



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Friday, February 17, 2017 at 7:57 AM
To: Rick Angelini 
Cc: Fabian Wein , ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re:  Superbuild repo change?

On Fri, Feb 17, 2017 at 12:43:17 +0000, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> Cmake was complaining about CMAKE_OSX_SDK not being set …
> I’m not sure if I needed to set both variables, but I recalled seeing
>this
> in a mail thread, so I just set it!   8-)

Ah, then you just set it to what you had. That's fine :) . I just saw
"10.9" and assumed you were setting it to an older version.

--Ben


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Cmake was complaining about CMAKE_OSX_SDK not being set …
I’m not sure if I needed to set both variables, but I recalled seeing this
in a mail thread, so I just set it!   8-)


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Thursday, February 16, 2017 at 4:00 PM
To: Rick Angelini 
Cc: Fabian Wein , ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re:  Superbuild repo change?

On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> Fabian - thank you - that was enough of a hint to get me over the hump.
> Switched my build to qt5 AND based on some information from a previous
> email thread, I added the following to my CMAKE command:
> 
> -DCMAKE_OSX_SDK="macosx10.9" \
> 
>-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/
>M
> acOSX.platform/Developer/SDKs/MacOSX10.9.sdk"

That shouldn't be necessary for Qt5 (though if it works, that's great).

--Ben


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Fabian - thank you - that was enough of a hint to get me over the hump.
Switched my build to qt5 AND based on some information from a previous
email thread, I added the following to my CMAKE command:

-DCMAKE_OSX_SDK="macosx10.9" \
-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M
acOSX.platform/Developer/SDKs/MacOSX10.9.sdk"





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Fabian Wein 
Date: Wednesday, February 15, 2017 at 4:58 PM
To: Rick Angelini 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?

> I did a fresh pull of the ParaView superbuild repository, and now I
>can’t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
> 
> First, I had to remove the entries for “qt” and “scipy“ in the
>CMakeLists.txt:
..

> After removing those entries, the cmake completes and the build starts
>and passes out in qt4.
> I’m not sure why it’s complaining about OS X 10.7 or later?)

For recent OS X qt4 is known to not compile. Use qt5 and it works (macOS
10.12)

Fabian


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] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Duh. “git submodule update” seems to fix things related to the qt and
scipy issue.

My Mac has Xcode version 6.2



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Wednesday, February 15, 2017 at 11:34 AM
To: Rick Angelini 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?

On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> I did a fresh pull of the ParaView superbuild repository, and now I
>can’t do
> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
> 
> First, I had to remove the entries for “qt” and “scipy" in the
> CMakeLists.txt:

You need to run `git submodule update` to update the common-superbuild
bits.

> After removing those entries, the cmake completes and the build starts
>and
> passes out in qt4.
> I’m not sure why it’s complaining about OS X 10.7 or later?)

What version of Xcode are you using?

--Ben


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

[Paraview] Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I did a fresh pull of the ParaView superbuild repository, and now I can’t do
a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).

First, I had to remove the entries for “qt” and “scipy" in the
CMakeLists.txt:

-- Determined source version for paraview: 5.2.0
CMake Error at superbuild/CMakeLists.txt:112 (include):
  include could not find load file:
qt

CMake Error at superbuild/CMakeLists.txt:112 (include):
  include could not find load file:
scipy

After removing those entries, the cmake completes and the build starts and
passes out in qt4. 
I’m not sure why it’s complaining about OS X 10.7 or later?)

[ 19%] Built target boost
[ 24%] Built target visitbridge
[ 27%] Built target libxml2
[ 29%] Performing build step for 'qt4'
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
make[4]: *** [.obj/release-static/qsimplecodec.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: *** [.obj/release-static/qlatincodec.o] Error 1
make[4]: *** [.obj/release-static/qisciicodec.o] Error 1
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
make[4]: *** [.obj/release-static/qtextcodec.o] Error 1
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
make[4]: *** [.obj/release-static/qtsciicodec.o] Error 1
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
make[4]: *** [.obj/release-static/qutfcodec.o] Error 1
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X
10.7 or later)
make[4]: *** [.obj/release-static/qmalloc.o] Error 1
make[4]: *** [.obj/release-static/qglobal.o] Error 1
make[3]: *** [sub-tools-bootstrap-make_default-ordered] Error 2
CMake Error at /Users/angel/PV/Build/superbuild/sb-qt4-build.cmake:43
(message):
  Failed with exit code 2


make[2]: *** [superbuild/qt4/stamp/qt4-build] Error 1
make[1]: *** [superbuild/CMakeFiles/qt4.dir/all] Error 2
make: *** [all] Error 2



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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

[Paraview] Paraview 5.2.0 - Superbuild using Mesa

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I’m seeing this error on multiple machines trying to get a Mesa build to
work and I’m not sure how to get around it.

Making all in state_trackers/glx/xlib
gmake[7]: Entering directory
`/home/angel/PV-Build/5.2.0/Build_5.2.0_mesa/superbuild/mesa/src/src/gallium
/state_trackers/glx/xlib'
  CC   glx_api.lo
  CC   glx_usefont.lo
  CC   xm_st.lo
  CC   glx_getproc.lo
  CC   xm_api.lo
glx_api.c: In function 'glXQueryDrawable':
glx_api.c:2179:43: error: 'X_GLXCreateContextAttribsARB' undeclared (first
use in this function)
  generate_error(dpy, BadValue, 0, X_GLXCreateContextAttribsARB,
true);
   ^
glx_api.c:2179:43: note: each undeclared identifier is reported only once
for each function it appears in
glx_api.c: In function 'glXCreateContextAttribsARB':
glx_api.c:2773:43: error: 'X_GLXCreateContextAttribsARB' undeclared (first
use in this function)
  generate_error(dpy, BadValue, 0, X_GLXCreateContextAttribsARB,
True);
   ^
glx_api.c:2788:27: error: 'GLXBadProfileARB' undeclared (first use in this
function)
   generate_error(dpy, GLXBadProfileARB, 0,
X_GLXCreateContextAttribsARB, False);



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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] [Non-DoD Source] Re: Superbuild WIKI page

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Cory thanks for the update and the pointer.

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Cory Quammen 
Date: Tuesday, November 1, 2016 at 11:42 AM
To: Rick Angelini 
Cc: "paraview@paraview.org" 
Subject: [Non-DoD Source] Re: [Paraview] Superbuild WIKI page

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 Rick,

It looks like you caught us in transition moving the build
instructions from the wiki to the paraview-superbuild repository.

We have just added build instructions from the README.md file located at:

Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master
/README.md

The previous version of the instructions on the wiki are available here:

Caution-http://www.paraview.org/Wiki/index.php?title=ParaView/Superbuild&ol
did=59804

Please let us know if you have any additional questions.

Thanks,
Cory

On Fri, Oct 28, 2016 at 8:35 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> I went to the Paraview SuperBuild page and found this message:
>
> "Updated for ParaView Superbuild have moved to the source repository
> starting with ParaView 5.2. For docs for earlier versions, please check
>out
> the history tab for this page."
>
>
> If I follow the link to the source repository page, there are no
> instructions for how to build using Superbuild, no instructions how to
> obtain the source or to checkout a specific release.  Am I
>missing
> something?
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.


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

[Paraview] Superbuild WIKI page

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I went to the Paraview SuperBuild page and found this message:

"Updated for ParaView Superbuild have moved to the source repository
  starting with
ParaView 5.2. For docs for earlier versions, please check out the history
tab for this page."


If I follow the link to the source repository page, there are no
instructions for how to build using Superbuild, no instructions how to
obtain the source or to checkout a specific release.  Am I missing
something?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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] [Non-DoD Source] Building Paraview with OSMESA

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Chris - Yeah, so I’m also not sure how Catalyst might be firing this up.
Here’s an example OS_Mesa/cmake command used on one of our generic RHEL6
systems.   With this build, we throw the “—use-offscreen-rendering” flag
when we fire up the pvserver.I think that the critical flags are
“osmesa=ON, mesa=OFF, qt=OFF” …..   Can you use your current build in a
traditional client-server configuration to verify that the OS_Mesa is built
correctly?  That might make it easier to narrow down to a build issue or
a Catalyst issue.   Just a thought.




cmake 
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv/${paraview_version}${build_extension}
\
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v${paraview_version}-source.tar.g
z \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_boost=ON \
-DBoost_NO_BOOST_CMAKE:BOOL=ON \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_osmesa=ON \
-DENABLE_mesa=OFF \
-DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
-DENABLE_mpi=ON \
-DUSE_SYSTEM_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=ON \
-DMPI_CXX_LIBRARIES:STRING="-L${MPI_HOME}/lib -lmpi_cxx -ldl" \
-DMPI_C_LIBRARIES:STRING="-L${MPI_HOME}/lib -lmpi -ldl" \
-DMPI_LIBRARY:FILEPATH="-L${MPI_HOME}/lib -lmpi_cxx -ldl" \
../Source

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  Christopher Neal  on behalf of Christopher
Neal 
Date:  Wednesday, September 14, 2016 at 1:44 PM
To:  Rick Angelini , Benson Muite via
ParaView 
Subject:  Re: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

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. 




Thanks Rick!

I’m running OpenSuse 13.2 64bit. I’m not explicitly starting a pvserver,
because I’m running one of the C++ Catalyst examples, which is located at
ParaView/Examples/Catalyst/CxxFullExample. That is mainly what is confusing
me. I’m not sure if I built ParaView with osMesa incorrectly, or if that
Catalyst example is somehow just telling ParaView ‘Hey, don’t use the
offscreen rendering stuff, just go ahead and keep rendering to the screen.”

I’m thinking that I should be able to test the offscreen rendering
capability independently of that Catalyst example by generating a Python
trace of a pipeline that creates an image output, and the running it with a
command like:
pvserver –use-offscreen-rendering TestScript.py
 

From: "Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)"

Date: Wednesday, September 14, 2016 at 1:24 PM
To: Christopher Neal , Benson Muite via ParaView

Subject: Re: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

 

Stupid question – when you start up the pvserver process, are you passing it
the “—use-offscreen-rendering” flag?

 

mpirun –np 8 pvserver —use-offscreen-rendering …….

 

What’s your build platform?  I have lots and lots of build scripts I can
share!   

 



Rick Angelini

USArmy Research Laboratory

CISD/HPC Architectures Team

Phone:  410-278-6266

 

From: ParaView mailto:paraview-boun...@paraview.org > > on behalf of Christopher
Neal mailto:chrisn...@snumerics.com > >
Date: Wednesday, September 14, 2016 at 12:44 PM
To: Benson Muite via ParaView mailto:paraview@paraview.org > >
Subject: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

 

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’ve been trying to compile a version of ParaView that uses osMesa. I’ve
tried to follow the process that is explained on the wiki
(Caution-Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
< Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >  <
Caution-Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D <
Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >  >  ),
but I haven’t been able to get ParaView to render offscreen. I don’t have
build errors, but when I run something that saves a screenshot I still see a
window pop up on my screen. Would anyone be willing to share their
configuration script/command that they use for compiling ParaView with
osMESA?  

Also – If I have a python script that creates a screenshot of some geometry,
do I need to edit it in any way before running it with a version of ParaView
that uses osMesa? Or is all of that handled behind the scenes?

Re: [Paraview] [Non-DoD Source] Building Paraview with OSMESA

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Stupid question – when you start up the pvserver process, are you passing it
the “—use-offscreen-rendering” flag?

mpirun –np 8 pvserver —use-offscreen-rendering …….

What’s your build platform?  I have lots and lots of build scripts I can
share!   


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  ParaView  on behalf of Christopher
Neal 
Date:  Wednesday, September 14, 2016 at 12:44 PM
To:  Benson Muite via ParaView 
Subject:  [Non-DoD Source] [Paraview] Building Paraview with OSMESA

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’ve been trying to compile a version of ParaView that uses osMesa. I’ve
tried to follow the process that is explained on the wiki
(Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D <
Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >  ), but
I haven’t been able to get ParaView to render offscreen. I don’t have build
errors, but when I run something that saves a screenshot I still see a
window pop up on my screen. Would anyone be willing to share their
configuration script/command that they use for compiling ParaView with
osMESA?  

Also – If I have a python script that creates a screenshot of some geometry,
do I need to edit it in any way before running it with a version of ParaView
that uses osMesa? Or is all of that handled behind the scenes?


Thank you,
Chris N




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] [Non-DoD Source] Re: 5.1.2/OpenGL2 issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Yes - this is an OpenGL2 build.

Is this the information on TurboVNC that you’re looking for?

server glx vendor string: VirtualGL
server glx version string: 1.4


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Wednesday, August 24, 2016 at 8:57 AM
To: Rick Angelini 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] 5.1.2/OpenGL2 issue

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.  






Rick,

I am assuming with is with VTK_RENDERING_BACKEND set to OpenGL2.

Do you know what VirtualGL version is being used?

On Tue, Aug 23, 2016 at 2:56 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> We are trying to build/run ParaView 5.1.2 on a particular HPC system with
> graphics nodes via TurboVNC. ParaView 5.0.1 build/runs fine in this
> configuration.ParaView 5.1.2 compiles fine (using identical build
> configuration used to build 5.0.1) - however the GUI fails at execution.
> I’m not sure how to debug it any further. It *appears* that 5.1.2 is
> maybe doing some additional environment querying that might be causing
>this
> failure?
>
>
> When I try to run 5.1.2, I get this error:
>
> g01 > paraview
> [VGL] WARNING: The OpenGL rendering context obtained on X display
> [VGL]:0.0 is indirect, which may cause performance to suffer.
> [VGL]If :0.0 is a local X display, then the framebuffer device
> [VGL]permissions may be set incorrectly.
> Segmentation fault
>
>
> The particular message about indirect rendering – if I run glxinfo,
>direct
> rendering is set to YES.
>
> g01 > glxinfo
> name of display: :5.0
> display: :5  screen: 0
> direct rendering: Yes
> server glx vendor string: VirtualGL
> server glx version string: 1.4
> [deleted stuff]
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Tesla K40m/PCIe/SSE2
> OpenGL core profile version string: 4.3.0 NVIDIA 340.93
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>


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

[Paraview] 5.1.2/OpenGL2 issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

We are trying to build/run ParaView 5.1.2 on a particular HPC system with
graphics nodes via TurboVNC. ParaView 5.0.1 build/runs fine in this
configuration.ParaView 5.1.2 compiles fine (using identical build
configuration used to build 5.0.1) - however the GUI fails at execution.
I’m not sure how to debug it any further. It *appears* that 5.1.2 is
maybe doing some additional environment querying that might be causing this
failure?


When I try to run 5.1.2, I get this error:

g01 > paraview
[VGL] WARNING: The OpenGL rendering context obtained on X display
[VGL]:0.0 is indirect, which may cause performance to suffer.
[VGL]If :0.0 is a local X display, then the framebuffer device
[VGL]permissions may be set incorrectly.
Segmentation fault


The particular message about indirect rendering – if I run glxinfo,   direct
rendering is set to YES.

g01 > glxinfo
name of display: :5.0
display: :5  screen: 0
direct rendering: Yes
server glx vendor string: VirtualGL
server glx version string: 1.4
[deleted stuff]
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Tesla K40m/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 340.93




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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] [Non-DoD Source] PV 5.1.2 Mesa Build

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I’m not sure if this is the right way to fix this problem,  but there was
not a URL_MD5 value for mesa-12.0.0 in the versions.cmake file.   So I
manually added a URL_MD5 entry to versions.cmake and it now works correctly
(if the tar ball is there it does not attempt to download it)

if (CROSS_BUILD_STAGE STREQUAL "CROSS")
add_revision(mesa
URL "http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz";
URL_MD5 e80fabad2e3eb7990adae773d6aeacba)
else()
add_revision(mesa
URL "ftp://ftp.freedesktop.org/pub/mesa/12.0.0/mesa-12.0.0-rc2.tar.gz";)
URL_MD5 cca449752b58c35f03af5a009d099283)
  I added this!
endif()



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  ParaView  on behalf of Rick Angelini

Date:  Wednesday, August 10, 2016 at 2:13 PM
To:  ParaView 
Subject:  [Non-DoD Source] [Paraview] PV 5.1.2 Mesa Build

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. 




I’m using the Superbuild to attempt to build ParaView on a system which
cannot FTP to the outside world. I have downloaded all of the tar balls
into a Downloads directory, including mesa-12.0.0-rc2.tar.gz – however, the
SuperBuild insists on zero’ing out the mesa-12.0.0-rc2.tar.gz file and
trying to FTP it down.   I have GIT=OFF in my cmake command.



[ 24%] Completed 'llvm'
[ 24%] Built target llvm
Scanning dependencies of target mesa
[ 25%] Creating directories for 'mesa'
[ 25%] Performing download step (download, verify and extract) for 'mesa'
-- downloading...
 
src='Caution-ftp://ftp.freedesktop.org/pub/mesa/12.0.0/mesa-12.0.0-rc2.tar.g
z'
 dst='/u/home/angel/PV/5.1.2/Downloads/mesa-12.0.0-rc2.tar.gz'
 timeout='none'
CMake Error at mesa-stamp/download-mesa.cmake:21 (message):
  error: downloading
  'Caution-ftp://ftp.freedesktop.org/pub/mesa/12.0.0/mesa-12.0.0-rc2.tar.gz'
failed

status_code: 7
status_string: "Couldn't connect to server"
log:   Trying 131.252.210.176...

  Connected to Caution-ftp.freedesktop.org (131.252.210.176) port 21 (#0)

  220 Welcome to the freedesktop.org FTP server.

  USER anonymous

  331 Please specify the password.

  PASS f...@example.com

  230 Login successful.

  PWD

  257 "/"

  Entry path is '/'

  CWD pub

  ftp_perform ends with SECONDARY: 0

  250 Directory successfully changed.

  CWD mesa

  250 Directory successfully changed.

  CWD 12.0.0

  250 Directory successfully changed.

  EPSV

  Connect data stream passively

  229 Entering Extended Passive Mode (|||37332|).

Trying 131.252.210.176...

  Connecting to 131.252.210.176 (131.252.210.176) port 37332

  connect to 131.252.210.176 port 21 failed: Connection timed out

  Failed to connect to Caution-ftp.freedesktop.org port 21: Connection timed
out

  Failed EPSV attempt.  Disabling EPSV

  PASV

  227 Entering Passive Mode (131,252,210,176,180,31).

Trying 131.252.210.176...

  Connecting to 131.252.210.176 (131.252.210.176) port 46111

  connect to 131.252.210.176 port 21 failed: Connection timed out

  Failed to connect to Caution-ftp.freedesktop.org port 21: Connection timed
out

  Closing connection 0





make[2]: *** [mesa/src/mesa-stamp/mesa-download] Error 1
make[1]: *** [CMakeFiles/mesa.dir/all] Error 2
make: *** [all] Error 2
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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

[Paraview] PV 5.1.2 Mesa Build

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I’m using the Superbuild to attempt to build ParaView on a system which
cannot FTP to the outside world. I have downloaded all of the tar balls
into a Downloads directory, including mesa-12.0.0-rc2.tar.gz – however, the
SuperBuild insists on zero’ing out the mesa-12.0.0-rc2.tar.gz file and
trying to FTP it down.   I have GIT=OFF in my cmake command.



[ 24%] Completed 'llvm'
[ 24%] Built target llvm
Scanning dependencies of target mesa
[ 25%] Creating directories for 'mesa'
[ 25%] Performing download step (download, verify and extract) for 'mesa'
-- downloading...
 src='ftp://ftp.freedesktop.org/pub/mesa/12.0.0/mesa-12.0.0-rc2.tar.gz'
 dst='/u/home/angel/PV/5.1.2/Downloads/mesa-12.0.0-rc2.tar.gz'
 timeout='none'
CMake Error at mesa-stamp/download-mesa.cmake:21 (message):
  error: downloading
  'ftp://ftp.freedesktop.org/pub/mesa/12.0.0/mesa-12.0.0-rc2.tar.gz' failed

status_code: 7
status_string: "Couldn't connect to server"
log:   Trying 131.252.210.176...

  Connected to ftp.freedesktop.org (131.252.210.176) port 21 (#0)

  220 Welcome to the freedesktop.org FTP server.

  USER anonymous

  331 Please specify the password.

  PASS f...@example.com

  230 Login successful.

  PWD

  257 "/"

  Entry path is '/'

  CWD pub

  ftp_perform ends with SECONDARY: 0

  250 Directory successfully changed.

  CWD mesa

  250 Directory successfully changed.

  CWD 12.0.0

  250 Directory successfully changed.

  EPSV

  Connect data stream passively

  229 Entering Extended Passive Mode (|||37332|).

Trying 131.252.210.176...

  Connecting to 131.252.210.176 (131.252.210.176) port 37332

  connect to 131.252.210.176 port 21 failed: Connection timed out

  Failed to connect to ftp.freedesktop.org port 21: Connection timed out

  Failed EPSV attempt.  Disabling EPSV

  PASV

  227 Entering Passive Mode (131,252,210,176,180,31).

Trying 131.252.210.176...

  Connecting to 131.252.210.176 (131.252.210.176) port 46111

  connect to 131.252.210.176 port 21 failed: Connection timed out

  Failed to connect to ftp.freedesktop.org port 21: Connection timed out

  Closing connection 0





make[2]: *** [mesa/src/mesa-stamp/mesa-download] Error 1
make[1]: *** [CMakeFiles/mesa.dir/all] Error 2
make: *** [all] Error 2
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

2016 at 4:09 PM
To: Rick Angelini , Utkarsh Ayachit

Cc: ParaView Developers , ParaView

Subject: Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for
download

I made slight change to my build script - turned GIT=OFF to GIT=ON, and I
seem to have a clean build

Changed this:
cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/5.1.2 \
-Ddownload_location=`pwd`/../Downloads \
DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v5.1.2.tar.gz \
…


to this:

cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
-Ddownload_location=`pwd`/../Downloads \
DParaView_FROM_GIT=ON \
-DParaView_URL=git://www.paraview.org/files/v5.1/ParaView-v5.1.2.tar.gz \
….



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Thursday, July 28, 2016 at 2:23 PM
To: Utkarsh Ayachit 
Cc: ParaView Developers , ParaView

Subject: Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for
download

Utkarsh - yes I was building 5.1.2 in a totally clean directory - as I
said, I also downloaded clean SuperBuild sources prior to doing the build.
   

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-----
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 2:09 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

You are doing a clean build, right? In an empty directory and not just
"make clean".

Utkarsh

On Thu, Jul 28, 2016 at 2:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> OK - but it is creating lib/paraview-5.0  which I believe is a mistake of
> some sort …..
>
> I can’t believe that it’s anything in my CMAKE command:
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> -DParaView_FROM_GIT=OFF \
> -DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt4=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_NONFREE_COMPONENTS=OFF \
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
> -DUSE_SYSTEM_mpi=OFF ../ParaViewSuperbuild
>
> make -j 8 install
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Thursday, July 28, 2016 at 1:57 PM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available
>for
> download
>
> mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1


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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I made slight change to my build script - turned GIT=OFF to GIT=ON, and I
seem to have a clean build

Changed this:
cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/5.1.2 \
-Ddownload_location=`pwd`/../Downloads \
DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v5.1.2.tar.gz \
…


to this:

cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
-Ddownload_location=`pwd`/../Downloads \
DParaView_FROM_GIT=ON \
-DParaView_URL=git://www.paraview.org/files/v5.1/ParaView-v5.1.2.tar.gz \
….



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Thursday, July 28, 2016 at 2:23 PM
To: Utkarsh Ayachit 
Cc: ParaView Developers , ParaView

Subject: Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for
download

Utkarsh - yes I was building 5.1.2 in a totally clean directory - as I
said, I also downloaded clean SuperBuild sources prior to doing the build.
   

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 2:09 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

You are doing a clean build, right? In an empty directory and not just
"make clean".

Utkarsh

On Thu, Jul 28, 2016 at 2:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> OK - but it is creating lib/paraview-5.0  which I believe is a mistake of
> some sort …..
>
> I can’t believe that it’s anything in my CMAKE command:
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> -DParaView_FROM_GIT=OFF \
> -DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt4=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_NONFREE_COMPONENTS=OFF \
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
> -DUSE_SYSTEM_mpi=OFF ../ParaViewSuperbuild
>
> make -j 8 install
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Thursday, July 28, 2016 at 1:57 PM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available
>for
> download
>
> mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1


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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Meh!   I created the lib/paraview-5.1 directory and the build gets further
along then dies again.   If I look at the output —  the initial make is
stuffing files into lib/paraview-5.0 - then the make install seems to
correctly push to the release directory in lib/paraview-5.1

-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/s
pread/banana.py
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/s
pread/interfaces.pyc
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/s
pread/pb.pyo
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/s
pread/jelly.py
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/s
pread/__init__.pyo
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/site-packages/twisted/_
_init__.pyo
-- Installing: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/libvtkUtilitiesPythonIn
itializer-pv5.0.so.1
-- Up-to-date: 
/home/angel/PV/5.1.2/Build/install/lib/paraview-5.0/libvtkUtilitiesPythonIn
itializer-pv5.0.so

then

[100%] Completed 'paraview'
[100%] Built target paraview
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /home/angel/pv-test/5.1.2/lib/paraview-5.1
-- Installing: /home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7
-- Installing: 
/home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7/token.pyc
-- Installing: 
/home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7/tempfile.pyo
-- Installing: 
/home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7/mailcap.pyo
-- Installing: 
/home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7/pydoc.pyc
-- Installing: 
/home/angel/pv-test/5.1.2/lib/paraview-5.1/lib/python2.7/sndhdr.pyc
 
and finally another failure:

-- Installing: 
/home/angel/pv-test/5.1.2/share/icons/hicolor/96x96/apps/paraview.png
-- Installing: /home/angel/pv-test/5.1.2/share/icons/hicolor/22x22
-- Installing: /home/angel/pv-test/5.1.2/share/icons/hicolor/22x22/apps
-- Installing: 
/home/angel/pv-test/5.1.2/share/icons/hicolor/22x22/apps/paraview.png
CMake Error at cmake_install.cmake:114 (file):
  file INSTALL cannot find
  "/home/angel/PV/5.1.2/Build/install/share/paraview-5.1/www".


BTW - I’m not on the ParaView Developers mail list, so my replies back to
that list keep getting rejected!  8-)



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 1:57 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

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.  






Not sure, but I cannot reproduce the issue. Can you do this:

> mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1

ensure that the directory is created and then try again. I wonder if
that directory is not being created for some reason.

On Thu, Jul 28, 2016 at 1:18 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> Yes, the changes to both of those files are in place.
>
> Here’s what I ran prior to the build:
>
> git clone Caution-http://paraview.org/ParaViewSuperbuild.git
> cd ParaViewSuperbuild
> git checkout v5.1.2
>
>
>
> I then ran cmake using cmake-3.5.2
>
> I can see that the build is using the 5.1.2 tar ball
>
> [ 97%] Performing download step (download, verify and extract) for
> 'paraview'
> -- verifying file...
>  file='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz'
> -- verifying file... done
> -- extracting...
>  src='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz'
>  dst='/home/angel/PV/5.1.2/Build/paraview/src/paraview'
> -- extracting... [tar xfz]
> -- extracting... [analysis]
> -- extracting... [rename]
> -- extracting... [clean up]
> -- extracting... done
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Thursday, July 28, 2016 at 1:09 PM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available
>for
> download
>
> Can you confirm that your ParaView superbuild has this commit
> 
>(Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/commit/bf
>831e2e2b4
> c3a6a764c63f65759884eb287b3f6)?
>
> On 

Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - yes I was building 5.1.2 in a totally clean directory - as I
said, I also downloaded clean SuperBuild sources prior to doing the build.
   

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 2:09 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

You are doing a clean build, right? In an empty directory and not just
"make clean".

Utkarsh

On Thu, Jul 28, 2016 at 2:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> OK - but it is creating lib/paraview-5.0  which I believe is a mistake of
> some sort …..
>
> I can’t believe that it’s anything in my CMAKE command:
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> -DParaView_FROM_GIT=OFF \
> -DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt4=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_NONFREE_COMPONENTS=OFF \
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
> -DUSE_SYSTEM_mpi=OFF ../ParaViewSuperbuild
>
> make -j 8 install
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Thursday, July 28, 2016 at 1:57 PM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available
>for
> download
>
> mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1


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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

OK - but it is creating lib/paraview-5.0  which I believe is a mistake of
some sort …..

I can’t believe that it’s anything in my CMAKE command:

cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_boost=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt4=ON \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=OFF \
-DUSE_NONFREE_COMPONENTS=OFF \
-DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
-DUSE_SYSTEM_mpi=OFF ../ParaViewSuperbuild

make -j 8 install




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 1:57 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1


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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Yes, the changes to both of those files are in place.

Here’s what I ran prior to the build:

git clone http://paraview.org/ParaViewSuperbuild.git
cd ParaViewSuperbuild
git checkout v5.1.2



I then ran cmake using cmake-3.5.2

I can see that the build is using the 5.1.2 tar ball

[ 97%] Performing download step (download, verify and extract) for
'paraview'
-- verifying file...
 file='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz'
-- verifying file... done
-- extracting...
 src='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz'
 dst='/home/angel/PV/5.1.2/Build/paraview/src/paraview'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, July 28, 2016 at 1:09 PM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

Can you confirm that your ParaView superbuild has this commit
(https://gitlab.kitware.com/paraview/paraview-superbuild/commit/bf831e2e2b4
c3a6a764c63f65759884eb287b3f6)?

On Thu, Jul 28, 2016 at 12:51 PM, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US)  wrote:
> There still seems to be something misconfigured deep down in the
> Superbuild configuration files.We saw this in the 5.1.0 build as
>well.
> The install directory has install/lib/paraview-5.0 rather than
> install/lib/paraview-5.1.   I downloaded clean Superbuild source
>directory
> before this build …..
>
>
> -- Installing: /home/angel/PV/5.1.2/Build/install/bin/paraview
> -- Installing:
> /home/angel/PV/5.1.2/Build/install/share/applications/paraview.desktop
> -- Installing:
> 
>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/22x22/apps/paraview
>.
> png
> -- Installing:
> 
>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/32x32/apps/paraview
>.
> png
> -- Installing:
> 
>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/96x96/apps/paraview
>.
> png
> -- Installing:
> /home/angel/PV/5.1.2/Build/install/share/appdata/paraview.appdata.xml
> [100%] Completed 'paraview'
> [100%] Built target paraview
> Install the project...
> -- Install configuration: "Release"
> CMake Error at cmake_install.cmake:36 (file):
>   file INSTALL cannot find
>   "/home/angel/PV/5.1.2/Build/install/lib/paraview-5.1".
>
>
> make: *** [install] Error 1
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView  on behalf of Utkarsh
> Ayachit 
> Date: Thursday, July 28, 2016 at 10:55 AM
> To: ParaView , ParaView Developers
> 
> Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
> download
>
> 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.
>
>
>
>
> 
>
> Folks,
>
> ParaView 5.1.2 is now available for download [1]. Please refer to the
> release notes on the Kitware blog [2]. As always, we look forward to
> your feedback [3].
>
> Also stay tuned to the Kitware Blog [4] for upcoming features and
> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> more!
>
> - ParaView Team
>
> [1] Caution-http://www.paraview.org/download/
> [2] Caution-https://blog.kitware.com/paraview-5-1-2-release-notes/
> [3] Caution-http://paraview.uservoice.com
> [4] Caution-https://blog.kitware.com/tag/ParaView/
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview


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] [Non-DoD Source] ANN: ParaView 5.1.2 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

There still seems to be something misconfigured deep down in the
Superbuild configuration files.We saw this in the 5.1.0 build as well.
The install directory has install/lib/paraview-5.0 rather than
install/lib/paraview-5.1.   I downloaded clean Superbuild source directory
before this build …..


-- Installing: /home/angel/PV/5.1.2/Build/install/bin/paraview
-- Installing: 
/home/angel/PV/5.1.2/Build/install/share/applications/paraview.desktop
-- Installing: 
/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/22x22/apps/paraview.
png
-- Installing: 
/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/32x32/apps/paraview.
png
-- Installing: 
/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/96x96/apps/paraview.
png
-- Installing: 
/home/angel/PV/5.1.2/Build/install/share/appdata/paraview.appdata.xml
[100%] Completed 'paraview'
[100%] Built target paraview
Install the project...
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:36 (file):
  file INSTALL cannot find
  "/home/angel/PV/5.1.2/Build/install/lib/paraview-5.1".


make: *** [install] Error 1



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Utkarsh
Ayachit 
Date: Thursday, July 28, 2016 at 10:55 AM
To: ParaView , ParaView Developers

Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for
download

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.  






Folks,

ParaView 5.1.2 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] Caution-http://www.paraview.org/download/
[2] Caution-https://blog.kitware.com/paraview-5-1-2-release-notes/
[3] Caution-http://paraview.uservoice.com
[4] Caution-https://blog.kitware.com/tag/ParaView/
___
Powered by Caution-www.kitware.com

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

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

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

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


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] [Non-DoD Source] making the leap to v5.1 on the cray

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Burlen - we’ve successfully built 4.x and 5.x on a number of different
Crays.   We use the Superbuild and allow ParaView to pull whatever
versions of the dependent libraries it needs and build everything on the
fly.It looks like the recent builds used mesa-11.2.2 …..



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Burlen Loring

Date: Tuesday, July 5, 2016 at 2:51 PM
To: ParaView 
Subject: [Non-DoD Source] [Paraview] making the leap to v5.1 on the cray

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,

first of all, is 5.1 production ready? or is 4.4 still the way to go in
a production environment? this would be the only install available for
users so it's important that it function reliably/correctly.

re: 5.1, I'm wondering what the recommended mesa config for use with pv
5.1 on cray is?  Which version of mesa have been tested/recommended? is
open swr an option yet? or is llvmpipe still a better bet?

Thanks
Burlen
___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] [Non-DoD Source] ANN: ParaView 5.1.0 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - I’ve having trouble getting a build using 5.1 ….   I’m running a
“make install” and it seems to be looking for install/lib/paraview-5.1 but
what actually exists in the build directory is install/lib/paraview-5.0  …
not sure if my superbuild is hosed or if there’s something wrong deep in
one of the configuration files.



-- Installing: 
/home/angel/PV/5.1.0/Build/install/share/applications/paraview.desktop
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/22x22/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/32x32/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/96x96/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/appdata/paraview.appdata.xml
[100%] Completed 'paraview'
[100%] Built target paraview
Install the project...
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:36 (file):
  file INSTALL cannot find
  "/home/angel/PV/5.1.0/Build/install/lib/paraview-5.1".



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Utkarsh
Ayachit 
Date: Tuesday, June 21, 2016 at 12:04 PM
To: ParaView , ParaView Developers

Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for
download

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.  






Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] Caution-http://www.paraview.org/download/
[2] Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] Caution-http://paraview.uservoice.com
[4] Caution-https://blog.kitware.com/tag/ParaView/
___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] [Non-DoD Source] ANN: ParaView 5.1.0 available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Should there be a tag for v5.1.0 for the Superbuild?I was looking at
the Superbuild wiki and I should be able to checkout the Superbuild using
a new tag - unless those instructions are now obsolete?



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Utkarsh
Ayachit 
Date: Tuesday, June 21, 2016 at 12:04 PM
To: ParaView , ParaView Developers

Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for
download

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.  






Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] Caution-http://www.paraview.org/download/
[2] Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] Caution-http://paraview.uservoice.com
[4] Caution-https://blog.kitware.com/tag/ParaView/
___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] [Non-DoD Source] Re: [EXTERNAL] Re: Rendering issue with cross-sections in 3D

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

With regard to OpenGL1 vs OpenGL2 backends – I think that there’s an issue with 
5.0.1 where the frontend/backend need to be compiled using the same OpenGL ….. 
so if you want to jump back to OpenGL1 on the backend, you’ll need a similarly 
configured frontend ……



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: ParaView 
mailto:paraview-boun...@paraview.org>> on behalf 
of David Lonie mailto:david.lo...@kitware.com>>
Date: Friday, June 17, 2016 at 7:22 AM
To: Cory Quammen mailto:cory.quam...@kitware.com>>
Cc: Craig Christensen 
mailto:craig.christen...@ucalgary.ca>>, 
"paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: [Non-DoD Source] Re: [Paraview] [EXTERNAL] Re: Rendering issue with 
cross-sections in 3D

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.




Has anyone tested OpenGL1 vs. OpenGL2 backends on master?

It may be an issue with the recent changes to depth peeling. OpenGL1 will still 
use the old implementation, OpenGL2 (not on mesa) will use the new version.

On Fri, Jun 17, 2016 at 5:34 AM, Cory Quammen 
mailto:cory.quam...@kitware.com> < 
Caution-mailto:cory.quam...@kitware.com > > wrote:
Folks,

The bad Caution-news: I can reproduce this in ParaView 5.0.1 on a Mac given
the data files Craig shared.

The good Caution-news: I cannot reproduce it in my development version of
ParaView 5.1 RC1. Mind downloading that version of ParaView and giving
it a shot? I would guess there might have been a rendering bug in the
OpenGL2 backend in VTK that has since been fixed.

Thanks,
Cory



On Fri, Jun 17, 2016 at 3:15 AM, Scott, W Alan 
mailto:wasc...@sandia.gov> < 
Caution-mailto:wasc...@sandia.gov > > wrote:
> Steve,
>
> I worry it sounds a bit like a bug.
>
> Can you provide us with a toy dataset (or non-toy, if necessary) that 
> replicates the issue?  Also, really, really good directions (+Y, roll mouse 
> wheel in 4 times)?
>
> Alan
>
> -Original Message-
> From: ParaView [Caution-mailto:paraview-boun...@paraview.org < 
> Caution-mailto:paraview-boun...@paraview.org > ] On Behalf Of Steve Lamont
> Sent: Thursday, June 16, 2016 7:12 PM
> To: paraview@paraview.org < 
> Caution-mailto:paraview@paraview.org >
> Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections in 3D
>
>> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
>> running into a rendering issue. When I zoom in to my data sets, data
>> in the background randomly jumps in front of cross-sections in the
>> foreground.
>
> I'm running into a similar issue.
>
> I have three cross sections, along the three major axes, and they do not seem 
> to occlude one another as one would expect.
>
> I've turned on depth peeling and have experimented with setting the maximum 
> number of peels to no avail.
>
> I know this is a classic OpenGL depth sorting issue since I've run into 
> myself back when I was coding such things.
>
> I've updated my nVidia drivers to what passes for the Latest and Greatest for 
> Ubuntu Linux and I have a fairly recent graphics card (Quadro K2000D).  I'll 
> be happy to supply any other system information I can if it'll help.
>
> Is there something else I need to switch on in order to get ParaView to 
> operate in the "expected" manner?
>
> Thanx.
>
> spl
>
> ___
> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
> Visit other Kitware open-source projects at 
> Caution-http://www.kitware.com/opensource/opensource.html < 
> Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> Caution-http://paraview.org/Wiki/ParaView < 
> Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < 
> Caution-http://markmail.org/search/?q=ParaView >
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview < 
> Caution-http://public.kitware.com/mailman/listinfo/paraview >
> ___
> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
> Visit other Kitware open-source projects at 
> Caution-http://www.kitware.com/opensource/opensource.html < 
> Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> Caution-http://paraview.org/Wiki/ParaView < 
> Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < 
> Caution-http://markmail.org

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

We did indeed build 5.0.1 (with your updates) and the connect_id is the
same on both ends …..



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Tuesday, June 7, 2016 at 11:30 AM
To: Rick Angelini 
Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
, Simon Su ,
ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production
>5.0.1
> client??

That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.

> **
> Connection failed during handshake. This can happen for the following
> reasons:
>  1. Connection dropped during the handshake.
>  2. vtkSocketCommunicator::GetVersion() returns different values on the
> two connecting processes (Current value: 100).
>  3. ParaView handshake strings are different on the two connecting
> processes (Current value: paraview.5.0.connect_id.9407).
> **

This message is printed on both client and server. See the value for
item 3. Do they match? Looks like you're using connection ids. Are
they being specified appropriately on both ends?

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I used the same job launching scripts that I use for all of the previous
versions, including the broken attempts at 5.0.1 OSMesa builds  which were
able to connect and launch (and eventually fail).

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Tuesday, June 7, 2016 at 11:30 AM
To: Rick Angelini 
Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
, Simon Su ,
ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production
>5.0.1
> client??

That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.

> **
> Connection failed during handshake. This can happen for the following
> reasons:
>  1. Connection dropped during the handshake.
>  2. vtkSocketCommunicator::GetVersion() returns different values on the
> two connecting processes (Current value: 100).
>  3. ParaView handshake strings are different on the two connecting
> processes (Current value: paraview.5.0.connect_id.9407).
> **

This message is printed on both client and server. See the value for
item 3. Do they match? Looks like you're using connection ids. Are
they being specified appropriately on both ends?

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - I was able to get a clean build with this OSMesa patch - but it
looks like the OSMesa pvserver is not compatible with the production 5.0.1
client??

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Par
allel/Core/vtkSocketCommunicator.cxx, line 558
vtkSocketCommunicator (0x12324f0): Endian handshake failed.

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 33
0
vtkTCPNetworkAccessManager (0x6612b0): Failed to connect to
excalibur03-int:22886

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 34
0
vtkTCPNetworkAccessManager (0x6612b0):
**
Connection failed during handshake. This can happen for the following
reasons:
 1. Connection dropped during the handshake.
 2. vtkSocketCommunicator::GetVersion() returns different values on the
two connecting processes (Current value: 100).
 3. ParaView handshake strings are different on the two connecting
processes (Current value: paraview.5.0.connect_id.9407).
**






Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Monday, June 6, 2016 at 1:53 PM
To: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"

Cc: Rick Angelini , Simon Su
, 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.  






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

Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_reque
sts/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
>>
>> Caution-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 [Caution-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

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Would it be sufficient to change the cmake flags OSMESA_INCLUDE_DIR and
OSMESA_LIBRARY in CMakeCache file to point to the external build of Mesa
11.x.x?



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, June 2, 2016 at 4:19 PM
To: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"

Cc: Rick Angelini , Simon Su
, 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

___
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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - thanks - in the mean time, we're going to try to build Mesa 11.1 (?) 
outside of ParaView and link it in and see how far we can get!   8-)But it 
would certainly be cleaner to use the Superbuild when you get that updated with 
the proper Mesa build!



-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Thursday, June 02, 2016 1:18 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 

Cc: Chuck Atkins ; ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Roger that. I will have updates for you early next week (plan to work on it as 
soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US)  wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to 
> address Mesa w/X support .
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
> 
> Cc: Chuck Atkins ; ParaView 
> 
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have 
> superbuild build the right versions of Mesa. Do you only  care about OSMesa 
> or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
> ARL (US)  wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.   The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild? We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC 
>> systems - so stepping outside of the super build paradigm isn’t necessarily 
>> obvious
>> to me!8-)
>>
>>
>>
>>
>>
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: Utkarsh Ayachit 
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini 
>> Cc: Chuck Atkins , ParaView 
>> 
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> 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.
>>
>>
>>
>>
>> 
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2 
>> (released in 2009), then alas there's more work to get ParaView 
>> working which could include building a newer version of Mesa. Not 
>> sure if you have seen this blog [1], but that talks about how I got 
>> Mesa to build with appropriate OpenGL renderer enabled. Things have 
>> gotten a little better since then and the Docker script encapsulates 
>> that. The moral of the story is get latest Mesa version and build it 
>> with LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vt
>> k
>> -7-0/
>>


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] [Non-DoD Source] Re: 5.0.1/Exodus Reader

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Our *immediate* concern is OSMesa - but we'll probably eventually want to 
address Mesa w/X support .

-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Thursday, June 02, 2016 9:48 AM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 

Cc: Chuck Atkins ; ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Ah okay. Give me a few days to sort it out. The end goal is indeed to have 
superbuild build the right versions of Mesa. Do you only  care about OSMesa or 
also Mesa with X support?

Utkarsh




On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US)  wrote:
> Our current issues seem to be related to our osmesa build for the HPC_side
> servers.   The Superbuild is building 7.11.2 - you are suggesting that
> we need to *manually* build a different version of Mesa and somehow link
> in that new version of Mesa in to the Superbuild? We rely exclusively
> on the Superbuild for compiling ParaView across 20 different HPC 
> systems - so stepping outside of the super build paradigm isn’t necessarily 
> obvious
> to me!8-)
>
>
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Thursday, June 2, 2016 at 8:37 AM
> To: Rick Angelini 
> Cc: Chuck Atkins , ParaView 
> 
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> 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.
>
>
>
>
> 
>
>> So there is much more to be done than adding
>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>> to the cmake flags?
>
> As far as ParaView is concerned, no there's not much more to it.
> However if your OpenGL implementation doesn't support OpenGL 3.2 
> (released in 2009), then alas there's more work to get ParaView 
> working which could include building a newer version of Mesa. Not sure 
> if you have seen this blog [1], but that talks about how I got Mesa to 
> build with appropriate OpenGL renderer enabled. Things have gotten a 
> little better since then and the Docker script encapsulates that. The 
> moral of the story is get latest Mesa version and build it with 
> LLVM/Gallum support.
>
> Utkarsh
>
> [1]
> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk
> -7-0/
>


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] [Non-DoD Source] Re: 5.0.1/Exodus Reader

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Our current issues seem to be related to our osmesa build for the HPC_side
servers.   The Superbuild is building 7.11.2 - you are suggesting that
we need to *manually* build a different version of Mesa and somehow link
in that new version of Mesa in to the Superbuild? We rely exclusively
on the Superbuild for compiling ParaView across 20 different HPC systems -
so stepping outside of the super build paradigm isn’t necessarily obvious
to me!8-)






Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Thursday, June 2, 2016 at 8:37 AM
To: Rick Angelini 
Cc: Chuck Atkins , ParaView

Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

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.  






> So there is much more to be done than adding
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
> to the cmake flags?

As far as ParaView is concerned, no there's not much more to it.
However if your OpenGL implementation doesn't support OpenGL 3.2
(released in 2009), then alas there's more work to get ParaView
working which could include building a newer version of Mesa. Not sure
if you have seen this blog [1], but that talks about how I got Mesa to
build with appropriate OpenGL renderer enabled. Things have gotten a
little better since then and the Docker script encapsulates that. The
moral of the story is get latest Mesa version and build it with
LLVM/Gallum support.

Utkarsh

[1] 
Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/

___
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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

So there is much more to be done than adding

-DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
-DVTK_RENDERING_BACKEND:STRING="OpenGL2"



to the cmake flags?

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Wednesday, June 1, 2016 at 4:28 PM
To: Rick Angelini , Chuck Atkins

Cc: ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

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.  






Rick,

The superbuild isn't updated yet to build newer Mesa. Mesa now needs
LLVM etc and hence it's a little tricky. I believe Chuck is working on
getting that working. In the mean time, here's a docker file we use to
build mesa verions:

Caution-https://gitlab.kitware.com/paraview/mesa-builds/tree/master

That will show what options to use to build mesa appropriately.

Utkarsh


On Wed, Jun 1, 2016 at 4:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> Is there an issue in the SuperBuild?   I just did a quick look through
>the
> Superbuild source, and it looks like the file version.cmake is wanting to
> use MesaLib-7.11.2 …..
>
>
> 59  $ git pull
> Already up-to-date.
>
>
> 60 $ grep -i mesa versions.cmake
>   add_revision(mesa
> URL 
>"Caution-http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz";
>   add_revision(mesa
> URL 
>"Caution-http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz";
> # We stick with 7.11.2 for Mesa version for now. Newer mesa doesn't seem
>to
> add_revision(osmesa
> URL 
>"Caution-http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz";
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView  on behalf of Rick Angelini
> 
> Date: Wednesday, June 1, 2016 at 3:59 PM
> To: Utkarsh Ayachit 
> Cc: ParaView 
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> 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.
>
>
>
>
> 
>
> DOH!  The render threshold values were set differently on the Mac and
> Linux systems.   As soon as I forced the Mac to use distributed
>rendering,
> it failed with the same error messages.So do we have a build issue on
> the HPC-side?  We have rebuilt with OpenGL2 enabled, but it seems
>like
> it’s not picking up the correct Mesa libsPresumably we’re using
> the Superbuild and it should be building using the Mesa that’s part of
>the
> Superbuild
>
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa supports OpenGL 3.2.
>
>
> ERROR: In
> 
>/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_o
>s
> 
>x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManage
>r
> /Core/vtkSMSessionClient.cxx, line 821
> vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.
>
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-----
> From: Utkarsh Ayachit 
> Date: Wednesday, June 1, 2016 at 3:48 PM
> To: Rick Angelini 
> Cc: ParaView 
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Rick,
>
> Are you by any change using local rendering on your Mac and remote
> rendering on your linux client box?
>
> Utkarsh
>
> On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
>> So, we are continuing to have issues with 5.0.1 and OpenGL2.  I have
>> recompiled the server-side to use OpenGL2, and it works fine if when I
>>run
>> ParaView 5.0.1 from my Mac. However, if I run ParaView 5

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Is there an issue in the SuperBuild?   I just did a quick look through the
Superbuild source, and it looks like the file version.cmake is wanting to
use MesaLib-7.11.2 …..


59  $ git pull
Already up-to-date.


60 $ grep -i mesa versions.cmake
  add_revision(mesa
URL "http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz";
  add_revision(mesa
URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz";
# We stick with 7.11.2 for Mesa version for now. Newer mesa doesn't seem to
add_revision(osmesa
URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz";




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Wednesday, June 1, 2016 at 3:59 PM
To: Utkarsh Ayachit 
Cc: ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

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.  






DOH!  The render threshold values were set differently on the Mac and
Linux systems.   As soon as I forced the Mac to use distributed rendering,
it failed with the same error messages.So do we have a build issue on
the HPC-side?  We have rebuilt with OpenGL2 enabled, but it seems like
it’s not picking up the correct Mesa libsPresumably we’re using
the Superbuild and it should be building using the Mesa that’s part of the
Superbuild

ERROR: In 
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.


ERROR: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_os
x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager
/Core/vtkSMSessionClient.cxx, line 821
vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Wednesday, June 1, 2016 at 3:48 PM
To: Rick Angelini 
Cc: ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Rick,

Are you by any change using local rendering on your Mac and remote
rendering on your linux client box?

Utkarsh

On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> So, we are continuing to have issues with 5.0.1 and OpenGL2.  I have
> recompiled the server-side to use OpenGL2, and it works fine if when I
>run
> ParaView 5.0.1 from my Mac. However, if I run ParaView 5.0.1 from my
> Linux box,  I’m still getting failures.   Looks like 5.0.1 on my Linux
>box
> (RHEL6) is also built with OpenGL2, but there are apparently additional
> issues? Here’s some of the output from the error log on the
>SERVER
> side.What’s generating these GL_Version info messages?  I’m using
> the same exact server-side job launching whether I’m running the client
>on
> my Mac or Linux machine - so it would seem that maybe something’s wrong
>on
> the Linux client?
>
>
> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
> -sp=4459 --connect-id=40460
> Connecting to client (reverse connection requested)...
> Connection Caution-url: csrc://excalibur09-int:4459
> Client connected.
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa sup

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

DOH!  The render threshold values were set differently on the Mac and
Linux systems.   As soon as I forced the Mac to use distributed rendering,
it failed with the same error messages.So do we have a build issue on
the HPC-side?  We have rebuilt with OpenGL2 enabled, but it seems like
it’s not picking up the correct Mesa libsPresumably we’re using
the Superbuild and it should be building using the Mesa that’s part of the
Superbuild

ERROR: In 
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.


ERROR: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_os
x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager
/Core/vtkSMSessionClient.cxx, line 821
vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Wednesday, June 1, 2016 at 3:48 PM
To: Rick Angelini 
Cc: ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Rick,

Are you by any change using local rendering on your Mac and remote
rendering on your linux client box?

Utkarsh

On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> So, we are continuing to have issues with 5.0.1 and OpenGL2.  I have
> recompiled the server-side to use OpenGL2, and it works fine if when I
>run
> ParaView 5.0.1 from my Mac. However, if I run ParaView 5.0.1 from my
> Linux box,  I’m still getting failures.   Looks like 5.0.1 on my Linux
>box
> (RHEL6) is also built with OpenGL2, but there are apparently additional
> issues? Here’s some of the output from the error log on the
>SERVER
> side.What’s generating these GL_Version info messages?  I’m using
> the same exact server-side job launching whether I’m running the client
>on
> my Mac or Linux machine - so it would seem that maybe something’s wrong
>on
> the Linux client?
>
>
> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
> -sp=4459 --connect-id=40460
> Connecting to client (reverse connection requested)...
> Connection URL: csrc://excalibur09-int:4459
> Client connected.
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa supports OpenGL 3.2.
>
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView  on behalf of Rick Angelini
> 
> Date: Tuesday, May 31, 2016 at 8:09 AM
> To: Utkarsh Ayachit 
> Cc: ParaView 
> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>
> 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.
>
>
>
>
> 
>
> Utkarsh - thanks for info.Recompiling the server-side with OpenGL2
> resolved the problem!
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Friday, May 27, 2016 at 2:37 PM
> To: Rick Angelini 
> Cc: ParaView 
> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

So, we are continuing to have issues with 5.0.1 and OpenGL2.  I have
recompiled the server-side to use OpenGL2, and it works fine if when I run
ParaView 5.0.1 from my Mac. However, if I run ParaView 5.0.1 from my
Linux box,  I’m still getting failures.   Looks like 5.0.1 on my Linux box
(RHEL6) is also built with OpenGL2, but there are apparently additional
issues? Here’s some of the output from the error log on the SERVER
side.What’s generating these GL_Version info messages?  I’m using
the same exact server-side job launching whether I’m running the client on
my Mac or Linux machine - so it would seem that maybe something’s wrong on
the Linux client?


/opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
/usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
-sp=4459 --connect-id=40460
Connecting to client (reverse connection requested)...
Connection URL: csrc://excalibur09-int:4459
Client connected.
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
ERROR: In
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Tuesday, May 31, 2016 at 8:09 AM
To: Utkarsh Ayachit 
Cc: ParaView 
Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader

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.  






Utkarsh - thanks for info.Recompiling the server-side with OpenGL2
resolved the problem!



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini 
Cc: ParaView 
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh

___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] [Non-DoD Source] Re: ParaView 5.0.1 on an older Mac

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

This system is still running 10.9 and is scheduled for a 10.11 upgrade in the 
near-term – presumably the warning message will go away with 10.11 …….

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: Michael Jackson 
mailto:mike.jack...@bluequartz.net>>
Date: Tuesday, May 31, 2016 at 4:31 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: [Non-DoD Source] Re: [Paraview] ParaView 5.0.1 on an older Mac

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.




Richard,
   You will get this warning/error message on any OS X machine using ATI/AMD 
graphics hardware running OS X 10.10 or earlier. OS X 10.11 corrected an OpenGL 
driver issue that this error is reporting. It is down in the VTK stack. I do 
not know if we should be worried or not about the warning/error.

--
Mike Jackson  [mike.jack...@bluequartz.net<mailto:mike.jack...@bluequartz.net> 
< Caution-mailto:mike.jack...@bluequartz.net > ]
Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) < 
Caution-mailto:richard.c.angelini@mail.mil >
May 31, 2016 at 4:07 PM
I have the following message from one of my local ParaView users:

Following is the message I am getting with the Paraview 5 client on the Mac. It 
appears to work in spite of this warning.

Warning: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx,
 line 2856
vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in 
Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant 
memory and performance impacts. Your hardware has been identified as vendor ATI 
Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and version 
4.1 ATI-1.24.39

About this Mac has the following information about my system:
Graphics  ATI Radeon HD 5770 1024 MB


The user does not see this error running ParaView 4.x.x … so – presumably this 
warning message is related to OpenGL2 running on an older graphics card???
Is this something we should be worried about in the short-term?  I’m not sure 
how much longer this older Mac will be in service – but will we run in to 
issues with OpenGL2 which will preclude it from working on these older systems?





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >

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

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

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

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

___
Powered by www.kitware.com

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

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

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

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

[Paraview] ParaView 5.0.1 on an older Mac

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I have the following message from one of my local ParaView users:

Following is the message I am getting with the Paraview 5 client on the Mac. It 
appears to work in spite of this warning.

Warning: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx,
 line 2856
vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in 
Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant 
memory and performance impacts. Your hardware has been identified as vendor ATI 
Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and version 
4.1 ATI-1.24.39

About this Mac has the following information about my system:
Graphics  ATI Radeon HD 5770 1024 MB


The user does not see this error running ParaView 4.x.x … so – presumably this 
warning message is related to OpenGL2 running on an older graphics card???
Is this something we should be worried about in the short-term?  I’m not sure 
how much longer this older Mac will be in service – but will we run in to 
issues with OpenGL2 which will preclude it from working on these older systems?





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - thanks for info.Recompiling the server-side with OpenGL2
resolved the problem!



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini 
Cc: ParaView 
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh

___
Powered by www.kitware.com

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

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

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

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

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Utkarsh - thanks for the info.  I believe that you’re right that the build
didn’t go as intended.

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini 
Cc: ParaView 
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh

___
Powered by www.kitware.com

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

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

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

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

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

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
pre-built Mac/Linux binaries were both built with OpenGL?Is there some
way to check to see which OpenGL the client was built with?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, May 27, 2016 at 2:24 PM
To: Rick Angelini 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

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.  






Rick,

I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL and other to OpenGL2. You need them to match.

Utkarsh

On Fri, May 27, 2016 at 2:08 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> We’re seeing an issue with the Exodus reader in version 5.0.1.  We
>can
> read any particular Exodus dataset when running ParaView 5.0.1 locally –
> read the data on the same machine where the client is running.   However,
> when we try to load any of the Exodus datasets in client-server mode,
> ParaView 5.0.1 immediately crashes.Crash happens when the client is
>run
> on either a Mac or Linux workstation.
>
>
> Accepting connection(s): my_Mac:52994
> ERROR: In
> 
>/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_o
>sx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImple
>mentation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper.
>Aborting
> for debugging purposes.
>
>
> Accepting connection(s): my_Linux:35227
> ERROR: In
> 
>/usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCo
>re/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting
>for
> debugging purposes.
>
> This same dataset works in client-server mode using ParaView 4.3.1.
> We seem to be able to load up other data types using ParaView 5.0.1 – so
> far, it *appears* that only Exodus files are failing.
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-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] 5.0.1/Exodus Reader

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

We’re seeing an issue with the Exodus reader in version 5.0.1.  We can read 
any particular Exodus dataset when running ParaView 5.0.1 locally – read the 
data on the same machine where the client is running.   However, when we try to 
load any of the Exodus datasets in client-server mode,   ParaView 5.0.1 
immediately crashes.Crash happens when the client is run on either a Mac or 
Linux workstation.


Accepting connection(s): my_Mac:52994
ERROR: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
 line 310
vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper. Aborting for 
debugging purposes.


Accepting connection(s): my_Linux:35227
ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
 line 310
vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting for 
debugging purposes.

This same dataset works in client-server mode using ParaView 4.3.1.
We seem to be able to load up other data types using ParaView 5.0.1 – so far, 
it *appears* that only Exodus files are failing.



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

 --use-offscreen-rendering 
benchmarknew/manyspheres.py -s 16384 -r 725 -v 1920,1080 -f 10 -o 
"manyspheres_16384s_725r_256m"

This will result in the following files:

  *   manyspheres_16384s_725r_256m.args.txt
 *   The arguments the benchmark was run with
  *   manyspheres_16384s_725r_256m.mem.txt
 *   Memory info for each pvserver at each frame
  *   manyspheres_16384s_725r_256m.logs.raw.bin
 *   Raw log data that be loaded with logbase.load()
  *   manyspheres_16384s_725r_256m.logs.parsed.bin
 *   Parsed log data that be loaded with Python pickel
  *   manyspheres_16384s_725r_256m.scene.f0.tiff
 *   Rendered image of the scene from Frame 0
  *   manyspheres_16384s_725r_256m.stats.r0f0.txt
 *   Log information for Rank 0, Frame 0
  *   manyspheres_16384s_725r_256m.stats.frame.txt
 *   Statistics per-frame calculated across ranks
  *   manyspheres_16384s_725r_256m.stats.summary.txt
 *   Statistics calculated across all frames

Note that you can just as easily run it on a single node without MPI and you'll 
get valid numbers.  Please let me know if you have any questions or need help 
trying to run it.


Thanks

- Chuck

- Chuck

On Fri, Mar 25, 2016 at 10:02 AM, David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com >  < 
Caution-Caution-mailto:dave.dema...@kitware.com < 
Caution-mailto:dave.dema...@kitware.com >  > > wrote:
It is still in 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  < 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  >  
which hasn't been merged yet because we have a few changes left to make in it. 
It would be great if you could try it and comment in the gitlab review on 
anything you find.

I expect it will be merged next week. Note that although this won't show up in 
a release until ParaView 7.1, it is possible to copy to use with older 
ParaViews.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Fri, Mar 25, 2016 at 8:02 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > > wrote:
Pointer?   I’m searching through the repository and I don’t see it.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com >  < 
Caution-Caution-mailto:dave.dema...@kitware.com < 
Caution-mailto:dave.dema...@kitware.com >  > >
Date: Thursday, March 24, 2016 at 4:17 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org >  < 
Caution-Caution-mailto:paraview@paraview.org < 
Caution-mailto:paraview@paraview.org >  > >
Subject: Re: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




Not sure what you mean by new_benchmark.py. You should run 
benchmark/manyspheres.py.

It takes resolution and numspheres arguments. numspheres is the total number of 
objects in the scene and each processors makes a diffent set of them. 
Resolution is the phi&theta resolution of each that controls the number of 
polygons each sphere has.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Thu, Mar 24, 2016 at 4:03 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  >  < 
Caution-Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  >  > > wrot

Re: [Paraview] [Non-DoD Source] Re: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

M, David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > > wrote:
It is still in 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 < 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  
which hasn't been merged yet because we have a few changes left to make in it. 
It would be great if you could try it and comment in the gitlab review on 
anything you find.

I expect it will be merged next week. Note that although this won't show up in 
a release until ParaView 7.1, it is possible to copy to use with older 
ParaViews.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Fri, Mar 25, 2016 at 8:02 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
Pointer?   I’m searching through the repository and I don’t see it.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > >
Date: Thursday, March 24, 2016 at 4:17 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org > >
Subject: Re: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




Not sure what you mean by new_benchmark.py. You should run 
benchmark/manyspheres.py.

It takes resolution and numspheres arguments. numspheres is the total number of 
objects in the scene and each processors makes a diffent set of them. 
Resolution is the phi&theta resolution of each that controls the number of 
polygons each sphere has.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Thu, Mar 24, 2016 at 4:03 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > > wrote:
Dave – I’m running the new_benchmark.py script from the command line

pvpython new_benchmark.py


Is there a way to jack up the number of polygons that the script generates?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >  < tel:410-278-6266 < 
tel:410-278-6266 >  >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com >  < 
Caution-Caution-mailto:dave.dema...@kitware.com < 
Caution-mailto:dave.dema...@kitware.com >  > >
Date: Monday, March 21, 2016 at 1:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org >  < 
Caution-Caution-mailto:paraview@paraview.org < 
Caution-mailto:paraview@paraview.org >  > >
Subject: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




At the VTK single node level, enable Module_vtkUtilitiesBenchmarks module in 
cmake, compile and run bin/TimingTests

At the ParaView multiple node level, Chuck Atkins is nearly done with revamping 
the old benchmark.py and adding to it a simple canonical test script that uses 
the programmable filter to make arbitrarily large meshes to test parallel 
rendering with. That can be found at: 
Caution-Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692
 < Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  < 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  >  
< 
Caution-Caution-Caution-https://gitlab.kitware.com/paraview/p

Re: [Paraview] [Non-DoD Source] Re: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

e let me know if you have any questions or need help 
trying to run it.


Thanks

- Chuck

- Chuck

On Fri, Mar 25, 2016 at 10:02 AM, David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > > wrote:
It is still in 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 < 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  
which hasn't been merged yet because we have a few changes left to make in it. 
It would be great if you could try it and comment in the gitlab review on 
anything you find.

I expect it will be merged next week. Note that although this won't show up in 
a release until ParaView 7.1, it is possible to copy to use with older 
ParaViews.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Fri, Mar 25, 2016 at 8:02 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
Pointer?   I’m searching through the repository and I don’t see it.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > >
Date: Thursday, March 24, 2016 at 4:17 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org > >
Subject: Re: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




Not sure what you mean by new_benchmark.py. You should run 
benchmark/manyspheres.py.

It takes resolution and numspheres arguments. numspheres is the total number of 
objects in the scene and each processors makes a diffent set of them. 
Resolution is the phi&theta resolution of each that controls the number of 
polygons each sphere has.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Thu, Mar 24, 2016 at 4:03 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > > wrote:
Dave – I’m running the new_benchmark.py script from the command line

pvpython new_benchmark.py


Is there a way to jack up the number of polygons that the script generates?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >  < tel:410-278-6266 < 
tel:410-278-6266 >  >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com >  < 
Caution-Caution-mailto:dave.dema...@kitware.com < 
Caution-mailto:dave.dema...@kitware.com >  > >
Date: Monday, March 21, 2016 at 1:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org >  < 
Caution-Caution-mailto:paraview@paraview.org < 
Caution-mailto:paraview@paraview.org >  > >
Subject: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




At the VTK single node level, enable Module_vtkUtilitiesBenchmarks module in 
cmake, compile and run bin/TimingTests

At the ParaView multiple node level, Chuck Atkins is nearly done with revamping 
the old benchmark.py and adding to it a simple canonical test script that uses 
the programmable filter to make arbitrarily large meshes to test parallel 
rendering with. That can be found at: 
Caution-Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692
 < Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  < 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.k

Re: [Paraview] [Non-DoD Source] Re: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Pointer?   I’m searching through the repository and I don’t see it.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: David E DeMarle 
mailto:dave.dema...@kitware.com>>
Date: Thursday, March 24, 2016 at 4:17 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: Re: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




Not sure what you mean by new_benchmark.py. You should run 
benchmark/manyspheres.py.

It takes resolution and numspheres arguments. numspheres is the total number of 
objects in the scene and each processors makes a diffent set of them. 
Resolution is the phi&theta resolution of each that controls the number of 
polygons each sphere has.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Mar 24, 2016 at 4:03 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
Dave – I’m running the new_benchmark.py script from the command line

pvpython new_benchmark.py


Is there a way to jack up the number of polygons that the script generates?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > >
Date: Monday, March 21, 2016 at 1:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org > >
Subject: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




At the VTK single node level, enable Module_vtkUtilitiesBenchmarks module in 
cmake, compile and run bin/TimingTests

At the ParaView multiple node level, Chuck Atkins is nearly done with revamping 
the old benchmark.py and adding to it a simple canonical test script that uses 
the programmable filter to make arbitrarily large meshes to test parallel 
rendering with. That can be found at: 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  < 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  >




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Mon, Mar 21, 2016 at 12:28 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > > wrote:
I need to do some quick performance tests to compare the results between two 
graphics cards using “real world” applications.   Do you guys have a benchmark 
handy to measure interactive graphics performance???

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >  < tel:410-278-6266 < 
tel:410-278-6266 >  >

___
Powered by Caution-Caution-www.kitware.com < 
Caution-http://Caution-Caution-www.kitware.com >  < 
Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com >  >

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

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

Search the list archives at: 
Caution-Cau

Re: [Paraview] [Non-DoD Source] Re: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I apparently found the wrong benchmark!Off to search again.   Thanks


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: David E DeMarle 
mailto:dave.dema...@kitware.com>>
Date: Thursday, March 24, 2016 at 4:17 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: Re: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




Not sure what you mean by new_benchmark.py. You should run 
benchmark/manyspheres.py.

It takes resolution and numspheres arguments. numspheres is the total number of 
objects in the scene and each processors makes a diffent set of them. 
Resolution is the phi&theta resolution of each that controls the number of 
polygons each sphere has.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Mar 24, 2016 at 4:03 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
Dave – I’m running the new_benchmark.py script from the command line

pvpython new_benchmark.py


Is there a way to jack up the number of polygons that the script generates?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

From: David E DeMarle 
mailto:dave.dema...@kitware.com> < 
Caution-mailto:dave.dema...@kitware.com > >
Date: Monday, March 21, 2016 at 1:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > >
Cc: ParaView mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org > >
Subject: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




At the VTK single node level, enable Module_vtkUtilitiesBenchmarks module in 
cmake, compile and run bin/TimingTests

At the ParaView multiple node level, Chuck Atkins is nearly done with revamping 
the old benchmark.py and adding to it a simple canonical test script that uses 
the programmable filter to make arbitrarily large meshes to test parallel 
rendering with. That can be found at: 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  < 
Caution-Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 
< Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >  >




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909 < tel:518-881-4909 >

On Mon, Mar 21, 2016 at 12:28 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL 
(US)mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil >  < 
Caution-Caution-mailto:richard.c.angelini@mail.mil < 
Caution-mailto:richard.c.angelini@mail.mil >  > > wrote:
I need to do some quick performance tests to compare the results between two 
graphics cards using “real world” applications.   Do you guys have a benchmark 
handy to measure interactive graphics performance???

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >  < tel:410-278-6266 < 
tel:410-278-6266 >  >

___
Powered by Caution-Caution-www.kitware.com < 
Caution-http://Caution-Caution-www.kitware.com >  < 
Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com >  >

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

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

Search the list archives at: 
Caution-Cau

Re: [Paraview] [Non-DoD Source] Re: Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Dave – I’m running the new_benchmark.py script from the command line

pvpython new_benchmark.py


Is there a way to jack up the number of polygons that the script generates?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: David E DeMarle 
mailto:dave.dema...@kitware.com>>
Date: Monday, March 21, 2016 at 1:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: [Non-DoD Source] Re: [Paraview] Measure graphics performance?

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.




At the VTK single node level, enable Module_vtkUtilitiesBenchmarks module in 
cmake, compile and run bin/TimingTests

At the ParaView multiple node level, Chuck Atkins is nearly done with revamping 
the old benchmark.py and adding to it a simple canonical test script that uses 
the programmable filter to make arbitrarily large meshes to test parallel 
rendering with. That can be found at: 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 < 
Caution-https://gitlab.kitware.com/paraview/paraview/merge_requests/692 >




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Mar 21, 2016 at 12:28 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
I need to do some quick performance tests to compare the results between two 
graphics cards using “real world” applications.   Do you guys have a benchmark 
handy to measure interactive graphics performance???

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266 < tel:410-278-6266 >

___
Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-http://public.kitware.com/mailman/listinfo/paraview < 
Caution-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] Measure graphics performance?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I need to do some quick performance tests to compare the results between two 
graphics cards using “real world” applications.   Do you guys have a benchmark 
handy to measure interactive graphics performance???

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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] Building on Cray systems

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

OK – I didn’t realize that this was for Catalyst development work.   We do no 
currently install the development files – but I would think that the best 
chance for success for inclusion of Catalyst would be a customized build using 
the same exact compilers/mpi as the linking computational code.   I’ll send Tim 
build examples directly ….


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: Andy Bauer mailto:andy.ba...@kitware.com>>
Date: Thursday, February 4, 2016 at 9:15 AM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Cc: "tim.gallag...@gatech.edu<mailto:tim.gallag...@gatech.edu>" 
mailto:tim.gallag...@gatech.edu>>, paraview 
mailto:paraview@paraview.org>>
Subject: Re: [Paraview] [Non-DoD Source] Building on Cray systems

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 Rick,

Did you build ParaView with PARAVIEW_INSTALL_DEVELOPMENT_FILES enabled? Tim 
will need that for using Catalyst if he's going to be using your builds but not 
if he's going to do his own.

Tim, some questions on what you need:

  *   Do you have a specific compiler and version you want/need to use? Same 
thing for MPI implementation.
  *   Do you have a specific version of ParaView that you want to use?

I would recommend using the superbuild tools, to build statically with Python 
and Mesa. The other libraries can be built with the superbuild (definitely use 
system MPI though) for convenience even though for Catalyst  you probably won't 
need many of them. The FREEZE_PYTHON option is to statically linking the other 
Python modules into the executable. This is definitely useful for when running 
with a high number of MPI ranks since when loading a module (e.g. 
paraview.simple) in parallel it can really kill the file system if thousands of 
processes are simultaneously trying to load a bunch of Python modules. Note 
though that this isn't needed for a Catalyst Python script since that is done 
specially where process 0 reads the file and broadcasts it to all of the other 
processes.

Cheers,

Andy

On Thu, Feb 4, 2016 at 8:54 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM 
ARL (US) 
mailto:richard.c.angelini@mail.mil> < 
Caution-mailto:richard.c.angelini@mail.mil > > wrote:
Tim - I've already built ParaView on all of these systems - there are
modules available to load various version of Paraview.If you need to do
your own builds to support specific functionality - I can provide you the
build scripts we use on those systems.




-Original Message-
From: ParaView [Caution-mailto:paraview-boun...@paraview.org < 
Caution-mailto:paraview-boun...@paraview.org > ] On Behalf Of Tim
Gallagher
Sent: Thursday, February 04, 2016 8:25 AM
To: paraview mailto:paraview@paraview.org> < 
Caution-mailto:paraview@paraview.org > >
Subject: [Non-DoD Source] [Paraview] Building on Cray systems

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 everybody,

I'm about to endeavor on the always fun process of building Paraview on Cray
systems, specifically Copper (ERDC), Garnet (ERDC) and Excalibur (ARL).
Little is ever easy on these systems and I've never succeeded at building
paraview on them in the past. However, we want to run with co-processing on
the compute nodes and so it's time to try again.

I saw there are some build scripts in the ParaviewSuperbuild for Cray
systems. Does anybody know of any documentation or examples on how to use
them? What dependencies do I need to build using the superbuild and what can
I use that is already on the system? For example -- python, HDF5, zlib, etc
are all available, but do I need to build my own versions?

Is it possible to build just Paraview (not using the superbuild) using the
system-installed modules? Does the FREEZE_PYTHON option work or help
eliminate the issues of running on the compute nodes?

If anybody has any advice on the best way to go, I would greatly appreciate
it. We need to have python, co-processing, and off-screen rendering enabled;
otherwise, it's just the standard build options.

Thanks!

Tim
___
Powered by Caution-Caution-www.kitware.com < 
Caution-http://Caution-Caution-www.kitware.com >

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

Please keep messages on-topic and check the

Re: [Paraview] [Non-DoD Source] Building on Cray systems

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Tim - I've already built ParaView on all of these systems - there are
modules available to load various version of Paraview.If you need to do
your own builds to support specific functionality - I can provide you the
build scripts we use on those systems.




-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Tim
Gallagher
Sent: Thursday, February 04, 2016 8:25 AM
To: paraview 
Subject: [Non-DoD Source] [Paraview] Building on Cray systems

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 everybody,

I'm about to endeavor on the always fun process of building Paraview on Cray
systems, specifically Copper (ERDC), Garnet (ERDC) and Excalibur (ARL).
Little is ever easy on these systems and I've never succeeded at building
paraview on them in the past. However, we want to run with co-processing on
the compute nodes and so it's time to try again. 

I saw there are some build scripts in the ParaviewSuperbuild for Cray
systems. Does anybody know of any documentation or examples on how to use
them? What dependencies do I need to build using the superbuild and what can
I use that is already on the system? For example -- python, HDF5, zlib, etc
are all available, but do I need to build my own versions? 

Is it possible to build just Paraview (not using the superbuild) using the
system-installed modules? Does the FREEZE_PYTHON option work or help
eliminate the issues of running on the compute nodes? 

If anybody has any advice on the best way to go, I would greatly appreciate
it. We need to have python, co-processing, and off-screen rendering enabled;
otherwise, it's just the standard build options.

Thanks!

Tim
___
Powered by Caution-www.kitware.com

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

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

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

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


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] [Non-DoD Source] ANN: ParaView 5.0.0-RC1 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

gcc on our RHEL5 systems is 4.1 and seemingly cannot be upgraded.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Ben Boeckel 
Reply-To: "ben.boec...@kitware.com" 
Date: Wednesday, January 13, 2016 at 1:20 PM
To: Rick Angelini 
Cc: "paraview@paraview.org" 
Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.0.0-RC1 is
available for download

On Wed, Jan 13, 2016 at 16:50:59 +0000, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) wrote:
> Has anyone tried or been able to build ParaView 5.0 on RHEL5?Looks
> like there may be compiler dependencies which exclude a successful build
> on RHEL5?  So far, I’ve not had any luck …..

Doesn't Red Hat provide a gcc44 package? Or was that EPEL?

--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] ANN: ParaView 5.0.0-RC1 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Has anyone tried or been able to build ParaView 5.0 on RHEL5?Looks
like there may be compiler dependencies which exclude a successful build
on RHEL5?  So far, I’ve not had any luck …..

Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Ben Boeckel

Reply-To: "ben.boec...@kitware.com" 
Date: Thursday, November 12, 2015 at 3:45 PM
To: "paraview@paraview.org" 
Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.0.0-RC1 is available
for download

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.  






Folks,

ParaView 5.0.0-RC1 is now available for download. Checkout the release
notes on the Kitware blog [1].

As always, we look forward to your feedback [2].

Also stay tuned to the Kitware Blog [3] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- The ParaView team

[1] Caution-http://kitware.com/blog/home/post/998
[2] Caution-http://paraview.uservoice.com
[3] Caution-http://www.kitware.com/blog/
___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] [Non-DoD Source] Re: PV 4.4.0 crashing issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Is there a v5.0-RC tag in the Paraview superbuild?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Friday, January 8, 2016 at 3:40 PM
To: Utkarsh Ayachit 
Cc: "paraview@paraview.org" 
Subject: Re: [Paraview] [Non-DoD Source] Re:  PV 4.4.0 crashing issue

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.  






Yep - I think so - I’ll keep an eye out for the production release of 5.0
…..



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, January 8, 2016 at 3:35 PM
To: Rick Angelini 
Cc: "paraview@paraview.org" 
Subject: [Non-DoD Source] Re: [Paraview] PV 4.4.0 crashing issue

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.  






Rick,

That sounds like this bug:
Caution-Caution-http://www.paraview.org/Bug/view.php?id=15763
It was fixed 5.0.0.

Utkarsh

On Fri, Jan 8, 2016 at 3:31 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> In my original message, I attached the wrong cmake command - I’m not
>using
> qt5 on  my Linux release of PV 4.4.0.
>
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> -DParaView_FROM_GIT=OFF \
> -DParaView_URL=`pwd`/../Downloads/ParaView-v4.3.1-source.tar.gz \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_SYSTEM_mpi=OFF ../Source
> make -j 8 install
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: Rick Angelini 
> Date: Friday, January 8, 2016 at 3:20 PM
> To: "paraview@paraview.org" 
> Subject: PV 4.4.0 crashing issue
>
> I’m finding an issue with the production release of PV 4.4.0 …. I can
> consistently make a client-server connection crash by loading up either
>an
> Exodus or CTH dataset and through some combination of quick left-right
>mouse
> clicks, or double-right mouse clicks in the graphics window,  I can shut
> things down.  I’m only seeing this on Linux clients – I cannot duplicate
> running PV 4.4.0 on a Mac.   See attached screenshot.   I’ve been
>able
> to duplicate this behavior on many different datasets of CTH/Exodus
>format,
> but I suspect this is a GUI interaction issue, not a data issue.
>
> I’ve sent this on both standard RHEL5 and RHEL5 Linux workstations – I’ve
> tried recompiling the client using the super build script, but doesn’t
>seem
> to make much any difference.Any ideas?
>
> which cmake
> cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> 
>-DParaView_URL=Caution-Caution-http://www.paraview.org/files/v4.4/ParaView
>-v4.4.0-
>source.tar.gz
> \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt5=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_NONFREE_COMPONENTS=OFF \
> -DUSE_SYSTEM_mpi=OFF ../Source
>
> make -j 8 install
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> ___
> Powered by Caution-Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe

Re: [Paraview] [Non-DoD Source] Re: PV 4.4.0 crashing issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Yep - I think so - I’ll keep an eye out for the production release of 5.0
…..



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Friday, January 8, 2016 at 3:35 PM
To: Rick Angelini 
Cc: "paraview@paraview.org" 
Subject: [Non-DoD Source] Re: [Paraview] PV 4.4.0 crashing issue

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.  






Rick,

That sounds like this bug:
Caution-http://www.paraview.org/Bug/view.php?id=15763
It was fixed 5.0.0.

Utkarsh

On Fri, Jan 8, 2016 at 3:31 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> In my original message, I attached the wrong cmake command - I’m not
>using
> qt5 on  my Linux release of PV 4.4.0.
>
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> -DParaView_FROM_GIT=OFF \
> -DParaView_URL=`pwd`/../Downloads/ParaView-v4.3.1-source.tar.gz \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_SYSTEM_mpi=OFF ../Source
> make -j 8 install
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: Rick Angelini 
> Date: Friday, January 8, 2016 at 3:20 PM
> To: "paraview@paraview.org" 
> Subject: PV 4.4.0 crashing issue
>
> I’m finding an issue with the production release of PV 4.4.0 …. I can
> consistently make a client-server connection crash by loading up either
>an
> Exodus or CTH dataset and through some combination of quick left-right
>mouse
> clicks, or double-right mouse clicks in the graphics window,  I can shut
> things down.  I’m only seeing this on Linux clients – I cannot duplicate
> running PV 4.4.0 on a Mac.   See attached screenshot.   I’ve been
>able
> to duplicate this behavior on many different datasets of CTH/Exodus
>format,
> but I suspect this is a GUI interaction issue, not a data issue.
>
> I’ve sent this on both standard RHEL5 and RHEL5 Linux workstations – I’ve
> tried recompiling the client using the super build script, but doesn’t
>seem
> to make much any difference.Any ideas?
>
> which cmake
> cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
> -Ddownload_location=`pwd`/../Downloads \
> 
>-DParaView_URL=Caution-http://www.paraview.org/files/v4.4/ParaView-v4.4.0-
>source.tar.gz
> \
> -DCMAKE_BUILD_TYPE=Release \
> -DENABLE_visitbridge:BOOL=ON \
> -DENABLE_cgns=ON \
> -DENABLE_boost=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt5=ON \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -Dqt_DISABLE_WEBKIT=OFF \
> -DUSE_NONFREE_COMPONENTS=OFF \
> -DUSE_SYSTEM_mpi=OFF ../Source
>
> make -j 8 install
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> ___
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-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] PV 4.4.0 crashing issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I’m finding an issue with the production release of PV 4.4.0 …. I can 
consistently make a client-server connection crash by loading up either an 
Exodus or CTH dataset and through some combination of quick left-right mouse 
clicks, or double-right mouse clicks in the graphics window,  I can shut things 
down.  I’m only seeing this on Linux clients – I cannot duplicate running PV 
4.4.0 on a Mac.   See attached screenshot.   I’ve been able to duplicate 
this behavior on many different datasets of CTH/Exodus format, but I suspect 
this is a GUI interaction issue, not a data issue.

I’ve sent this on both standard RHEL5 and RHEL5 Linux workstations – I’ve tried 
recompiling the client using the super build script, but doesn’t seem to make 
much any difference.Any ideas?

which cmake
cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_URL=http://www.paraview.org/files/v4.4/ParaView-v4.4.0-source.tar.gz 
\
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_boost=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt5=ON \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=OFF \
-DUSE_NONFREE_COMPONENTS=OFF \
-DUSE_SYSTEM_mpi=OFF ../Source

make -j 8 install


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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] PV 4.4.0 crashing issue

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

In my original message, I attached the wrong cmake command - I’m not using qt5 
on  my Linux release of PV 4.4.0.


cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v4.3.1-source.tar.gz \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_boost=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt=ON \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=OFF \
-DUSE_SYSTEM_mpi=OFF ../Source
make -j 8 install



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Friday, January 8, 2016 at 3:20 PM
To: "paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: PV 4.4.0 crashing issue

I’m finding an issue with the production release of PV 4.4.0 …. I can 
consistently make a client-server connection crash by loading up either an 
Exodus or CTH dataset and through some combination of quick left-right mouse 
clicks, or double-right mouse clicks in the graphics window,  I can shut things 
down.  I’m only seeing this on Linux clients – I cannot duplicate running PV 
4.4.0 on a Mac.   See attached screenshot.   I’ve been able to duplicate 
this behavior on many different datasets of CTH/Exodus format, but I suspect 
this is a GUI interaction issue, not a data issue.

I’ve sent this on both standard RHEL5 and RHEL5 Linux workstations – I’ve tried 
recompiling the client using the super build script, but doesn’t seem to make 
much any difference.Any ideas?

which cmake
cmake -DCMAKE_INSTALL_PREFIX:PATH=~/paraview/${version} \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_URL=http://www.paraview.org/files/v4.4/ParaView-v4.4.0-source.tar.gz 
\
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_boost=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt5=ON \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=OFF \
-DUSE_NONFREE_COMPONENTS=OFF \
-DUSE_SYSTEM_mpi=OFF ../Source

make -j 8 install


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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] QT5/libxcb on RHEL5

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I’m doing some test build of PV 4.4.0, and if I try to build using QT5, I need 
to have access to the libxcb libraries.It doesn’t look like there’s an RPM 
for this for RHEL5 .Can the Superbuild script be tweaked to pick up the 
sources for this dependent library and build it if it can’t find it on the 
system? Otherwise, at least on RHEL5, I’ll need to download/build outside 
of the Superbuild?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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] Pull Downloads only

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

I have to build systems that do not have external network connectivity – is 
there a trick to tell the Superbuild to only pull down the tar balls that it 
needs to build but not actually do the build?




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
___
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] ANN: ParaView 4.4.0 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Duh, found it … -D Enable_qt4 ….


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Rick Angelini

Date: Tuesday, September 15, 2015 at 9:09 AM
To: Utkarsh Ayachit , ParaView

Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download

This email was sent from a non-Department of Defense email account, and
contained active links. All links are disabled, and require you to copy
and paste the address to a Web browser. Please verify the identity of the
sender, and confirm authenticity of all links contained within the
message.  



 
How do I tell the superbuild to use QT4?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Tuesday, September 15, 2015 at 9:05 AM
To: Rick Angelini 
Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download

:), thanks for pointing it out.

On Tue, Sep 15, 2015 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> Thanks Utkarsh.  That makes it consistent with other production releases
> are tagged for download ….   8-)
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Tuesday, September 15, 2015 at 8:42 AM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download
>
> This email was sent from a non-Department of Defense email account, and
> contained active links. All links are disabled, and require you to copy
> and paste the address to a Web browser. Please verify the identity of the
> sender, and confirm authenticity of all links contained within the
> message.
>
>
>
>
> Hmm...I was using it to point to the "latest stable" release. I
> suppose I'll just remove the text to avoid confusion .... fixed.
>
> Utkarsh
>
> On Tue, Sep 15, 2015 at 8:27 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
>> If I go to the download page ,  I can download something called '4.4
>> (Latest Stable)' which to me implies that’s still a development build
>>and
>> not the final production release?
>>
>> Caution-www.paraview.org/download/
>>
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: ParaView  on behalf of Utkarsh
>> Ayachit 
>> Date: Monday, September 14, 2015 at 2:08 PM
>> To: ParaView 
>> Cc: ParaView Developers 
>> Subject: [Paraview] ANN: ParaView 4.4.0 is available for download
>>
>> Caution-www.kitware.com/blog/home/post/966
>>
>

___
Powered by Caution-www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
Caution-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] ANN: ParaView 4.4.0 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

How do I tell the superbuild to use QT4?


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Tuesday, September 15, 2015 at 9:05 AM
To: Rick Angelini 
Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download

:), thanks for pointing it out.

On Tue, Sep 15, 2015 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> Thanks Utkarsh.  That makes it consistent with other production releases
> are tagged for download ….   8-)
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit 
> Date: Tuesday, September 15, 2015 at 8:42 AM
> To: Rick Angelini 
> Cc: ParaView , ParaView Developers
> 
> Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download
>
> This email was sent from a non-Department of Defense email account, and
> contained active links. All links are disabled, and require you to copy
> and paste the address to a Web browser. Please verify the identity of the
> sender, and confirm authenticity of all links contained within the
> message.
>
>
>
>
> Hmm...I was using it to point to the "latest stable" release. I
> suppose I'll just remove the text to avoid confusion .... fixed.
>
> Utkarsh
>
> On Tue, Sep 15, 2015 at 8:27 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
>> If I go to the download page ,  I can download something called '4.4
>> (Latest Stable)' which to me implies that’s still a development build
>>and
>> not the final production release?
>>
>> Caution-www.paraview.org/download/
>>
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: ParaView  on behalf of Utkarsh
>> Ayachit 
>> Date: Monday, September 14, 2015 at 2:08 PM
>> To: ParaView 
>> Cc: ParaView Developers 
>> Subject: [Paraview] ANN: ParaView 4.4.0 is available for download
>>
>> Caution-www.kitware.com/blog/home/post/966
>>
>

___
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] ANN: ParaView 4.4.0 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Thanks Utkarsh.  That makes it consistent with other production releases
are tagged for download ….   8-)


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Utkarsh Ayachit 
Date: Tuesday, September 15, 2015 at 8:42 AM
To: Rick Angelini 
Cc: ParaView , ParaView Developers

Subject: Re: [Paraview] ANN: ParaView 4.4.0 is available for download

This email was sent from a non-Department of Defense email account, and
contained active links. All links are disabled, and require you to copy
and paste the address to a Web browser. Please verify the identity of the
sender, and confirm authenticity of all links contained within the
message.  



 
Hmm...I was using it to point to the "latest stable" release. I
suppose I'll just remove the text to avoid confusion  fixed.

Utkarsh

On Tue, Sep 15, 2015 at 8:27 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> If I go to the download page ,  I can download something called '4.4
> (Latest Stable)' which to me implies that’s still a development build and
> not the final production release?
>
> Caution-www.paraview.org/download/
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView  on behalf of Utkarsh
> Ayachit 
> Date: Monday, September 14, 2015 at 2:08 PM
> To: ParaView 
> Cc: ParaView Developers 
> Subject: [Paraview] ANN: ParaView 4.4.0 is available for download
>
> Caution-www.kitware.com/blog/home/post/966
>

___
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] ANN: ParaView 4.4.0 is available for download

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

If I go to the download page ,  I can download something called '4.4
(Latest Stable)' which to me implies that’s still a development build and
not the final production release?

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


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: ParaView  on behalf of Utkarsh
Ayachit 
Date: Monday, September 14, 2015 at 2:08 PM
To: ParaView 
Cc: ParaView Developers 
Subject: [Paraview] ANN: ParaView 4.4.0 is available for download

www.kitware.com/blog/home/post/966

___
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