[Paraview] default_servers.pvsc question

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

Question about the default_servers.pvsc file…..

I have this in my host profile:

  

  

 


So, when the GUI pops up, the user has an opportunity to change the path to 
ssh.   But, rather than hard-coding the default value, or presenting blank 
field and have the user put in the correct path, is it possible to query the 
user’s environment and find `which ssh` and substitute in that value??





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] default_servers.pvsc question

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

Burlen/Utkarsh —— my preferred solution is also to not set an environment
variable if possible.  For my particular issue, I’d much rather be able to
do a `which ssh` (or equivalent) to get the answer than than asking the
user to set an environment variable.

Implementing a python-based default_servers definition opens things up for
much more programmatic flexibility.

# take a guess at which ssh command to use

try:
default_shell=os.popen("which ssh").read()
default_shell=default_shell.rstrip("\r\n")
except:
default_shell="/usr/krb5/bin/





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




-Original Message-
From: Burlen Loring 
Date: Sunday, April 12, 2015 at 10:34 PM
To: Utkarsh Ayachit , Rick Angelini

Cc: "paraview@paraview.org" 
Subject: Re: [Paraview] default_servers.pvsc question

Hi Utkarsh,

I think environment variables are kind of a band aid around a larger
issue. In addition to leveraging the user's local environment, there's
also no way to get information from the server side environment. for
example list of account numbers a user can charge jobs to, or a list of
active queues. One thing I have been thinking about is  rather than just
reading pvsc from an xml file, paraview could call a script to get the
pvsc xml. This script could query the user's local/remote environment
and generate the xml. A long time ago we had talked about a python based
solution. What do you think?

Burlen

On 4/12/2015 11:31 AM, Utkarsh Ayachit wrote:
> Rick,
>
> Alas no, this isn't currently supported. But should be fairly
> straightforward to add. I've reported a bug:
> http://www.paraview.org/Bug/view.php?id=15421
>
> Utkarsh
>
> On Fri, Apr 10, 2015 at 4:09 PM, Angelini, Richard C (Rick) CIV USARMY
> ARL (US)  wrote:
>> Question about the default_servers.pvsc file…..
>>
>> I have this in my host profile:
>>
>>
>>  
>>
>> 
>>   
>> 
>>
>> So, when the GUI pops up, the user has an opportunity to change the
>>path to
>> ssh.   But, rather than hard-coding the default value, or presenting
>>blank
>> field and have the user put in the correct path, is it possible to
>>query the
>> user’s environment and find `which ssh` and substitute in that value??
>>
>>
>>
>>
>> 
>> 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
>>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
>http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
>http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview


___
Powered by www.kitware.com

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

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

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

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

[Paraview] Offscreen rendering? (UNCLASSIFIED)

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

CLASSIFICATION: UNCLASSIFIED

I have a standard client-server connection set up to a remote system.   I'm
dumping out a long animation, saving JPG files. If I iconify my ParaView
session or allow the Linux screenlock to kick in, my resulting saved images
are corrupted (blank, black, garbled).In this scenario, is there
some way to force ParaView to do offscreen rendering in this interactive
session?


I've been looking at settings and command line flags, but I don't see
anything in the GUI or the client.   There does seem to be a flag on the
pvserver, but the user doesn't have access to that flag directly using the
preconfigure job launching configuration scripts.



CLASSIFICATION: UNCLASSIFIED


smime.p7s
Description: S/MIME cryptographic signature
___
Powered by www.kitware.com

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

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

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

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

Re: [Paraview] [EXTERNAL] Offscreen rendering? (UNCLASSIFIED)

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

CLASSIFICATION: UNCLASSIFIED

Bingo!   There it is ... thanks!

-Original Message-
From: Scott, W Alan [mailto:wasc...@sandia.gov] 
Sent: Wednesday, April 29, 2015 3:22 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: RE: [EXTERNAL] [Paraview] Offscreen rendering? (UNCLASSIFIED)

Sorry, my bad.

This is an "advanced" setting.  The Settings panels now have standard
(default) and advanced layouts (sticky, which is what I currently have).
You change it by clicking the little gear icon in the upper right corner of
the Settings dialog.  This setting is found in the advanced settings.

Alan

-Original Message-----
From: Angelini, Richard C (Rick) CIV USARMY ARL (US)
[mailto:richard.c.angelini@mail.mil]
Sent: Wednesday, April 29, 2015 1:13 PM
To: Scott, W Alan
Subject: RE: [EXTERNAL] [Paraview] Offscreen rendering? (UNCLASSIFIED)

CLASSIFICATION: UNCLASSIFIED

That would do it if I could find such a thing!  That exists in 4.3.1?

Would I have had to do something at build time to enable such a feature


-Original Message-
From: Scott, W Alan [mailto:wasc...@sandia.gov]
Sent: Wednesday, April 29, 2015 2:25 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US); paraview@paraview.org
Subject: RE: [EXTERNAL] [Paraview] Offscreen rendering? (UNCLASSIFIED)

Rick,
Do you mean Edit/ Settings/ Render View/ Use Offscreen Rendering for
Screenshots?

Alan

-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Angelini,
Richard C (Rick) CIV USARMY ARL (US)
Sent: Wednesday, April 29, 2015 11:59 AM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Offscreen rendering? (UNCLASSIFIED)

CLASSIFICATION: UNCLASSIFIED

I have a standard client-server connection set up to a remote system.   I'm
dumping out a long animation, saving JPG files. If I iconify my ParaView
session or allow the Linux screenlock to kick in, my resulting saved images
are corrupted (blank, black, garbled).In this scenario, is there
some way to force ParaView to do offscreen rendering in this interactive
session?


I've been looking at settings and command line flags, but I don't see
anything in the GUI or the client.   There does seem to be a flag on the
pvserver, but the user doesn't have access to that flag directly using the
preconfigure job launching configuration scripts.



CLASSIFICATION: UNCLASSIFIED


CLASSIFICATION: UNCLASSIFIED


CLASSIFICATION: UNCLASSIFIED


smime.p7s
Description: S/MIME cryptographic signature
___
Powered by www.kitware.com

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

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

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

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

[Paraview] 4.3.1 warnings

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

I thought we saw this warning message several releases ago, but it seems to be 
back again???  Reading CTH dataset in client-server mode:



/app/paraview/4.3.1_osmesa/bin/pvserver
Connecting to client (reverse connection requested)...
Connection URL: csrc://hostname-0001:25248
Client connected.
Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x235a500): vtkSpyPlotReader reported invalid progress 
(2.01875). Value must be between [0, 1]. Clamping to this range.

Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x21034c0): vtkSpyPlotReader reported invalid progress 
(1.81875). Value must be between [0, 1]. Clamping to this range.




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] [EXTERNAL] 4.3.1 warnings

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

This was not a debug build.   It’s a standard CTH-11.0 generated dataset ….



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

From: , Alan Scott mailto:wasc...@sandia.gov>>
Date: Monday, May 4, 2015 at 2:18 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
"paraview@paraview.org<mailto:paraview@paraview.org>" 
mailto:paraview@paraview.org>>
Subject: RE: [EXTERNAL] [Paraview] 4.3.1 warnings

Rick,
If this is a debug build, it is to be expected.  Two issues – one is that 
release builds should never show warnings, debug builds always print out 
warnings.  Second issue, which still needs to be fixed, but is smaller, is that 
the spyplot reader is passing incorrect information to the Progress Handler.  
Frankly, I thought I had fixed it a few years ago...

Can you share this dataset?  Is this a debug build?

Alan

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Angelini, 
Richard C (Rick) CIV USARMY ARL (US)
Sent: Monday, May 04, 2015 9:39 AM
To: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: [EXTERNAL] [Paraview] 4.3.1 warnings

I thought we saw this warning message several releases ago, but it seems to be 
back again???  Reading CTH dataset in client-server mode:



/app/paraview/4.3.1_osmesa/bin/pvserver
Connecting to client (reverse connection requested)...
Connection URL: csrc://hostname-0001:25248
Client connected.
Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x235a500): vtkSpyPlotReader reported invalid progress 
(2.01875). Value must be between [0, 1]. Clamping to this range.

Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x21034c0): vtkSpyPlotReader reported invalid progress 
(1.81875). Value must be between [0, 1]. Clamping to this range.




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] [EXTERNAL] 4.3.1 warnings

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

Thanks for confirming!

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

From: , Alan Scott mailto:wasc...@sandia.gov>>
Date: Monday, May 4, 2015 at 4:12 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
"paraview@paraview.org<mailto:paraview@paraview.org>" 
mailto:paraview@paraview.org>>
Subject: RE: [EXTERNAL] [Paraview] 4.3.1 warnings

Just talked to Utkarsh.  My bad, I gave you wrong information, you did find a 
bug.  I will work on fixing it.

Thanks,

Alan

From: Angelini, Richard C (Rick) CIV USARMY ARL (US) 
[mailto:richard.c.angelini@mail.mil]
Sent: Monday, May 04, 2015 1:55 PM
To: Scott, W Alan; paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [EXTERNAL] [Paraview] 4.3.1 warnings

This was not a debug build.   It’s a standard CTH-11.0 generated dataset ….



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

From: , Alan Scott mailto:wasc...@sandia.gov>>
Date: Monday, May 4, 2015 at 2:18 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
"paraview@paraview.org<mailto:paraview@paraview.org>" 
mailto:paraview@paraview.org>>
Subject: RE: [EXTERNAL] [Paraview] 4.3.1 warnings

Rick,
If this is a debug build, it is to be expected.  Two issues – one is that 
release builds should never show warnings, debug builds always print out 
warnings.  Second issue, which still needs to be fixed, but is smaller, is that 
the spyplot reader is passing incorrect information to the Progress Handler.  
Frankly, I thought I had fixed it a few years ago...

Can you share this dataset?  Is this a debug build?

Alan

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Angelini, 
Richard C (Rick) CIV USARMY ARL (US)
Sent: Monday, May 04, 2015 9:39 AM
To: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: [EXTERNAL] [Paraview] 4.3.1 warnings

I thought we saw this warning message several releases ago, but it seems to be 
back again???  Reading CTH dataset in client-server mode:



/app/paraview/4.3.1_osmesa/bin/pvserver
Connecting to client (reverse connection requested)...
Connection URL: csrc://hostname-0001:25248
Client connected.
Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x235a500): vtkSpyPlotReader reported invalid progress 
(2.01875). Value must be between [0, 1]. Clamping to this range.

Warning: In 
/u/home/angel/PV/4.3.1/Build/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgressHandler.cxx,
 line 261
vtkPVProgressHandler (0x21034c0): vtkSpyPlotReader reported invalid progress 
(1.81875). Value must be between [0, 1]. Clamping to this range.




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] Superbuild 3.98.1

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

I've been playing around with SuperBuild and it seems to working correct.  But, 
it also seems to be pulling the most recent source updates from the git 
repository.   Is there a way use SuperBuild to only build the most recent 
production release (3.98.1)?

Thanks



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

[Paraview] SuperBuild question

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

Is there a way to tell the SuperBuild process to not look for software updates 
using GIT? I doing a build on a system that doesn't have public network 
access and I'm actually dying on a complaint about my instance of git being too 
old.  However, I have already copied in the sources, so I don't want it looking 
for updates anyway.




Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] SuperBuild question (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Can you point the cmake directives to look in a Downloads directory and
determine which packages to be built based on the tarballs in that download
directory?


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Wednesday, May 01, 2013 12:08 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] SuperBuild question

You can do the following:

> edit the versions.cmake file
> in there, you'll find a stub like so

add_revision(paraview
  GIT_REPOSITORY git://paraview.org/ParaView.git
  GIT_TAG "master")

Change that to  something as follows:
add_revision(paraview
  URL 
  URL_MD5 )

I think I want to add some mode for this, but I'm not sure what tar ball it
should point to and what MD5SUM it should use. Maybe I can provide cmake
options to set the two? What do you think?

Utkarsh


On Wed, May 1, 2013 at 11:36 AM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Is there a way to tell the SuperBuild process to not look for software
> updates using GIT? I doing a build on a system that doesn't have
public
> network access and I'm actually dying on a complaint about my instance 
> of git being too old.  However, I have already copied in the sources, 
> so I don't want it looking for updates anyway.
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>

Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] RHEL6 Superbuild error

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

I'm trying to build ParaView 3.98.1 on a RHEL6 cluster and I'm getting stuck in 
Qt.The errors look like they are related to Webkit and the tests/examples.  
   Does it need to build with Webkit? Or better yet, how to I get the 
Superbuild to not build Webkit, examples and tests?There's a file 
pv-qt-configure.cmake where I can set some flags, but it keeps getting 
overwritten if I make changes to this file.There must be a better way to do 
this!   8-)


FYI - here is the error I seen on my RHEL6 cluster build:

make[2]: Entering directory 
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/WebKit/qt/tests'
cd qwebframe/ && make -f Makefile.WebKit
make[3]: Entering directory 
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/WebKit/qt/tests/qwebframe'
g++ -L/u/home/angelini/PV/Build/install/lib -Wl,-O1 
-Wl,-rpath,/u/US_HOME1/angelini/PV/Build/qt/src/qt/src/3rdparty/webkit/Source/lib
 -Wl,-rpath,/u/home/angelini/PV/Build/install/lib 
-Wl,-rpath,/u/home/angelini/PV/Build/install/lib -o tst_qwebframe 
.obj/release-shared/tst_qwebframe.o .obj/release-shared/qrc_tst_qwebframe.o
-L/u/home/angelini/PV/Build/install/lib 
-L/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/lib -L/usr/X11R6/lib64 
-L/u/home/angelini/PV/Build/install/lib 
-L/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/lib -lQtDeclarative -lQtScript 
-lQtSql -lQtXmlPatterns -L/usr/X11R6/lib64 -lQtWebKit -lQtTest -lQtGui 
-lQtNetwork -lQtCore -lpthread -lXrender -lfontconfig -lfreetype -lXext -lX11 
-lm
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlOutputBufferCreateFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNodeGetContent@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewChild@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDocNode@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseCharEncoding@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSearchNsByHref@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFindCharEncodingHandler@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSaveFormatFileTo@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseMemory@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFree@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlDocGetRootElement@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFreeDoc@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewNs@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDoc@LIBXML2_2.4.30'
collect2: ld returned 1 exit status
make[3]: *** [tst_qwebframe] Error 1
make[3]: Leaving directory 
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/WebKit/qt/tests/qwebframe'
make[2]: *** [sub-qwebframe-make_default] Error 2
make[2]: Leaving directory 
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/WebKit/qt/tests'
make[1]: *** [sub-WebKit-qt-tests-make_default-ordered] Error 2
make[1]: Leaving directory 
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source'
make: *** [sub-webkit-make_default-ordered] Error 2



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'll try modifying the files as you suggest.  I've used Superbuild on
numerous systems to build 3.98.1 and I have not run into this particular QT
issue.  This is also one of the first (the first?) RHEL6 cluster that I've
tried to build on. 

Given the error messages, I thought that the easiest workaround would be to
throw some flags at the configuration script to avoid building WebKit,
examples and tests.HOWEVER, it may be worth someone's effort to try to
figure out where the error messages are coming from and what's the correct
fix, rather than giggling the configuration command!   8-)



-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Wednesday, May 08, 2013 12:56 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] RHEL6 Superbuild error

Try changing the flags in Source/Prohects/qt.cmake instead. For my info,
what are the flags that you're setting. Maybe we can change the default
setup itself.

Utkarsh

On Wed, May 8, 2013 at 11:34 AM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> I'm trying to build ParaView 3.98.1 on a RHEL6 cluster and I'm getting
stuck
> in Qt.The errors look like they are related to Webkit and the
> tests/examples. Does it need to build with Webkit? Or better yet,
> how to I get the Superbuild to not build Webkit, examples and tests?
> There's a file pv-qt-configure.cmake where I can set some flags, but it
> keeps getting overwritten if I make changes to this file.There must be
a
> better way to do this!   8-)
>
>
> FYI - here is the error I seen on my RHEL6 cluster build:
>
> make[2]: Entering directory
>
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/We
bKit/qt/tests'
> cd qwebframe/ && make -f Makefile.WebKit
> make[3]: Entering directory
>
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/We
bKit/qt/tests/qwebframe'
> g++ -L/u/home/angelini/PV/Build/install/lib -Wl,-O1
> -Wl,-rpath,/u/US_HOME1/angelini/PV/Build/qt/src/qt/src/3rdparty/webkit
> /Source/lib -Wl,-rpath,/u/home/angelini/PV/Build/install/lib
> -Wl,-rpath,/u/home/angelini/PV/Build/install/lib -o tst_qwebframe 
> .obj/release-shared/tst_qwebframe.o 
> .obj/release-shared/qrc_tst_qwebframe.o
> -L/u/home/angelini/PV/Build/install/lib
> -L/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/lib -L/usr/X11R6/lib64 
> -L/u/home/angelini/PV/Build/install/lib
> -L/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/lib -lQtDeclarative 
> -lQtScript -lQtSql -lQtXmlPatterns -L/usr/X11R6/lib64 -lQtWebKit 
> -lQtTest -lQtGui -lQtNetwork -lQtCore -lpthread -lXrender -lfontconfig 
> -lfreetype -lXext -lX11 -lm
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlOutputBufferCreateFile@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlNodeGetContent@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlNewChild@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlNewDocNode@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlParseCharEncoding@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlParseFile@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlSearchNsByHref@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlFindCharEncodingHandler@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlSaveFormatFileTo@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlParseMemory@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlFree@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlDocGetRootElement@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlFreeDoc@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlNewNs@LIBXML2_2.4.30'
> /usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
> `xmlNewDoc@LIBXML2_2.4.30'
> collect2: ld returned 1 exit status
> make[3]: *** [tst_qwebframe] Error 1
> make[3]: Leaving directory
>
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/We
bKit/qt/tests/qwebframe'
> make[2]: *** [sub-qwebframe-make_default] Error 2
> make[2]: Leaving directory
>
`/u/US_HOME1/angelini/PV/Build/qt/src/qt-build/src/3rdparty/webkit/Source/We
bKit/qt/tests'
> make[1]: *** [sub-WebKit-qt-tests-mak

Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

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

eference to 
`xmlParseMemory@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFree@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlDocGetRootElement@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFreeDoc@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewNs@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDoc@LIBXML2_2.4.30'
collect2: ld returned 1 exit status
gmake[7]: *** [tst_qgraphicswebview] Error 1
gmake[6]: *** [sub-qgraphicswebview-make_default] Error 2
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlOutputBufferCreateFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNodeGetContent@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewChild@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDocNode@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseCharEncoding@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSearchNsByHref@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFindCharEncodingHandler@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSaveFormatFileTo@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseMemory@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFree@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlDocGetRootElement@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFreeDoc@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewNs@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDoc@LIBXML2_2.4.30'
collect2: ld returned 1 exit status
gmake[7]: *** [tst_qwebframe] Error 1
gmake[6]: *** [sub-qwebframe-make_default] Error 2
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlOutputBufferCreateFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNodeGetContent@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewChild@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDocNode@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseCharEncoding@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseFile@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSearchNsByHref@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFindCharEncodingHandler@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlSaveFormatFileTo@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlParseMemory@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFree@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlDocGetRootElement@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlFreeDoc@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewNs@LIBXML2_2.4.30'
/usr/lib64/libgstreamer-0.10.so.0: undefined reference to 
`xmlNewDoc@LIBXML2_2.4.30'
collect2: ld returned 1 exit status
gmake[7]: *** [tst_qwebpage] Error 1
gmake[6]: *** [sub-qwebpage-make_default] Error 2
gmake[5]: *** [sub-WebKit-qt-tests-make_default-ordered] Error 2
gmake[4]: *** [sub-webkit-make_default-ordered] Error 2
CMake Error at /u/home/angelini/PV/Build/pv-qt-build.cmake:26 (message):
  Failed!!!


make[3]: *** [qt/src/qt-stamp/qt-build] Error 1
make[2]: *** [CMakeFiles/qt.dir/all] Error 2
make[1]: *** [CMakeFiles/qt.dir/rule] Error 2
make: *** [qt] Error 2



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Wednesday, May 08, 2013 2:11 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

Rick,

You cannot avoid building WebKit for ParaView (the tests/examples sure
can be skipped). ParaView currently needs WebKit. I've been thinking
of making that optional and not build the help-subsystem if WebKit is
unavailable, but that hasn't happened yet.

Utkarsh

On Wed, May 8, 2013 at 1:49 PM, Angel

Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

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

Any ideas on a short-term solution on how I might get past this build issue?
   I'd like to get a ParaView build on this platform!   8-)   I am able to 
get a clean build with Mesa turned on.It's the GL build that's failing.


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Thursday, May 09, 2013 8:32 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

Rick,

> I'd take an option to not build the webkit and eliminate the help-subsystem 
> if that'll get me a clean build.

I'll put that on my todo list.

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

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

Re: [Paraview] RHEL6 Superbuild error [Re: ParaView Digest, Vol 109, Issue 20]

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

Bill - great suggestion on the Webkit ... but there's NO WAY the system admins 
will allow that!  8-)They tend to lock out systems down quite a bit 

Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Bill Sherman [sherm...@indiana.edu]
Sent: Thursday, May 09, 2013 10:51 AM
To: paraview@paraview.org
Cc: Bill Sherman
Subject: Re: [Paraview] RHEL6 Superbuild error [Re: ParaView Digest, Vol 109,   
Issue 20]

Rick, Utkarsh,

> Message: 3
> Date: Thu, 9 May 2013 08:32:35 -0400
> From: Utkarsh Ayachit
> Subject: Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)
> To: "Angelini,    Richard C (Rick) CIV USARMY ARL (US)"
>   
>
> Rick,
>
>> I'd take an option to not build the webkit and eliminate the help-subsystem 
>> if that'll get me a clean build.
>
> I'll put that on my todo list.

So I've built a recent git clone of ParaView on an RHEL 6 system, and
I too hit the webkit requirement.  (In fact, on my second build I'd
forgotten about it, so I got stalled on that myself.)

But I got a working/clean build by including the "qtwebkit" package.
Of course with RHEL, a lot of these packages aren't in the Redhat
repositories.  So, I found that by using the "epel" repository I
have access to that package.

Not that you don't know how to do this, but for others following the
thread, the I was able to add the "epel" respository with this
command:
% su -c 'rpm -Uvh
http://mirrors.nebo.edu/public/epel/5/x86_64/epel-release-5-4.noarch.rpm'

Of course, if there is a way to not include extras that require extra
package installs, that would be good too.

> Utkarsh

Bill

--
Bill Sherman
Sr. Technology Adivsor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University
sherm...@indiana.edu

> End of ParaView Digest, Vol 109, Issue 20
> *

___
Powered by www.kitware.com

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

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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
___
Powered by www.kitware.com

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

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

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

Re: [Paraview] [EXTERNAL] Re: RHEL6 Superbuild error (UNCLASSIFIED)

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

Utkarsh - thanks for the update.   Is there (or will there be) a corresponding 
flag in the Superbuild to enable/disable webkit?   Also, I presume that this is 
for version 4 and not applied to 3.98.1?


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Thursday, May 16, 2013 10:21 AM
To: Scott, W Alan
Cc: Angelini, Richard C (Rick) CIV USARMY ARL (US); paraview@paraview.org
Subject: Re: [EXTERNAL] Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)

Rick,

I've pushed a fix to git-master to allow disabling QtWebKit. Turn on
cmake option PQWIDGETS_DISABLE_QTWEBKIT and ParaView will not longer
look for QtWebKit when configuring/building.

http://paraview.org/Bug/view.php?id=13061

Utkarsh


On Thu, May 9, 2013 at 5:28 PM, Scott, W Alan  wrote:
> +1
>
> -Original Message-
> From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On 
> Behalf Of Utkarsh Ayachit
> Sent: Thursday, May 09, 2013 6:33 AM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org
> Subject: [EXTERNAL] Re: [Paraview] RHEL6 Superbuild error (UNCLASSIFIED)
>
> Rick,
>
>> I'd take an option to not build the webkit and eliminate the help-subsystem 
>> if that'll get me a clean build.
>
> I'll put that on my todo list.
>
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

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

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

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

[Paraview] Superbuild installation directory

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

I want to set the installation directory using the Superbuild script, but it 
seems to be ignoring the value

My cmake command looks like:

cmake -DCMAKE_INSTALL_PREFIX=/usr/people/angel/pv-test/3.98.1_osmesa \
-Ddownload_location=`pwd`/../Downloads \
-DENABLE_boost=ON \
-DENABLE_cgns=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_osmesa=ON \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DGIT_EXECUTABLE=/usr/cta/CSE.20130220/Release/git-1.6.5.2/bin/git \
-DUSE_SYSTEM_mpi=ON ../Source


When I run "make install" it get a clean build, but the installation directory 
is in Build/install  rather than /usr/people/angel/pv-test/3.98.1_osmesa.If 
I drop into the Build/paraview directory and rerun cmake to change the 
installation directory and then rerun "make install", I get the proper 
installation.   Am I setting the wrong variable when I run the cmake 
command?This is the correct variable as described in the wiki page at 
http://paraview.org/Wiki/ParaView/Superbuild

I'm seeing this with 3.98.1 and 4.0.0rc2






Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] Superbuild installation directory

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

Adding :PATH seems to be the right fix.  Thanks



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Wednesday, May 29, 2013 8:43 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild installation directory

Rick,

There is always going to be a BUILD/install. This is where all the
internal packages ParaViewSuperbuild builds are temporarily installed.
Something is resetting the CMAKE_INSTALL_PREFIX. I cannot find any
code in ParaViewSuperbuild itself that does that. Try this instead:
-DCMAKE_INSTALL_PREFIX:PATH=... (note the :PATH). Does that help?

What cmake version are you using?

Utkarsh

On Wed, May 29, 2013 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US)  wrote:
> I want to set the installation directory using the Superbuild script, but it
> seems to be ignoring the value
>
> My cmake command looks like:
>
> cmake -DCMAKE_INSTALL_PREFIX=/usr/people/angel/pv-test/3.98.1_osmesa \
> -Ddownload_location=`pwd`/../Downloads \
> -DENABLE_boost=ON \
> -DENABLE_cgns=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_osmesa=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt=OFF \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -DGIT_EXECUTABLE=/usr/cta/CSE.20130220/Release/git-1.6.5.2/bin/git \
> -DUSE_SYSTEM_mpi=ON ../Source
>
>
> When I run "make install" it get a clean build, but the installation
> directory is in Build/install  rather than
> /usr/people/angel/pv-test/3.98.1_osmesa.If I drop into the
> Build/paraview directory and rerun cmake to change the installation
> directory and then rerun "make install", I get the proper installation.
> Am I setting the wrong variable when I run the cmake command?This is the
> correct variable as described in the wiki page at
> http://paraview.org/Wiki/ParaView/Superbuild
>
> I'm seeing this with 3.98.1 and 4.0.0rc2
>
>
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

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

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

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

Re: [Paraview] Superbuild installation directory

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

Is there something hard-coded for 4.0 in the Superbuild sources.  I'm building 
3.98.1 and but I'm seeing this error:


CMake Error at cmake_install.cmake:48 (FILE):
  file INSTALL cannot find
  "/usr/people/angel/PV/Build/install/lib/paraview-4.0".



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Wednesday, May 29, 2013 8:43 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild installation directory

Rick,

There is always going to be a BUILD/install. This is where all the
internal packages ParaViewSuperbuild builds are temporarily installed.
Something is resetting the CMAKE_INSTALL_PREFIX. I cannot find any
code in ParaViewSuperbuild itself that does that. Try this instead:
-DCMAKE_INSTALL_PREFIX:PATH=... (note the :PATH). Does that help?

What cmake version are you using?

Utkarsh

On Wed, May 29, 2013 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US)  wrote:
> I want to set the installation directory using the Superbuild script, but it
> seems to be ignoring the value
>
> My cmake command looks like:
>
> cmake -DCMAKE_INSTALL_PREFIX=/usr/people/angel/pv-test/3.98.1_osmesa \
> -Ddownload_location=`pwd`/../Downloads \
> -DENABLE_boost=ON \
> -DENABLE_cgns=ON \
> -DENABLE_ffmpeg=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_matplotlib=ON \
> -DENABLE_osmesa=ON \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_paraview=ON \
> -DENABLE_python=ON \
> -DENABLE_qt=OFF \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -DGIT_EXECUTABLE=/usr/cta/CSE.20130220/Release/git-1.6.5.2/bin/git \
> -DUSE_SYSTEM_mpi=ON ../Source
>
>
> When I run "make install" it get a clean build, but the installation
> directory is in Build/install  rather than
> /usr/people/angel/pv-test/3.98.1_osmesa.If I drop into the
> Build/paraview directory and rerun cmake to change the installation
> directory and then rerun "make install", I get the proper installation.
> Am I setting the wrong variable when I run the cmake command?This is the
> correct variable as described in the wiki page at
> http://paraview.org/Wiki/ParaView/Superbuild
>
> I'm seeing this with 3.98.1 and 4.0.0rc2
>
>
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

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

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

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

[Paraview] 4.0.0-RC2 build issue

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

I am using Superbuild to compile 4.0.0-RC2 and for the most part I'm having 
very good success.  I have a particular HPC system (SGI ICE X) where I'm 
getting a strange error when configuring paraview itself.

"string sub-command REGEX, mode MATCH needs at least 5 arguments total to 
command."

Google pointed me here to a hack/fix that got me past the cmake error message.

http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Build-error-Windows-td1858.html

Is there possibly a better solution to this problem other than manually editing 
the ParaViewDetermineVersion.cmake file?   I'm running cmake 2.8.11 and the 
latest ParaViewSuperbuild source files.



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

[Paraview] Superbuild: passing compiler flags

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

I'm trying to pass some MPI-related flags through the Superbuild cmake.  These 
flags need to get passed down to the actual Paraview source cmake, but they 
don't seem to getting included.   If I run ccmake I can see that the flags have 
not been set - and if I manually add the flags at that time, the build proceeds.

(I'm talking about the MPI_xx) flags being passed via the cmake command line)   
I'm using cmake 2.8.11


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version}_mesa \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-4.0.0-RC3-source.tar.gz \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_boost=ON \
-DENABLE_cgns=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=ON \
-DENABLE_osmesa=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=ON \
-DMPI_CXX=mpicxx \
-DMPI_CXX_INCLUDE_PATH=${CPATH} \
-DMPI_CXX_LIBRARIES=-lmpi -lmpixx -L${LIBRARY_PATH} \
-DMPI_C=mpicc \
-DMPI_C_LIBRARIES=-lmpi -lmpixx -L${LIBRARY_PATH} \
-DMPI_C_INCLUDE_PATH=${CPATH} \
../Source


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] Superbuild: passing compiler flags

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

Thanks for the pointer.   I changed my Superbuild cmake command to pass these 
arguments which I believe now include the correct tags

-DUSE_SYSTEM_mpi=ON \
-DMPI_CXX:FILEPATH=`which mpicxx` \
-DMPI_CXX_INCLUDE_PATH:STRING=${CPATH} \
-DMPI_CXX_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
-DMPI_C:FILEPATH=`which mpicc` \
-DMPI_C_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
-DMPI_C_INCLUDE_PATH:STRING=${CPATH} \
-DMPI_Fortran:FILEPATH=`which mpif90` \
-DMPI_Fortran_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
-DMPI_Fortran_INCLUDE_PATH:STRING=${CPATH} \

In the Build directory, the  CMakeCache.txt file has the correct values:

MPI_C:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
MPI_CXX:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
MPI_CXX_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
MPI_CXX_COMPILE_FLAGS:STRING=
MPI_CXX_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_CXX_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_CXX_LINK_FLAGS:STRING=
MPI_C_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
MPI_C_COMPILE_FLAGS:STRING=
MPI_C_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_C_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_C_LINK_FLAGS:STRING=
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND
MPI_Fortran:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
MPI_Fortran_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_Fortran_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_LIBRARY:FILEPATH=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib

However, the in the Build/paraview/src/paraview-build directory, the 
CMakeCache.txt file does not have the correct values:

MPI_CXX_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
MPI_CXX_COMPILE_FLAGS:STRING=
MPI_CXX_INCLUDE_PATH:STRING=
MPI_CXX_LIBRARIES:STRING=
MPI_CXX_LINK_FLAGS:STRING=
MPI_C_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
MPI_C_COMPILE_FLAGS:STRING=
MPI_C_INCLUDE_PATH:STRING=
MPI_C_LIBRARIES:STRING=
MPI_C_LINK_FLAGS:STRING=
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND
MPI_Fortran_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
MPI_Fortran_COMPILE_FLAGS:STRING=
MPI_Fortran_INCLUDE_PATH:STRING=
MPI_Fortran_LIBRARIES:STRING=
MPI_Fortran_LINK_FLAGS:STRING=



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Wednesday, June 12, 2013 11:48 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing compiler flags

Rick,

Can you try using -D arguments with the correct syntax and see if that works?

cmake documentation states the following:

  -D := = Create a cmake cache entry.

Ensure that you pass each of the -D arguments correctly with ":type" suffix. 
You can identify the type for the variables by running ccmake once and then 
looking at the generated CMakeCache.txt. Also, try quoting the arguments with 
spaces in them, namely MPI_*_LIBRARIES variables.

Utkarsh


On Wed, Jun 12, 2013 at 11:23 AM, Angelini, Richard C (Rick) CIV USARMY ARL 
(US) mailto:richard.c.angelini@mail.mil>> 
wrote:
I'm trying to pass some MPI-related flags through the Superbuild cmake.  These 
flags need to get passed down to the actual Paraview source cmake, but they 
don't seem to getting included.   If I run ccmake I can see that the flags have 
not been set - and if I manually add the flags at that time, the build proceeds.

(I'm talking about the MPI_xx) flags being passed via the cmake command line)   
I'm using cmake 2.8.11


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version}_mesa \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-4.0.0-RC3-source.tar.gz \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_boost=ON \
-DENABLE_cgns=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_mesa=ON \
-DENABLE_osmesa=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=ON \
-DMPI_CXX=mpicxx \
-DMPI_CXX_INCLUDE_PATH=${CPATH} \
-DMPI_CXX_LIBRARIES=-lmpi -lmpixx -L${LIBRARY_PATH} \
-DMPI_C=mpicc \
-DMPI_C_LIBRARIES=-lmpi -lmpixx -L${LIBRARY_PATH} \
-DMPI_C_INCLUDE_PATH=${CPATH} \
../Source


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

___
Powered by www.kitware.com<http://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/Para

Re: [Paraview] Superbuild: passing compiler flags

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

Curiously, if I rerun cmake in the Build/paraview/paraview-build directory 
using these same exact flags,  cmake seems to complete correctly as does the 
build.

MPI_C:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
MPI_CXX:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
MPI_CXX_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
MPI_CXX_COMPILE_FLAGS:STRING=
MPI_CXX_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_CXX_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_CXX_LINK_FLAGS:STRING=
MPI_C_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
MPI_C_COMPILE_FLAGS:STRING=
MPI_C_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_C_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_C_LINK_FLAGS:STRING=
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND
MPI_Fortran:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
MPI_Fortran_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
MPI_Fortran_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
MPI_LIBRARY:FILEPATH=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Sebastien Jourdain [sebastien.jourd...@kitware.com]
Sent: Thursday, June 13, 2013 1:37 PM
To: Utkarsh Ayachit
Cc: Angelini, Richard C (Rick) CIV USARMY ARL (US); paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing compiler flags

Hi Richard,

the solution seems to be elsewhere...

The variables that get propagated to ParaView don't have necessarily the same 
names. (I've listed the ones that are not using the same name)

-DMPI_CXX_LIBRARIES:STRING=${PV_MPI_CXX_LIBRARIES}
-DMPI_C_LIBRARIES:STRING=${PV_MPI_C_LIBRARIES}
-DMPI_EXTRA_LIBRARY:STRING=${PV_MPI_EXTRA_LIBRARY}
-DMPI_LIBRARY:FILEPATH=${PV_MPI_LIBRARY}

Therefore you may need to duplicate some values and use PV_XXX as key.

Not sure that's intended, but I tried to set  -DPV_MPI_CXX_LIBRARIES:STRING="a 
b c d"
and it properly get pushed to the ParaView CMakeCache.txt.

Seb


On Thu, Jun 13, 2013 at 11:29 AM, Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>> wrote:
I think I know what could be happening. Let try a few things here and
I'll get back to you.

Utkarsh

On Thu, Jun 13, 2013 at 8:46 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
> Thanks for the pointer.   I changed my Superbuild cmake command to pass
> these arguments which I believe now include the correct tags
>
> -DUSE_SYSTEM_mpi=ON \
> -DMPI_CXX:FILEPATH=`which mpicxx` \
> -DMPI_CXX_INCLUDE_PATH:STRING=${CPATH} \
> -DMPI_CXX_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
> -DMPI_C:FILEPATH=`which mpicc` \
> -DMPI_C_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
> -DMPI_C_INCLUDE_PATH:STRING=${CPATH} \
> -DMPI_Fortran:FILEPATH=`which mpif90` \
> -DMPI_Fortran_LIBRARIES:STRING="-lmpi -lmpi++ -L${LIBRARY_PATH}" \
> -DMPI_Fortran_INCLUDE_PATH:STRING=${CPATH} \
>
> In the Build directory, the  CMakeCache.txt file has the correct values:
>
> MPI_C:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
> MPI_CXX:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
> MPI_CXX_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
> MPI_CXX_COMPILE_FLAGS:STRING=
> MPI_CXX_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
> MPI_CXX_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
> MPI_CXX_LINK_FLAGS:STRING=
> MPI_C_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
> MPI_C_COMPILE_FLAGS:STRING=
> MPI_C_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
> MPI_C_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
> MPI_C_LINK_FLAGS:STRING=
> MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND
> MPI_Fortran:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
> MPI_Fortran_INCLUDE_PATH:STRING=/opt/sgi/mpt/mpt-2.07/include:/usr/include
> MPI_Fortran_LIBRARIES:STRING=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
> MPI_LIBRARY:FILEPATH=-lmpi -lmpi++ -L/opt/sgi/mpt/mpt-2.07/lib
>
> However, the in the Build/paraview/src/paraview-build directory, the
> CMakeCache.txt file does not have the correct values:
>
> MPI_CXX_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicxx
> MPI_CXX_COMPILE_FLAGS:STRING=
> MPI_CXX_INCLUDE_PATH:STRING=
> MPI_CXX_LIBRARIES:STRING=
> MPI_CXX_LINK_FLAGS:STRING=
> MPI_C_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpicc
> MPI_C_COMPILE_FLAGS:STRING=
> MPI_C_INCLUDE_PATH:STRING=
> MPI_C_LIBRARIES:STRING=
> MPI_C_LINK_FLAGS:STRING=
> MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND
> MPI_Fortran_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
> MPI_Fortra

Re: [Paraview] Superbuild: passing compiler flags

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

Andy - I'm hitting numerous issues with the latest Superbuild sources that I've 
reported directly to Utkarsh/Sebastien 

-Rick


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: Andy Bauer [andy.ba...@kitware.com]
Sent: Monday, June 17, 2013 3:07 PM
To: Sebastien Jourdain
Cc: Utkarsh Ayachit; Angelini, Richard C (Rick) CIV USARMY ARL (US); 
paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing compiler flags

It kind of looks like something funky is still going on with this, at least for 
using the system MPI. In my superbuild cmake cache I get the following for 
MPI_C_LIBRARIES:
/usr/lib/libmpich.so;/usr/lib/libopa.so;/usr/lib/libmpl.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/libcr.so;/usr/lib/x86_64-linux-gnu/libpthread.so

For my paraview/src/paraview-build/CMakeCache.txt I get:
/usr/lib/libmpich.so

Is anyone else hitting this issue besides me?

Andy

On Thu, Jun 13, 2013 at 3:02 PM, Sebastien Jourdain 
mailto:sebastien.jourd...@kitware.com>> wrote:
I'm currently pushing a fix that remove that PV_ prefix. So once it's in, you 
should be good.

commit 3fb38e429260288cbb723fb198fa396e6cc2de27
Author: Sebastien Jourdain 
mailto:sebastien.jourd...@kitware.com>>
Date:   Thu Jun 13 14:59:55 2013 -0400

Remove PV_ prefix for ParaView MPI variable names

Change-Id: Ia40c16c77bbd494c4626def729ea964f3abd9d9c


On Thu, Jun 13, 2013 at 1:51 PM, Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>> wrote:
> Shouldn't there be PV_ variables defined in the CMakeCache.txt file in the 
> paraview directory?

They wont. If you look at mpi.use.system.cmake in PAraViewSuperbuild,
it pass the PV variables as MPI_* variables. I'd say the bug is that
the file uses PV_MPI_* variables at all. They should all just be
MPI_*.

Utkarsh


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

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

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

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


___
Powered by www.kitware.com

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

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

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

[Paraview] Intel Build: QT Error

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

I am trying to build 4.0.1 using the Superbuild on an Intel-build system.I 
have my compilers set to icc/icpc I'm failing deep down in the QT build 
with missing Intel libraries - and I believe that the reason for the failure is 
that somehow QT is trying to build with gcc/g++ rather than icc/icpc.  Is there 
any way to force the compiler selection down to QT?

cd src/corelib/ && make -f Makefile
make[1]: Entering directory 
`/usr/local/u/angel/PV/Build/qt/src/qt-build/src/corelib'
rm -f libQtCore.so.4.8.2 libQtCore.so libQtCore.so.4 libQtCore.so.4.8
g++ -L/usr/local/u/angel/PV/Build/install/lib -Wl,--no-undefined 
-Wl,-e,qt_core_boilerplate -Wl,-O1 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib -shared 
-Wl,-soname,libQtCore.so.4 -o libQtCore.so.4.8.2 
.obj/release-shared/qabstractanimation.o .obj/


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] Intel Build: QT Error

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

Andy - I think that I have that set when I run the top level cmake.   The 
Build/CMakeCache.txt file has this:

CMAKE_CXX_COMPILER:FILEPATH=/opt/intel/Compiler/11.1/056/bin/intel64/icpc
CMAKE_C_COMPILER:FILEPATH=/opt/intel/Compiler/11.1/056/bin/intel64/icc



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: Andy Bauer [andy.ba...@kitware.com]
Sent: Friday, June 21, 2013 2:43 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Intel Build: QT Error

Hi Rick,

You may be able to set your CXX and CC environment variables in the shell your 
building in to get what you want. I don't know enough about the Qt build system 
though to know if it will then use those compilers but I'm optimistic enough to 
think it will :)

Regards,
Andy

On Fri, Jun 21, 2013 at 2:27 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
I am trying to build 4.0.1 using the Superbuild on an Intel-build system.I 
have my compilers set to icc/icpc I'm failing deep down in the QT build 
with missing Intel libraries - and I believe that the reason for the failure is 
that somehow QT is trying to build with gcc/g++ rather than icc/icpc.  Is there 
any way to force the compiler selection down to QT?

cd src/corelib/ && make -f Makefile
make[1]: Entering directory 
`/usr/local/u/angel/PV/Build/qt/src/qt-build/src/corelib'
rm -f libQtCore.so.4.8.2 libQtCore.so libQtCore.so.4 libQtCore.so.4.8
g++ -L/usr/local/u/angel/PV/Build/install/lib -Wl,--no-undefined 
-Wl,-e,qt_core_boilerplate -Wl,-O1 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib -shared 
-Wl,-soname,libQtCore.so.4 -o libQtCore.so.4.8.2 
.obj/release-shared/qabstractanimation.o .obj/


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

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

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

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

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


___
Powered by www.kitware.com

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

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

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

Re: [Paraview] Intel Build: QT Error

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

I may have actually found the right answer ...

You can pass a platform command to qt/configure and one of the options is 
linux-icc-64.

So, in the top level cmake, I've added:

qt_EXTRA_CONFIGURATION_OPTIONS:STRING=-platform linux-icc-64

and it *seems* to be building now!


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Andy Bauer [andy.ba...@kitware.com]
Sent: Friday, June 21, 2013 3:46 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Intel Build: QT Error

Hmm, just to make sure things are working properly do you also get the same 
thing in the Build/paraview/src/paraview-build/CMakeCache.txt? If you aren't 
then it may not have been set properly. If it is then the superbuild code would 
have to be changed to pass that information down to the external projects which 
probably isn't too hard of a task to do. At that point it may be faster to just 
build your own version of Qt with specified compilers (look at 
ParaViewSuperbuild/Projects/qt.cmake for the options that are used to build Qt).

Andy

On Fri, Jun 21, 2013 at 3:31 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
Andy - I think that I have that set when I run the top level cmake.   The 
Build/CMakeCache.txt file has this:

CMAKE_CXX_COMPILER:FILEPATH=/opt/intel/Compiler/11.1/056/bin/intel64/icpc
CMAKE_C_COMPILER:FILEPATH=/opt/intel/Compiler/11.1/056/bin/intel64/icc



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: Andy Bauer [andy.ba...@kitware.com<mailto:andy.ba...@kitware.com>]
Sent: Friday, June 21, 2013 2:43 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] Intel Build: QT Error

Hi Rick,

You may be able to set your CXX and CC environment variables in the shell your 
building in to get what you want. I don't know enough about the Qt build system 
though to know if it will then use those compilers but I'm optimistic enough to 
think it will :)

Regards,
Andy

On Fri, Jun 21, 2013 at 2:27 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
I am trying to build 4.0.1 using the Superbuild on an Intel-build system.I 
have my compilers set to icc/icpc I'm failing deep down in the QT build 
with missing Intel libraries - and I believe that the reason for the failure is 
that somehow QT is trying to build with gcc/g++ rather than icc/icpc.  Is there 
any way to force the compiler selection down to QT?

cd src/corelib/ && make -f Makefile
make[1]: Entering directory 
`/usr/local/u/angel/PV/Build/qt/src/qt-build/src/corelib'
rm -f libQtCore.so.4.8.2 libQtCore.so libQtCore.so.4 libQtCore.so.4.8
g++ -L/usr/local/u/angel/PV/Build/install/lib -Wl,--no-undefined 
-Wl,-e,qt_core_boilerplate -Wl,-O1 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib 
-Wl,-rpath,/usr/local/u/angel/PV/Build/install/lib -shared 
-Wl,-soname,libQtCore.so.4 -o libQtCore.so.4.8.2 
.obj/release-shared/qabstractanimation.o .obj/


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

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

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

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

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



___
Powered by www.kitware.com

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

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

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

[Paraview] Superbuild: Passing VTK parameter?

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

I want to pass a VTK build parameter from the Superbuild down into the depths 
of the ParaView build.   In my top level cmake command, I'm passing the flag:

-DVTK_USE_OFFSCREEN:BOOL=ON \

but if I look in the paraview/src/*build/CMakeCache.txt file I'm getting this:

VTK_USE_OFFSCREEN:BOOL=OFF

Should I be able to pass this parameter from the top-level cmake command in the 
Superbuild?


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

[Paraview] CTH Reader generating lots of output (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

We're using ParaView 4.0.1 to read in some (large) CTH datasets, and the
reader is spewing gobs of output.  I think that they are warning messages,
but it may be  indicative of something going wrong under behind the curtain.

The message that we're seeing is:

Warning in:
./paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVProgress
Hander.cxx
Line 261:  vtkSpyPlotReader reported invalid progress [2.4]
Value must be between [0,1]
Clamping to this range

It seems as though the progress value is reporting a lot of values > 1!
8-)



Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] Re: Port number

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

I set them randomly in my host PVSC file:


  


  




Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Scott, W Alan [wasc...@sandia.gov]
Sent: Wednesday, July 31, 2013 12:58 PM
To: DeMarle, David Edward (External Contacts)
Cc: paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] Re: Port number

Thanks David!

Unfortunately, I am trying to automate the process, thus need to set the client 
side port number by command line or environment variable.  The user won’t even 
know the port number I am using.  Further, it may/will change every run.

Any idea how to set the client side port number through command line?

Alan

From: David E DeMarle [mailto:dave.dema...@kitware.com]
Sent: Tuesday, July 30, 2013 8:55 PM
To: Scott, W Alan
Cc: paraview@paraview.org
Subject: [EXTERNAL] Re: [Paraview] Port number

In the Edit Server Configuration dialog with a Client / Server (reverse 
connection) server type, enter the desired port number. The client will then 
wait on that port for the server to connect back to it.

Afterward start up pvserver with arguments of "-rc -sp=port#" to make it 
connect to the waiting client on the specified port number.

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

On Tue, Jul 30, 2013 at 7:47 PM, Scott, W Alan 
mailto:wasc...@sandia.gov>> wrote:
Is there a way to tell ParaView what port to use on the client side, as well as 
the server side, for reverse connect remote pvserver paraview?

Thanks,

Alan




___
Powered by www.kitware.com

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

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

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

___
Powered by www.kitware.com

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

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

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

[Paraview] CGNS Reader

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

I'm using the Superbuild to build ParaView 4.0.1  and I'm enabling CGNS but 
the reader doesn't seem to be there.   I can see that it downloaded at cgnslib 
tarball and it seems to have been built.I poked around on the Wiki and 
there's also a mention of using the VisIt bridge. Is the VisIt bridge 
(which I'm not using) the only way to read a CGNS file?




Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
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

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

Re: [Paraview] CGNS Reader

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

OK - maybe I'm taking this too literally.  Does the VisIt_Bridge actually link 
against the VisIt libraries?I built and compiled with the 
ENABLE_visitbridge turned on and I somehow ended up with a working CGNS reader. 
   But at no point did I specify any paths to my VisIt installation .   8-)



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of David E DeMarle [dave.dema...@kitware.com]
Sent: Wednesday, August 07, 2013 4:39 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] CGNS Reader

I think the only extra flag will be make sure boost is one of the projects 
superbuild makes. When superbuild makes paraview it will see this and then turn 
visitbridge on and link it in when it configures paraview.

Robert probably knows best the state of this particular file format.


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


On Wed, Aug 7, 2013 at 3:56 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
I was afraid you say that!   8-)

So, are there any additional parameters that need to be set, such as where the 
VisIt libraries are installed, etc?   In the Superbuild, I've looked in the 
CMakeCache.txt file, and I don't see any additional parameters for the bridge 
or for cgns.

Is this page still current and correct?   
http://www.paraview.org/Wiki/VisIt_Database_Bridge#CGNS_Support




Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: Utkarsh Ayachit 
[utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
Sent: Wednesday, August 07, 2013 3:25 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] CGNS Reader

Rick,

Correct, VisItBridge is required for CGNS support. You can turn on
VisItBridge by using the ENABLE_visitbridge cmake option.

Utkarsh

On Wed, Aug 7, 2013 at 3:05 PM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
> I'm using the Superbuild to build ParaView 4.0.1  and I'm enabling CGNS
> but the reader doesn't seem to be there.   I can see that it downloaded at
> cgnslib tarball and it seems to have been built.I poked around on the
> Wiki and there's also a mention of using the VisIt bridge. Is the VisIt
> bridge (which I'm not using) the only way to read a CGNS file?
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> Phone:  410-278-6266
>
> ___
> Powered by www.kitware.com<http://www.kitware.com>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com<http://www.kitware.com>

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

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

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

___
Powered by www.kitware.com

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

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

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

Re: [Paraview] CGNS Reader

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

OK - thanks!



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Robert Maynard [robert.mayn...@kitware.com]
Sent: Thursday, August 08, 2013 10:58 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] CGNS Reader

If you enable visitbridge without enabling cgns we won't build the visit cgns 
reader. This was done to allow people to selectively choose what readers that 
require extra external libraries they wish to build.


On Thu, Aug 8, 2013 at 10:53 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
So, is there any value in this flag:

-DENABLE_cgns=ON

if we're using the ENABLE_visitbridge flag?


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
[paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on behalf 
of Utkarsh Ayachit 
[utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
Sent: Thursday, August 08, 2013 10:23 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] CGNS Reader

Rick,

Yea, you don't need any separate build of VisIt, by turning on
ENABLE_visitbridge, ParaViewSuperbuild builds all the components
needed (including parts of VisIt). BTW, you don't neeed to ensure
ENABLE_boost is ON either (contrary to what Dave suggested). If
ENABLE_visitbridge is ON, ParaViewSuperbuid will automatically turn on
ENABLE_boost during its dependency determination pass.

Utkarsh

On Thu, Aug 8, 2013 at 8:13 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
> OK - maybe I'm taking this too literally.  Does the VisIt_Bridge actually
> link against the VisIt libraries?I built and compiled with the
> ENABLE_visitbridge turned on and I somehow ended up with a working CGNS
> reader.But at no point did I specify any paths to my VisIt installation
> .   8-)
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> Phone:  410-278-6266
> 
> From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
> [paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on
> behalf of David E DeMarle 
> [dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>]
> Sent: Wednesday, August 07, 2013 4:39 PM
>
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org<mailto:paraview@paraview.org>
> Subject: Re: [Paraview] CGNS Reader
>
> I think the only extra flag will be make sure boost is one of the projects
> superbuild makes. When superbuild makes paraview it will see this and then
> turn visitbridge on and link it in when it configures paraview.
>
> Robert probably knows best the state of this particular file format.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Wed, Aug 7, 2013 at 3:56 PM, Angelini, Richard C (Rick) CIV USARMY ARL
> (US) 
> mailto:richard.c.angelini@mail.mil>> 
> wrote:
>>
>> I was afraid you say that!   8-)
>>
>> So, are there any additional parameters that need to be set, such as where
>> the VisIt libraries are installed, etc?   In the Superbuild, I've looked in
>> the CMakeCache.txt file, and I don't see any additional parameters for the
>> bridge or for cgns.
>>
>> Is this page still current and correct?
>> http://www.paraview.org/Wiki/VisIt_Database_Bridge#CGNS_Support
>>
>>
>>
>> 
>> Rick Angelini
>>
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Building 120 Cube 315
>> Phone:  410-278-6266
>>
>> 
>> From: Utkarsh Ayachit 
>> [utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
>> Sent: Wednesday, August 07, 2013 3:25 PM
>> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
>> Cc: paraview@paraview.org<mailto:paraview@paraview.org>
>> Subject: Re: [Paraview] CGNS Reader
>>
>> Rick,
>>
>> Correct, VisItBridge is required for 

Re: [Paraview] CGNS Reader

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

So - if someone chooses to set the ENABLE_cgns flag (as I was doing) should the 
cmake rules automatically set the ENABLE_visitbridge flag? I was setting 
the CGNS and assuming (without actually testing) that I was getting the cgns 
reader.



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Robert Maynard [robert.mayn...@kitware.com]
Sent: Thursday, August 08, 2013 10:58 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] CGNS Reader

If you enable visitbridge without enabling cgns we won't build the visit cgns 
reader. This was done to allow people to selectively choose what readers that 
require extra external libraries they wish to build.


On Thu, Aug 8, 2013 at 10:53 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
So, is there any value in this flag:

-DENABLE_cgns=ON

if we're using the ENABLE_visitbridge flag?


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
[paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on behalf 
of Utkarsh Ayachit 
[utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
Sent: Thursday, August 08, 2013 10:23 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] CGNS Reader

Rick,

Yea, you don't need any separate build of VisIt, by turning on
ENABLE_visitbridge, ParaViewSuperbuild builds all the components
needed (including parts of VisIt). BTW, you don't neeed to ensure
ENABLE_boost is ON either (contrary to what Dave suggested). If
ENABLE_visitbridge is ON, ParaViewSuperbuid will automatically turn on
ENABLE_boost during its dependency determination pass.

Utkarsh

On Thu, Aug 8, 2013 at 8:13 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
> OK - maybe I'm taking this too literally.  Does the VisIt_Bridge actually
> link against the VisIt libraries?I built and compiled with the
> ENABLE_visitbridge turned on and I somehow ended up with a working CGNS
> reader.But at no point did I specify any paths to my VisIt installation
> .   8-)
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> Phone:  410-278-6266
> 
> From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
> [paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on
> behalf of David E DeMarle 
> [dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>]
> Sent: Wednesday, August 07, 2013 4:39 PM
>
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org<mailto:paraview@paraview.org>
> Subject: Re: [Paraview] CGNS Reader
>
> I think the only extra flag will be make sure boost is one of the projects
> superbuild makes. When superbuild makes paraview it will see this and then
> turn visitbridge on and link it in when it configures paraview.
>
> Robert probably knows best the state of this particular file format.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Wed, Aug 7, 2013 at 3:56 PM, Angelini, Richard C (Rick) CIV USARMY ARL
> (US) 
> mailto:richard.c.angelini@mail.mil>> 
> wrote:
>>
>> I was afraid you say that!   8-)
>>
>> So, are there any additional parameters that need to be set, such as where
>> the VisIt libraries are installed, etc?   In the Superbuild, I've looked in
>> the CMakeCache.txt file, and I don't see any additional parameters for the
>> bridge or for cgns.
>>
>> Is this page still current and correct?
>> http://www.paraview.org/Wiki/VisIt_Database_Bridge#CGNS_Support
>>
>>
>>
>> 
>> Rick Angelini
>>
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Building 120 Cube 315
>> Phone:  410-278-6266
>>
>> 
>> From: Utkarsh Ayachit 
>> [utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
>> Sent: Wednesday, August 07, 2013 3:25 PM
&g

Re: [Paraview] CGNS Reader

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

Fair enough   8-)



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: Moreland, Kenneth [kmo...@sandia.gov]
Sent: Thursday, August 08, 2013 12:57 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US); Robert Maynard
Cc: paraview@paraview.org
Subject: Re: [Paraview] CGNS Reader

I agree that CMake should do something when you turn on ENABLE_cgns.  I would 
advocate rather than blindly turning on ENABLE_visitbridge (which could have 
other consequences) that it instead outputs a warning explaining that 
ENABLE_cgns has no effect if ENABLE_visitbridge is off.

-Ken

From: , "Richard C CIV USARMY ARL (RickUS)" 
mailto:richard.c.angelini@mail.mil>>
Date: Thursday, August 8, 2013 9:10 AM
To: Robert Maynard 
mailto:robert.mayn...@kitware.com>>
Cc: "paraview@paraview.org<mailto:paraview@paraview.org>" 
mailto:paraview@paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] CGNS Reader

So - if someone chooses to set the ENABLE_cgns flag (as I was doing) should the 
cmake rules automatically set the ENABLE_visitbridge flag? I was setting 
the CGNS and assuming (without actually testing) that I was getting the cgns 
reader.



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
[paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on behalf 
of Robert Maynard 
[robert.mayn...@kitware.com<mailto:robert.mayn...@kitware.com>]
Sent: Thursday, August 08, 2013 10:58 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] CGNS Reader

If you enable visitbridge without enabling cgns we won't build the visit cgns 
reader. This was done to allow people to selectively choose what readers that 
require extra external libraries they wish to build.


On Thu, Aug 8, 2013 at 10:53 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
So, is there any value in this flag:

-DENABLE_cgns=ON

if we're using the ENABLE_visitbridge flag?


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
[paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on behalf 
of Utkarsh Ayachit 
[utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>]
Sent: Thursday, August 08, 2013 10:23 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org<mailto:paraview@paraview.org>
Subject: Re: [Paraview] CGNS Reader

Rick,

Yea, you don't need any separate build of VisIt, by turning on
ENABLE_visitbridge, ParaViewSuperbuild builds all the components
needed (including parts of VisIt). BTW, you don't neeed to ensure
ENABLE_boost is ON either (contrary to what Dave suggested). If
ENABLE_visitbridge is ON, ParaViewSuperbuid will automatically turn on
ENABLE_boost during its dependency determination pass.

Utkarsh

On Thu, Aug 8, 2013 at 8:13 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
> OK - maybe I'm taking this too literally.  Does the VisIt_Bridge actually
> link against the VisIt libraries?I built and compiled with the
> ENABLE_visitbridge turned on and I somehow ended up with a working CGNS
> reader.But at no point did I specify any paths to my VisIt installation
> .   8-)
>
>
>
> 
> Rick Angelini
>
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Building 120 Cube 315
> Phone:  410-278-6266
> 
> From: paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org> 
> [paraview-boun...@paraview.org<mailto:paraview-boun...@paraview.org>] on
> behalf of David E DeMarle 
> [dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>]
> Sent: Wednesday, August 07, 2013 4:39 PM
>
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org<mailto:paraview@paraview.org>
> Subject: Re: [Paraview] CGNS Reader
>
> I think the only extra flag will be make sure boost is one of the projects
> superbuild makes. When superbuild makes paraview it will see this and then
> turn visitbridge on and link it in when it configures paraview.
>
> Robert probably knows best the state of this particular file format.
>
>
> David E DeMarle
> Kitware, In

[Paraview] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'm having an issue with the extract CTH parts filter in ParaView 4.0.1.
The dataset consists of 1024 spcth files, regular structured mesh, 14
blocks.  The issue seems to be that once I exceed X number of server
processes (it seems to be about 80 servers), I start seeing holes in the
resulting geometry.  The more I exceed the magic number of servers, the more
holes I see in the resulting part.If I create a clip using the
volume_fraction scalar variable(s),  the geometry of the clip is correct -
that is, the underlying data seems to be there.   So, I'm thinking that the
data is being properly distributed and all of the data is accounted for, but
that there's an issue with the "extract CTH parts" filter?Doesn't seem
likely, but stranger things have happened.

Any ideas?

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Alan - yeah, the dataset opens correctly with < 80 servers.   It doesn't
matter how I distribute those 80 servers - I can do 16 processes on 5 nodes,
8 processes on 10 nodes and it works.   If I play the same game with > 80
nodes, I start seeing the holes.   I *doubt* that it's a bad node, but I'll
do some deeper investigating just to verify.   

-Original Message-
From: Scott, W Alan [mailto:wasc...@sandia.gov] 
Sent: Monday, August 26, 2013 3:43 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US); paraview@paraview.org
Subject: RE: [EXTERNAL] [Paraview] extract CTH parts (UNCLASSIFIED)

Bad node?

Try running the problem on a few nodes.  Next, try running the "big node"
problem.  As you shift the nodes you are using, does the issue follow the
underlying iron, or the same bad blocks in the dataset?

Dataset opens correctly with smaller number of nodes?

Want me to try it here?  80 does seem really, really small/easy/trivial for
big data...

Alan

-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Angelini, Richard C (Rick) CIV USARMY ARL (US)
Sent: Monday, August 26, 2013 1:38 PM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] extract CTH parts (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

I'm having an issue with the extract CTH parts filter in ParaView 4.0.1.
The dataset consists of 1024 spcth files, regular structured mesh, 14
blocks.  The issue seems to be that once I exceed X number of server
processes (it seems to be about 80 servers), I start seeing holes in the
resulting geometry.  The more I exceed the magic number of servers, the more
holes I see in the resulting part.If I create a clip using the
volume_fraction scalar variable(s),  the geometry of the clip is correct -
that is, the underlying data seems to be there.   So, I'm thinking that the
data is being properly distributed and all of the data is accounted for, but
that there's an issue with the "extract CTH parts" filter?Doesn't seem
likely, but stranger things have happened.

Any ideas?

Classification: UNCLASSIFIED
Caveats: NONE




Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

No, I'm not able to share either ... I'm going to try to find a similarly
sized dataset that might be more readily available.   Although, there's not
really an easy way to share a dataset with 1024 spcth files .

We are having an additional issue with this same dataset  loading the
dataset using less than 80 servers (so there are no holes in the geometry)
we are creating a simple animation.   There are several hundred timesteps of
data and we are able to interactively march through time and see the
animation.  However, when trying to save out a movie,   the frames suddenly
go blank.  We tried saving out as PNG files, and the first 22 timesteps
dumped fine, and then we started saving out solid black images.   We
restarted ParaView and started dumping out JPEG frames, and we got out to
timestep 100 and it again started dumping black frames. Interactively
viewing the data, all of the timesteps are valid -  is there a memory leak
or something similar that's causing the renderer to hose up?


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Tuesday, August 27, 2013 10:26 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: Scott, W Alan; paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

Rick,

Coincidentally, I am looking at the CTH parts class of filters right now.
Can you share the data or the images with the holes?

Utkarsh


On Mon, Aug 26, 2013 at 4:08 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:


Classification: UNCLASSIFIED
Caveats: NONE

Alan - yeah, the dataset opens correctly with < 80 servers.   It
doesn't
matter how I distribute those 80 servers - I can do 16 processes on
5 nodes,
8 processes on 10 nodes and it works.   If I play the same game with
> 80
nodes, I start seeing the holes.   I *doubt* that it's a bad node,
but I'll
do some deeper investigating just to verify.


-Original Message-
From: Scott, W Alan [mailto:wasc...@sandia.gov]
Sent: Monday, August 26, 2013 3:43 PM
    To: Angelini, Richard C (Rick) CIV USARMY ARL (US);
paraview@paraview.org
Subject: RE: [EXTERNAL] [Paraview] extract CTH parts (UNCLASSIFIED)

Bad node?

Try running the problem on a few nodes.  Next, try running the "big
node"
problem.  As you shift the nodes you are using, does the issue
follow the
underlying iron, or the same bad blocks in the dataset?

Dataset opens correctly with smaller number of nodes?

Want me to try it here?  80 does seem really, really
small/easy/trivial for
big data...

Alan

-Original Message-
From: paraview-boun...@paraview.org
[mailto:paraview-boun...@paraview.org]
    On Behalf Of Angelini, Richard C (Rick) CIV USARMY ARL (US)
Sent: Monday, August 26, 2013 1:38 PM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] extract CTH parts (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

I'm having an issue with the extract CTH parts filter in ParaView
4.0.1.
The dataset consists of 1024 spcth files, regular structured mesh,
14
blocks.  The issue seems to be that once I exceed X number of server
processes (it seems to be about 80 servers), I start seeing holes in
the
resulting geometry.  The more I exceed the magic number of servers,
the more
holes I see in the resulting part.If I create a clip using the
volume_fraction scalar variable(s),  the geometry of the clip is
correct -
that is, the underlying data seems to be there.   So, I'm thinking
that the
data is being properly distributed and all of the data is accounted
for, but
that there's an issue with the "extract CTH parts" filter?
Doesn't seem
likely, but stranger things have happened.

Any ideas?

Classification: UNCLASSIFIED
Caveats: NONE





Classification: UNCLASSIFIED
Caveats: NONE



___
Powered by www.kitware.com

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

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

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





Classification: UNCLASSIFIED
Caveats: NONE




smime.p7s
Description: S/MIME cryptographic signature
__

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Thanks for the suggestions  

-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Tuesday, August 27, 2013 10:44 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: Scott, W Alan; paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

> Interactively
> viewing the data, all of the timesteps are valid -  is there a memory 
> leak or something similar that's causing the renderer to hose up?

I'll try to do some profiling to see if I can reproduce this. In the mean
time, can you try turning off display lists, i.e. turn on "Use Immediate
Mode Rendering" from the Settings Dialog's "Render View"
page? If that doesn't help, also try turning off "Use Offscreen Rendering
for Screenshots" from the same dialog.

Utkarsh

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Terrific - thanks for the update.Very much appreciate the feedback.


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Tuesday, August 27, 2013 11:51 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: Scott, W Alan; paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

I was able to reproduce a hole with ExtractCTHParts filter using a dataset I
have. I'll dig deeper and keep you posted.

Utkarsh

On Tue, Aug 27, 2013 at 10:59 AM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Thanks for the suggestions 
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Tuesday, August 27, 2013 10:44 AM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: Scott, W Alan; paraview@paraview.org
> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>
>> Interactively
>> viewing the data, all of the timesteps are valid -  is there a memory 
>> leak or something similar that's causing the renderer to hose up?
>
> I'll try to do some profiling to see if I can reproduce this. In the 
> mean time, can you try turning off display lists, i.e. turn on "Use 
> Immediate Mode Rendering" from the Settings Dialog's "Render View"
> page? If that doesn't help, also try turning off "Use Offscreen 
> Rendering for Screenshots" from the same dialog.
>
> Utkarsh
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Sorry - can you give me some details about how to apply the patch?I can
apply this to 4.0.1?

Thanks

-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Utkarsh Ayachit
Sent: Wednesday, August 28, 2013 1:14 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

Rick/Alan,

Can you guys try the attached patch to see if the holes issue is fixed? I am
going to further cleanup the filter, but I want to make sure the holes were
indeed caused by this particular bug before I change more code.

Thanks
Utkarsh

On Tue, Aug 27, 2013 at 11:51 AM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Terrific - thanks for the update.Very much appreciate the feedback.
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Tuesday, August 27, 2013 11:51 AM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: Scott, W Alan; paraview@paraview.org
> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>
> I was able to reproduce a hole with ExtractCTHParts filter using a 
> dataset I have. I'll dig deeper and keep you posted.
>
> Utkarsh
>
> On Tue, Aug 27, 2013 at 10:59 AM, Angelini, Richard C (Rick) CIV 
> USARMY ARL
> (US)  wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Thanks for the suggestions 
>>
>> -Original Message-
>> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>> Sent: Tuesday, August 27, 2013 10:44 AM
>> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
>> Cc: Scott, W Alan; paraview@paraview.org
>> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>>
>>> Interactively
>>> viewing the data, all of the timesteps are valid -  is there a 
>>> memory leak or something similar that's causing the renderer to hose up?
>>
>> I'll try to do some profiling to see if I can reproduce this. In the 
>> mean time, can you try turning off display lists, i.e. turn on "Use 
>> Immediate Mode Rendering" from the Settings Dialog's "Render View"
>> page? If that doesn't help, also try turning off "Use Offscreen 
>> Rendering for Screenshots" from the same dialog.
>>
>> Utkarsh
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] Performance of the CGNS Reader

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

As a followup to this that may be related - does the CGNS reader through the 
VisItBridge work in parallel?I've loaded up a couple of different CGNS 
datasets and then applied the ProcessIDScalars filter and it doesn't appear to 
be distributing the data - even multi-block CGNS files.



Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266


From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf 
of Richard GRENON [richard.gre...@onera.fr]
Sent: Thursday, August 29, 2013 10:38 AM
To: paraview@paraview.org
Subject: [Paraview]  Performance of the CGNS Reader

Hello.

I am testing the CGNS reader of Paraview 4.0.1 64 bits running on a
Linux Workstation having 4 CPUs and 5.8 Gbytes of memory. Paraview was
installed from the binaries available on the download page.

I am trying to load a 1.36 Gbytes CGNS file that is available through
the network.

While loading this file, the Paraview Windows is frozen and cannot be
refreshed, and I must check with the "ps" command on a terminal window
or with a system monitor if PV  is still running or if it is really
frozen. A progress bar for all readers would be welcome in a next release.

Finally, the file can be loaded, but it always takes about 15 mn (+ or -
1 mn depending of the load of the network), while Tecplot always loads
the same file within less that 1 mn !

How do you explain this poor performance of the CGNS reader ? Can it be
improved, or am I missing something ? Is there some Paraview option that
could reduce loading time of large files ?

Best regards

--
  Richard GRENON
  ONERA
  Departement d'Aerodynamique Appliquee - DAAP/ACI
  8 rue des Vertugadins
  92190 MEUDON - FRANCE
  phone : +33 1 46 73 42 17
  fax   : +33 1 46 73 41 46
  mailto:richard.gre...@onera.fr
  http://www.onera.fr

___
Powered by www.kitware.com

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

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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
___
Powered by www.kitware.com

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

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

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

Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Utkarsh - I've not yet had a chance to test the patch.  A number of
misfortunes have my compile machine temporarily down and for some reason I'm
unable to get a clean build on a similar machine.   I'm working towards
being able to test your patch - but just not there yet.   I don't want you
to think that I'm ignoring your effort!


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Utkarsh Ayachit
Sent: Wednesday, August 28, 2013 1:33 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)

Yes, you can apply it to 4.0.1. Do the following:

> cd ParaViewSource/VTK
> git apply [path to path file]

If you're building using source tar balls and not git, you can do the
following:

> cd ParaViewSource/VTK
> patch -p1 < [path to patch file]

Utkarsh


On Wed, Aug 28, 2013 at 1:17 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Sorry - can you give me some details about how to apply the patch?I
can
> apply this to 4.0.1?
>
> Thanks
>
> -Original Message-
> From: paraview-boun...@paraview.org 
> [mailto:paraview-boun...@paraview.org]
> On Behalf Of Utkarsh Ayachit
> Sent: Wednesday, August 28, 2013 1:14 PM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>
> Rick/Alan,
>
> Can you guys try the attached patch to see if the holes issue is 
> fixed? I am going to further cleanup the filter, but I want to make 
> sure the holes were indeed caused by this particular bug before I change
more code.
>
> Thanks
> Utkarsh
>
> On Tue, Aug 27, 2013 at 11:51 AM, Angelini, Richard C (Rick) CIV 
> USARMY ARL
> (US)  wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Terrific - thanks for the update.Very much appreciate the feedback.
>>
>>
>> -----Original Message-
>> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>> Sent: Tuesday, August 27, 2013 11:51 AM
>> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
>> Cc: Scott, W Alan; paraview@paraview.org
>> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>>
>> I was able to reproduce a hole with ExtractCTHParts filter using a 
>> dataset I have. I'll dig deeper and keep you posted.
>>
>> Utkarsh
>>
>> On Tue, Aug 27, 2013 at 10:59 AM, Angelini, Richard C (Rick) CIV 
>> USARMY ARL
>> (US)  wrote:
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> Thanks for the suggestions 
>>>
>>> -Original Message-
>>> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>>> Sent: Tuesday, August 27, 2013 10:44 AM
>>> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
>>> Cc: Scott, W Alan; paraview@paraview.org
>>> Subject: Re: [Paraview] [EXTERNAL] extract CTH parts (UNCLASSIFIED)
>>>
>>>> Interactively
>>>> viewing the data, all of the timesteps are valid -  is there a 
>>>> memory leak or something similar that's causing the renderer to hose
up?
>>>
>>> I'll try to do some profiling to see if I can reproduce this. In the 
>>> mean time, can you try turning off display lists, i.e. turn on "Use 
>>> Immediate Mode Rendering" from the Settings Dialog's "Render View"
>>> page? If that doesn't help, also try turning off "Use Offscreen 
>>> Rendering for Screenshots" from the same dialog.
>>>
>>> Utkarsh
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
___
Powered by www.kitware.com

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

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

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

Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] ParaView 4.0.1 Opacity performance (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I am working on a CTH dataset with 1024 spcth files.I'm able to extract
8 CTH parts using the "CTH Extract Parts" filter and things work reasonably
well.  In client-server mode, I'm able to interact with the data, rotate,
translate, scale, etc without any noticeable performance issues.   By
default, I have distributed rendering enabled and the interactive
performance is good.

However, if I enable opacity on any of those CTH parts that I extract,
interactive performance drops to the point of being unusable. Once
enabled, it takes about 10 minutes for ParaView to update the GL window.
I've tried diddling with the render window settings - such totally disabling
distributed rendering, but it doesn't seem to make any difference on the
performance with opacity.

I've also saved out animations of this dataset and use the "disconnect"
feature.Without opacity enabled, I can march through time at something
slightly less than 1 timestep/minute running in disconnected batch mode.
With opacity enabled on any one of the parts,  it takes ~10
minutes/timestep.   

On the server side, I have paraview 4.0.1 built with the OSMesa library
that's downloaded as part of the superbuild.I'm assuming that opacity
should not totally destroy performance as we're seeing. There are other
packages that we use in client-server mode with opacity that show no
noticeable performance degradation when using opacity.  

Thanks


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

Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] default_servers.pvsc file for Windows (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'm trying to create a pvsc file that'll work on Windows and I'm having
trouble creating the path for the plink executable.


If I set the path via the GUI,  I need to put quotes around the pathname and
in the GUI it looks like this:

"C:\Program Files\KRB5\PuTTy\plink.exe"

And this works and makes the remote connect as long as I put the double
quotes around the pathname.

I can't figure out how to set up the quoted path in the default_servers.pvsc
file.   Using this syntax, I get XML parsing errors.




  

 


I've also tried setting the string to this, but neither worked.  It
apparently doesn't like the  \" to force the inclusion of the quote
character in the string.




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



Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] default_servers.pvsc file for Windows (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Yep - also just found the use " as the solution - thanks!



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


-Original Message-
From: Andy Bauer [mailto:andy.ba...@kitware.com] 
Sent: Friday, October 11, 2013 11:43 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] default_servers.pvsc file for Windows (UNCLASSIFIED)

Hi Rick,

The attached pvsc file should have the proper syntax for using plink on
windows. You'll need to fill in the stuff I cleaned out.

Regards,
Andy





On Fri, Oct 11, 2013 at 11:30 AM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:


Classification: UNCLASSIFIED
Caveats: NONE

I'm trying to create a pvsc file that'll work on Windows and I'm
having
trouble creating the path for the plink executable.


If I set the path via the GUI,  I need to put quotes around the
pathname and
in the GUI it looks like this:

"C:\Program Files\KRB5\PuTTy\plink.exe"

And this works and makes the remote connect as long as I put the
double
quotes around the pathname.

I can't figure out how to set up the quoted path in the
default_servers.pvsc
file.   Using this syntax, I get XML parsing errors.




  

 


I've also tried setting the string to this, but neither worked.  It
apparently doesn't like the  \" to force the inclusion of the quote
character in the string.




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



Classification: UNCLASSIFIED
Caveats: NONE



___
Powered by www.kitware.com

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

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

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





Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] paraview superbuild on standalone system - how to, get the sources ? (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

You can download all of the dependency library tarballs from:

http://paraview.org/files/v4.0/dependencies


Your cmake in the Superbuild would then point to a downloads directory:

EXAMPLE:
ccmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/paraview \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v4.0.1-source.tgz \
-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 \
-DENABLE_visitbridge:BOOL=ON \
-DUSE_SYSTEM_mpi=OFF ../Source



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


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Thomas
Sent: Sunday, October 13, 2013 11:36 AM
To: paraview@paraview.org
Subject: Re: [Paraview] paraview superbuild on standalone system - how to,
get the sources ?

Hi Benson,
I have already tried the precompiled binaries - they work O.K. but I am not
able to use paraview as intended - parallel.
I guess I have to build it on my system and link the correct mpi libraries.
I cannot build the superbuild on the chosen architecture - it has no
internet connection so I cannot use git.
So I have to download all the sources I need (qt, python...) on another
machine and then transfer to the target system and build there.
That is my problem - I basically need to know if I can use git to donwload
"everything" and then compile offline somwhere else.
Cheers,
thomas




Am 12.10.2013 11:20, schrieb Benson Muite:
> Hi Thomas,
>
> May want to try downloading a precompiled binary for the architecture
> you are considering:
> http://paraview.org/paraview/resources/software.php
>
> This will only give serial code, but is a first step. Next step would be
> to use superbuild on the computer with an internet connection to try and
> generate a binary for your chosen architecture. Some introductory
> information here:
> http://www.paraview.org/Wiki/ParaView:Superbuild
>
> Benson
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
> -
> E-Mail ist virenfrei.
> Von AVG uberpruft - www.avg.de
> Version: 2012.0.2242 / Virendatenbank: 3222/6246 - Ausgabedatum:
13.10.2013
>
>

___
Powered by www.kitware.com

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

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

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

Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I've built 4.1.0 on a couple of our HPC systems and I'm getting a clean
build, but fails on execution of parallel servers.   On both systems (an SGI
Altix/ICE and an IBM iDataPlex) I'm using gcc and openmpi  and the same
exact build environment that I used to build 4.0.1.   However, both systems
are failing with identical errors that begins with a "Leave Pinned" mpi
feature which is a flag set in our mpirun command environment and works with
4.0.1. Did something change behind that scenes in ParaView 4.1.0 that
impacts the build or runtime parameters?



orterun -x MODULE_VERSION_STACK -x MANPATH -x MPI_VER -x HOSTNAME -x
_MODULESBEGINENV_ -x PBS_ACCOUNT -x HOST -x SHELL -x TMPDIR -x PBS_JOBNAME
-x PBS_ENVIRONMENT -x PBS_O_WORKDIR -x NCPUS -x DAAC_HOME -x GROUP -x
PBS_TASKNUM -x USER -x LD_LIBRARY_PATH -x LS_COLORS -x PBS_O_HOME -x
COMPILER_VER -x HOSTTYPE -x PBS_MOMPORT -x PV_ROOT -x PBS_O_QUEUE -x NLSPATH
-x MODULE_VERSION -x MAIL -x PBS_O_LOGNAME -x PATH -x PBS_O_LANG -x
PBS_JOBCOOKIE -x F90 -x PWD -x _LMFILES_ -x PBS_NODENUM -x LANG -x
MODULEPATH -x LOADEDMODULES -x PBS_JOBDIR -x F77 -x PBS_O_SHELL -x PBS_JOBID
-x MPICC_F77 -x CXX -x ENVIRONMENT -x SHLVL -x HOME -x OSTYPE -x PBS_O_HOST
-x MPIHOME -x FC -x VENDOR -x MACHTYPE -x LOGNAME -x MPICC_CXX -x PBS_QUEUE
-x MPI_HOME -x MODULESHOME -x COMPILER -x LESSOPEN -x OMP_NUM_THREADS -x
PBS_O_MAIL -x CC -x PBS_O_SYSTEM -x MPICC_F90 -x G_BROKEN_FILENAMES -x
PBS_NODEFILE -x MPICC_CC -x PBS_O_PATH -x module -x } -x premode -x premod
-x PBS_HOME -x PBS_GET_IBWINS -x NUM_MPITASKS -np 3 -machinefile
new.1133.machines.txt --prefix
/usr/cta/unsupported/openmpi/gcc/4.4.0/openmpi-1.6.3 -mca orte_rsh_agent ssh
-mca mpi_paffinity_alone 1 -mca maffinity first_use -mca mpi_leave_pinned 1
-mca btl openib,self -mca orte_default_hostname new.1133.machines.txt
pvserver --use-offscreen-rendering --server-port=50481
--client-host=localhost --reverse-connection --timeout=15 --connect-id=30526
[pershing-n0221:01190] Warning: could not find environment variable "}"
--
A process attempted to use the "leave pinned" MPI feature, but no
memory registration hooks were found on the system at run time.  This
may be the result of running on a system that does not support memory
hooks or having some other software subvert Open MPI's use of the
memory hooks.  You can disable Open MPI's use of memory hooks by
setting both the mpi_leave_pinned and mpi_leave_pinned_pipeline MCA
parameters to 0.

Open MPI will disable any transports that are attempting to use the
leave pinned functionality; your job may still run, but may fall back
to a slower network transport (such as TCP).

  Mpool name: rdma
  Process:[[43622,1],0]
  Local host: xxx-n0221
--
--
WARNING: There is at least one OpenFabrics device found but there are
no active ports detected (or Open MPI was unable to use them).  This
is most certainly not what you wanted.  Check your cables, subnet
manager configuration, etc.  The openib BTL will be ignored for this
job.

  Local host: xxx-n0221
--
--
At least one pair of MPI processes are unable to reach each other for
MPI communications.  This means that no Open MPI device has indicated
that it can be used to communicate between these processes.  This is
an error; Open MPI requires that all MPI processes be able to reach
each other.  This error can sometimes be the result of forgetting to
specify the "self" BTL.

  Process 1 ([[43622,1],2]) is on host: xxx-n0221
  Process 2 ([[43622,1],0]) is on host: xxx-n0221
  BTLs attempted: self

Your MPI job is now going to abort; sorry.
--
--
MPI_INIT has failed because at least one MPI process is unreachable
from another.  This *usually* means that an underlying communication
plugin -- such as a BTL or an MTL -- has either not loaded or not
allowed itself to be used.  Your MPI job will now abort.

You may wish to try to narrow down the problem;

 * Check the output of ompi_info to see which BTL/MTL plugins are
   available.
 * Run your application with MPI_THREAD_SINGLE.
 * Set the MCA parameter btl_base_verbose to 100 (or mtl_base_verbose,
   if using MTL-based communications) to see exactly which
   communication plugins were considered and/or discarded.
--
[pershing-n0221:1198] *** An error occurred in MPI_Init
[pershing-n0221:1198] *** on a NULL communicator
[pershing-n0221:1198] *** Unknown error
[pershing-n0221:1198] *** MPI_ERRORS_

Re: [Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I've been able to narrow down the problem to a flag that's being passed
through to the mpirun command (we have a wrapper script called
openmpirun.pbs that's used in place of mpirun). ParaView 4.0.1 works
perfectly fine with the openmpirun.pbs wrapper script, but 4.1.0 fails with
this script.If I diddle a flag that's being set in the script I can get
4.1.0 to work with the wrapper script. Specifically, if I change the flag
"-mca mpi_leave_pinned 1" to "-mca mpi_leave_pinned 0" in the openmpirun.pbs
script, then ParaView 4.1.0 works.

So, this is outside of my area of expertise.  Given that I compiled 4.0.1
and 4.1.0 with a (presumably) identical environment, what would bring this
runtime flag into play with version 4.1.0?   I also used the same cmake for
both builds, so hopefully cmake collected the same compile flags for both
versions.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Angelini, Richard C (Rick) CIV USARMY ARL (US)
Sent: Wednesday, December 04, 2013 11:14 AM
To: Utkarsh Ayachit
Cc: paraview@paraview.org
Subject: Re: [Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

I'm seeing those errors with both client-server parallel pvserver and with
pvbatch.I'm going to throw this over to our systems people to see if
they have any ideas.   But, I'm suspicious that is a ParaView thing since it
happens on two different machines, two different compute platforms.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Utkarsh Ayachit
Sent: Tuesday, December 03, 2013 10:07 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

I can't think of anything in particular that changed that could affect this.
Are you trying this with pvserver? Can you try pvbatch? Same problem?

On Tue, Dec 3, 2013 at 12:44 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I've built 4.1.0 on a couple of our HPC systems and I'm getting a clean
> build, but fails on execution of parallel servers.   On both systems (an
SGI
> Altix/ICE and an IBM iDataPlex) I'm using gcc and openmpi  and the same
> exact build environment that I used to build 4.0.1.   However, both
systems
> are failing with identical errors that begins with a "Leave Pinned" 
> mpi feature which is a flag set in our mpirun command environment and 
> works with 4.0.1. Did something change behind that scenes in ParaView 
> 4.1.0 that impacts the build or runtime parameters?
>
>
>
> orterun -x MODULE_VERSION_STACK -x MANPATH -x MPI_VER -x HOSTNAME -x 
> _MODULESBEGINENV_ -x PBS_ACCOUNT -x HOST -x SHELL -x TMPDIR -x 
> PBS_JOBNAME -x PBS_ENVIRONMENT -x PBS_O_WORKDIR -x NCPUS -x DAAC_HOME 
> -x GROUP -x PBS_TASKNUM -x USER -x LD_LIBRARY_PATH -x LS_COLORS -x 
> PBS_O_HOME -x COMPILER_VER -x HOSTTYPE -x PBS_MOMPORT -x PV_ROOT -x 
> PBS_O_QUEUE -x NLSPATH -x MODULE_VERSION -x MAIL -x PBS_O_LOGNAME -x 
> PATH -x PBS_O_LANG -x PBS_JOBCOOKIE -x F90 -x PWD -x _LMFILES_ -x 
> PBS_NODENUM -x LANG -x MODULEPATH -x LOADEDMODULES -x PBS_JOBDIR -x 
> F77 -x PBS_O_SHELL -x PBS_JOBID -x MPICC_F77 -x CXX -x ENVIRONMENT -x 
> SHLVL -x HOME -x OSTYPE -x PBS_O_HOST -x MPIHOME -x FC -x VENDOR -x 
> MACHTYPE -x LOGNAME -x MPICC_CXX -x PBS_QUEUE -x MPI_HOME -x 
> MODULESHOME -x COMPILER -x LESSOPEN -x OMP_NUM_THREADS -x PBS_O_MAIL 
> -x CC -x PBS_O_SYSTEM -x MPICC_F90 -x G_BROKEN_FILENAMES -x 
> PBS_NODEFILE -x MPICC_CC -x PBS_O_PATH -x module -x } -x premode -x 
> premod -x PBS_HOME -x PBS_GET_IBWINS -x NUM_MPITASKS -np 3 
> -machinefile new.1133.machines.txt --prefix
> /usr/cta/unsupported/openmpi/gcc/4.4.0/openmpi-1.6.3 -mca 
> orte_rsh_agent ssh -mca mpi_paffinity_alone 1 -mca maffinity first_use 
> -mca mpi_leave_pinned 1 -mca btl openib,self -mca 
> orte_default_hostname new.1133.machines.txt pvserver 
> --use-offscreen-rendering --server-port=50481 --client-host=localhost 
> --reverse-connection --timeout=15 --connect-id=30526
[pershing-n0221:01190] Warning: could not find environment variable "}"
> --
>  A process attempted to use the "leave pinned" MPI feature, bu

Re: [Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'm seeing those errors with both client-server parallel pvserver and with
pvbatch.I'm going to throw this over to our systems people to see if
they have any ideas.   But, I'm suspicious that is a ParaView thing since it
happens on two different machines, two different compute platforms.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Utkarsh Ayachit
Sent: Tuesday, December 03, 2013 10:07 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] 4.1.0 release candidate build (UNCLASSIFIED)

I can't think of anything in particular that changed that could affect this.
Are you trying this with pvserver? Can you try pvbatch? Same problem?

On Tue, Dec 3, 2013 at 12:44 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I've built 4.1.0 on a couple of our HPC systems and I'm getting a clean
> build, but fails on execution of parallel servers.   On both systems (an
SGI
> Altix/ICE and an IBM iDataPlex) I'm using gcc and openmpi  and the same
> exact build environment that I used to build 4.0.1.   However, both
systems
> are failing with identical errors that begins with a "Leave Pinned" 
> mpi feature which is a flag set in our mpirun command environment and 
> works with 4.0.1. Did something change behind that scenes in ParaView 
> 4.1.0 that impacts the build or runtime parameters?
>
>
>
> orterun -x MODULE_VERSION_STACK -x MANPATH -x MPI_VER -x HOSTNAME -x 
> _MODULESBEGINENV_ -x PBS_ACCOUNT -x HOST -x SHELL -x TMPDIR -x 
> PBS_JOBNAME -x PBS_ENVIRONMENT -x PBS_O_WORKDIR -x NCPUS -x DAAC_HOME 
> -x GROUP -x PBS_TASKNUM -x USER -x LD_LIBRARY_PATH -x LS_COLORS -x 
> PBS_O_HOME -x COMPILER_VER -x HOSTTYPE -x PBS_MOMPORT -x PV_ROOT -x 
> PBS_O_QUEUE -x NLSPATH -x MODULE_VERSION -x MAIL -x PBS_O_LOGNAME -x 
> PATH -x PBS_O_LANG -x PBS_JOBCOOKIE -x F90 -x PWD -x _LMFILES_ -x 
> PBS_NODENUM -x LANG -x MODULEPATH -x LOADEDMODULES -x PBS_JOBDIR -x 
> F77 -x PBS_O_SHELL -x PBS_JOBID -x MPICC_F77 -x CXX -x ENVIRONMENT -x 
> SHLVL -x HOME -x OSTYPE -x PBS_O_HOST -x MPIHOME -x FC -x VENDOR -x 
> MACHTYPE -x LOGNAME -x MPICC_CXX -x PBS_QUEUE -x MPI_HOME -x 
> MODULESHOME -x COMPILER -x LESSOPEN -x OMP_NUM_THREADS -x PBS_O_MAIL 
> -x CC -x PBS_O_SYSTEM -x MPICC_F90 -x G_BROKEN_FILENAMES -x 
> PBS_NODEFILE -x MPICC_CC -x PBS_O_PATH -x module -x } -x premode -x 
> premod -x PBS_HOME -x PBS_GET_IBWINS -x NUM_MPITASKS -np 3 
> -machinefile new.1133.machines.txt --prefix
> /usr/cta/unsupported/openmpi/gcc/4.4.0/openmpi-1.6.3 -mca 
> orte_rsh_agent ssh -mca mpi_paffinity_alone 1 -mca maffinity first_use 
> -mca mpi_leave_pinned 1 -mca btl openib,self -mca 
> orte_default_hostname new.1133.machines.txt pvserver 
> --use-offscreen-rendering --server-port=50481 --client-host=localhost 
> --reverse-connection --timeout=15 --connect-id=30526
[pershing-n0221:01190] Warning: could not find environment variable "}"
> --
>  A process attempted to use the "leave pinned" MPI feature, but no 
> memory registration hooks were found on the system at run time.  This 
> may be the result of running on a system that does not support memory 
> hooks or having some other software subvert Open MPI's use of the 
> memory hooks.  You can disable Open MPI's use of memory hooks by 
> setting both the mpi_leave_pinned and mpi_leave_pinned_pipeline MCA 
> parameters to 0.
>
> Open MPI will disable any transports that are attempting to use the 
> leave pinned functionality; your job may still run, but may fall back 
> to a slower network transport (such as TCP).
>
>   Mpool name: rdma
>   Process:[[43622,1],0]
>   Local host: xxx-n0221
> --
> 
> --
> 
> WARNING: There is at least one OpenFabrics device found but there are 
> no active ports detected (or Open MPI was unable to use them).  This 
> is most certainly not what you wanted.  Check your cables, subnet 
> manager configuration, etc.  The openib BTL will be ignored for this 
> job.
>
>   Local host: xxx-n0221
> --
> 
> --
>  At least one pair of MPI processes are unable to reach ea

Re: [Paraview] how do I do this? (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I wonder if this might be accomplished using a ParaView "surface flow":

http://www.cfd-online.com/Forums/openfoam-paraview/98726-surface-path-oilflo
w-paraview.html


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Ryan Abernathey
Sent: Thursday, December 19, 2013 3:53 PM
To: paraview
Subject: [Paraview] how do I do this?

I have vector velocity data from a CFD simulation, and I would like to
visualize the flow like this:
http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.
73,5.54,350


Is there any way I can do this with paraview?

Thanks,
Ryan

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] paraview 4.1 cmake error (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE


Dave - did you start with a clean build directory?   Cmake changed between
4.0 and 4.1 and any cmake cache files laying around confuse things 



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org]
On Behalf Of Utkarsh Ayachit
Sent: Wednesday, January 08, 2014 9:06 AM
To: Semeraro, B David
Cc: paraview@paraview.org
Subject: Re: [Paraview] paraview 4.1 cmake error

That is weird. I don't see any reference to MPI_HEADER_PATH in the ParaView
source. What version of CMake are you using? Mind attaching your
CMakeCache.txt from the build directory?

Thanks
Utkarsh


On Tue, Jan 7, 2014 at 2:48 PM, Semeraro, B David 
wrote:


Hello,

 

I am trying to configure paraview 4.1. I get the following cmake
error:

 

CMake Error: The following variables are used in this project, but
they are

set to NOTFOUND.

Please set them or make sure they are set and tested correctly in
the CMake

files:

MPI_HEADER_PATH

used as include directory in directory


/u/staff/semeraro/Paraview/ParaView-v4.1.0-RC2/Plugins/SciberQuestToolKit/Pa
ra

ViewPlugin

 

There is no MPI_HEADER_PATH in the list of variables when I use
ccmake. How do I set MPI_HEADER_PATH in that case? 

 

Regards,

Dave Semeraro


___
Powered by www.kitware.com

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

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

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





Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] ParaView 4.1.0 (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'm seeing some weirdness with the color map editor.   If I choose the color
map editor option, a separate window pops up as expected.  But when I move
my cursor from the main window over to the color map pop-up window, the
color map window disappears.  If I move my cursor back to the main window,
the color map pop-up reappears.   If I drag the main GUI window over to so
that the edges of the main GUI window and the color map popup window are
touching, then the color map editor window does not disappear.   

I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system running KDE
3.5.4.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh
Ayachit
Sent: Monday, January 13, 2014 12:25 PM
To: ParaView
Cc: ParaView Developers
Subject: [Paraview] ANN: ParaView 4.1.0 is available for download

Folks,




ParaView 4.1.0 is now available for download
(http://paraview.org/paraview/resources/software.php
 ). With over 170
issues resolved, this release includes several bug fixes and feature
enhancements. For a detailed list of issues resolved, refer to the change
log (http://paraview.org/Bug/changelog_page.php
 ).  Some of the notable
enhancements in this release are as follows:


Redesigned Color Map Editor panel

This release introduces a completely designed panel for editing color and
opacity transfer functions for scalar coloring. The panel, which is now a
dockable widget, instead of a popup dialog, makes it easier to edit transfer
functions as well as edit labels and annotations on the color legend or
scalar bar. This also makes it easier to access some of the functionality
introduced in the previous version of ParaView, such as categorical colors.
It is now easier to edit transfer functions when using log scaling as the
transfer function editor view now switches to log space.


 
 





Enhancements to Find Data dialog

Find Data dialog, introduced several versions ago, has quickly become of the
main mechanisms for creating new selections. However, until now, if the user
created selection using some other mechanism, such as selecting cells in the
3D view, the Find Data dialog could not be used to inspect that selection.
One had to use what was called the Selection Inspector. That has now been
changed. Find Data dialog has been updated to always show the active
selection, no matter how it was created.


Selection Inspector panel has been removed. Selection Inspector was
primarily used to control how selections are labelled, their font
properties, etc. One can affect these directly from the Find Data dialog or
the new Selection Display Inspector which is dockable panel specially
designed for picking selection labels, label properties, or showing the
selection frustum for frustum based selections.


 
 





Enhancements for interactions with Plots

Inspired by plots in matplotlib, individual axes in line and bar charts can
now be zoomed by right-clicking and dragging along the x- or y- axis. Of
course, one can still drag diagonally to scale both axes as before. Also the
the user interactions for making new selections in line chart view have been
cleaned up to be more consistent with the render view.


Support for Python-based views

This release adds mechanisms to enable Python developers to integrate views
that use libraries such as matplotlib for rendering. This will make it
possible to take ParaView's charting capabilities even further. More details
on how to create such views can be found on Kitware blog
(http://www.kitware.com/blog/home/post/588
 ).


ParaView Catalyst: Zero-Copy infrastructure for transferring data

A set of experimental interfaces have been added for reusing simulation
memory in portions of a Catalyst pipeline. A vtkMappedDataArray subclass may
be used for attribute/coordinate arrays, and vtkMappedUnstructuredGrid is
used for dataset topologies. More information can be found at
http://www.paraview.org/Wiki/CoProcessing#Experimental:_Reusing_simulation_m
emory
 .


ParaView Catalyst: Editions

Several new editions of ParaView Catalyst are now available for download and
are routinely built and tested. These editions are:


Base

minimal set of dependencies needed for Catalyst

Base-Python

B

Re: [Paraview] ParaView 4.1.0 (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

If I run with the "-dr" flag, the color map window shows up inside of the
main GUI (on the right hand side of the GL window) and works correctly.   If
I drag the color map editor tool outside of the main gui,  I get the same
behavior of the window disappearing if the cursor is outside of the main GL
window.




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Tuesday, January 14, 2014 1:26 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: ParaView
Subject: Re: ParaView 4.1.0 (UNCLASSIFIED)

Rick,

Can you try running ParaView with "-dr" command line option and see if the
problem persists?

Utkarsh


On Tue, Jan 14, 2014 at 12:31 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:


Classification: UNCLASSIFIED
Caveats: NONE

I'm seeing some weirdness with the color map editor.   If I choose
the color
map editor option, a separate window pops up as expected.  But when
I move
my cursor from the main window over to the color map pop-up window,
the
color map window disappears.  If I move my cursor back to the main
window,
the color map pop-up reappears.   If I drag the main GUI window over
to so
that the edges of the main GUI window and the color map popup window
are
touching, then the color map editor window does not disappear.

I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system
running KDE
3.5.4.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD
Phone:  410-278-6266


-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of
Utkarsh
Ayachit
Sent: Monday, January 13, 2014 12:25 PM
To: ParaView
Cc: ParaView Developers
Subject: [Paraview] ANN: ParaView 4.1.0 is available for download

Folks,




ParaView 4.1.0 is now available for download
(http://paraview.org/paraview/resources/software.php
<http://paraview.org/paraview/resources/software.php> ). With over
170
issues resolved, this release includes several bug fixes and feature
enhancements. For a detailed list of issues resolved, refer to the
change
log (http://paraview.org/Bug/changelog_page.php
<http://paraview.org/Bug/changelog_page.php> ).  Some of the notable
enhancements in this release are as follows:


Redesigned Color Map Editor panel

This release introduces a completely designed panel for editing
color and
opacity transfer functions for scalar coloring. The panel, which is
now a
dockable widget, instead of a popup dialog, makes it easier to edit
transfer
functions as well as edit labels and annotations on the color legend
or
scalar bar. This also makes it easier to access some of the
functionality
introduced in the previous version of ParaView, such as categorical
colors.
It is now easier to edit transfer functions when using log scaling
as the
transfer function editor view now switches to log space.




<https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c

GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR
<https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c
GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR
> 
p_acg>





Enhancements to Find Data dialog

Find Data dialog, introduced several versions ago, has quickly
become of the
main mechanisms for creating new selections. However, until now, if
the user
created selection using some other mechanism, such as selecting
cells in the
3D view, the Find Data dialog could not be used to inspect that
selection.
One had to use what was called the Selection Inspector. That has now
been
changed. Find Data dialog has been updated to always show the active
selection, no matter how it was created.


Selection Inspector panel has been removed. Selection Inspector was
primarily used to control how selections are labelled, their font
properties, etc. One can affect these directly from the Find Data
dialog or
the new Selection Display Inspector which is dockable panel
specially
desig

Re: [Paraview] ParaView 4.1.0 (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I have verified that the issue is specific to KDE ... If I run the GNOME
window manager on the same workstation,  the pop-up behaves correctly.
Curiously, the behavior only impacts the color map editor.   Other pop-up
windows (file select, python window, connection window, etc) all behave
correctly using KDE.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Sent: Tuesday, January 14, 2014 1:57 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: ParaView
Subject: Re: ParaView 4.1.0 (UNCLASSIFIED)

I suspect that has something to do with KDE/X Windowing system. I wonder if
anyone else on this list has seen this problem.

Utkarsh


On Tue, Jan 14, 2014 at 1:53 PM, Angelini, Richard C (Rick) CIV USARMY ARL
(US)  wrote:


Classification: UNCLASSIFIED
Caveats: NONE

If I run with the "-dr" flag, the color map window shows up inside
of the
main GUI (on the right hand side of the GL window) and works
correctly.   If
I drag the color map editor tool outside of the main gui,  I get the
same
behavior of the window disappearing if the cursor is outside of the
main GL
window.





Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD
Phone:  410-278-6266


-Original Message-

From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Tuesday, January 14, 2014 1:26 PM
    To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: ParaView
Subject: Re: ParaView 4.1.0 (UNCLASSIFIED)

Rick,

Can you try running ParaView with "-dr" command line option and see
if the
problem persists?

Utkarsh


On Tue, Jan 14, 2014 at 12:31 PM, Angelini, Richard C (Rick) CIV
USARMY ARL
(US)  wrote:


Classification: UNCLASSIFIED
Caveats: NONE

I'm seeing some weirdness with the color map editor.   If I
choose
the color
map editor option, a separate window pops up as expected.
But when
I move
my cursor from the main window over to the color map pop-up
window,
the
color map window disappears.  If I move my cursor back to
the main
window,
the color map pop-up reappears.   If I drag the main GUI
window over
to so
that the edges of the main GUI window and the color map
popup window
are
touching, then the color map editor window does not
disappear.

I'm using the Linux_64 prebuilt binary on a RHEL5 Linux
system
running KDE
3.5.4.


Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD
Phone:  410-278-6266


-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On
Behalf Of
Utkarsh
Ayachit
Sent: Monday, January 13, 2014 12:25 PM
To: ParaView
Cc: ParaView Developers
Subject: [Paraview] ANN: ParaView 4.1.0 is available for
download

Folks,




ParaView 4.1.0 is now available for download
(http://paraview.org/paraview/resources/software.php
<http://paraview.org/paraview/resources/software.php> ).
With over
170
issues resolved, this release includes several bug fixes and
feature
enhancements. For a detailed list of issues resolved, refer
to the
change
log (http://paraview.org/Bug/changelog_page.php
<http://paraview.org/Bug/changelog_page.php> ).  Some of the
notable
enhancements in this release are as follows:


Redesigned Color Map Editor panel

This release introduces a completely designed panel for
editing
color and
opacity transfer functions for scalar coloring. The panel,
which is
now a
dockable widget, instead of a popup dialog, makes it easier
to edit
transfer
functions as well as edit labels and 

[Paraview] Verbose output on Windows? (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

I'm debugging a ParaView client-server connection issue between ParaView
4.1.0 running on a Windows machine and a remote HPC system.I'd like to
see the SSH string that's being generated on the Windows side, but I don't
see any output that says "Server Launch command is :"  like I see on the
Linux and Mac systems.   Is there some way to see this output on the Windows
machine?   This output must be generated by Paraview by default, because I
don't think that that I'm doing anything in my default_servers.pvsc file to
print this output.


Here's what I see on Mac/Linux in the terminal window where I run the
client.   There are the values that I'm setting in the host profile as
described in the default_servers.pvsc file, and I then see the SSH command
that gets built and executed.

LOGINNODE=remote-host.xx.xx.xx
NODES=2
NODE_TYPE=compute
PROCS=8
PROJECTNUM=ABC123456789
PV_CONNECT_ID=43481
PV_SERVER_PORT=9333
QUEUE=serial
SERVER_PORT=49130
SSHLOC=/usr/krb5/bin/ssh
USERNAME=my_username
WALLTIME=10
Setting ConnectID: 43481
Accepting connection(s): my-host.xx.xx.xx:9333

Server launch command is : /usr/krb5/bin/ssh -q "-o
StrictHostKeyChecking=no" "-o ExitOnForwardFailure=yes" -R
49130:127.0.0.1:9333 -l my_username remote-host.xx.xx.xx  /usr/bin/env
PV_CONNECT_ID=43481 PV_PORT=49130 VERSION=4.1.0 WALLTIME=10
PROJECTNUM=ABC123456789 QUEUE=serial NODES=2 PROCS=8 TUNNEL=1
NODE_TYPE=compute LOGINNODE=remote-hostname.xx.xx.xx
/app/DAAC/paraview/utils/pvserver.sh



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] Verbose output on Windows? (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Thanks - redirecting the output from the cmd.exe window captured what I
needed.




Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


-Original Message-
From: Burlen Loring [mailto:blor...@lbl.gov] 
Sent: Tuesday, April 01, 2014 4:35 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US); paraview@paraview.org
Subject: Re: [Paraview] Verbose output on Windows? (UNCLASSIFIED)

Hi Rick,

If you are running from cmd.exe you capture the output in a file as follows:


paraview.exe > out.txt 2>&1


If you launch from within a cygwin shell, you see the output as usual. I
find cygwin much nicer than cmd.

Burlen



On 04/01/2014 12:52 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US)
wrote:


Classification: UNCLASSIFIED
Caveats: NONE

I'm debugging a ParaView client-server connection issue between
ParaView
4.1.0 running on a Windows machine and a remote HPC system.I'd
like to
see the SSH string that's being generated on the Windows side, but I
don't
see any output that says "Server Launch command is :"  like I see on
the
Linux and Mac systems.   Is there some way to see this output on the
Windows
machine?   This output must be generated by Paraview by default,
because I
don't think that that I'm doing anything in my default_servers.pvsc
file to
print this output.


Here's what I see on Mac/Linux in the terminal window where I run
the
client.   There are the values that I'm setting in the host profile
as
described in the default_servers.pvsc file, and I then see the SSH
command
that gets built and executed.

LOGINNODE=remote-host.xx.xx.xx
NODES=2
NODE_TYPE=compute
PROCS=8
PROJECTNUM=ABC123456789
PV_CONNECT_ID=43481
PV_SERVER_PORT=9333
QUEUE=serial
SERVER_PORT=49130
SSHLOC=/usr/krb5/bin/ssh
USERNAME=my_username
WALLTIME=10
Setting ConnectID: 43481
Accepting connection(s): my-host.xx.xx.xx:9333

Server launch command is : /usr/krb5/bin/ssh -q "-o
StrictHostKeyChecking=no" "-o ExitOnForwardFailure=yes" -R
49130:127.0.0.1:9333 -l my_username remote-host.xx.xx.xx
/usr/bin/env
PV_CONNECT_ID=43481 PV_PORT=49130 VERSION=4.1.0 WALLTIME=10
PROJECTNUM=ABC123456789 QUEUE=serial NODES=2 PROCS=8 TUNNEL=1
NODE_TYPE=compute LOGINNODE=remote-hostname.xx.xx.xx
/app/DAAC/paraview/utils/pvserver.sh



Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Aberdeen Proving Ground, MD 
Phone:  410-278-6266


Classification: UNCLASSIFIED
Caveats: NONE



 

___
Powered by www.kitware.com

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

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

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



Classification: UNCLASSIFIED
Caveats: NONE




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

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

[Paraview] connectivity errors

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

I¹m setting up Paraview client/server  on a new Cray XC30 system.   I have
a totally clean build on Paraview on the Cray side, but I can¹t get the
client-server connection to work, and I¹m seeing a strange error.   It
looks like the client-server connection is being established, and then the
client crashes with this error:

Accepting connection(s): my-client-host:53484
ERROR: In 
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/
paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefi
nitionManager.cxx, line 565
vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
group=misc and proxy=StrictLoadBalancing were found.


Segmentation fault



On the server side,  I¹m getting a more standard connectivity error:

Client connected.
ERROR: In 
/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/C
ore/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0xe2b930): Could not receive tag. 1


I know that the communication path from the compute nodes to the client
workstation is valid because VisIt and Ensight both work on this system.

Any ideas?




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

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

Re: [Paraview] connectivity errors

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

I forgot to include that I get the same behavior on both an OSX and Linux
ParaView client - so I don’t think that it’s a client-side software issue.
  But, what I don’t understand is what could happen on the server side to
crash the client?

I think that my cmake/build command is pretty straight forward an
essentially identical to the cmake command I’ve used on other Cray systems:

cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
-DParaView_FROM_GIT=ON \
-DENABLE_boost=ON \
-DENABLE_cgns=OFF \
-DENABLE_ffmpeg=ON \
-DENABLE_fontconfig=ON \
-DENABLE_freetype=ON \
-DENABLE_hdf5=ON \
-DENABLE_libxml2=ON \
-DENABLE_matplotlib=OFF \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_osmesa=ON \
-DENABLE_paraview=ON \
-DENABLE_png=ON \
-DENABLE_python=ON \
-DENABLE_qhull=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DENABLE_visitbridge=ON \
-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
ichcxx.so" \
-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
h.so" \
-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
xx.so" \
-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
e/" \
-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
" \
-DUSE_SYSTEM_mpi=ON \
-DUSE_SYSTEM_python=ON \
-DUSE_SYSTEM_zlib=ON \
../Source




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




On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
 wrote:

>I¹m setting up Paraview client/server  on a new Cray XC30 system.   I have
>a totally clean build on Paraview on the Cray side, but I can¹t get the
>client-server connection to work, and I¹m seeing a strange error.   It
>looks like the client-server connection is being established, and then the
>client crashes with this error:
>
>Accepting connection(s): my-client-host:53484
>ERROR: In 
>/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
>/
>paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
>i
>nitionManager.cxx, line 565
>vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
>group=misc and proxy=StrictLoadBalancing were found.
>
>
>Segmentation fault
>
>
>
>On the server side,  I¹m getting a more standard connectivity error:
>
>Client connected.
>ERROR: In 
>/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
>C
>ore/vtkSocketCommunicator.cxx, line 812
>vtkSocketCommunicator (0xe2b930): Could not receive tag. 1
>
>
>I know that the communication path from the compute nodes to the client
>workstation is valid because VisIt and Ensight both work on this system.
>
>Any ideas?
>
>
>
>
>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

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

Re: [Paraview] connectivity errors

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

Yes – it was a versions issue.I “borrowed” someone else’s build script and 
didn’t look closely enough to see that it wasn’t picking up the production 
release. 8-)




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

From: Burlen Loring mailto:burlen.lor...@gmail.com>>
Date: Thursday, July 10, 2014 at 12:16 PM
To: "U.S. ARL" 
mailto:richard.c.angelini@mail.mil>>, 
"paraview@paraview.org<mailto:paraview@paraview.org>" 
mailto:paraview@paraview.org>>
Subject: Re: [Paraview] connectivity errors

Hi Rich,

Did you get it to work? You should be using the same version on both sides. If 
you are setting this up for multiple people it's simpler to use the official 
releases, and do version check in your server side scripts, print a nice error 
message when someone connects with an unsupported version. The 
scripts<https://github.com/burlen/pvserver-configs> I wrote for NERSC Edison  
have this check.

Burlen

On 07/09/2014 06:15 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote:

I forgot to include that I get the same behavior on both an OSX and Linux
ParaView client - so I don’t think that it’s a client-side software issue.
  But, what I don’t understand is what could happen on the server side to
crash the client?

I think that my cmake/build command is pretty straight forward an
essentially identical to the cmake command I’ve used on other Cray systems:

cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
-DParaView_FROM_GIT=ON \
-DENABLE_boost=ON \
-DENABLE_cgns=OFF \
-DENABLE_ffmpeg=ON \
-DENABLE_fontconfig=ON \
-DENABLE_freetype=ON \
-DENABLE_hdf5=ON \
-DENABLE_libxml2=ON \
-DENABLE_matplotlib=OFF \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_osmesa=ON \
-DENABLE_paraview=ON \
-DENABLE_png=ON \
-DENABLE_python=ON \
-DENABLE_qhull=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DENABLE_visitbridge=ON \
-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
ichcxx.so" \
-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
h.so" \
-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
xx.so" \
-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
e/" \
-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
" \
-DUSE_SYSTEM_mpi=ON \
-DUSE_SYSTEM_python=ON \
-DUSE_SYSTEM_zlib=ON \
../Source




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




On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
<mailto:richard.c.angelini@mail.mil> wrote:



I¹m setting up Paraview client/server  on a new Cray XC30 system.   I have
a totally clean build on Paraview on the Cray side, but I can¹t get the
client-server connection to work, and I¹m seeing a strange error.   It
looks like the client-server connection is being established, and then the
client crashes with this error:

Accepting connection(s): my-client-host:53484
ERROR: In
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
/
paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
i
nitionManager.cxx, line 565
vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
group=misc and proxy=StrictLoadBalancing were found.


Segmentation fault



On the server side,  I¹m getting a more standard connectivity error:

Client connected.
ERROR: In
/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
C
ore/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0xe2b930): Could not receive tag. 1


I know that the communication path from the compute nodes to the client
workstation is valid because VisIt and Ensight both work on this system.

Any ideas?




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




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

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

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

Follow this link to subscribe/unsubscribe:
http://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

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

Re: [Paraview] Movies from my desktop (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

"ffmpeg" will do this on Linux.

The command looks something like:

ffmpeg -f x11grab -s 1680x1050 -r 30 -i :0.0 -sameq /tmp/out.mpg

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


-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Scott, W
Alan
Sent: Tuesday, August 05, 2014 12:41 PM
To: paraview@paraview.org
Subject: [Paraview] Movies from my desktop

I want to make a movie of my screen as I interact with ParaView.  Since I
want to see a user's interactions with ParaView, Save Animation isn't what I
want.  Does anyone know of a tool that will do this?  Windows, Mac or Linux
are fine.
 
Thanks!
 
Alan
 
 
 

Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] [EXTERNAL] build trouble on LLNL clusters

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

So, what changed on the system-side?  New GL development libraries, or maybe 
they were accidentally removed, or something like that?It's probably not 
you, your source code or your build script .


Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266

From: ParaView [paraview-boun...@paraview.org] on behalf of Cook, Rich 
[coo...@llnl.gov]
Sent: Wednesday, August 20, 2014 3:19 PM
To: Alan Scott
Cc: paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] build trouble on LLNL clusters

Hi Alan
It’s from a tarball called "ParaView-v4.1.0-source.tar.gz” which I downloaded a 
while ago.
I’m not sure if I pulled from a repo at the time, but I don’t think so.
Checksum is

rcook@rzgpu52 (paraview-4.1.0 ): sum ParaView-v4.1.0-source.tar.gz
47281 49278



On Aug 20, 2014, at 12:11 PM, Scott, W Alan 
mailto:wasc...@sandia.gov>> wrote:

Master source pull, or PV 4.1?

Alan

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Cook, Rich
Sent: Wednesday, August 20, 2014 1:06 PM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters

Hello,
I’m seeing this new error on our machines, which is mysterious as I have not 
changed my build process at all.  Can someone help me spot the source of my 
woes here?  Thanks!

[  5%] cd 
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype
 && /usr/local/tools/gcc-4.4.6/bin/gcc  -DFT2_BUILD_LIBRARY -DVTK_IN_VTK 
-Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include 
-I/usr/local/tools/hdf5-gnu-serial-1.8.8/include  -I/usr/local/include  -w -w 
-g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include
 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src
 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype
 
-I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include
-o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o   -c 
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c
[  5%] [  5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText':
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886:
 undefined reference to `glGetBooleanv'
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889:
 undefined reference to `glGetFloatv'
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907:
 undefined reference to `glGetFloatv'
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918:
 undefined reference to `glPassThrough'
CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function 
`gl2psPrintPostScriptBeginViewport':
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154:
 undefined reference to `glRenderMode'
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166:
 undefined reference to `glGetFloatv'
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169:
 undefined reference to `glGetIntegerv'
CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport':
/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346:
 undefined reference to `glRenderMode'
CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport’:
etc. etc. etc.


Here is how I build.

/usr/local/tools/cmake-2.8.10/bin/cmake.real \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\
-DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \
-DVTK_USE_OFFSCREEN:BOOL=ON \
-DOPENGL_gl_LIBRARY:FILEPATH= \
-DVTK_USE_X:BOOL=OFF \
-DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \
-DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \
-DPARAVIEW_USE_MPI:BOOL=OFF \
-DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \
-DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \
-DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \
-DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \
-DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \
-DPARAVIEW_USE_BOOST:BOOL=ON \
-DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
-DVISIT_BUILD_READER_CGNS:BOOL=ON \
-DVISIT_BUILD_READER_Mili:BOOL=ON \
-DVISIT_BUILD_READER_Silo:BOOL=ON \
-DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/c

Re: [Paraview] Dropping Snow Leopard OsX binaries for ParaView (UNCLASSIFIED)

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

Classification: UNCLASSIFIED
Caveats: NONE

Utkarsh - unfortunately, we still have a number of Macs that are still
running 10.6 and are using ParaView.  We'd like to use the pre-built
binaries for the next ParaView release on these machines if possible.  We
currently don't build from source for the Macs, so that could be a real
challenge for us if we needed to start doing that .We're pushing
hard to get these 10.6 systems either replaced or upgraded in the near
future, but not soon enough.

-

Folks,

I wanted to get a quick survey if anyone cares if we drop support for
distributing ParaVIew binaries compatible with Snow Leopard. Lion on
wards will still be supported.

There are two OsX binaries for ParaView currently and it can be a
little confusing which one to use and why and hence this change.

Utkarsh


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



Classification: UNCLASSIFIED
Caveats: NONE




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

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

Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED)

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

When doing a clean production build, it’s very  useful to be able to do a
“git pull” to get all of the correct tarballs downloaded.   The
functionality that was previous to 4.2.0 was exactly appropriate - “git
checkout v4.1.0”

The alternative (as I understand it) is to enable GIT and do a build from
the development tree.  (This will pull all of the tarballs for the
supporting libraries).   Then re-run the build with “GIT=OFF” , manually
download the production tarball, and then re-run the build.   Does this
sound like the best solution?






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




On 10/11/14, 6:04 PM, "Cory Quammen"  wrote:

>Hi Simon,
>
>What you are doing as a workaround is indeed how production builds
>should be created. The ParaView superbuild is now set up to check out
>the master branch of ParaView, which varies day to day. In 4.1 and
>prior to that, it was set up to check out out the release branch,
>which was far more static. If you disable ParaView_FROM_GIT in CMake,
>it will download the release source tar ball and build from that,
>essentially what you have been doing.
>
>I'll update the superbuild wiki instructions to note this.
>
>Best regards,
>Cory
>
>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US)
> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hello,
>>
>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to
>> build a specific version, I will do
>>
>> git clone git://paraview.org/ParaViewSuperbuild.git
>> cd ParaViewSuperbuild
>> git checkout v4.1.0
>>
>> That has always worked for me for v4.1.0 tag
>>
>> But with v4.2.0 release, if I do the following on different days,
>>
>> git clone git://paraview.org/ParaViewSuperbuild.git
>> cd ParaViewSuperbuild
>> git checkout v4.2.0
>>
>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time.
>>Am I
>> missing something? This is causing me problem when I am trying to get
>>the
>> same version of ParaView mesa and osmesa build for client/server mode.
>>I end
>> up doing a
>>
>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz
>>
>> To get around the problem. Thoughts?
>>
>>
>> Thanks
>> -simon
>>
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>>http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>>http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://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
>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/paraview

___
Powered by www.kitware.com

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

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

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

Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED)

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

Yes - we want the 4.2.0 tag on the Superbuild (and for all future
production releases).   In an earlier message on the this thread, Corey
implied that it was no longer supported ….  of course, at this point we’re
more or less done  with the 4.2.0 implementation.  Next time, it would be
nice to have when the production release is announced!   8-)




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




On 10/14/14, 8:45 AM, "Utkarsh Ayachit" 
wrote:

>Rick,
>
>Are you taking referring to  the "v4.1.0" tag on the superbuild repo?
>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about
>that.
>
>Utkarsh
>
>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY
>ARL (US)  wrote:
>> When doing a clean production build, it’s very  useful to be able to do
>>a
>> “git pull” to get all of the correct tarballs downloaded.   The
>> functionality that was previous to 4.2.0 was exactly appropriate - “git
>> checkout v4.1.0”
>>
>> The alternative (as I understand it) is to enable GIT and do a build
>>from
>> the development tree.  (This will pull all of the tarballs for the
>> supporting libraries).   Then re-run the build with “GIT=OFF” , manually
>> download the production tarball, and then re-run the build.   Does this
>> sound like the best solution?
>>
>>
>>
>>
>>
>>
>> __
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> On 10/11/14, 6:04 PM, "Cory Quammen"  wrote:
>>
>>>Hi Simon,
>>>
>>>What you are doing as a workaround is indeed how production builds
>>>should be created. The ParaView superbuild is now set up to check out
>>>the master branch of ParaView, which varies day to day. In 4.1 and
>>>prior to that, it was set up to check out out the release branch,
>>>which was far more static. If you disable ParaView_FROM_GIT in CMake,
>>>it will download the release source tar ball and build from that,
>>>essentially what you have been doing.
>>>
>>>I'll update the superbuild wiki instructions to note this.
>>>
>>>Best regards,
>>>Cory
>>>
>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US)
>>> wrote:
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> Hello,
>>>>
>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want
>>>>to
>>>> build a specific version, I will do
>>>>
>>>> git clone git://paraview.org/ParaViewSuperbuild.git
>>>> cd ParaViewSuperbuild
>>>> git checkout v4.1.0
>>>>
>>>> That has always worked for me for v4.1.0 tag
>>>>
>>>> But with v4.2.0 release, if I do the following on different days,
>>>>
>>>> git clone git://paraview.org/ParaViewSuperbuild.git
>>>> cd ParaViewSuperbuild
>>>> git checkout v4.2.0
>>>>
>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time.
>>>>Am I
>>>> missing something? This is causing me problem when I am trying to get
>>>>the
>>>> same version of ParaView mesa and osmesa build for client/server mode.
>>>>I end
>>>> up doing a
>>>>
>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz
>>>>
>>>> To get around the problem. Thoughts?
>>>>
>>>>
>>>> Thanks
>>>> -simon
>>>>
>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>> ___
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>>http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>http://paraview.org/Wiki/ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://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
>>>
>>>Follow this link to subscribe/unsubscribe:
>>>http://public.kitware.com/mailman/listinfo/paraview
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>>http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>>http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview

___
Powered by www.kitware.com

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

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

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

Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED)

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

Should you also update the Paraview SuperBuild wiki page?


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




On 10/14/14, 8:57 AM, "Utkarsh Ayachit" 
wrote:

>Tag "v4.2.0-1" is now available on the ParaView Superbuild repo.
>
>Utkarsh
>
>
>On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit
> wrote:
>> Doh! I see I added the tag but forgot to toggle the git/branch name,
>> which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1"
>> tag fixing this issue.
>>
>> Again, really sorry about this :/.
>>
>> Utkarsh
>>
>> On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY
>> ARL (US)  wrote:
>>> Yes - we want the 4.2.0 tag on the Superbuild (and for all future
>>> production releases).   In an earlier message on the this thread, Corey
>>> implied that it was no longer supported ….  of course, at this point
>>>we’re
>>> more or less done  with the 4.2.0 implementation.  Next time, it would
>>>be
>>> nice to have when the production release is announced!   8-)
>>>
>>>
>>>
>>> 
>>> Rick Angelini
>>> USArmy Research Laboratory
>>> CISD/HPC Architectures Team
>>> Phone:  410-278-6266
>>>
>>>
>>>
>>>
>>> On 10/14/14, 8:45 AM, "Utkarsh Ayachit" 
>>> wrote:
>>>
>>>>Rick,
>>>>
>>>>Are you taking referring to  the "v4.1.0" tag on the superbuild repo?
>>>>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about
>>>>that.
>>>>
>>>>Utkarsh
>>>>
>>>>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY
>>>>ARL (US)  wrote:
>>>>> When doing a clean production build, it’s very  useful to be able to
>>>>>do
>>>>>a
>>>>> “git pull” to get all of the correct tarballs downloaded.   The
>>>>> functionality that was previous to 4.2.0 was exactly appropriate -
>>>>>“git
>>>>> checkout v4.1.0”
>>>>>
>>>>> The alternative (as I understand it) is to enable GIT and do a build
>>>>>from
>>>>> the development tree.  (This will pull all of the tarballs for the
>>>>> supporting libraries).   Then re-run the build with “GIT=OFF” ,
>>>>>manually
>>>>> download the production tarball, and then re-run the build.   Does
>>>>>this
>>>>> sound like the best solution?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> __
>>>>> Rick Angelini
>>>>> USArmy Research Laboratory
>>>>> CISD/HPC Architectures Team
>>>>> Phone:  410-278-6266
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 10/11/14, 6:04 PM, "Cory Quammen" 
>>>>>wrote:
>>>>>
>>>>>>Hi Simon,
>>>>>>
>>>>>>What you are doing as a workaround is indeed how production builds
>>>>>>should be created. The ParaView superbuild is now set up to check out
>>>>>>the master branch of ParaView, which varies day to day. In 4.1 and
>>>>>>prior to that, it was set up to check out out the release branch,
>>>>>>which was far more static. If you disable ParaView_FROM_GIT in CMake,
>>>>>>it will download the release source tar ball and build from that,
>>>>>>essentially what you have been doing.
>>>>>>
>>>>>>I'll update the superbuild wiki instructions to note this.
>>>>>>
>>>>>>Best regards,
>>>>>>Cory
>>>>>>
>>>>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US)
>>>>>> wrote:
>>>>>>> Classification: UNCLASSIFIED
>>>>>>> Caveats: NONE
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I
>>>>>>>want
>>>>>>>to
>>>>>>> build a specific version, I will do
>>>>>>>
>>>>>>> git clone git://par

Re: [Paraview] Paravew on XC30

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

Chris - I’ve been able to build on 3 different XC30 systems … here’s my
script.  I’m using 
PrgEnv-gnu/5.2.14
cray-mpich/6.3.1
gcc/4.8.2



#!/bin/csh

module unload PrgEnv-cray
module load PrgEnv-gnu
module load cray-mpich
module load pbs
module list


setenv gcc "gcc"
setenv gplusplus "g++"
setenv gfortran "gfortran"

setenv CC $gcc
setenv CXX $gplusplus
setenv FC $gfortran
setenv F70 $gfortran
setenv F77 $gfortran
setenv F90 $gfortran
setenv F95 $gfortran

set version=4.2.0

if (! -d Build_${version}_mesa) mkdir Build_${version}_mesa

cd Build_${version}_mesa

if (! -d install) mkdir install

set INSTALLPATH=`pwd`/install

#Build the latest version of CMAKE
if (! -e install/bin/cmake) then
echo "Need to build cmake"
cp ../Downloads/cmake-2.8.11.tar.gz .
tar xzvf cmake-2.8.11.tar.gz
cd cmake-2.8.11
./bootstrap --prefix=$INSTALLPATH
make -j 8 install
cd ..
endif

setenv PATH ${INSTALLPATH}/bin:$PATH

cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_mesa \
-DCMAKE_BUILD_TYPE=Release \
-DParaView_FROM_GIT=OFF \
-Ddownload_location=`pwd`/../Downloads \
-DParaView_URL=`pwd`/../Downloads/ParaView-v4.2.0-source.tar.gz \
-DENABLE_boost=ON \
-DENABLE_cgns=OFF \
-DENABLE_ffmpeg=ON \
-DENABLE_fontconfig=ON \
-DENABLE_freetype=ON \
-DENABLE_hdf5=ON \
-DENABLE_libxml2=ON \
-DENABLE_matplotlib=OFF \
-DENABLE_osmesa=OFF \
-DENABLE_mesa=ON \
-DENABLE_qt=ON \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_png=ON \
-DENABLE_python=ON \
-DENABLE_qhull=ON \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DENABLE_visitbridge=OFF \
-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
ichcxx.so" \
-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
h.so" \
-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
xx.so" \
-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
e/" \
-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
" \
-DUSE_SYSTEM_mpi=ON \
-DUSE_SYSTEM_python=ON \
-DUSE_SYSTEM_zlib=ON \
../Source

make -j 4 install


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




On 10/27/14, 11:00 AM, "Burlen Loring"  wrote:

>
>
>
>Hi Christopher,
>
>I can't help you with the superbuild, but I can show you how to build PV
>on the XC30. here's
>
>the script 
>lds/config-pv-mesa.sh> I used to build ParaView 4.2 with
>PrgEnv-gnu/5.2.25 on our XC30
>
>You'll see a bunch of paths that need to be set specific to the version
>of PrgEnv-gnu that you are running. The easiest way to figure out these
>is to look at the CRAY_LD_LIBRARY_PATH environment variable. If for some
>reason that isn't set then you can alway
> look at the output of "CC --verbose". You also need to point to an
>OSMesa install 
>.
>
>Burlen
>
>On 10/26/2014 10:22 PM, R C Bording wrote:
>
>
>Hi, 
> Trying to build Paraview on our XC30,
>here is the end of the build log where it goes pear-shape,
>
>Making install in test
>/usr/bin/install -c -m 644 fonts.dtd
>'/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2
>.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts'
>/usr/bin/install -c -m 644 ./fonts.conf
>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.
>0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf
>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.
>0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v
>/usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
>/usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction
>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.
>0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v
>make[5]: *** [install-data-local] Error 132
>make[4]: *** [install-am] Error 2
>make[3]: *** [install-recursive] Error 1
>make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] Error 2
>make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2
>make: *** [all] Error 2
>
>Here is the cmake build flags for the paraviewsuperbuild script.
>
>IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \
>-DParaView_FROM_GIT=OFF \
>-DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \
>-DENABLE_boost=ON \
>-DENABLE_cgns=OFF \
>-DENABLE_ffmpeg=ON \
>-DENABLE_fontconfig=ON \
>-DENABLE_freetype=ON \
>-DENABLE_hdf5=ON \
>-DENABLE_libxml2=ON \
>-DENABLE_matplotlib=OFF \
>-DENABLE_mesa=OFF \
>-DENABLE_mpi=ON \
>-DENABLE_numpy=ON \
>-DENABLE_osmesa=ON \
>-DENABLE_paraview=ON \
>-DENABLE_png=ON \
>-DENABLE_python=ON \
>-DENABLE_qhull=ON \
>-DENABLE_qt=OFF \
>-DENABLE_silo=ON \
>-DENABLE_szip=ON \
>-DENABLE_visitbridge=ON \
>-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libm
>pichc

Re: [Paraview] Paravew on XC30

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

Yeah - I have two builds - one for the login nodes and one for the compute
nodes … yeah, I included the login node build - but the structure is
essentially the same.

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




On 10/27/14, 12:11 PM, "Burlen Loring"  wrote:

>Hi Rick,
>
>It doesn't look like you're building for the compute nodes, either that
>or you've got GPU's. for example Qt is on and OSMesa is off. I'm
>unfamiliar with the superbuild process but normally that would produce a
>binary that couldn't be run on the compute node without gpu's.
>
>I'm expecting my installs to work with the Kitware provided client
>binaries. For that in the past at least we need to match their build
>options to some some extent. For example the VisIt bridge would be on. I
>know there have been some updates to how the server capabilities are
>exposed so I'm not sure how much of an issue that is in 4.2.
>
>Burlen
>
>On 10/27/2014 08:22 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US)
>wrote:
>> Chris - I’ve been able to build on 3 different XC30 systems … here’s my
>> script.  I’m using
>> PrgEnv-gnu/5.2.14
>> cray-mpich/6.3.1
>> gcc/4.8.2
>>
>>
>>
>> #!/bin/csh
>>
>> module unload PrgEnv-cray
>> module load PrgEnv-gnu
>> module load cray-mpich
>> module load pbs
>> module list
>>
>>
>> setenv gcc "gcc"
>> setenv gplusplus "g++"
>> setenv gfortran "gfortran"
>>
>> setenv CC $gcc
>> setenv CXX $gplusplus
>> setenv FC $gfortran
>> setenv F70 $gfortran
>> setenv F77 $gfortran
>> setenv F90 $gfortran
>> setenv F95 $gfortran
>>
>> set version=4.2.0
>>
>> if (! -d Build_${version}_mesa) mkdir Build_${version}_mesa
>>
>> cd Build_${version}_mesa
>>
>> if (! -d install) mkdir install
>>
>> set INSTALLPATH=`pwd`/install
>>
>> #Build the latest version of CMAKE
>> if (! -e install/bin/cmake) then
>>  echo "Need to build cmake"
>>  cp ../Downloads/cmake-2.8.11.tar.gz .
>>  tar xzvf cmake-2.8.11.tar.gz
>>  cd cmake-2.8.11
>>  ./bootstrap --prefix=$INSTALLPATH
>>  make -j 8 install
>>  cd ..
>> endif
>>
>> setenv PATH ${INSTALLPATH}/bin:$PATH
>>
>> cmake \
>> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_mesa \
>> -DCMAKE_BUILD_TYPE=Release \
>> -DParaView_FROM_GIT=OFF \
>> -Ddownload_location=`pwd`/../Downloads \
>> -DParaView_URL=`pwd`/../Downloads/ParaView-v4.2.0-source.tar.gz \
>> -DENABLE_boost=ON \
>> -DENABLE_cgns=OFF \
>> -DENABLE_ffmpeg=ON \
>> -DENABLE_fontconfig=ON \
>> -DENABLE_freetype=ON \
>> -DENABLE_hdf5=ON \
>> -DENABLE_libxml2=ON \
>> -DENABLE_matplotlib=OFF \
>> -DENABLE_osmesa=OFF \
>> -DENABLE_mesa=ON \
>> -DENABLE_qt=ON \
>> -DENABLE_mpi=ON \
>> -DENABLE_numpy=ON \
>> -DENABLE_paraview=ON \
>> -DENABLE_png=ON \
>> -DENABLE_python=ON \
>> -DENABLE_qhull=ON \
>> -DENABLE_silo=ON \
>> -DENABLE_szip=ON \
>> -DENABLE_visitbridge=OFF \
>> 
>>-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/lib
>>mp
>> ichcxx.so" \
>> 
>>-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
>>ic
>> h.so" \
>> 
>>-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
>>hc
>> xx.so" \
>> 
>>-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/incl
>>ud
>> e/" \
>> 
>>-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
>>e/
>> " \
>> -DUSE_SYSTEM_mpi=ON \
>> -DUSE_SYSTEM_python=ON \
>> -DUSE_SYSTEM_zlib=ON \
>> ../Source
>>
>> make -j 4 install
>>
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> On 10/27/14, 11:00 AM, "Burlen Loring"  wrote:
>>
>>>
>>>
>>> Hi Christopher,
>>>
>>> I can't help you with the superbuild, but I can show you how to build
>>>PV
>>> on the XC30. here's
>>>
>>> the script
>>> 
>>><https://github.com/burlen/pvserver-configs/blob/master/servers/edison/b
>>>ui
>>> l

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

I’m having trouble building 4.3.1 on several systems where 4.2 built without 
issue.  Is there a particular version of cmake that 4.3.1 needs to be built 
with?


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

From: Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>
Date: Tuesday, January 20, 2015 at 4:17 PM
To: ParaView mailto:paraview@paraview.org>>, ParaView 
Developers 
mailto:paraview-develop...@paraview.org>>
Subject: [Paraview] ANN: ParaView 4.3.1 is available for download

Folks,

ParaView 4.3.1 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] http://www.kitware.com/blog/posts/view/825
[2] http://paraview.uservoice.com
[3] http://www.kitware.com/blog/
___
Powered by www.kitware.com

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

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

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

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

___
Powered by www.kitware.com

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

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

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

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

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still seeing 
errors.   I’m currently dying in QT -  I’ve seen these QCLUcene errors before, 
but not on the platforms  that I’m currently testing the builds on ….  I 
believe that I get around this by going into the qt build directory and running 
“make install” and the problem goes  away.

/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexSearcher::~QCLuceneIndexSearcher()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTermQuery::QCLuceneTermQuery(QCLuceneTerm 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexReader::deleteDocuments(QCLuceneTerm 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::close()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLucenePhraseQuery::addTerm(QCLuceneTerm const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTermQuery::~QCLuceneTermQuery()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneQueryPrivate::~QCLuceneQueryPrivate()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStopAnalyzer::~QCLuceneStopAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneBooleanQuery::add(QCLuceneQuery*, bool, bool, 
bool)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStandardAnalyzer::QCLuceneStandardAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::setMinMergeDocs(int)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStopAnalyzer::englishStopWords() const'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::clear()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTerm::QCLuceneTerm(QString const&, QString 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::setMaxFieldLength(int)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLucenePhraseQuery::QCLucenePhraseQuery()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStandardAnalyzer::~QCLuceneStandardAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::addDocument(QCLuceneDocument&, 
QCLuceneAnalyzer&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneSearcher::search(QCLuceneQuery const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::QCLuceneDocument()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneQuery::toString() const'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::~QCLuceneDocument()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexReader::open(QString const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::add(QCLuceneField*)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::optimize()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneField::QCLuceneField(QString const&, QString 
const&, int)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexReader::indexExists(QString const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTerm::~QCLuceneTerm()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocumentPrivate::~QCLuceneDocumentPrivate()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

FYI – as I thought, manually running “make install” allowed me to get past the 
QCLucene errors as it has in the past. Looks like I then made it all of the 
way through to the paraview before it died with some python class errors.
Looks like cmake is picking up my system python instead of the one that I’m 
building as part of the ParaView distro.   That’s new. How do I get it to 
pick up the Paraview/python not the system python?




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

From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Wednesday, January 21, 2015 at 12:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>, ParaView Developers 
mailto:paraview-develop...@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still seeing 
errors.   I’m currently dying in QT -  I’ve seen these QCLUcene errors before, 
but not on the platforms  that I’m currently testing the builds on ….  I 
believe that I get around this by going into the qt build directory and running 
“make install” and the problem goes  away.

/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexSearcher::~QCLuceneIndexSearcher()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTermQuery::QCLuceneTermQuery(QCLuceneTerm 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexReader::deleteDocuments(QCLuceneTerm 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::close()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLucenePhraseQuery::addTerm(QCLuceneTerm const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTermQuery::~QCLuceneTermQuery()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneQueryPrivate::~QCLuceneQueryPrivate()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStopAnalyzer::~QCLuceneStopAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneBooleanQuery::add(QCLuceneQuery*, bool, bool, 
bool)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStandardAnalyzer::QCLuceneStandardAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::setMinMergeDocs(int)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStopAnalyzer::englishStopWords() const'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::clear()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneTerm::QCLuceneTerm(QString const&, QString 
const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::setMaxFieldLength(int)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLucenePhraseQuery::QCLucenePhraseQuery()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneStandardAnalyzer::~QCLuceneStandardAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexWriter::addDocument(QCLuceneDocument&, 
QCLuceneAnalyzer&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneSearcher::search(QCLuceneQuery const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::QCLuceneDocument()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneQuery::toString() const'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneDocument::~QCLuceneDocument()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
 undefined reference to `QCLuceneIndexReader::open(QString const&)'
/home/angel/PV/

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

I reran “ccmake” in the paraview build directory and changed python to
point to the one in the Paraview build rather than the system python, and
I now have a clean build.  So,  there are a couple of issues:

QCLucene – why does it fail and require a manual “make install” to complete
Python – why isnt’ cmake picking up python  from the build directory?
It seems to have ignored the CMAKE_INSTALL_PREFIX directive

As far as I know, these are “new” issues.  I’m building on a generic RHEL5
workstation for the first build.  They get much more difficult on the HPC
systems.


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${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:  Thursday, January 22, 2015 at 7:55 AM
To:  Rick Angelini , Utkarsh Ayachit
, ParaView 
Subject:  Re: [Paraview] ANN: ParaView 4.3.1 is available for download


>FYI – as I thought, manually running “make install” allowed me to get
>past the QCLucene errors as it has in the past. Looks like I then
>made it all of the way through to the paraview before it died with some
>python class errors.Looks like cmake
> is picking up my system python instead of the one that I’m building as
>part of the ParaView distro.   That’s new. How do I get it to pick up
>the Paraview/python not the system python?
>
>
>
>
>Rick Angelini
>USArmy Research Laboratory
>CISD/HPC Architectures Team
>Phone:  410-278-6266
>
>
>
>
>From: , Rick Angelini 
>Date: Wednesday, January 21, 2015 at 12:08 PM
>To: Rick Angelini , Utkarsh Ayachit
>, ParaView ,
> ParaView Developers 
>Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download
>
>
>>I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still
>>seeing errors.   I’m currently dying in QT -  I’ve seen these QCLUcene
>>errors before, but not on the platforms  that I’m currently testing the
>>builds on ….  I believe that I get around
>> this by going into the qt build directory and running “make install”
>>and the problem goes  away.
>>
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneIndexSearcher::~QCLuceneIndexSearcher()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneTermQuery::QCLuceneTermQuery(QCLuceneTerm const&)'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneIndexReader::deleteDocuments(QCLuceneTerm const&)'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to `QCLuceneIndexWriter::close()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLucenePhraseQuery::addTerm(QCLuceneTerm const&)'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneTermQuery::~QCLuceneTermQuery()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneQueryPrivate::~QCLuceneQueryPrivate()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneStopAnalyzer::~QCLuceneStopAnalyzer()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneBooleanQuery::add(QCLuceneQuery*, bool, bool, bool)'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneStandardAnalyzer::QCLuceneStandardAnalyzer()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneIndexWriter::setMinMergeDocs(int)'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to
>>`QCLuceneStopAnalyzer::englishStopWords() const'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to `QCLuceneDocument::clear()'
>>/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
>>ibQtHelp.so: undefined reference to `QCLuceneTerm::QCLuceneTerm(QString
>>const&, QString const&)'
>>/home/an

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

Also – mpiexec didn’t get pushed to the install directory.
It’s in the build directory but didn’t make it to install.



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

From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Thursday, January 22, 2015 at 8:44 AM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

I reran “ccmake” in the paraview build directory and changed python to
point to the one in the Paraview build rather than the system python, and
I now have a clean build.  So,  there are a couple of issues:

QCLucene – why does it fail and require a manual “make install” to complete
Python – why isnt’ cmake picking up python  from the build directory?
It seems to have ignored the CMAKE_INSTALL_PREFIX directive

As far as I know, these are “new” issues.  I’m building on a generic RHEL5
workstation for the first build.  They get much more difficult on the HPC
systems.


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${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:  Thursday, January 22, 2015 at 7:55 AM
To:  Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject:  Re: [Paraview] ANN: ParaView 4.3.1 is available for download


FYI – as I thought, manually running “make install” allowed me to get
past the QCLucene errors as it has in the past. Looks like I then
made it all of the way through to the paraview before it died with some
python class errors.Looks like cmake
is picking up my system python instead of the one that I’m building as
part of the ParaView distro.   That’s new. How do I get it to pick up
the Paraview/python not the system python?




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




From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Wednesday, January 21, 2015 at 12:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>,
ParaView Developers 
mailto:paraview-develop...@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download


I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still
seeing errors.   I’m currently dying in QT -  I’ve seen these QCLUcene
errors before, but not on the platforms  that I’m currently testing the
builds on ….  I believe that I get around
this by going into the qt build directory and running “make install”
and the problem goes  away.

/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneIndexSearcher::~QCLuceneIndexSearcher()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneTermQuery::QCLuceneTermQuery(QCLuceneTerm const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneIndexReader::deleteDocuments(QCLuceneTerm const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to `QCLuceneIndexWriter::close()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLucenePhraseQuery::addTerm(QCLuceneTerm const&)'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneTermQuery::~QCLuceneTermQuery()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneQueryPrivate::~QCLuceneQueryPrivate()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneStopAnalyzer::~QCLuceneStopAnalyzer()'
/home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/l
ibQtHelp.so: undefined reference to
`QCLuceneBooleanQuery::add(QCLuceneQuery*, bool, bool, bool)'
/h

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

The python and mpi issues both exist with the v4.3.1 of the superbuild — 
assuming I’m pulling things in correctly.




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

From: Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>
Date: Thursday, January 22, 2015 at 9:41 AM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Chuck Atkins mailto:chuck.atk...@kitware.com>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

Rich,

I'd definitely stick with v4.3.1 checkout of the Superbuild. There
have been changed pushed to git/master since the release that don't
yet build on even our dashboards, so there's work that needs to be
done.

i.e.
git clone git://paraview.org/ParaViewSuperbuild.git
git checkout v4.3.1

Even if that doesnt' solve the QCLucene problem. Since you said that
was present in the past too, I somehow must have missed that it.
That'd need separate tracking down. Let me know if the Python/MPI
problems persist with the v4.3.1 version of the Superbuild. The
git/master is certainly broken -- Chuck, I am assuming you're looking
into fix the git/master version.

Utkarsh

On Thu, Jan 22, 2015 at 9:30 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
Also – mpiexec didn’t get pushed to the install directory.
It’s in the build directory but didn’t make it to install.



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

From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Thursday, January 22, 2015 at 8:44 AM

To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

I reran “ccmake” in the paraview build directory and changed python to
point to the one in the Paraview build rather than the system python, and
I now have a clean build.  So,  there are a couple of issues:

QCLucene – why does it fail and require a manual “make install” to complete
Python – why isnt’ cmake picking up python  from the build directory?
It seems to have ignored the CMAKE_INSTALL_PREFIX directive

As far as I know, these are “new” issues.  I’m building on a generic RHEL5
workstation for the first build.  They get much more difficult on the HPC
systems.


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${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:  Thursday, January 22, 2015 at 7:55 AM
To:  Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject:  Re: [Paraview] ANN: ParaView 4.3.1 is available for download


FYI – as I thought, manually running “make install” allowed me to get
past the QCLucene errors as it has in the past. Looks like I then
made it all of the way through to the paraview before it died with some
python class errors.Looks like cmake
is picking up my system python instead of the one that I’m building as
part of the ParaView distro.   That’s new. How do I get it to pick up
the Paraview/python not the system python?




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




From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Wednesday, January 21, 2015 at 12:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>,
ParaView Developers 
mailto:paraview-develop...@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download


I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still
seeing errors.   I’m currently dying in QT -  I’ve seen these QCLUcene
errors before, but not on the platforms  that I’m currently testing the
builds on ….  I believe that I get around
this by going into the qt build d

Re: [Paraview] ANN: ParaView 4.3.1 is available for download

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

I’ve seen the QCLucene issue on isolated (SGI machines?) in the past.   I seem 
to now be seeing on every machine I’m trying to build on ….

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

From: Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>>
Date: Thursday, January 22, 2015 at 9:41 AM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Chuck Atkins mailto:chuck.atk...@kitware.com>>
Cc: ParaView mailto:paraview@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

Rich,

I'd definitely stick with v4.3.1 checkout of the Superbuild. There
have been changed pushed to git/master since the release that don't
yet build on even our dashboards, so there's work that needs to be
done.

i.e.
git clone git://paraview.org/ParaViewSuperbuild.git
git checkout v4.3.1

Even if that doesnt' solve the QCLucene problem. Since you said that
was present in the past too, I somehow must have missed that it.
That'd need separate tracking down. Let me know if the Python/MPI
problems persist with the v4.3.1 version of the Superbuild. The
git/master is certainly broken -- Chuck, I am assuming you're looking
into fix the git/master version.

Utkarsh

On Thu, Jan 22, 2015 at 9:30 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) 
mailto:richard.c.angelini@mail.mil>> wrote:
Also – mpiexec didn’t get pushed to the install directory.
It’s in the build directory but didn’t make it to install.



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

From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Thursday, January 22, 2015 at 8:44 AM

To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download

I reran “ccmake” in the paraview build directory and changed python to
point to the one in the Paraview build rather than the system python, and
I now have a clean build.  So,  there are a couple of issues:

QCLucene – why does it fail and require a manual “make install” to complete
Python – why isnt’ cmake picking up python  from the build directory?
It seems to have ignored the CMAKE_INSTALL_PREFIX directive

As far as I know, these are “new” issues.  I’m building on a generic RHEL5
workstation for the first build.  They get much more difficult on the HPC
systems.


cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${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:  Thursday, January 22, 2015 at 7:55 AM
To:  Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>
Subject:  Re: [Paraview] ANN: ParaView 4.3.1 is available for download


FYI – as I thought, manually running “make install” allowed me to get
past the QCLucene errors as it has in the past. Looks like I then
made it all of the way through to the paraview before it died with some
python class errors.Looks like cmake
is picking up my system python instead of the one that I’m building as
part of the ParaView distro.   That’s new. How do I get it to pick up
the Paraview/python not the system python?




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




From: , Rick Angelini 
mailto:richard.c.angelini@mail.mil>>
Date: Wednesday, January 21, 2015 at 12:08 PM
To: Rick Angelini 
mailto:richard.c.angelini@mail.mil>>, 
Utkarsh Ayachit
mailto:utkarsh.ayac...@kitware.com>>, ParaView 
mailto:paraview@paraview.org>>,
ParaView Developers 
mailto:paraview-develop...@paraview.org>>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download


I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I’m still
seeing errors.   I’m currently dying in QT -  I’ve seen these QCLUcene
errors before, but not on the platforms  that I’m currently testing the
builds on ….  I believe that I get around
this by goi

Re: [Paraview] rhel5 vs rhel6

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

Alan – I build on a RHEL5 system and it seems to work on RHEL6 systems … or at 
least I haven’t heard anyone complain ….   8-)


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

From: , Alan Scott mailto:wasc...@sandia.gov>>
Date: Tuesday, February 24, 2015 at 12:59 PM
To: "paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: [Paraview] rhel5 vs rhel6

Can builds of ParaView run only on the version of rhel that they were built 
for, or can they move between OS versions?  Also, what was the Kitware Linux 
build – rhel5 or rhel6?

Thanks,

Alan



___
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