[Paraview] Attempting to run Catalyst CFullExample

[Pettey . Lucas]

Hi Bill,

The Catalyst C and C++ examples all require the python script as an argument at run time. The Fortran example requires that the script be in the same directory. So when you aren't giving the script as an argument, the code is running but doesn't have any information about what to co-process, and it exits doing nothing.

As for the seg fault, my guess is that the ParaView versions of the python script and the one against which you are compiling are different. I know they are different on mine and while I don't get a seg fault, I get some errors about the VTK class structures.

I would recommend also checking out the latest versions of the examples. Andy has done a lot of work on them recently, so if they are even a few weeks old, they might not work as expected. Also, you could just export a new script with the PV version built on your system.

I hope this points you in the right direction.

Lucas Pettey

________________________________________
From: paraview-bounces at paraview.org [paraview-bounces at paraview.org] on behalf of Bill Sherman [shermanw at indiana.edu]
Sent: Friday, May 24, 2013 6:56 PM
To: ParaView list
Cc: Bill Sherman
Subject: [Paraview] Attempting to run Catalyst CFullExample

Hello,

I'm in the process of attempting to learn how to use the Catalyst
feature of ParaView, and I have a problem.

I found the sample code on github:
        - https://github.com/acbauer/CatalystExampleCode

and I began by compiling the "CFullExample" application.

There is some weirdness when trying to compile the application
as a non-Catalyst simulation, but since I'm trying to learn
Catalyst, that's just an aside to the code maintainers.

So I have the application (FEDriver) compiled, and there is
a sample python script.  I ran ParaView (same version as I
used when compiling FEDriver -- a git clone from April),
and I start the Catalyst connection:
        -> Tools -> Connect to Catalyst

(which I had to find by poking around, the SC'12 Catalyst
tutorial doesn't seem to mention this -- or not that I noticed.
An aside to the code documenters.)

So I followed the instructions in the python script, and
with ParaView accepting Catalyst connections on port 22222,
this is what happens:
        % ./FEDriver SampleScripts/feslicescript.py
        Segmentation fault (core dumped)

Actually, that happens regardless of whether ParaView is running
or not, but it only happens when I give the python script as an
argument -- w/o the script, it runs for a moment and then returns
to the prompt.

So what am I missing?

        Thanks,
        Bill

--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University
shermanw at indiana.edu

_______________________________________________
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
________________________________

This electronic message transmission and any attachments that accompany it contain information from DRC® (Dynamics Research Corporation) or its subsidiaries, or the intended recipient, which is privileged, proprietary, business confidential, or otherwise protected from disclosure and is the exclusive property of DRC and/or the intended recipient. The information in this email is solely intended for the use of the individual or entity that is the intended recipient. If you are not the intended recipient, any use, dissemination, distribution, retention, or copying of this communication, attachments, or substance is prohibited. If you have received this electronic transmission in error, please immediately reply to the author via email that you received the message by mistake and also promptly and permanently delete this message and all copies of this email and any attachments. We thank you for your assistance and apologize for any inconvenience.