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

[Tim Gallagher]

Thank you, that would be incredible helpful! Do you have a list of what options your builds support? 

It looks like it doesn't have the co-processing or the development files installed during the build that are needed to link our code to paraview. Those are likely the only two additional options we need.

If you don't mind sending me the build scripts, I can get my version with those options built and tested. If it works fine for me, I can send you back the changes needed and you guys can decide if you want to update your build scripts to turn them on by default in the future. The impact of the two options should be minimal -- if it isn't used by somebody, they wouldn't know it was there. 

I don't know what the best way to share the scripts is for you. If they are already buried on the machines somewhere, I can copy them directly.

Thanks again,

Tim

----- Original Message -----
From: "Richard C Angelini (Rick) CIV USARMY RDECOM ARL (US)" <richard.c.angelini.civ at mail.mil>
To: "tim gallagher" <tim.gallagher at gatech.edu>, "paraview" <paraview at paraview.org>
Sent: Thursday, February 4, 2016 8:54:08 AM
Subject: RE: [Non-DoD Source] [Paraview] Building on Cray systems

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




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

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




----

Hi everybody,

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

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

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

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

Thanks!

Tim
_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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