[Paraview] "WriteAllImages" fails when doing phasta in-situ viz linked with ParaView v3.98.1 coprocessing lib

[Hong Yi]

Hi Andy,

Many thanks for the tip! Once I linked all the ParaView libraries to Phasta by referring to the CMake-generated fake version, everything works and I can see all images generated for each time step while phasta is running in-situ :)

Thanks again for all your help!

Hong


From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: Wednesday, April 24, 2013 5:15 PM
To: Hong Yi; paraview at paraview.org
Subject: Re: [Paraview] "WriteAllImages" fails when doing phasta in-situ viz linked with ParaView v3.98.1 coprocessing lib

Hi Hong,

Please keep the discussion on the mailing list so that everyone can benefit.
Were you able to run the fake version and output images from there? You probably already know this but you can do "make VERBOSE=1" to see the full build output so you don't have to go through CMake generated Makefiles to see what libraries are linked in.
I still think going through CMake with Phasta is the best solution since it will work on other machines as well.
Andy

On Tue, Apr 23, 2013 at 3:35 PM, Hong Yi <hongyi at renci.org<mailto:hongyi at renci.org>> wrote:
Hi Andy,

I know this is a naïve question, but I hope you don't mind and can drop me a quick response. Since I did use CMake to build a simple fake fortran simulation code linked to Paraview coprocessing library version 3.98.1, so I am hoping I can use that CMake-generated Makefile (or other CMake-generated files) to determine which Paraview modules need to be linked to for in-situ viz, especially those modules related off-screen rendering and image writers. This way, I don't have to use CMake to build Phasta but instead can leverage the existing Phasta Makefiles with sufficient number of Paraview module libraries related to in-situ viz linked. In fact, I have already got phasta with in-situ run mostly working - it is just that "WriteAllImages" part does not work, which makes me suspect some offscreen rendering-related libraries may not be linked. I did link to Mesa library for off-screen rendering. I guess I just want to check with you to get expert's advice to see if there is any simpler way to fix this problem without rebuilding phasta with CMake. Otherwise, I'll just go ahead to try to build Phasta with CMake if you think that is the best way to proceed at this point.

Many thanks as always,

Best,

Hong

From: paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org> [mailto:paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>] On Behalf Of Hong Yi
Sent: Monday, April 22, 2013 4:01 PM
To: Andy Bauer

Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] "WriteAllImages" fails when doing phasta in-situ viz linked with ParaView v3.98.1 coprocessing lib

Hi Andy,

I did not build Phasta with CMake since the current Phasta I am using already has all Makefiles and build scripts available and working well, so to test it with Paraview in-situ, I just modified a phasta source code file and modified corresponding Makefile to link all needed ParaView libs. Looks like the only way to figure out which libraries are missing is through CMake. So I will give it a try.

Thanks,

Hong

From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: Monday, April 22, 2013 3:22 PM
To: Hong Yi
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] "WriteAllImages" fails when doing phasta in-situ viz linked with ParaView v3.98.1 coprocessing lib

Hi Hong,
Correct me if I'm wrong but isn't Phasta built with CMake? If it is, in CMakeLists.txt you can do something like:
find_package(ParaView REQUIRED)
include("${PARAVIEW_USE_FILE}")
...
If not, I would suggest creating a simple executable and build it with CMake and see what libraries are linked in there. It's a bit tough to figure out which libraries are missing as that depends on how you build ParaView and what system libraries you're running on.

Andy


On Mon, Apr 22, 2013 at 2:52 PM, Hong Yi <hongyi at renci.org<mailto:hongyi at renci.org>> wrote:
Hello,

I am working to build an in-situ viz for a phasta simulation. I am able to build phasta linked to ParaView v3.98.1 coprocessing library and run phasta simulation linked to coprocessing library to process a python pipeline in-situ for each time step iteration.  In the pipeline, there are two rendered views with each view containing a slice and an isocontour showing a bubble in the slice, which are set to be exported to png images when exporting the pipeline. This phasta simulation with in-situ viz can run through if I comment out "WriteAllImages" in the pipeline python code and the output data (parallel unstructured grid writer output) can be written out as expected during the simulation iteration. However, when I uncomment out "WriteAllImages" statement, I got a "Generic Warning: In /../ParaView-3.98.1-source/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error" and phasta simulation code then exits and no images are written out. So I know "WriteAllImages" causes this run time problem. I suspect I may not link all shared libs that are needed for off-screen rendering and then export to png images. Here are the libraries I have linked to currently in the Makefile:

-lPhastaAdaptor -lvtkFortranAdaptor-pv3.98 -lvtkCoProcessor-pv3.98 -lvtkCoProcessorPython -lvtkCoProcessorPython27D-pv3.98 -lvtkPVPythonSupport-pv3.98 -lvtkPVServerManagerRenderingPython -lvtkPVServerManagerCorePython -lvtkPVServerManagerDefaultPython -lvtkPVServerManagerApplicationPython -lvtkFiltersCore-pv3.98 -lvtkFiltersCorePython27D-pv3.98 -lvtkFiltersGeneral-pv3.98 -lvtkFiltersGeneralPython27D-pv3.98 -lvtkFiltersImaging-pv3.98 -lvtkFiltersImagingPython27D-pv3.98 -lOSMesa.so

I am hoping someone could spot some libraries that I have missed here to get "WriteAllImages" work for in-situ viz, or perhaps there are something else I did not do correctly.

Many thanks for any suggestions or advice you can offer regarding this problem.

Hong

_______________________________________________
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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130425/3834fa46/attachment.htm>