Hi Jim, I think at this point the best option is to build Catalyst with OSMesa.
Cheers, Andy ps. I cc'ed the mailing list in case someone else has a better answer than mine. On Wed, Nov 25, 2015 at 12:28 PM, <jim.el...@awe.co.uk> wrote: > Hi Andy, > > > > Thank you for your reply. > > > > I seem to get the same behaviour with pvbatch. When I run in parallel > using pvbatch like so: > > > > mpirun -np 4 pvbatch ./myscript.py > > > > Four windows are created. The outputted image file from the script is > incomplete. > > > > If I use the --use-offscreen-rendering option like so: > > > > mpirun -np 4 pvbatch --use-offscreen-rendering ./myscript.py > > > > no windows appear and the final image looks correct. > > > > Should I build ParaView with osmesa for use with my Catalyst simulations? > > > > Kind regards, > > Jim > > > > *From:* Andy Bauer [mailto:andy.ba...@kitware.com] > *Sent:* 25 November 2015 15:30 > *To:* Eliot Jim AWE <jim.el...@awe1.awe.co.uk> > *Cc:* paraview@paraview.org > *Subject:* EXTERNAL: Re: [Paraview] Rendering offscreen images from > parallel simulation using Catalyst > > > > Hi Jim, > > You can use OSMesa if you want offscreen rendering to work. There has been > some work with EGL with NVIDIA but I haven't tried that yet myself since I > don't have the EGL libraries on my machine. Intel's OpenSWR may also be an > option but I haven't tried that either. > > > > I think this issue though is independent of Catalyst. Can you try creating > a Python script that outputs an image and try running that in parallel with > pvbatch? Let me know if you get the same behaviour or not. > > Cheers, > > Andy > > > > On Tue, Nov 24, 2015 at 6:04 AM, <jim.el...@awe.co.uk> wrote: > > > > Good morning all, > > > > I have experienced some problems when trying to render images in parallel > from a multipiece dataset using ParaView Catalyst. It seems to work when I > connect live using the ParaView client – I see the full mesh, and a plot of > vtkCompositeIndex looks sensible. > > > > However when I try to render out images, one render window appears on > screen for each parallel process (in a stack). The windows appear to > contain one chunk each. If I manually grab the windows and spread them out > so that each is visible on screen, then chunk zero plots updates to include > the whole dataset, i.e. it looks as if it is grabbing the data from the > screen. > > > > Is there a way to make ParaView Catalyst render offscreen? > > > > I am using ParaView 4.4.0 on my workstation (which has a graphics card) > built from source using Superbuild without mesa. > > > > When I run on a remote platform (no graphics cards) where I build ParaView > using osmesa, the images render without creating a window and contain all > the chunks. > > > > Should I be using a separate ParaView build for my Catalyst simulations > that is built with osmesa? > > > > Apologies if there is not much to go on here – it would be tricky to share > the simulation code and the catalyst adaptor code that I am using. If more > information is needed, I’ll try to put together a representative > simulation/adaptor. > > > > Thanks everyone, > > Jim > > > > > > *Jim Eliot* > > *High Performance Computing Group* > > AWE, Aldermaston, Reading, RG7 4PR > > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR > > > _______________________________________________ > 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 > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR >
_______________________________________________ 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