[Paraview] Statically linking catalyst to fortran simulation code on Titan

[Hong Yi]

Many thanks for the info, David. Yes, I can get the Catalyst Fortran example running as expected on Titan now after setting up Python as you indicated below. However, I still cannot get expected coprocessing output from our simulation code since requestdatadescription() always returns 0 for the need flag for each time step, hence no further coprocessing is done. At this stage, python coprocessing script is not even touched yet (no corresponding pyc file is generated). Not sure at this point what causes requestdatadescription() to return 0 indicating no need to do coprocessing further, but will investigate further trying to resolve the issue and will start a new thread if I have specific questions to ask along the way.

Thank you again for all your help!

Best regards,
Hong

________________________________
From: David E DeMarle [dave.demarle at kitware.com]
Sent: Friday, September 13, 2013 4:08 PM
To: Hong Yi
Cc: Andy Bauer; paraview at paraview.org
Subject: Re: [Paraview] Statically linking catalyst to fortran simulation code on Titan

Great news on getting it to compile and link!

Pretty sure that the statically built python and paraview python modules need to be accessible from the compute nodes as well.
I would have expected something worse to show up in the log but definately try this first.

What I do is put $cross/install/lib (python itself) and $cross/paraview/src/paraview-build/lib/site-packages (paraview's python modules) somewhere on lustre (like next to where I put $cross/parview/src/paraview-build/bin), and set PYTHONHOME and PYTHONPATH in my pbs script to point to the python and the modules respectively.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130916/49af0a0c/attachment.htm>