[Paraview] Procedure for compiling Catalyst

[Andy Bauer]

Hi Chris,

Catalyst is not a separate entity from ParaView. It is a subset of ParaView
that is used for *in situ *processing. The concept of the editions is that
the subset of interest differs based on the desired *in situ *processing
and linking your simulation code to all of ParaView Catalyst can take up a
significant amount of memory. Hopefully the blog post at
https://blog.kitware.com/paraview-catalyst-editions-what-are-they/ may
clear up your confusion.

Best,
Andy

On Mon, Jul 25, 2016 at 1:07 PM, Christopher Neal <chrisneal at snumerics.com>
wrote:

> Thank you Andy,
>
>
>
> My understanding is that the Catalyst editions can be compiled separately
> from Paraview i.e. I do not need to have a version of Paraview compiled in
> order to compile a Catalyst edition. Is this correct?
>
> Thank you,
>
> Chris
>
>
>
> *From: *Andy Bauer <andy.bauer at kitware.com>
> *Date: *Friday, July 22, 2016 at 8:23 PM
> *To: *Christopher Neal <chrisneal at snumerics.com>
> *Cc: *"paraview at paraview.org" <paraview at paraview.org>
> *Subject: *Re: [Paraview] Procedure for compiling Catalyst
>
>
>
> Hi Chris,
>
> You can get the Catalyst editions source code at
> http://www.paraview.org/download/ by just selecting Catalyst editions for
> Type of Download. If you're just getting started though I would recommend
> doing a build of ParaView without the GUI. Yes this will require learning a
> bit of CMake (see instructions for building ParaView at
> http://www.paraview.org/Wiki/ParaView:Build_And_Install) but it will
> likely be smoother for you for understanding Catalyst's capabilities. Also,
> it's much easier to link a simulation code with Catalyst through CMake than
> specifying all of the include directories and libraries. When you're
> looking for a lean build of Catalyst on an HPC machine then I'd suggest
> going the edition route (the editions help avoid cross-compilation issues
> on HPC machines too).
>
> Best,
>
> Andy
>
>
>
> On Fri, Jul 22, 2016 at 6:16 PM, Christopher Neal <chrisneal at snumerics.com>
> wrote:
>
> Hi All,
>
>
>
> I’m interesting in trying to compile Paraview Catalyst. I understand that
> there are ‘Editions’ of the Catalyst library that vary in the amount of
> functions that are included from the Paraview library. That’s about the
> extent of my knowledge about the actual source for the Catalyst library.
> The documentation that I have found for compiling Catalyst is a bit
> dated(~3 years old), and I haven’t been able to locate an up-to-date set of
> documents that detail the compilation procedure for building Catalyst.  If
> I want Catalyst, must I first have a version of Paraview built from scratch
> on my system? The best documentation that I have found for building
> Paraview is (
> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Download_ParaView_Source_Code),
> and I’m having trouble getting Paraview to build from the instructions(I’ve
> never used cmake before).
>
> Has anyone who has successfully built the Catalyst library or knows about
> the process lend me any tips about how I should approach building Catalyst?
>
> Thank you,
>
> Chris Neal
>
>
> _______________________________________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160725/92d8773b/attachment.html>