[Paraview-developers] OSPRay render

[David E DeMarle]

Nice to meet you Rob and thanks for trying it out.

I have to confess I have not yet tried the KNC.
Checking, did you cross compile paraview itself? What I would do is to
compile paraview and ospray once for the host, and then cross compile
pvserver and ospray for the phi. Then you will be assured of a consistant
executable on both sides.


On Monday, June 6, 2016, ƦOB COASTN <robertpancoast77 at gmail.com> wrote:

> Greetings!
>
> This is first message to the developers list
> The recent integration of OSPRay as a module sparks interest.
>
> I am trying to run ParaView with OSPRay as VTK module.
> I want to utilize Xeon Phi KNC.
>
> The compilation from source needs host binaries for x86_64
> architecture, and mic binaries for k1om.
>
> ParaView master branch was linked with OSPRay release v0.10.1.
> This source was linked with the pre-compiled embree-2.9.0 release
> libraries for each k1om and x86_64. *build log linked
>
> https://github.com/mancoast/logs/blob/master/paraview-build_bot-20160606150234.txt
> (~50mb)
>
> ParaView correctly renders with both legacy OpenGL and OSPRay without
> issue when using the host x86_64 build. *screenshots linked
> https://raw.githubusercontent.com/mancoast/img/master/paraview_5opengl.png
> https://raw.githubusercontent.com/mancoast/img/master/paraview_5ospr.png
>
> The issue occurs after MPI launch of PVserver.
> The MPI execution produces errors exactly when the OSPRay rendering is
> enabled. *screenshot linked
>
> https://raw.githubusercontent.com/mancoast/img/master/paraview_5_knc_ospr.png
>
>
>
> [root at coast77 ParaView]# mpirun -env
>
> LD_LIBRARY_PATH=/opt/intel/compilers_and_libraries/linux/lib/mic:/opt/intel/impi/
> 5.1.3.210/mic/lib:/opt/intel/compilers_and_libraries_2016.3.210/linux/compiler/lib/intel64_lin_mic/
> -iface mic0 -host mic0 -n 1 /home/ParaView/build-mic/bin/pvserver
> Waiting for client...
> Connection URL: cs://coast77-mic0.mancoast.int:11111
> Accepting connection(s): coast77-mic0.mancoast.int:11111
> Client connected.
>
>
> ===================================================================================
> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
> =   PID 21651 RUNNING AT mic0
> =   EXIT CODE: 11
> =   CLEANING UP REMAINING PROCESSES
> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>
> ===================================================================================
>
>
> ===================================================================================
> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
> =   PID 21651 RUNNING AT mic0
> =   EXIT CODE: 11
> =   CLEANING UP REMAINING PROCESSES
> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>
> ===================================================================================
> [root at coast77 ParaView]#
>
>
>
> I concurrently see these messages in another terminal:
>
>
> [coast at coast77 ~]$ /home/ParaView/build-host/bin/paraview
> Generic Warning: In
> /home/ParaView/VTK/Rendering/Parallel/vtkSynchronizedRenderers.cxx,
> line 743
> Only 3 or 4 component images are handled.
>
>
> ERROR: In /home/ParaView/VTK/Common/System/vtkSocket.cxx, line 572
> vtkClientSocket (0x2406210): Socket error in call to send. Broken pipe.
>
>
>
> Any recommendations?
>
> Thanks,
> Rob
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>


-- 
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20160607/f3121004/attachment.html>