Re: [Paraview] [EXTERNAL] Re: pvbatch
OK, this … sort of … worked. I was able to use the Kitware download (Yay!). I called pvbatch (surprisingly, it was built by Kitware for Linux), and then used flags --mesa-llvm and --use-offscreen-rendering. I believe --use-offscreen-rendering will be replaced in the future by --force-offscreen-rendering in PV 5.5.0. Thanks Cory, and everyone else that chimed in. Alan From: Cory Quammen Date: Wednesday, November 15, 2017 at 10:46 AM To: W Scott Cc: Ben Boeckel , "paraview@paraview.org" Subject: Re: [Paraview] [EXTERNAL] Re: pvbatch Alan, You should be able to run pvpython --force-offscreen-rendering script.py and no render window will appear. The help for --force-offscreen-rendering says: "If supported by the build and platform, create headless (offscreen) render windows for rendering results." I believe this should work on linux systems, but you should try it out on the system on which you want to force offscreen rendering just to be sure before using it to produce classified images. pvbatch running the same script will indeed not pop up a render window even without the --force-offscreen-rendering option. Let us know how it goes, Cory On Mon, Nov 13, 2017 at 5:04 PM, Scott, W Alan mailto:wasc...@sandia.gov>> wrote: Ben, I believe this is a change from the past. Here is what I desire – how do I get it? I want to run pv(pythonScript). I want it to produce output. I want it to run off screen, not showing on the console display or current display. This is especially important on classified systems. MPI is not available. Not too long ago, my understanding was this was pvbatch. pvpython used either the console display or current display as it’s rendering space. This does not catch my needs. Alan On 11/13/17, 9:04 AM, "Ben Boeckel" mailto:ben.boec...@kitware.com>> wrote: On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote: > What are the magic cmake switches, for superbuild, that are used to > build a non MPI, Mesa version of pvbatch? Where is this documented? pvpython is the non-MPI version of pvbatch. The superbuild docs could probably be improved here. Currently, the mention is: ParaView supports multiple rendering engines including `egl`, `mesa`, `osmesa`, and `qt5`. All of these are incompatible with each other. If none of these are chosen, a UI-less ParaView will be built (basically just `pvpython`). On Windows and macOS, only the `qt5` rendering engine is available. --Ben ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. ___ 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
Re: [Paraview] [EXTERNAL] Re: pvbatch
Alan, You should be able to run pvpython --force-offscreen-rendering script.py and no render window will appear. The help for --force-offscreen-rendering says: "If supported by the build and platform, create headless (offscreen) render windows for rendering results." I believe this should work on linux systems, but you should try it out on the system on which you want to force offscreen rendering just to be sure before using it to produce classified images. pvbatch running the same script will indeed not pop up a render window even without the --force-offscreen-rendering option. Let us know how it goes, Cory On Mon, Nov 13, 2017 at 5:04 PM, Scott, W Alan wrote: > Ben, > I believe this is a change from the past. Here is what I desire – how do > I get it? > > I want to run pv(pythonScript). I want it to produce output. I want it > to run off screen, not showing on the console display or current display. > This is especially important on classified systems. MPI is not available. > > Not too long ago, my understanding was this was pvbatch. pvpython used > either the console display or current display as it’s rendering space. > This does not catch my needs. > > Alan > > On 11/13/17, 9:04 AM, "Ben Boeckel" wrote: > > On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote: > > What are the magic cmake switches, for superbuild, that are used to > > build a non MPI, Mesa version of pvbatch? Where is this documented? > > pvpython is the non-MPI version of pvbatch. The superbuild docs could > probably be improved here. Currently, the mention is: > > ParaView supports multiple rendering engines including `egl`, > `mesa`, `osmesa`, and `qt5`. All of these are incompatible with > each > other. If none of these are chosen, a UI-less ParaView will be > built > (basically just `pvpython`). On Windows and macOS, only the `qt5` > rendering engine is available. > > --Ben > > > ___ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. ___ 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
Re: [Paraview] [EXTERNAL] Re: pvbatch
On Mon, Nov 13, 2017 at 22:04:19 +, Scott, W Alan wrote: > I believe this is a change from the past. Here is what I desire – how > do I get it? > > I want to run pv(pythonScript). I want it to produce output. I want > it to run off screen, not showing on the console display or current > display. This is especially important on classified systems. MPI is > not available. > > Not too long ago, my understanding was this was pvbatch. pvpython > used either the console display or current display as it’s rendering > space. This does not catch my needs. Yeah, it seems I was mistaken. pvbatch is not conditional on MPI. If the superbuild is built with mesa and Python and without MPI, pvbatch should be there. I've filed an MR to fix the packaging/install step in the superbuild: https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/388 --Ben ___ 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
Re: [Paraview] [EXTERNAL] Re: pvbatch
Ben, I believe this is a change from the past. Here is what I desire – how do I get it? I want to run pv(pythonScript). I want it to produce output. I want it to run off screen, not showing on the console display or current display. This is especially important on classified systems. MPI is not available. Not too long ago, my understanding was this was pvbatch. pvpython used either the console display or current display as it’s rendering space. This does not catch my needs. Alan On 11/13/17, 9:04 AM, "Ben Boeckel" wrote: On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote: > What are the magic cmake switches, for superbuild, that are used to > build a non MPI, Mesa version of pvbatch? Where is this documented? pvpython is the non-MPI version of pvbatch. The superbuild docs could probably be improved here. Currently, the mention is: ParaView supports multiple rendering engines including `egl`, `mesa`, `osmesa`, and `qt5`. All of these are incompatible with each other. If none of these are chosen, a UI-less ParaView will be built (basically just `pvpython`). On Windows and macOS, only the `qt5` rendering engine is available. --Ben ___ 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