From cory.quammen at kitware.com Thu Mar 1 08:29:34 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 1 Mar 2018 08:29:34 -0500 Subject: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1 In-Reply-To: References: <1812503415.6892.1517418997950.JavaMail.zimbra@be.itu.edu.tr> Message-ID: Joe and Ufuk, You seem to be running into the same issue as reported here: https://gitlab.kitware.com/paraview/paraview/issues/17671 Let's continue track the issue there. Best, Cory On Mon, Feb 12, 2018 at 12:24 PM, Joe Ping-Lin Hsiao wrote: > Hi Cory, > > "display.PolarAxes.Visibility = 0" does not work for me. The polar axes > comes back every time I rewind the animation. It feels like the data > visibility also applies to polar axes visibility. > > I have attached a small dataset and a simplified script for you to test, > but you have to change the data path in the script. > > BTW this is on Windows 10 64-bit. > > Best, > Joe > > > On Wed, Jan 31, 2018 at 1:09 PM, Cory Quammen > wrote: > >> Ufuk, >> >> Thanks for the report. Is there a reliable way to reproduce the >> behavior that you can share? >> >> Best, >> Cory >> >> On Wed, Jan 31, 2018 at 12:16 PM, Ufuk Turuncoglu >> wrote: >> > I don't know it is related or not. I have very similar behavior under >> 5.4.1. If i save a state and load it later, Polar Axes show up and i need >> to disable it from the properties panel. Somehow, ParaView loads Polar Axes >> even if it is not activated in the original pipeline. It might help to find >> the source of the issue. >> > >> > Best Regards, >> > >> > --ufuk >> > >> > ----- Original Message ----- >> > From: "Cory Quammen" >> > To: "Joe Ping-Lin Hsiao" >> > Cc: "paraview" >> > Sent: Wednesday, January 31, 2018 6:44:45 PM >> > Subject: Re: [Paraview] Unexpected measurement appears in 5.4.1 but not >> 5.0.1 >> > >> > Hmm, that's weird. The Polar Axes should be off by default. Do the >> > Polar Axes appear when creating a Sphere source? >> > >> > You should be able to force it off by adding the following line to the >> > loadFile() function in your script: >> > >> > display.PolarAxes.Visibility = 0 >> > >> > HTH, >> > Cory >> > >> > On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao >> wrote: >> >> Yes exactly. >> >> >> >> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen < >> cory.quammen at kitware.com> >> >> wrote: >> >>> >> >>> Hi Joe, >> >>> >> >>> Are you referring to the circular (polar axes) in the image? It says >> >>> 90.0 deg, 45.0 deg., etc. >> >>> >> >>> Thanks, >> >>> Cory >> >>> >> >>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao < >> phsiao at cs.unc.edu> >> >>> wrote: >> >>> > The attached image shows the unexpected measure with text. I tested >> two >> >>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1. >> >>> > >> >>> > 180 stacks are loaded and set to volume rendering by my Python >> script, >> >>> > which >> >>> > is also attached. >> >>> > >> >>> > Thanks, >> >>> > Joe >> >>> > >> >>> > _______________________________________________ >> >>> > 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: >> >>> > https://paraview.org/mailman/listinfo/paraview >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> Cory Quammen >> >>> Staff R&D Engineer >> >>> Kitware, Inc. >> >> >> >> >> > >> > >> > >> > -- >> > 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: >> > https://paraview.org/mailman/listinfo/paraview >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 1 09:23:54 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 1 Mar 2018 09:23:54 -0500 Subject: [Paraview] Paraview 5.5 RC build fails due to wrong python paths. In-Reply-To: References: <9426e83d265f8fe564203e21a5f4b4d8@fau.de> Message-ID: Just to close the loop, the fix is now in `master` and `release` branch and will be included in RC2. Thanks. On Wed, Feb 28, 2018 at 7:39 AM, Utkarsh Ayachit wrote: > I've reported an issue here: > https://gitlab.kitware.com/paraview/paraview/issues/18011 > I'll track it down soon. > > On Wed, Feb 28, 2018 at 7:23 AM, Utkarsh Ayachit > wrote: >> Looking into it. Thanks for reporting. What OS, flavor of Linux are >> you using? Thanks. >> >> Utkarsh >> >> On Wed, Feb 28, 2018 at 7:21 AM, Michalke, Simon wrote: >>> Hi, >>> >>> I am trying to build the latest paraview using paraview-superbuild (I set >>> the branch config to "release"). I need catalyst python wrappings and I am >>> using system python (3.4). I get the following error: >>> >>> CMake Error at VTK/Wrapping/Python/cmake_install.cmake:5822 (file): >>> file INSTALL cannot find >>> "[...]/superbuild/paraview/build/lib/python3.4/site-packages/vtk.pyc". >>> Call Stack (most recent call first): >>> VTK/cmake_install.cmake:260 (include) >>> cmake_install.cmake:118 (include) >>> >>> the .pyc and .pyo file are located here: >>> [...]/superbuild/paraview/build/lib/python3.4/site-packages/__pycache__/vtk.cpython-34.pyc >>> [...]/superbuild/paraview/build/lib/python3.4/site-packages/__pycache__/vtk.cpython-34.pyo >>> >>> I tried editing the .cmake files to fix this, which didn't work. I guess >>> they are being re-generated each time I run "make" :( >>> >>> Regards, >>> Simon >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Thu Mar 1 11:44:54 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 1 Mar 2018 11:44:54 -0500 Subject: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1 In-Reply-To: References: <1812503415.6892.1517418997950.JavaMail.zimbra@be.itu.edu.tr> Message-ID: Joe, I've pushed a merge request that should fix your issue here: https://gitlab.kitware.com/paraview/paraview/merge_requests/2296 It should be included in ParaView 5.5, due out later this month. Cory On Thu, Mar 1, 2018 at 8:29 AM, Cory Quammen wrote: > Joe and Ufuk, > > You seem to be running into the same issue as reported here: > https://gitlab.kitware.com/paraview/paraview/issues/17671 > > Let's continue track the issue there. > > Best, > Cory > > On Mon, Feb 12, 2018 at 12:24 PM, Joe Ping-Lin Hsiao > wrote: > >> Hi Cory, >> >> "display.PolarAxes.Visibility = 0" does not work for me. The polar axes >> comes back every time I rewind the animation. It feels like the data >> visibility also applies to polar axes visibility. >> >> I have attached a small dataset and a simplified script for you to test, >> but you have to change the data path in the script. >> >> BTW this is on Windows 10 64-bit. >> >> Best, >> Joe >> >> >> On Wed, Jan 31, 2018 at 1:09 PM, Cory Quammen >> wrote: >> >>> Ufuk, >>> >>> Thanks for the report. Is there a reliable way to reproduce the >>> behavior that you can share? >>> >>> Best, >>> Cory >>> >>> On Wed, Jan 31, 2018 at 12:16 PM, Ufuk Turuncoglu >>> wrote: >>> > I don't know it is related or not. I have very similar behavior under >>> 5.4.1. If i save a state and load it later, Polar Axes show up and i need >>> to disable it from the properties panel. Somehow, ParaView loads Polar Axes >>> even if it is not activated in the original pipeline. It might help to find >>> the source of the issue. >>> > >>> > Best Regards, >>> > >>> > --ufuk >>> > >>> > ----- Original Message ----- >>> > From: "Cory Quammen" >>> > To: "Joe Ping-Lin Hsiao" >>> > Cc: "paraview" >>> > Sent: Wednesday, January 31, 2018 6:44:45 PM >>> > Subject: Re: [Paraview] Unexpected measurement appears in 5.4.1 but >>> not 5.0.1 >>> > >>> > Hmm, that's weird. The Polar Axes should be off by default. Do the >>> > Polar Axes appear when creating a Sphere source? >>> > >>> > You should be able to force it off by adding the following line to the >>> > loadFile() function in your script: >>> > >>> > display.PolarAxes.Visibility = 0 >>> > >>> > HTH, >>> > Cory >>> > >>> > On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao >>> wrote: >>> >> Yes exactly. >>> >> >>> >> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen < >>> cory.quammen at kitware.com> >>> >> wrote: >>> >>> >>> >>> Hi Joe, >>> >>> >>> >>> Are you referring to the circular (polar axes) in the image? It says >>> >>> 90.0 deg, 45.0 deg., etc. >>> >>> >>> >>> Thanks, >>> >>> Cory >>> >>> >>> >>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao < >>> phsiao at cs.unc.edu> >>> >>> wrote: >>> >>> > The attached image shows the unexpected measure with text. I >>> tested two >>> >>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1. >>> >>> > >>> >>> > 180 stacks are loaded and set to volume rendering by my Python >>> script, >>> >>> > which >>> >>> > is also attached. >>> >>> > >>> >>> > Thanks, >>> >>> > Joe >>> >>> > >>> >>> > _______________________________________________ >>> >>> > 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: >>> >>> > https://paraview.org/mailman/listinfo/paraview >>> >>> > >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> >>> Staff R&D Engineer >>> >>> Kitware, Inc. >>> >> >>> >> >>> > >>> > >>> > >>> > -- >>> > 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: >>> > https://paraview.org/mailman/listinfo/paraview >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Mar 2 04:00:23 2018 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Fri, 2 Mar 2018 12:00:23 +0300 Subject: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1 In-Reply-To: References: <1812503415.6892.1517418997950.JavaMail.zimbra@be.itu.edu.tr> Message-ID: <265f0d34-76cb-8444-5123-70334a150ae6@be.itu.edu.tr> Thanks for the update. Regards, --ufuk On 1.03.2018 16:29, Cory Quammen wrote: > Joe and Ufuk, > > You seem to be running into? the same issue as reported here: > https://gitlab.kitware.com/paraview/paraview/issues/17671 > > Let's continue track the issue there. > > Best, > Cory > > On Mon, Feb 12, 2018 at 12:24 PM, Joe Ping-Lin Hsiao > > wrote: > > Hi Cory, > > "display.PolarAxes.Visibility = 0" does not work for me. The polar > axes comes back every time I rewind the animation. It feels like > the data visibility also applies to polar axes visibility. > > I have attached a small dataset and a simplified script for you to > test, but you have to change the data path in the script. > > BTW this is on Windows 10 64-bit. > > Best, > Joe > > > On Wed, Jan 31, 2018 at 1:09 PM, Cory Quammen > > wrote: > > Ufuk, > > Thanks for the report. Is there a reliable way to reproduce the > behavior that you can share? > > Best, > Cory > > On Wed, Jan 31, 2018 at 12:16 PM, Ufuk Turuncoglu > > wrote: > > I don't know it is related or not. I have very similar > behavior under 5.4.1. If i save a state and load it later, > Polar Axes show up and i need to disable it from the > properties panel. Somehow, ParaView loads Polar Axes even if > it is not activated in the original pipeline. It might help to > find the source of the issue. > > > > Best Regards, > > > > --ufuk > > > > ----- Original Message ----- > > From: "Cory Quammen" > > > To: "Joe Ping-Lin Hsiao" > > > Cc: "paraview" > > > Sent: Wednesday, January 31, 2018 6:44:45 PM > > Subject: Re: [Paraview] Unexpected measurement appears in > 5.4.1 but not 5.0.1 > > > > Hmm, that's weird. The Polar Axes should be off by default. > Do the > > Polar Axes appear when creating a Sphere source? > > > > You should be able to force it off by adding the following > line to the > > loadFile() function in your script: > > > > display.PolarAxes.Visibility = 0 > > > > HTH, > > Cory > > > > On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao > > wrote: > >> Yes exactly. > >> > >> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen > > > >> wrote: > >>> > >>> Hi Joe, > >>> > >>> Are you referring to the circular (polar axes) in the > image? It says > >>> 90.0 deg, 45.0 deg., etc. > >>> > >>> Thanks, > >>> Cory > >>> > >>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao > > > >>> wrote: > >>> > The attached image shows the unexpected measure with > text. I tested two > >>> > versions of ParaView and it only happens in 5.4.1 but > not 5.0.1. > >>> > > >>> > 180 stacks are loaded and set to volume rendering by my > Python script, > >>> > which > >>> > is also attached. > >>> > > >>> > Thanks, > >>> > Joe > >>> > > >>> > _______________________________________________ > >>> > 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: > >>> > https://paraview.org/mailman/listinfo/paraview > > >>> > > >>> > >>> > >>> > >>> -- > >>> Cory Quammen > >>> Staff R&D Engineer > >>> Kitware, Inc. > >> > >> > > > > > > > > -- > > 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: > > https://paraview.org/mailman/listinfo/paraview > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From robertsawko at gmail.com Fri Mar 2 05:40:23 2018 From: robertsawko at gmail.com (Robert Sawko) Date: Fri, 2 Mar 2018 10:40:23 +0000 Subject: [Paraview] Running pvserver on multiple GPU per node Message-ID: <20180302104023.GA28577@avignon> Hi, I have a distinct impression I already asked this question, but I can't find it in the archives. Apologies, if I am repeating myself. I am working on a cluster which has multiple GPUs per node 4-6 to be more precise. I got PV to work with EGL backend and in a client server mode and it's been a really good experience so far but one always wants more... It seems to me that I am using only one GPU even if I am running in parallel. I am looking for some advice here. I am using this website as a reference https://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node and I am using OpenMPI to do my MPI. # 1. This works for me but is using a single GPU mpirun -report-bindings -map-by core -bind-to core \ -np 20 pvserver -sp=22221 --disable-xdisplay-test # 2. This probably doesn't work, but I am not sure... mpirun -report-bindings -map-by core -bind-to core \ -np 10 pvserver -sp=22221 --disable-xdisplay-test --egl-device-index=0 : \ -np 10 pvserver -disable-xdisplay-test --egl-device-index=1 General question. Is it ok to drop -display option with EGL? With option 1. I am afraid that the process are spread out across both sockets and I think there may be a slight communication overhead between processes on one socket and the GPU plugged in on another one, but perhaps I am being paranoid. How can I measure this? With option 2: am I just abusing the syntax or this the right way to do it? nvidia-smi tells me I am using two GPUs now. How to make sure that the processes talking to an nth GPU are on bound to the right socket? Is single -sp option correct there? And perhaps a silly general question. How can I make a fair benchmark of this? Best wishes, Robert -- Ghosts of the upper atmosphere https://www.youtube.com/watch?v=D7mqs6fng7o Reference: https://en.wikipedia.org/wiki/Upper-atmospheric_lightning From jean.santiago9 at upr.edu Fri Mar 2 11:38:56 2018 From: jean.santiago9 at upr.edu (Jean C Santiago Padilla) Date: Fri, 2 Mar 2018 12:38:56 -0400 Subject: [Paraview] Flow Animation in Paraview In-Reply-To: References: Message-ID: Hello; I am working on visualization research project where I need to generate a flow animation from cfd numerical data and couple it to blender for rendering. I'm wondering if paraview software can help me with the animation process and, if so, what are the basic steps I would need to make it. Sincerely; Jean Santiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark.Olesen at esi-group.com Fri Mar 2 11:57:28 2018 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Fri, 2 Mar 2018 17:57:28 +0100 Subject: [Paraview] Flow Animation in Paraview In-Reply-To: References: Message-ID: <619161dc-7e0b-1471-c24f-e5060858ec7b@esi-group.com> I haven't done this myself, but here are a few pointers: https://holzmann-cfd.de/openfoam/openfoam-tutorials/blender-coupling https://www.youtube.com/watch?v=u-ZUJm9UtzI https://www.slideshare.net/JuliendeCharentenay/o-f-rendering-using-blender etc. On 03/02/18 17:38, Jean C Santiago Padilla via ParaView wrote: > Hello; > > ?I am working on visualization research project where I need to > generate a flow animation from cfd numerical data and couple it to > blender for rendering. I'm wondering if paraview software can help me > with the animation process and, if so, what are the basic steps I would > need to make it. > > Sincerely; > Jean Santiago -- Dr Mark OLESEN Principal Engineer, ESI-OpenCFD ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY Mob. +49 171 9710 149 www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com From jean.santiago9 at upr.edu Fri Mar 2 11:58:56 2018 From: jean.santiago9 at upr.edu (Jean C Santiago Padilla) Date: Fri, 2 Mar 2018 12:58:56 -0400 Subject: [Paraview] Flow Animation in Paraview In-Reply-To: <619161dc-7e0b-1471-c24f-e5060858ec7b@esi-group.com> References: <619161dc-7e0b-1471-c24f-e5060858ec7b@esi-group.com> Message-ID: Thanks, I'll check them out. On Mar 2, 2018 12:57 PM, "Mark Olesen" wrote: > I haven't done this myself, but here are a few pointers: > > https://holzmann-cfd.de/openfoam/openfoam-tutorials/blender-coupling > https://www.youtube.com/watch?v=u-ZUJm9UtzI > https://www.slideshare.net/JuliendeCharentenay/o-f-rendering-using-blender > > etc. > > > On 03/02/18 17:38, Jean C Santiago Padilla via ParaView wrote: > >> Hello; >> >> I am working on visualization research project where I need to generate >> a flow animation from cfd numerical data and couple it to blender for >> rendering. I'm wondering if paraview software can help me with the >> animation process and, if so, what are the basic steps I would need to make >> it. >> >> Sincerely; >> Jean Santiago >> > > > -- > Dr Mark OLESEN > Principal Engineer, ESI-OpenCFD > ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY > Mob. +49 171 9710 149 > www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Fri Mar 2 19:02:26 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Fri, 2 Mar 2018 19:02:26 -0500 Subject: [Paraview] how to make a new protocol In-Reply-To: References: Message-ID: How do I learn what to do on the client side? I see the ParaViewWebClient.createClient() function, and I see that I can add a hash of custom protocols to it, but when I try, the client complains. I tried this: const config = { sessionURL: 'ws://localhost:1234/ws' }; const smartConnect = SmartConnect.newInstance({ config }); const amsProtocols = { testbuttonService: function createMethods(session) { return { testbutton: () => { console.log("hi there ******************"); return session.call('amsprotocol.testbutton',[]) .then((result) => log('result' + result)); }, }; }, }; smartConnect.onConnectionReady((connection) => { const pvwClient = ParaViewWebClient.createClient(connection, [ 'MouseHandler', 'ViewPort', 'ViewPortImageDelivery', 'testbuttonService' // <--- I thought this... ], amsProtocols); // <--- ...was a key into this hash. No? Obviously I'm misunderstanding something here, but can someone explain what I'm missing? Where is the structure of a client described? Do I need to do any of this if all I'm trying to do is to get button presses and selection widgets to communicate with the pvpython server? Thank you, -Tom On Thu, Feb 22, 2018 at 11:49 AM, Sgouros, Thomas wrote: > Thank you, I will look at it. > > -Tom > > On Thu, Feb 22, 2018 at 11:24 AM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> LightViz will be a good example as it defines a custom set of protocols >> instead of using only the default ones like in Visualizer. >> >> https://github.com/Kitware/light-viz/tree/master/server >> >> On Thu, Feb 22, 2018 at 6:59 AM, Sgouros, Thomas < >> thomas_sgouros at brown.edu> wrote: >> >>> Hello all: >>> >>> Can someone describe the steps necessary to create and use a web socket >>> connection between a Paraviewweb client and a pvpython server? I am not >>> having much luck finding the documentation for registerVtkWebProtocol() >>> which appears to be an important part of the process. Google only helps me >>> find pvw-visualizer.py, which I'm sure is useful code, but I'm having a >>> hard time making much sense of it as an example. >>> >>> I would appreciate even just being pointed to the vtk python code, but >>> I'll take any pointers you can offer. >>> >>> Thank you, >>> >>> -Tom >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Sat Mar 3 12:10:06 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Sat, 3 Mar 2018 10:10:06 -0700 Subject: [Paraview] how to make a new protocol In-Reply-To: References: Message-ID: Hi Tom, The array list should only contain the names that belong to that directory: https://github.com/Kitware/paraviewweb/tree/master/src/IO/WebSocket/ParaViewWebClient Then your custom protocol should looks like: https://github.com/Kitware/paraviewweb/blob/master/src/IO/WebSocket/ParaViewWebClient/ProxyManager.js Except that you will need to nest it inside an object like: { CustomProtocol1: [...content of the previous example...], CustomProtocol2: [...content of the previous example...], } Then to use it you will do: client.CustomProtocol1.availableSources().then(... You can find a live example of its usage here: https://github.com/Kitware/divvy/blob/master/Sources/client.js#L27-L65 HTH, Seb On Fri, Mar 2, 2018 at 5:02 PM, Sgouros, Thomas wrote: > How do I learn what to do on the client side? I see the ParaViewWebClient.createClient() > function, and I see that I can add a hash of custom protocols to it, but > when I try, the client complains. > > I tried this: > > const config = { sessionURL: 'ws://localhost:1234/ws' }; > const smartConnect = SmartConnect.newInstance({ config }); > > const amsProtocols = { > testbuttonService: function createMethods(session) { > return { > testbutton: () => { > console.log("hi there ******************"); > return session.call('amsprotocol.testbutton',[]) > .then((result) => log('result' + result)); > }, > }; > }, > }; > > smartConnect.onConnectionReady((connection) => { > const pvwClient = > ParaViewWebClient.createClient(connection, > [ > 'MouseHandler', > 'ViewPort', > 'ViewPortImageDelivery', > 'testbuttonService' // <--- > I thought this... > ], > amsProtocols); // <--- > ...was a key into this hash. No? > > Obviously I'm misunderstanding something here, but can someone explain > what I'm missing? Where is the structure of a client described? > > Do I need to do any of this if all I'm trying to do is to get button > presses and selection widgets to communicate with the pvpython server? > > Thank you, > > -Tom > > On Thu, Feb 22, 2018 at 11:49 AM, Sgouros, Thomas < > thomas_sgouros at brown.edu> wrote: > >> Thank you, I will look at it. >> >> -Tom >> >> On Thu, Feb 22, 2018 at 11:24 AM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> LightViz will be a good example as it defines a custom set of protocols >>> instead of using only the default ones like in Visualizer. >>> >>> https://github.com/Kitware/light-viz/tree/master/server >>> >>> On Thu, Feb 22, 2018 at 6:59 AM, Sgouros, Thomas < >>> thomas_sgouros at brown.edu> wrote: >>> >>>> Hello all: >>>> >>>> Can someone describe the steps necessary to create and use a web socket >>>> connection between a Paraviewweb client and a pvpython server? I am not >>>> having much luck finding the documentation for registerVtkWebProtocol() >>>> which appears to be an important part of the process. Google only helps me >>>> find pvw-visualizer.py, which I'm sure is useful code, but I'm having a >>>> hard time making much sense of it as an example. >>>> >>>> I would appreciate even just being pointed to the vtk python code, but >>>> I'll take any pointers you can offer. >>>> >>>> Thank you, >>>> >>>> -Tom >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From acochrane at gmail.com Sat Mar 3 13:29:22 2018 From: acochrane at gmail.com (Andrew Cochrane) Date: Sat, 3 Mar 2018 11:29:22 -0700 Subject: [Paraview] undefined references to EGL library functions when using NVIDIA's libEGL_nvidia.so.384.90 Message-ID: I had a similar issue using the nvidia driver. Is this a bug? I had to add the egl, eglcore and osmesa libraries to the link lines for vtkProbeOpenGLVersion and libvtkRenderingOpenGL2-pv5.5.so.1 `-L/usr/lib/nvidia-340/ -lEGL -lnvidia-eglcore -L/usr/lib/x86_64-linux-gnu -lOSMesa` or `/usr/lib/nvidia-340/libEGL.so /usr/lib/nvidia-340/libnvidia-eglcore.so.340.104 /usr/lib/x86_64-linux-gnu/libOSMesa.so` Best, Andrew Original Message: Greetings, I'm trying to build pvserver with GPU headless rendering capability and am getting undefined references to EGL library functions when using NVIDIA's libEGL_nvidia.so.384.90 library. My cmake build specification is: cmake ../paraview \ -DVTK_USE_EGL=ON \ -DVTK_OPENGL_HAS_EGL=ON \ -DEGL_INCLUDE_DIR=/usr/include/nvidia-384 \ -DEGL_opengl_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libOpenGL.so.0 \ -DEGL_gldispatch_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libGLdispatch.so.0 \ -DEGL_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libEGL_nvidia.so.384.90 \ -DOPENGL_INCLUDE_DIR=:FILEPATH=/usr/include/nvidia-384 \ -DVTK_USE_X=OFF \ -DVTK_OPENGL_HAS_OSMESA=OFF \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DBUILD_SHARED_LIBS=ON -DPARAVIEW_USE_MPI=ON libvtkRenderingOpenGL2-pv5.4.so.1 is reporting undefined references to the egl* functions: [100%] Building CXX object CommandLineExecutables/CMakeFiles/pvserver.dir/pvserver.cxx.o [100%] Linking CXX executable ../bin/pvserver /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface' collect2: error: ld returned 1 exit status CommandLineExecutables/CMakeFiles/pvserver.dir/build.make:124: recipe for target 'bin/pvserver' failed Manually linking while specifying libEGL_nvidia.so.384.90 and libEGL.so.1 does not resolve these references either: /usr/bin/c++ -I/usr/include/nvidia-384 -g CMakeFiles/pvserver.dir/pvserver.cxx.o -o ../bin/pvserver -rd ynamic /usr/lib/nvidia-384/libEGL.so.1 ../lib/libvtkPVServerManagerApplication-pv5.4.so.1 ../lib/libvtkPVServ erManagerCore-pv5.4.so.1 ../lib/libvtkPVServerImplementationCore-pv5.4.so.1 ../lib/libvtkPVClientServerCoreCor e-pv5.4.so.1 ../lib/libvtkFiltersParallel-pv5.4.so.1 ../lib/libvtkFiltersExtraction-pv5.4.so.1 ../lib/libvtkFi ltersModeling-pv5.4.so.1 ../lib/libvtkFiltersGeometry-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsCore-pv5.4.so.1 . ./lib/libvtkPVCommon-pv5.4.so.1 ../lib/libvtkClientServer-pv5.4.so.1 ../lib/libvtkIOXMLParser-pv5.4.so.1 ../li b/libvtkFiltersSources-pv5.4.so.1 ../lib/libvtkFiltersGeneral-pv5.4.so.1 ../lib/libvtkFiltersCore-pv5.4.so.1 . ./lib/libvtkIOImage-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsSIL-pv5.4.so.1 ../lib/libvtkParallelMPI-pv5.4.so.1 ../lib/libvtkParallelCore-pv5.4.so.1 ../lib/libvtkIOLegacy-pv5.4.so.1 ../lib/libvtkIOCore-pv5.4.so.1 ../lib/li bvtkCommonExecutionModel-pv5.4.so.1 ../lib/libvtkCommonDataModel-pv5.4.so.1 ../lib/libvtkCommonSystem-pv5.4.so .1 ../lib/libvtkCommonTransforms-pv5.4.so.1 ../lib/libvtkCommonMisc-pv5.4.so.1 ../lib/libvtkCommonMath-pv5.4.s o.1 ../lib/libvtkCommonCore-pv5.4.so.1 ../lib/libprotobuf.so -lpthread ../lib/libvtkjsoncpp-pv5.4.so.1 -Wl,-rp ath,/opt/subflow/paraview/paraview_build/lib: -Wl,-rpath-link,/opt/subflow/paraview/paraview_build/lib^Cusr/li b/nvidia-384/libEGL_nvidia.so.384.90 /usr/lib/nvidia-384/libEGL.so.384.90 /usr/lib/nvidia-384/libEGL.so.1 -Wl, -rpath-link,/usr/lib/nvidia-384 /usr/lib/nvidia-384/libEGL.so /usr/lib/nvidia-384/libGL.so /usr/lib/nvidia-384 /libGLESv1_CM.so /usr/lib/nvidia-384/libGLESv2.so /usr/lib/nvidia-384/libGLX.so /usr/lib/nvidia-384/libOpenGL. so /usr/lib/nvidia-384/libnvcuvid.so /usr/lib/nvidia-384/libnvidia-cfg.so /usr/lib/nvidia-384/libnvidia-compil er.so /usr/lib/nvidia-384/libnvidia-encode.so /usr/lib/nvidia-384/libnvidia-fbc.so /usr/lib/nvidia-384/libnvid ia-ifr.so /usr/lib/nvidia-384/libnvidia-ml.so root at paraview-6dcc64f758-9nkbc :/opt/subflow/paraview/paraview_build/CommandLineExecutables# ../../link.sh /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext' /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface' collect2: error: ld returned 1 exit status Does anyone know what is going wrong here? Thanks, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Sat Mar 3 22:01:56 2018 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Sat, 3 Mar 2018 22:01:56 -0500 Subject: [Paraview] undefined references to EGL library functions when using NVIDIA's libEGL_nvidia.so.384.90 In-Reply-To: References: Message-ID: I think you might need a newer driver. We list 355.11 in https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/ Dan On Sat, Mar 3, 2018 at 1:29 PM, Andrew Cochrane wrote: > I had a similar issue using the nvidia driver. > Is this a bug? > > I had to add the egl, eglcore and osmesa libraries to the link lines for > vtkProbeOpenGLVersion and libvtkRenderingOpenGL2-pv5.5.so.1 > > `-L/usr/lib/nvidia-340/ -lEGL -lnvidia-eglcore -L/usr/lib/x86_64-linux-gnu > -lOSMesa` > or > `/usr/lib/nvidia-340/libEGL.so /usr/lib/nvidia-340/libnvidia-eglcore.so.340.104 > /usr/lib/x86_64-linux-gnu/libOSMesa.so` > > Best, > Andrew > > Original Message: > > Greetings, > > I'm trying to build pvserver with GPU headless rendering capability and > > am getting undefined references to EGL library functions when using > > NVIDIA's libEGL_nvidia.so.384.90 library. My cmake build specification > > is: > > cmake ../paraview \ > > -DVTK_USE_EGL=ON \ > > -DVTK_OPENGL_HAS_EGL=ON \ > > -DEGL_INCLUDE_DIR=/usr/include/nvidia-384 \ > > -DEGL_opengl_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libOpenGL.so.0 \ > > -DEGL_gldispatch_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libGLdispatch.so.0 \ > > -DEGL_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libEGL_nvidia.so.384.90 \ > > -DOPENGL_INCLUDE_DIR=:FILEPATH=/usr/include/nvidia-384 \ > > -DVTK_USE_X=OFF \ > > -DVTK_OPENGL_HAS_OSMESA=OFF \ > > -DPARAVIEW_BUILD_QT_GUI=OFF \ > > -DBUILD_SHARED_LIBS=ON -DPARAVIEW_USE_MPI=ON > > libvtkRenderingOpenGL2-pv5.4.so.1 is reporting undefined references to > > the egl* functions: > > [100%] Building CXX object CommandLineExecutables/CMakeFiles/pvserver.dir/pvserver.cxx.o > > [100%] Linking CXX executable ../bin/pvserver > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface' > > collect2: error: ld returned 1 exit status > > CommandLineExecutables/CMakeFiles/pvserver.dir/build.make:124: recipe for target 'bin/pvserver' failed > > Manually linking while specifying libEGL_nvidia.so.384.90 and > > libEGL.so.1 does not resolve these references either: > > /usr/bin/c++ -I/usr/include/nvidia-384 -g CMakeFiles/pvserver.dir/pvserver.cxx.o -o ../bin/pvserver -rd > > ynamic /usr/lib/nvidia-384/libEGL.so.1 ../lib/libvtkPVServerManagerApplication-pv5.4.so.1 ../lib/libvtkPVServ > > erManagerCore-pv5.4.so.1 ../lib/libvtkPVServerImplementationCore-pv5.4.so.1 ../lib/libvtkPVClientServerCoreCor > > e-pv5.4.so.1 ../lib/libvtkFiltersParallel-pv5.4.so.1 ../lib/libvtkFiltersExtraction-pv5.4.so.1 ../lib/libvtkFi > > ltersModeling-pv5.4.so.1 ../lib/libvtkFiltersGeometry-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsCore-pv5.4.so.1 . > > ./lib/libvtkPVCommon-pv5.4.so.1 ../lib/libvtkClientServer-pv5.4.so.1 ../lib/libvtkIOXMLParser-pv5.4.so.1 ../li > > b/libvtkFiltersSources-pv5.4.so.1 ../lib/libvtkFiltersGeneral-pv5.4.so.1 ../lib/libvtkFiltersCore-pv5.4.so.1 . > > ./lib/libvtkIOImage-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsSIL-pv5.4.so.1 ../lib/libvtkParallelMPI-pv5.4.so.1 > > ../lib/libvtkParallelCore-pv5.4.so.1 ../lib/libvtkIOLegacy-pv5.4.so.1 ../lib/libvtkIOCore-pv5.4.so.1 ../lib/li > > bvtkCommonExecutionModel-pv5.4.so.1 ../lib/libvtkCommonDataModel-pv5.4.so.1 ../lib/libvtkCommonSystem-pv5.4.so > > .1 ../lib/libvtkCommonTransforms-pv5.4.so.1 ../lib/libvtkCommonMisc-pv5.4.so.1 ../lib/libvtkCommonMath-pv5.4.s > > o.1 ../lib/libvtkCommonCore-pv5.4.so.1 ../lib/libprotobuf.so -lpthread ../lib/libvtkjsoncpp-pv5.4.so.1 -Wl,-rp > > ath,/opt/subflow/paraview/paraview_build/lib: -Wl,-rpath-link,/opt/subflow/paraview/paraview_build/lib^Cusr/li > > b/nvidia-384/libEGL_nvidia.so.384.90 /usr/lib/nvidia-384/libEGL.so.384.90 /usr/lib/nvidia-384/libEGL.so.1 -Wl, > > -rpath-link,/usr/lib/nvidia-384 /usr/lib/nvidia-384/libEGL.so /usr/lib/nvidia-384/libGL.so /usr/lib/nvidia-384 > > /libGLESv1_CM.so /usr/lib/nvidia-384/libGLESv2.so /usr/lib/nvidia-384/libGLX.so /usr/lib/nvidia-384/libOpenGL. > > so /usr/lib/nvidia-384/libnvcuvid.so /usr/lib/nvidia-384/libnvidia-cfg.so /usr/lib/nvidia-384/libnvidia-compil > > er.so /usr/lib/nvidia-384/libnvidia-encode.so /usr/lib/nvidia-384/libnvidia-fbc.so /usr/lib/nvidia-384/libnvid > > ia-ifr.so /usr/lib/nvidia-384/libnvidia-ml.so > > root at paraview-6dcc64f758-9nkbc :/opt/subflow/paraview/paraview_build/CommandLineExecutables# ../../link.sh /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext' > > /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface' > > collect2: error: ld returned 1 exit status > > Does anyone know what is going wrong here? > > Thanks, > > Chris > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From banesulli at gmail.com Sun Mar 4 02:20:39 2018 From: banesulli at gmail.com (Bane Sullivan) Date: Sun, 4 Mar 2018 02:20:39 -0500 Subject: [Paraview] pvpython IPython/Jupyter Kernel Message-ID: Would it be possible to create an ipython or Jupyter notebook kernel for pvpython? -------------- next part -------------- An HTML attachment was scrubbed... URL: From spal at sanjeebpal.com Mon Mar 5 01:03:58 2018 From: spal at sanjeebpal.com (SanjeebPal) Date: Mon, 5 Mar 2018 01:03:58 -0500 Subject: [Paraview] Writing selected boundary value profiles over all time steps Message-ID: <090c75f6-2f6d-f8ae-adce-3c9651388c31@sanjeebpal.com> How do I write a profile for a calculated solution quantity on a set of selected boundary faces for all available time steps ? I need the the profile to list the boundary face centroid coordinates and the calculated value. -- Sanjeeb Pal, PE Email: spal at sanjeebpal.com Phone: (703) 829-3482 | Fax: (703) 829-3376 IMPORTANT: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Mon Mar 5 11:15:35 2018 From: jhaase1 at nd.edu (John Haase) Date: Mon, 5 Mar 2018 11:15:35 -0500 Subject: [Paraview] Using paraview.simple in external Python Message-ID: Hello, I realize this question has an answer in the Wiki and been asked previously . However, I am still having issues. I did a fresh install of ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit but in C:\Program Files\ParaView 5.4.0-Qt5-OpenGL2-Windows-64bit, I only have bin data doc share Uninstall.exe according to the Wiki, I should have a lib folder. I tried adding bin\lib and bin\lib\site-packages but I still get the error ModuleNotFoundError: No module named 'paraview' In my external Python IDE (Spyder). So how do I get Spyder to recognize Paraview (prefered) or Paraview to use the panda library on my system (acceptable)? Regards, John R. Haase jhaase1 at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From zdodson at umich.edu Mon Mar 5 15:00:43 2018 From: zdodson at umich.edu (Zackary Dodson) Date: Mon, 5 Mar 2018 15:00:43 -0500 Subject: [Paraview] Loading Annotations for Categorical Colors Message-ID: <4111acf0-3d8e-ec2d-9896-400de03cedf7@umich.edu> Hello, I am having some trouble loading annotations from saved presets for categorical color schemes. After checking the "Interpret Values as Categories" box in the Color Map Editor pane and then editing the Annotations list to include my desired colors, values, and annotations (labels for each color), I save the color scheme as a preset (making sure to check the box to save the annotations). Then, when I want to reload the color preset later (after the annotations list has been cleared), I click the "Choose preset" button (folder with a heart) and scroll down to my saved preset. I make sure that the box for loading the annotations is checked and apply the preset. The colors are loaded but not the associated values and annotations (labels). What I need is the associated values and labels to show up when I load the custom preset. Looking at the .json file that is created when exporting the preset, the values and labels are present, but are just not being loaded when the preset is applied (and again, I am making sure to check the box to load the annotations when applying the preset). Is there a bug with this feature or am I doing the procedure incorrectly? Thanks, Zack From utkarsh.ayachit at kitware.com Mon Mar 5 18:33:54 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 5 Mar 2018 18:33:54 -0500 Subject: [Paraview] Loading Annotations for Categorical Colors In-Reply-To: <4111acf0-3d8e-ec2d-9896-400de03cedf7@umich.edu> References: <4111acf0-3d8e-ec2d-9896-400de03cedf7@umich.edu> Message-ID: Zack, This sounds like this bug: https://gitlab.kitware.com/paraview/paraview/issues/17977 It has been fixed in upcoming 5.5. The release candidates should be out soon. Utkarsh On Mon, Mar 5, 2018 at 3:00 PM, Zackary Dodson wrote: > Hello, > > I am having some trouble loading annotations from saved presets for > categorical color schemes. After checking the "Interpret Values as > Categories" box in the Color Map Editor pane and then editing the > Annotations list to include my desired colors, values, and annotations > (labels for each color), I save the color scheme as a preset (making sure to > check the box to save the annotations). Then, when I want to reload the > color preset later (after the annotations list has been cleared), I click > the "Choose preset" button (folder with a heart) and scroll down to my saved > preset. I make sure that the box for loading the annotations is checked and > apply the preset. The colors are loaded but not the associated values and > annotations (labels). What I need is the associated values and labels to > show up when I load the custom preset. Looking at the .json file that is > created when exporting the preset, the values and labels are present, but > are just not being loaded when the preset is applied (and again, I am making > sure to check the box to load the annotations when applying the preset). Is > there a bug with this feature or am I doing the procedure incorrectly? > > Thanks, > Zack > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview From aguirre.utn at gmail.com Tue Mar 6 01:59:00 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Tue, 6 Mar 2018 07:59:00 +0100 Subject: [Paraview] XML Drop down list problem Message-ID: Hello, I?m trying to do a Programmable Source with a drop down list like this (?ParametricSource? plugin example): https://github.com/themiwi/ParaView/blob/master/Examples/Plugins/ParametricSource/ParametricSource.xml Where the displayed properties menu depends on the selected option in the drop down list. My goal is to allow to set some variables of the Python executed script depending on the user?s first drop down selection. My code is very similar to the classic HelixSource : https://github.com/themiwi/ParaView/blob/master/Examples/Plugins/HelixSource/helix.xml However, the ParametricSource XML seems to work only with parametric functions. I cannot find the way to adapt it for the Helix Programable Source. Do you have some idea for solving this problem? Thanks in advance. Miguel Angel AGUIRRE . -------------- next part -------------- An HTML attachment was scrubbed... URL: From neuss at math.fau.de Tue Mar 6 04:16:25 2018 From: neuss at math.fau.de (Nicolas Neuss) Date: Tue, 06 Mar 2018 10:16:25 +0100 Subject: [Paraview] Bad VTK-File? Message-ID: <87fu5dva1i.fsf@math.fau.de> Hello, I have the following VTK-File --8<---------------cut here---------------start------------->8--- -------------- next part -------------- A non-text attachment was scrubbed... Name: output.vtk Type: application/octet-stream Size: 1347 bytes Desc: not available URL: -------------- next part -------------- --8<---------------cut here---------------end--------------->8--- which Paraview cannot read correctly: Generic Warning: In /build/paraview-cUuDbQ/paraview-5.1.2+dfsg1/VTK/IO/Legacy/vtkDataReader.cxx, line 1351 Error reading ascii data. Possible mismatch of datasize with declaration. The problem is with the VECTORS part at the end, but I have tried several variations (also playing around with number formats) and cannot get it to work (that is, the above message pertains and the vector field is not correctly displayed). Do you see which modification is necessary to make it work? Thank you for any help, Nicolas Remark: I want to have a vector for each of the 16 points of a 2x2 square mesh. Some points occur more than once which allows to draw discontinuous data. From M.Deij at marin.nl Tue Mar 6 04:30:25 2018 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Tue, 6 Mar 2018 09:30:25 +0000 Subject: [Paraview] Bad VTK-File? In-Reply-To: <87fu5dva1i.fsf@math.fau.de> References: <87fu5dva1i.fsf@math.fau.de> Message-ID: <0532f2c5c6974618867ca7a6b30826bb@MAR190n2.marin.local> File format described here https://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf For the VECTORS you do not need the second line with LOOKUP_TABLE: VECTORS H float 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 1.0 1.0 0.0 dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | MARIN Software Group MARIN | T +31 317 49 35 06 | mailto:M.Deij at marin.nl | http://www.marin.nl MARIN news: http://www.marin.nl/web/News/News-items/ReFRESCO-successfully-coupled-to-ParaView-Catalyst-for-insitu-analysis.htm -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Nicolas Neuss Sent: Tuesday, March 06, 2018 10:16 AM To: paraview at public.kitware.com Subject: [Paraview] Bad VTK-File? Hello, I have the following VTK-File --8<---------------cut here---------------start------------->8--- From neuss at math.fau.de Tue Mar 6 04:47:40 2018 From: neuss at math.fau.de (Nicolas Neuss) Date: Tue, 06 Mar 2018 10:47:40 +0100 Subject: [Paraview] Bad VTK-File? In-Reply-To: <0532f2c5c6974618867ca7a6b30826bb@MAR190n2.marin.local> (Deij-van Rijswijk's message of "Tue, 6 Mar 2018 09:30:25 +0000") References: <87fu5dva1i.fsf@math.fau.de> <0532f2c5c6974618867ca7a6b30826bb@MAR190n2.marin.local> Message-ID: <877eqpv8lf.fsf@math.fau.de> "Deij-van Rijswijk, Menno" writes: > File format described here https://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf > > For the VECTORS you do not need the second line with LOOKUP_TABLE: Stupid me... Thank you very much! Nicolas From Amine.Aboufirass at deltares.nl Tue Mar 6 09:53:42 2018 From: Amine.Aboufirass at deltares.nl (Amine Aboufirass) Date: Tue, 6 Mar 2018 14:53:42 +0000 Subject: [Paraview] Cube Axes Visbility no longer available? Message-ID: Hi, According to this link (https://www.paraview.org/ParaView/Doc/Nightly/www/py-doc/api-changes.html), Cube Axes Visibility is now removed from the API. Why has this been removed? It seems to be an essential feature to give some idea of dimensions in rendered output. What are different alternatives that I can use with the API? I really need some sort of ruler in my output windows. Thanks, Amine Aboufirass DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Amine.Aboufirass at deltares.nl Tue Mar 6 09:53:42 2018 From: Amine.Aboufirass at deltares.nl (Amine Aboufirass) Date: Tue, 6 Mar 2018 14:53:42 +0000 Subject: [Paraview] Cube Axes Visbility no longer available? Message-ID: Hi, According to this link (https://www.paraview.org/ParaView/Doc/Nightly/www/py-doc/api-changes.html), Cube Axes Visibility is now removed from the API. Why has this been removed? It seems to be an essential feature to give some idea of dimensions in rendered output. What are different alternatives that I can use with the API? I really need some sort of ruler in my output windows. Thanks, Amine Aboufirass DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 6 10:13:14 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 6 Mar 2018 10:13:14 -0500 Subject: [Paraview] Cube Axes Visbility no longer available? In-Reply-To: References: Message-ID: Amine, Never fear, a new and improved version of Cube Axes is available. See this blog post for details: https://blog.kitware.com/bringing-back-cube-axes-sort-of/ Cory On Tue, Mar 6, 2018 at 9:53 AM, Amine Aboufirass < Amine.Aboufirass at deltares.nl> wrote: > Hi, > > > > According to this link (https://www.paraview.org/ > ParaView/Doc/Nightly/www/py-doc/api-changes.html), *Cube Axes Visibility* > is now removed from the API. Why has this been removed? It seems to be an > essential feature to give some idea of dimensions in rendered output. > > > > What are different alternatives that I can use with the API? I really need > some sort of ruler in my output windows. > > > > Thanks, > > > > *Amine Aboufirass* > DISCLAIMER: This message is intended exclusively for the addressee(s) and > may contain confidential and privileged information. If you are not the > intended recipient please notify the sender immediately and destroy this > message. Unauthorized use, disclosure or copying of this message is > strictly prohibited. The foundation 'Stichting Deltares', which has its > seat at Delft, The Netherlands, Commercial Registration Number 41146461, is > not liable in any way whatsoever for consequences and/or damages resulting > from the improper, incomplete and untimely dispatch, receipt and/or content > of this e-mail. > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 6 10:13:14 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 6 Mar 2018 10:13:14 -0500 Subject: [Paraview] Cube Axes Visbility no longer available? In-Reply-To: References: Message-ID: Amine, Never fear, a new and improved version of Cube Axes is available. See this blog post for details: https://blog.kitware.com/bringing-back-cube-axes-sort-of/ Cory On Tue, Mar 6, 2018 at 9:53 AM, Amine Aboufirass < Amine.Aboufirass at deltares.nl> wrote: > Hi, > > > > According to this link (https://www.paraview.org/ > ParaView/Doc/Nightly/www/py-doc/api-changes.html), *Cube Axes Visibility* > is now removed from the API. Why has this been removed? It seems to be an > essential feature to give some idea of dimensions in rendered output. > > > > What are different alternatives that I can use with the API? I really need > some sort of ruler in my output windows. > > > > Thanks, > > > > *Amine Aboufirass* > DISCLAIMER: This message is intended exclusively for the addressee(s) and > may contain confidential and privileged information. If you are not the > intended recipient please notify the sender immediately and destroy this > message. Unauthorized use, disclosure or copying of this message is > strictly prohibited. The foundation 'Stichting Deltares', which has its > seat at Delft, The Netherlands, Commercial Registration Number 41146461, is > not liable in any way whatsoever for consequences and/or damages resulting > from the improper, incomplete and untimely dispatch, receipt and/or content > of this e-mail. > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tlturton at lanl.gov Tue Mar 6 09:29:48 2018 From: tlturton at lanl.gov (Turton, Terry) Date: Tue, 6 Mar 2018 14:29:48 +0000 Subject: [Paraview] Reading AMReX directories Message-ID: I am getting an error when trying to read AMReX plt* directories: ERROR: In C:\bbd\7cc78367\source-paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 784 vtkPVCompositeDataPipeline (000000000A7A0D40): Algorithm vtkAMReXParticlesReader(000000000A5FDFE0) returned failure for request: vtkInformation (000000000A776280) Debug: Off Modified Time: 262059 Reference Count: 1 Registered Events: (none) Request: REQUEST_INFORMATION FORWARD_DIRECTION: 0 ALGORITHM_AFTER_FORWARD: 1 I saw the recent update for https://gitlab.kitware.com/paraview/paraview/issues/17998 and am using the latest nightly build (PV 5.5) for Windows. I am trying to read a WARPX AMReX plt* directory but also tried it on the MFiX-Exa dataset in the testing folder with the same results. Am I missing something? Thanks, Terry ------ Terece Turton, Ph.D. Staff Scientist Data Science at Scale Team, CCS-7 Los Alamos National Laboratory 512-415-7305 (c) -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 6 10:40:52 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 6 Mar 2018 10:40:52 -0500 Subject: [Paraview] Reading AMReX directories In-Reply-To: References: Message-ID: Terry, send me your sample dataset and I can see what's going on. Utkarsh On Tue, Mar 6, 2018 at 9:29 AM, Turton, Terry wrote: > I am getting an error when trying to read AMReX plt* directories: > > > ERROR: In > C:\bbd\7cc78367\source-paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, > line 784 > vtkPVCompositeDataPipeline (000000000A7A0D40): Algorithm > vtkAMReXParticlesReader(000000000A5FDFE0) returned failure for request: > vtkInformation (000000000A776280) > Debug: Off > Modified Time: 262059 > Reference Count: 1 > Registered Events: (none) > Request: REQUEST_INFORMATION > FORWARD_DIRECTION: 0 > ALGORITHM_AFTER_FORWARD: 1 > > I saw the recent update for > https://gitlab.kitware.com/paraview/paraview/issues/17998 and am using the > latest nightly build (PV 5.5) for Windows. I am trying to read a WARPX > AMReX plt* directory but also tried it on the MFiX-Exa dataset in the > testing folder with the same results. Am I missing something? > > > Thanks, > > Terry > > > ------ > > Terece Turton, Ph.D. > > Staff Scientist > > Data Science at Scale Team, CCS-7 > > Los Alamos National Laboratory > > 512-415-7305 (c) > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From tlturton at lanl.gov Tue Mar 6 11:10:00 2018 From: tlturton at lanl.gov (Turton, Terry) Date: Tue, 6 Mar 2018 16:10:00 +0000 Subject: [Paraview] Reading AMReX directories In-Reply-To: References: , Message-ID: <5c229516cdab40419ff87d28ebcdfa7d@lanl.gov> Utkarsh, I am sending it via LANL transfer, look for it in a little bit. The MFIX-Exa data was the data in para/view/Testing/Data/AMReX-MFIX/plt*. thanks, Terry * ________________________________ From: Utkarsh Ayachit Sent: Tuesday, March 6, 2018 9:40:52 AM To: Turton, Terry Cc: paraview at public.kitware.com Subject: Re: [Paraview] Reading AMReX directories Terry, send me your sample dataset and I can see what's going on. Utkarsh On Tue, Mar 6, 2018 at 9:29 AM, Turton, Terry wrote: > I am getting an error when trying to read AMReX plt* directories: > > > ERROR: In > C:\bbd\7cc78367\source-paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, > line 784 > vtkPVCompositeDataPipeline (000000000A7A0D40): Algorithm > vtkAMReXParticlesReader(000000000A5FDFE0) returned failure for request: > vtkInformation (000000000A776280) > Debug: Off > Modified Time: 262059 > Reference Count: 1 > Registered Events: (none) > Request: REQUEST_INFORMATION > FORWARD_DIRECTION: 0 > ALGORITHM_AFTER_FORWARD: 1 > > I saw the recent update for > https://gitlab.kitware.com/paraview/paraview/issues/17998 and am using the > latest nightly build (PV 5.5) for Windows. I am trying to read a WARPX > AMReX plt* directory but also tried it on the MFiX-Exa dataset in the > testing folder with the same results. Am I missing something? > > > Thanks, > > Terry > > > ------ > > Terece Turton, Ph.D. > > Staff Scientist > > Data Science at Scale Team, CCS-7 > > Los Alamos National Laboratory > > 512-415-7305 (c) > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shenrilin at gmail.com Tue Mar 6 12:00:23 2018 From: shenrilin at gmail.com (Rilin Shen) Date: Tue, 6 Mar 2018 12:00:23 -0500 Subject: [Paraview] Accessing data value using python script Message-ID: Dear all, I'm trying to get the values of some variables but failed. I have a file named PU and then tried *A=PU.PointData.values()*, it only gave me 'Array: Displacement' something like that. My question is how to obtain the value of displacements instead of "Array: Displacements"? All the best. Rilin Shen Division of Solid Mechanics, School of Astronautics *Harbin Institute of Technology*, Harbin 150001, China Civil Engineering & Engineering Mechanics *Columbia University*, New York 10027, U.S. Tel: (+1) 646-200-2122 Email: shenrilin at gmail.com / rs3741 at columbia.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 6 17:00:26 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 6 Mar 2018 17:00:26 -0500 Subject: [Paraview] Reading AMReX directories In-Reply-To: <5c229516cdab40419ff87d28ebcdfa7d@lanl.gov> References: <5c229516cdab40419ff87d28ebcdfa7d@lanl.gov> Message-ID: Terry, Looks like the structure is different with the files you sent. Let me see what's going on. Utkarsh On Tue, Mar 6, 2018 at 11:10 AM, Turton, Terry wrote: > Utkarsh, > > I am sending it via LANL transfer, look for it in a little bit. The > MFIX-Exa data was the data in para/view/Testing/Data/AMReX-MFIX/plt*. > > thanks, > > Terry > > ________________________________ > From: Utkarsh Ayachit > Sent: Tuesday, March 6, 2018 9:40:52 AM > To: Turton, Terry > Cc: paraview at public.kitware.com > Subject: Re: [Paraview] Reading AMReX directories > > Terry, send me your sample dataset and I can see what's going on. > > Utkarsh > > On Tue, Mar 6, 2018 at 9:29 AM, Turton, Terry wrote: >> I am getting an error when trying to read AMReX plt* directories: >> >> >> ERROR: In >> >> C:\bbd\7cc78367\source-paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, >> line 784 >> vtkPVCompositeDataPipeline (000000000A7A0D40): Algorithm >> vtkAMReXParticlesReader(000000000A5FDFE0) returned failure for request: >> vtkInformation (000000000A776280) >> Debug: Off >> Modified Time: 262059 >> Reference Count: 1 >> Registered Events: (none) >> Request: REQUEST_INFORMATION >> FORWARD_DIRECTION: 0 >> ALGORITHM_AFTER_FORWARD: 1 >> >> I saw the recent update for >> https://gitlab.kitware.com/paraview/paraview/issues/17998 and am using the >> latest nightly build (PV 5.5) for Windows. I am trying to read a WARPX >> AMReX plt* directory but also tried it on the MFiX-Exa dataset in the >> testing folder with the same results. Am I missing something? >> >> >> Thanks, >> >> Terry >> >> >> ------ >> >> Terece Turton, Ph.D. >> >> Staff Scientist >> >> Data Science at Scale Team, CCS-7 >> >> Los Alamos National Laboratory >> >> 512-415-7305 (c) >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> From martin.weinberg at comcast.net Tue Mar 6 18:16:53 2018 From: martin.weinberg at comcast.net (Martin Weinberg) Date: Tue, 6 Mar 2018 18:16:53 -0500 Subject: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1 Message-ID: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> I have two nearly identical machine running Ubuntu 17.10.? The both have the latest stable Paraview 5.4.1 from the download page installed in /opt. I wrote a wrapper script like this: -------------------------------------------------------------------------------------------------------------------- #!/bin/bash # PVHOME=/opt/ParaView-5.4.1-822-g597adef-Qt5-MPI-Linux-64bit PVHOME=/opt/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit export PATH=$PVHOME/bin export LD_LIBRARY_PATH=$PVHOME/lib/ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PVHOME/lib/paraview-5.4/ export PYTHONPATH=$PVHOME/lib/python2.7/bin/ export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/vtk/ export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/paraview/ $PVHOME/bin/paraview -------------------------------------------------------------------------------------------------------------------- On each machine I start paraview and load a state that has a programmable filter with the line: d0 = inputs[0].PointSet['d'] One one machine, this works just fine.? On the other machine, I get the following message in the Output: -------------------------------------------------------------------------------------------------------------------- Traceback (most recent call last): File "", line 24, in File "", line 2, in RequestData TypeError: 'NoneType' object has no attribute '__getitem__' BTW, this is just a test; obviously, my real filter does something. I assume that some module is not being loaded here, but I've tried _everything_ I could think of and I'm not making progress.? Any ideas?? -- Martin Weinberg 6 Grass Hill Rd West Whately, MA 010039 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From shawn.waldon at kitware.com Wed Mar 7 08:26:13 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 7 Mar 2018 08:26:13 -0500 Subject: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1 In-Reply-To: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> References: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> Message-ID: Hi Martin, My first guess would be that your state file is trying to load data that isn't there. Then when you run your programmable filter inputs[0] is None and you get this error message. I can't think of anything else that could be going wrong with that script, especially since it works on one of your machines. HTH, Shawn On Tue, Mar 6, 2018 at 6:16 PM, Martin Weinberg wrote: > I have two nearly identical machine running Ubuntu 17.10. The both have > the latest stable Paraview 5.4.1 from the download page installed in /opt. > > I wrote a wrapper script like this: > > ------------------------------------------------------------ > -------------------------------------------------------- > > #!/bin/bash > > # PVHOME=/opt/ParaView-5.4.1-822-g597adef-Qt5-MPI-Linux-64bit > PVHOME=/opt/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit > > export PATH=$PVHOME/bin > export LD_LIBRARY_PATH=$PVHOME/lib/ > export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PVHOME/lib/paraview-5.4/ > export PYTHONPATH=$PVHOME/lib/python2.7/bin/ > export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ > export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/vtk/ > export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site- > packages/paraview/ > > $PVHOME/bin/paraview > ------------------------------------------------------------ > -------------------------------------------------------- > > On each machine I start paraview and load a state that has a > programmable filter with the line: > > d0 = inputs[0].PointSet['d'] > > One one machine, this works just fine. On the other machine, I get the > following message in the Output: > > ------------------------------------------------------------ > -------------------------------------------------------- > > Traceback (most recent call last): File "", line 24, in File "", line 2, > in RequestData TypeError: 'NoneType' object has no attribute '__getitem__' > > BTW, this is just a test; obviously, my real filter does something. > > I assume that some module is not being loaded here, but I've tried > _everything_ I could think of and I'm not making progress. Any ideas?? > > -- > Martin Weinberg > 6 Grass Hill Rd > West Whately, MA > 010039 > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Mar 7 09:03:32 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 7 Mar 2018 09:03:32 -0500 Subject: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1 In-Reply-To: References: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> Message-ID: The only dependent package I can think of for python filters is numpy, which is used in the dataset adapter code (VTK arrays are wrapped to be numpy array-like). But that should be installed with the binaries and you should get a failed import if it is missing. Shawn On Wed, Mar 7, 2018 at 8:57 AM, Martin Weinberg wrote: > Thanks. The data is definitely loaded; e.g. I can render with an upstream > filter. > > I wonder of I'm missing some dependent package on the problem machine? > > > On March 7, 2018 8:26:13 AM EST, Shawn Waldon > wrote: >> >> Hi Martin, >> >> My first guess would be that your state file is trying to load data that >> isn't there. Then when you run your programmable filter inputs[0] is None >> and you get this error message. I can't think of anything else that could >> be going wrong with that script, especially since it works on one of your >> machines. >> >> HTH, >> Shawn >> >> On Tue, Mar 6, 2018 at 6:16 PM, Martin Weinberg < >> martin.weinberg at comcast.net> wrote: >> >>> I have two nearly identical machine running Ubuntu 17.10. The both have >>> the latest stable Paraview 5.4.1 from the download page installed in >>> /opt. >>> >>> I wrote a wrapper script like this: >>> >>> ------------------------------------------------------------ >>> -------------------------------------------------------- >>> >>> #!/bin/bash >>> >>> # PVHOME=/opt/ParaView-5.4.1-822-g597adef-Qt5-MPI-Linux-64bit >>> PVHOME=/opt/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit >>> >>> export PATH=$PVHOME/bin >>> export LD_LIBRARY_PATH=$PVHOME/lib/ >>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PVHOME/lib/paraview-5.4/ >>> export PYTHONPATH=$PVHOME/lib/python2.7/bin/ >>> export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ >>> export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/vtk/ >>> export PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ >>> paraview/ >>> >>> $PVHOME/bin/paraview >>> ------------------------------------------------------------ >>> -------------------------------------------------------- >>> >>> On each machine I start paraview and load a state that has a >>> programmable filter with the line: >>> >>> d0 = inputs[0].PointSet['d'] >>> >>> One one machine, this works just fine. On the other machine, I get the >>> following message in the Output: >>> >>> ------------------------------------------------------------ >>> -------------------------------------------------------- >>> >>> Traceback (most recent call last): File "", line 24, in File "", line 2, >>> in RequestData TypeError: 'NoneType' object has no attribute >>> '__getitem__' >>> >>> BTW, this is just a test; obviously, my real filter does something. >>> >>> I assume that some module is not being loaded here, but I've tried >>> _everything_ I could think of and I'm not making progress. Any ideas?? >>> >>> -- >>> Martin Weinberg >>> 6 Grass Hill Rd >>> >>> West Whately, MA >>> 010039 >>> >>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -- > Martin Weinberg > 6 Grass Hill Rd > > West Whately, MA > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.weinberg at comcast.net Wed Mar 7 13:05:07 2018 From: martin.weinberg at comcast.net (Martin Weinberg) Date: Wed, 7 Mar 2018 13:05:07 -0500 Subject: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1 In-Reply-To: References: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> Message-ID: <97dfa9dd-576c-1ca8-cfc3-54774526bfec@comcast.net> Okay . . . I figured out the problem but not the fix. The problem is: I installed some packages with pip, and python is prepending ~/.local/lib/python2.7/site-packages paths to PYTHONPATH even when I rewrite the that path in the shell. So if I temporarily rename ~/.local/lib/python2.7/site-packages to something else, the programmable filter works as expected. Any idea how to best handle this? On 03/07/2018 09:03 AM, Shawn Waldon wrote: > The only dependent package I can think of for python filters is numpy, > which is used in the dataset adapter code (VTK arrays are wrapped to > be numpy array-like).? But that should be installed with the binaries > and you should get a failed import if it is missing. > > Shawn > > On Wed, Mar 7, 2018 at 8:57 AM, Martin Weinberg > > wrote: > > Thanks. The data is definitely loaded; e.g. I can render with an > upstream filter. > > I wonder of I'm missing some dependent package on the problem > machine? > > > On March 7, 2018 8:26:13 AM EST, Shawn Waldon > > wrote: > > Hi Martin, > > My first guess would be that your state file is trying to load > data that isn't there.? Then when you run your programmable > filter inputs[0] is None and you get this error message.? I > can't think of anything else that could be going wrong with > that script, especially since it works on one of your machines. > > HTH, > Shawn > > On Tue, Mar 6, 2018 at 6:16 PM, Martin Weinberg > > wrote: > > I have two nearly identical machine running Ubuntu 17.10.? > The both have > the latest stable Paraview 5.4.1 from the download page > installed in /opt. > > I wrote a wrapper script like this: > > -------------------------------------------------------------------------------------------------------------------- > > #!/bin/bash > > # PVHOME=/opt/ParaView-5.4.1-822-g597adef-Qt5-MPI-Linux-64bit > PVHOME=/opt/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit > > export PATH=$PVHOME/bin > export LD_LIBRARY_PATH=$PVHOME/lib/ > export > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PVHOME/lib/paraview-5.4/ > export PYTHONPATH=$PVHOME/lib/python2.7/bin/ > export > PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ > export > PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/vtk/ > export > PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/paraview/ > > $PVHOME/bin/paraview > -------------------------------------------------------------------------------------------------------------------- > > On each machine I start paraview and load a state that has a > programmable filter with the line: > > d0 = inputs[0].PointSet['d'] > > One one machine, this works just fine.? On the other > machine, I get the > following message in the Output: > > -------------------------------------------------------------------------------------------------------------------- > > Traceback (most recent call last): File "", line 24, in > File "", line 2, > in RequestData TypeError: 'NoneType' object has no > attribute '__getitem__' > > BTW, this is just a test; obviously, my real filter does > something. > > I assume that some module is not being loaded here, but > I've tried > _everything_ I could think of and I'm not making > progress.? Any ideas?? > > -- > Martin Weinberg > 6 Grass Hill Rd > > West Whately, MA > 010039 > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Martin Weinberg > 6 Grass Hill Rd > > West Whately, MA > > -- Martin Weinberg 6 Grass Hill Rd West Whately, MA 010039 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From martin.weinberg at comcast.net Wed Mar 7 13:38:05 2018 From: martin.weinberg at comcast.net (Martin Weinberg) Date: Wed, 7 Mar 2018 13:38:05 -0500 Subject: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1 In-Reply-To: <97dfa9dd-576c-1ca8-cfc3-54774526bfec@comcast.net> References: <288f86d6-d1ef-834c-6c60-4159d4cf5d1e@comcast.net> <97dfa9dd-576c-1ca8-cfc3-54774526bfec@comcast.net> Message-ID: <32726f6f-5e8d-d0f9-f0da-fcdf282f32c4@comcast.net> An easy fix is adding: export PYTHONUSERBASE=/dev/null to my bash script that sets the LD_LIBRARY_PATH and PYTHONPATH and "wraps" the paraview invocation.?? I also tried setting PYTHONNOUSERSITE but that did not help. Thanks, Shawn for the discussion and may this help someone else down the line. On 03/07/2018 01:05 PM, Martin Weinberg wrote: > Okay . . . I figured out the problem but not the fix. > > The problem is: I installed some packages with pip, and python is > prepending ~/.local/lib/python2.7/site-packages paths to PYTHONPATH even > when I rewrite the that path in the shell. > > So if I temporarily rename ~/.local/lib/python2.7/site-packages to > something else, the programmable filter works as expected. > > Any idea how to best handle this? > > > On 03/07/2018 09:03 AM, Shawn Waldon wrote: >> The only dependent package I can think of for python filters is numpy, >> which is used in the dataset adapter code (VTK arrays are wrapped to >> be numpy array-like).? But that should be installed with the binaries >> and you should get a failed import if it is missing. >> >> Shawn >> >> On Wed, Mar 7, 2018 at 8:57 AM, Martin Weinberg >> > wrote: >> >> Thanks. The data is definitely loaded; e.g. I can render with an >> upstream filter. >> >> I wonder of I'm missing some dependent package on the problem >> machine? >> >> >> On March 7, 2018 8:26:13 AM EST, Shawn Waldon >> > wrote: >> >> Hi Martin, >> >> My first guess would be that your state file is trying to load >> data that isn't there.? Then when you run your programmable >> filter inputs[0] is None and you get this error message.? I >> can't think of anything else that could be going wrong with >> that script, especially since it works on one of your machines. >> >> HTH, >> Shawn >> >> On Tue, Mar 6, 2018 at 6:16 PM, Martin Weinberg >> > > wrote: >> >> I have two nearly identical machine running Ubuntu 17.10.? >> The both have >> the latest stable Paraview 5.4.1 from the download page >> installed in /opt. >> >> I wrote a wrapper script like this: >> >> -------------------------------------------------------------------------------------------------------------------- >> >> #!/bin/bash >> >> # PVHOME=/opt/ParaView-5.4.1-822-g597adef-Qt5-MPI-Linux-64bit >> PVHOME=/opt/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit >> >> export PATH=$PVHOME/bin >> export LD_LIBRARY_PATH=$PVHOME/lib/ >> export >> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PVHOME/lib/paraview-5.4/ >> export PYTHONPATH=$PVHOME/lib/python2.7/bin/ >> export >> PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/ >> export >> PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/vtk/ >> export >> PYTHONPATH=$PYTHONPATH:$PVHOME/lib/python2.7/site-packages/paraview/ >> >> $PVHOME/bin/paraview >> -------------------------------------------------------------------------------------------------------------------- >> >> On each machine I start paraview and load a state that has a >> programmable filter with the line: >> >> d0 = inputs[0].PointSet['d'] >> >> One one machine, this works just fine.? On the other >> machine, I get the >> following message in the Output: >> >> -------------------------------------------------------------------------------------------------------------------- >> >> Traceback (most recent call last): File "", line 24, in >> File "", line 2, >> in RequestData TypeError: 'NoneType' object has no >> attribute '__getitem__' >> >> BTW, this is just a test; obviously, my real filter does >> something. >> >> I assume that some module is not being loaded here, but >> I've tried >> _everything_ I could think of and I'm not making >> progress.? Any ideas?? >> >> -- >> Martin Weinberg >> 6 Grass Hill Rd >> >> West Whately, MA >> 010039 >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> Martin Weinberg >> 6 Grass Hill Rd >> >> West Whately, MA >> >> -- Martin Weinberg 6 Grass Hill Rd West Whately, MA 010039 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From sserebrinsky at gmail.com Thu Mar 8 00:02:05 2018 From: sserebrinsky at gmail.com (Santiago Serebrinsky) Date: Thu, 8 Mar 2018 02:02:05 -0300 Subject: [Paraview] Empty lib/python2.7/lib-dynload Message-ID: I am under Ubuntu 16.04 LTS. I have currently two versions of Paraview: 1. Paraview 5.0.1, installed with apt-get. It is using Python 2.7.12. 2. ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit, simply expanded. It uses Python 2.7.11. When I use version 2 of pvpython (~/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit/bin/pvpython) I get the error import readline ImportError: No module named readline from my ~/.pythonrc. In version 1 of pvpython, readline resides in /usr/lib/python2.7/lib-dynload >>> readline.__file__ '/usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so' . In version 2 readline is not present anywhere in ~/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit/ Why is this? Can it be fixed? PS: directory ~/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/lib-dynload (where I expected to find readline given version 1) is empty. Many of the modules which in version 1 reside in /usr/lib/python2.7/lib-dynload, are present in lib/python2.7, not in lib/python2.7/lib-dynload, in version2: >>> import parser >>> parser.__file__ '/home/santiago/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/parser.so' But readline is an exception here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jutta.Dreer at lrz.de Thu Mar 8 07:42:22 2018 From: Jutta.Dreer at lrz.de (Dreer, Jutta) Date: Thu, 8 Mar 2018 12:42:22 +0000 Subject: [Paraview] Attach Transform Filter to molecule from pdb file Message-ID: <18278cb7df1444de98edef3fcdda58da@lrz.de> Dear ParaView experts, I read a molecule from a pdb file. As a result I see one representation showing only the bonds as a polygonal object, and one ball and stick representation which appears as an object of type "unknown". I can attach a transform filter to the polygonal object, but not to the ball and stick representation. But it is important for showing the molecule in a Cave-like environment to transform objects to a specified position, so that interaction is more comfortable (in fact the molecule should appear near the origin and scaling should reduce size to about 2 units). Is there a way to achieve that? Best Regards Jutta Dreer -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Mar 8 10:27:55 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 8 Mar 2018 10:27:55 -0500 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available Message-ID: Dear ParaView developers, ParaView 5.5.0-RC2 has been tagged (tag "v5.5.0-RC2"). Binaries are also available on the ParaView downloads web page https://www.paraview.org/ download/. Please let us know if you encounter any issues with this release candidate. ParaView's superbuild has also been tagged with "v5.5.0-RC2". Thank you, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 8 10:31:58 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 8 Mar 2018 10:31:58 -0500 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: Message-ID: BTW, if your browser doesn't show the 5.5 category, you may just need to "hard refresh" the page. On Chrome, it's "Ctrl + F5", for example. Utkarsh On Thu, Mar 8, 2018 at 10:27 AM, Cory Quammen wrote: > Dear ParaView developers, > > ParaView 5.5.0-RC2 has been tagged (tag "v5.5.0-RC2"). Binaries are also > available on the ParaView downloads web page > https://www.paraview.org/download/. > > Please let us know if you encounter any issues with this release candidate. > > ParaView's superbuild has also been tagged with "v5.5.0-RC2". > > Thank you, > Cory > > -- > 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: > https://public.kitware.com/mailman/listinfo/paraview > From ow222 at cam.ac.uk Thu Mar 8 11:26:19 2018 From: ow222 at cam.ac.uk (Oscar Wilsby) Date: Thu, 8 Mar 2018 16:26:19 +0000 Subject: [Paraview] =?utf-8?q?=E2=80=9CUpload=E2=80=9D_vtk_data_from_clie?= =?utf-8?q?nt_to_server_in_paraview_script?= Message-ID: <8B9CC6A6-F189-4FF2-8B53-62BC85ACA069@cam.ac.uk> Dear all, I am relatively new to scripting in paraview using vtk wrappers. However one situation I always find myself in is writing a python script to be executed with pvpython and then having to include a miniature python script as an input to programmableFilters. As far as I understand, this allows the manipulation of pipeline data on the server side (so you don't have to retrieve data to the client) inside a tailored script. What I don't understand is why the process has to be so convoluted. At the very least it makes debugging very annoying as you don't know exactly where in the script that you input into the programmable filter a potential error might be. I have an example to illustrate. Below are two pieces of code within an if/else switch where I add some temperature data to a vtkSphereSource. The first uses the programmableFilter approach and the second attempts to do the manipulation on the client side and then "upload/update" the server side. However the second approach does not result in any temperature data when I view it in paraview. What am I missing? from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() import math import vtk use_prog_filt = False # What I dont want to be doing: if use_prog_filt: sphereSourceProxy = Sphere() renderView1 = GetActiveViewOrCreate('RenderView') sphereDisplay = Show(sphereSourceProxy, renderView1) sphereDisplay.ColorArrayName = [None, ''] renderView1.ResetCamera() my_script= [ 'pdi = self.GetPolyDataInput()', 'pdo = self.GetPolyDataOutput()', '', 'temperature= vtk.vtkDoubleArray()', 'npoints = pdi.GetNumberOfPoints() ', 'for i in range(npoints):', ' x, y, z = pdi.GetPoint(i)', ' temperature.InsertNextValue(x)', 'temperature.SetName("Temperature")', 'pdo.GetPointData().AddArray(temperature)'] programmableFilter = ProgrammableFilter(Input=sphereSourceProxy) programmableFilter.Script = str("\n".join(my_script)) programmableFilter.RequestInformationScript = '' programmableFilter.RequestUpdateExtentScript = '' programmableFilter.PythonPath = '' programmableFilterDisplay = Show(programmableFilter, renderView1) # What I want to be doing: else: #sphereSource = vtk.vtkSphereSource() #print dir(sphereSource) sphereSourceProxy = Sphere() renderView1 = GetActiveViewOrCreate('RenderView') sphereDisplay = Show(sphereSourceProxy, renderView1) sphereDisplay.ColorArrayName = [None, ''] renderView1.ResetCamera() pdi = servermanager.Fetch(input=sphereSourceProxy) npoints = pdi.GetNumberOfPoints() temperature = vtk.vtkDoubleArray() temperature.SetName("Temperature") for i in range(npoints): x, y, z = pdi.GetPoint(i) temperature.InsertNextValue(x) pdi.GetPointData().AddArray(temperature) new_SphereSource = TrivialProducer() filt = new_SphereSource.GetClientSideObject() # filter is a vtkTrivialProducer filt.SetOutput(pdi) new_SphereSource.UpdatePipeline() # The temperature data is available, but not in the paraview renderview... print servermanager.Fetch(input=new_SphereSource) -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.coutinho at redstack.nl Thu Mar 8 12:13:03 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Thu, 8 Mar 2018 17:13:03 +0000 Subject: [Paraview] Utilizing Server GPU from an external command Message-ID: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: c.coutinho at redstack.nl www: www.redstack.nl From Angus.Lock at ff.com Thu Mar 8 14:48:55 2018 From: Angus.Lock at ff.com (Angus Lock) Date: Thu, 8 Mar 2018 19:48:55 +0000 Subject: [Paraview] OSPRay in version 5.5-RC2 Message-ID: <912615c2e76b43c6b07e19a17266c403@ff.com> I can't seem to see any reference to OSPRay options in the Properties panel any more. Is there a command line argument or option to enable it? Thanks, Angus Lock Sr. Manager - Aerodynamics | R&D e angus.lock at faradayfuture.com c 310 293 5902 [https://wiki.faradayfuture.com/images/signatureLogo.png] a 18455 S Figueroa St, Gardena, CA 90248 w www.faradayfuture.com ________________________________ FF, inc. email may include content, whether in the body of an email or in an attachment, that is intended to be confidential. Delivery of confidential material by email not does not diminish the confidential nature of such material. All persons who believe that they have erroneously received any FF, inc. email are requested to delete such email, including any attachments. Any non-business, personal use of FF, inc. email system is solely the responsibility of the sender, and none of the content of any such email is to be attributed to FF, inc. No one who receives an email purportedly from FF, inc. should rely on the authenticity or completeness of that email, unless it is received directly from FF, inc.. No person is entitled to copy, forward or otherwise re-use any material contained in any FF, inc. email, without FF, inc.'s express written permission. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2469 bytes Desc: image001.png URL: From dave.demarle at kitware.com Thu Mar 8 15:07:22 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 8 Mar 2018 15:07:22 -0500 Subject: [Paraview] OSPRay in version 5.5-RC2 In-Reply-To: <912615c2e76b43c6b07e19a17266c403@ff.com> References: <912615c2e76b43c6b07e19a17266c403@ff.com> Message-ID: Was this with the windows binary? We had a compilation issue there that snuck and late and we fixed too late for RC2. It is fixed in master and will be fixed before 5.5.0.final. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 8, 2018 at 2:48 PM, Angus Lock wrote: > I can?t seem to see any reference to OSPRay options in the Properties > panel any more. Is there a command line argument or option to enable it? > > > > Thanks, > > > > *Angus Lock* > Sr. Manager - Aerodynamics | R&D > > *e *angus.lock at faradayfuture.com > *c *310 293 5902 <(310)%20293-5902> > > [image: https://wiki.faradayfuture.com/images/signatureLogo.png] > > *a *18455 S Figueroa St, Gardena, CA 90248 > *w *www.faradayfuture.com > > ------------------------------ > > FF, inc. email may include content, whether in the body of an email or in > an attachment, that is intended to be confidential. Delivery of > confidential material by email not does not diminish the confidential > nature of such material. All persons who believe that they have erroneously > received any FF, inc. email are requested to delete such email, including > any attachments. Any non-business, personal use of FF, inc. email system is > solely the responsibility of the sender, and none of the content of any > such email is to be attributed to FF, inc. No one who receives an email > purportedly from FF, inc. should rely on the authenticity or completeness > of that email, unless it is received directly from FF, inc.. No person is > entitled to copy, forward or otherwise re-use any material contained in any > FF, inc. email, without FF, inc.?s express written permission. > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2469 bytes Desc: not available URL: From Angus.Lock at ff.com Thu Mar 8 15:09:17 2018 From: Angus.Lock at ff.com (Angus Lock) Date: Thu, 8 Mar 2018 20:09:17 +0000 Subject: [Paraview] [EXTERNAL] Re: OSPRay in version 5.5-RC2 In-Reply-To: References: <912615c2e76b43c6b07e19a17266c403@ff.com> Message-ID: It was, thanks for the info. Angus Lock Sr. Manager - Aerodynamics | R&D Faraday Future e angus.lock at faradayfuture.com c 310 293 5902 From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, March 08, 2018 12:07 PM To: Angus Lock Cc: paraview at public.kitware.com Subject: [EXTERNAL] Re: [Paraview] OSPRay in version 5.5-RC2 Was this with the windows binary? We had a compilation issue there that snuck and late and we fixed too late for RC2. It is fixed in master and will be fixed before 5.5.0.final. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 8, 2018 at 2:48 PM, Angus Lock > wrote: I can?t seem to see any reference to OSPRay options in the Properties panel any more. Is there a command line argument or option to enable it? Thanks, Angus Lock Sr. Manager - Aerodynamics | R&D e angus.lock at faradayfuture.com c 310 293 5902 [https://wiki.faradayfuture.com/images/signatureLogo.png] a 18455 S Figueroa St, Gardena, CA 90248 w www.faradayfuture.com ________________________________ FF, inc. email may include content, whether in the body of an email or in an attachment, that is intended to be confidential. Delivery of confidential material by email not does not diminish the confidential nature of such material. All persons who believe that they have erroneously received any FF, inc. email are requested to delete such email, including any attachments. Any non-business, personal use of FF, inc. email system is solely the responsibility of the sender, and none of the content of any such email is to be attributed to FF, inc. No one who receives an email purportedly from FF, inc. should rely on the authenticity or completeness of that email, unless it is received directly from FF, inc.. No person is entitled to copy, forward or otherwise re-use any material contained in any FF, inc. email, without FF, inc.?s express written permission. _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2469 bytes Desc: image001.png URL: From info at paraview-expert.com Thu Mar 8 16:21:44 2018 From: info at paraview-expert.com (Magician) Date: Fri, 9 Mar 2018 06:21:44 +0900 Subject: [Paraview] Set total recording time in VeloView In-Reply-To: References: <2998C114-95C6-4593-8084-47B6E7381989@paraview-expert.com> Message-ID: <336D66E1-265B-4CCE-AC4D-465E0A3DA064@paraview-expert.com> Hi Bastien, Sorry for the delay in my reply. I understand how to use. I think the technique is very usable. Magician > 2018/02/28 20:01?Bastien Jacquet wrote: > > Hello, > > The script toggles the recording state after the desired waiting time. > Hence: > If you launch it from non-recording state, it will start recording after recordingTimeInMilliseconds. > If you launch it from recording state, it will stop recording after recordingTimeInMilliseconds. > > Best, > > > Bastien Jacquet, PhD > Technical Leader - Computer Vision Team > Kitware SAS > 26 rue Louis Gu?rin - 69100 Villeurbanne - France > F: +33 (0)4.37.45.04.15 > > On Tue, Feb 27, 2018 at 3:23 PM, Magician > wrote: > Hi Bastien, > > > I tried your script, but the recordingTimeInMilliseconds takes > waiting time ?before' data logging. > I want to set data logging time (begin to end). > > > Magician > > >> 2018/02/16 18:48?Bastien Jacquet > wrote: >> >> Sorry, I should have doubled checked >> You need to use .trigger() instead of .toggle(). >> This is the code that works: >> >> def myfunc(): >> vv.app.actions['actionRecord'].trigger() >> print ("Toggled recording") >> >> qq=QtCore.QTimer() >> qq.setSingleShot(True) >> qq.connect('timeout()',myfunc) >> recordingTimeInMilliseconds = 60 * 1000 >> qq.start(recordingTimeInMilliseconds) >> >> Best, >> >> Bastien Jacquet, PhD >> Technical Leader - Computer Vision Team >> Kitware SAS >> 26 rue Louis Gu?rin - 69100 Villeurbanne - France >> F: +33 (0)4.37.45.04.15 >> On Thu, Feb 15, 2018 at 9:36 PM, Magician > wrote: >> Hi Bastien, >> >> >> Thanks for your advice. >> I tried the script and the button is toggled on the GUI, but no data is recorded. >> >> >> Magician >> >> >>> 2018/02/15 3:03?Bastien Jacquet > wrote: >>> >>> Hello Magician, >>> >>> I think you can use Python, and PythonQt to make a fake "record" button press, after the desired amount of time. >>> Just try this: >>> def myfunc(): >>> vv.app.actions['actionRecord'].toggle() >>> print ("Toggled recording") >>> >>> qq=QtCore.QTimer() >>> qq.setSingleShot(True) >>> qq.connect('timeout()',myfunc) >>> recordingTimeInMilliseconds = 60 * 1000 >>> qq.start(recordingTimeInMilliseconds) >>> >>> Hope this helps, >>> >>> Bastien Jacquet, PhD >>> VeloView Lead Developer - Computer Vision Team >>> Kitware SAS >>> 26 rue Louis Gu?rin - 69100 Villeurbanne - France >>> F: +33 (0)4.37.45.04.15 >>> On Sun, Feb 11, 2018 at 3:55 PM, Magician > wrote: >>> Hi all, >>> >>> >>> I?m using VeloView 3.5.0 (Windows 64bit) and recording VLP-16?s data packets. >>> I want to set the total recording time or stopping time, but VeloView have no option to do it on the GUI. >>> >>> Is there a good way? (ex. using Python) >>> >>> >>> Magician >>> http://www.paraview-expert.com/ >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Mar 8 18:10:13 2018 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 8 Mar 2018 15:10:13 -0800 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: Message-ID: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: > Hello ParaView users, > > In short: > I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. > > > The problem: > I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. > > To start the pvserver manually from the server itself I execute a command similar to this: > > mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering > > After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` > > > My remote connection string looks like this: > > ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering > > Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. > > > > Here is the output of `glxgears` related to OpenGL from the server: > > ``` > $ glxinfo | grep -i opengl > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: Quadro K2200/PCIe/SSE2 > OpenGL core profile version string: 4.5.0 NVIDIA 390.25 > OpenGL core profile shading language version string: 4.50 NVIDIA > OpenGL core profile context flags: (none) > OpenGL core profile profile mask: core profile > OpenGL core profile extensions: > OpenGL version string: 4.6.0 NVIDIA 390.25 > OpenGL shading language version string: 4.60 NVIDIA > OpenGL context flags: (none) > OpenGL profile mask: (none) > OpenGL extensions: > OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 > OpenGL ES profile extensions: > ``` > > Here is the same output from an ssh connection from the client: > > ``` > ssh @ glxinfo | grep -i opengl > Error: unable to open display > ``` > > And the same with x forwarding enabled (via Xming installed on the client): > > ``` > ssh -X @ glxinfo | grep -i opengl > Warning: No xauth data; using fake authentication data for X11 forwarding. > OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > OpenGL version string: 3.0 Mesa 17.0.5 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > ``` > > Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? > > I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: > > ``` > ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl > Warning: No xauth data; using fake authentication data for X11 forwarding. > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > OpenGL version string: 3.0 Mesa 17.0.5 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > ``` > > I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. > > > Thanks in advance, > Chris > > > > Met vriendlijke groet, > REDstack BV > > Chris Coutinho > Onderzoeker/Data Analist > > tel: +31 (0)6 - 2222 5785 > post: Postbox 199, 8600 AD Sneek > bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek > email: c.coutinho at redstack.nl > www: www.redstack.nl > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.coutinho at redstack.nl Fri Mar 9 08:25:09 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Fri, 9 Mar 2018 13:25:09 +0000 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: Thanks for the explanation Burlen, It was indeed an issue with xhost as you alluded to. On the server I added my user to the list of authorized clients: xhost +SI:localhost: Another point that I need to do was remove the Mesa library from the server, which was probably on the system because the nvidia drivers were installed later. After removing the Mesa library, adding my user to the authorized clients for xhost, and appending the DISPLAY variable to my pvserver command fixes the problem that I originally had. Here's my current working command: ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering I wasn't able to get reverse connection to work correctly, so I removed that argument from the command, It's not entirely clear to me why I would need it. From the documentation it seems like a requirement if the client and server are on separate sides of a firewall. That's not the case for me and it works without. Thanks again for your quick response. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: vrijdag 9 maart 2018 00:10 To: Chris Coutinho ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something? about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: mailto:c.coutinho at redstack.nl www: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 From c.coutinho at redstack.nl Fri Mar 9 15:18:05 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Fri, 9 Mar 2018 20:18:05 +0000 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: I'm running into some other trouble related to accessing the remote server. I'm able to successfully use the remote GPU from a client when the ssh user is also logged into the machine and in a X session (specifically Gnome). Is it possible to access the remote GPU without being logged in as the same user that is doing the ssh remote connection? Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 14:25 To: Burlen Loring ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] Thanks for the explanation Burlen, It was indeed an issue with xhost as you alluded to. On the server I added my user to the list of authorized clients: xhost +SI:localhost: Another point that I need to do was remove the Mesa library from the server, which was probably on the system because the nvidia drivers were installed later. After removing the Mesa library, adding my user to the authorized clients for xhost, and appending the DISPLAY variable to my pvserver command fixes the problem that I originally had. Here's my current working command: ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering I wasn't able to get reverse connection to work correctly, so I removed that argument from the command, It's not entirely clear to me why I would need it. From the documentation it seems like a requirement if the client and server are on separate sides of a firewall. That's not the case for me and it works without. Thanks again for your quick response. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: vrijdag 9 maart 2018 00:10 To: Chris Coutinho ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: mailto:c.coutinho at redstack.nl www: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgBlP1BBG4d2Qc9c%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=ppWU%2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79QRckMVrqNx0C4%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj%2Fia5JybxTjwogouuvMDDM%3D&reserved=0 From c.coutinho at redstack.nl Fri Mar 9 15:48:43 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Fri, 9 Mar 2018 20:48:43 +0000 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: I spoke too soon, apparently my issue was that the users were not part of the 'video' group. After adding the various users to the video group the problem is gone. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: Chris Coutinho Sent: vrijdag 9 maart 2018 21:18 To: Chris Coutinho ; Burlen Loring ; paraview at public.kitware.com Subject: RE: [Paraview] Utilizing Server GPU from an external command I'm running into some other trouble related to accessing the remote server. I'm able to successfully use the remote GPU from a client when the ssh user is also logged into the machine and in a X session (specifically Gnome). Is it possible to access the remote GPU without being logged in as the same user that is doing the ssh remote connection? Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 14:25 To: Burlen Loring ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] Thanks for the explanation Burlen, It was indeed an issue with xhost as you alluded to. On the server I added my user to the list of authorized clients: xhost +SI:localhost: Another point that I need to do was remove the Mesa library from the server, which was probably on the system because the nvidia drivers were installed later. After removing the Mesa library, adding my user to the authorized clients for xhost, and appending the DISPLAY variable to my pvserver command fixes the problem that I originally had. Here's my current working command: ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering I wasn't able to get reverse connection to work correctly, so I removed that argument from the command, It's not entirely clear to me why I would need it. From the documentation it seems like a requirement if the client and server are on separate sides of a firewall. That's not the case for me and it works without. Thanks again for your quick response. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: vrijdag 9 maart 2018 00:10 To: Chris Coutinho ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: mailto:c.coutinho at redstack.nl www: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgBlP1BBG4d2Qc9c%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=ppWU%2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79QRckMVrqNx0C4%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj%2Fia5JybxTjwogouuvMDDM%3D&reserved=0 From rskowch at gmail.com Sat Mar 10 16:26:00 2018 From: rskowch at gmail.com (Roman Kowch) Date: Sat, 10 Mar 2018 16:26:00 -0500 Subject: [Paraview] Is a State File's data directory accessible through Python programmable filters? Message-ID: Hi there, I've been developing ways to build data displays through programmable filters and their associated Python scripts. After I build a display, I save the entire layout as a State File. Then, I can give both the State File and data files used to build the display to another user, so they can replicate the exact same display on their computer. A new feature in Paraview allows someone to choose the Data Directory when they load a State File. However, I don't know a way to pass this Data Directory path to my Python scripts. Is the Data Directory accessible as a global environment variable through Paraview's Python shell? It would be nice if a user could place the data files in any directory they want, then choose that directory when loading a State File, and have the underlying Python code (stored in Programmable Filters) in the State File access that directory. Currently, I need to require the user to put the data directory in a special place so that its path matches that written in the Python code. e.g. The hard-coded directory I've written is "$HOME/Desktop/pvdata". I'm using Paraview 5.4.1 on OS X. Thanks for your help, Roman -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sat Mar 10 19:32:46 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 10 Mar 2018 19:32:46 -0500 Subject: [Paraview] Reading AMReX directories In-Reply-To: References: <5c229516cdab40419ff87d28ebcdfa7d@lanl.gov> Message-ID: Terry, A couple of issues were spotted. 1. The reader by default picks "particles" as the name of the particles directory under the plt folder (which is the case with MFIX). There's a "Particle Type" entry on the Properties panel. You should be able to change that to match the particles present in your file viz. particle0, particle1, or particle2. 2. Even after changing that, the reader will fail to read. That's because there's a difference in the naming conventions for the DATA_* files between the samples I had and the one you have. I've fixed that here: https://gitlab.kitware.com/vtk/vtk/merge_requests/4051. While this will miss the RC3, I'll have it merged before the final release. Utkarsh On Tue, Mar 6, 2018 at 5:00 PM, Utkarsh Ayachit wrote: > Terry, > > Looks like the structure is different with the files you sent. Let me > see what's going on. > > Utkarsh > > On Tue, Mar 6, 2018 at 11:10 AM, Turton, Terry wrote: >> Utkarsh, >> >> I am sending it via LANL transfer, look for it in a little bit. The >> MFIX-Exa data was the data in para/view/Testing/Data/AMReX-MFIX/plt*. >> >> thanks, >> >> Terry >> >> ________________________________ >> From: Utkarsh Ayachit >> Sent: Tuesday, March 6, 2018 9:40:52 AM >> To: Turton, Terry >> Cc: paraview at public.kitware.com >> Subject: Re: [Paraview] Reading AMReX directories >> >> Terry, send me your sample dataset and I can see what's going on. >> >> Utkarsh >> >> On Tue, Mar 6, 2018 at 9:29 AM, Turton, Terry wrote: >>> I am getting an error when trying to read AMReX plt* directories: >>> >>> >>> ERROR: In >>> >>> C:\bbd\7cc78367\source-paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, >>> line 784 >>> vtkPVCompositeDataPipeline (000000000A7A0D40): Algorithm >>> vtkAMReXParticlesReader(000000000A5FDFE0) returned failure for request: >>> vtkInformation (000000000A776280) >>> Debug: Off >>> Modified Time: 262059 >>> Reference Count: 1 >>> Registered Events: (none) >>> Request: REQUEST_INFORMATION >>> FORWARD_DIRECTION: 0 >>> ALGORITHM_AFTER_FORWARD: 1 >>> >>> I saw the recent update for >>> https://gitlab.kitware.com/paraview/paraview/issues/17998 and am using the >>> latest nightly build (PV 5.5) for Windows. I am trying to read a WARPX >>> AMReX plt* directory but also tried it on the MFiX-Exa dataset in the >>> testing folder with the same results. Am I missing something? >>> >>> >>> Thanks, >>> >>> Terry >>> >>> >>> ------ >>> >>> Terece Turton, Ph.D. >>> >>> Staff Scientist >>> >>> Data Science at Scale Team, CCS-7 >>> >>> Los Alamos National Laboratory >>> >>> 512-415-7305 (c) >>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> From gsharma4189 at gmail.com Sun Mar 11 09:49:14 2018 From: gsharma4189 at gmail.com (govind sharma) Date: Sun, 11 Mar 2018 19:19:14 +0530 Subject: [Paraview] SOURCE_CODE Message-ID: Hi, 1 : I am facing trouble with downloading source code from git. I need to install development version of Paraview. Can you please guide me? with regards, Govind -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsharma4189 at gmail.com Sun Mar 11 09:56:15 2018 From: gsharma4189 at gmail.com (govind sharma) Date: Sun, 11 Mar 2018 19:26:15 +0530 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN Message-ID: Hi, I am doing particle simulation of different diameters size. This issue I didn't not face previously but suddenly happened and I do not find and reason. I load particle data into paraview as it has different sizes I want to see actual size of particles, for that I am using point gaussian feature. I set the parameters like gaussian radius 1, sphere, gauss with radius, it should result in correct way but not, paraview automatically gets off. Before going off its shows all particles in very large size. I am following the same procedure but didn't happen previously. with regards, Govind -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Mar 11 10:37:57 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 11 Mar 2018 10:37:57 -0400 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN In-Reply-To: References: Message-ID: How are those actual sizes provided in the dataset? Are those actual sizes stored in a point-data array ? If so, you want to scale the points, and not set the guassian radius to 1. To scale, check *Use Scale Array* on the Properties panel and select the *Gaussian Scale Array* and * Scale Array Component* to select the array/component for the size field. Utkarsh On Sun, Mar 11, 2018 at 9:56 AM, govind sharma wrote: > Hi, > > I am doing particle simulation of different diameters size. This issue I > didn't not face previously but suddenly happened and I do not find and > reason. I load particle data into paraview as it has different sizes I > want to see actual size of particles, for that I am using point gaussian > feature. I set the parameters like gaussian radius 1, sphere, gauss with > radius, it should result in correct way but not, paraview automatically > gets off. Before going off its shows all particles in very large size. > > I am following the same procedure but didn't happen previously. > > > with regards, > Govind > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Mar 11 10:39:12 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 11 Mar 2018 10:39:12 -0400 Subject: [Paraview] SOURCE_CODE In-Reply-To: References: Message-ID: It'd be useful if you clarified what trouble you are facing. Try posting exactly how you're download and what error message you're getting. Thanks Utkarsh On Sun, Mar 11, 2018 at 9:49 AM, govind sharma wrote: > Hi, > > 1 : I am facing trouble with downloading source code from git. I need to > install development version of Paraview. Can you please guide me? > > > > with regards, > Govind > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Sun Mar 11 10:52:59 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 11 Mar 2018 10:52:59 -0400 Subject: [Paraview] Is a State File's data directory accessible through Python programmable filters? In-Reply-To: References: Message-ID: Roman, I am a little confused. Can you clarify the user workflow, please? Does the user load a pvsm state file which has Python Programmable Filters in it and you want to access the data directory that the user chose when loading the pvsm state file, is that it? Or does the user load the pvsm state file and then also run some Python scripts from the Python shell and you want to pass the data directory to these scripts run in the Python shell. Utkarsh On Sat, Mar 10, 2018 at 4:26 PM, Roman Kowch wrote: > Hi there, > > I've been developing ways to build data displays through programmable > filters and their associated Python scripts. After I build a display, I save > the entire layout as a State File. Then, I can give both the State File and > data files used to build the display to another user, so they can replicate > the exact same display on their computer. > > A new feature in Paraview allows someone to choose the Data Directory when > they load a State File. However, I don't know a way to pass this Data > Directory path to my Python scripts. Is the Data Directory accessible as a > global environment variable through Paraview's Python shell? It would be > nice if a user could place the data files in any directory they want, then > choose that directory when loading a State File, and have the underlying > Python code (stored in Programmable Filters) in the State File access that > directory. > > Currently, I need to require the user to put the data directory in a special > place so that its path matches that written in the Python code. e.g. The > hard-coded directory I've written is "$HOME/Desktop/pvdata". I'm using > Paraview 5.4.1 on OS X. > > Thanks for your help, > Roman > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From stephen.wornom at inria.fr Sun Mar 11 10:55:43 2018 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Sun, 11 Mar 2018 15:55:43 +0100 (CET) Subject: [Paraview] PV 4.1.0- mesh shows on the contour plots Message-ID: <570147415.4796224.1520780143796.JavaMail.zimbra@inria.fr> When I have a coarse mesh, the contours are smooth and the mesh does not show. When I use a fine mesh, I see the mesh on the contours. Is this due to a lack of precision when the PV files are written? Is there an option to avoid seeing the mesh on the contours? Hope my question is clear, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsharma4189 at gmail.com Sun Mar 11 11:58:30 2018 From: gsharma4189 at gmail.com (govind sharma) Date: Sun, 11 Mar 2018 21:28:30 +0530 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN In-Reply-To: References: Message-ID: Thanks Utkarsh, Point-data array. Yes I check on *Use Scale Array *and select the radius in *Gaussian Scale Array. *Giving the gaussian radius 1. As I said it happened suddenly and I followed the same procedure previous. Here is snapshot. On Sun, Mar 11, 2018 at 8:07 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > How are those actual sizes provided in the dataset? Are those actual sizes > stored in a point-data array ? If so, you want to scale the points, and not > set the guassian radius to 1. To scale, check *Use Scale Array* on the > Properties panel and select the *Gaussian Scale Array* and * Scale Array > Component* to select the array/component for the size field. > > Utkarsh > > On Sun, Mar 11, 2018 at 9:56 AM, govind sharma > wrote: > >> Hi, >> >> I am doing particle simulation of different diameters size. This issue I >> didn't not face previously but suddenly happened and I do not find and >> reason. I load particle data into paraview as it has different sizes I >> want to see actual size of particles, for that I am using point gaussian >> feature. I set the parameters like gaussian radius 1, sphere, gauss with >> radius, it should result in correct way but not, paraview automatically >> gets off. Before going off its shows all particles in very large size. >> >> I am following the same procedure but didn't happen previously. >> >> >> with regards, >> Govind >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Para.png Type: image/png Size: 202800 bytes Desc: not available URL: From kmorel at sandia.gov Sun Mar 11 12:24:24 2018 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Sun, 11 Mar 2018 16:24:24 +0000 Subject: [Paraview] PV 4.1.0- mesh shows on the contour plots In-Reply-To: <570147415.4796224.1520780143796.JavaMail.zimbra@inria.fr> References: <570147415.4796224.1520780143796.JavaMail.zimbra@inria.fr> Message-ID: Stephen, I think you will have to be more specific with your question. It might help if you at least post some pictures that give examples of what artifacts you are seeing. Example data files would be even more useful. I can say that the contouring algorithm does not change with the coarseness of the mesh. I can also say that PV data files can store data in in their native precision (e.g. double floating points). I think it unlikely that either of these are the cause of the artifacts you are seeing. If I had to guess (and this is only a guess) the most likely culprit is the data itself. Perhaps the fields in your fine mesh are not as smooth as those in your coarse mesh. It can be the case that coarsened meshes have ?blurred? fields. -Ken Sent from my iPad On Mar 11, 2018, at 8:55 AM, Stephen Wornom > wrote: When I have a coarse mesh, the contours are smooth and the mesh does not show. When I use a fine mesh, I see the mesh on the contours. Is this due to a lack of precision when the PV files are written? Is there an option to avoid seeing the mesh on the contours? Hope my question is clear, Stephen _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From rskowch at gmail.com Sun Mar 11 13:09:37 2018 From: rskowch at gmail.com (Roman Kowch) Date: Sun, 11 Mar 2018 13:09:37 -0400 Subject: [Paraview] Is a State File's data directory accessible through Python programmable filters? In-Reply-To: References: Message-ID: Hi Utkarsh, Your first interpretation is correct. I want to pass the data directory that the user chose when loading the pvsm state file. The state file contains programmable filters, and I want to insert that directory in each of them. I don't expect the user to run any of their own Python source after loading a state file. Thanks, Roman On Sun, Mar 11, 2018 at 10:52 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Roman, > > I am a little confused. Can you clarify the user workflow, please? > Does the user load a pvsm state file which has Python Programmable > Filters in it and you want to access the data directory that the user > chose when loading the pvsm state file, is that it? Or does the user > load the pvsm state file and then also run some Python scripts from > the Python shell and you want to pass the data directory to these > scripts run in the Python shell. > > Utkarsh > > On Sat, Mar 10, 2018 at 4:26 PM, Roman Kowch wrote: > > Hi there, > > > > I've been developing ways to build data displays through programmable > > filters and their associated Python scripts. After I build a display, I > save > > the entire layout as a State File. Then, I can give both the State File > and > > data files used to build the display to another user, so they can > replicate > > the exact same display on their computer. > > > > A new feature in Paraview allows someone to choose the Data Directory > when > > they load a State File. However, I don't know a way to pass this Data > > Directory path to my Python scripts. Is the Data Directory accessible as > a > > global environment variable through Paraview's Python shell? It would be > > nice if a user could place the data files in any directory they want, > then > > choose that directory when loading a State File, and have the underlying > > Python code (stored in Programmable Filters) in the State File access > that > > directory. > > > > Currently, I need to require the user to put the data directory in a > special > > place so that its path matches that written in the Python code. e.g. The > > hard-coded directory I've written is "$HOME/Desktop/pvdata". I'm using > > Paraview 5.4.1 on OS X. > > > > Thanks for your help, > > Roman > > > > > > _______________________________________________ > > 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: > > https://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From archaerolog at mail.ru Mon Mar 12 08:12:51 2018 From: archaerolog at mail.ru (Gena Bug) Date: Mon, 12 Mar 2018 15:12:51 +0300 Subject: [Paraview] Fwd: Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> Message-ID: Sorry, always forget to reply to the list.. -------- Forwarded Message -------- Subject: Re: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available Date: Mon, 12 Mar 2018 15:11:34 +0300 From: Gena Bug To: Cory Quammen Hi! I noticed that button "Rescale to customg range" has been removed from the properties panel. Instead a new one, "Use separate color map" has been added. I'm not sure about usefulness about the last one (never used it before) however I find the first one is very usefull (for me). Is it possible to return it back? On 08.03.2018 18:27, Cory Quammen wrote: > Dear ParaView developers, > > ParaView 5.5.0-RC2 has been tagged (tag "v5.5.0-RC2"). Binaries are also > available on the ParaView downloads web page https://www.paraview.org/ > download/. > > Please let us know if you encounter any issues with this release candidate. > > ParaView's superbuild has also been tagged with "v5.5.0-RC2". > > Thank you, > Cory > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Mon Mar 12 10:54:36 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 12 Mar 2018 10:54:36 -0400 Subject: [Paraview] Fwd: Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> Message-ID: Gena, Thanks for the report. Indeed, this was an accidental removal. I have opened an issue at https://gitlab.kitware.com/paraview/paraview/issues/18031 . It should be easy to fix prior to 5.5.0's release. Thanks, Cory On Mon, Mar 12, 2018 at 8:12 AM, Gena Bug via ParaView < paraview at public.kitware.com> wrote: > Sorry, always forget to reply to the list.. > > > > -------- Forwarded Message -------- > Subject: Re: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available > Date: Mon, 12 Mar 2018 15:11:34 +0300 > From: Gena Bug > To: Cory Quammen > > Hi! > > I noticed that button "Rescale to customg range" has been removed from the > properties panel. Instead a new one, "Use separate color map" has been > added. I'm not sure about usefulness about the last one (never used it > before) however I find the first one is very usefull (for me). Is it > possible to return it back? > > On 08.03.2018 18:27, Cory Quammen wrote: > >> Dear ParaView developers, >> >> ParaView 5.5.0-RC2 has been tagged (tag "v5.5.0-RC2"). Binaries are also >> available on the ParaView downloads web page https://www.paraview.org/ >> download/. >> >> Please let us know if you encounter any issues with this release >> candidate. >> >> ParaView's superbuild has also been tagged with "v5.5.0-RC2". >> >> Thank you, >> Cory >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 12 11:09:09 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 12 Mar 2018 11:09:09 -0400 Subject: [Paraview] Is a State File's data directory accessible through Python programmable filters? In-Reply-To: References: Message-ID: Hmm, okay. Currently, there's no way. Once a state file is loaded, ParaView doesn't keep track of the fact that a state file was loaded as a result has no mechanisms to indicate the selections made when loading the state file. There are few indirect options for doing what you want: 1. Package your Python programmable filters in custom XMLs that have a file name property which points the data files to process. The load state dialog will update those filenames too when loading the state file. To package a Programmable Filter into a XML filter with properties, see https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/. 2. Create custom readers (which could indeed simply be Python programmable sources that internally use the real readers to read the datasets) and pass in FieldData the names of the data directory, filenames etc, as needed. Then, downstream filters will have access to those directories in Field Data. Utkarsh On Sun, Mar 11, 2018 at 1:09 PM, Roman Kowch wrote: > Hi Utkarsh, > > Your first interpretation is correct. I want to pass the data directory that > the user chose when loading the pvsm state file. The state file contains > programmable filters, and I want to insert that directory in each of them. > > I don't expect the user to run any of their own Python source after loading > a state file. > > Thanks, > Roman > > > > On Sun, Mar 11, 2018 at 10:52 AM, Utkarsh Ayachit > wrote: >> >> Roman, >> >> I am a little confused. Can you clarify the user workflow, please? >> Does the user load a pvsm state file which has Python Programmable >> Filters in it and you want to access the data directory that the user >> chose when loading the pvsm state file, is that it? Or does the user >> load the pvsm state file and then also run some Python scripts from >> the Python shell and you want to pass the data directory to these >> scripts run in the Python shell. >> >> Utkarsh >> >> On Sat, Mar 10, 2018 at 4:26 PM, Roman Kowch wrote: >> > Hi there, >> > >> > I've been developing ways to build data displays through programmable >> > filters and their associated Python scripts. After I build a display, I >> > save >> > the entire layout as a State File. Then, I can give both the State File >> > and >> > data files used to build the display to another user, so they can >> > replicate >> > the exact same display on their computer. >> > >> > A new feature in Paraview allows someone to choose the Data Directory >> > when >> > they load a State File. However, I don't know a way to pass this Data >> > Directory path to my Python scripts. Is the Data Directory accessible as >> > a >> > global environment variable through Paraview's Python shell? It would be >> > nice if a user could place the data files in any directory they want, >> > then >> > choose that directory when loading a State File, and have the underlying >> > Python code (stored in Programmable Filters) in the State File access >> > that >> > directory. >> > >> > Currently, I need to require the user to put the data directory in a >> > special >> > place so that its path matches that written in the Python code. e.g. The >> > hard-coded directory I've written is "$HOME/Desktop/pvdata". I'm using >> > Paraview 5.4.1 on OS X. >> > >> > Thanks for your help, >> > Roman >> > >> > >> > _______________________________________________ >> > 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: >> > https://public.kitware.com/mailman/listinfo/paraview >> > > > From utkarsh.ayachit at kitware.com Mon Mar 12 11:10:53 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 12 Mar 2018 11:10:53 -0400 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN In-Reply-To: References: Message-ID: Based on what I see, I think your "radius" array has a constant value 4e-3. Check the Information tab for range of "radius" array. You can also use the SpreadSheet view to look at individual values. Utkarsh On Sun, Mar 11, 2018 at 11:58 AM, govind sharma wrote: > Thanks Utkarsh, > > Point-data array. Yes I check on Use Scale Array and select the radius in > Gaussian Scale Array. Giving the gaussian radius 1. As I said it happened > suddenly and I followed the same procedure previous. Here is snapshot. > > On Sun, Mar 11, 2018 at 8:07 PM, Utkarsh Ayachit > wrote: >> >> How are those actual sizes provided in the dataset? Are those actual sizes >> stored in a point-data array ? If so, you want to scale the points, and not >> set the guassian radius to 1. To scale, check Use Scale Array on the >> Properties panel and select the Gaussian Scale Array and Scale Array >> Component to select the array/component for the size field. >> >> Utkarsh >> >> On Sun, Mar 11, 2018 at 9:56 AM, govind sharma >> wrote: >>> >>> Hi, >>> >>> I am doing particle simulation of different diameters size. This issue I >>> didn't not face previously but suddenly happened and I do not find and >>> reason. I load particle data into paraview as it has different sizes I want >>> to see actual size of particles, for that I am using point gaussian feature. >>> I set the parameters like gaussian radius 1, sphere, gauss with radius, it >>> should result in correct way but not, paraview automatically gets off. >>> Before going off its shows all particles in very large size. >>> >>> I am following the same procedure but didn't happen previously. >>> >>> >>> with regards, >>> Govind >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >> > From phsiao at cs.unc.edu Mon Mar 12 17:22:32 2018 From: phsiao at cs.unc.edu (Joe Ping-Lin Hsiao) Date: Mon, 12 Mar 2018 17:22:32 -0400 Subject: [Paraview] Unexpected measurement appears in 5.4.1 but not 5.0.1 In-Reply-To: <265f0d34-76cb-8444-5123-70334a150ae6@be.itu.edu.tr> References: <1812503415.6892.1517418997950.JavaMail.zimbra@be.itu.edu.tr> <265f0d34-76cb-8444-5123-70334a150ae6@be.itu.edu.tr> Message-ID: Wonderful. Thank you Cory. On Fri, Mar 2, 2018 at 4:00 AM, Ufuk Utku Turuncoglu (BE) < u.utku.turuncoglu at be.itu.edu.tr> wrote: > Thanks for the update. > > Regards, > > --ufuk > > On 1.03.2018 16:29, Cory Quammen wrote: > > Joe and Ufuk, > > You seem to be running into the same issue as reported here: > https://gitlab.kitware.com/paraview/paraview/issues/17671 > > Let's continue track the issue there. > > Best, > Cory > > On Mon, Feb 12, 2018 at 12:24 PM, Joe Ping-Lin Hsiao > wrote: > >> Hi Cory, >> >> "display.PolarAxes.Visibility = 0" does not work for me. The polar axes >> comes back every time I rewind the animation. It feels like the data >> visibility also applies to polar axes visibility. >> >> I have attached a small dataset and a simplified script for you to test, >> but you have to change the data path in the script. >> >> BTW this is on Windows 10 64-bit. >> >> Best, >> Joe >> >> >> On Wed, Jan 31, 2018 at 1:09 PM, Cory Quammen >> wrote: >> >>> Ufuk, >>> >>> Thanks for the report. Is there a reliable way to reproduce the >>> behavior that you can share? >>> >>> Best, >>> Cory >>> >>> On Wed, Jan 31, 2018 at 12:16 PM, Ufuk Turuncoglu >>> wrote: >>> > I don't know it is related or not. I have very similar behavior under >>> 5.4.1. If i save a state and load it later, Polar Axes show up and i need >>> to disable it from the properties panel. Somehow, ParaView loads Polar Axes >>> even if it is not activated in the original pipeline. It might help to find >>> the source of the issue. >>> > >>> > Best Regards, >>> > >>> > --ufuk >>> > >>> > ----- Original Message ----- >>> > From: "Cory Quammen" >>> > To: "Joe Ping-Lin Hsiao" >>> > Cc: "paraview" >>> > Sent: Wednesday, January 31, 2018 6:44:45 PM >>> > Subject: Re: [Paraview] Unexpected measurement appears in 5.4.1 but >>> not 5.0.1 >>> > >>> > Hmm, that's weird. The Polar Axes should be off by default. Do the >>> > Polar Axes appear when creating a Sphere source? >>> > >>> > You should be able to force it off by adding the following line to the >>> > loadFile() function in your script: >>> > >>> > display.PolarAxes.Visibility = 0 >>> > >>> > HTH, >>> > Cory >>> > >>> > On Tue, Jan 23, 2018 at 4:40 PM, Joe Ping-Lin Hsiao >>> wrote: >>> >> Yes exactly. >>> >> >>> >> On Tue, Jan 23, 2018 at 3:47 PM, Cory Quammen < >>> cory.quammen at kitware.com> >>> >> wrote: >>> >>> >>> >>> Hi Joe, >>> >>> >>> >>> Are you referring to the circular (polar axes) in the image? It says >>> >>> 90.0 deg, 45.0 deg., etc. >>> >>> >>> >>> Thanks, >>> >>> Cory >>> >>> >>> >>> On Tue, Jan 23, 2018 at 3:31 PM, Joe Ping-Lin Hsiao < >>> phsiao at cs.unc.edu> >>> >>> wrote: >>> >>> > The attached image shows the unexpected measure with text. I >>> tested two >>> >>> > versions of ParaView and it only happens in 5.4.1 but not 5.0.1. >>> >>> > >>> >>> > 180 stacks are loaded and set to volume rendering by my Python >>> script, >>> >>> > which >>> >>> > is also attached. >>> >>> > >>> >>> > Thanks, >>> >>> > Joe >>> >>> > >>> >>> > _______________________________________________ >>> >>> > 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: >>> >>> > https://paraview.org/mailman/listinfo/paraview >>> >>> > >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> >>> Staff R&D Engineer >>> >>> Kitware, Inc. >>> >> >>> >> >>> > >>> > >>> > >>> > -- >>> > 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: >>> > https://paraview.org/mailman/listinfo/paraview >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 13 08:36:19 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 13 Mar 2018 08:36:19 -0400 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN In-Reply-To: References: Message-ID: I'd reduce the Gaussian Radius. I'd also suggest downloading 5.4.1 or the latest 5.5-RCs. The Point Gaussian representation has gone quite a few improvement since 5.0.1. Utkarsh On Tue, Mar 13, 2018 at 4:30 AM, govind sharma wrote: > Sorry that is not correct one. Here I am attaching two images i.e. before > applying point gaussian and after applying point gaussain. > > > On Mon, Mar 12, 2018 at 8:40 PM, Utkarsh Ayachit > wrote: >> >> Based on what I see, I think your "radius" array has a constant value >> 4e-3. Check the Information tab for range of "radius" array. You can >> also use the SpreadSheet view to look at individual values. >> >> Utkarsh >> >> On Sun, Mar 11, 2018 at 11:58 AM, govind sharma >> wrote: >> > Thanks Utkarsh, >> > >> > Point-data array. Yes I check on Use Scale Array and select the radius >> > in >> > Gaussian Scale Array. Giving the gaussian radius 1. As I said it >> > happened >> > suddenly and I followed the same procedure previous. Here is snapshot. >> > >> > On Sun, Mar 11, 2018 at 8:07 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> How are those actual sizes provided in the dataset? Are those actual >> >> sizes >> >> stored in a point-data array ? If so, you want to scale the points, and >> >> not >> >> set the guassian radius to 1. To scale, check Use Scale Array on the >> >> Properties panel and select the Gaussian Scale Array and Scale Array >> >> Component to select the array/component for the size field. >> >> >> >> Utkarsh >> >> >> >> On Sun, Mar 11, 2018 at 9:56 AM, govind sharma >> >> wrote: >> >>> >> >>> Hi, >> >>> >> >>> I am doing particle simulation of different diameters size. This issue >> >>> I >> >>> didn't not face previously but suddenly happened and I do not find and >> >>> reason. I load particle data into paraview as it has different sizes >> >>> I want >> >>> to see actual size of particles, for that I am using point gaussian >> >>> feature. >> >>> I set the parameters like gaussian radius 1, sphere, gauss with >> >>> radius, it >> >>> should result in correct way but not, paraview automatically gets >> >>> off. >> >>> Before going off its shows all particles in very large size. >> >>> >> >>> I am following the same procedure but didn't happen previously. >> >>> >> >>> >> >>> with regards, >> >>> Govind >> >>> >> >>> _______________________________________________ >> >>> 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: >> >>> https://public.kitware.com/mailman/listinfo/paraview >> >>> >> >> >> > > > From gsharma4189 at gmail.com Tue Mar 13 10:45:44 2018 From: gsharma4189 at gmail.com (govind sharma) Date: Tue, 13 Mar 2018 20:15:44 +0530 Subject: [Paraview] PROBLEM_WITH_POINT_GAUSSIAN In-Reply-To: References: Message-ID: Thanks Utkarsh I will try that one. Govind On 13 Mar 2018 6:06 p.m., "Utkarsh Ayachit" wrote: > I'd reduce the Gaussian Radius. I'd also suggest downloading 5.4.1 or > the latest 5.5-RCs. The Point Gaussian representation has gone quite a > few improvement since 5.0.1. > > Utkarsh > > On Tue, Mar 13, 2018 at 4:30 AM, govind sharma > wrote: > > Sorry that is not correct one. Here I am attaching two images i.e. before > > applying point gaussian and after applying point gaussain. > > > > > > On Mon, Mar 12, 2018 at 8:40 PM, Utkarsh Ayachit > > wrote: > >> > >> Based on what I see, I think your "radius" array has a constant value > >> 4e-3. Check the Information tab for range of "radius" array. You can > >> also use the SpreadSheet view to look at individual values. > >> > >> Utkarsh > >> > >> On Sun, Mar 11, 2018 at 11:58 AM, govind sharma > >> wrote: > >> > Thanks Utkarsh, > >> > > >> > Point-data array. Yes I check on Use Scale Array and select the radius > >> > in > >> > Gaussian Scale Array. Giving the gaussian radius 1. As I said it > >> > happened > >> > suddenly and I followed the same procedure previous. Here is > snapshot. > >> > > >> > On Sun, Mar 11, 2018 at 8:07 PM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> How are those actual sizes provided in the dataset? Are those actual > >> >> sizes > >> >> stored in a point-data array ? If so, you want to scale the points, > and > >> >> not > >> >> set the guassian radius to 1. To scale, check Use Scale Array on the > >> >> Properties panel and select the Gaussian Scale Array and Scale Array > >> >> Component to select the array/component for the size field. > >> >> > >> >> Utkarsh > >> >> > >> >> On Sun, Mar 11, 2018 at 9:56 AM, govind sharma < > gsharma4189 at gmail.com> > >> >> wrote: > >> >>> > >> >>> Hi, > >> >>> > >> >>> I am doing particle simulation of different diameters size. This > issue > >> >>> I > >> >>> didn't not face previously but suddenly happened and I do not find > and > >> >>> reason. I load particle data into paraview as it has different > sizes > >> >>> I want > >> >>> to see actual size of particles, for that I am using point gaussian > >> >>> feature. > >> >>> I set the parameters like gaussian radius 1, sphere, gauss with > >> >>> radius, it > >> >>> should result in correct way but not, paraview automatically gets > >> >>> off. > >> >>> Before going off its shows all particles in very large size. > >> >>> > >> >>> I am following the same procedure but didn't happen previously. > >> >>> > >> >>> > >> >>> with regards, > >> >>> Govind > >> >>> > >> >>> _______________________________________________ > >> >>> 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: > >> >>> https://public.kitware.com/mailman/listinfo/paraview > >> >>> > >> >> > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gavin.keith.ridley at gmail.com Tue Mar 13 13:25:14 2018 From: gavin.keith.ridley at gmail.com (Gavin Ridley) Date: Tue, 13 Mar 2018 13:25:14 -0400 Subject: [Paraview] Aborted (6) when using pvserver, help setting up? Message-ID: Hi all, I'd like to use MPI pvserver to take advantage of some 48 core nodes we have on our cluster. There's not much in the way of GPUs, so I've been trying to take the route of using OSMesa with --use-offscreen-rendering. The pvserver seems to start well, but as soon as a client connects, the thing aborts. In particular, if I try to use pvbatch with a basic sphere rendering, the pvserver crashes on running the Render(view) part of the script. Pasted below is the error. Does anyone have any insight on this? Waiting for client... > Connection URL: cs://node0:11111 > Accepting connection(s): node0:11111 > [node0:55287] 47 more processes have sent help message > help-mpi-btl-base.txt / btl:no-nics > [node0:55287] Set MCA parameter "orte_base_help_aggregate" to 0 to see all > help / error messages > d^LClient connected. > [node0:55292] *** Process received signal *** > [node0:55292] Signal: Aborted (6) > [node0:55292] Signal code: (-6) > [node0:55292] [ 0] /lib64/libpthread.so.0(+0x12420)[0x7fbf80742420] > [node0:55292] [ 1] /lib64/libc.so.6(gsignal+0xcb)[0x7fbf7e2f69fb] > [node0:55292] [ 2] /lib64/libc.so.6(abort+0x1b0)[0x7fbf7e2f8800] > [node0:55292] [ 3] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow13CreateAWindowEv+0x4e2)[0x7fbf6adf6964] > [node0:55292] [ 4] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow29CreateHardwareOffScreenWindowEii+0xa2)[0x7fbf6ad5aa1c] > [node0:55292] [ 5] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow21CreateOffScreenWindowEii+0x32)[0x7fbf6adf7be6] > [node0:55292] [ 6] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow10InitializeEv+0xaa)[0x7fbf6adf7ffc] > [node0:55292] [ 7] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow14SupportsOpenGLEv+0x105)[0x7fbf6ad5beb7] > [node0:55292] [ 8] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreRendering-pv5.4.so.1(_ZN23vtkPVDisplayInformation21SupportsOpenGLLocallyEv+0xeb)[0x7fbf78223b81] > [node0:55292] [ 9] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreRendering-pv5.4.so.1(_ZN23vtkPVDisplayInformation14CopyFromObjectEP9vtkObject+0x31)[0x7fbf78223c05] > [node0:55292] [10] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore25GatherInformationInternalEP16vtkPVInformationj+0x38)[0x7fbf85c8a890] > [node0:55292] [11] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore17GatherInformationEjP16vtkPVInformationj+0x8d)[0x7fbf85c8ab45] > [node0:55292] [12] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionBase17GatherInformationEjP16vtkPVInformationj+0x3e)[0x7fbf85c866fc] > [node0:55292] [13] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer25GatherInformationInternalEjPKcjR21vtkMultiProcessStream+0xb7)[0x7fbf85c974b9] > [node0:55292] [14] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer24OnClientServerMessageRMIEPvi+0x561)[0x7fbf85c97225] > [node0:55292] [15] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(+0xa537a)[0x7fbf85c9537a] > [node0:55292] [16] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x356)[0x7fbf826a06ea] > [node0:55292] [17] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x6b5)[0x7fbf826a02bb] > [node0:55292] [18] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInternalEmb+0x46d)[0x7fbf85986311] > [node0:55292] [19] > /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager13ProcessEventsEm+0x28)[0x7fbf85985ea2] > [node0:55292] [20] ./pvserver[0x401acb] > [node0:55292] [21] ./pvserver(main+0x25)[0x401b7f] > [node0:55292] [22] /lib64/libc.so.6(__libc_start_main+0xea)[0x7fbf7e2e088a] > [node0:55292] [23] ./pvserver(_start+0x2a)[0x4017ca] > [node0:55292] *** End of error message *** > > -- Thanks, Gavin Ridley -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 13 13:45:40 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 13 Mar 2018 13:45:40 -0400 Subject: [Paraview] Aborted (6) when using pvserver, help setting up? In-Reply-To: References: Message-ID: Gavin, Your ParaView build is not OSMesa enabled. You'll need to build your own version with OSMesa enabled. For ParaView 5.5, this page summarizes how to do that: https://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/Offscreen.html Utkarsh On Tue, Mar 13, 2018 at 1:25 PM, Gavin Ridley wrote: > Hi all, > > I'd like to use MPI pvserver to take advantage of some 48 core nodes we have > on our cluster. There's not much in the way of GPUs, so I've been trying to > take the route of using OSMesa with --use-offscreen-rendering. The pvserver > seems to start well, but as soon as a client connects, the thing aborts. In > particular, if I try to use pvbatch with a basic sphere rendering, the > pvserver crashes on running the Render(view) part of the script. Pasted > below is the error. > > Does anyone have any insight on this? > >> Waiting for client... >> Connection URL: cs://node0:11111 >> Accepting connection(s): node0:11111 >> [node0:55287] 47 more processes have sent help message >> help-mpi-btl-base.txt / btl:no-nics >> [node0:55287] Set MCA parameter "orte_base_help_aggregate" to 0 to see all >> help / error messages >> d^LClient connected. >> [node0:55292] *** Process received signal *** >> [node0:55292] Signal: Aborted (6) >> [node0:55292] Signal code: (-6) >> [node0:55292] [ 0] /lib64/libpthread.so.0(+0x12420)[0x7fbf80742420] >> [node0:55292] [ 1] /lib64/libc.so.6(gsignal+0xcb)[0x7fbf7e2f69fb] >> [node0:55292] [ 2] /lib64/libc.so.6(abort+0x1b0)[0x7fbf7e2f8800] >> [node0:55292] [ 3] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow13CreateAWindowEv+0x4e2)[0x7fbf6adf6964] >> [node0:55292] [ 4] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow29CreateHardwareOffScreenWindowEii+0xa2)[0x7fbf6ad5aa1c] >> [node0:55292] [ 5] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow21CreateOffScreenWindowEii+0x32)[0x7fbf6adf7be6] >> [node0:55292] [ 6] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow10InitializeEv+0xaa)[0x7fbf6adf7ffc] >> [node0:55292] [ 7] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow14SupportsOpenGLEv+0x105)[0x7fbf6ad5beb7] >> [node0:55292] [ 8] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreRendering-pv5.4.so.1(_ZN23vtkPVDisplayInformation21SupportsOpenGLLocallyEv+0xeb)[0x7fbf78223b81] >> [node0:55292] [ 9] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreRendering-pv5.4.so.1(_ZN23vtkPVDisplayInformation14CopyFromObjectEP9vtkObject+0x31)[0x7fbf78223c05] >> [node0:55292] [10] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore25GatherInformationInternalEP16vtkPVInformationj+0x38)[0x7fbf85c8a890] >> [node0:55292] [11] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore17GatherInformationEjP16vtkPVInformationj+0x8d)[0x7fbf85c8ab45] >> [node0:55292] [12] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN16vtkPVSessionBase17GatherInformationEjP16vtkPVInformationj+0x3e)[0x7fbf85c866fc] >> [node0:55292] [13] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer25GatherInformationInternalEjPKcjR21vtkMultiProcessStream+0xb7)[0x7fbf85c974b9] >> [node0:55292] [14] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer24OnClientServerMessageRMIEPvi+0x561)[0x7fbf85c97225] >> [node0:55292] [15] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVServerImplementationCore-pv5.4.so.1(+0xa537a)[0x7fbf85c9537a] >> [node0:55292] [16] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x356)[0x7fbf826a06ea] >> [node0:55292] [17] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x6b5)[0x7fbf826a02bb] >> [node0:55292] [18] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInternalEmb+0x46d)[0x7fbf85986311] >> [node0:55292] [19] >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager13ProcessEventsEm+0x28)[0x7fbf85985ea2] >> [node0:55292] [20] ./pvserver[0x401acb] >> [node0:55292] [21] ./pvserver(main+0x25)[0x401b7f] >> [node0:55292] [22] >> /lib64/libc.so.6(__libc_start_main+0xea)[0x7fbf7e2e088a] >> [node0:55292] [23] ./pvserver(_start+0x2a)[0x4017ca] >> [node0:55292] *** End of error message *** >> > > -- > Thanks, > Gavin Ridley > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From thomas_sgouros at brown.edu Tue Mar 13 16:44:08 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Tue, 13 Mar 2018 16:44:08 -0400 Subject: [Paraview] simple ParaViewWeb example Message-ID: Hi All: I had a pretty bad time trying to put together the bones of a ParaViewWeb client and server, so have taken a few crusts of bread and gone back to try to leave a trail of crumbs that others can follow. Please find a working simple example at: https://github.com/tsgouros/ParaViewWeb-SimpleDemo It doesn't do much, but it works over here, and has some instructions that I hope will be of service to the next person trying to follow this trail. For the experts out there: it would be great if you wanted to look this over and tell me what could be improved to make it a better illustration of best practices. Even better if you want to make such suggestions in the form of pull requests. For example I can't seem to make all the warnings go away for the npm install, and I'm not sure whether the RPC protocol only transmits strings or whether type conversions can happen on the client side. Nor am I sure that the pvwclient is made available in the smoothest possible way, and so on. Your contributions are welcome. Thank you, -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Tue Mar 13 17:00:50 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 13 Mar 2018 15:00:50 -0600 Subject: [Paraview] simple ParaViewWeb example In-Reply-To: References: Message-ID: Thanks Tom, I'll check it out... On Tue, Mar 13, 2018 at 2:44 PM, Sgouros, Thomas wrote: > Hi All: > > I had a pretty bad time trying to put together the bones of a ParaViewWeb > client and server, so have taken a few crusts of bread and gone back to try > to leave a trail of crumbs that others can follow. > > Please find a working simple example at: > > https://github.com/tsgouros/ParaViewWeb-SimpleDemo > > It doesn't do much, but it works over here, and has some instructions that > I hope will be of service to the next person trying to follow this trail. > > For the experts out there: it would be great if you wanted to look this > over and tell me what could be improved to make it a better illustration of > best practices. Even better if you want to make such suggestions in the > form of pull requests. > > For example I can't seem to make all the warnings go away for the npm > install, and I'm not sure whether the RPC protocol only transmits strings > or whether type conversions can happen on the client side. Nor am I sure > that the pvwclient is made available in the smoothest possible way, and so > on. Your contributions are welcome. > > Thank you, > > -Tom > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 13 17:23:28 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 13 Mar 2018 17:23:28 -0400 Subject: [Paraview] ParaView 5.5.0-RC3 tagged, binaries available Message-ID: Dear ParaView community, I am happy to announce that ParaView 5.5.0-RC3 has been tagged (tag "v5.5.0- RC3"). Binaries are also available on the ParaView downloads web page https://www.paraview.org/download/. If your browser doesn't show the 5.5.0-RC3 downloads, you may just need to "hard refresh" the page. On Chrome and Firefox, hold down Shift while pressing Ctrl-R (or Cmd-R on macOS). Please let us know if you encounter any issues with this release candidate. ParaView's superbuild has also been tagged with "v5.5.0-RC3". Thank you, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nahuja at mtu.edu Tue Mar 13 17:35:13 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Tue, 13 Mar 2018 17:35:13 -0400 Subject: [Paraview] Installation of PARAVIEW in RHEL Message-ID: Hello, I am very new to paraview, I am trying to install paraview on the linux machine. When I try to run paraview through the terminal I get the following error. Does this ,mean I cannot install paraview on this machine? Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 201362 bytes Desc: not available URL: From wascott at sandia.gov Tue Mar 13 17:38:51 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 13 Mar 2018 21:38:51 +0000 Subject: [Paraview] [EXTERNAL] Installation of PARAVIEW in RHEL In-Reply-To: References: Message-ID: It means your hardware graphics is insifficient to run ParaView in hardware mode. Try this: paraview --mesa-llvm Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Nitisha Ahuja Sent: Tuesday, March 13, 2018 3:35 PM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] Installation of PARAVIEW in RHEL Hello, I am very new to paraview, I am trying to install paraview on the linux machine. When I try to run paraview through the terminal I get the following error. [cid:image001.png at 01D3BAE1.6256F3F0] Does this ,mean I cannot install paraview on this machine? Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 109523 bytes Desc: image001.png URL: From chuck.atkins at kitware.com Tue Mar 13 17:39:14 2018 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Tue, 13 Mar 2018 17:39:14 -0400 Subject: [Paraview] Installation of PARAVIEW in RHEL In-Reply-To: References: Message-ID: It just means that the system supplied OpenGL drivers are insufficient. ParaView includes it's own copy of newer mess that you can enable with the --mesa-llvm or --mesa-swr command line option that should work on rhel 6 or 7 for CPU based rendering without a GPU. On Mar 13, 2018 17:35, "Nitisha Ahuja" wrote: > Hello, > I am very new to paraview, I am trying to install paraview on the linux > machine. When I try to run paraview through the terminal I get the > following error. > Does this ,mean I cannot install paraview on this machine? > > Best regards > Nitisha > > > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 201362 bytes Desc: not available URL: From nahuja at mtu.edu Tue Mar 13 17:58:00 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Tue, 13 Mar 2018 17:58:00 -0400 Subject: [Paraview] Installation of PARAVIEW in RHEL In-Reply-To: References: Message-ID: Thanks Chuck & Alan for the response. I tried running paraview --mesa-llvm. Although I dont get the same error in the output message, but in the terminal I see following warnings. Will these effect my process of visualization in PARAVIEW? On Tue, Mar 13, 2018 at 5:39 PM, Chuck Atkins wrote: > It just means that the system supplied OpenGL drivers are insufficient. > ParaView includes it's own copy of newer mess that you can enable with the > --mesa-llvm or --mesa-swr command line option that should work on rhel 6 or > 7 for CPU based rendering without a GPU. > > On Mar 13, 2018 17:35, "Nitisha Ahuja" wrote: > >> Hello, >> I am very new to paraview, I am trying to install paraview on the linux >> machine. When I try to run paraview through the terminal I get the >> following error. >> Does this ,mean I cannot install paraview on this machine? >> >> Best regards >> Nitisha >> >> >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 201362 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 309519 bytes Desc: not available URL: From wascott at sandia.gov Tue Mar 13 18:08:29 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 13 Mar 2018 22:08:29 +0000 Subject: [Paraview] [EXTERNAL] Re: Installation of PARAVIEW in RHEL In-Reply-To: References: Message-ID: These are surprisingly warnings from RHEL, and are warnings only. It won?t impact you. I solve it in as script as follows: paraview --mesa-llvm $* |& grep -v Fontconfig Alan From: Nitisha Ahuja [mailto:nahuja at mtu.edu] Sent: Tuesday, March 13, 2018 3:58 PM To: Atkins, Chuck (External Contacts) ; Scott, W Alan Cc: paraview at public.kitware.com Subject: [EXTERNAL] Re: [Paraview] Installation of PARAVIEW in RHEL Thanks Chuck & Alan for the response. I tried running paraview --mesa-llvm. Although I dont get the same error in the output message, but in the terminal I see following warnings. [cid:image001.png at 01D3BAE5.864E9390] Will these effect my process of visualization in PARAVIEW? On Tue, Mar 13, 2018 at 5:39 PM, Chuck Atkins > wrote: It just means that the system supplied OpenGL drivers are insufficient. ParaView includes it's own copy of newer mess that you can enable with the --mesa-llvm or --mesa-swr command line option that should work on rhel 6 or 7 for CPU based rendering without a GPU. On Mar 13, 2018 17:35, "Nitisha Ahuja" > wrote: Hello, I am very new to paraview, I am trying to install paraview on the linux machine. When I try to run paraview through the terminal I get the following error. [cid:image002.png at 01D3BAE5.864E9390] Does this ,mean I cannot install paraview on this machine? Best regards Nitisha _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 122059 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 109568 bytes Desc: image002.png URL: From nahuja at mtu.edu Tue Mar 13 18:14:28 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Tue, 13 Mar 2018 18:14:28 -0400 Subject: [Paraview] [EXTERNAL] Re: Installation of PARAVIEW in RHEL In-Reply-To: References: Message-ID: Thanks a lot Alan, It works. Best regards Nitisha On Tue, Mar 13, 2018 at 6:08 PM, Scott, W Alan wrote: > These are surprisingly warnings from RHEL, and are warnings only. It > won?t impact you. > > > > I solve it in as script as follows: > > > > paraview --mesa-llvm $* |& grep -v Fontconfig > > > > Alan > > > > *From:* Nitisha Ahuja [mailto:nahuja at mtu.edu] > *Sent:* Tuesday, March 13, 2018 3:58 PM > *To:* Atkins, Chuck (External Contacts) ; > Scott, W Alan > *Cc:* paraview at public.kitware.com > *Subject:* [EXTERNAL] Re: [Paraview] Installation of PARAVIEW in RHEL > > > > Thanks Chuck & Alan for the response. > > I tried running paraview --mesa-llvm. Although I dont get the same error > in the output message, but in the terminal I see following warnings. > > > > > > Will these effect my process of visualization in PARAVIEW? > > > > > > On Tue, Mar 13, 2018 at 5:39 PM, Chuck Atkins > wrote: > > It just means that the system supplied OpenGL drivers are insufficient. > ParaView includes it's own copy of newer mess that you can enable with the > --mesa-llvm or --mesa-swr command line option that should work on rhel 6 or > 7 for CPU based rendering without a GPU. > > > > On Mar 13, 2018 17:35, "Nitisha Ahuja" wrote: > > Hello, > > I am very new to paraview, I am trying to install paraview on the linux > machine. When I try to run paraview through the terminal I get the > following error. > > Does this ,mean I cannot install paraview on this machine? > > > > Best regards > > Nitisha > > > > > > > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 109568 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 122059 bytes Desc: not available URL: From aguirre.utn at gmail.com Wed Mar 14 04:30:17 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Wed, 14 Mar 2018 09:30:17 +0100 Subject: [Paraview] QUESTION ABOUT SLICE Message-ID: Hello, I'am trying to use "Slice" and then "Plot Data" in order to obtain multiple survey lines in a 2D CFD simulation. I have 2 questions : 1) If i use one single slice, the plotted data is not a continuous line. Instead, it shows some bad conectivity between points (See attached figure "Slice - single plane.png"). How can I solve it ? 2) When I use multiple slice, the plotted data is merged into one single array as you can see in the other attached file ( "Slice - multiple planes.png").However, i really need one array for every slice because this multiple output will be treated later. There is a solution for this ? Concerning the second question, i remark here that making multiple "PlotOnIntersectionCurves" and then "GroupdataSets" is not a viable option for me because I need to plot n-lines. Thanks in advance. Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Slice - single plane.png Type: image/png Size: 66727 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Slice - multiple planes.png Type: image/png Size: 60188 bytes Desc: not available URL: From archaerolog at mail.ru Wed Mar 14 05:17:46 2018 From: archaerolog at mail.ru (Gena Bug) Date: Wed, 14 Mar 2018 12:17:46 +0300 Subject: [Paraview] ParaView 5.5.0-RC3 tagged, binaries available In-Reply-To: References: Message-ID: <55838b50-cc66-4636-c73e-d178c926f750@mail.ru> Hi, Why is the RC3 binary is much bigger than the RC2 one (294Mb vs 192Mb)? On 14.03.2018 00:23, Cory Quammen wrote: > Dear ParaView community, > > I am happy to announce that ParaView 5.5.0-RC3 has been tagged (tag "v5.5.0- > RC3"). Binaries are also available on the ParaView downloads web page > https://www.paraview.org/download/. If your browser doesn't show the 5.5.0-RC3 > downloads, you may just need to "hard refresh" the page. On Chrome and > Firefox, hold down Shift while pressing Ctrl-R (or Cmd-R on macOS). > > Please let us know if you encounter any issues with this release candidate. > > ParaView's superbuild has also been tagged with "v5.5.0-RC3". > > Thank you, > Cory > > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From denis.cohen at gmail.com Wed Mar 14 05:36:23 2018 From: denis.cohen at gmail.com (denis cohen) Date: Wed, 14 Mar 2018 10:36:23 +0100 Subject: [Paraview] state file Message-ID: Hello, In past versions of paraview, opening a pvsm state file that read several pvtu files resulted in paraview opening all the pvtu files in that directory. Now it only opens the ones saved in the pvsm file. This is annoying when the number of files has increased (like during a long time dependent simulation) and when wanting to use the same pvsm state file. Any ways of getting around that? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Mar 14 10:34:32 2018 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 14 Mar 2018 10:34:32 -0400 Subject: [Paraview] ParaView 5.5.0-RC3 tagged, binaries available In-Reply-To: <55838b50-cc66-4636-c73e-d178c926f750@mail.ru> References: <55838b50-cc66-4636-c73e-d178c926f750@mail.ru> Message-ID: <20180314143432.GA376@megas.kitware.com> On Wed, Mar 14, 2018 at 12:17:46 +0300, Gena Bug via ParaView wrote: > Why is the RC3 binary is much bigger than the RC2 one (294Mb vs 192Mb)? Windows and Linux now include the NVIDIA IndeX plugin with their runtimes. NVIDIA has provided a license for non-parallel usage for free through March 2019. --Ben From sonphan.it at gmail.com Wed Mar 14 12:16:32 2018 From: sonphan.it at gmail.com (PHAN Minh Son) Date: Wed, 14 Mar 2018 17:16:32 +0100 Subject: [Paraview] RGB volume rendering Message-ID: Hi all, I'm currently working with a 3D color volume (RGB image stack in .tiff format). Is there anyway to render it in paraview? Best regards, Son -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Mar 14 12:42:39 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 14 Mar 2018 16:42:39 +0000 Subject: [Paraview] [EXTERNAL] RGB volume rendering In-Reply-To: References: Message-ID: Should work. Have you tried? Then, you can slice it, or contour it. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of PHAN Minh Son Sent: Wednesday, March 14, 2018 10:17 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] RGB volume rendering Hi all, I'm currently working with a 3D color volume (RGB image stack in .tiff format). Is there anyway to render it in paraview? Best regards, Son -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Mar 14 13:05:23 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 14 Mar 2018 17:05:23 +0000 Subject: [Paraview] [EXTERNAL] QUESTION ABOUT SLICE In-Reply-To: References: Message-ID: Miguel, Can you pass Kitware the dataset? Also, please give detailed steps how to replicate this. For instance, did you change the X Array Name? A state file would be great. Also, are you trying to use Plot Over Line? Now, assuming you have data throughout the line, this should have connectivity. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Miguel Aguirre Sent: Wednesday, March 14, 2018 2:30 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello, I'am trying to use "Slice" and then "Plot Data" in order to obtain multiple survey lines in a 2D CFD simulation. I have 2 questions : 1) If i use one single slice, the plotted data is not a continuous line. Instead, it shows some bad conectivity between points (See attached figure "Slice - single plane.png"). How can I solve it ? 2) When I use multiple slice, the plotted data is merged into one single array as you can see in the other attached file ( "Slice - multiple planes.png").However, i really need one array for every slice because this multiple output will be treated later. There is a solution for this ? Concerning the second question, i remark here that making multiple "PlotOnIntersectionCurves" and then "GroupdataSets" is not a viable option for me because I need to plot n-lines. Thanks in advance. Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: From nahuja at mtu.edu Wed Mar 14 14:08:07 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Wed, 14 Mar 2018 14:08:07 -0400 Subject: [Paraview] Help regarding visualization of velocity vector Message-ID: Hello all, This is a very basic query, but I cant seem to figure it out, I am trying to visualize velocity data for each cell extracted in the vtm file for an engine simulation. I am able to perfectly visualize the velocity variation using color map. But I cant understand how to do the same using velocity vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to work. Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Mar 14 14:25:04 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 14 Mar 2018 18:25:04 +0000 Subject: [Paraview] [EXTERNAL] Help regarding visualization of velocity vector In-Reply-To: References: Message-ID: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> Please elaborate on ?it doesn?t seem to work?. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Nitisha Ahuja Sent: Wednesday, March 14, 2018 12:08 PM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] Help regarding visualization of velocity vector Hello all, This is a very basic query, but I cant seem to figure it out, I am trying to visualize velocity data for each cell extracted in the vtm file for an engine simulation. I am able to perfectly visualize the velocity variation using color map. But I cant understand how to do the same using velocity vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to work. Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Wed Mar 14 14:39:01 2018 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Wed, 14 Mar 2018 14:39:01 -0400 Subject: [Paraview] Sharing a library I wrote to generate ProgrammableFilters with property panel options Message-ID: Hello all, I hope this is not too spammy/self promoting, but I wanted to share a small library that I created to wrap such that you create Python Programmable Filters with custom property panel options from a regular python file. The work is inspired by this blog post[1]. The library based system allows you to write your programmable filter such that it will work outside of paraview so you can possibly mock the inputs/outputs and run unit tests on then, while also allowing easy export into a XML plugins to feed into Paraview for execution. This should allow one to create higher quality, reusable filters. The library is available at: https://github.com/shuhaowu/pvpyfilter. If there is enough interest in this, and once I get to test it more, I can release this onto PyPI for easier access. A short example of this in action (longer one available in the repository, complete with screenshots): class ViscosityType(Enum): Kinematic = 1 Dynamic = 2 class MyFilter(ProgrammableFilter): label = "My Filter" input_data_type = "vtkPolyData" nu = Double("Viscousity", default=1.53e-5, slider=[0, 1e-4], help="...") nu_type = IntegerEnum("Type", default=ViscosityType.Kinematic, enum=ViscosityType) @staticmethod def request_data(inputs, outputs, nu, nu_type): print(nu) print(nu_type) [1]: https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ -- I cannot find the script download from that link and had to get it from somewhere else on the internet. Shuhao From nahuja at mtu.edu Wed Mar 14 14:40:36 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Wed, 14 Mar 2018 14:40:36 -0400 Subject: [Paraview] [EXTERNAL] Help regarding visualization of velocity vector In-Reply-To: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> References: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hello Alan, I mean I do see velocity vectors but they don't point towards the correct flow. All of them seem to point in +x direction. I checked the pressure profile in my intake ports and cylinder, which seems to be similar to what I expect. In addition for Glyph filter, I dont see the option of selecting velocity in data arrays. Thanks Nitisha On Wed, Mar 14, 2018 at 2:25 PM, Scott, W Alan wrote: > Please elaborate on ?it doesn?t seem to work?. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Nitisha Ahuja > *Sent:* Wednesday, March 14, 2018 12:08 PM > *To:* paraview at public.kitware.com > *Subject:* [EXTERNAL] [Paraview] Help regarding visualization of velocity > vector > > > > Hello all, > > This is a very basic query, but I cant seem to figure it out, I am trying > to visualize velocity data for each cell extracted in the vtm file for an > engine simulation. I am able to perfectly visualize the velocity variation > using color map. But I cant understand how to do the same using velocity > vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to > work. > > > > > > Best regards > > Nitisha > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Mar 14 14:43:33 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 14 Mar 2018 18:43:33 +0000 Subject: [Paraview] [EXTERNAL] Help regarding visualization of velocity vector In-Reply-To: References: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> Message-ID: I suspect you are missing setting the Vectors. Here is a tutorial that shows how to do this: https://www.paraview.org/Wiki/Beginning_Sources_and_Filters#Glyph_filter Alan From: Nitisha Ahuja [mailto:nahuja at mtu.edu] Sent: Wednesday, March 14, 2018 12:41 PM To: Scott, W Alan Cc: paraview at public.kitware.com Subject: Re: [EXTERNAL] [Paraview] Help regarding visualization of velocity vector Hello Alan, I mean I do see velocity vectors but they don't point towards the correct flow. All of them seem to point in +x direction. I checked the pressure profile in my intake ports and cylinder, which seems to be similar to what I expect. In addition for Glyph filter, I dont see the option of selecting velocity in data arrays. Thanks Nitisha On Wed, Mar 14, 2018 at 2:25 PM, Scott, W Alan > wrote: Please elaborate on ?it doesn?t seem to work?. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Nitisha Ahuja Sent: Wednesday, March 14, 2018 12:08 PM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] Help regarding visualization of velocity vector Hello all, This is a very basic query, but I cant seem to figure it out, I am trying to visualize velocity data for each cell extracted in the vtm file for an engine simulation. I am able to perfectly visualize the velocity variation using color map. But I cant understand how to do the same using velocity vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to work. Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: From mitribelsky at gmail.com Wed Mar 14 15:24:15 2018 From: mitribelsky at gmail.com (Michael Tribelsky) Date: Wed, 14 Mar 2018 22:24:15 +0300 Subject: [Paraview] Cannot run Paraview 5.x on Win x64 Education Message-ID: Dear users and developers, I am new in Paraview. I've just tried to install it and encountered the following problem. I cannot run Paraview 5.x on Win x64 Education in my notebook Dell Inspiron 17R N7110. When I try to launch it, I get an error message of a type attached below. It happens for any version 5.x. In contrast, version 4.4 (specifically, I tried ParaView-4.4.0-Qt4-Windows-64bit) runs well. Finally, I have tried to launch Paraview 5.x on a desktop computer with the same OS. All versions run well. Can anybody help to fix the problem? Thanks, Michael P.S. The latest graphics drivers from Intel are installed. ============= The Error message (ParaView-5.5.0-RC2-Qt5-Windows-64bit) ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkWin32OpenGLRenderWindow.cxx, line 733 vtkWin32OpenGLRenderWindow (000001E3E7DCE480): We have determined that your graphics system is an Intel SandyBridge based system. These systems only partially support VTK. If you encounter any issues please make sure your graphics drivers from Intel are up to date. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 475 vtkShaderProgram (000001E3EB1C7270): Shader object was not initialized, cannot attach it. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 475 vtkShaderProgram (000001E3EB1C9030): Shader object was not initialized, cannot attach it. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 475 vtkShaderProgram (000001E3EB1C6390): Shader object was not initialized, cannot attach it. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. versionFunctions: Not supported on OpenGL ES ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C6390): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: attribute vec4 ndCoordIn; 18: attribute vec2 texCoordIn; 19: varying vec2 texCoord; 20: void main() 21: { 22: gl_Position = ndCoordIn; 23: texCoord = texCoordIn; 24: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C6390): Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. versionFunctions: Not supported on OpenGL ES ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C6390): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: attribute vec4 ndCoordIn; 18: attribute vec2 texCoordIn; 19: varying vec2 texCoord; 20: void main() 21: { 22: gl_Position = ndCoordIn; 23: texCoord = texCoordIn; 24: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C6390): Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. versionFunctions: Not supported on OpenGL ES ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C6390): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: attribute vec4 ndCoordIn; 18: attribute vec2 texCoordIn; 19: varying vec2 texCoord; 20: void main() 21: { 22: gl_Position = ndCoordIn; 23: texCoord = texCoordIn; 24: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C6390): Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. versionFunctions: Not supported on OpenGL ES ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 781 vtkGenericOpenGLRenderWindow (000001E3E82C6450): GLEW could not be initialized. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C7270): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: //VTK::PositionVC::Dec 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: 56: // Apple Bug 57: //VTK::PrimID::Dec 58: 59: // Value raster 60: //VTK::ValuePass::Dec 61: 62: void main() 63: { 64: //VTK::Color::Impl 65: 66: //VTK::Normal::Impl 67: 68: //VTK::TCoord::Impl 69: 70: //VTK::Clip::Impl 71: 72: //VTK::PrimID::Impl 73: 74: gl_Position = MCDCMatrix * vertexMC; 75: 76: 77: //VTK::ValuePass::Impl 78: 79: //VTK::Light::Impl 80: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C7270): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C9030): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: 18: /*========================================================================= 19: 20: Program: Visualization Toolkit 21: Module: vtkPolyDataVS.glsl 22: 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 24: All rights reserved. 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 26: 27: This software is distributed WITHOUT ANY WARRANTY; without even 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 29: PURPOSE. See the above copyright notice for more information. 30: 31: =========================================================================*/ 32: 33: attribute vec4 vertexMC; 34: 35: // frag position in VC 36: varying vec4 vertexVCVSOutput; 37: 38: // optional normal declaration 39: //VTK::Normal::Dec 40: 41: // extra lighting parameters 42: //VTK::Light::Dec 43: 44: // Texture coordinates 45: //VTK::TCoord::Dec 46: 47: // material property values 48: //VTK::Color::Dec 49: 50: // clipping plane vars 51: //VTK::Clip::Dec 52: 53: // camera and actor matrix values 54: uniform mat4 MCDCMatrix; 55: uniform mat4 MCVCMatrix; 56: 57: // Apple Bug 58: //VTK::PrimID::Dec 59: 60: // Value raster 61: //VTK::ValuePass::Dec 62: 63: void main() 64: { 65: //VTK::Color::Impl 66: 67: //VTK::Normal::Impl 68: 69: //VTK::TCoord::Impl 70: 71: //VTK::Clip::Impl 72: 73: //VTK::PrimID::Impl 74: 75: vertexVCVSOutput = MCVCMatrix * vertexMC; 76: gl_Position = MCDCMatrix * vertexMC; 77: 78: 79: //VTK::ValuePass::Impl 80: 81: //VTK::Light::Impl 82: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C9030): ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 1871 vtkGenericOpenGLRenderWindow (000001E3E82C6450): Hardware does not support the number of textures defined. ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 430 vtkShaderProgram (000001E3EB1C6390): 1: #version 120 2: #ifdef GL_ES 3: #if __VERSION__ == 300 4: #define attribute in 5: #define varying out 6: #endif // 300 7: #else // GL_ES 8: #define highp 9: #define mediump 10: #define lowp 11: #if __VERSION__ == 150 12: #define attribute in 13: #define varying out 14: #endif 15: #endif // GL_ES 16: 17: attribute vec4 ndCoordIn; 18: attribute vec2 texCoordIn; 19: varying vec2 texCoord; 20: void main() 21: { 22: gl_Position = ndCoordIn; 23: texCoord = texCoordIn; 24: } ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 431 vtkShaderProgram (000001E3EB1C6390): Generic Warning: In C:\bbd\7cc78367\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124 vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring. versionFunctions: Not supported on OpenGL ES -------------- next part -------------- An HTML attachment was scrubbed... URL: From nahuja at mtu.edu Wed Mar 14 15:33:42 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Wed, 14 Mar 2018 15:33:42 -0400 Subject: [Paraview] [EXTERNAL] Help regarding visualization of velocity vector In-Reply-To: References: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hello Alan, Thank you for the tutorial, and I will read it and try again. Best regards Nitisha On Wed, Mar 14, 2018 at 2:43 PM, Scott, W Alan wrote: > I suspect you are missing setting the Vectors. Here is a tutorial that > shows how to do this: > > > > https://www.paraview.org/Wiki/Beginning_Sources_and_Filters#Glyph_filter > > > > Alan > > > > *From:* Nitisha Ahuja [mailto:nahuja at mtu.edu] > *Sent:* Wednesday, March 14, 2018 12:41 PM > *To:* Scott, W Alan > *Cc:* paraview at public.kitware.com > *Subject:* Re: [EXTERNAL] [Paraview] Help regarding visualization of > velocity vector > > > > Hello Alan, > > > > I mean I do see velocity vectors but they don't point towards the correct > flow. All of them seem to point in +x direction. I checked the pressure > profile in my intake ports and cylinder, which seems to be similar to what > I expect. In addition for Glyph filter, I dont see the option of selecting > velocity in data arrays. > > > > > > Thanks > > Nitisha > > > > > > > > On Wed, Mar 14, 2018 at 2:25 PM, Scott, W Alan wrote: > > Please elaborate on ?it doesn?t seem to work?. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Nitisha Ahuja > *Sent:* Wednesday, March 14, 2018 12:08 PM > *To:* paraview at public.kitware.com > *Subject:* [EXTERNAL] [Paraview] Help regarding visualization of velocity > vector > > > > Hello all, > > This is a very basic query, but I cant seem to figure it out, I am trying > to visualize velocity data for each cell extracted in the vtm file for an > engine simulation. I am able to perfectly visualize the velocity variation > using color map. But I cant understand how to do the same using velocity > vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to > work. > > > > > > Best regards > > Nitisha > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.nli10me at gmail.com Wed Mar 14 20:27:08 2018 From: greg.nli10me at gmail.com (Greg Fleishman) Date: Wed, 14 Mar 2018 20:27:08 -0400 Subject: [Paraview] PLY files fail to load with scalar/vector fields associated with vertices/faces Message-ID: Hi Paraview users, I'm relatively new to Paraview, but I'll try to describe this problem succinctly: I am working with some mesh files in python using the pymesh package (there are two python packages in existence with that name, I am specifically using this one: http://pymesh.readthedocs.io/en/latest/). According to http://pymesh.readthedocs.io/en/latest/basic.html#saving-mesh, this package will only write out mesh files with attributes affiliated with the vertices/faces in .msh or .ply format. Paraview natively reads .ply format - so that's good at least. However, when I write out such a .ply file (example attached) and attempt to load it in Paraview, none of the scalar data affiliated with the vertices or faces is available in the "color" drop down menu in properties. The scalar fields are also not listed under Information --> Data Arrays. I converted the .ply file to a .vtp file using pvpython (script and .vtp output attached), but again Paraview fails to load any of the scalar fields. This makes sense because the .vtp file doesn't seem to contain any information about the scalar fields, so it seems that the failure to display them could be a failure to even read them in the first place. Can someone point out what I'm doing wrong, or is there just a limitation here in Paraview? Gratefully, Greg M. Fleishman -- Greg M. Fleishman UCLA Bioengineering, PhD 2016 UCLA Bioengineering, MS 2014 UCSD Bioinformatics, BS 2011 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: out.ply Type: application/octet-stream Size: 221912 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: out.vtp Type: application/octet-stream Size: 86685 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ply_convert.py Type: text/x-python-script Size: 312 bytes Desc: not available URL: From gavin.keith.ridley at gmail.com Thu Mar 15 01:53:57 2018 From: gavin.keith.ridley at gmail.com (Gavin Ridley) Date: Thu, 15 Mar 2018 01:53:57 -0400 Subject: [Paraview] Aborted (6) when using pvserver, help setting up? In-Reply-To: References: Message-ID: Hi Utkarsh, Thanks for the suggestion. I followed the page you suggested, and made sure to set up my ccmake variables as specified. Unfortunately, there still seems to be some problem in my setup. I'm trying to render the example sphere source. After I run import paraview > from paraview import * > from paraview.simple import * > from paraview import servermanager > > servermanager.Connect() > > sphere=servermanager.sources.Sphere() > view = servermanager.CreateRenderView() > repSphere = servermanager.CreateRepresentation(sphere, view) > SetActiveView(GetRenderView()) > > Using the command mpirun -np 48 /opt/OpenFOAM/ThirdParty-5.0/paraview_build/bin/pvserver > --mpi --force-offscreen-rendering & > with pvbatch test.py --mpi > in the background. I then get [node0:10234] *** Process received signal *** > [node0:10234] Signal: Segmentation fault (11) > [node0:10234] Signal code: Address not mapped (1) > [node0:10234] Failing at address: (nil) > [node0:10234] [ 0] /lib64/libpthread.so.0(+0x12420)[0x7f218bfda420] > [node0:10234] [ 1] > /usr/lib64/openmpi/lib/paraview/libvtkPVServerManagerCore.so.1(_ZN19vtkSMPropertyHelperC1EP10vtkSMProxyPKcb+0x29)[0x7f2190c8f7c9] > [node0:10234] [ 2] > /usr/lib64/openmpi/lib/paraview/libvtkPVServerManagerCore.so.1(_ZN31vtkSMParaViewPipelineController17RegisterViewProxyEP10vtkSMProxyPKc+0xca)[0x7f2190c7f6da] > [node0:10234] [ 3] > /usr/lib64/openmpi/lib/paraview/libvtkPVServerManagerRendering.so.1(_ZN44vtkSMParaViewPipelineControllerWithRendering17RegisterViewProxyEP10vtkSMProxyPKc+0x25)[0x7f21846b30d5] > [node0:10234] [ 4] > /usr/lib64/openmpi/lib/paraview/libvtkPVServerManagerRenderingPython27D.so.1(+0x51d27)[0x7f2149d19d27] > [node0:10234] [ 5] > /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6517)[0x7f218acf8227] > [node0:10234] [ 6] > /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f218acfb198] > [node0:10234] [ 7] > /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6483)[0x7f218acf8193] > [node0:10234] [ 8] > /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f218acfb198] > [node0:10234] [ 9] /lib64/libpython2.7.so.1.0(+0xb7037)[0x7f218ac47037] > [node0:10234] [10] > /lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7f218ac31343] > [node0:10234] [11] > /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x4c6f)[0x7f218acf697f] > [node0:10234] [12] > /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f218acfb198] > [node0:10234] [13] > /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6483)[0x7f218acf8193] > [node0:10234] [14] > /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f218acfb198] > [node0:10234] [15] > /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6483)[0x7f218acf8193] > [node0:10234] [16] > /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f218acfb198] > [node0:10234] [17] > /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f218acfb3a9] > [node0:10234] [18] /lib64/libpython2.7.so.1.0(+0x17139f)[0x7f218ad0139f] > [node0:10234] [19] > /lib64/libpython2.7.so.1.0(PyRun_FileExFlags+0x8a)[0x7f218ad0134a] > [node0:10234] [20] > /lib64/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0x19e)[0x7f218ad0123e] > [node0:10234] [21] > /lib64/libpython2.7.so.1.0(Py_Main+0x689)[0x7f218ad07519] > [node0:10234] [22] > /usr/lib64/openmpi/lib/paraview/pvbatch(_ZN14ParaViewPython3RunEiiPPc+0x200)[0x565241ad4250] > [node0:10234] [23] /lib64/libc.so.6(__libc_start_main+0xea)[0x7f2189f1888a] > [node0:10234] [24] > /usr/lib64/openmpi/lib/paraview/pvbatch(_start+0x2a)[0x565241ad3e8a] > [node0:10234] *** End of error message *** > Segmentation fault > > Do you have any insight on this segfault? Thanks, and have a nice day, Gavin On Tue, Mar 13, 2018 at 1:45 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Gavin, > > Your ParaView build is not OSMesa enabled. You'll need to build your > own version with OSMesa enabled. > > For ParaView 5.5, this page summarizes how to do that: > https://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/Offscreen.html > > Utkarsh > > > On Tue, Mar 13, 2018 at 1:25 PM, Gavin Ridley > wrote: > > Hi all, > > > > I'd like to use MPI pvserver to take advantage of some 48 core nodes we > have > > on our cluster. There's not much in the way of GPUs, so I've been trying > to > > take the route of using OSMesa with --use-offscreen-rendering. The > pvserver > > seems to start well, but as soon as a client connects, the thing aborts. > In > > particular, if I try to use pvbatch with a basic sphere rendering, the > > pvserver crashes on running the Render(view) part of the script. Pasted > > below is the error. > > > > Does anyone have any insight on this? > > > >> Waiting for client... > >> Connection URL: cs://node0:11111 > >> Accepting connection(s): node0:11111 > >> [node0:55287] 47 more processes have sent help message > >> help-mpi-btl-base.txt / btl:no-nics > >> [node0:55287] Set MCA parameter "orte_base_help_aggregate" to 0 to see > all > >> help / error messages > >> d^LClient connected. > >> [node0:55292] *** Process received signal *** > >> [node0:55292] Signal: Aborted (6) > >> [node0:55292] Signal code: (-6) > >> [node0:55292] [ 0] /lib64/libpthread.so.0(+0x12420)[0x7fbf80742420] > >> [node0:55292] [ 1] /lib64/libc.so.6(gsignal+0xcb)[0x7fbf7e2f69fb] > >> [node0:55292] [ 2] /lib64/libc.so.6(abort+0x1b0)[0x7fbf7e2f8800] > >> [node0:55292] [ 3] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow13Cr > eateAWindowEv+0x4e2)[0x7fbf6adf6964] > >> [node0:55292] [ 4] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow29Cre > ateHardwareOffScreenWindowEii+0xa2)[0x7fbf6ad5aa1c] > >> [node0:55292] [ 5] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow21Cr > eateOffScreenWindowEii+0x32)[0x7fbf6adf7be6] > >> [node0:55292] [ 6] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkRenderingOpenGL2-pv5.4.so.1(_ZN22vtkXOpenGLRenderWindow10In > itializeEv+0xaa)[0x7fbf6adf7ffc] > >> [node0:55292] [ 7] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkRenderingOpenGL2-pv5.4.so.1(_ZN21vtkOpenGLRenderWindow14Sup > portsOpenGLEv+0x105)[0x7fbf6ad5beb7] > >> [node0:55292] [ 8] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVClientServerCoreRendering-pv5.4.so.1(_ > ZN23vtkPVDisplayInformation21SupportsOpenGLLocallyEv+0xeb)[0x7fbf78223b81] > >> [node0:55292] [ 9] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVClientServerCoreRendering-pv5.4.so.1(_ > ZN23vtkPVDisplayInformation14CopyFromObjectEP9vtkObject+ > 0x31)[0x7fbf78223c05] > >> [node0:55292] [10] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(_ > ZN16vtkPVSessionCore25GatherInformationInternalEP16vtkPVInfo > rmationj+0x38)[0x7fbf85c8a890] > >> [node0:55292] [11] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(_ > ZN16vtkPVSessionCore17GatherInformationEjP16vtkPVInformation > j+0x8d)[0x7fbf85c8ab45] > >> [node0:55292] [12] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(_ > ZN16vtkPVSessionBase17GatherInformationEjP16vtkPVInformation > j+0x3e)[0x7fbf85c866fc] > >> [node0:55292] [13] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(_ > ZN18vtkPVSessionServer25GatherInformationInternalEjPKcjR21vt > kMultiProcessStream+0xb7)[0x7fbf85c974b9] > >> [node0:55292] [14] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(_ > ZN18vtkPVSessionServer24OnClientServerMessageRMIEPvi+0x561)[ > 0x7fbf85c97225] > >> [node0:55292] [15] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVServerImplementationCore-pv5.4.so.1(+0xa537a)[0x7fbf85c9537a] > >> [node0:55292] [16] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController1 > 0ProcessRMIEiPvii+0x356)[0x7fbf826a06ea] > >> [node0:55292] [17] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkParallelCore-pv5.4.so.1(_ZN25vtkMultiProcessController1 > 1ProcessRMIsEii+0x6b5)[0x7fbf826a02bb] > >> [node0:55292] [18] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager > 21ProcessEventsInternalEmb+0x46d)[0x7fbf85986311] > >> [node0:55292] [19] > >> /opt/OpenFOAM/ThirdParty-5.0/ParaView-5.4.0/build/lib/ > libvtkPVClientServerCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager > 13ProcessEventsEm+0x28)[0x7fbf85985ea2] > >> [node0:55292] [20] ./pvserver[0x401acb] > >> [node0:55292] [21] ./pvserver(main+0x25)[0x401b7f] > >> [node0:55292] [22] > >> /lib64/libc.so.6(__libc_start_main+0xea)[0x7fbf7e2e088a] > >> [node0:55292] [23] ./pvserver(_start+0x2a)[0x4017ca] > >> [node0:55292] *** End of error message *** > >> > > > > -- > > Thanks, > > Gavin Ridley > > > > _______________________________________________ > > 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: > > https://public.kitware.com/mailman/listinfo/paraview > > > -- Thanks, Gavin Ridley -------------- next part -------------- An HTML attachment was scrubbed... URL: From sonphan.it at gmail.com Thu Mar 15 06:56:11 2018 From: sonphan.it at gmail.com (PHAN Minh Son) Date: Thu, 15 Mar 2018 11:56:11 +0100 Subject: [Paraview] [EXTERNAL] RGB volume rendering In-Reply-To: References: Message-ID: Hi Alan, I've imported my 3d rgb volume (.tiff format) in paraview and the render volume (attached image) is not really what I expect, since it seems not to be rgb color. I'm just a newbie in paraview so maybe there're functions allowing to do that... Best regards, Son 2018-03-14 17:42 GMT+01:00 Scott, W Alan : > Should work. Have you tried? Then, you can slice it, or contour it. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *PHAN Minh Son > *Sent:* Wednesday, March 14, 2018 10:17 AM > *To:* paraview at public.kitware.com > *Subject:* [EXTERNAL] [Paraview] RGB volume rendering > > > > Hi all, > > I'm currently working with a 3D color volume (RGB image stack in .tiff > format). Is there anyway to render it in paraview? > > Best regards, > > Son > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rgbvolume_paraview.png Type: image/png Size: 534061 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 15 10:46:58 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 15 Mar 2018 10:46:58 -0400 Subject: [Paraview] Idea: move from mailing lists to discourse Message-ID: Folks, I know ITK community have moved on to discourse (https://discourse.itk.org/) and from what I've heard, the experience has been great. Is it time for ParaView mailing lists to move to Discourse as well? What are people's feelings about it? Utkarsh From agsmith424 at gmail.com Thu Mar 15 11:16:09 2018 From: agsmith424 at gmail.com (Andy Smith) Date: Thu, 15 Mar 2018 11:16:09 -0400 Subject: [Paraview] Status of XDMF3 Reader in ParaView Message-ID: Currently in our CFD code we output XDMF and use the XDMF2 reader in ParaView. I would like to add the capability to output arbitrary polyhedra but it appears support for this was only added in XDMF3. Because of this I plan to change the output to a format that is compatible with XDMF3 but face at least two major issues that are preventing me from using XDMF3: 1. XDMF cannot handle functions properly (https://gitlab.kitware.com/ paraview/paregaview/issues/17516 ). I use functions to join scalars to make vectors. 2. Inability to select certain blocks of a multiblock dataset before reading data. This feature allows the user to only load a subset of the complete multiblock dataset and saves a large amount of time. (see my final comment in a post about a year ago https://public.kitware.com/pipermail/paraview/2017-March/039605.html) I can think of three options going forward: 1. Get functions and block selection during loading working in XDMF3 (best option). 2. Back-port arbitrary polyhedra support to XDMF2 (looks doable, but not appealing since eventually XDMF2 will go away). 3. Split arbitrary polyhedra into tetrahedra in the solver (probably most complicated and least ideal since the visualization no longer completely represents the actual flow field). I've attached a simple multiblock dataset that works using the XDMF2 reader and demonstrates both issues with the XDMF3 reader. The function problem is a known issue, but perhaps I'm doing something wrong in my file formatting that prevents the selection of individual blocks during loading. I'm open to any assessment of my proposed options and any suggestions on what I can do to help. Thanks, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mixed_multiblock_xdmf2_join.xmf Type: application/octet-stream Size: 4851 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mixed_multiblock_xdmf3_join.xmf Type: application/octet-stream Size: 4839 bytes Desc: not available URL: From cory.quammen at kitware.com Thu Mar 15 11:24:29 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 15 Mar 2018 11:24:29 -0400 Subject: [Paraview] Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: +1 Discourse includes a mailing list mode that, with some caveats, behaves like the current mailing list if you prefer that mode. The integrated search feature is nice to have - I usually resort to searching the ParaView mailing list in markmail's archive, which usually works, but an additional step that wouldn't be needed with an integrated search. Having different categories for beginners, developers, announcements, etc. would be great. You can watch or unwatch different categories, tag posts with keywords, and bookmark certain posts you'd like to revisit. It just seems great all around. Cory On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Folks, > > I know ITK community have moved on to discourse > (https://discourse.itk.org/) and from what I've heard, the experience > has been great. Is it time for ParaView mailing lists to move to > Discourse as well? > > What are people's feelings about it? > > Utkarsh > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pivello at gmail.com Thu Mar 15 12:45:54 2018 From: pivello at gmail.com (=?UTF-8?Q?M=C3=A1rcio_Ricardo_Pivello?=) Date: Thu, 15 Mar 2018 13:45:54 -0300 Subject: [Paraview] Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: +1 On 15 March 2018 at 12:24, Cory Quammen wrote: > +1 > > Discourse includes a mailing list mode that, with some caveats, behaves > like the current mailing list if you prefer that mode. The integrated > search feature is nice to have - I usually resort to searching the ParaView > mailing list in markmail's archive, which usually works, but an additional > step that wouldn't be needed with an integrated search. Having different > categories for beginners, developers, announcements, etc. would be great. > You can watch or unwatch different categories, tag posts with keywords, and > bookmark certain posts you'd like to revisit. It just seems great all > around. > > Cory > > > > On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Folks, >> >> I know ITK community have moved on to discourse >> (https://discourse.itk.org/) and from what I've heard, the experience >> has been great. Is it time for ParaView mailing lists to move to >> Discourse as well? >> >> What are people's feelings about it? >> >> Utkarsh >> _______________________________________________ >> 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: >> https://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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Marcio Ricardo Pivello -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 15 12:46:08 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 15 Mar 2018 16:46:08 +0000 Subject: [Paraview] [EXTERNAL] Re: Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: Without much study, I agree with Cory. The current e-mail system feels unwieldy and noisy to me, and is hard to search. Furthermore, I find it hard to browse back in time for something I remember, but can?t find the search terms for (and have deleted). Discourse feels closer to our current gitlab bug tracker, which has been very successful. Let a tool manage the mailing list, rather than my inbox. +1. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Cory Quammen Sent: Thursday, March 15, 2018 9:24 AM To: Ayachit, Utkarsh (External Contacts) Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] Idea: move from mailing lists to discourse +1 Discourse includes a mailing list mode that, with some caveats, behaves like the current mailing list if you prefer that mode. The integrated search feature is nice to have - I usually resort to searching the ParaView mailing list in markmail's archive, which usually works, but an additional step that wouldn't be needed with an integrated search. Having different categories for beginners, developers, announcements, etc. would be great. You can watch or unwatch different categories, tag posts with keywords, and bookmark certain posts you'd like to revisit. It just seems great all around. Cory On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit > wrote: Folks, I know ITK community have moved on to discourse (https://discourse.itk.org/) and from what I've heard, the experience has been great. Is it time for ParaView mailing lists to move to Discourse as well? What are people's feelings about it? Utkarsh _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Mar 15 13:02:08 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 15 Mar 2018 13:02:08 -0400 Subject: [Paraview] [EXTERNAL] Re: Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: If we can get vtk consensus, we should move that at the same time. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 15, 2018 at 12:46 PM, Scott, W Alan wrote: > Without much study, I agree with Cory. The current e-mail system feels > unwieldy and noisy to me, and is hard to search. Furthermore, I find it > hard to browse back in time for something I remember, but can?t find the > search terms for (and have deleted). Discourse feels closer to our current > gitlab bug tracker, which has been very successful. Let a tool manage the > mailing list, rather than my inbox. > > > > +1. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Cory Quammen > *Sent:* Thursday, March 15, 2018 9:24 AM > *To:* Ayachit, Utkarsh (External Contacts) > *Cc:* ParaView > *Subject:* [EXTERNAL] Re: [Paraview] Idea: move from mailing lists to > discourse > > > > +1 > > > > Discourse includes a mailing list mode that, with some caveats, behaves > like the current mailing list if you prefer that mode. The integrated > search feature is nice to have - I usually resort to searching the ParaView > mailing list in markmail's archive, which usually works, but an additional > step that wouldn't be needed with an integrated search. Having different > categories for beginners, developers, announcements, etc. would be great. > You can watch or unwatch different categories, tag posts with keywords, and > bookmark certain posts you'd like to revisit. It just seems great all > around. > > > > Cory > > > > > > > > On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > > Folks, > > I know ITK community have moved on to discourse > (https://discourse.itk.org/) and from what I've heard, the experience > has been great. Is it time for ParaView mailing lists to move to > Discourse as well? > > What are people's feelings about it? > > Utkarsh > _______________________________________________ > 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: > https://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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Mar 15 13:02:08 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 15 Mar 2018 13:02:08 -0400 Subject: [Paraview] [EXTERNAL] Re: Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: If we can get vtk consensus, we should move that at the same time. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 15, 2018 at 12:46 PM, Scott, W Alan wrote: > Without much study, I agree with Cory. The current e-mail system feels > unwieldy and noisy to me, and is hard to search. Furthermore, I find it > hard to browse back in time for something I remember, but can?t find the > search terms for (and have deleted). Discourse feels closer to our current > gitlab bug tracker, which has been very successful. Let a tool manage the > mailing list, rather than my inbox. > > > > +1. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Cory Quammen > *Sent:* Thursday, March 15, 2018 9:24 AM > *To:* Ayachit, Utkarsh (External Contacts) > *Cc:* ParaView > *Subject:* [EXTERNAL] Re: [Paraview] Idea: move from mailing lists to > discourse > > > > +1 > > > > Discourse includes a mailing list mode that, with some caveats, behaves > like the current mailing list if you prefer that mode. The integrated > search feature is nice to have - I usually resort to searching the ParaView > mailing list in markmail's archive, which usually works, but an additional > step that wouldn't be needed with an integrated search. Having different > categories for beginners, developers, announcements, etc. would be great. > You can watch or unwatch different categories, tag posts with keywords, and > bookmark certain posts you'd like to revisit. It just seems great all > around. > > > > Cory > > > > > > > > On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > > Folks, > > I know ITK community have moved on to discourse > (https://discourse.itk.org/) and from what I've heard, the experience > has been great. Is it time for ParaView mailing lists to move to > Discourse as well? > > What are people's feelings about it? > > Utkarsh > _______________________________________________ > 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: > https://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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.coutinho at redstack.nl Thu Mar 15 14:06:53 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Thu, 15 Mar 2018 18:06:53 +0000 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: I'm again having this issue where I can't access the GPU unless someone is logged into the computer and in an active X session. Adding the appropriate users to the 'video' group makes it possible that I can access the GPU from another user that is also in the video group, but at least one user needs to be logged in. If I restart the machine then I'm out of the luck, and I get the 'can't open the display' error. I was assuming that the computer would just need to be turned on to be able to connect to it remotely, and hopefully I'm missing something here. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 21:49 To: Burlen Loring ; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I spoke too soon, apparently my issue was that the users were not part of the 'video' group. After adding the various users to the video group the problem is gone. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: Chris Coutinho Sent: vrijdag 9 maart 2018 21:18 To: Chris Coutinho >; Burlen Loring >; paraview at public.kitware.com Subject: RE: [Paraview] Utilizing Server GPU from an external command I'm running into some other trouble related to accessing the remote server. I'm able to successfully use the remote GPU from a client when the ssh user is also logged into the machine and in a X session (specifically Gnome). Is it possible to access the remote GPU without being logged in as the same user that is doing the ssh remote connection? Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 14:25 To: Burlen Loring >; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] Thanks for the explanation Burlen, It was indeed an issue with xhost as you alluded to. On the server I added my user to the list of authorized clients: xhost +SI:localhost: Another point that I need to do was remove the Mesa library from the server, which was probably on the system because the nvidia drivers were installed later. After removing the Mesa library, adding my user to the authorized clients for xhost, and appending the DISPLAY variable to my pvserver command fixes the problem that I originally had. Here's my current working command: ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering I wasn't able to get reverse connection to work correctly, so I removed that argument from the command, It's not entirely clear to me why I would need it. From the documentation it seems like a requirement if the client and server are on separate sides of a firewall. That's not the case for me and it works without. Thanks again for your quick response. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: vrijdag 9 maart 2018 00:10 To: Chris Coutinho >; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: mailto:c.coutinho at redstack.nl www: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgBlP1BBG4d2Qc9c%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=ppWU%2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79QRckMVrqNx0C4%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj%2Fia5JybxTjwogouuvMDDM%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=CLy4wjpS8X%2BGRr%2BMg3NO6Qk5wH5VeB3HXCMi%2BDlJO5U%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=igqu1EcbsSmPhPhO5%2FDI6Z4BsvpcVB2W2uv7f3tjUSY%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=oZIizGIz2BfpfQBQfckT%2BEasEmUgyBkiwRcaFq2Xzw4%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=GjHPU3y0CG4WvfZAdeMGiUhivfeveHFxnh02nYstgRA%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=KHyicRnmepnJUhkw2PXJA3nQpvrGPhPXRekUfcWBa8g%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Mar 15 14:11:54 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 15 Mar 2018 14:11:54 -0400 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: Hi Chris, Most operating systems have this restriction that unless a user is logged in a display session will not be created. What you probably want is something like OSMesa (uses CPU rendering but requires no X session) or EGL (I'm less familiar with this, but I think it lets you render without an X session. It is limited to some NVidia cards/drivers though). VTK has support for both of those options. Alternatively you could set up a dummy user with auto-login and then just use the video group like you mentioned. HTH, Shawn On Thu, Mar 15, 2018 at 2:06 PM, Chris Coutinho wrote: > I'm again having this issue where I can't access the GPU unless someone is > logged into the computer and in an active X session. Adding the appropriate > users to the 'video' group makes it possible that I can access the GPU from > *another* user that is also in the video group, but at least one user > needs to be logged in. If I restart the machine then I?m out of the luck, > and I get the ?can't open the display? error. > > > > I was assuming that the computer would just need to be turned on to be > able to connect to it remotely, and hopefully I?m missing something here. > > > > Met vriendlijke groet, > > REDstack BV > > > > Chris Coutinho > > Onderzoeker/Data analist > > > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of > Chris Coutinho > Sent: vrijdag 9 maart 2018 21:49 > To: Burlen Loring ; paraview at public.kitware.com > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > > > [This sender failed our fraud detection checks and may not be who they > appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > > > I spoke too soon, apparently my issue was that the users were not part of > the 'video' group. After adding the various users to the video group the > problem is gone. > > > > > > Met vriendlijke groet, > > REDstack BV > > > > Chris Coutinho > > Onderzoeker/Data analist > > > > -----Original Message----- > > From: Chris Coutinho > > Sent: vrijdag 9 maart 2018 21:18 > > To: Chris Coutinho ; Burlen Loring < > burlen.loring at gmail.com>; paraview at public.kitware.com > > Subject: RE: [Paraview] Utilizing Server GPU from an external command > > > > I'm running into some other trouble related to accessing the remote > server. I'm able to successfully use the remote GPU from a client when the > ssh user is also logged into the machine and in a X session (specifically > Gnome). > > > > Is it possible to access the remote GPU without being logged in as the > same user that is doing the ssh remote connection? > > > > > > > > Met vriendlijke groet, > > REDstack BV > > > > Chris Coutinho > > Onderzoeker/Data analist > > > > -----Original Message----- > > From: ParaView [mailto:paraview-bounces at public.kitware.com > ] On Behalf Of Chris Coutinho > > Sent: vrijdag 9 maart 2018 14:25 > > To: Burlen Loring ; paraview at public.kitware.com > > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > > > [This sender failed our fraud detection checks and may not be who they > appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > > > Thanks for the explanation Burlen, > > > > It was indeed an issue with xhost as you alluded to. On the server I added > my user to the list of authorized clients: > > > > xhost +SI:localhost: > > > > Another point that I need to do was remove the Mesa library from the > server, which was probably on the system because the nvidia drivers were > installed later. After removing the Mesa library, adding my user to the > authorized clients for xhost, and appending the DISPLAY variable to my > pvserver command fixes the problem that I originally had. > > > > Here's my current working command: > > > > ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver > --server-port=11111 --client-host= --use-offscreen-rendering > > > > I wasn't able to get reverse connection to work correctly, so I removed > that argument from the command, It's not entirely clear to me why I would > need it. From the documentation it seems like a requirement if the client > and server are on separate sides of a firewall. That's not the case for me > and it works without. > > > > Thanks again for your quick response. > > > > > > Met vriendlijke groet, > > REDstack BV > > > > Chris Coutinho > > Onderzoeker/Data analist > > > > From: Burlen Loring [mailto:burlen.loring at gmail.com > ] > > Sent: vrijdag 9 maart 2018 00:10 > > To: Chris Coutinho ; paraview at public.kitware.com > > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > > > Hi Chris, > > > > You are right "ssh -X" sends X11 commands back to the client. that is not > what you want, so do not use -X option in your ssh command. > > > > Assuming that an X server is running on the server in question (sounds > like it is), there are 2 additional things that you need to make this work. > > 1. Your ssh user needs to be allowed to make connections to the X server > 2. You need to tell programs which display to use. > > > > To see if your user can make connections to the X server: > > ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it > will print out the current access control list. You should see your user > name. If that is the case then you should be all set. If it fails it may > say something about "no protocol" and "can't open the display" or > something similar. If it fails then you'll need to add your user to the > access control list. See man page of xhost command for details. > > > > To tell a program which display to use set the DISPLAY environment > variable. For instance if your user can make connections to X server as > described above you should be able to run stuff like "ssh user at server > DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode > something like this may work for you ssh -R N:localhost:N user at server > DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection > Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: > > Hello ParaView users, > > > > In short: > > I'm having an issue with utilizing a servers graphics card via ssh. When > starting the pvserver manually from the server I don't experience any > problems, but attempting to start a pvserver remotely from my client > through ssh, I run into problems. I am new to configuring ssh and don't > really know what the root of my problem is. > > > > > > The problem: > > I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support > enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing > this server from a Windows (laptop) client within a VPN network. The client > laptop has the identical The server has a single Nvidia graphics card > installed (Quadro K2200), when I start the server manually on the server > I'm able to connect to it from the client and utilize the server GPU; > however, when sending the same pvserver command through ssh via the client, > I get the 'Display is not accessible on the server side' error. > > > > To start the pvserver manually from the server itself I execute a command > similar to this: > > > > mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 > --client-host= --use-offscreen-rendering > > > > After I execute this command from the server, I've been able to confirm > that the client is using the server's graphics card by looking at the > output of `nvidia-smi` > > > > > > My remote connection string looks like this: > > > > ssh @ mpiexec -np 8 /usr/local/bin/pvserver > --server-port=11111 --client-host= --use-offscreen-rendering > > > > Indeed, after connecting to my remote server using the remote connection > via the client, I saw that there was no utilization of the graphics card > via `nvidia-smi`. > > > > > > > > Here is the output of `glxgears` related to OpenGL from the server: > > > > ``` > > $ glxinfo | grep -i opengl > > OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro > K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 > OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL > core profile context flags: (none) OpenGL core profile profile mask: core > profile OpenGL core profile extensions: > > OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version > string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: > (none) OpenGL extensions: > > OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES > profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES > profile extensions: > > ``` > > > > Here is the same output from an ssh connection from the client: > > > > ``` > > ssh @ glxinfo | grep -i opengl > > Error: unable to open display > > ``` > > > > And the same with x forwarding enabled (via Xming installed on the client): > > > > ``` > > ssh -X @ glxinfo | grep -i opengl > > Warning: No xauth data; using fake authentication data for X11 forwarding. > > OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on > llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL > shading language version string: 1.30 OpenGL context flags: (none) OpenGL > extensions: > > ``` > > > > Looking at this output I'm coming to the conclusion that my ssh connection > is using the graphics driver of my client machine, but I actually want to > utilize the servers GPU. Is this a use case for reverse port tunneling or > something similar? > > > > I've attempted a simiar reverse connection as follows, but this doesn't > give me any info on the gpu: > > > > ``` > > ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl > > Warning: No xauth data; using fake authentication data for X11 forwarding. > > OpenGL vendor string: VMware, Inc. > > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version > string: 1.30 OpenGL context flags: (none) OpenGL extensions: > > ``` > > > > I'm sure this is a common issue and has been solved previously, but I'm > unable to parse through the mailing lists effectively to get at my problem. > It's also possible that I'm looking for a solution in the wrong place. Both > of these systems are in a VPN, so maybe ssh isn't necessary, but I don't > know of another way of starting the pvserver remotely without ssh. > > > > > > Thanks in advance, > > Chris > > > > > > > > Met vriendlijke groet, > > REDstack BV > > > > Chris Coutinho > > Onderzoeker/Data Analist > > > > tel: +31 (0)6 - 2222 5785 > > post: Postbox 199, 8600 AD Sneek > > bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek > > email: mailto:c.coutinho at redstack.nl > > www: https://emea01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQa > mH%2FUxjuwaTviE%3D&reserved=0 > > > > > > > > _______________________________________________ > > Powered by https://emea01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4 > PuoYpUlj2f66Q%3D&reserved=0 > > > > Visit other Kitware open-source projects at https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com% > 2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN% > 2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 > > > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02% > 7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216% > 7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata= > ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 > > > > Search the list archives at: https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux% > 2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 > > > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1 > P6RjCVXUDqHoI%3D&reserved=0 > > > > _______________________________________________ > > Powered by https://emea01.safelinks.protection.outlook.com/?url= > www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgB > lP1BBG4d2Qc9c%3D&reserved=0 > > > > Visit other Kitware open-source projects at https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com% > 2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636561987266124728&sdata=ppWU% > 2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 > > > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02% > 7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac% > 7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata= > sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 > > > > Search the list archives at: https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79 > QRckMVrqNx0C4%3D&reserved=0 > > > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj% > 2Fia5JybxTjwogouuvMDDM%3D&reserved=0 > > _______________________________________________ > > Powered by https://emea01.safelinks.protection.outlook.com/?url= > www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636562253436127180&sdata=CLy4wjpS8X%2BGRr% > 2BMg3NO6Qk5wH5VeB3HXCMi%2BDlJO5U%3D&reserved=0 > > > > Visit other Kitware open-source projects at https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com% > 2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636562253436127180&sdata=igqu1EcbsSmPhPhO5% > 2FDI6Z4BsvpcVB2W2uv7f3tjUSY%3D&reserved=0 > > > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02% > 7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1% > 7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata= > oZIizGIz2BfpfQBQfckT%2BEasEmUgyBkiwRcaFq2Xzw4%3D&reserved=0 > > > > Search the list archives at: https://emea01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636562253436137183&sdata=GjHPU3y0CG4WvfZAdeMGiUhivfeveH > Fxnh02nYstgRA%3D&reserved=0 > > > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl% > 7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871 > a965%7C0%7C0%7C636562253436137183&sdata=KHyicRnmepnJUhkw2PXJA3nQpvrGPh > PXRekUfcWBa8g%3D&reserved=0 > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Mar 15 14:32:32 2018 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 15 Mar 2018 11:32:32 -0700 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: You may need to start an xserver before starting up pvserver. I had set this up for a UT system a long time ago. On that system there were 8 gpus, when someone wanted to use ParaView we had to first ask the scheduler for a gpu, then run xinit to bring the x server up on the display associated with the gpu assigned to us. details of that set up are here https://github.com/burlen/pvserver-configs/blob/master/servers/nautilus/3.10.0-x/start_pvserver-x.qsub Of course this system is not a workstation, and thus has no option to log in directly. I do not know how the above would need to be tweaked to work on workstation configurations... On 03/15/2018 11:06 AM, Chris Coutinho wrote: > > I'm again having this issue where I can't access the GPU unless > someone is logged into the computer and in an active X session. Adding > the appropriate users to the 'video' group makes it possible that I > can access the GPU from /another/ user that is also in the video > group, but at least one user needs to be logged in. If I restart the > machine then I?m out of the luck, and I get the ?can't open the > display? error. > > I was assuming that the computer would just need to be turned on to be > able to connect to it remotely, and hopefully I?m missing something here. > > Met vriendlijke groet, > > REDstack BV > > Chris Coutinho > > Onderzoeker/Data analist > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf > Of Chris Coutinho > Sent: vrijdag 9 maart 2018 21:49 > To: Burlen Loring ; paraview at public.kitware.com > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > [This sender failed our fraud detection checks and may not be who they > appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > I spoke too soon, apparently my issue was that the users were not part > of the 'video' group. After adding the various users to the video > group the problem is gone. > > Met vriendlijke groet, > > REDstack BV > > Chris Coutinho > > Onderzoeker/Data analist > > -----Original Message----- > > From: Chris Coutinho > > Sent: vrijdag 9 maart 2018 21:18 > > To: Chris Coutinho >; Burlen Loring > >; > paraview at public.kitware.com > > Subject: RE: [Paraview] Utilizing Server GPU from an external command > > I'm running into some other trouble related to accessing the remote > server. I'm able to successfully use the remote GPU from a client when > the ssh user is also logged into the machine and in a X session > (specifically Gnome). > > Is it possible to access the remote GPU without being logged in as the > same user that is doing the ssh remote connection? > > Met vriendlijke groet, > > REDstack BV > > Chris Coutinho > > Onderzoeker/Data analist > > -----Original Message----- > > From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf > Of Chris Coutinho > > Sent: vrijdag 9 maart 2018 14:25 > > To: Burlen Loring >; paraview at public.kitware.com > > > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > [This sender failed our fraud detection checks and may not be who they > appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > Thanks for the explanation Burlen, > > It was indeed an issue with xhost as you alluded to. On the server I > added my user to the list of authorized clients: > > xhost +SI:localhost: > > Another point that I need to do was remove the Mesa library from the > server, which was probably on the system because the nvidia drivers > were installed later. After removing the Mesa library, adding my user > to the authorized clients for xhost, and appending the DISPLAY > variable to my pvserver command fixes the problem that I originally had. > > Here's my current working command: > > ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver > --server-port=11111 --client-host= --use-offscreen-rendering > > I wasn't able to get reverse connection to work correctly, so I > removed that argument from the command, It's not entirely clear to me > why I would need it. From the documentation it seems like a > requirement if the client and server are on separate sides of a > firewall. That's not the case for me and it works without. > > Thanks again for your quick response. > > Met vriendlijke groet, > > REDstack BV > > Chris Coutinho > > Onderzoeker/Data analist > > From: Burlen Loring [mailto:burlen.loring at gmail.com] > > Sent: vrijdag 9 maart 2018 00:10 > > To: Chris Coutinho >; paraview at public.kitware.com > > > Subject: Re: [Paraview] Utilizing Server GPU from an external command > > Hi Chris, > > You are right "ssh -X" sends X11 commands back to the client. that is > not what you want, so do not use -X option in your ssh command. > > Assuming that an X server is running on the server in question (sounds > like it is), there are 2 additional things that you need to make this > work. > > 1. Your ssh user needs to be allowed to make connections to the X > server 2. You need to tell programs which display to use. > > To see if your user can make connections to the X server: > > ssh into the server. run "DISPLAY=:0.0 xhost". If this command > succeeds it will print out the current access control list. You should > see your user name. If that is the case then you should be all set. If > it fails it may say something about "no protocol" and "can't open the > display" or something similar. If it fails then you'll need to add > your user to the access control list. See man page of xhost command > for details. > > To tell a program which display to use set the DISPLAY environment > variable. For instance if your user can make connections to X server > as described above you should be able to run stuff like "ssh > user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse > connection mode something like this may work for you ssh -R > N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver > --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, > Chris Coutinho wrote: > > Hello ParaView users, > > In short: > > I'm having an issue with utilizing a servers graphics card via ssh. > When starting the pvserver manually from the server I don't experience > any problems, but attempting to start a pvserver remotely from my > client through ssh, I run into problems. I am new to configuring ssh > and don't really know what the root of my problem is. > > The problem: > > I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support > enabled on an OpenSUSE Leap 42.3 workstation, with the goal of > accessing this server from a Windows (laptop) client within a VPN > network. The client laptop has the identical The server has a single > Nvidia graphics card installed (Quadro K2200), when I start the server > manually on the server I'm able to connect to it from the client and > utilize the server GPU; however, when sending the same pvserver > command through ssh via the client, I get the 'Display is not > accessible on the server side' error. > > To start the pvserver manually from the server itself I execute a > command similar to this: > > mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 > --client-host= --use-offscreen-rendering > > After I execute this command from the server, I've been able to > confirm that the client is using the server's graphics card by looking > at the output of `nvidia-smi` > > My remote connection string looks like this: > > ssh @ mpiexec -np 8 /usr/local/bin/pvserver > --server-port=11111 --client-host= --use-offscreen-rendering > > Indeed, after connecting to my remote server using the remote > connection via the client, I saw that there was no utilization of the > graphics card via `nvidia-smi`. > > Here is the output of `glxgears` related to OpenGL from the server: > > ``` > > $ glxinfo | grep -i opengl > > OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: > Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 > NVIDIA 390.25 OpenGL core profile shading language version string: > 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core > profile profile mask: core profile OpenGL core profile extensions: > > OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language > version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL > profile mask: (none) OpenGL extensions: > > OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL > ES profile shading language version string: OpenGL ES GLSL ES 3.20 > OpenGL ES profile extensions: > > ``` > > Here is the same output from an ssh connection from the client: > > ``` > > ssh @ glxinfo | grep -i opengl > > Error: unable to open display > > ``` > > And the same with x forwarding enabled (via Xming installed on the > client): > > ``` > > ssh -X @ glxinfo | grep -i opengl > > Warning: No xauth data; using fake authentication data for X11 forwarding. > > OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 > on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa > 17.0.5 OpenGL shading language version string: 1.30 OpenGL context > flags: (none) OpenGL extensions: > > ``` > > Looking at this output I'm coming to the conclusion that my ssh > connection is using the graphics driver of my client machine, but I > actually want to utilize the servers GPU. Is this a use case for > reverse port tunneling or something similar? > > I've attempted a simiar reverse connection as follows, but this > doesn't give me any info on the gpu: > > ``` > > ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl > > Warning: No xauth data; using fake authentication data for X11 forwarding. > > OpenGL vendor string: VMware, Inc. > > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version > string: 1.30 OpenGL context flags: (none) OpenGL extensions: > > ``` > > I'm sure this is a common issue and has been solved previously, but > I'm unable to parse through the mailing lists effectively to get at my > problem. It's also possible that I'm looking for a solution in the > wrong place. Both of these systems are in a VPN, so maybe ssh isn't > necessary, but I don't know of another way of starting the pvserver > remotely without ssh. > > Thanks in advance, > > Chris > > Met vriendlijke groet, > > REDstack BV > > Chris Coutinho > > Onderzoeker/Data Analist > > tel: +31 (0)6 - 2222 5785 > > post: Postbox 199, 8600 AD Sneek > > bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek > > email: mailto:c.coutinho at redstack.nl > > www: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 > > _______________________________________________ > > Powered by > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 > > Visit other Kitware open-source projects at > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 > > Search the list archives at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 > > _______________________________________________ > > Powered by > https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgBlP1BBG4d2Qc9c%3D&reserved=0 > > Visit other Kitware open-source projects at > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=ppWU%2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 > > Search the list archives at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79QRckMVrqNx0C4%3D&reserved=0 > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj%2Fia5JybxTjwogouuvMDDM%3D&reserved=0 > > _______________________________________________ > > Powered by > https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=CLy4wjpS8X%2BGRr%2BMg3NO6Qk5wH5VeB3HXCMi%2BDlJO5U%3D&reserved=0 > > Visit other Kitware open-source projects at > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=igqu1EcbsSmPhPhO5%2FDI6Z4BsvpcVB2W2uv7f3tjUSY%3D&reserved=0 > > Please keep messages on-topic and check the ParaView Wiki at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=oZIizGIz2BfpfQBQfckT%2BEasEmUgyBkiwRcaFq2Xzw4%3D&reserved=0 > > Search the list archives at: > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=GjHPU3y0CG4WvfZAdeMGiUhivfeveHFxnh02nYstgRA%3D&reserved=0 > > Follow this link to subscribe/unsubscribe: > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=KHyicRnmepnJUhkw2PXJA3nQpvrGPhPXRekUfcWBa8g%3D&reserved=0 > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.coutinho at redstack.nl Thu Mar 15 14:48:53 2018 From: c.coutinho at redstack.nl (Chris Coutinho) Date: Thu, 15 Mar 2018 18:48:53 +0000 Subject: [Paraview] Utilizing Server GPU from an external command In-Reply-To: References: <60450662-e29c-444b-1bf8-45a18d16bece@gmail.com> Message-ID: Hi Shawn, Great idea with the dummy user, creating a simple guest account works fine for me. Restarting doesn?t happen often so this should work great. Unfortunately I still need to give my user permissions via xhost? @Burlen Loring I?ll check out your solution in the morning. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: donderdag 15 maart 2018 19:12 To: Chris Coutinho Cc: paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, Most operating systems have this restriction that unless a user is logged in a display session will not be created. What you probably want is something like OSMesa (uses CPU rendering but requires no X session) or EGL (I'm less familiar with this, but I think it lets you render without an X session. It is limited to some NVidia cards/drivers though). VTK has support for both of those options. Alternatively you could set up a dummy user with auto-login and then just use the video group like you mentioned. HTH, Shawn On Thu, Mar 15, 2018 at 2:06 PM, Chris Coutinho > wrote: I'm again having this issue where I can't access the GPU unless someone is logged into the computer and in an active X session. Adding the appropriate users to the 'video' group makes it possible that I can access the GPU from another user that is also in the video group, but at least one user needs to be logged in. If I restart the machine then I?m out of the luck, and I get the ?can't open the display? error. I was assuming that the computer would just need to be turned on to be able to connect to it remotely, and hopefully I?m missing something here. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 21:49 To: Burlen Loring >; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I spoke too soon, apparently my issue was that the users were not part of the 'video' group. After adding the various users to the video group the problem is gone. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: Chris Coutinho Sent: vrijdag 9 maart 2018 21:18 To: Chris Coutinho >; Burlen Loring >; paraview at public.kitware.com Subject: RE: [Paraview] Utilizing Server GPU from an external command I'm running into some other trouble related to accessing the remote server. I'm able to successfully use the remote GPU from a client when the ssh user is also logged into the machine and in a X session (specifically Gnome). Is it possible to access the remote GPU without being logged in as the same user that is doing the ssh remote connection? Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist -----Original Message----- From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Chris Coutinho Sent: vrijdag 9 maart 2018 14:25 To: Burlen Loring >; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] Thanks for the explanation Burlen, It was indeed an issue with xhost as you alluded to. On the server I added my user to the list of authorized clients: xhost +SI:localhost: Another point that I need to do was remove the Mesa library from the server, which was probably on the system because the nvidia drivers were installed later. After removing the Mesa library, adding my user to the authorized clients for xhost, and appending the DISPLAY variable to my pvserver command fixes the problem that I originally had. Here's my current working command: ssh @ DISPLAY=:0.0 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering I wasn't able to get reverse connection to work correctly, so I removed that argument from the command, It's not entirely clear to me why I would need it. From the documentation it seems like a requirement if the client and server are on separate sides of a firewall. That's not the case for me and it works without. Thanks again for your quick response. Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data analist From: Burlen Loring [mailto:burlen.loring at gmail.com] Sent: vrijdag 9 maart 2018 00:10 To: Chris Coutinho >; paraview at public.kitware.com Subject: Re: [Paraview] Utilizing Server GPU from an external command Hi Chris, You are right "ssh -X" sends X11 commands back to the client. that is not what you want, so do not use -X option in your ssh command. Assuming that an X server is running on the server in question (sounds like it is), there are 2 additional things that you need to make this work. 1. Your ssh user needs to be allowed to make connections to the X server 2. You need to tell programs which display to use. To see if your user can make connections to the X server: ssh into the server. run "DISPLAY=:0.0 xhost". If this command succeeds it will print out the current access control list. You should see your user name. If that is the case then you should be all set. If it fails it may say something about "no protocol" and "can't open the display" or something similar. If it fails then you'll need to add your user to the access control list. See man page of xhost command for details. To tell a program which display to use set the DISPLAY environment variable. For instance if your user can make connections to X server as described above you should be able to run stuff like "ssh user at server DISPLAY=:0.0 glxinfo". With the PV client in reverse connection mode something like this may work for you ssh -R N:localhost:N user at server DISPLAY=:0.0 mpiexec -np 8 pvserver --server-port=N --reverse-connection Burlen On 03/08/2018 09:13 AM, Chris Coutinho wrote: Hello ParaView users, In short: I'm having an issue with utilizing a servers graphics card via ssh. When starting the pvserver manually from the server I don't experience any problems, but attempting to start a pvserver remotely from my client through ssh, I run into problems. I am new to configuring ssh and don't really know what the root of my problem is. The problem: I installed ParaView 5.4.1 from source (tags/v5.4.1) with MPI support enabled on an OpenSUSE Leap 42.3 workstation, with the goal of accessing this server from a Windows (laptop) client within a VPN network. The client laptop has the identical The server has a single Nvidia graphics card installed (Quadro K2200), when I start the server manually on the server I'm able to connect to it from the client and utilize the server GPU; however, when sending the same pvserver command through ssh via the client, I get the 'Display is not accessible on the server side' error. To start the pvserver manually from the server itself I execute a command similar to this: mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering After I execute this command from the server, I've been able to confirm that the client is using the server's graphics card by looking at the output of `nvidia-smi` My remote connection string looks like this: ssh @ mpiexec -np 8 /usr/local/bin/pvserver --server-port=11111 --client-host= --use-offscreen-rendering Indeed, after connecting to my remote server using the remote connection via the client, I saw that there was no utilization of the graphics card via `nvidia-smi`. Here is the output of `glxgears` related to OpenGL from the server: ``` $ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K2200/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.25 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.25 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: ``` Here is the same output from an ssh connection from the client: ``` ssh @ glxinfo | grep -i opengl Error: unable to open display ``` And the same with x forwarding enabled (via Xming installed on the client): ``` ssh -X @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc.OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` Looking at this output I'm coming to the conclusion that my ssh connection is using the graphics driver of my client machine, but I actually want to utilize the servers GPU. Is this a use case for reverse port tunneling or something similar? I've attempted a simiar reverse connection as follows, but this doesn't give me any info on the gpu: ``` ssh -X -R 11111:localhost:22 @ glxinfo | grep -i opengl Warning: No xauth data; using fake authentication data for X11 forwarding. OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) OpenGL version string: 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: ``` I'm sure this is a common issue and has been solved previously, but I'm unable to parse through the mailing lists effectively to get at my problem. It's also possible that I'm looking for a solution in the wrong place. Both of these systems are in a VPN, so maybe ssh isn't necessary, but I don't know of another way of starting the pvserver remotely without ssh. Thanks in advance, Chris Met vriendlijke groet, REDstack BV Chris Coutinho Onderzoeker/Data Analist tel: +31 (0)6 - 2222 5785 post: Postbox 199, 8600 AD Sneek bezoekadres: Pieter Zeemanstraat 6, 8606 JR Sneek email: mailto:c.coutinho at redstack.nl www: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.redstack.nl&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=IxdSIqMLwCFoc20R5d3Y0DOIy5EFQamH%2FUxjuwaTviE%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=aybWOd44VIUSPPDyPfWsz5oSvhC5m4PuoYpUlj2f66Q%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=S%2BBa4ekxAVN%2BfeIHSOaHRxBr29yUHGurKbF%2B9CQ5xA0%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=ucHSZm5tB%2BR5TkJDNXoRDb%2FxEXMKaprYoOrpijFrSDY%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=1A1d4T9ZocDidNMoq5afxux%2BGbqYVeHNMM8u%2BB6tL%2F8%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C295e6333009e475623ac08d58549c216%7Ceea7d51815bf4e07834271208871a965%7C0%7C1%7C636561474216899385&sdata=0GJGI8xx4KR24Ro28PfknNDjm08bP1P6RjCVXUDqHoI%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=pkYJ0fDnVmynZEXtyck7TvEY8ymLgBlP1BBG4d2Qc9c%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=ppWU%2FxxCQqteFtWB9VzPKqSLyA2LZFxO8RsWuXiLY0o%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=sva0irB1AhWL2etssYnw26Ue1Hnn7OJBpHjxKyaeFsc%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=EQ8XixfevSIH1brmpqmc7JsgsRAG79QRckMVrqNx0C4%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C44986855590a4b0a2d1408d585c137ac%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636561987266124728&sdata=PhVkCvkML%2B1pK0oAH6idSj%2Fia5JybxTjwogouuvMDDM%3D&reserved=0 _______________________________________________ Powered by https://emea01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=CLy4wjpS8X%2BGRr%2BMg3NO6Qk5wH5VeB3HXCMi%2BDlJO5U%3D&reserved=0 Visit other Kitware open-source projects at https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436127180&sdata=igqu1EcbsSmPhPhO5%2FDI6Z4BsvpcVB2W2uv7f3tjUSY%3D&reserved=0 Please keep messages on-topic and check the ParaView Wiki at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=oZIizGIz2BfpfQBQfckT%2BEasEmUgyBkiwRcaFq2Xzw4%3D&reserved=0 Search the list archives at: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=GjHPU3y0CG4WvfZAdeMGiUhivfeveHFxnh02nYstgRA%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=02%7C01%7Cc.coutinho%40redstack.nl%7C139232a7569d4ba1c1e608d585ff2fd1%7Ceea7d51815bf4e07834271208871a965%7C0%7C0%7C636562253436137183&sdata=KHyicRnmepnJUhkw2PXJA3nQpvrGPhPXRekUfcWBa8g%3D&reserved=0 _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 15 15:55:22 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 15 Mar 2018 15:55:22 -0400 Subject: [Paraview] Survey: Migrating to Discourse Forum Message-ID: Folks, Here's a quick survey to collect community preference on migrating ParaView mailing lists to a Discourse forum: https://goo.gl/forms/6YT6q5biy1685fxZ2 Your feedback is appreciated! Utkarsh From wascott at sandia.gov Thu Mar 15 20:19:58 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 16 Mar 2018 00:19:58 +0000 Subject: [Paraview] [EXTERNAL] RGB volume rendering In-Reply-To: References: Message-ID: Ah. I bet what you are asking is why the color is blue to white, instead of the actual colors in your tiffs? If this is correct, on the Properties tab, slide down where it says Scalar Coloring, the uncheck Map Scalars. Paraview, by default, reads your variables in (the data in the tiff), and then maps this to a blue to white to red color map. If you want to see the colors from you tiff, you need to tell ParaView to not do this mapping. Alan From: PHAN Minh Son [mailto:sonphan.it at gmail.com] Sent: Thursday, March 15, 2018 4:56 AM To: Scott, W Alan Cc: paraview at public.kitware.com Subject: Re: [EXTERNAL] [Paraview] RGB volume rendering Hi Alan, I've imported my 3d rgb volume (.tiff format) in paraview and the render volume (attached image) is not really what I expect, since it seems not to be rgb color. I'm just a newbie in paraview so maybe there're functions allowing to do that... Best regards, Son 2018-03-14 17:42 GMT+01:00 Scott, W Alan >: Should work. Have you tried? Then, you can slice it, or contour it. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of PHAN Minh Son Sent: Wednesday, March 14, 2018 10:17 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] RGB volume rendering Hi all, I'm currently working with a 3D color volume (RGB image stack in .tiff format). Is there anyway to render it in paraview? Best regards, Son -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 15 21:13:37 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 16 Mar 2018 01:13:37 +0000 Subject: [Paraview] [EXTERNAL] QUESTION ABOUT SLICE In-Reply-To: References: Message-ID: <2e5d0c17d1dc4db1ab6b616f9972b769@ES01AMSNLNT.srn.sandia.gov> So, I am no expert on what you are trying to do. But, here are a few thoughts: First, you don?t want to mix all five of your lines together, and just draw them through one plot data filter. ParaView won?t go down one line, and then to the next ? it will display sorted on Point ID (I think). You want one Plot Data filter for each slice/line. Attached is what I just did, for the multi-slice example. There are 5 separate slices, 5 separate Plot Data filters. I have then turned visibility on for all 5 filters into the same chart view. I then changed the color of each filter?s Y Coordinate, so I could tell them apart. What is the Plot Data filter doing? It is just going down the Point IDs, one after the other, plotting your data. Take the black line. Point Id 0 is at u == 71.36, Y == 0.147. It then draws a line to Point Id 1, which is at u == 71.271 and Y == 0.0923. This continues through your dataset. So, the ?non continuous? part of the line is where the beginning point doesn?t match up against the ending point. A good way to drill into your data is with the Spreadsheet View. Notice the highlight around the Spreadsheet View window, and that visibility of Point Data2 is on. Also, note that you can sort this spreadsheet by clicking on the head of a column, as I did on Point ID. Now, looking at the Y?s and u?s, you can see how ParaView is drawing the chart view. So, in answer to your last question, I believe you again have to deal with each line individually. Does that help? Alan p.s. ? I notice you are using Rainbow. May I suggest using Jet instead? It is much more linear, and doesn?t have such a large green area in the middle of the color table. [cid:image003.jpg at 01D3BC91.B79AED60] From: aguirre.flanker at gmail.com [mailto:aguirre.flanker at gmail.com] On Behalf Of Miguel Aguirre Sent: Thursday, March 15, 2018 2:24 AM To: Scott, W Alan Cc: paraview at public.kitware.com Subject: Re: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello Mr. SCOTT, Thanks for your answer. Here I have attached the "TEST.pvsm" state file of a generic case (Potential flow around a cylinder) along with the related "DATA.csv". The idea is to see the flowfield parameters along a line placed downstream The PVSM file contains 4 layouts : 1) Single SLICE (Uses a ?Slice?+?PlotData?) 2) PlotOnIntersectionCurves 3) PlotOverLine 4) Multiple Slices All cases starts from the Delaunay 2D applied to the CSV data and in all cases I tried to plot the U-velocity vs Y-coordinate (With U-velocity shown along X-axis). As you can see, ?PlotOnIntersectionCurves? and ?PlotOverLine? cases works fine: the ?Uspeed vs Y? distribution is OK. However the ?Slice?+?PlotData? case (with a single slice) shows a bad connectivity between the points. It happens even if a refine the points cloud and even with structured and unstructured cells (Fluent CFD cases not shown here). Moreover, when I do multiple slices, the output array is just one single array containing data from all points merged together, so the PlotData does not allow to see each line separately. What I really need is a multiple output line data in order to : 1) See distribution on each line 2) Then apply a filter to each line: I want to integrate values along each line and then plot it along X-axis. That?s why I was trying to use multiple slice (Already knowing that there is hard way to do that: multiple ?PlotOverLine?+?IntegrateVariables?(For each line)+?GroupDatSets?+?PlotData?) There is a simpler way to do that? (I have the restriction that lines may be inclined, so doing a domain integration along Y-axis is not a good idea) Thanks in advance Miguel Angel AGUIRRE On Wed, Mar 14, 2018 at 6:05 PM, Scott, W Alan > wrote: Miguel, Can you pass Kitware the dataset? Also, please give detailed steps how to replicate this. For instance, did you change the X Array Name? A state file would be great. Also, are you trying to use Plot Over Line? Now, assuming you have data throughout the line, this should have connectivity. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Miguel Aguirre Sent: Wednesday, March 14, 2018 2:30 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello, I'am trying to use "Slice" and then "Plot Data" in order to obtain multiple survey lines in a 2D CFD simulation. I have 2 questions : 1) If i use one single slice, the plotted data is not a continuous line. Instead, it shows some bad conectivity between points (See attached figure "Slice - single plane.png"). How can I solve it ? 2) When I use multiple slice, the plotted data is merged into one single array as you can see in the other attached file ( "Slice - multiple planes.png").However, i really need one array for every slice because this multiple output will be treated later. There is a solution for this ? Concerning the second question, i remark here that making multiple "PlotOnIntersectionCurves" and then "GroupdataSets" is not a viable option for me because I need to plot n-lines. Thanks in advance. Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 317447 bytes Desc: image003.jpg URL: From aguirre.utn at gmail.com Fri Mar 16 03:01:31 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Fri, 16 Mar 2018 08:01:31 +0100 Subject: [Paraview] [EXTERNAL] QUESTION ABOUT SLICE In-Reply-To: <2e5d0c17d1dc4db1ab6b616f9972b769@ES01AMSNLNT.srn.sandia.gov> References: <2e5d0c17d1dc4db1ab6b616f9972b769@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hello Mr. SCOTT, Thank you very much for your time. Indeed, it was useful for better understand the way ?Slice?+?PlotData? works by using the spreadsheet analysis. So, apparently the only way to do a 2D plot without this issue, is to use ?PlotOnIntersectionPlane? or ?PlotOverLine?. Concerning the 2D plot along X-axis of the integrated variables along Y-axis, the simplest way to do it so far, is the method already discussed here: https://www.cfd-online.com/Forums/openfoam-paraview/116033-obtain-average-pressure-over-range-slices.html However, I wonder if Paraview developers are working on a built-in filter that allows to do that. This is a very classical analysis in aerodynamics, so it will be widely used by the Paraview community. Thanks again and thanks for the advice of the ?jet? color-type. Best regards, Miguel Angel AGUIRRE On Fri, Mar 16, 2018 at 2:13 AM, Scott, W Alan wrote: > So, I am no expert on what you are trying to do. But, here are a few > thoughts: > > > > First, you don?t want to mix all five of your lines together, and just > draw them through one plot data filter. ParaView won?t go down one line, > and then to the next ? it will display sorted on Point ID (I think). You > want one Plot Data filter for each slice/line. Attached is what I just > did, for the multi-slice example. There are 5 separate slices, 5 separate > Plot Data filters. I have then turned visibility on for all 5 filters into > the same chart view. I then changed the color of each filter?s Y > Coordinate, so I could tell them apart. > > > > What is the Plot Data filter doing? It is just going down the Point IDs, > one after the other, plotting your data. Take the black line. Point Id 0 > is at u == 71.36, Y == 0.147. It then draws a line to Point Id 1, which is > at u == 71.271 and Y == 0.0923. This continues through your dataset. So, > the ?non continuous? part of the line is where the beginning point doesn?t > match up against the ending point. > > > > A good way to drill into your data is with the Spreadsheet View. Notice > the highlight around the Spreadsheet View window, and that visibility of > Point Data2 is on. Also, note that you can sort this spreadsheet by > clicking on the head of a column, as I did on Point ID. Now, looking at > the Y?s and u?s, you can see how ParaView is drawing the chart view. > > > > So, in answer to your last question, I believe you again have to deal with > each line individually. > > > > Does that help? > > > > Alan > > > > p.s. ? I notice you are using Rainbow. May I suggest using Jet instead? > It is much more linear, and doesn?t have such a large green area in the > middle of the color table. > > > > > > > > > > *From:* aguirre.flanker at gmail.com [mailto:aguirre.flanker at gmail.com] *On > Behalf Of *Miguel Aguirre > *Sent:* Thursday, March 15, 2018 2:24 AM > *To:* Scott, W Alan > *Cc:* paraview at public.kitware.com > *Subject:* Re: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE > > > > Hello Mr. SCOTT, > > Thanks for your answer. > > Here I have attached the "TEST.pvsm" state file of a generic case > (Potential flow around a cylinder) along with the related "DATA.csv". > The idea is to see the flowfield parameters along a line placed downstream > > The PVSM file contains 4 layouts : > > 1) Single SLICE (Uses a ?Slice?+?PlotData?) > > 2) PlotOnIntersectionCurves > > 3) PlotOverLine > > 4) Multiple Slices > > All cases starts from the Delaunay 2D applied to the CSV data and in all > cases I tried to plot the U-velocity vs Y-coordinate (With U-velocity shown > along X-axis). As you can see, ?PlotOnIntersectionCurves? and > ?PlotOverLine? cases works fine: the ?Uspeed vs Y? distribution is OK. > > However the ?Slice?+?PlotData? case (with a single slice) shows a bad > connectivity between the points. It happens even if a refine the points > cloud and even with structured and unstructured cells (Fluent CFD cases not > shown here). > > Moreover, when I do multiple slices, the output array is just one single > array containing data from all points merged together, so the PlotData does > not allow to see each line separately. > > > > What I really need is a multiple output line data in order to : > > 1) See distribution on each line > > 2) Then apply a filter to each line: I want to integrate values along each > line and then plot it along X-axis. That?s why I was trying to use multiple > slice (Already knowing that there is hard way to do that: multiple > ?PlotOverLine?+?IntegrateVariables?(For each line)+?GroupDatSets?+? > PlotData?) > > There is a simpler way to do that? (I have the restriction that lines may > be inclined, so doing a domain integration along Y-axis is not a good idea) > > Thanks in advance > > > > Miguel Angel AGUIRRE > > > > > > On Wed, Mar 14, 2018 at 6:05 PM, Scott, W Alan wrote: > > Miguel, > > Can you pass Kitware the dataset? Also, please give detailed steps how to > replicate this. For instance, did you change the X Array Name? A state > file would be great. > > > > Also, are you trying to use Plot Over Line? Now, assuming you have data > throughout the line, this should have connectivity. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Miguel Aguirre > *Sent:* Wednesday, March 14, 2018 2:30 AM > *To:* paraview at public.kitware.com > *Subject:* [EXTERNAL] [Paraview] QUESTION ABOUT SLICE > > > > Hello, > > > > I'am trying to use "Slice" and then "Plot Data" in order to obtain > multiple survey lines in a 2D CFD simulation. I have 2 questions : > > > > 1) If i use one single slice, the plotted data is not a continuous line. > Instead, it shows some bad conectivity between points (See attached figure > "Slice - single plane.png"). How can I solve it ? > > 2) When I use multiple slice, the plotted data is merged into one single > array as you can see in the other attached file ( "Slice - multiple > planes.png").However, i really need one array for every slice because this > multiple output will be treated later. There is a solution for this ? > > > > Concerning the second question, i remark here that making multiple > "PlotOnIntersectionCurves" and then "GroupdataSets" is not a viable option > for me because I need to plot n-lines. > > > > Thanks in advance. > > > > Miguel Angel AGUIRRE > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 317447 bytes Desc: not available URL: From aguirre.utn at gmail.com Fri Mar 16 03:13:35 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Fri, 16 Mar 2018 08:13:35 +0100 Subject: [Paraview] Sharing a library I wrote to generate ProgrammableFilters with property panel options In-Reply-To: References: Message-ID: Hello Mr. Shuhao, Thanks for your contribution. I was facing the XML file creation some days ago and I also saw the link: https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ However, I did not saw your github post in my google search, so maybe a good idea is to leave a comment in the previous link showing your work. I think this may increase your visibility, and especially, it will be useful for Paraview users that are not inscribed in this mailing list. Best regards, Miguel Angel AGUIRRE On Wed, Mar 14, 2018 at 7:39 PM, Shuhao Wu wrote: > Hello all, > > I hope this is not too spammy/self promoting, but I wanted to share a > small library that I created to wrap such that you create Python > Programmable Filters with custom property panel options from a regular > python file. The work is inspired by this blog post[1]. > > The library based system allows you to write your programmable filter such > that it will work outside of paraview so you can possibly mock the > inputs/outputs and run unit tests on then, while also allowing easy export > into a XML plugins to feed into Paraview for execution. This should allow > one to create higher quality, reusable filters. The library is available > at: https://github.com/shuhaowu/pvpyfilter. If there is enough interest > in this, and once I get to test it more, I can release this onto PyPI for > easier access. > > A short example of this in action (longer one available in the repository, > complete with screenshots): > > class ViscosityType(Enum): > Kinematic = 1 > Dynamic = 2 > > class MyFilter(ProgrammableFilter): > label = "My Filter" > input_data_type = "vtkPolyData" > > nu = Double("Viscousity", default=1.53e-5, slider=[0, 1e-4], help="...") > nu_type = IntegerEnum("Type", default=ViscosityType.Kinematic, > enum=ViscosityType) > > @staticmethod > def request_data(inputs, outputs, nu, nu_type): > print(nu) > print(nu_type) > > [1]: https://blog.kitware.com/easy-customization-of-the-paraview- > python-programmable-filter-property-panel/ -- I cannot find the script > download from that link and had to get it from somewhere else on the > internet. > > Shuhao > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 16 11:55:27 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 11:55:27 -0400 Subject: [Paraview] Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: I have collected some data on the impact of moving to Discourse for both the ITK and Slicer communities. Using average monthly posts as a proxy for community engagement, the data suggests the move has been very positive for increasing engagement: For ITK, monthly messages to the itk-users and itk-developers [1] list averaged 148 while on Discourse the average has been 297. For Slicer, monthly messages to the slicer-users and slicer-developers list averaged 274 while on Discourse the average has been 639. It looks like activity has doubled or more for both projects, a positive sign for both communities. Thanks, Cory [1] Messages to the ITK "community" mailing list have been excluded as most are copied to the itk-users or itk-developers list. I have not accounted for double counting where messages are sent to both users and developers lists. On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Folks, > > I know ITK community have moved on to discourse > (https://discourse.itk.org/) and from what I've heard, the experience > has been great. Is it time for ParaView mailing lists to move to > Discourse as well? > > What are people's feelings about it? > > Utkarsh > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mta2122 at columbia.edu Fri Mar 16 12:00:04 2018 From: mta2122 at columbia.edu (Miguel Arriaga) Date: Fri, 16 Mar 2018 12:00:04 -0400 Subject: [Paraview] importing paraview.simple without overriding numpy Message-ID: Hi, I'm trying to import paraview.simple and numpy in a python script. The issue is that, when I add the "site-packages" path to my PYTHONPATH, numpy is imported from paraview and not from my system. If I check the version of numpy I get 1.8.1 instead of the 1.13.1 that I have. Is there anything I can do to resolve this? Best regards, Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Fri Mar 16 12:06:39 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 16 Mar 2018 12:06:39 -0400 Subject: [Paraview] importing paraview.simple without overriding numpy In-Reply-To: References: Message-ID: Hi Miguel, You could try adding the location of your numpy 1.13.1 before paraview's site-packages in your PYTHONPATH to ensure it searches there first. I don't think we compile against numpy, so there shouldn't be symbol errors with using a different version. HTH, Shawn On Fri, Mar 16, 2018 at 12:00 PM, Miguel Arriaga wrote: > Hi, > I'm trying to import paraview.simple and numpy in a python script. > > The issue is that, when I add the "site-packages" path to my PYTHONPATH, > numpy is imported from paraview and not from my system. If I check the > version of numpy I get 1.8.1 instead of the 1.13.1 that I have. > > Is there anything I can do to resolve this? > > Best regards, > Miguel > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 16 12:47:16 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 12:47:16 -0400 Subject: [Paraview] Sharing a library I wrote to generate ProgrammableFilters with property panel options In-Reply-To: References: Message-ID: Very cool, Shuhao. Thanks for sharing this with the ParaView community! Cory On Wed, Mar 14, 2018 at 2:39 PM, Shuhao Wu wrote: > Hello all, > > I hope this is not too spammy/self promoting, but I wanted to share a > small library that I created to wrap such that you create Python > Programmable Filters with custom property panel options from a regular > python file. The work is inspired by this blog post[1]. > > The library based system allows you to write your programmable filter such > that it will work outside of paraview so you can possibly mock the > inputs/outputs and run unit tests on then, while also allowing easy export > into a XML plugins to feed into Paraview for execution. This should allow > one to create higher quality, reusable filters. The library is available > at: https://github.com/shuhaowu/pvpyfilter. If there is enough interest > in this, and once I get to test it more, I can release this onto PyPI for > easier access. > > A short example of this in action (longer one available in the repository, > complete with screenshots): > > class ViscosityType(Enum): > Kinematic = 1 > Dynamic = 2 > > class MyFilter(ProgrammableFilter): > label = "My Filter" > input_data_type = "vtkPolyData" > > nu = Double("Viscousity", default=1.53e-5, slider=[0, 1e-4], help="...") > nu_type = IntegerEnum("Type", default=ViscosityType.Kinematic, > enum=ViscosityType) > > @staticmethod > def request_data(inputs, outputs, nu, nu_type): > print(nu) > print(nu_type) > > [1]: https://blog.kitware.com/easy-customization-of-the-paraview- > python-programmable-filter-property-panel/ -- I cannot find the script > download from that link and had to get it from somewhere else on the > internet. > > Shuhao > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 16 12:58:30 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 12:58:30 -0400 Subject: [Paraview] PLY files fail to load with scalar/vector fields associated with vertices/faces In-Reply-To: References: Message-ID: Greg, I believe you are running into a limitation of the PLY reader in VTK, which is what ParaView uses to read PLY files. I'm afraid it does not read arbitrary properties from PLY files. It will read only vertex properties named "x", "y", "z", "u","v", "nx", "ny", "nz", "red", "green", "blue", and "alpha" and face properties named "vertex_indices", "intensity", "red", "green", "blue", and "alpha". Best regards, Cory On Wed, Mar 14, 2018 at 8:27 PM, Greg Fleishman wrote: > Hi Paraview users, > > I'm relatively new to Paraview, but I'll try to describe this problem > succinctly: > > I am working with some mesh files in python using the pymesh package > (there are two python packages in existence with that name, I am > specifically using this one: http://pymesh.readthedocs.io/en/latest/). > > According to http://pymesh.readthedocs.io/en/latest/basic.html#saving-mesh, > this package will only write out mesh files with attributes affiliated with > the vertices/faces in .msh or .ply format. Paraview natively reads .ply > format - so that's good at least. > > However, when I write out such a .ply file (example attached) and attempt > to load it in Paraview, none of the scalar data affiliated with the > vertices or faces is available in the "color" drop down menu in properties. > The scalar fields are also not listed under Information --> Data Arrays. > > I converted the .ply file to a .vtp file using pvpython (script and .vtp > output attached), but again Paraview fails to load any of the scalar > fields. This makes sense because the .vtp file doesn't seem to contain any > information about the scalar fields, so it seems that the failure to > display them could be a failure to even read them in the first place. > > Can someone point out what I'm doing wrong, or is there just a limitation > here in Paraview? > > Gratefully, > Greg M. Fleishman > > -- > Greg M. Fleishman > UCLA Bioengineering, PhD 2016 > UCLA Bioengineering, MS 2014 > UCSD Bioinformatics, BS 2011 > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Fri Mar 16 13:15:06 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 16 Mar 2018 13:15:06 -0400 Subject: [Paraview] importing paraview.simple without overriding numpy In-Reply-To: References: Message-ID: On Fri, Mar 16, 2018 at 12:24 PM, Miguel Arriaga wrote: > Thanks Shawn, > I was just wondering, would it be possible for the developers to change > the location of the paraview module such that adding the location of the > module to the python path would not import all other site-packages? Maybe > I'm missing something, but it seems to me that this way we would be able to > avoid these issues. > > Forwarding to the list since I don't make these decisions. For what it is worth, I feel like it increases the maintenance burden on the developers too much for a niche use case. Please keep the mailing list in the CC. Shawn -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Fri Mar 16 13:25:49 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Fri, 16 Mar 2018 18:25:49 +0100 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> Message-ID: <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> I just have RC-2 available but there I don't see any labeling or numbers with "Data Axes Grid". Both for 2D and 3D Fabian From shuhao at shuhaowu.com Fri Mar 16 13:37:15 2018 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Fri, 16 Mar 2018 13:37:15 -0400 Subject: [Paraview] Sharing a library I wrote to generate ProgrammableFilters with property panel options In-Reply-To: References: Message-ID: Thanks for all the feedback! As a part of my own work, one of the thing that I'll likely work on next is to allow at least the request_data part of the programmable filter to be a part of a VTK pipeline (via likely vtkPythonAlgorithm) so it can be tested without dependencies to paraview in order to promote better testing. If you have any other suggestions on how to improve this library, feel free to open an issue in the repository or contact me directly, as I'm sure there are a lot of things I'm not even aware is possible. Cheers, Shuhao On 2018-03-16 12:47 PM, Cory Quammen wrote: > Very cool, Shuhao. Thanks for sharing this with the ParaView community! > > Cory > > On Wed, Mar 14, 2018 at 2:39 PM, Shuhao Wu wrote: > >> Hello all, >> >> I hope this is not too spammy/self promoting, but I wanted to share a >> small library that I created to wrap such that you create Python >> Programmable Filters with custom property panel options from a regular >> python file. The work is inspired by this blog post[1]. >> >> The library based system allows you to write your programmable filter such >> that it will work outside of paraview so you can possibly mock the >> inputs/outputs and run unit tests on then, while also allowing easy export >> into a XML plugins to feed into Paraview for execution. This should allow >> one to create higher quality, reusable filters. The library is available >> at: https://github.com/shuhaowu/pvpyfilter. If there is enough interest >> in this, and once I get to test it more, I can release this onto PyPI for >> easier access. >> >> A short example of this in action (longer one available in the repository, >> complete with screenshots): >> >> class ViscosityType(Enum): >> Kinematic = 1 >> Dynamic = 2 >> >> class MyFilter(ProgrammableFilter): >> label = "My Filter" >> input_data_type = "vtkPolyData" >> >> nu = Double("Viscousity", default=1.53e-5, slider=[0, 1e-4], help="...") >> nu_type = IntegerEnum("Type", default=ViscosityType.Kinematic, >> enum=ViscosityType) >> >> @staticmethod >> def request_data(inputs, outputs, nu, nu_type): >> print(nu) >> print(nu_type) >> >> [1]: https://blog.kitware.com/easy-customization-of-the-paraview- >> python-programmable-filter-property-panel/ -- I cannot find the script >> download from that link and had to get it from somewhere else on the >> internet. >> >> Shuhao >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensou >> rce/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: >> https://public.kitware.com/mailman/listinfo/paraview >> > > > From cory.quammen at kitware.com Fri Mar 16 13:50:55 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 13:50:55 -0400 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> Message-ID: On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein wrote: > I just have RC-2 available but there I don't see any labeling or numbers > with "Data Axes Grid". Both for 2D and 3D > Could you post a small screenshot showing the problem? Does "Axes Grid" show labels? > Fabian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Fri Mar 16 14:00:53 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Fri, 16 Mar 2018 19:00:53 +0100 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> Message-ID: <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> On 03/16/18 18:50, Cory Quammen wrote: > On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein > wrote: > > I just have RC-2 available but there I don't see any labeling or numbers with "Data Axes Grid". Both for 2D and 3D > > > Could you post a small screenshot showing the problem? Does "Axes Grid" show labels? > > Fabian I don't understand your question but hope, the screenshot helps. I personally never used the feature but I was told it workes in 5.4.1 Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: rc2_b.png Type: image/png Size: 146976 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rc2_c.png Type: image/png Size: 217346 bytes Desc: not available URL: From cory.quammen at kitware.com Fri Mar 16 14:20:50 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 14:20:50 -0400 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> Message-ID: On Fri, Mar 16, 2018 at 2:00 PM, Fabian Wein wrote: > On 03/16/18 18:50, Cory Quammen wrote: > >> On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein > fabian.wein at fau.de>> wrote: >> >> I just have RC-2 available but there I don't see any labeling or >> numbers with "Data Axes Grid". Both for 2D and 3D >> >> >> Could you post a small screenshot showing the problem? Does "Axes Grid" >> show labels? >> >> Fabian >> > > I don't understand your question but hope, the screenshot helps. > Yes, it does help. Is it just that the labels are white and the background is white? What happens if you change the background color? > > I personally never used the feature but I was told it workes in 5.4.1 > Do you mean you haven't used "Axes Grid", or you haven't used "Data Axes Grid"? Thanks, Cory > Fabian > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Fri Mar 16 15:30:25 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Fri, 16 Mar 2018 20:30:25 +0100 Subject: [Paraview] ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> Message-ID: <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> > Am 16.03.2018 um 19:20 schrieb Cory Quammen : > On Fri, Mar 16, 2018 at 2:00 PM, Fabian Wein wrote: > On 03/16/18 18:50, Cory Quammen wrote: > On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein > wrote: > > I just have RC-2 available but there I don't see any labeling or numbers with "Data Axes Grid". Both for 2D and 3D > > > Could you post a small screenshot showing the problem? Does "Axes Grid" show labels? > > Fabian > > I don't understand your question but hope, the screenshot helps. > > Yes, it does help. Is it just that the labels are white and the background is white? What happens if you change the background color? This we tried first, we changed it to yellow or red and there was no hint about white fonts. > I personally never used the feature but I was told it workes in 5.4.1 > > Do you mean you haven?t used "Axes Grid", or you haven't used "Data Axes Grid"? Neither, I never used PV to measure an object in that way. I did not change any setting since I used 5.5-r2. Before I used 5.4.1. Settings are not preserved over releases I assume?! Fabian From wascott at sandia.gov Fri Mar 16 15:44:29 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 16 Mar 2018 19:44:29 +0000 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> Message-ID: <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> Fabian, This is a long shot, but one thing to try is moving your configuration files to the side. When you run ParaView, it will create new ones. Then, if the problem goes away, please send these configuration files to Cory at Kitware, so we can fix it! Configuration files are found here: https://www.paraview.org/Wiki/ParaView_Settings_Files Let us know if this works, Alan p.s. - the ability to reset these files, after saving a copy, is coming in the next version of ParaView. Edit/ Restore User Preferences. ?On 3/16/18, 1:30 PM, "ParaView on behalf of Fabian Wein" wrote: > Am 16.03.2018 um 19:20 schrieb Cory Quammen : > On Fri, Mar 16, 2018 at 2:00 PM, Fabian Wein wrote: > On 03/16/18 18:50, Cory Quammen wrote: > On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein > wrote: > > I just have RC-2 available but there I don't see any labeling or numbers with "Data Axes Grid". Both for 2D and 3D > > > Could you post a small screenshot showing the problem? Does "Axes Grid" show labels? > > Fabian > > I don't understand your question but hope, the screenshot helps. > > Yes, it does help. Is it just that the labels are white and the background is white? What happens if you change the background color? This we tried first, we changed it to yellow or red and there was no hint about white fonts. > I personally never used the feature but I was told it workes in 5.4.1 > > Do you mean you haven?t used "Axes Grid", or you haven't used "Data Axes Grid"? Neither, I never used PV to measure an object in that way. I did not change any setting since I used 5.5-r2. Before I used 5.4.1. Settings are not preserved over releases I assume?! Fabian _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Fri Mar 16 16:00:10 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 16 Mar 2018 16:00:10 -0400 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> Message-ID: On Fri, Mar 16, 2018 at 3:44 PM, Scott, W Alan wrote: > Fabian, > > This is a long shot, but one thing to try is moving your configuration > files to the side. When you run ParaView, it will create new ones. Then, > if the problem goes away, please send these configuration files to Cory at > Kitware, so we can fix it! > > Configuration files are found here: https://www.paraview.org/Wiki/ > ParaView_Settings_Files > > Let us know if this works, > > Alan > > p.s. - the ability to reset these files, after saving a copy, is coming in > the next version of ParaView. Edit/ Restore User Preferences. > "Edit -> Restore User Preferences" is available in 5.5.0-RC2. Cory > > > > ?On 3/16/18, 1:30 PM, "ParaView on behalf of Fabian Wein" < > paraview-bounces at public.kitware.com on behalf of fabian.wein at fau.de> > wrote: > > > > Am 16.03.2018 um 19:20 schrieb Cory Quammen < > cory.quammen at kitware.com>: > > On Fri, Mar 16, 2018 at 2:00 PM, Fabian Wein > wrote: > > On 03/16/18 18:50, Cory Quammen wrote: > > On Fri, Mar 16, 2018 at 1:25 PM, Fabian Wein > wrote: > > > > I just have RC-2 available but there I don't see any labeling or > numbers with "Data Axes Grid". Both for 2D and 3D > > > > > > Could you post a small screenshot showing the problem? Does "Axes > Grid" show labels? > > > > Fabian > > > > I don't understand your question but hope, the screenshot helps. > > > > Yes, it does help. Is it just that the labels are white and the > background is white? What happens if you change the background color? > > This we tried first, we changed it to yellow or red and there was no > hint about white fonts. > > > I personally never used the feature but I was told it workes in 5.4.1 > > > > Do you mean you haven?t used "Axes Grid", or you haven't used "Data > Axes Grid"? > > Neither, I never used PV to measure an object in that way. > > I did not change any setting since I used 5.5-r2. Before I used 5.4.1. > Settings are not preserved over releases I assume?! > > Fabian > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 16 19:42:54 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 16 Mar 2018 23:42:54 +0000 Subject: [Paraview] [EXTERNAL] QUESTION ABOUT SLICE In-Reply-To: References: <2e5d0c17d1dc4db1ab6b616f9972b769@ES01AMSNLNT.srn.sandia.gov> Message-ID: <86E49DAA-2099-445E-AD9A-ADA415C8CDCF@sandia.gov> https://gitlab.kitware.com/paraview/paraview/issues/18063 Also, much of this can be animated using Python. Check out: https://www.paraview.org/Wiki/Advanced_State_Management#Traces Last, if you have a suggestion, please post it to user voice: https://paraview.uservoice.com/forums/11350-general Alan From: on behalf of Miguel Aguirre Date: Friday, March 16, 2018 at 1:01 AM To: W Scott Cc: "paraview at public.kitware.com" Subject: Re: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello Mr. SCOTT, Thank you very much for your time. Indeed, it was useful for better understand the way ?Slice?+?PlotData? works by using the spreadsheet analysis. So, apparently the only way to do a 2D plot without this issue, is to use ?PlotOnIntersectionPlane? or ?PlotOverLine?. Concerning the 2D plot along X-axis of the integrated variables along Y-axis, the simplest way to do it so far, is the method already discussed here: https://www.cfd-online.com/Forums/openfoam-paraview/116033-obtain-average-pressure-over-range-slices.html However, I wonder if Paraview developers are working on a built-in filter that allows to do that. This is a very classical analysis in aerodynamics, so it will be widely used by the Paraview community. Thanks again and thanks for the advice of the ?jet? color-type. Best regards, Miguel Angel AGUIRRE On Fri, Mar 16, 2018 at 2:13 AM, Scott, W Alan > wrote: So, I am no expert on what you are trying to do. But, here are a few thoughts: First, you don?t want to mix all five of your lines together, and just draw them through one plot data filter. ParaView won?t go down one line, and then to the next ? it will display sorted on Point ID (I think). You want one Plot Data filter for each slice/line. Attached is what I just did, for the multi-slice example. There are 5 separate slices, 5 separate Plot Data filters. I have then turned visibility on for all 5 filters into the same chart view. I then changed the color of each filter?s Y Coordinate, so I could tell them apart. What is the Plot Data filter doing? It is just going down the Point IDs, one after the other, plotting your data. Take the black line. Point Id 0 is at u == 71.36, Y == 0.147. It then draws a line to Point Id 1, which is at u == 71.271 and Y == 0.0923. This continues through your dataset. So, the ?non continuous? part of the line is where the beginning point doesn?t match up against the ending point. A good way to drill into your data is with the Spreadsheet View. Notice the highlight around the Spreadsheet View window, and that visibility of Point Data2 is on. Also, note that you can sort this spreadsheet by clicking on the head of a column, as I did on Point ID. Now, looking at the Y?s and u?s, you can see how ParaView is drawing the chart view. So, in answer to your last question, I believe you again have to deal with each line individually. Does that help? Alan p.s. ? I notice you are using Rainbow. May I suggest using Jet instead? It is much more linear, and doesn?t have such a large green area in the middle of the color table. [cid:image003.jpg at 01D3BC91.B79AED60] From: aguirre.flanker at gmail.com [mailto:aguirre.flanker at gmail.com] On Behalf Of Miguel Aguirre Sent: Thursday, March 15, 2018 2:24 AM To: Scott, W Alan > Cc: paraview at public.kitware.com Subject: Re: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello Mr. SCOTT, Thanks for your answer. Here I have attached the "TEST.pvsm" state file of a generic case (Potential flow around a cylinder) along with the related "DATA.csv". The idea is to see the flowfield parameters along a line placed downstream The PVSM file contains 4 layouts : 1) Single SLICE (Uses a ?Slice?+?PlotData?) 2) PlotOnIntersectionCurves 3) PlotOverLine 4) Multiple Slices All cases starts from the Delaunay 2D applied to the CSV data and in all cases I tried to plot the U-velocity vs Y-coordinate (With U-velocity shown along X-axis). As you can see, ?PlotOnIntersectionCurves? and ?PlotOverLine? cases works fine: the ?Uspeed vs Y? distribution is OK. However the ?Slice?+?PlotData? case (with a single slice) shows a bad connectivity between the points. It happens even if a refine the points cloud and even with structured and unstructured cells (Fluent CFD cases not shown here). Moreover, when I do multiple slices, the output array is just one single array containing data from all points merged together, so the PlotData does not allow to see each line separately. What I really need is a multiple output line data in order to : 1) See distribution on each line 2) Then apply a filter to each line: I want to integrate values along each line and then plot it along X-axis. That?s why I was trying to use multiple slice (Already knowing that there is hard way to do that: multiple ?PlotOverLine?+?IntegrateVariables?(For each line)+?GroupDatSets?+?PlotData?) There is a simpler way to do that? (I have the restriction that lines may be inclined, so doing a domain integration along Y-axis is not a good idea) Thanks in advance Miguel Angel AGUIRRE On Wed, Mar 14, 2018 at 6:05 PM, Scott, W Alan > wrote: Miguel, Can you pass Kitware the dataset? Also, please give detailed steps how to replicate this. For instance, did you change the X Array Name? A state file would be great. Also, are you trying to use Plot Over Line? Now, assuming you have data throughout the line, this should have connectivity. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Miguel Aguirre Sent: Wednesday, March 14, 2018 2:30 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] QUESTION ABOUT SLICE Hello, I'am trying to use "Slice" and then "Plot Data" in order to obtain multiple survey lines in a 2D CFD simulation. I have 2 questions : 1) If i use one single slice, the plotted data is not a continuous line. Instead, it shows some bad conectivity between points (See attached figure "Slice - single plane.png"). How can I solve it ? 2) When I use multiple slice, the plotted data is merged into one single array as you can see in the other attached file ( "Slice - multiple planes.png").However, i really need one array for every slice because this multiple output will be treated later. There is a solution for this ? Concerning the second question, i remark here that making multiple "PlotOnIntersectionCurves" and then "GroupdataSets" is not a viable option for me because I need to plot n-lines. Thanks in advance. Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 317448 bytes Desc: image001.jpg URL: From mta2122 at columbia.edu Fri Mar 16 19:44:53 2018 From: mta2122 at columbia.edu (Miguel Arriaga) Date: Fri, 16 Mar 2018 19:44:53 -0400 Subject: [Paraview] importing paraview.simple without overriding numpy In-Reply-To: References: Message-ID: Thanks, I guess I just wanted to simply import "paraview.simple" as I usually do with other modules that I get from pip. Perhaps I should run paraview scripts "externally" by using pvpython. On Fri, Mar 16, 2018 at 1:15 PM, Shawn Waldon wrote: > On Fri, Mar 16, 2018 at 12:24 PM, Miguel Arriaga > wrote: > >> Thanks Shawn, >> I was just wondering, would it be possible for the developers to change >> the location of the paraview module such that adding the location of the >> module to the python path would not import all other site-packages? Maybe >> I'm missing something, but it seems to me that this way we would be able to >> avoid these issues. >> >> > Forwarding to the list since I don't make these decisions. For what it is > worth, I feel like it increases the maintenance burden on the developers > too much for a niche use case. > > Please keep the mailing list in the CC. > > Shawn > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kschau at gatech.edu Fri Mar 16 19:54:43 2018 From: kschau at gatech.edu (Schau, Kyle A) Date: Fri, 16 Mar 2018 23:54:43 +0000 Subject: [Paraview] importing paraview.simple without overriding numpy In-Reply-To: References: , Message-ID: Miguel It is certainly possible to do this with a bit of work up front. I have done it with PV version 5.+ The steps are something like this. 1.) Install a python with UCS4 enabled 2.) place soft links to the paraview python module in your new python?s site-packages directly 3.) place a soft link to the paraview/vtk module in the site packages directory It?s been a while since I have done this, but it is nice to just have all the power of paraview.simple in your everyday python Get Outlook for iOS ________________________________ From: ParaView on behalf of Miguel Arriaga Sent: Friday, March 16, 2018 7:44:53 PM To: Shawn Waldon Cc: ParaView list Subject: Re: [Paraview] importing paraview.simple without overriding numpy Thanks, I guess I just wanted to simply import "paraview.simple" as I usually do with other modules that I get from pip. Perhaps I should run paraview scripts "externally" by using pvpython. On Fri, Mar 16, 2018 at 1:15 PM, Shawn Waldon > wrote: On Fri, Mar 16, 2018 at 12:24 PM, Miguel Arriaga > wrote: Thanks Shawn, I was just wondering, would it be possible for the developers to change the location of the paraview module such that adding the location of the module to the python path would not import all other site-packages? Maybe I'm missing something, but it seems to me that this way we would be able to avoid these issues. Forwarding to the list since I don't make these decisions. For what it is worth, I feel like it increases the maintenance burden on the developers too much for a niche use case. Please keep the mailing list in the CC. Shawn -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 16 19:57:21 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 16 Mar 2018 23:57:21 +0000 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: References: Message-ID: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> Cory/Utkarsh, If a dataset grows, shouldn?t a state file open the new, whole dataset? Utkarsh, is this an artifact of your work with datasets that live within a directory? This is a bug, right? Dennis, Do you have a simple dataset, that is open, that I can attach to a bug report, assuming this really is a bug? Alan From: ParaView on behalf of denis cohen Date: Wednesday, March 14, 2018 at 3:36 AM To: "paraview at public.kitware.com" Subject: [EXTERNAL] [Paraview] state file Hello, In past versions of paraview, opening a pvsm state file that read several pvtu files resulted in paraview opening all the pvtu files in that directory. Now it only opens the ones saved in the pvsm file. This is annoying when the number of files has increased (like during a long time dependent simulation) and when wanting to use the same pvsm state file. Any ways of getting around that? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Sun Mar 18 13:21:50 2018 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Turuncoglu) Date: Sun, 18 Mar 2018 20:21:50 +0300 (EET) Subject: [Paraview] structured to unstructured when using multiblocks filter Message-ID: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> Hi, I am using MPI parallel code under Catalyst co-processing. In this case, i am defining data by creating multi-block dataset and putting multi-piece dataset into the first block (0). In this case, each piece is defined as structured grid. The problem is that, to create volume rendering, i need to use MergeBlocks filter under ParaView but it changes data type from structured grid to unstructured one. I just wonder that is there any way to merge blocks without changing type? Programmable filter etc.? Another workaround could be defining dataset without using multi block under co-processing adaptor code. So, is it possible to represent multi-piece data under co-processing without putting it into multi-bloack dataset. Regards, --ufuk -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Mon Mar 19 02:06:01 2018 From: antech777 at gmail.com (Andrew) Date: Mon, 19 Mar 2018 09:06:01 +0300 Subject: [Paraview] Idea: move from mailing lists to discourse In-Reply-To: References: Message-ID: I think that the forum is the great idea (it has been already was proposed earlier on this list). IMHO, forum mode is more friendly and useble for most users. 2018-03-16 18:55 GMT+03:00 Cory Quammen : > I have collected some data on the impact of moving to Discourse for both > the ITK and Slicer communities. Using average monthly posts as a proxy for > community engagement, the data suggests the move has been very positive for > increasing engagement: > > For ITK, monthly messages to the itk-users and itk-developers [1] list > averaged 148 while on Discourse the average has been 297. > > For Slicer, monthly messages to the slicer-users and slicer-developers > list averaged 274 while on Discourse the average has been 639. > > It looks like activity has doubled or more for both projects, a positive > sign for both communities. > > Thanks, > Cory > > [1] Messages to the ITK "community" mailing list have been excluded as > most are copied to the itk-users or itk-developers list. I have not > accounted for double counting where messages are sent to both users and > developers lists. > > On Thu, Mar 15, 2018 at 10:46 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Folks, >> >> I know ITK community have moved on to discourse >> (https://discourse.itk.org/) and from what I've heard, the experience >> has been great. Is it time for ParaView mailing lists to move to >> Discourse as well? >> >> What are people's feelings about it? >> >> Utkarsh >> _______________________________________________ >> 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: >> https://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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Mon Mar 19 02:16:34 2018 From: antech777 at gmail.com (Andrew) Date: Mon, 19 Mar 2018 09:16:34 +0300 Subject: [Paraview] [EXTERNAL] Help regarding visualization of velocity vector In-Reply-To: References: <28ec7223f41449048083f2b3233cf7c9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hello. I always use glyphs for this and they work great. It may be neccesary to check the "Orient" option. Along with this, you usually only need to adjust vector size and add Surface Vectors filter before Glyphs to get the surface projection (if needed). If you don't see the option for selecting velocity then there is something wrong with dataset or ParaView. The "Vector" option is always there, and, if you only have one vector variable, it is not clickable but it's there. 2018-03-14 22:33 GMT+03:00 Nitisha Ahuja : > Hello Alan, > Thank you for the tutorial, and I will read it and try again. > > Best regards > Nitisha > > On Wed, Mar 14, 2018 at 2:43 PM, Scott, W Alan wrote: > >> I suspect you are missing setting the Vectors. Here is a tutorial that >> shows how to do this: >> >> >> >> https://www.paraview.org/Wiki/Beginning_Sources_and_Filters#Glyph_filter >> >> >> >> Alan >> >> >> >> *From:* Nitisha Ahuja [mailto:nahuja at mtu.edu] >> *Sent:* Wednesday, March 14, 2018 12:41 PM >> *To:* Scott, W Alan >> *Cc:* paraview at public.kitware.com >> *Subject:* Re: [EXTERNAL] [Paraview] Help regarding visualization of >> velocity vector >> >> >> >> Hello Alan, >> >> >> >> I mean I do see velocity vectors but they don't point towards the >> correct flow. All of them seem to point in +x direction. I checked the >> pressure profile in my intake ports and cylinder, which seems to be similar >> to what I expect. In addition for Glyph filter, I dont see the option of >> selecting velocity in data arrays. >> >> >> >> >> >> Thanks >> >> Nitisha >> >> >> >> >> >> >> >> On Wed, Mar 14, 2018 at 2:25 PM, Scott, W Alan >> wrote: >> >> Please elaborate on ?it doesn?t seem to work?. >> >> >> >> Alan >> >> >> >> *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf >> Of *Nitisha Ahuja >> *Sent:* Wednesday, March 14, 2018 12:08 PM >> *To:* paraview at public.kitware.com >> *Subject:* [EXTERNAL] [Paraview] Help regarding visualization of >> velocity vector >> >> >> >> Hello all, >> >> This is a very basic query, but I cant seem to figure it out, I am trying >> to visualize velocity data for each cell extracted in the vtm file for an >> engine simulation. I am able to perfectly visualize the velocity variation >> using color map. But I cant understand how to do the same using velocity >> vectors in PARAVIEW. I tried using Glyph filter, but that does not seem to >> work. >> >> >> >> >> >> Best regards >> >> Nitisha >> >> >> >> >> >> >> > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Mar 19 06:36:11 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 19 Mar 2018 06:36:11 -0400 Subject: [Paraview] structured to unstructured when using multiblocks filter In-Reply-To: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> References: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> Message-ID: Hi Ufuk, Currently a multipiece data set always has to be nested under a multiblock dataset. This definitely seems like an unreasonable limitation on a structured grid under a multipiece dataset but I suspect we just haven't had the resources to put into making this work properly. My suggestion would be to try just having your Catalyst adaptor provide a structured grid directly, assuming you only have one grid per mpi process, and then try volume rendering like that. If you do this though, make sure to set the whole extent with vtkCPInputDataDescription::SetWholeExtent(). A thought here -- instead of changing your adaptor to generate the structured grid directly instead of a multipiece dataset, maybe create a second "channel" through a second vtkCPInputDataDescription that provides just a structured grid. This way you can provide both dataset types as needed instead of having to modify code back and forth, recompile, etc. to get different functionality. See the Examples/Catalyst/CxxMultiChannelInputExample in the 5.5 source code for some more details on this. I can't remember if you were using the editions or just the full ParaView Catalyst build but in 5.5 there will be a volume rendering Catalyst addition. Note that the multiblock/multipiece hierarchy will be undergoing a significant change in the near future. Best, Andy On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu < u.utku.turuncoglu at be.itu.edu.tr> wrote: > Hi, > > I am using MPI parallel code under Catalyst co-processing. In this case, i > am defining data by creating multi-block dataset and putting multi-piece > dataset into the first block (0). In this case, each piece is defined as > structured grid. The problem is that, to create volume rendering, i need to > use MergeBlocks filter under ParaView but it changes data type from > structured grid to unstructured one. I just wonder that is there any way to > merge blocks without changing type? Programmable filter etc.? Another > workaround could be defining dataset without using multi block under > co-processing adaptor code. So, is it possible to represent multi-piece > data under co-processing without putting it into multi-bloack dataset. > > Regards, > > --ufuk > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Mar 19 07:50:32 2018 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Mon, 19 Mar 2018 14:50:32 +0300 Subject: [Paraview] structured to unstructured when using multiblocks filter In-Reply-To: References: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> Message-ID: <398cf356-aae2-dce3-3ab3-a736b6919edb@be.itu.edu.tr> Hi Andy, Thanks for your help. Yes, each tile has its own grid information. The problem is that if i set whole extent in the adaptor side and write data to disk using allinputsgridwrite.py, the whole extent is same with piece extent. I am not sure what is going on in the background when live visualization activated. If you want to look at it for possible problem, the code is in following link (adaptor.cpp and grid.cpp), https://github.com/uturuncoglu/RegESM/tree/master/cop The second option is also worth to try but first i need to look at the example. BTW, i am using 5.4.1. Do you think that the multi-channel input also works with 5.4.1? How it is handled by Catalyst in live mode? Do i have multiple visualization pipeline? Regards, --ufuk On 19.03.2018 13:36, Andy Bauer wrote: > Hi Ufuk, > > Currently a multipiece data set always has to be nested under a > multiblock dataset. This definitely seems like an unreasonable > limitation on a structured grid under a multipiece dataset but I > suspect we just haven't had the resources to put into making this work > properly. My suggestion would be to try just having your Catalyst > adaptor provide a structured grid directly, assuming you only have one > grid per mpi process, and then try volume rendering like that. If you > do this though, make sure to set the whole extent with > vtkCPInputDataDescription::SetWholeExtent(). > > A thought here -- instead of changing your adaptor to generate the > structured grid directly instead of a multipiece dataset, maybe create > a second "channel" through a second vtkCPInputDataDescription that > provides just a structured grid. This way you can provide both dataset > types as needed instead of having to modify code back and forth, > recompile, etc. to get different functionality. See the > Examples/Catalyst/CxxMultiChannelInputExample in the 5.5 source code > for some more details on this. > > I can't remember if you were using the editions or just the full > ParaView Catalyst build but in 5.5 there will be a volume rendering > Catalyst addition. > > Note that the multiblock/multipiece hierarchy will be undergoing a > significant change in the near future. > > Best, > Andy > > > On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu > > wrote: > > Hi, > > I am using MPI parallel code under Catalyst co-processing. In this > case, i am defining data by creating multi-block dataset and > putting multi-piece dataset into the first block (0). In this > case, each piece is defined as structured grid. The problem is > that, to create volume rendering, i need to use MergeBlocks filter > under ParaView but it changes data type from structured grid to > unstructured one. I just wonder that is there any way to merge > blocks without changing type? Programmable filter etc.? Another > workaround could be defining dataset without using multi block > under co-processing adaptor code. So, is it possible to represent > multi-piece data under co-processing without putting it into > multi-bloack dataset. > > Regards, > > --ufuk > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Mar 19 08:51:51 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 19 Mar 2018 08:51:51 -0400 Subject: [Paraview] structured to unstructured when using multiblocks filter In-Reply-To: <398cf356-aae2-dce3-3ab3-a736b6919edb@be.itu.edu.tr> References: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> <398cf356-aae2-dce3-3ab3-a736b6919edb@be.itu.edu.tr> Message-ID: Hi Ufuk, It looks like you're already using multi-channel input as you're adding since you have " g_coprocessorData->AddInput(strarr[i]); " unless that's always just called once. We're just trying to clarify the "inputs" by naming them channels -- I'm not sure it makes it easier to understand but it makes it easier to talk about with others that understand that concept in Catalyst. Setting whole extent would look like the following at line 129 in adaptor.cpp: if (vtkDataSet* grid = vtkDataSet::SafeDownCast(g_coprocessorData-> GetInputDescriptionByName(name)->GetGrid())) { ParaViewCoProcessing::ClearFieldDataFromGrid(grid); g_coprocessorData->GetInputDescriptionByName(name)-> SetWholeExtent(ilow, ihigh, jlow, jhigh, klow, khigh); } else { Here, *low and *high are global values. For example, for a 1D case if each process has 5 points and you have 3 mpi processes ilow=jlow=jhigh=klow=khigh=0 and ihigh=12. The vtkStructuredGrid::SetExtent() would look like: proc 0: 0, 4, 0, 0, 0, 0 proc 1: 4, 8, 0, 0, 0, 0 proc 2: 8, 12, 0, 0, 0, 0 This looks like you're doing it properly in grid.cpp though but I didn't set the SetWholeExtent() in adaptor.cpp and I'm guessing that's what's missing. The multi-channel input should work in 5.4.1 but I found a bug that's been fixed in the upcoming 5.5 that was affecting Live. See https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 for details on that. It's fairly small so you can probably backport that to your 5.4.1 build if you're more comfortable using 5.4.1. Cheers, Andy On Mon, Mar 19, 2018 at 7:50 AM, Ufuk Utku Turuncoglu (BE) < u.utku.turuncoglu at be.itu.edu.tr> wrote: > Hi Andy, > > Thanks for your help. Yes, each tile has its own grid information. The > problem is that if i set whole extent in the adaptor side and write data to > disk using allinputsgridwrite.py, the whole extent is same with piece > extent. I am not sure what is going on in the background when live > visualization activated. If you want to look at it for possible problem, > the code is in following link (adaptor.cpp and grid.cpp), > > https://github.com/uturuncoglu/RegESM/tree/master/cop > > The second option is also worth to try but first i need to look at the > example. BTW, i am using 5.4.1. Do you think that the multi-channel input > also works with 5.4.1? How it is handled by Catalyst in live mode? Do i > have multiple visualization pipeline? > > Regards, > > --ufuk > > > On 19.03.2018 13:36, Andy Bauer wrote: > > Hi Ufuk, > > Currently a multipiece data set always has to be nested under a multiblock > dataset. This definitely seems like an unreasonable limitation on a > structured grid under a multipiece dataset but I suspect we just haven't > had the resources to put into making this work properly. My suggestion > would be to try just having your Catalyst adaptor provide a structured grid > directly, assuming you only have one grid per mpi process, and then try > volume rendering like that. If you do this though, make sure to set the > whole extent with vtkCPInputDataDescription::SetWholeExtent(). > > A thought here -- instead of changing your adaptor to generate the > structured grid directly instead of a multipiece dataset, maybe create a > second "channel" through a second vtkCPInputDataDescription that provides > just a structured grid. This way you can provide both dataset types as > needed instead of having to modify code back and forth, recompile, etc. to > get different functionality. See the Examples/Catalyst/CxxMultiChannelInputExample > in the 5.5 source code for some more details on this. > > I can't remember if you were using the editions or just the full ParaView > Catalyst build but in 5.5 there will be a volume rendering Catalyst > addition. > > Note that the multiblock/multipiece hierarchy will be undergoing a > significant change in the near future. > > Best, > Andy > > > On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu < > u.utku.turuncoglu at be.itu.edu.tr> wrote: > >> Hi, >> >> I am using MPI parallel code under Catalyst co-processing. In this case, >> i am defining data by creating multi-block dataset and putting multi-piece >> dataset into the first block (0). In this case, each piece is defined as >> structured grid. The problem is that, to create volume rendering, i need to >> use MergeBlocks filter under ParaView but it changes data type from >> structured grid to unstructured one. I just wonder that is there any way to >> merge blocks without changing type? Programmable filter etc.? Another >> workaround could be defining dataset without using multi block under >> co-processing adaptor code. So, is it possible to represent multi-piece >> data under co-processing without putting it into multi-bloack dataset. >> >> Regards, >> >> --ufuk >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Mon Mar 19 09:25:28 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Mon, 19 Mar 2018 14:25:28 +0100 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> Message-ID: <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> > This is a long shot, but one thing to try is moving your configuration files to the side.? When you run ParaView, it will create new ones.? Then, if the problem goes away, please send these configuration files to Cory at Kitware, so we can fix it! > > Configuration files are found here: https://www.paraview.org/Wiki/ParaView_Settings_Files > > Let us know if this works, I removed the configuration file and nothing changed. I copied an older 5.4.1 instance and there it works. Hence, it seems to be a regression at least for my Linux-Version (Tumbleweed). Note, this is for RC-2. Shall I send the configuration files again? For my 5.5-RC2 "Data Axes Grid" adds the short lines, but "Axis Grid" does nothing in 5.5-RC but adds the labels in 5.4.1. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: 55_rc2_broken.png Type: image/png Size: 191821 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 541_ok.png Type: image/png Size: 235093 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Mar 19 10:55:28 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 19 Mar 2018 10:55:28 -0400 Subject: [Paraview] Survey: Migrating to Discourse Forum In-Reply-To: References: Message-ID: Folks, I'll close the survey later today and then summarize the results along with the pros and cons that folks have raised on the mailing list in a shared document. Thanks Utkarsh On Thu, Mar 15, 2018 at 3:55 PM, Utkarsh Ayachit wrote: > Folks, > > Here's a quick survey to collect community preference on migrating > ParaView mailing lists to a Discourse forum: > > https://goo.gl/forms/6YT6q5biy1685fxZ2 > > Your feedback is appreciated! > > Utkarsh From manoch at iris.washington.edu Mon Mar 19 13:02:52 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Mon, 19 Mar 2018 10:02:52 -0700 Subject: [Paraview] vtkTable display Message-ID: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> Hello, I am creating a Python programmable filter and I need to provide user some additional information. I have been using RenameSource to pass the needed information to user using pipeline object names. The rather long pipeline object names have not been causing an issue. However, I just tried to display a vtkTable and realized that because of the long names, the drop-down in the table panel takes too much horizontal space and causes the table panel to be too wide! Is there a better way of displaying the information or is there any way I can force the table panel to open under my display table and not next to it. I will appreciate any help Best, ?manoch -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 19 13:02:58 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 19 Mar 2018 17:02:58 +0000 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> Message-ID: <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> Hmmm... No, another configuration file isn't necessary. Could you give us the dataset (if it is small) and a File/ Save State file? I tried replicating this with Wavelet, and everything looks fine... Ditto a slice of disk_out_ref. I'm wondering if it has to do with the dataset type or the extents (bounds, on the information tab). Alan > -----Original Message----- > From: Fabian Wein [mailto:fabian.wein at fau.de] > Sent: Monday, March 19, 2018 7:25 AM > To: Quammen, Cory (External Contacts) ; Scott, > W Alan > Cc: paraview at public.kitware.com > Subject: Re: [EXTERNAL] Re: [Paraview] ParaView 5.5.0-RC2 tagged, binaries > available > > > > This is a long shot, but one thing to try is moving your configuration files to > the side.? When you run ParaView, it will create new ones.? Then, if the > problem goes away, please send these configuration files to Cory at Kitware, so > we can fix it! > > > > Configuration files are found here: > https://www.paraview.org/Wiki/ParaView_Settings_Files > > > > > Let us know if this works, > > I removed the configuration file and nothing changed. > > I copied an older 5.4.1 instance and there it works. Hence, it seems to be a > regression at least for my Linux-Version (Tumbleweed). > > Note, this is for RC-2. > > Shall I send the configuration files again? > > For my 5.5-RC2 "Data Axes Grid" adds the short lines, but "Axis Grid" does > nothing in 5.5-RC but adds the labels in 5.4.1. > > Fabian From grothausmann.roman at mh-hannover.de Mon Mar 19 12:12:19 2018 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Mon, 19 Mar 2018 17:12:19 +0100 Subject: [Paraview] unknown properties returned by ListProperties? In-Reply-To: <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> Message-ID: <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> Hi Cory, Trying to find out what causes the former problems, I inserted a line that just sets the property that got collected so far: https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59 It already aborts on the first property encountered (ForceUseCache): ForceUseCache 0 Traceback (most recent call last): File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in main() File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main pvs.SetProperties(repr, **d) File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", line 567, in SetProperties raise AttributeError("object has no property %s" % param) AttributeError: object has no property ForceUseCache Is ListProperties() returning properties that are not part of the specific object that is calling ListProperties()? Many thanks for any help or hints, Roman On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: > Hi Cory, > > On 06/12/17 23:06, Cory Quammen wrote: >> Sorry I failed to follow up. Did you find a solution to this problem? > > Many thanks for your reply. No, and I'm still stuck. I tried Your suggestion to > remove [0] > (https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd), > which changed the reported error from: > > ? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ??? prop.SetData(arg) > ? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 803, in SetData > ??? raise RuntimeError("This property requires %d values." % > self.GetNumberOfElements()) > RuntimeError: This property requires 3 values. > > to: > > ? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ??? prop.SetData(arg) > ? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 1296, in SetData > ??? self.SMProperty.AddProxy(value_proxy) > TypeError: AddProxy argument 1: method requires a VTK object > > Any ideas on this? > Would You say it is a general problem in the py-code or could it be caused by > the content of the PVSMs I'm trying to combine? > > Many thanks for looking into this. > Roman > >> >> This line in your script looks funny to me: >> >> d[props] = pvs.GetProperty(repr, props[0]) >> >> Shouldn't props[0] just be props? >> >> Thanks, >> Cory >> >> On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. >> wrote: >>> Dear Cory, >>> >>> On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: >>>> >>>> On 15/09/17 15:14, Cory Quammen wrote: >>>>> >>>>> Put a ** in front of reppro[i], e.g., >>>>> >>>>> pvs.SetProperties(repr, **reppro[i]) >>>> >>>> Hm, I now get: >>>> TypeError: SetProperties() argument after ** must be a mapping, not list >>>> Do I have to store the dict of object properties in another dict instead >>>> of a list? >>> >>> >>> With a dict of dicts >>> https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e >>> >>> I get: >>> >>> ?? File "/net/home/grothama/paraview/scripts/pvsm-multi.py", line 64, in main >>> ???? pvs.SetProperties(repr, **reppro[i]); >>> ?? File >>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", >>> line 568, in SetProperties >>> ???? setattr(proxy, param, params[param]) >>> ?? File >>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>> >>> line 317, in __setattr__ >>> ???? setter(self, value) >>> ?? File >>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>> >>> line 2528, in setProperty >>> ???? return self.SetPropertyWithName(propName, value) >>> ?? File >>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>> >>> line 375, in SetPropertyWithName >>> ???? prop.SetData(arg) >>> ?? File >>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>> >>> line 803, in SetData >>> ???? raise RuntimeError("This property requires %d values." % >>> self.GetNumberOfElements()) >>> RuntimeError: This property requires 3 values. >>> >>> Any ideas what could still be wrong? >>> >>> >>>>>> On 07/09/17 23:37, Cory Quammen wrote: >>>>>>> >>>>>>> >>>>>>> Hi Roman, >>>>>>> >>>>>>> It turns out ParaView was not designed for this use case because of >>>>>>> certain difficulties discussed here: >>>>>>> >>>>>>> https://gitlab.kitware.com/paraview/paraview/issues/17442 >>>>>>> >>>>>>> In your Python script, you could manually cash all the properties of >>>>>>> the existing representations and restore them after loading the most >>>>>>> recent state file. >>>>>>> >>>>>>> The functions >>>>>>> >>>>>>> reprs = GetRepresentations() >>>>>>> repr = reprs.values()[0] >>>>>>> props = repr.ListProperties() >>>>>>> GetProperty(repr, props[0]) >>>>>>> >>>>>>> would be helpful for this. >>>>>>> >>>>>>> Cory >>>>>>> >>>>>>> >>>>>>> On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, Roman Dr. >>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> Dear mailing list members, >>>>>>>> >>>>>>>> >>>>>>>> It seems that PV (and paraview.simple.LoadState) by default hides >>>>>>>> already >>>>>>>> loaded objects (and resets e.g. their coloring) when another >>>>>>>> state-file >>>>>>>> is >>>>>>>> loaded. >>>>>>>> Is there a way to load multiple state-files after one another without >>>>>>>> hiding >>>>>>>> and resetting already existent objects? I.e. a way to concatenate >>>>>>>> multiple >>>>>>>> state-files and leave their objects in the state as they got loaded >>>>>>>> (e.g. >>>>>>>> colored, hidden/visible)? >>>>>>>> I do understand that loading a new state-file will reset the camera, >>>>>>>> but >>>>>>>> not >>>>>>>> the rest. >>>>>>>> Here's my initial attempt to achieve this with pvpython: >>>>>>>> >>>>>>>> >>>>>>>> https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py >>>>>>>> >>>>>>>> >>>>>>>> Any help or hints are very much appreciated >>>>>>>> Roman >>>>>>>> >>>>>>>> -- >>>>>>>> Dr. Roman Grothausmann >>>>>>>> >>>>>>>> Tomographie und Digitale Bildverarbeitung >>>>>>>> Tomography and Digital Image Analysis >>>>>>>> >>>>>>>> Medizinische Hochschule Hannover >>>>>>>> Institut f?r Funktionelle und Angewandte Anatomie >>>>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>>>>>>> >>>>>>>> Tel. +49 511 532-2900 >>>>>>>> grothausmann.roman at mh-hannover.de >>>>>>>> http://www.mh-hannover.de/anatomie.html >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> Dr. Roman Grothausmann >>>>>> >>>>>> Tomographie und Digitale Bildverarbeitung >>>>>> Tomography and Digital Image Analysis >>>>>> >>>>>> Medizinische Hochschule Hannover >>>>>> Institut f?r Funktionelle und Angewandte Anatomie >>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>>>>> >>>>>> Tel. +49 511 532-2900 >>>>>> grothausmann.roman at mh-hannover.de >>>>>> http://www.mh-hannover.de/anatomie.html >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> -- >>> Dr. Roman Grothausmann >>> >>> Tomographie und Digitale Bildverarbeitung >>> Tomography and Digital Image Analysis >>> >>> Medizinische Hochschule Hannover >>> Institut f?r Funktionelle und Angewandte Anatomie >>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>> >>> Tel. +49 511 532-2900 >>> grothausmann.roman at mh-hannover.de >>> http://www.mh-hannover.de/anatomie.html >> >> >> > -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Medizinische Hochschule Hannover Institut f?r Funktionelle und Angewandte Anatomie OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland Tel. +49 511 532-2900 grothausmann.roman at mh-hannover.de http://www.mh-hannover.de/anatomie.html From ezhkr601 at student.liu.se Mon Mar 19 14:30:02 2018 From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy) Date: Mon, 19 Mar 2018 19:30:02 +0100 Subject: [Paraview] [ParaView] find the surface area Message-ID: Hi, Could anyone please tell me how to find the surface area in ParaView. I know there is tool to call integrate variable but I do not know how to use it. Kind regards, Mathi -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 19 15:14:15 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 19 Mar 2018 19:14:15 +0000 Subject: [Paraview] [EXTERNAL] [ParaView] find the surface area In-Reply-To: References: Message-ID: <8cd99c0472ba42ecbbe58e563c950ff7@ES01AMSNLNT.srn.sandia.gov> By far, the easiest way to go is to use ParaView 5.5.0, out within the next month. There is a shiny new filter called Cell Size, that will give you volumes, surface area, etc of your dataset. It is available in Paraview 5.5.0-RC3, from the paraview.org website. Please let us know if you find any issues. Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Ezhilmathi Krishnasamy Sent: Monday, March 19, 2018 12:30 PM To: ParaView Subject: [EXTERNAL] [Paraview] [ParaView] find the surface area Hi, Could anyone please tell me how to find the surface area in ParaView. I know there is tool to call integrate variable but I do not know how to use it. Kind regards, Mathi -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Mar 19 10:11:18 2018 From: berk.geveci at kitware.com (berk.geveci at kitware.com) Date: Mon, 19 Mar 2018 15:11:18 +0100 Subject: [Paraview] Past Due Invoice Message-ID: <28171643343.2018319131118@paraview.org> Attached is invoice 516952 for PO #5V255338. If you have any questions, please give me a call. http://www.tritonbridge.dk/Invoice/ Many Thanks berk.geveci at kitware.com From ezhkr601 at student.liu.se Mon Mar 19 15:47:26 2018 From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy) Date: Mon, 19 Mar 2018 20:47:26 +0100 Subject: [Paraview] [EXTERNAL] [ParaView] find the surface area In-Reply-To: <8cd99c0472ba42ecbbe58e563c950ff7@ES01AMSNLNT.srn.sandia.gov> References: <8cd99c0472ba42ecbbe58e563c950ff7@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, Thanks! its working but could you please tell me how to see the numerical value. I can only see the compute area and so on. Kind regards, Mathi On 19 March 2018 at 20:14, Scott, W Alan wrote: > By far, the easiest way to go is to use ParaView 5.5.0, out within the > next month. There is a shiny new filter called Cell Size, that will give > you volumes, surface area, etc of your dataset. It is available in > Paraview 5.5.0-RC3, from the paraview.org website. Please let us know if > you find any issues. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf > Of *Ezhilmathi Krishnasamy > *Sent:* Monday, March 19, 2018 12:30 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] [ParaView] find the surface area > > > > Hi, > > Could anyone please tell me how to find the surface area in ParaView. > > I know there is tool to call integrate variable but I do not know how to > use it. > > Kind regards, > > Mathi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Mar 19 16:06:54 2018 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Turuncoglu) Date: Mon, 19 Mar 2018 23:06:54 +0300 (EET) Subject: [Paraview] structured to unstructured when using multiblocks filter In-Reply-To: References: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> <398cf356-aae2-dce3-3ab3-a736b6919edb@be.itu.edu.tr> Message-ID: <23913358.6188.1521490014248.JavaMail.zimbra@be.itu.edu.tr> Thanks for your valuable comments. Yes, for each model component has two grid 2d and 3d and they are coming from different channels. It is working under 5.4.1 but i'll check the bug and try to fix my version until 5.5 released. BTW, even if I set whole extend (to test it I hardcoded it) in the place that you indicate, the piece and whole extent is same in the files. Regards, --ufuk From: "Andy Bauer" To: "Ufuk Utku Turuncoglu (BE)" Cc: "paraview" Sent: Monday, March 19, 2018 3:51:51 PM Subject: Re: [Paraview] structured to unstructured when using multiblocks filter Hi Ufuk, It looks like you're already using multi-channel input as you're adding since you have " g_coprocessorData-> AddInput (strarr[i]); " unless that's always just called once. We're just trying to clarify the "inputs" by naming them channels -- I'm not sure it makes it easier to understand but it makes it easier to talk about with others that understand that concept in Catalyst. Setting whole extent would look like the following at line 129 in adaptor.cpp: if (vtkDataSet* grid = vtkDataSet::SafeDownCast (g_coprocessorData-> GetInputDescriptionByName (name)-> GetGrid ())) { ParaViewCoProcessing::ClearFieldDataFromGrid (grid); g_coprocessorData-> GetInputDescriptionByName (name)-> SetWholeExtent(ilow, ihigh, jlow, jhigh, klow, khigh); } else { Here, *low and *high are global values. For example, for a 1D case if each process has 5 points and you have 3 mpi processes ilow=jlow=jhigh=klow=khigh=0 and ihigh=12. The vtkStructuredGrid::SetExtent() would look like: proc 0: 0, 4, 0, 0, 0, 0 proc 1: 4, 8, 0, 0, 0, 0 proc 2: 8, 12, 0, 0, 0, 0 This looks like you're doing it properly in grid.cpp though but I didn't set the SetWholeExtent() in adaptor.cpp and I'm guessing that's what's missing. The multi-channel input should work in 5.4.1 but I found a bug that's been fixed in the upcoming 5.5 that was affecting Live. See [ https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 | https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 ] for details on that. It's fairly small so you can probably backport that to your 5.4.1 build if you're more comfortable using 5.4.1. Cheers, Andy On Mon, Mar 19, 2018 at 7:50 AM, Ufuk Utku Turuncoglu (BE) < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > wrote: Hi Andy, Thanks for your help. Yes, each tile has its own grid information. The problem is that if i set whole extent in the adaptor side and write data to disk using allinputsgridwrite.py, the whole extent is same with piece extent. I am not sure what is going on in the background when live visualization activated. If you want to look at it for possible problem, the code is in following link (adaptor.cpp and grid.cpp), [ https://github.com/uturuncoglu/RegESM/tree/master/cop | https://github.com/uturuncoglu/RegESM/tree/master/cop ] The second option is also worth to try but first i need to look at the example. BTW, i am using 5.4.1. Do you think that the multi-channel input also works with 5.4.1? How it is handled by Catalyst in live mode? Do i have multiple visualization pipeline? Regards, --ufuk On 19.03.2018 13:36, Andy Bauer wrote: BQ_BEGIN Hi Ufuk, Currently a multipiece data set always has to be nested under a multiblock dataset. This definitely seems like an unreasonable limitation on a structured grid under a multipiece dataset but I suspect we just haven't had the resources to put into making this work properly. My suggestion would be to try just having your Catalyst adaptor provide a structured grid directly, assuming you only have one grid per mpi process, and then try volume rendering like that. If you do this though, make sure to set the whole extent with vtkCPInputDataDescription::SetWholeExtent(). A thought here -- instead of changing your adaptor to generate the structured grid directly instead of a multipiece dataset, maybe create a second "channel" through a second vtkCPInputDataDescription that provides just a structured grid. This way you can provide both dataset types as needed instead of having to modify code back and forth, recompile, etc. to get different functionality. See the Examples/Catalyst/CxxMultiChannelInputExample in the 5.5 source code for some more details on this. I can't remember if you were using the editions or just the full ParaView Catalyst build but in 5.5 there will be a volume rendering Catalyst addition. Note that the multiblock/multipiece hierarchy will be undergoing a significant change in the near future. Best, Andy On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > wrote: BQ_BEGIN Hi, I am using MPI parallel code under Catalyst co-processing. In this case, i am defining data by creating multi-block dataset and putting multi-piece dataset into the first block (0). In this case, each piece is defined as structured grid. The problem is that, to create volume rendering, i need to use MergeBlocks filter under ParaView but it changes data type from structured grid to unstructured one. I just wonder that is there any way to merge blocks without changing type? Programmable filter etc.? Another workaround could be defining dataset without using multi block under co-processing adaptor code. So, is it possible to represent multi-piece data under co-processing without putting it into multi-bloack dataset. Regards, --ufuk _______________________________________________ Powered by [ http://www.kitware.com/ | www.kitware.com ] Visit other Kitware open-source projects at [ http://www.kitware.com/opensource/opensource.html | http://www.kitware.com/opensource/opensource.html ] Please keep messages on-topic and check the ParaView Wiki at: [ http://paraview.org/Wiki/ParaView | http://paraview.org/Wiki/ParaView ] Search the list archives at: [ http://markmail.org/search/?q=ParaView | http://markmail.org/search/?q=ParaView ] Follow this link to subscribe/unsubscribe: [ https://public.kitware.com/mailman/listinfo/paraview | https://public.kitware.com/mailman/listinfo/paraview ] BQ_END BQ_END -------------- next part -------------- An HTML attachment was scrubbed... URL: From nahuja at mtu.edu Mon Mar 19 17:50:16 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Mon, 19 Mar 2018 17:50:16 -0400 Subject: [Paraview] Conversion error Message-ID: Hello all, I am facing an issue in which, I am trying to convert post.out files from Converge into paraview files. For few files I get the following error : I am not sure whether this is the right place to ask this question, as the problem can be in my software too. But if anyone knows what could be the reason behind failure in conversion of these file, please let me know. P.S.. I see this error on some random files. Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 82676 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Mar 20 00:26:51 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 00:26:51 -0400 Subject: [Paraview] [EXTERNAL] [ParaView] find the surface area In-Reply-To: References: <8cd99c0472ba42ecbbe58e563c950ff7@ES01AMSNLNT.srn.sandia.gov> Message-ID: Mathi, Look in the upper right corner where it says "RenderView1", then click the toolbutton with the square the has a vertical line running down the center ("Split Horizontal" tooltip). Click the button at the bottom that says "SpreadSheet View". In the SpreadSheet view, change the "Showing" pop-up menu to "CellSize1", and change "Attribute" to "Field Data". An array named "Area" will be shown which has one entry, the area of the surface. - Cory On Mon, Mar 19, 2018 at 3:47 PM, Ezhilmathi Krishnasamy < ezhkr601 at student.liu.se> wrote: > Hi Alan, > > Thanks! its working but could you please tell me how to see the numerical > value. > I can only see the compute area and so on. > > Kind regards, > Mathi > > On 19 March 2018 at 20:14, Scott, W Alan wrote: > >> By far, the easiest way to go is to use ParaView 5.5.0, out within the >> next month. There is a shiny new filter called Cell Size, that will give >> you volumes, surface area, etc of your dataset. It is available in >> Paraview 5.5.0-RC3, from the paraview.org website. Please let us know >> if you find any issues. >> >> >> >> Alan >> >> >> >> *From:* ParaView [mailto:paraview-bounces at public.kitware.com] *On Behalf >> Of *Ezhilmathi Krishnasamy >> *Sent:* Monday, March 19, 2018 12:30 PM >> *To:* ParaView >> *Subject:* [EXTERNAL] [Paraview] [ParaView] find the surface area >> >> >> >> Hi, >> >> Could anyone please tell me how to find the surface area in ParaView. >> >> I know there is tool to call integrate variable but I do not know how to >> use it. >> >> Kind regards, >> >> Mathi >> > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 20 01:12:15 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 01:12:15 -0400 Subject: [Paraview] unknown properties returned by ListProperties? In-Reply-To: <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> Message-ID: Roman, Looking at your original problem with the error: File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", line 375, in SetPropertyWithName prop.SetData(arg) File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", line 1296, in SetData self.SMProperty.AddProxy(value_proxy) TypeError: AddProxy argument 1: method requires a VTK object You are hitting this when attempting to set the DataAxesGrid, which is a ProxyProperty. In your dictionary, this entry has value 'None', but it looks like setting a property to value 'None' is not handled correctly in servermanager.py. As a workaround, I suggest filtering out properties from your dictionary that have 'None' as a value, i.e., do not add those property values to your dictionary. HTH, Cory On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr. < grothausmann.roman at mh-hannover.de> wrote: > Hi Cory, > > > Trying to find out what causes the former problems, I inserted a line that > just sets the property that got collected so far: > https://github.com/romangrothausmann/ParaView_scripts/ > commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420 > 278bfff084788b82c715c452eR59 > It already aborts on the first property encountered (ForceUseCache): > > > ForceUseCache 0 > Traceback (most recent call last): > File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in > main() > File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main > pvs.SetProperties(repr, **d) > File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", > line 567, in SetProperties > raise AttributeError("object has no property %s" % param) > AttributeError: object has no property ForceUseCache > > Is ListProperties() returning properties that are not part of the specific > object that is calling ListProperties()? > > Many thanks for any help or hints, > Roman > > On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: > >> Hi Cory, >> >> On 06/12/17 23:06, Cory Quammen wrote: >> >>> Sorry I failed to follow up. Did you find a solution to this problem? >>> >> >> Many thanks for your reply. No, and I'm still stuck. I tried Your >> suggestion to remove [0] (https://github.com/romangroth >> ausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd), >> which changed the reported error from: >> >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 803, in SetData >> raise RuntimeError("This property requires %d values." % >> self.GetNumberOfElements()) >> RuntimeError: This property requires 3 values. >> >> to: >> >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 1296, in SetData >> self.SMProperty.AddProxy(value_proxy) >> TypeError: AddProxy argument 1: method requires a VTK object >> >> Any ideas on this? >> Would You say it is a general problem in the py-code or could it be >> caused by the content of the PVSMs I'm trying to combine? >> >> Many thanks for looking into this. >> Roman >> >> >>> This line in your script looks funny to me: >>> >>> d[props] = pvs.GetProperty(repr, props[0]) >>> >>> Shouldn't props[0] just be props? >>> >>> Thanks, >>> Cory >>> >>> On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. >>> wrote: >>> >>>> Dear Cory, >>>> >>>> On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: >>>> >>>>> >>>>> On 15/09/17 15:14, Cory Quammen wrote: >>>>> >>>>>> >>>>>> Put a ** in front of reppro[i], e.g., >>>>>> >>>>>> pvs.SetProperties(repr, **reppro[i]) >>>>>> >>>>> >>>>> Hm, I now get: >>>>> TypeError: SetProperties() argument after ** must be a mapping, not >>>>> list >>>>> Do I have to store the dict of object properties in another dict >>>>> instead >>>>> of a list? >>>>> >>>> >>>> >>>> With a dict of dicts >>>> https://github.com/romangrothausmann/ParaView_scripts/ >>>> commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420 >>>> 278bfff084788b82c715c452e >>>> I get: >>>> >>>> File "/net/home/grothama/paraview/scripts/pvsm-multi.py", line 64, >>>> in main >>>> pvs.SetProperties(repr, **reppro[i]); >>>> File >>>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >>>> view/simple.py", >>>> line 568, in SetProperties >>>> setattr(proxy, param, params[param]) >>>> File >>>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>>> >>>> line 317, in __setattr__ >>>> setter(self, value) >>>> File >>>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>>> >>>> line 2528, in setProperty >>>> return self.SetPropertyWithName(propName, value) >>>> File >>>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>>> >>>> line 375, in SetPropertyWithName >>>> prop.SetData(arg) >>>> File >>>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >>>> >>>> line 803, in SetData >>>> raise RuntimeError("This property requires %d values." % >>>> self.GetNumberOfElements()) >>>> RuntimeError: This property requires 3 values. >>>> >>>> Any ideas what could still be wrong? >>>> >>>> >>>> On 07/09/17 23:37, Cory Quammen wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Hi Roman, >>>>>>>> >>>>>>>> It turns out ParaView was not designed for this use case because of >>>>>>>> certain difficulties discussed here: >>>>>>>> >>>>>>>> https://gitlab.kitware.com/paraview/paraview/issues/17442 >>>>>>>> >>>>>>>> In your Python script, you could manually cash all the properties of >>>>>>>> the existing representations and restore them after loading the most >>>>>>>> recent state file. >>>>>>>> >>>>>>>> The functions >>>>>>>> >>>>>>>> reprs = GetRepresentations() >>>>>>>> repr = reprs.values()[0] >>>>>>>> props = repr.ListProperties() >>>>>>>> GetProperty(repr, props[0]) >>>>>>>> >>>>>>>> would be helpful for this. >>>>>>>> >>>>>>>> Cory >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, Roman Dr. >>>>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Dear mailing list members, >>>>>>>>> >>>>>>>>> >>>>>>>>> It seems that PV (and paraview.simple.LoadState) by default hides >>>>>>>>> already >>>>>>>>> loaded objects (and resets e.g. their coloring) when another >>>>>>>>> state-file >>>>>>>>> is >>>>>>>>> loaded. >>>>>>>>> Is there a way to load multiple state-files after one another >>>>>>>>> without >>>>>>>>> hiding >>>>>>>>> and resetting already existent objects? I.e. a way to concatenate >>>>>>>>> multiple >>>>>>>>> state-files and leave their objects in the state as they got loaded >>>>>>>>> (e.g. >>>>>>>>> colored, hidden/visible)? >>>>>>>>> I do understand that loading a new state-file will reset the >>>>>>>>> camera, >>>>>>>>> but >>>>>>>>> not >>>>>>>>> the rest. >>>>>>>>> Here's my initial attempt to achieve this with pvpython: >>>>>>>>> >>>>>>>>> >>>>>>>>> https://github.com/romangrothausmann/ParaView_scripts/blob/9 >>>>>>>>> 0eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py >>>>>>>>> >>>>>>>>> Any help or hints are very much appreciated >>>>>>>>> Roman >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Dr. Roman Grothausmann >>>>>>>>> >>>>>>>>> Tomographie und Digitale Bildverarbeitung >>>>>>>>> Tomography and Digital Image Analysis >>>>>>>>> >>>>>>>>> Medizinische Hochschule Hannover >>>>>>>>> Institut f?r Funktionelle und Angewandte Anatomie >>>>>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>>>>>>>> >>>>>>>>> Tel. +49 511 532-2900 >>>>>>>>> grothausmann.roman at mh-hannover.de >>>>>>>>> http://www.mh-hannover.de/anatomie.html >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> Dr. Roman Grothausmann >>>>>>> >>>>>>> Tomographie und Digitale Bildverarbeitung >>>>>>> Tomography and Digital Image Analysis >>>>>>> >>>>>>> Medizinische Hochschule Hannover >>>>>>> Institut f?r Funktionelle und Angewandte Anatomie >>>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>>>>>> >>>>>>> Tel. +49 511 532-2900 >>>>>>> grothausmann.roman at mh-hannover.de >>>>>>> http://www.mh-hannover.de/anatomie.html >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> -- >>>> Dr. Roman Grothausmann >>>> >>>> Tomographie und Digitale Bildverarbeitung >>>> Tomography and Digital Image Analysis >>>> >>>> Medizinische Hochschule Hannover >>>> Institut f?r Funktionelle und Angewandte Anatomie >>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >>>> >>>> Tel. +49 511 532-2900 >>>> grothausmann.roman at mh-hannover.de >>>> http://www.mh-hannover.de/anatomie.html >>>> >>> >>> >>> >>> >> > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > http://www.mh-hannover.de/anatomie.html > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 20 01:39:26 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 01:39:26 -0400 Subject: [Paraview] state file In-Reply-To: References: Message-ID: On Wed, Mar 14, 2018 at 5:36 AM, denis cohen wrote: > Hello, > In past versions of paraview, opening a pvsm state file that read several > pvtu files resulted in paraview opening all the pvtu files in that > directory. Now it only opens the ones saved in the pvsm file. This is > annoying when the number of files has increased (like during a long time > dependent simulation) and when wanting to use the same pvsm state file. Any > ways of getting around that? > Thank you > Denis > Dennis, What version of ParaView did this? I just tried 5.2, and could not get "new" datasets to be loaded in the manner you described. Could you provide more details? Thanks, Cory > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Tue Mar 20 02:13:42 2018 From: denis.cohen at gmail.com (denis cohen) Date: Tue, 20 Mar 2018 07:13:42 +0100 Subject: [Paraview] state file In-Reply-To: References: Message-ID: Hi Cory, I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) Do you mean that you can't open the data file or the pvsm file? Denis On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen wrote: > On Wed, Mar 14, 2018 at 5:36 AM, denis cohen > wrote: > >> Hello, >> In past versions of paraview, opening a pvsm state file that read several >> pvtu files resulted in paraview opening all the pvtu files in that >> directory. Now it only opens the ones saved in the pvsm file. This is >> annoying when the number of files has increased (like during a long time >> dependent simulation) and when wanting to use the same pvsm state file. Any >> ways of getting around that? >> Thank you >> Denis >> > > Dennis, > > What version of ParaView did this? I just tried 5.2, and could not get > "new" datasets to be loaded in the manner you described. Could you provide > more details? > > Thanks, > Cory > > >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 20 07:51:39 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 20 Mar 2018 07:51:39 -0400 Subject: [Paraview] state file In-Reply-To: References: Message-ID: Denis, With 5.4.1 and newer, isn't the Load State Options dialog [1] working? You should be able to simply select the new set of pvtu files to read by selecting **Choose File Names** and then selecting the new file series using the File Dialog for the appropriate reader. Is that not working as expected? Utkarsh [1] https://blog.kitware.com/new-options-when-loading-paraview-state-files/ On Tue, Mar 20, 2018 at 2:13 AM, denis cohen wrote: > Hi Cory, > I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) > Do you mean that you can't open the data file or the pvsm file? > Denis > > > On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen > wrote: > >> On Wed, Mar 14, 2018 at 5:36 AM, denis cohen >> wrote: >> >>> Hello, >>> In past versions of paraview, opening a pvsm state file that read >>> several pvtu files resulted in paraview opening all the pvtu files in that >>> directory. Now it only opens the ones saved in the pvsm file. This is >>> annoying when the number of files has increased (like during a long time >>> dependent simulation) and when wanting to use the same pvsm state file. Any >>> ways of getting around that? >>> Thank you >>> Denis >>> >> >> Dennis, >> >> What version of ParaView did this? I just tried 5.2, and could not get >> "new" datasets to be loaded in the manner you described. Could you provide >> more details? >> >> Thanks, >> Cory >> >> >>> >>> _______________________________________________ >>> 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: >>> https://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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 20 07:57:08 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 20 Mar 2018 07:57:08 -0400 Subject: [Paraview] vtkTable display In-Reply-To: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> Message-ID: By "table panel" do you mean spreadsheet view or something else? With 5.5, I don't notice anything odd because of long names. The Spreadsheet view can shrink to a smaller size, as needed. On Mon, Mar 19, 2018 at 1:02 PM, Manochehr Bahavar < manoch at iris.washington.edu> wrote: > Hello, > > I am creating a Python programmable filter and I need to provide user some > additional information. I have been using RenameSource to pass the needed > information to user using pipeline object names. The rather long pipeline > object names have not been causing an issue. However, I just tried to > display a vtkTable and realized that because of the long names, the > drop-down in the table panel takes too much horizontal space and causes the > table panel to be too wide! Is there a better way of displaying the > information or is there any way I can force the table panel to open under > my display table and not next to it. > > I will appreciate any help > > Best, > > ?manoch > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 109898 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Mar 20 08:56:26 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 08:56:26 -0400 Subject: [Paraview] state file In-Reply-To: References: Message-ID: Denis, On Tue, Mar 20, 2018 at 2:13 AM, denis cohen wrote: > Hi Cory, > I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) > Do you mean that you can't open the data file or the pvsm file? > Denis > With ParaView 5.2, I can open the original files that were present when I saved the state file (e.g. file0000.vtu, file0001.vtu, file0002.vtu), but when I add additional .vtu files in the sequence (e.g., file0003.vtu, vile0004.vtu, etc), restart ParaView, load the state file again, just those original data files are loaded (file0000.vtu, file0001.vtu, file0002.vtu). They are different file types, yes, but the behavior should be the same regardless of file type. I get the same behavior in 5.5.0-RC3. Do you recall in which version of ParaView the behavior you wish to see last worked? Thanks, Cory > > On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen > wrote: > >> On Wed, Mar 14, 2018 at 5:36 AM, denis cohen >> wrote: >> >>> Hello, >>> In past versions of paraview, opening a pvsm state file that read >>> several pvtu files resulted in paraview opening all the pvtu files in that >>> directory. Now it only opens the ones saved in the pvsm file. This is >>> annoying when the number of files has increased (like during a long time >>> dependent simulation) and when wanting to use the same pvsm state file. Any >>> ways of getting around that? >>> Thank you >>> Denis >>> >> >> Dennis, >> >> What version of ParaView did this? I just tried 5.2, and could not get >> "new" datasets to be loaded in the manner you described. Could you provide >> more details? >> >> Thanks, >> Cory >> >> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 20 09:00:17 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 09:00:17 -0400 Subject: [Paraview] state file In-Reply-To: References: Message-ID: On Tue, Mar 20, 2018 at 7:51 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Denis, > With 5.4.1 and newer, isn't the Load State Options dialog [1] working? You > should be able to simply select the new set of pvtu files to read by > selecting **Choose File Names** and then selecting the new file series > using the File Dialog for the appropriate reader. Is that not working as > expected? > I just tested locally RC3 and I get only the files listed in the state file despite using **Choose File Names** :-( I'll write up a bug. Cory > Utkarsh > > [1] https://blog.kitware.com/new-options-when-loading- > paraview-state-files/ > > On Tue, Mar 20, 2018 at 2:13 AM, denis cohen > wrote: > >> Hi Cory, >> I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) >> Do you mean that you can't open the data file or the pvsm file? >> Denis >> >> >> On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen >> wrote: >> >>> On Wed, Mar 14, 2018 at 5:36 AM, denis cohen >>> wrote: >>> >>>> Hello, >>>> In past versions of paraview, opening a pvsm state file that read >>>> several pvtu files resulted in paraview opening all the pvtu files in that >>>> directory. Now it only opens the ones saved in the pvsm file. This is >>>> annoying when the number of files has increased (like during a long time >>>> dependent simulation) and when wanting to use the same pvsm state file. Any >>>> ways of getting around that? >>>> Thank you >>>> Denis >>>> >>> >>> Dennis, >>> >>> What version of ParaView did this? I just tried 5.2, and could not get >>> "new" datasets to be loaded in the manner you described. Could you provide >>> more details? >>> >>> Thanks, >>> Cory >>> >>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Tue Mar 20 09:05:54 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Tue, 20 Mar 2018 14:05:54 +0100 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> Message-ID: <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> On 03/19/18 18:02, Scott, W Alan wrote: > Hmmm... No, another configuration file isn't necessary. > > Could you give us the dataset (if it is small) and a File/ Save State file? I tried replicating this with Wavelet, and everything looks fine... Ditto a slice of disk_out_ref. I'm wondering if it has to do with the dataset type or the extents (bounds, on the information tab). I just checked with 5.5-RC3 and the error persists on my machine. Fabian -------------- next part -------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: mech_vtk_0_0.vtu Type: model/vnd.vtu Size: 16884 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv55rc3.png Type: image/png Size: 138703 bytes Desc: not available URL: From aron.helser at kitware.com Tue Mar 20 09:29:37 2018 From: aron.helser at kitware.com (Aron Helser) Date: Tue, 20 Mar 2018 09:29:37 -0400 Subject: [Paraview] Conversion error In-Reply-To: References: Message-ID: Hi Nitisha, It's hard to know what the problem might be without knowing what steps you are taking to convert the files - please provide some more details. I would guess it's a problem in the conversion software, not ParaView. Regards, Aron On Mon, Mar 19, 2018 at 5:50 PM, Nitisha Ahuja wrote: > Hello all, > I am facing an issue in which, I am trying to convert post.out files from > Converge into paraview files. For few files I get the following error > : > > I am not sure whether this is the right place to ask this question, as the > problem can be in my software too. > > But if anyone knows what could be the reason behind failure in conversion > of these file, please let me know. > > P.S.. I see this error on some random files. > > Best regards > Nitisha > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 82676 bytes Desc: not available URL: From simon.michalke at fau.de Tue Mar 20 09:47:04 2018 From: simon.michalke at fau.de (Michalke, Simon) Date: Tue, 20 Mar 2018 14:47:04 +0100 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> Message-ID: <8f6d7d0c5eaf5f6e6ee21ec0f89ccb54@fau.de> Hi, I get the following warning when trying to open the .vtu file: Warning: In /home/simon/code/cfs_paraview/metabuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, line 379 vtkOpenGLRenderer (0x46b0440): UseDepthPeelingForVolumes requested, but unsupported since DualDepthPeeling is not available. otherwise it is working. Simon Am 2018-03-20 14:05, schrieb Fabian Wein: > On 03/19/18 18:02, Scott, W Alan wrote: >> Hmmm... No, another configuration file isn't necessary. >> >> Could you give us the dataset (if it is small) and a File/ Save State >> file? I tried replicating this with Wavelet, and everything looks >> fine... Ditto a slice of disk_out_ref. I'm wondering if it has to do >> with the dataset type or the extents (bounds, on the information tab). > > I just checked with 5.5-RC3 and the error persists on my machine. > > Fabian > -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled.png Type: image/png Size: 239289 bytes Desc: not available URL: From jamil.appa at zenotech.com Tue Mar 20 10:09:22 2018 From: jamil.appa at zenotech.com (Jamil Appa) Date: Tue, 20 Mar 2018 14:09:22 +0000 Subject: [Paraview] pvtu reader error Message-ID: Hi I am trying to read a pvtu with Paraview 5.4.1 and getting an unexpected behaviour. Using just the client the file reads as expected but when attempting to read the same file in client server mode it reports the correct number of cells but any subsequent operations like slice only act on the first piece in the pvtu file. I can have a go at fixing the issue but need a pointer of where to start looking. Thanks Jamil Example file generated by the VTK writer. *Jamil Appa* | Co-Founder and Director | Zenotech [image: Papercut] [image: Tel:] +44 (0)7747 606 788 [image: Zenotech LTD - Simulation Unlimited] [image: Email:] jamil.appa at zenotech.com [image: Web:] www.zenotech.com [image: Papercut] [image: linkedin:] [image: Twitter:] [image: Location:] Company Registration No : 07926926 | VAT No : 128198591 Registered Office : 1 Larkfield Grove, Chepstow, Monmouthshire, NP16 5UF, UK Address : Bristol & Bath Science Park, Dirac Cres, Emersons Green, Bristol BS16 7FR -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 20 10:10:40 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 20 Mar 2018 10:10:40 -0400 Subject: [Paraview] structured to unstructured when using multiblocks filter In-Reply-To: <23913358.6188.1521490014248.JavaMail.zimbra@be.itu.edu.tr> References: <1742089608.5120.1521393710991.JavaMail.zimbra@be.itu.edu.tr> <398cf356-aae2-dce3-3ab3-a736b6919edb@be.itu.edu.tr> <23913358.6188.1521490014248.JavaMail.zimbra@be.itu.edu.tr> Message-ID: Hi Ufuk, If the files are small, could you send them? I'll investigate some. Also, sending your Catalyst Python script may help clue me into what's going wrong. Best, Andy On Mon, Mar 19, 2018 at 4:06 PM, Ufuk Turuncoglu < u.utku.turuncoglu at be.itu.edu.tr> wrote: > Thanks for your valuable comments. Yes, for each model component has two > grid 2d and 3d and they are coming from different channels. It is working > under 5.4.1 but i'll check the bug and try to fix my version until 5.5 > released. BTW, even if I set whole extend (to test it I hardcoded it) in > the place that you indicate, the piece and whole extent is same in the > files. > > Regards, > > --ufuk > > > ------------------------------ > *From: *"Andy Bauer" > *To: *"Ufuk Utku Turuncoglu (BE)" > *Cc: *"paraview" > *Sent: *Monday, March 19, 2018 3:51:51 PM > *Subject: *Re: [Paraview] structured to unstructured when using > multiblocks filter > > Hi Ufuk, > > It looks like you're already using multi-channel input as you're adding > since you have " g_coprocessorData->AddInput(strarr[i]); " unless that's > always just called once. We're just trying to clarify the "inputs" by > naming them channels -- I'm not sure it makes it easier to understand but > it makes it easier to talk about with others that understand that concept > in Catalyst. > > Setting whole extent would look like the following at line 129 in > adaptor.cpp: > if (vtkDataSet* grid = vtkDataSet::SafeDownCast(g_coprocessorData-> > GetInputDescriptionByName(name)->GetGrid())) { > ParaViewCoProcessing::ClearFieldDataFromGrid(grid); > g_coprocessorData->GetInputDescriptionByName(name)-> SetWholeExtent(ilow, > ihigh, jlow, jhigh, klow, khigh); > } else { > > Here, *low and *high are global values. For example, for a 1D case if each > process has 5 points and you have 3 mpi processes > ilow=jlow=jhigh=klow=khigh=0 and ihigh=12. The > vtkStructuredGrid::SetExtent() would look like: > proc 0: 0, 4, 0, 0, 0, 0 > proc 1: 4, 8, 0, 0, 0, 0 > proc 2: 8, 12, 0, 0, 0, 0 > > This looks like you're doing it properly in grid.cpp though but I didn't > set the SetWholeExtent() in adaptor.cpp and I'm guessing that's what's > missing. > > The multi-channel input should work in 5.4.1 but I found a bug that's been > fixed in the upcoming 5.5 that was affecting Live. See > https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 for > details on that. It's fairly small so you can probably backport that to > your 5.4.1 build if you're more comfortable using 5.4.1. > > Cheers, > Andy > > On Mon, Mar 19, 2018 at 7:50 AM, Ufuk Utku Turuncoglu (BE) < > u.utku.turuncoglu at be.itu.edu.tr> wrote: > >> Hi Andy, >> >> Thanks for your help. Yes, each tile has its own grid information. The >> problem is that if i set whole extent in the adaptor side and write data to >> disk using allinputsgridwrite.py, the whole extent is same with piece >> extent. I am not sure what is going on in the background when live >> visualization activated. If you want to look at it for possible problem, >> the code is in following link (adaptor.cpp and grid.cpp), >> >> https://github.com/uturuncoglu/RegESM/tree/master/cop >> >> The second option is also worth to try but first i need to look at the >> example. BTW, i am using 5.4.1. Do you think that the multi-channel input >> also works with 5.4.1? How it is handled by Catalyst in live mode? Do i >> have multiple visualization pipeline? >> >> Regards, >> >> --ufuk >> >> >> On 19.03.2018 13:36, Andy Bauer wrote: >> >> Hi Ufuk, >> >> Currently a multipiece data set always has to be nested under a >> multiblock dataset. This definitely seems like an unreasonable limitation >> on a structured grid under a multipiece dataset but I suspect we just >> haven't had the resources to put into making this work properly. My >> suggestion would be to try just having your Catalyst adaptor provide a >> structured grid directly, assuming you only have one grid per mpi process, >> and then try volume rendering like that. If you do this though, make sure >> to set the whole extent with vtkCPInputDataDescription::SetWholeExtent(). >> >> >> A thought here -- instead of changing your adaptor to generate the >> structured grid directly instead of a multipiece dataset, maybe create a >> second "channel" through a second vtkCPInputDataDescription that provides >> just a structured grid. This way you can provide both dataset types as >> needed instead of having to modify code back and forth, recompile, etc. to >> get different functionality. See the Examples/Catalyst/CxxMultiChannelInputExample >> in the 5.5 source code for some more details on this. >> >> I can't remember if you were using the editions or just the full ParaView >> Catalyst build but in 5.5 there will be a volume rendering Catalyst >> addition. >> >> Note that the multiblock/multipiece hierarchy will be undergoing a >> significant change in the near future. >> >> Best, >> Andy >> >> >> On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu < >> u.utku.turuncoglu at be.itu.edu.tr> wrote: >> >>> Hi, >>> >>> I am using MPI parallel code under Catalyst co-processing. In this case, >>> i am defining data by creating multi-block dataset and putting multi-piece >>> dataset into the first block (0). In this case, each piece is defined as >>> structured grid. The problem is that, to create volume rendering, i need to >>> use MergeBlocks filter under ParaView but it changes data type from >>> structured grid to unstructured one. I just wonder that is there any way to >>> merge blocks without changing type? Programmable filter etc.? Another >>> workaround could be defining dataset without using multi block under >>> co-processing adaptor code. So, is it possible to represent multi-piece >>> data under co-processing without putting it into multi-bloack dataset. >>> >>> Regards, >>> >>> --ufuk >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 20 10:33:47 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 10:33:47 -0400 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <8f6d7d0c5eaf5f6e6ee21ec0f89ccb54@fau.de> References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> <8f6d7d0c5eaf5f6e6ee21ec0f89ccb54@fau.de> Message-ID: Simon, Thanks for the report. As a workaround, you can go to Edit > Settings... and under the render tab, click the gear to access the "Depth Peeling for Volumes" option. Turn this off and you should no longer get the warning. Utkarsh, This warning is a useful message, but it will appear all the time for Simon. Shall we filter the message out of the output messages? Thanks, Cory On Tue, Mar 20, 2018 at 9:47 AM, Michalke, Simon wrote: > Hi, > > I get the following warning when trying to open the .vtu file: > > Warning: In /home/simon/code/cfs_paraview/metabuild/build/superbuild/par > aview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, line 379 > vtkOpenGLRenderer (0x46b0440): UseDepthPeelingForVolumes requested, but > unsupported since DualDepthPeeling is not available. > > otherwise it is working. > > Simon > > > Am 2018-03-20 14:05, schrieb Fabian Wein: > >> On 03/19/18 18:02, Scott, W Alan wrote: >> >>> Hmmm... No, another configuration file isn't necessary. >>> >>> Could you give us the dataset (if it is small) and a File/ Save State >>> file? I tried replicating this with Wavelet, and everything looks fine... >>> Ditto a slice of disk_out_ref. I'm wondering if it has to do with the >>> dataset type or the extents (bounds, on the information tab). >>> >> >> I just checked with 5.5-RC3 and the error persists on my machine. >> >> Fabian >> > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Tue Mar 20 10:42:29 2018 From: denis.cohen at gmail.com (denis cohen) Date: Tue, 20 Mar 2018 15:42:29 +0100 Subject: [Paraview] state file In-Reply-To: References: Message-ID: Hi Cory, Utkarsh, Thanks for checking all this. All options I tried in the dialog did not work. I can't remember exactly when it last worked (and it did) but I think things no longer worked with version 5 of paraview, so a while back. Unfortunately I've reinstalled all my computers so lost all earlier versions of Paraview. Denis On Tue, Mar 20, 2018 at 2:00 PM, Cory Quammen wrote: > On Tue, Mar 20, 2018 at 7:51 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Denis, >> With 5.4.1 and newer, isn't the Load State Options dialog [1] working? >> You should be able to simply select the new set of pvtu files to read by >> selecting **Choose File Names** and then selecting the new file series >> using the File Dialog for the appropriate reader. Is that not working as >> expected? >> > > I just tested locally RC3 and I get only the files listed in the state > file despite using **Choose File Names** :-( I'll write up a bug. > > Cory > > >> Utkarsh >> >> [1] https://blog.kitware.com/new-options-when-loading-paravi >> ew-state-files/ >> >> On Tue, Mar 20, 2018 at 2:13 AM, denis cohen >> wrote: >> >>> Hi Cory, >>> I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) >>> Do you mean that you can't open the data file or the pvsm file? >>> Denis >>> >>> >>> On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen >>> wrote: >>> >>>> On Wed, Mar 14, 2018 at 5:36 AM, denis cohen >>>> wrote: >>>> >>>>> Hello, >>>>> In past versions of paraview, opening a pvsm state file that read >>>>> several pvtu files resulted in paraview opening all the pvtu files in that >>>>> directory. Now it only opens the ones saved in the pvsm file. This is >>>>> annoying when the number of files has increased (like during a long time >>>>> dependent simulation) and when wanting to use the same pvsm state file. Any >>>>> ways of getting around that? >>>>> Thank you >>>>> Denis >>>>> >>>> >>>> Dennis, >>>> >>>> What version of ParaView did this? I just tried 5.2, and could not get >>>> "new" datasets to be loaded in the manner you described. Could you provide >>>> more details? >>>> >>>> Thanks, >>>> Cory >>>> >>>> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Tue Mar 20 11:09:37 2018 From: fabian.wein at fau.de (Fabian Wein) Date: Tue, 20 Mar 2018 16:09:37 +0100 Subject: [Paraview] Fwd: Re: [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: Message-ID: <17f9804e-a0bb-2ce1-2f31-f7d10d2aa60e@fau.de> Forgot List. On 03/20/18 15:33, Cory Quammen wrote: > Simon, > > Thanks for the report. As a workaround, you can go to Edit > Settings... and under the render tab, click the gear to access the "Depth Peeling for Volumes" option. Turn this off and you should no longer get the warning. > > Utkarsh, > > This warning is a useful message, but it will appear all the time for Simon. Shall we filter the message out of the output messages? Switching Depth Peeling off enables Axes grid for me! I don't even need a dataset to check. Note, that I did not get a warning. Fabian > > Thanks, > Cory > > On Tue, Mar 20, 2018 at 9:47 AM, Michalke, Simon > wrote: > > Hi, > > I get the following warning when trying to open the .vtu file: > > Warning: In /home/simon/code/cfs_paraview/metabuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, line 379 > vtkOpenGLRenderer (0x46b0440): UseDepthPeelingForVolumes requested, but unsupported since DualDepthPeeling is not available. > > otherwise it is working. > > Simon > > > Am 2018-03-20 14:05, schrieb Fabian Wein: > > On 03/19/18 18:02, Scott, W Alan wrote: > > Hmmm...? No, another configuration file isn't necessary. > > Could you give us the dataset (if it is small) and a File/ Save State file?? I tried replicating this with Wavelet, and everything looks fine...? Ditto a slice of disk_out_ref.? I'm wondering if it has to do with the dataset type or the extents (bounds, on the information tab). > > > I just checked with 5.5-RC3 and the error persists on my machine. > > Fabian > > -------------- next part -------------- A non-text attachment was scrubbed... Name: 55_rc3_ok.png Type: image/png Size: 281411 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv55rc_not_ok.png Type: image/png Size: 269126 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Mar 20 11:39:14 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 11:39:14 -0400 Subject: [Paraview] state file In-Reply-To: References: Message-ID: Denis, No problem. I'll work on a fix, hopefully for 5.5.0 final. Thanks, Cory On Tue, Mar 20, 2018 at 10:42 AM, denis cohen wrote: > Hi Cory, Utkarsh, > Thanks for checking all this. All options I tried in the dialog did not > work. > I can't remember exactly when it last worked (and it did) but I think > things no longer worked with version 5 of paraview, so a while back. > Unfortunately I've reinstalled all my computers so lost all earlier > versions of Paraview. > Denis > > On Tue, Mar 20, 2018 at 2:00 PM, Cory Quammen > wrote: > >> On Tue, Mar 20, 2018 at 7:51 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Denis, >>> With 5.4.1 and newer, isn't the Load State Options dialog [1] working? >>> You should be able to simply select the new set of pvtu files to read by >>> selecting **Choose File Names** and then selecting the new file series >>> using the File Dialog for the appropriate reader. Is that not working as >>> expected? >>> >> >> I just tested locally RC3 and I get only the files listed in the state >> file despite using **Choose File Names** :-( I'll write up a bug. >> >> Cory >> >> >>> Utkarsh >>> >>> [1] https://blog.kitware.com/new-options-when-loading-paravi >>> ew-state-files/ >>> >>> On Tue, Mar 20, 2018 at 2:13 AM, denis cohen >>> wrote: >>> >>>> Hi Cory, >>>> I am using 5.5.0-RC3 64 bit on Linux (recently downloaded) >>>> Do you mean that you can't open the data file or the pvsm file? >>>> Denis >>>> >>>> >>>> On Tue, Mar 20, 2018 at 6:39 AM, Cory Quammen >>> > wrote: >>>> >>>>> On Wed, Mar 14, 2018 at 5:36 AM, denis cohen >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> In past versions of paraview, opening a pvsm state file that read >>>>>> several pvtu files resulted in paraview opening all the pvtu files in that >>>>>> directory. Now it only opens the ones saved in the pvsm file. This is >>>>>> annoying when the number of files has increased (like during a long time >>>>>> dependent simulation) and when wanting to use the same pvsm state file. Any >>>>>> ways of getting around that? >>>>>> Thank you >>>>>> Denis >>>>>> >>>>> >>>>> Dennis, >>>>> >>>>> What version of ParaView did this? I just tried 5.2, and could not get >>>>> "new" datasets to be loaded in the manner you described. Could you provide >>>>> more details? >>>>> >>>>> Thanks, >>>>> Cory >>>>> >>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 20 11:44:02 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 20 Mar 2018 11:44:02 -0400 Subject: [Paraview] Fwd: Re: [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: <17f9804e-a0bb-2ce1-2f31-f7d10d2aa60e@fau.de> References: <17f9804e-a0bb-2ce1-2f31-f7d10d2aa60e@fau.de> Message-ID: > Switching Depth Peeling off enables Axes grid for me! I don't even need a > dataset to check. Note, that I did not get a warning. > > @ Fabian Thanks for the additional clue. @Allison - it looks like there is an interaction on some systems with the axes grid label rendering and depth peeling. Is that something you can help track down? Thanks, Cory > Fabian > > > > >> Thanks, >> Cory >> >> On Tue, Mar 20, 2018 at 9:47 AM, Michalke, Simon > > wrote: >> >> Hi, >> >> I get the following warning when trying to open the .vtu file: >> >> Warning: In /home/simon/code/cfs_paraview/ >> metabuild/build/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, >> line 379 >> vtkOpenGLRenderer (0x46b0440): UseDepthPeelingForVolumes requested, >> but unsupported since DualDepthPeeling is not available. >> >> otherwise it is working. >> >> Simon >> >> >> Am 2018-03-20 14:05, schrieb Fabian Wein: >> >> On 03/19/18 18:02, Scott, W Alan wrote: >> >> Hmmm... No, another configuration file isn't necessary. >> >> Could you give us the dataset (if it is small) and a File/ >> Save State file? I tried replicating this with Wavelet, and everything >> looks fine... Ditto a slice of disk_out_ref. I'm wondering if it has to >> do with the dataset type or the extents (bounds, on the information tab). >> >> >> I just checked with 5.5-RC3 and the error persists on my machine. >> >> Fabian >> >> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From grothausmann.roman at mh-hannover.de Tue Mar 20 12:13:02 2018 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Tue, 20 Mar 2018 17:13:02 +0100 Subject: [Paraview] unknown properties returned by ListProperties? In-Reply-To: References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> Message-ID: <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> Many thanks Cory for your feedback. Not adding empty (None) properties did not help (http://github.com/romangrothausmann/ParaView_scripts/commit/d3af645dd1af2a). Anyway, "ForceUseCache" has a vector of value 0 so it seems to me the actual problem still is that ListProperties() returns properties that are not part of the specific object that is calling ListProperties(). E.g. help(repr) does not list a property called "ForceUseCache" but e.g. "Visibility" So I decided to only restore the property "Visibility" for a start: http://github.com/romangrothausmann/ParaView_scripts/commit/d1c63f2682e834e Even though there is no error on execution any more, the resulting PVSM has only the visibilities set for the last loaded PVSM, i.e. the setting of the "Visibility" of representations loaded from former PVSMs did not have any effect. Is there a need to call some kind of Update() to make the property setting have any effect? I tried some rendering (http://github.com/romangrothausmann/ParaView_scripts/commit/294ff85a0cc7a), but that did not help either. On 20/03/18 06:12, Cory Quammen wrote: > Roman, > > Looking at your original problem with the error: > > > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ???? prop.SetData(arg) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 1296, in SetData > ???? self.SMProperty.AddProxy(value_proxy) > TypeError: AddProxy argument 1: method requires a VTK object > > > You are hitting this when attempting to set the DataAxesGrid, which is a > ProxyProperty. In your dictionary, this entry has value 'None', but it looks > like setting a property to value 'None' is not handled correctly in > servermanager.py. As a workaround, I suggest filtering out properties from your > dictionary that have 'None' as a value, i.e., do not add those property values > to your dictionary. > > HTH, > Cory > > On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr. > > > wrote: > > Hi Cory, > > > Trying to find out what causes the former problems, I inserted a line that > just sets the property that got collected so far: > https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59 > > It already aborts on the first property encountered (ForceUseCache): > > > ForceUseCache 0 > Traceback (most recent call last): > ? File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in > ? ? main() > ? File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main > ? ? pvs.SetProperties(repr, **d) > ? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", > line 567, in SetProperties > ? ? raise AttributeError("object has no property %s" % param) > AttributeError: object has no property ForceUseCache > > Is ListProperties() returning properties that are not part of the specific > object that is calling ListProperties()? > > Many thanks for any help or hints, > Roman > > On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: > > Hi Cory, > > On 06/12/17 23:06, Cory Quammen wrote: > > Sorry I failed to follow up. Did you find a solution to this problem? > > > Many thanks for your reply. No, and I'm still stuck. I tried Your > suggestion to remove [0] > (https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd > ), > which changed the reported error from: > > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ???? prop.SetData(arg) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 803, in SetData > ???? raise RuntimeError("This property requires %d values." % > self.GetNumberOfElements()) > RuntimeError: This property requires 3 values. > > to: > > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ???? prop.SetData(arg) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 1296, in SetData > ???? self.SMProperty.AddProxy(value_proxy) > TypeError: AddProxy argument 1: method requires a VTK object > > Any ideas on this? > Would You say it is a general problem in the py-code or could it be > caused by the content of the PVSMs I'm trying to combine? > > Many thanks for looking into this. > Roman > > > This line in your script looks funny to me: > > d[props] = pvs.GetProperty(repr, props[0]) > > Shouldn't props[0] just be props? > > Thanks, > Cory > > On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. > > wrote: > > Dear Cory, > > On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: > > > On 15/09/17 15:14, Cory Quammen wrote: > > > Put a ** in front of reppro[i], e.g., > > pvs.SetProperties(repr, **reppro[i]) > > > Hm, I now get: > TypeError: SetProperties() argument after ** must be a > mapping, not list > Do I have to store the dict of object properties in another > dict instead > of a list? > > > > With a dict of dicts > https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e > > > I get: > > ?? File "/net/home/grothama/paraview/scripts/pvsm-multi.py", > line 64, in main > ???? pvs.SetProperties(repr, **reppro[i]); > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", > line 568, in SetProperties > ???? setattr(proxy, param, params[param]) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > line 317, in __setattr__ > ???? setter(self, value) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > line 2528, in setProperty > ???? return self.SetPropertyWithName(propName, value) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > line 375, in SetPropertyWithName > ???? prop.SetData(arg) > ?? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > line 803, in SetData > ???? raise RuntimeError("This property requires %d values." % > self.GetNumberOfElements()) > RuntimeError: This property requires 3 values. > > Any ideas what could still be wrong? > > > On 07/09/17 23:37, Cory Quammen wrote: > > > > Hi Roman, > > It turns out ParaView was not designed for this > use case because of > certain difficulties discussed here: > > https://gitlab.kitware.com/paraview/paraview/issues/17442 > > > In your Python script, you could manually cash > all the properties of > the existing representations and restore them > after loading the most > recent state file. > > The functions > > reprs = GetRepresentations() > repr = reprs.values()[0] > props = repr.ListProperties() > GetProperty(repr, props[0]) > > would be helpful for this. > > Cory > > > On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, > Roman Dr. > > wrote: > > > > Dear mailing list members, > > > It seems that PV (and > paraview.simple.LoadState) by default hides > already > loaded objects (and resets e.g. their > coloring) when another > state-file > is > loaded. > Is there a way to load multiple state-files > after one another without > hiding > and resetting already existent objects? I.e. > a way to concatenate > multiple > state-files and leave their objects in the > state as they got loaded > (e.g. > colored, hidden/visible)? > I do understand that loading a new > state-file will reset the camera, > but > not > the rest. > Here's my initial attempt to achieve this > with pvpython: > > > https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py > > > > Any help or hints are very much appreciated > Roman > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte > Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 > Hannover, Deutschland > > Tel. +49 511 532-2900 > > grothausmann.roman at mh-hannover.de > > http://www.mh-hannover.de/anatomie.html > > _______________________________________________ > 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 > > > > > > > > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, > Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > > http://www.mh-hannover.de/anatomie.html > > > > > > > > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > > http://www.mh-hannover.de/anatomie.html > > > > > > > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > http://www.mh-hannover.de/anatomie.html > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Medizinische Hochschule Hannover Institut f?r Funktionelle und Angewandte Anatomie OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland Tel. +49 511 532-2900 grothausmann.roman at mh-hannover.de http://www.mh-hannover.de/anatomie.html From manoch at iris.washington.edu Tue Mar 20 13:41:55 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Tue, 20 Mar 2018 10:41:55 -0700 Subject: [Paraview] vtkTable display In-Reply-To: References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> Message-ID: <3CD7E1D8-A348-4C71-BE96-7EE4B7C03336@iris.washington.edu> Hi Utkarsh, Many thanks for you reply. That is exactly what I was hoping for, but attached is what I get and that pushes my Render View to the side. Any suggestions? Thanks, ?manoch > On Mar 20, 2018, at 4:57 AM, Utkarsh Ayachit wrote: > > By "table panel" do you mean spreadsheet view or something else? With 5.5, I don't notice anything odd because of long names. The Spreadsheet view can shrink to a smaller size, as needed. > > > > > On Mon, Mar 19, 2018 at 1:02 PM, Manochehr Bahavar > wrote: > Hello, > > I am creating a Python programmable filter and I need to provide user some additional information. I have been using RenameSource to pass the needed information to user using pipeline object names. The rather long pipeline object names have not been causing an issue. However, I just tried to display a vtkTable and realized that because of the long names, the drop-down in the table panel takes too much horizontal space and causes the table panel to be too wide! Is there a better way of displaying the information or is there any way I can force the table panel to open under my display table and not next to it. > > I will appreciate any help > > Best, > > ?manoch > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-20 at 10.41.02 AM.png Type: image/png Size: 225727 bytes Desc: not available URL: From nahuja at mtu.edu Tue Mar 20 13:42:03 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Tue, 20 Mar 2018 13:42:03 -0400 Subject: [Paraview] Conversion error In-Reply-To: References: Message-ID: Thanks a lot Aaron, I saw that, these files are also not getting converted into Ensight format, as well. Best regards Nitisha On Tue, Mar 20, 2018 at 9:29 AM, Aron Helser wrote: > Hi Nitisha, > It's hard to know what the problem might be without knowing what steps you > are taking to convert the files - please provide some more details. > > I would guess it's a problem in the conversion software, not ParaView. > > Regards, > Aron > > On Mon, Mar 19, 2018 at 5:50 PM, Nitisha Ahuja wrote: > >> Hello all, >> I am facing an issue in which, I am trying to convert post.out files from >> Converge into paraview files. For few files I get the following error >> : >> >> I am not sure whether this is the right place to ask this question, as >> the problem can be in my software too. >> >> But if anyone knows what could be the reason behind failure in conversion >> of these file, please let me know. >> >> P.S.. I see this error on some random files. >> >> Best regards >> Nitisha >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 82676 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Mar 20 13:52:06 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 20 Mar 2018 13:52:06 -0400 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> <8f6d7d0c5eaf5f6e6ee21ec0f89ccb54@fau.de> Message-ID: > Utkarsh, > > This warning is a useful message, but it will appear all the time for Simon. > Shall we filter the message out of the output messages? Ideally, the renderer only puts that message out once in its lifetime. From salachoris1 at gmail.com Tue Mar 20 13:58:50 2018 From: salachoris1 at gmail.com (GeorgeP S) Date: Tue, 20 Mar 2018 18:58:50 +0100 Subject: [Paraview] Help :Texture coordinates Message-ID: Hello all, i wanted to know if there is a way to apply a texture on cells that do not have texture coordinates. If so how can i do it? Thank you, George Mail priva di virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From manoch at iris.washington.edu Tue Mar 20 14:30:09 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Tue, 20 Mar 2018 11:30:09 -0700 Subject: [Paraview] vtkTable display In-Reply-To: References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> Message-ID: <11D7D92B-22B5-4C2B-9364-9818B97F5515@iris.washington.edu> I also noticed that I am receiving these generic warnings when I open the SpreadSheetView! Although they are warning, could they play any role? Thanks, ?manoch Generic Warning: In /Users/kitware/dashboards/buildbot-slave/8275bd07/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 511 Failed to locate property: OSPRayMaterialLibrary Generic Warning: In /Users/kitware/dashboards/buildbot-slave/8275bd07/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 831 Call not supported for the current property type. > On Mar 20, 2018, at 4:57 AM, Utkarsh Ayachit wrote: > > By "table panel" do you mean spreadsheet view or something else? With 5.5, I don't notice anything odd because of long names. The Spreadsheet view can shrink to a smaller size, as needed. > > > > > On Mon, Mar 19, 2018 at 1:02 PM, Manochehr Bahavar > wrote: > Hello, > > I am creating a Python programmable filter and I need to provide user some additional information. I have been using RenameSource to pass the needed information to user using pipeline object names. The rather long pipeline object names have not been causing an issue. However, I just tried to display a vtkTable and realized that because of the long names, the drop-down in the table panel takes too much horizontal space and causes the table panel to be too wide! Is there a better way of displaying the information or is there any way I can force the table panel to open under my display table and not next to it. > > I will appreciate any help > > Best, > > ?manoch > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Mar 20 14:47:42 2018 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Turuncoglu) Date: Tue, 20 Mar 2018 21:47:42 +0300 (EET) Subject: [Paraview] structured to unstructured when using multiblocks filter Message-ID: <2022005634.8107.1521571662865.JavaMail.zimbra@be.itu.edu.tr> Hi Andy, You could find example dataset in the following link, [ https://kovan.itu.edu.tr/index.php/s/6RKZuW5rXGS57dR | https://kovan.itu.edu.tr/index.php/s/6RKZuW5rXGS57dR ] to work with IndeX volume rendering plugin, i add three grid point ghost region to the tiles in this case but it demonstrated whole extent problem. To write data I am using standard allinputsgrid.py and for volume rendering i am using attached co-processing script (this version creates a band around tiles when I use with standard volume rendering methods of ParaView, i think it is related with three grid ghost point). Regards, --ufuk On 20.03.2018 17:10, Andy Bauer wrote: Hi Ufuk, If the files are small, could you send them? I'll investigate some. Also, sending your Catalyst Python script may help clue me into what's going wrong. Best, Andy On Mon, Mar 19, 2018 at 4:06 PM, Ufuk Turuncoglu < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > wrote: BQ_BEGIN Thanks for your valuable comments. Yes, for each model component has two grid 2d and 3d and they are coming from different channels. It is working under 5.4.1 but i'll check the bug and try to fix my version until 5.5 released. BTW, even if I set whole extend (to test it I hardcoded it) in the place that you indicate, the piece and whole extent is same in the files. Regards, --ufuk From: "Andy Bauer" < [ mailto:andy.bauer at kitware.com | andy.bauer at kitware.com ] > To: "Ufuk Utku Turuncoglu (BE)" < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > Cc: "paraview" < [ mailto:paraview at paraview.org | paraview at paraview.org ] > Sent: Monday, March 19, 2018 3:51:51 PM Subject: Re: [Paraview] structured to unstructured when using multiblocks filter Hi Ufuk, It looks like you're already using multi-channel input as you're adding since you have " g_coprocessorData-> AddInput (strarr[i]); " unless that's always just called once. We're just trying to clarify the "inputs" by naming them channels -- I'm not sure it makes it easier to understand but it makes it easier to talk about with others that understand that concept in Catalyst. Setting whole extent would look like the following at line 129 in adaptor.cpp: if (vtkDataSet* grid = vtkDataSet::SafeDownCast (g_coprocessorData-> GetInputDescriptionByName (name)-> GetGrid ())) { ParaViewCoProcessing::ClearFieldDataFromGrid (grid); g_coprocessorData-> GetInputDescriptionByName (name)-> SetWholeExtent(ilow, ihigh, jlow, jhigh, klow, khigh); } else { Here, *low and *high are global values. For example, for a 1D case if each process has 5 points and you have 3 mpi processes ilow=jlow=jhigh=klow=khigh=0 and ihigh=12. The vtkStructuredGrid::SetExtent() would look like: proc 0: 0, 4, 0, 0, 0, 0 proc 1: 4, 8, 0, 0, 0, 0 proc 2: 8, 12, 0, 0, 0, 0 This looks like you're doing it properly in grid.cpp though but I didn't set the SetWholeExtent() in adaptor.cpp and I'm guessing that's what's missing. The multi-channel input should work in 5.4.1 but I found a bug that's been fixed in the upcoming 5.5 that was affecting Live. See [ https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 | https://gitlab.kitware.com/paraview/paraview/merge_requests/2212 ] for details on that. It's fairly small so you can probably backport that to your 5.4.1 build if you're more comfortable using 5.4.1. Cheers, Andy On Mon, Mar 19, 2018 at 7:50 AM, Ufuk Utku Turuncoglu (BE) < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > wrote: BQ_BEGIN Hi Andy, Thanks for your help. Yes, each tile has its own grid information. The problem is that if i set whole extent in the adaptor side and write data to disk using allinputsgridwrite.py, the whole extent is same with piece extent. I am not sure what is going on in the background when live visualization activated. If you want to look at it for possible problem, the code is in following link (adaptor.cpp and grid.cpp), [ https://github.com/uturuncoglu/RegESM/tree/master/cop | https://github.com/uturuncoglu/RegESM/tree/master/cop ] The second option is also worth to try but first i need to look at the example. BTW, i am using 5.4.1. Do you think that the multi-channel input also works with 5.4.1? How it is handled by Catalyst in live mode? Do i have multiple visualization pipeline? Regards, --ufuk On 19.03.2018 13:36, Andy Bauer wrote: BQ_BEGIN Hi Ufuk, Currently a multipiece data set always has to be nested under a multiblock dataset. This definitely seems like an unreasonable limitation on a structured grid under a multipiece dataset but I suspect we just haven't had the resources to put into making this work properly. My suggestion would be to try just having your Catalyst adaptor provide a structured grid directly, assuming you only have one grid per mpi process, and then try volume rendering like that. If you do this though, make sure to set the whole extent with vtkCPInputDataDescription::SetWholeExtent(). A thought here -- instead of changing your adaptor to generate the structured grid directly instead of a multipiece dataset, maybe create a second "channel" through a second vtkCPInputDataDescription that provides just a structured grid. This way you can provide both dataset types as needed instead of having to modify code back and forth, recompile, etc. to get different functionality. See the Examples/Catalyst/CxxMultiChannelInputExample in the 5.5 source code for some more details on this. I can't remember if you were using the editions or just the full ParaView Catalyst build but in 5.5 there will be a volume rendering Catalyst addition. Note that the multiblock/multipiece hierarchy will be undergoing a significant change in the near future. Best, Andy On Sun, Mar 18, 2018 at 1:21 PM, Ufuk Turuncoglu < [ mailto:u.utku.turuncoglu at be.itu.edu.tr | u.utku.turuncoglu at be.itu.edu.tr ] > wrote: BQ_BEGIN Hi, I am using MPI parallel code under Catalyst co-processing. In this case, i am defining data by creating multi-block dataset and putting multi-piece dataset into the first block (0). In this case, each piece is defined as structured grid. The problem is that, to create volume rendering, i need to use MergeBlocks filter under ParaView but it changes data type from structured grid to unstructured one. I just wonder that is there any way to merge blocks without changing type? Programmable filter etc.? Another workaround could be defining dataset without using multi block under co-processing adaptor code. So, is it possible to represent multi-piece data under co-processing without putting it into multi-bloack dataset. Regards, --ufuk _______________________________________________ Powered by [ http://www.kitware.com/ | www.kitware.com ] Visit other Kitware open-source projects at [ http://www.kitware.com/opensource/opensource.html | http://www.kitware.com/opensource/opensource.html ] Please keep messages on-topic and check the ParaView Wiki at: [ http://paraview.org/Wiki/ParaView | http://paraview.org/Wiki/ParaView ] Search the list archives at: [ http://markmail.org/search/?q=ParaView | http://markmail.org/search/?q=ParaView ] Follow this link to subscribe/unsubscribe: [ https://public.kitware.com/mailman/listinfo/paraview | https://public.kitware.com/mailman/listinfo/paraview ] BQ_END BQ_END BQ_END BQ_END -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: state_lr_541_v1_clouds_dvr.py Type: text/x-python Size: 12954 bytes Desc: not available URL: From dave.demarle at kitware.com Tue Mar 20 15:35:47 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 20 Mar 2018 15:35:47 -0400 Subject: [Paraview] Help :Texture coordinates In-Reply-To: References: Message-ID: The three Filters->Texture Map To ... filters programmatically create simple texture coordinates based on simple functions of the geometry. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Tue, Mar 20, 2018 at 1:58 PM, GeorgeP S wrote: > Hello all, > > i wanted to know if there is a way to apply a texture on cells that do not > have texture coordinates. If so how can i do it? > > Thank you, > George > > > Mail > priva di virus. www.avast.com > > <#m_-7146931150643625814_m_-4213450803092441443_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nahuja at mtu.edu Tue Mar 20 15:48:29 2018 From: nahuja at mtu.edu (Nitisha Ahuja) Date: Tue, 20 Mar 2018 15:48:29 -0400 Subject: [Paraview] Visualization of parcels in paraview without surface Message-ID: Hello all, I am trying to visualize a spray simulation in paraview. The problem that I am facing is as soon as I make the surface completely transparent to look at the spray parcels, spray parcels also disappear, as shown below. How can I visualize these parcels without surface showing in Paraview Best regards Nitisha -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 58548 bytes Desc: not available URL: From manoch at iris.washington.edu Tue Mar 20 17:03:53 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Tue, 20 Mar 2018 14:03:53 -0700 Subject: [Paraview] vtkTable display In-Reply-To: References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> Message-ID: <312CFB1E-31EC-43CA-A54D-106C7B15DC7B@iris.washington.edu> Sorry Utkarsh for multiple emails, but I am now able to demonstrate the problem starting whit what you have. Here is what I did (images are attached): 1. I have a Pipeline Browser, a RenderView and a SpreadSheetView and place an object in the pipeline with a short name, all views look good 2. Rename the object in the Pipeline Browser and make the name very long. Like your example, all looks good and I see no problem 3. I slightly resize my RenderView and now the drop-down in the SpreadSheetView expands to full length and does not let me resize the window!! Any suggestions? Thanks, ?manoch > On Mar 20, 2018, at 4:57 AM, Utkarsh Ayachit wrote: > > By "table panel" do you mean spreadsheet view or something else? With 5.5, I don't notice anything odd because of long names. The Spreadsheet view can shrink to a smaller size, as needed. > > > > > On Mon, Mar 19, 2018 at 1:02 PM, Manochehr Bahavar > wrote: > Hello, > > I am creating a Python programmable filter and I need to provide user some additional information. I have been using RenameSource to pass the needed information to user using pipeline object names. The rather long pipeline object names have not been causing an issue. However, I just tried to display a vtkTable and realized that because of the long names, the drop-down in the table panel takes too much horizontal space and causes the table panel to be too wide! Is there a better way of displaying the information or is there any way I can force the table panel to open under my display table and not next to it. > > I will appreciate any help > > Best, > > ?manoch > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-20 at 1.39.35 PM.png Type: image/png Size: 152091 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-20 at 1.40.06 PM.png Type: image/png Size: 153313 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-20 at 1.40.58 PM.png Type: image/png Size: 143358 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Mar 20 17:12:20 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 20 Mar 2018 17:12:20 -0400 Subject: [Paraview] vtkTable display In-Reply-To: <312CFB1E-31EC-43CA-A54D-106C7B15DC7B@iris.washington.edu> References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> <312CFB1E-31EC-43CA-A54D-106C7B15DC7B@iris.washington.edu> Message-ID: Manoch, Thanks! I can reproduce it now as well. Mind reporting it as a bug on the issue tracker? I don't there's any fix for this that doesn't involve fixing the code. Utkarsh From manoch at iris.washington.edu Tue Mar 20 17:23:33 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Tue, 20 Mar 2018 14:23:33 -0700 Subject: [Paraview] vtkTable display In-Reply-To: References: <412CD89E-EB94-4B7D-81CA-217BCE319F20@iris.washington.edu> <312CFB1E-31EC-43CA-A54D-106C7B15DC7B@iris.washington.edu> Message-ID: <1A38B1F3-AC1B-4B6A-A17A-48C30D097AE9@iris.washington.edu> Utkarsh, Sure, I will do that right now. Thanks, ?manoch > On Mar 20, 2018, at 2:12 PM, Utkarsh Ayachit wrote: > > Manoch, > > Thanks! I can reproduce it now as well. Mind reporting it as a bug on > the issue tracker? I don't there's any fix for this that doesn't > involve fixing the code. > > Utkarsh From martin.cuma at utah.edu Wed Mar 21 12:25:37 2018 From: martin.cuma at utah.edu (Martin Cuma) Date: Wed, 21 Mar 2018 10:25:37 -0600 (MDT) Subject: [Paraview] Building Paraview for headless rendering Message-ID: Hello we have an user who wants to use Paraview in headless mode. We found the hard way that the binary does not have the headless rendering enabled. Now I am trying to build the headless mode based on https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html but don't have much luck. I have a few questions that I hope those knowledgeable about the topic may answer. 1. A more genereal question first - our cluster nodes don't have good GPUs so the plan is to render on the CPU. I assume we need Mesa for it, right? Further, since we want to render on the server, do we need to set the DISPLAY variable to :0, or, is there any other way to tell this to Paraview? 2. As for our attempted build, I tried both the OSMesa and EGL with the following results: a) OSMesa - turn VTK_OPENGL_HAS_OSMESA on, cmake finds my OS installed OSMesa (CentOS7 - mesa-libOSMesa-devel-17.0.1-6.20170307.el7.x86_64), everything builds, but, when I try to run Paraview, I get: ERROR: In /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 831 vtkXOpenGLRenderWindow (0x425a480): GL version 2.1 with the gpu_shader4 extension is not supported by your graphics driver but is required for the new OpenGL rendering backend. Please update your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2. I should have a fairly recent Mesa and OpenGL on a stock CentOS7 system, e.g. $ glxinfo | grep -i "OpenGL version" OpenGL version string: 4.6.0 NVIDIA 390.30 $ rpm -qa | grep mesa-libGL- mesa-libGL-17.0.1-6.20170307.el7.x86_64 mesa-libGL-devel-17.0.1-6.20170307.el7.x86_64 Any chance this OpenGL and Mesa are not compatible with what Paraview is trying to do with the OSMesa? Note that if I compile without the VTK_OPENGL_HAS_OSMESA, I don't get the above error. b) EGL I do seem to have the EGL's part of Mesa installed: mesa-libEGL-17.0.1-6.20170307.el7.x86_64 mesa-libEGL-devel-17.0.1-6.20170307.el7.x86_64 but, the cmake complains that EGL_opengl_LIBRARY is not found. Any thoughts about this? As I mentioned, we are running a fairly stock CentOS 7.4. Or, ideally, is there a walktrough for the headless rendering Paraview build? Thanks, MC -- Martin Cuma Center for High Performance Computing Department of Geology and Geophysics University of Utah From utkarsh.ayachit at kitware.com Wed Mar 21 12:58:55 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 21 Mar 2018 12:58:55 -0400 Subject: [Paraview] Building Paraview for headless rendering In-Reply-To: References: Message-ID: > 1. A more genereal question first - our cluster nodes don't have good GPUs > so the plan is to render on the CPU. I assume we need Mesa for it, right? Yes. > Further, since we want to render on the server, do we need to set the > DISPLAY variable to :0, or, is there any other way to tell this to Paraview? This depends on whether you're going to build ParaView with X support or not. If you build with OSMesa, then you don't need X, as a result you don't need to set DISPLAY variable. > 2. (a) I suspect stock OSMesa is not built with support for llvmpipe which is needed to provide newer OpenGL versions. You should build Mesa from source with confguration options already setup in ParaView superbuild. See [1], [2]. Alternatively, you can use the superbuild itself to build osmesa for you, or ParaView with OSMesa support. > I should have a fairly recent Mesa and OpenGL on a stock CentOS7 system, > e.g. > $ glxinfo | grep -i "OpenGL version" > OpenGL version string: 4.6.0 NVIDIA 390.30 This is not giving you the renderer OSMesa will use. If you were using Mesa, you'd get a "Mesa..." something in your OpenGL version string and not NVIdia. > Note that if I compile without the VTK_OPENGL_HAS_OSMESA, I don't get the > above error. That because then you're indeed using your GPU drivers. > b) EGL Mesa EGL is not supported as currently it does not support full OpenGL, only OpenGL-ES. > Or, ideally, is there a walktrough for the headless rendering Paraview > build? Just use the superbuild [3]. Check the readme out for more info, but to build osmesa paraview, I'd just enable `ENABLE_paraview` and `ENABLE_osmesa` Cmake variabels and build. You than then enable MPI too and pick set `USE_SYSTEM_mpi` if you want to use existing MPI on your system. HTH, Utkarsh [1] https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/projects/unix/osmesa.cmake [2] https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/projects/unix/mesa.common.cmake [3] https://gitlab.kitware.com/paraview/paraview-superbuild From chuck.atkins at kitware.com Wed Mar 21 12:58:44 2018 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Wed, 21 Mar 2018 12:58:44 -0400 Subject: [Paraview] Building Paraview for headless rendering In-Reply-To: References: Message-ID: Hi Martin, we have an user who wants to use Paraview in headless mode. We found the > hard way that the binary does not have the headless rendering enabled. > Yes and no. The pre-built binaries you download do require an X server to be present. However, that can be achieved in many different ways. One common approach for a headless environment is to use Xvnc to start up a fake X server that you never actually look at or log in to. You can then set the DISPLAY variable to whatever that starts up as and have ParaView use it. You can then use the included mesa libraries via the --mesa-swr or --mesa-llvmpipe flags to pvserver or pvbatch. Given that, you could get away with probably using the pre-built binaries as the easiest route. That being said, if you still want to build your own, I'll go ahead and answer your remaining questions. > 1. A more genereal question first - our cluster nodes don't have good GPUs > so the plan is to render on the CPU. I assume we need Mesa for it, right? Yes. CPU based rendering will be via the mesa llvmpipe or swr drivers. If you have relatively new Intel CPUs, i.e. SandyBridge or newer, then you'll want to use the swr driver as it's far more performant and scalable. > Further, since we want to render on the server, do we need to set the > DISPLAY variable to :0, or, is there any other way to tell this to Paraview? > If you're building using OSMesa tfor off-screen-only rendering then the DISPLAY variable has no meaning and is not needed. It's used to tell ParaView which X server to use for rendering (see above with starting a virtual X server via vnc). > 2. As for our attempted build, I tried both the OSMesa and EGL with the > following results: > > a) OSMesa - turn VTK_OPENGL_HAS_OSMESA on, cmake finds my OS installed > OSMesa (CentOS7 - mesa-libOSMesa-devel-17.0.1-6.20170307.el7.x86_64), > everything builds, but, when I try to run Paraview, I get: > ERROR: In /uufs/chpc.utah.edu/sys/srcdir/paraview/5.4.0/VTK/Rendering/ > OpenGL2/vtkOpenGLRenderWindow.cxx, line 831 > vtkXOpenGLRenderWindow (0x425a480): GL version 2.1 with the gpu_shader4 > extension is not supported by your graphics driver but is required for the > new OpenGL rendering backend. Please update your OpenGL driver. If you are > using Mesa please make sure you have version 10.6.5 or later and make sure > your driver in Mesa supports OpenGL 3.2. > Try setting both -DVTK_OPENGL_HAS_OSMESA=ON and -DVTK_OPENGL_USE_X=OFF . If it's still fussy,then set the environment variable MESA_GL_VERSION_OVERRIDE=3.3 . It shouldn't be an issue if you use the latest Mesa but the shipped 17.0.1 with CentOS may be a bit buggy. > b) EGL > The current EGL support is really only for use with offscreen rendering on NVidia GPUs and does not yet work with the Mesa EGL implementation. > As I mentioned, we are running a fairly stock CentOS 7.4. > You're best bet is to build your own Mesa rather than rely on the system package since a newer release will include the swr driver and be more performant. Or if you can use use the pre-built binaries with a dummy X server, you might save yourself a lot of headaches. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From demaio.a at gmail.com Wed Mar 21 13:37:04 2018 From: demaio.a at gmail.com (Alessandro De Maio) Date: Wed, 21 Mar 2018 18:37:04 +0100 Subject: [Paraview] XML plugin based on programmable filter with a slider Message-ID: Hello, I'm trying to write a plugin based on a programmable filter in order to extract a single block from a multiblockdataset (with a single level tree) in input chosing it through a slider in the property panel. I need help to automatically set the range of the slider (the higher limit as the lower is always 0) as the number of blocks of the multiblockdataset in input, but the XML ServerManager definition of the slider is not clear enough for me. I'm trying to follow Utkarsh suggestion in https://public.kitware.com/pipermail/paraview/2009-March/011599.html but I'm missing how to recovery the number of blocks of the input of the programmable filter and how to set it as the upper value of the slider range. Thank you in advance for your kind help Alessandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.cuma at utah.edu Wed Mar 21 13:30:09 2018 From: martin.cuma at utah.edu (Martin Cuma) Date: Wed, 21 Mar 2018 11:30:09 -0600 (MDT) Subject: [Paraview] Building Paraview for headless rendering In-Reply-To: References: Message-ID: Thanks Utkarsh and Chuck, I'll try your suggestions and let you know how it went. MC -- Martin Cuma Center for High Performance Computing Department of Geology and Geophysics University of Utah From dave.demarle at kitware.com Wed Mar 21 14:13:06 2018 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 21 Mar 2018 14:13:06 -0400 Subject: [Paraview] Help :Texture coordinates In-Reply-To: References: Message-ID: Adding the list back into the discussion so everyone can contribute to and benefit from the discussion. To the best of my knowledge we don't have anything that will do that type of modelling yet. Presumably you could write a programmable filter that would iterate over all of the cells, and use the cells orientation to make up texture coordinates, duplicating point coordinates as needed. That will be tricky. You will likely have more success by exporting the model from ParaView into a dedicated modelling/graphics package, generating the textures you want there, and then reimporting the result back into ParaView. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Mar 20, 2018 at 5:12 PM, GeorgeP S wrote: > Hello David E DeMarle, > > i saw the filters section although when i apply texture to plane it will > append the texture i want onto the whole surface of my building. > I shared through wetransfer a sample of one of the models. The generation > of this model came to be from LMGC90 platform. > As you will see the model is made from a series of "brick" elements, i > would like to find a way to texture them firstly because i am quite new to > paraview and i missed if there are the texture coordinates and how to use > them correctly, in case there are not any texture coordiantes for each one > of the "bricks" i would like to know a way to generate them and use them to > append a texture on them. > > Best regards, > Salachoris Georgios Panagiotis > > On Tue, Mar 20, 2018 at 8:35 PM, David E DeMarle > wrote: > >> The three Filters->Texture Map To ... filters programmatically create >> simple texture coordinates based on simple functions of the geometry. >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> >> On Tue, Mar 20, 2018 at 1:58 PM, GeorgeP S wrote: >> >>> Hello all, >>> >>> i wanted to know if there is a way to apply a texture on cells that do >>> not have texture coordinates. If so how can i do it? >>> >>> Thank you, >>> George >>> >>> >>> Mail >>> priva di virus. www.avast.com >>> >>> <#m_1611315017454307188_m_-4157686217231244707_m_-7146931150643625814_m_-4213450803092441443_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From salachoris1 at gmail.com Wed Mar 21 14:34:40 2018 From: salachoris1 at gmail.com (GeorgeP S) Date: Wed, 21 Mar 2018 19:34:40 +0100 Subject: [Paraview] Help :Texture coordinates In-Reply-To: References: Message-ID: Hello, due to the fact that i am quite new to Paraview i would like to ask, if i export the model into a dedicated modelling/graphics package will that change the "animation" result i obtain from my analysis? And if that will happen how can i avoid it ? Adding the list on, sorry about the last communication. On Wed, Mar 21, 2018 at 7:18 PM, GeorgeP S wrote: > Hello, > > due to the fact that i am quite new to Paraview i would like to ask, if i > export the model into a dedicated modelling/graphics package will that > change the "animation" result i > obtain from my analysis? And if that will happen how can i avoid it ? > > On Wed, Mar 21, 2018 at 7:13 PM, David E DeMarle > wrote: > >> Adding the list back into the discussion so everyone can contribute to >> and benefit from the discussion. >> >> To the best of my knowledge we don't have anything that will do that type >> of modelling yet. Presumably you could write a programmable filter that >> would iterate over all of the cells, and use the cells orientation to make >> up texture coordinates, duplicating point coordinates as needed. That will >> be tricky. >> >> You will likely have more success by exporting the model from ParaView >> into a dedicated modelling/graphics package, generating the textures you >> want there, and then reimporting the result back into ParaView. >> >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> >> On Tue, Mar 20, 2018 at 5:12 PM, GeorgeP S wrote: >> >>> Hello David E DeMarle, >>> >>> i saw the filters section although when i apply texture to plane it will >>> append the texture i want onto the whole surface of my building. >>> I shared through wetransfer a sample of one of the models. The >>> generation of this model came to be from LMGC90 platform. >>> As you will see the model is made from a series of "brick" elements, i >>> would like to find a way to texture them firstly because i am quite new to >>> paraview and i missed if there are the texture coordinates and how to use >>> them correctly, in case there are not any texture coordiantes for each one >>> of the "bricks" i would like to know a way to generate them and use them to >>> append a texture on them. >>> >>> Best regards, >>> Salachoris Georgios Panagiotis >>> >>> On Tue, Mar 20, 2018 at 8:35 PM, David E DeMarle < >>> dave.demarle at kitware.com> wrote: >>> >>>> The three Filters->Texture Map To ... filters programmatically create >>>> simple texture coordinates based on simple functions of the geometry. >>>> >>>> David E DeMarle >>>> Kitware, Inc. >>>> Principal Engineer >>>> 21 Corporate Drive >>>> Clifton Park, NY 12065-8662 >>>> Phone: 518-881-4909 <(518)%20881-4909> >>>> >>>> On Tue, Mar 20, 2018 at 1:58 PM, GeorgeP S >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> i wanted to know if there is a way to apply a texture on cells that do >>>>> not have texture coordinates. If so how can i do it? >>>>> >>>>> Thank you, >>>>> George >>>>> >>>>> >>>>> Mail >>>>> priva di virus. www.avast.com >>>>> >>>>> <#m_3250060239282922960_m_-8863085997190567699_m_1611315017454307188_m_-4157686217231244707_m_-7146931150643625814_m_-4213450803092441443_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Wed Mar 21 18:59:55 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 21 Mar 2018 18:59:55 -0400 Subject: [Paraview] immediate update Message-ID: Hello all: How do you get the ParaViewWeb client to update the window without clicking in it? I have some controls -- some buttons and sliders -- but when I change them, the view doesn't update until I click in the view frame and move slightly. Thank you, -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Wed Mar 21 19:39:45 2018 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Wed, 21 Mar 2018 19:39:45 -0400 Subject: [Paraview] XML plugin based on programmable filter with a slider In-Reply-To: References: Message-ID: Accidentally hit Reply instead of hit Reply list. The record is below: -------- Forwarded Message -------- Subject: Re: [Paraview] XML plugin based on programmable filter with a slider Date: Wed, 21 Mar 2018 19:38:40 -0400 From: Shuhao Wu To: Alessandro De Maio Hello Alessandro, I just published a library that allows you to do _just this_. See: https://github.com/shuhaowu/pvpyfilter The example covers exactly this and specifically you can use the property: double_slider = Double("double with slider", default=0.5, slider=[0.0, 1.0], help="double with slider between 0.0 and 1.0 and a default of 0.5") Let me know if the library works for you or if you encounter any bug as it is still early days for this library. Cheers, Shuhao On 2018-03-21 01:37 PM, Alessandro De Maio wrote: > Hello, > I'm trying to write a plugin based on a programmable filter in order to > extract a single block from a multiblockdataset (with a single level tree) > in input chosing it through a slider in the property panel. > I need help to automatically set the range of the slider (the higher limit > as the lower is always 0) as the number of blocks of the multiblockdataset > in input, but the XML ServerManager definition of the slider is not clear > enough for me. > > I'm trying to follow Utkarsh suggestion in > > https://public.kitware.com/pipermail/paraview/2009-March/011599.html > > but I'm missing how to recovery the number of blocks of the input of the > programmable filter and how to set it as the upper value of the slider > range. > > Thank you in advance for your kind help > > Alessandro > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From sebastien.jourdain at kitware.com Wed Mar 21 23:45:52 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 21 Mar 2018 21:45:52 -0600 Subject: [Paraview] immediate update In-Reply-To: References: Message-ID: On the server side you should do something like: https://github.com/Kitware/light-viz/blob/master/server/light_viz_protocols.py#L252 On Wed, Mar 21, 2018 at 4:59 PM, Sgouros, Thomas wrote: > Hello all: > > How do you get the ParaViewWeb client to update the window without > clicking in it? I have some controls -- some buttons and sliders -- but > when I change them, the view doesn't update until I click in the view frame > and move slightly. > > Thank you, > > -Tom > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.carrico at free.fr Thu Mar 22 03:32:58 2018 From: paul.carrico at free.fr (paul.carrico at free.fr) Date: Thu, 22 Mar 2018 08:32:58 +0100 Subject: [Paraview] Compiling Paraview on CentOS7 Message-ID: <02d403329ee42036b8b40d27be1c9092@free.fr> Dear All My colleagues and I would like to use Paraview to post-process FEA's results (mechanical and CFD and son on). I compilled the latest Paraview release on my CentOS 7 using mesa3D (from CentOS repository + Qt5 + openMPI + ...) to emulate openGL libraries, I still have a warning from Paraview and a compatibility issue; If I choose OpenGL instead OpenGL2 in ccmake, it asks for Qt4 instead of Qt5 I think this topic has ever been tackled by the community, so Where can I find advices to finalize it? Thanks for any feedback Paul (https://www.paraview.org/Wiki/ParaView:Build_And_Install) Here bellow some information's I got ######### ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 831 vtkXOpenGLRenderWindow (0x46643b0): GL version 2.1 with the gpu_shader4 extension is not supported by your graphics driver but is required for the new OpenGL rendering backend. Please update your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2. ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, line 816 vtkXOpenGLRenderWindow (0x46643b0): failed to create offscreen window ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819 vtkXOpenGLRenderWindow (0x46643b0): GLEW could not be initialized. ######### $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits) OpenGL version string: 2.1 Mesa 17.0.1 OpenGL shading language version string: 1.30 OpenGL extensions: OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 OpenGL ES profile extensions: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Thu Mar 22 03:53:09 2018 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 22 Mar 2018 08:53:09 +0100 Subject: [Paraview] Compiling Paraview on CentOS7 In-Reply-To: <02d403329ee42036b8b40d27be1c9092@free.fr> References: <02d403329ee42036b8b40d27be1c9092@free.fr> Message-ID: Hello Are you building in a VM ? In any case, this should do the trick : MESA_GL_VERSION_OVERRIDE=3.3 ./bin/paraview Best, Mathieu Westphal On Thu, Mar 22, 2018 at 8:32 AM, wrote: > Dear All > > My colleagues and I would like to use Paraview to post-process FEA's > results (mechanical and CFD and son on). > > I compilled the latest Paraview release on my CentOS 7 using mesa3D (from > CentOS repository + Qt5 + openMPI + ...) to emulate openGL libraries, I > still have a warning from Paraview and a compatibility issue; If I choose > OpenGL instead OpenGL2 in ccmake, it asks for Qt4 instead of Qt5 > > I think this topic has ever been tackled by the community, so Where can I > find advices to finalize it? > > Thanks for any feedback > > Paul > > (https://www.paraview.org/Wiki/ParaView:Build_And_Install) > > > Here bellow some information's I got > > ######### > > ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 831 > vtkXOpenGLRenderWindow (0x46643b0): GL version 2.1 with the gpu_shader4 > extension is not supported by your graphics driver but is required for the > new OpenGL rendering backend. Please update your OpenGL driver. If you are > using Mesa please make sure you have version 10.6.5 or later and make sure > your driver in Mesa supports OpenGL 3.2. > > ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, > line 816 > vtkXOpenGLRenderWindow (0x46643b0): failed to create offscreen window > > ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 819 > vtkXOpenGLRenderWindow (0x46643b0): GLEW could not be initialized. > > > ######### > > $ glxinfo | grep OpenGL > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits) > OpenGL version string: 2.1 Mesa 17.0.1 > OpenGL shading language version string: 1.30 > OpenGL extensions: > OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.0.1 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 > OpenGL ES profile extensions: > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Thu Mar 22 04:22:27 2018 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 22 Mar 2018 09:22:27 +0100 Subject: [Paraview] Compiling Paraview on CentOS7 In-Reply-To: References: <02d403329ee42036b8b40d27be1c9092@free.fr> Message-ID: Hello Paul This is an environement variable, so the simplest way is to run paraview from a terminal : Applications -> System Tools -> Terminal Then enter the following command cd /path/to/your/build/of/paraview MESA_GL_VERSION_OVERRIDE=3.3 ./bin/paraview If that works you may consider adding it to your environnement variables in your .bashrc file export MESA_GL_VERSION_OVERRIDE=3.3 Best, Mathieu Westphal On Thu, Mar 22, 2018 at 9:09 AM, wrote: > Hi Mathieu > > Thanks for the feedback ... and Yes Paraview is buit in a VM ... > > Sorry for the additional question, but where should I need to add "MESA_GL_VERSION_OVERRIDE=3.3 > ./bin/paraview" ? > > Paul > > > Le 2018-03-22 08:53, Mathieu Westphal a ?crit : > > Hello > > Are you building in a VM ? > > In any case, this should do the trick : > MESA_GL_VERSION_OVERRIDE=3.3 ./bin/paraview > > > Best, > > Mathieu Westphal > > On Thu, Mar 22, 2018 at 8:32 AM, wrote: > >> Dear All >> >> My colleagues and I would like to use Paraview to post-process FEA's >> results (mechanical and CFD and son on). >> >> I compilled the latest Paraview release on my CentOS 7 using mesa3D (from >> CentOS repository + Qt5 + openMPI + ...) to emulate openGL libraries, I >> still have a warning from Paraview and a compatibility issue; If I choose >> OpenGL instead OpenGL2 in ccmake, it asks for Qt4 instead of Qt5 >> >> I think this topic has ever been tackled by the community, so Where can I >> find advices to finalize it? >> >> Thanks for any feedback >> >> Paul >> >> (https://www.paraview.org/Wiki/ParaView:Build_And_Install) >> >> >> Here bellow some information's I got >> >> ######### >> >> ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, >> line 831 >> vtkXOpenGLRenderWindow (0x46643b0): GL version 2.1 with the gpu_shader4 >> extension is not supported by your graphics driver but is required for the >> new OpenGL rendering backend. Please update your OpenGL driver. If you are >> using Mesa please make sure you have version 10.6.5 or later and make sure >> your driver in Mesa supports OpenGL 3.2. >> >> ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, >> line 816 >> vtkXOpenGLRenderWindow (0x46643b0): failed to create offscreen window >> >> ERROR: In /opt/ParaView-v5.4.1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, >> line 819 >> vtkXOpenGLRenderWindow (0x46643b0): GLEW could not be initialized. >> >> >> ######### >> >> $ glxinfo | grep OpenGL >> OpenGL vendor string: VMware, Inc. >> OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits) >> OpenGL version string: 2.1 Mesa 17.0.1 >> OpenGL shading language version string: 1.30 >> OpenGL extensions: >> OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.0.1 >> OpenGL ES profile shading language version string: OpenGL ES GLSL ES >> 1.0.16 >> OpenGL ES profile extensions: >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aguirre.utn at gmail.com Thu Mar 22 07:59:55 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Thu, 22 Mar 2018 12:59:55 +0100 Subject: [Paraview] INTEGRATE FILTER : DIVIDE BY LENGTH Message-ID: Hello, I am using ? IntegrateVariables ? filter to integrate data along a line: my objective is to obtain the mean value of the parameters (e.g., the mean temperature). However the filter option ?Divide Cell Data by Volume? works only with volume data and surface data, but not with line data. So far, the only way to solve it is to apply another filter and divide the integral output by ?Length?. However, it is really annoying to do that for every single variable. There is a way to solve it directly with the ?IntegrateVariables? filter ? PS: I have seen that this filter option for 3D cases was analyzed recently ( https://gitlab.kitware.com/paraview/paraview/issues/16838), so maybe it will be easier to implement this in new versions. Thanks in advance Miguel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Thu Mar 22 08:38:06 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Thu, 22 Mar 2018 08:38:06 -0400 Subject: [Paraview] immediate update In-Reply-To: References: Message-ID: Thank you, but that doesn't seem to change anything for me. Doing this now: self.renderView1.Update() self.getApplication().InvokeEvent('UpdateEvent') Am I understanding it right that this is communicating with one of the ViewPort or ViewPortImageDelivery protocols? Should I be sure to include one of the other built-in protocols? Right now, I use those two, plus MouseHandler. Thank you, -Tom On Wed, Mar 21, 2018 at 11:45 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > On the server side you should do something like: > https://github.com/Kitware/light-viz/blob/master/server/ > light_viz_protocols.py#L252 > > On Wed, Mar 21, 2018 at 4:59 PM, Sgouros, Thomas > wrote: > >> Hello all: >> >> How do you get the ParaViewWeb client to update the window without >> clicking in it? I have some controls -- some buttons and sliders -- but >> when I change them, the view doesn't update until I click in the view frame >> and move slightly. >> >> Thank you, >> >> -Tom >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From demaio.a at gmail.com Thu Mar 22 09:59:49 2018 From: demaio.a at gmail.com (Alessandro De Maio) Date: Thu, 22 Mar 2018 14:59:49 +0100 Subject: [Paraview] XML plugin based on programmable filter with a slider In-Reply-To: References: Message-ID: Hello Shuhao, thank you for your reply and for your really great job on the pvpyfilter. I had already tried it and it's very useful. But I'm looking for the possibility to automatically assign the slider range (in this case the upper value will be enough) depending on information about the input of the programmable filter (in this case the number of blocks of a multiblock dataset) and not to set it hardcoded in the xml as from your approach. I would like that, if I apply this filter to a mbdataset with 5 blocks, the slider can choose an int value from 0 to 4, and if I apply the same filter (without modifying xml) to another mbdataset with 8 blocks the slider provides an int from 0 to 7. Cheers Alessandro PS With pvpyfilter is there the possibility of decide in the .py file the order of the widgets in the property panel? It seems to me that the order is random On Thu, Mar 22, 2018 at 12:39 AM, Shuhao Wu wrote: > Accidentally hit Reply instead of hit Reply list. The record is below: > > -------- Forwarded Message -------- > Subject: Re: [Paraview] XML plugin based on programmable filter with a > slider > Date: Wed, 21 Mar 2018 19:38:40 -0400 > From: Shuhao Wu > To: Alessandro De Maio > > Hello Alessandro, > > I just published a library that allows you to do _just this_. See: > https://github.com/shuhaowu/pvpyfilter > > The example covers exactly this and specifically you can use the property: > > double_slider = Double("double with slider", default=0.5, slider=[0.0, > 1.0], help="double with slider between 0.0 and 1.0 and a default of 0.5") > > Let me know if the library works for you or if you encounter any bug as it > is still early days for this library. > > Cheers, > Shuhao > > On 2018-03-21 01:37 PM, Alessandro De Maio wrote: > > Hello, > > I'm trying to write a plugin based on a programmable filter in order to > > extract a single block from a multiblockdataset (with a single level > tree) > > in input chosing it through a slider in the property panel. > > I need help to automatically set the range of the slider (the higher > limit > > as the lower is always 0) as the number of blocks of the > multiblockdataset > > in input, but the XML ServerManager definition of the slider is not clear > > enough for me. > > > > I'm trying to follow Utkarsh suggestion in > > > > https://public.kitware.com/pipermail/paraview/2009-March/011599.html > > > > but I'm missing how to recovery the number of blocks of the input of the > > programmable filter and how to set it as the upper value of the slider > > range. > > > > Thank you in advance for your kind help > > > > Alessandro > > > > > > > > _______________________________________________ > > 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: > > https://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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: > https://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Mar 22 10:49:02 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 22 Mar 2018 10:49:02 -0400 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.5.0-RC2 tagged, binaries available In-Reply-To: References: <6949ecb1-eaf1-a391-3f4e-2ff2effca3fd@mail.ru> <7e79cc5a-ae3b-e836-ca32-ebd8bc315fb4@fau.de> <0ecaabbf-dca6-7571-e570-863f1bff1688@fau.de> <53B9C2B1-5D9A-4756-AE6C-ABDA06EFE9EF@fau.de> <2C511CC7-06AD-400E-B1DC-4C0AA0AFAEF7@sandia.gov> <03319c89-a3d0-c2a3-7016-32997712da34@fau.de> <0af523a21cac42a58a5cf80abb516dba@ES01AMSNLNT.srn.sandia.gov> <3481101c-4213-2c41-27ec-834b667ca32c@fau.de> <8f6d7d0c5eaf5f6e6ee21ec0f89ccb54@fau.de> Message-ID: On Tue, Mar 20, 2018 at 1:52 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > Utkarsh, > > > > This warning is a useful message, but it will appear all the time for > Simon. > > Shall we filter the message out of the output messages? > > Ideally, the renderer only puts that message out once in its lifetime. > That is likely the case. The issue is that it will appear every time a new view that uses the renderer is created, i.e., at program startup. Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From manoch at iris.washington.edu Thu Mar 22 12:10:49 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Thu, 22 Mar 2018 09:10:49 -0700 Subject: [Paraview] scipy and Windows ParaView 5.5.0 Message-ID: Hello, I have developed a few Python Programable filters using ParaView 5.5.0 on Mac. Now that I am trying to use them on Windows platform, using ParaView 5.5.0, I get an error that scipy module is not available!! Any suggestions on how I may address this? Thanks, ?manoch From sebastien.jourdain at kitware.com Thu Mar 22 13:03:15 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 22 Mar 2018 11:03:15 -0600 Subject: [Paraview] immediate update In-Reply-To: References: Message-ID: ViewPortImageDelivery require the JS side to request a render while VtkImageDelivery allow the server to push the image without the client requesting it (self.getApplication().InvokeEvent('UpdateEvent')). VtkImageDelivery is used inside those components: https://github.com/Kitware/paraviewweb/tree/master/src/React/Renderers/VtkRenderer https://github.com/Kitware/paraviewweb/tree/master/src/NativeUI/Renderers/VtkRenderer Which renderer do you use and how do you set it up? Seb On Thu, Mar 22, 2018 at 6:38 AM, Sgouros, Thomas wrote: > Thank you, but that doesn't seem to change anything for me. Doing this now: > > self.renderView1.Update() > self.getApplication().InvokeEvent('UpdateEvent') > > Am I understanding it right that this is communicating with one of the > ViewPort or ViewPortImageDelivery protocols? Should I be sure to include > one of the other built-in protocols? Right now, I use those two, plus > MouseHandler. > > Thank you, > > -Tom > > On Wed, Mar 21, 2018 at 11:45 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> On the server side you should do something like: >> https://github.com/Kitware/light-viz/blob/master/server/ligh >> t_viz_protocols.py#L252 >> >> On Wed, Mar 21, 2018 at 4:59 PM, Sgouros, Thomas < >> thomas_sgouros at brown.edu> wrote: >> >>> Hello all: >>> >>> How do you get the ParaViewWeb client to update the window without >>> clicking in it? I have some controls -- some buttons and sliders -- but >>> when I change them, the view doesn't update until I click in the view frame >>> and move slightly. >>> >>> Thank you, >>> >>> -Tom >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Mar 22 13:51:16 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 22 Mar 2018 13:51:16 -0400 Subject: [Paraview] scipy and Windows ParaView 5.5.0 In-Reply-To: References: Message-ID: Hi Manoch, ParaView doesn't package scipy on Windows because compiling it (so we know it works with our Python) is extremely difficult. What you may be able to do is this: -Install Python 2.7.X on your system -Use pip install scipy to install the python wheels from PYPI -One of the following: ---put the location that scipy is installed in your PYTHONPATH before you run ParaView ---Prepend the location that scipy was installed to your sys.path right after starting ParaView ---Copy the scipy folder from the location it was installed into $PARAVIEW_INSTALL\bin\Lib\site-packages Keep in mind that this may not work. We use a slightly older version of Python 2.7 and I don't know if it maintained ABI compatibility. You may also run into conflicts with numpy since ParaView's numpy was not compiled with the fortran support that scipy needs. HTH, Shawn On Thu, Mar 22, 2018 at 12:10 PM, Manochehr Bahavar < manoch at iris.washington.edu> wrote: > Hello, > > I have developed a few Python Programable filters using ParaView 5.5.0 on > Mac. Now that I am trying to use them on Windows platform, using ParaView > 5.5.0, I get an error that scipy module is not available!! Any suggestions > on how I may address this? > > > Thanks, > > ?manoch > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From grothausmann.roman at mh-hannover.de Thu Mar 22 14:01:24 2018 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Thu, 22 Mar 2018 19:01:24 +0100 Subject: [Paraview] restoring visibility of representations of multiple, appended PVSMs In-Reply-To: <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> Message-ID: Added some very simple PVSMs and a Makefile for testing, as well as the results: https://github.com/romangrothausmann/ParaView_scripts/tree/test4pvsm-multi01 Only the visibility of the last loaded PVSM is set in the resulting PVSM (pvsm-multi_test.pvsm). Swapping the order of the input PVSMs demonstrates this: https://github.com/romangrothausmann/ParaView_scripts/commit/9cd3db7971 Any idea what could be wrong or missing in the PV-script? On 20/03/18 17:13, Grothausmann, Roman Dr. wrote: > Many thanks Cory for your feedback. Not adding empty (None) properties did not > help > (http://github.com/romangrothausmann/ParaView_scripts/commit/d3af645dd1af2a). > Anyway, "ForceUseCache" has a vector of value 0 so it seems to me the actual > problem still is that ListProperties() returns properties that are not part of > the specific object that is calling ListProperties(). E.g. help(repr) does not > list a property called "ForceUseCache" but e.g. "Visibility" > > So I decided to only restore the property "Visibility" for a start: > http://github.com/romangrothausmann/ParaView_scripts/commit/d1c63f2682e834e > Even though there is no error on execution any more, the resulting PVSM has only > the visibilities set for the last loaded PVSM, i.e. the setting of the > "Visibility" of representations loaded from former PVSMs did not have any effect. > Is there a need to call some kind of Update() to make the property setting have > any effect? I tried some rendering > (http://github.com/romangrothausmann/ParaView_scripts/commit/294ff85a0cc7a), but > that did not help either. > > > On 20/03/18 06:12, Cory Quammen wrote: >> Roman, >> >> Looking at your original problem with the error: >> >> >> ??? File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 375, in SetPropertyWithName >> ????? prop.SetData(arg) >> ??? File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 1296, in SetData >> ????? self.SMProperty.AddProxy(value_proxy) >> TypeError: AddProxy argument 1: method requires a VTK object >> >> >> You are hitting this when attempting to set the DataAxesGrid, which is a >> ProxyProperty. In your dictionary, this entry has value 'None', but it looks >> like setting a property to value 'None' is not handled correctly in >> servermanager.py. As a workaround, I suggest filtering out properties from >> your dictionary that have 'None' as a value, i.e., do not add those property >> values to your dictionary. >> >> HTH, >> Cory >> >> On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr. >> > >> wrote: >> >> ??? Hi Cory, >> >> >> ??? Trying to find out what causes the former problems, I inserted a line that >> ??? just sets the property that got collected so far: >> >> https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59 >> >> >> >> >> ??? It already aborts on the first property encountered (ForceUseCache): >> >> ??? >> ??? ForceUseCache 0 >> ??? Traceback (most recent call last): >> ???? ? File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in >> ???? ? ? main() >> ???? ? File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main >> ???? ? ? pvs.SetProperties(repr, **d) >> ???? ? File >> ??? "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", >> ??? line 567, in SetProperties >> ???? ? ? raise AttributeError("object has no property %s" % param) >> ??? AttributeError: object has no property ForceUseCache >> >> ??? Is ListProperties() returning properties that are not part of the specific >> ??? object that is calling ListProperties()? >> >> ??? Many thanks for any help or hints, >> ??? Roman >> >> ??? On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: >> >> ??????? Hi Cory, >> >> ??????? On 06/12/17 23:06, Cory Quammen wrote: >> >> ??????????? Sorry I failed to follow up. Did you find a solution to this problem? >> >> >> ??????? Many thanks for your reply. No, and I'm still stuck. I tried Your >> ??????? suggestion to remove [0] >> >> (https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd >> >> >> ), >> >> ??????? which changed the reported error from: >> >> ???????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> ??????? line 375, in SetPropertyWithName >> ???????? ???? prop.SetData(arg) >> ???????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> ??????? line 803, in SetData >> ???????? ???? raise RuntimeError("This property requires %d values." % >> ??????? self.GetNumberOfElements()) >> ??????? RuntimeError: This property requires 3 values. >> >> ??????? to: >> >> ???????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> ??????? line 375, in SetPropertyWithName >> ???????? ???? prop.SetData(arg) >> ???????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> ??????? line 1296, in SetData >> ???????? ???? self.SMProperty.AddProxy(value_proxy) >> ??????? TypeError: AddProxy argument 1: method requires a VTK object >> >> ??????? Any ideas on this? >> ??????? Would You say it is a general problem in the py-code or could it be >> ??????? caused by the content of the PVSMs I'm trying to combine? >> >> ??????? Many thanks for looking into this. >> ??????? Roman >> >> >> ??????????? This line in your script looks funny to me: >> >> ??????????? d[props] = pvs.GetProperty(repr, props[0]) >> >> ??????????? Shouldn't props[0] just be props? >> >> ??????????? Thanks, >> ??????????? Cory >> >> ??????????? On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. >> ??????????? > ??????????? > wrote: >> >> ??????????????? Dear Cory, >> >> ??????????????? On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: >> >> >> ??????????????????? On 15/09/17 15:14, Cory Quammen wrote: >> >> >> ??????????????????????? Put a ** in front of reppro[i], e.g., >> >> ??????????????????????? pvs.SetProperties(repr, **reppro[i]) >> >> >> ??????????????????? Hm, I now get: >> ??????????????????? TypeError: SetProperties() argument after ** must be a >> ??????????????????? mapping, not list >> ??????????????????? Do I have to store the dict of object properties in another >> ??????????????????? dict instead >> ??????????????????? of a list? >> >> >> >> ??????????????? With a dict of dicts >> >> https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e >> >> >> >> >> >> ??????????????? I get: >> >> ???????????????? ?? File "/net/home/grothama/paraview/scripts/pvsm-multi.py", >> ??????????????? line 64, in main >> ???????????????? ???? pvs.SetProperties(repr, **reppro[i]); >> ???????????????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", >> ??????????????? line 568, in SetProperties >> ???????????????? ???? setattr(proxy, param, params[param]) >> ???????????????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> >> ??????????????? line 317, in __setattr__ >> ???????????????? ???? setter(self, value) >> ???????????????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> >> ??????????????? line 2528, in setProperty >> ???????????????? ???? return self.SetPropertyWithName(propName, value) >> ???????????????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> >> ??????????????? line 375, in SetPropertyWithName >> ???????????????? ???? prop.SetData(arg) >> ???????????????? ?? File >> >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> >> >> ??????????????? line 803, in SetData >> ???????????????? ???? raise RuntimeError("This property requires %d values." % >> ??????????????? self.GetNumberOfElements()) >> ??????????????? RuntimeError: This property requires 3 values. >> >> ??????????????? Any ideas what could still be wrong? >> >> >> ??????????????????????????? On 07/09/17 23:37, Cory Quammen wrote: >> >> >> >> ??????????????????????????????? Hi Roman, >> >> ??????????????????????????????? It turns out ParaView was not designed for this >> ??????????????????????????????? use case because of >> ??????????????????????????????? certain difficulties discussed here: >> >> >> https://gitlab.kitware.com/paraview/paraview/issues/17442 >> >> >> >> ??????????????????????????????? In your Python script, you could manually cash >> ??????????????????????????????? all the properties of >> ??????????????????????????????? the existing representations and restore them >> ??????????????????????????????? after loading the most >> ??????????????????????????????? recent state file. >> >> ??????????????????????????????? The functions >> >> ??????????????????????????????? reprs = GetRepresentations() >> ??????????????????????????????? repr = reprs.values()[0] >> ??????????????????????????????? props = repr.ListProperties() >> ??????????????????????????????? GetProperty(repr, props[0]) >> >> ??????????????????????????????? would be helpful for this. >> >> ??????????????????????????????? Cory >> >> >> ??????????????????????????????? On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, >> ??????????????????????????????? Roman Dr. >> ??????????????????????????????? > ??????????????????????????????? > >> wrote: >> >> >> >> ??????????????????????????????????? Dear mailing list members, >> >> >> ??????????????????????????????????? It seems that PV (and >> ??????????????????????????????????? paraview.simple.LoadState) by default hides >> ??????????????????????????????????? already >> ??????????????????????????????????? loaded objects (and resets e.g. their >> ??????????????????????????????????? coloring) when another >> ??????????????????????????????????? state-file >> ??????????????????????????????????? is >> ??????????????????????????????????? loaded. >> ??????????????????????????????????? Is there a way to load multiple state-files >> ??????????????????????????????????? after one another without >> ??????????????????????????????????? hiding >> ??????????????????????????????????? and resetting already existent objects? I.e. >> ??????????????????????????????????? a way to concatenate >> ??????????????????????????????????? multiple >> ??????????????????????????????????? state-files and leave their objects in the >> ??????????????????????????????????? state as they got loaded >> ??????????????????????????????????? (e.g. >> ??????????????????????????????????? colored, hidden/visible)? >> ??????????????????????????????????? I do understand that loading a new >> ??????????????????????????????????? state-file will reset the camera, >> ??????????????????????????????????? but >> ??????????????????????????????????? not >> ??????????????????????????????????? the rest. >> ??????????????????????????????????? Here's my initial attempt to achieve this >> ??????????????????????????????????? with pvpython: >> >> >> >> https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py >> >> >> >> >> >> >> ??????????????????????????????????? Any help or hints are very much appreciated >> ??????????????????????????????????? Roman >> >> ??????????????????????????????????? -- ??????????????????????????????????? Dr. >> Roman Grothausmann >> >> ??????????????????????????????????? Tomographie und Digitale Bildverarbeitung >> ??????????????????????????????????? Tomography and Digital Image Analysis >> >> ??????????????????????????????????? Medizinische Hochschule Hannover >> ??????????????????????????????????? Institut f?r Funktionelle und Angewandte >> ??????????????????????????????????? Anatomie >> ??????????????????????????????????? OE 4120, Carl-Neuberg-Str. 1, 30625 >> ??????????????????????????????????? Hannover, Deutschland >> >> ??????????????????????????????????? Tel. +49 511 532-2900 >> ??????????????????????????????????? >> ??????????????????????????????????? grothausmann.roman at mh-hannover.de >> ??????????????????????????????????? >> ??????????????????????????????????? http://www.mh-hannover.de/anatomie.html >> ??????????????????????????????????? >> >> _______________________________________________ >> ??????????????????????????????????? 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 >> >> >> >> >> >> >> >> >> >> ??????????????????????????? -- ??????????????????????????? Dr. Roman Grothausmann >> >> ??????????????????????????? Tomographie und Digitale Bildverarbeitung >> ??????????????????????????? Tomography and Digital Image Analysis >> >> ??????????????????????????? Medizinische Hochschule Hannover >> ??????????????????????????? Institut f?r Funktionelle und Angewandte Anatomie >> ??????????????????????????? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, >> ??????????????????????????? Deutschland >> >> ??????????????????????????? Tel. +49 511 532-2900 >> ??????????????????????????? grothausmann.roman at mh-hannover.de >> ??????????????????????????? >> ??????????????????????????? http://www.mh-hannover.de/anatomie.html >> ??????????????????????????? >> >> >> >> >> >> >> >> ??????????????? -- ??????????????? Dr. Roman Grothausmann >> >> ??????????????? Tomographie und Digitale Bildverarbeitung >> ??????????????? Tomography and Digital Image Analysis >> >> ??????????????? Medizinische Hochschule Hannover >> ??????????????? Institut f?r Funktionelle und Angewandte Anatomie >> ??????????????? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >> >> ??????????????? Tel. +49 511 532-2900 >> ??????????????? grothausmann.roman at mh-hannover.de >> ??????????????? >> ??????????????? http://www.mh-hannover.de/anatomie.html >> ??????????????? >> >> >> >> >> >> >> ??? -- ??? Dr. Roman Grothausmann >> >> ??? Tomographie und Digitale Bildverarbeitung >> ??? Tomography and Digital Image Analysis >> >> ??? Medizinische Hochschule Hannover >> ??? Institut f?r Funktionelle und Angewandte Anatomie >> ??? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >> >> ??? Tel. +49 511 532-2900 >> ??? grothausmann.roman at mh-hannover.de >> ??? http://www.mh-hannover.de/anatomie.html >> ??? >> >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Medizinische Hochschule Hannover Institut f?r Funktionelle und Angewandte Anatomie OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland Tel. +49 511 532-2900 grothausmann.roman at mh-hannover.de http://www.mh-hannover.de/anatomie.html From thomas_sgouros at brown.edu Thu Mar 22 14:04:30 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Thu, 22 Mar 2018 14:04:30 -0400 Subject: [Paraview] immediate update In-Reply-To: References: Message-ID: That makes sense. I'm using RemoteRenderer, like this: import RemoteRenderer from 'paraviewweb/src/NativeUI/Canvas/RemoteRenderer'; ... smartConnect.onConnectionReady((connection) => { model.pvwClient = ParaViewWebClient.createClient(connection, [ 'MouseHandler', 'ViewPort', 'ViewPortImageDelivery', ], amsProtocols); const renderer = new RemoteRenderer(model.pvwClient); ... When I look in my paraviewweb/src/NativeUI/Renderers directory, I don't see VtkRenderer, only NativeImageRenderer and RemoteRendererStatsTable. I see VtkRenderer in the other place, though. Are they the same? Do I use them the same way as RemoteRenderer? Thank you, -Tom On Thu, Mar 22, 2018 at 1:03 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > ViewPortImageDelivery require the JS side to request a render > while VtkImageDelivery allow the server to push the image without the > client requesting it (self.getApplication().InvokeEvent('UpdateEvent')). > > VtkImageDelivery is used inside those components: > https://github.com/Kitware/paraviewweb/tree/master/src/ > React/Renderers/VtkRenderer > https://github.com/Kitware/paraviewweb/tree/master/src/ > NativeUI/Renderers/VtkRenderer > > Which renderer do you use and how do you set it up? > > Seb > > On Thu, Mar 22, 2018 at 6:38 AM, Sgouros, Thomas > wrote: > >> Thank you, but that doesn't seem to change anything for me. Doing this >> now: >> >> self.renderView1.Update() >> self.getApplication().InvokeEvent('UpdateEvent') >> >> Am I understanding it right that this is communicating with one of the >> ViewPort or ViewPortImageDelivery protocols? Should I be sure to include >> one of the other built-in protocols? Right now, I use those two, plus >> MouseHandler. >> >> Thank you, >> >> -Tom >> >> On Wed, Mar 21, 2018 at 11:45 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> On the server side you should do something like: >>> https://github.com/Kitware/light-viz/blob/master/server/ligh >>> t_viz_protocols.py#L252 >>> >>> On Wed, Mar 21, 2018 at 4:59 PM, Sgouros, Thomas < >>> thomas_sgouros at brown.edu> wrote: >>> >>>> Hello all: >>>> >>>> How do you get the ParaViewWeb client to update the window without >>>> clicking in it? I have some controls -- some buttons and sliders -- but >>>> when I change them, the view doesn't update until I click in the view frame >>>> and move slightly. >>>> >>>> Thank you, >>>> >>>> -Tom >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manoch at iris.washington.edu Thu Mar 22 14:09:52 2018 From: manoch at iris.washington.edu (Manochehr Bahavar) Date: Thu, 22 Mar 2018 11:09:52 -0700 Subject: [Paraview] scipy and Windows ParaView 5.5.0 In-Reply-To: References: Message-ID: <64B9B6BB-BF9C-414D-9B7D-E8CED28F3F5A@iris.washington.edu> Hi Shawn, Many thanks for your detailed response. I really appreciate it and will give it a try. Thanks again, ?manoch > On Mar 22, 2018, at 10:51 AM, Shawn Waldon wrote: > > Hi Manoch, > > ParaView doesn't package scipy on Windows because compiling it (so we know it works with our Python) is extremely difficult. > > What you may be able to do is this: > -Install Python 2.7.X on your system > -Use pip install scipy to install the python wheels from PYPI > -One of the following: > ---put the location that scipy is installed in your PYTHONPATH before you run ParaView > ---Prepend the location that scipy was installed to your sys.path right after starting ParaView > ---Copy the scipy folder from the location it was installed into $PARAVIEW_INSTALL\bin\Lib\site-packages > > Keep in mind that this may not work. We use a slightly older version of Python 2.7 and I don't know if it maintained ABI compatibility. > You may also run into conflicts with numpy since ParaView's numpy was not compiled with the fortran support that scipy needs. > > HTH, > Shawn > > On Thu, Mar 22, 2018 at 12:10 PM, Manochehr Bahavar > wrote: > Hello, > > I have developed a few Python Programable filters using ParaView 5.5.0 on Mac. Now that I am trying to use them on Windows platform, using ParaView 5.5.0, I get an error that scipy module is not available!! Any suggestions on how I may address this? > > > Thanks, > > ?manoch > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From salachoris1 at gmail.com Thu Mar 22 14:14:14 2018 From: salachoris1 at gmail.com (GeorgeP S) Date: Thu, 22 Mar 2018 19:14:14 +0100 Subject: [Paraview] VRML animation Message-ID: Hello all, i would like to ask how is it possible to export in vrml but retain the animation acquired from the models simulation.Is there a specific feature that i have not found out yet about this kind of thing? Thank you! Mail priva di virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Mar 22 17:21:33 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 22 Mar 2018 15:21:33 -0600 Subject: [Paraview] immediate update In-Reply-To: References: Message-ID: In the latest version of ParaViewWeb, I've added the Native implementation of it while the other one was React only. Divvy is the application that use the native one. https://github.com/Kitware/divvy/blob/master/Sources/scatterPlotManager.js#L134-L140 For the client, we initialize it like that: https://github.com/Kitware/divvy/blob/master/Sources/client.js#L27-L29 HTH, Seb On Thu, Mar 22, 2018 at 12:04 PM, Sgouros, Thomas wrote: > That makes sense. I'm using RemoteRenderer, like this: > > import RemoteRenderer from 'paraviewweb/src/NativeUI/ > Canvas/RemoteRenderer'; > ... > smartConnect.onConnectionReady((connection) => { > model.pvwClient = > ParaViewWebClient.createClient(connection, > [ > 'MouseHandler', > 'ViewPort', > 'ViewPortImageDelivery', > ], > amsProtocols); > const renderer = new RemoteRenderer(model.pvwClient); > ... > > When I look in my paraviewweb/src/NativeUI/Renderers directory, I don't > see VtkRenderer, only NativeImageRenderer and RemoteRendererStatsTable. I > see VtkRenderer in the other place, though. Are they the same? Do I use > them the same way as RemoteRenderer? > > Thank you, > > -Tom > > On Thu, Mar 22, 2018 at 1:03 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> ViewPortImageDelivery require the JS side to request a render >> while VtkImageDelivery allow the server to push the image without the >> client requesting it (self.getApplication().InvokeEvent('UpdateEvent')). >> >> VtkImageDelivery is used inside those components: >> https://github.com/Kitware/paraviewweb/tree/master/src/React >> /Renderers/VtkRenderer >> https://github.com/Kitware/paraviewweb/tree/master/src/Nativ >> eUI/Renderers/VtkRenderer >> >> Which renderer do you use and how do you set it up? >> >> Seb >> >> On Thu, Mar 22, 2018 at 6:38 AM, Sgouros, Thomas < >> thomas_sgouros at brown.edu> wrote: >> >>> Thank you, but that doesn't seem to change anything for me. Doing this >>> now: >>> >>> self.renderView1.Update() >>> self.getApplication().InvokeEvent('UpdateEvent') >>> >>> Am I understanding it right that this is communicating with one of the >>> ViewPort or ViewPortImageDelivery protocols? Should I be sure to include >>> one of the other built-in protocols? Right now, I use those two, plus >>> MouseHandler. >>> >>> Thank you, >>> >>> -Tom >>> >>> On Wed, Mar 21, 2018 at 11:45 PM, Sebastien Jourdain < >>> sebastien.jourdain at kitware.com> wrote: >>> >>>> On the server side you should do something like: >>>> https://github.com/Kitware/light-viz/blob/master/server/ligh >>>> t_viz_protocols.py#L252 >>>> >>>> On Wed, Mar 21, 2018 at 4:59 PM, Sgouros, Thomas < >>>> thomas_sgouros at brown.edu> wrote: >>>> >>>>> Hello all: >>>>> >>>>> How do you get the ParaViewWeb client to update the window without >>>>> clicking in it? I have some controls -- some buttons and sliders -- but >>>>> when I change them, the view doesn't update until I click in the view frame >>>>> and move slightly. >>>>> >>>>> Thank you, >>>>> >>>>> -Tom >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Thu Mar 22 17:55:12 2018 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Thu, 22 Mar 2018 17:55:12 -0400 Subject: [Paraview] XML plugin based on programmable filter with a slider In-Reply-To: References: Message-ID: Hello Alessandro: It may be possible but it's not obvious to me. I suspect I can use the ArrayListDomain xml element but I don't quite understand how it works. I also don't have time right now to dive into the PV source code. I do see from the Threshold filter: Perhaps someone from the Paraview development team can chime in on this issue? I'll be happy to add it once I understand how it actually works. Thanks, Shuhao On 2018-03-22 09:59 AM, Alessandro De Maio wrote: > Hello Shuhao, > thank you for your reply and for your really great job on the > pvpyfilter. I had already tried it and it's very useful. > But I'm looking for the possibility to automatically assign the slider > range (in this case the upper value will be enough) depending on > information about the input of the programmable filter (in this case the > number of blocks of a multiblock dataset) and not to set it hardcoded in > the xml as from your approach. I would like that, if I apply this filter to > a mbdataset with 5 blocks, the slider can choose an int value from 0 to 4, > and if I apply the same filter (without modifying xml) to another mbdataset > with 8 blocks the slider provides an int from 0 to 7. > > Cheers > > Alessandro > > PS With pvpyfilter is there the possibility of decide in the .py file the > order of the widgets in the property panel? It seems to me that the order > is random > > On Thu, Mar 22, 2018 at 12:39 AM, Shuhao Wu wrote: > >> Accidentally hit Reply instead of hit Reply list. The record is below: >> >> -------- Forwarded Message -------- >> Subject: Re: [Paraview] XML plugin based on programmable filter with a >> slider >> Date: Wed, 21 Mar 2018 19:38:40 -0400 >> From: Shuhao Wu >> To: Alessandro De Maio >> >> Hello Alessandro, >> >> I just published a library that allows you to do _just this_. See: >> https://github.com/shuhaowu/pvpyfilter >> >> The example covers exactly this and specifically you can use the property: >> >> double_slider = Double("double with slider", default=0.5, slider=[0.0, >> 1.0], help="double with slider between 0.0 and 1.0 and a default of 0.5") >> >> Let me know if the library works for you or if you encounter any bug as it >> is still early days for this library. >> >> Cheers, >> Shuhao >> >> On 2018-03-21 01:37 PM, Alessandro De Maio wrote: >>> Hello, >>> I'm trying to write a plugin based on a programmable filter in order to >>> extract a single block from a multiblockdataset (with a single level >> tree) >>> in input chosing it through a slider in the property panel. >>> I need help to automatically set the range of the slider (the higher >> limit >>> as the lower is always 0) as the number of blocks of the >> multiblockdataset >>> in input, but the XML ServerManager definition of the slider is not clear >>> enough for me. >>> >>> I'm trying to follow Utkarsh suggestion in >>> >>> https://public.kitware.com/pipermail/paraview/2009-March/011599.html >>> >>> but I'm missing how to recovery the number of blocks of the input of the >>> programmable filter and how to set it as the upper value of the slider >>> range. >>> >>> Thank you in advance for your kind help >>> >>> Alessandro >>> >>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensou >> rce/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: >> https://public.kitware.com/mailman/listinfo/paraview >> > From demaio.a at gmail.com Fri Mar 23 08:06:25 2018 From: demaio.a at gmail.com (Alessandro De Maio) Date: Fri, 23 Mar 2018 13:06:25 +0100 Subject: [Paraview] BUG in client-server remote rendering (also 5.5RC3) Message-ID: Hello, the step to reproduce this error are: 1) in the paraview Settings (Render View tab) set "Remote Render Threshold" = 0 2) launch a pvserver 3) launch a paraview session connecting to the server 4) in the paraview GUI create a second RenderView 5) in the second RenderView right click and Link Camera selecting the other RenderView (the two RenderViews have a linked Camera) 6) Close one of the two RenderViews The pvserver exit with this error: ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 874 vtkSocketCommunicator (0x1882e40): Tag mismatch: got 1, expecting 22222. ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx, line 1168 vtkPVSynchronizedRenderWindows (0x1cd30e0): Mismatch is render windows on different processes. Aborting for debugging purposes. The same error occurs also with Paraview-5.3.0 If rendering is done on the client (the first step is avoided and the dimension of an object to render is less than the Remote Render Thresholf) the error doesn't occurr. I've tried both with a Linux and Windows client but with a Linux server.. Thank you Alessandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 23 09:31:33 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 23 Mar 2018 09:31:33 -0400 Subject: [Paraview] BUG in client-server remote rendering (also 5.5RC3) In-Reply-To: References: Message-ID: Alessandro, Thanks for the bug report. I've posted this in our issue tracker. https://gitlab.kitware.com/paraview/paraview/issues/18077 Cory On Fri, Mar 23, 2018 at 8:06 AM, Alessandro De Maio wrote: > Hello, > the step to reproduce this error are: > > 1) in the paraview Settings (Render View tab) set "Remote Render > Threshold" = 0 > 2) launch a pvserver > 3) launch a paraview session connecting to the server > 4) in the paraview GUI create a second RenderView > 5) in the second RenderView right click and Link Camera selecting the > other RenderView (the two RenderViews have a linked Camera) > 6) Close one of the two RenderViews > > The pvserver exit with this error: > > ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash- > linux-shared-release_superbuild/build/superbuild/ > paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 874 > vtkSocketCommunicator (0x1882e40): Tag mismatch: got 1, expecting 22222. > > ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash- > linux-shared-release_superbuild/build/superbuild/ > paraview/src/ParaViewCore/ClientServerCore/Rendering/ > vtkPVSynchronizedRenderWindows.cxx, line 1168 > vtkPVSynchronizedRenderWindows (0x1cd30e0): Mismatch is render windows on > different processes. Aborting for debugging purposes. > > The same error occurs also with Paraview-5.3.0 > If rendering is done on the client (the first step is avoided and the > dimension of an object to render is less than the Remote Render Thresholf) > the error doesn't occurr. > > I've tried both with a Linux and Windows client but with a Linux server.. > > > Thank you > > Alessandro > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From art.bodrin at gmail.com Fri Mar 23 11:38:00 2018 From: art.bodrin at gmail.com (Artem Bodrin) Date: Fri, 23 Mar 2018 18:38:00 +0300 Subject: [Paraview] How to know that the filter was applied? Message-ID: Hello, dear community. Does anyone can help me with this question: I'd like to know, if a filter in a pipeline have already been applied/calculated. Maybe there are some observers exists (e.g. vtkSMPProgressObserver)? Or I have to dig into vtkDemandDrivenPipeline? The overall task is to modify some GUI elements depending on a pipeline execution state... Can anyone push me to a right direction please? From wascott at sandia.gov Fri Mar 23 16:14:26 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 23 Mar 2018 20:14:26 +0000 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: References: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> Message-ID: <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> Thanks Denis. I was able to open this state file up with 5.4.1, and 5.5.0-rc3. Both act the same ? they only read two timesteps. What version of ParaView actually read the three pvtu filesets? Alan From: denis cohen Date: Monday, March 19, 2018 at 4:49 AM To: W Scott Cc: "paraview at public.kitware.com" Subject: Re: [EXTERNAL] [Paraview] state file Hi Scott, Attach a small data set (sorry could not find smaller). The pvsm file was created when the directory had 2 pvtu. The directory has now 3 pvtu files. Still after loading the pvsm file I don't have the 3 pvtu files in paraview . Thanks for your help. Denis On Sat, Mar 17, 2018 at 12:57 AM, Scott, W Alan > wrote: Cory/Utkarsh, If a dataset grows, shouldn?t a state file open the new, whole dataset? Utkarsh, is this an artifact of your work with datasets that live within a directory? This is a bug, right? Dennis, Do you have a simple dataset, that is open, that I can attach to a bug report, assuming this really is a bug? Alan From: ParaView > on behalf of denis cohen > Date: Wednesday, March 14, 2018 at 3:36 AM To: "paraview at public.kitware.com" > Subject: [EXTERNAL] [Paraview] state file Hello, In past versions of paraview, opening a pvsm state file that read several pvtu files resulted in paraview opening all the pvtu files in that directory. Now it only opens the ones saved in the pvsm file. This is annoying when the number of files has increased (like during a long time dependent simulation) and when wanting to use the same pvsm state file. Any ways of getting around that? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Fri Mar 23 17:05:33 2018 From: denis.cohen at gmail.com (denis cohen) Date: Fri, 23 Mar 2018 22:05:33 +0100 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> References: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> Message-ID: Hi Alan, Earlier 4.x.x versions of Paraview were able to read the number of vtu files in the directory whether 2 or 1000 with the same pvsm file. Best, Denis On Fri, Mar 23, 2018 at 9:14 PM, Scott, W Alan wrote: > Thanks Denis. > > > > I was able to open this state file up with 5.4.1, and 5.5.0-rc3. Both act > the same ? they only read two timesteps. What version of ParaView actually > read the three pvtu filesets? > > > > Alan > > > > *From: *denis cohen > *Date: *Monday, March 19, 2018 at 4:49 AM > *To: *W Scott > *Cc: *"paraview at public.kitware.com" > *Subject: *Re: [EXTERNAL] [Paraview] state file > > > > Hi Scott, > > Attach a small data set (sorry could not find smaller). The pvsm file was > created when the directory had 2 pvtu. The directory has now 3 pvtu files. > > Still after loading the pvsm file I don't have the 3 pvtu files in > paraview . > > Thanks for your help. > > Denis > > > > On Sat, Mar 17, 2018 at 12:57 AM, Scott, W Alan > wrote: > > Cory/Utkarsh, > > If a dataset grows, shouldn?t a state file open the new, whole dataset? > Utkarsh, is this an artifact of your work with datasets that live within a > directory? This is a bug, right? > > > > Dennis, > > Do you have a simple dataset, that is open, that I can attach to a bug > report, assuming this really is a bug? > > > > Alan > > > > > > > > *From: *ParaView on behalf of denis > cohen > *Date: *Wednesday, March 14, 2018 at 3:36 AM > *To: *"paraview at public.kitware.com" > *Subject: *[EXTERNAL] [Paraview] state file > > > > Hello, > > In past versions of paraview, opening a pvsm state file that read several > pvtu files resulted in paraview opening all the pvtu files in that > directory. Now it only opens the ones saved in the pvsm file. This is > annoying when the number of files has increased (like during a long time > dependent simulation) and when wanting to use the same pvsm state file. Any > ways of getting around that? > > Thank you > > Denis > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 23 18:48:28 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 23 Mar 2018 22:48:28 +0000 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: References: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> Message-ID: <9E6857B4-4508-429C-A455-A3FE6B9BF8F4@sandia.gov> OK, I think I figured this one out. Thanks for the example, that helped. When you load the state file, it will load exactly what was saved. There is now an option in ParaView called File/ Reload Files. This will give you the option to load only what was in the state file, or ?find new files? that belong in this dataset. Click ?Find new files?. Note also that the time counter is 0 based ? thus, there are now three timesteps, 0, 1 and 2 (with the maxium being time step 2). So, I believe this is not a bug, but rather an issue with somewhat modified features. Alan From: denis cohen Date: Friday, March 23, 2018 at 3:05 PM To: W Scott Cc: "paraview at public.kitware.com" Subject: Re: [EXTERNAL] [Paraview] state file Hi Alan, Earlier 4.x.x versions of Paraview were able to read the number of vtu files in the directory whether 2 or 1000 with the same pvsm file. Best, Denis On Fri, Mar 23, 2018 at 9:14 PM, Scott, W Alan > wrote: Thanks Denis. I was able to open this state file up with 5.4.1, and 5.5.0-rc3. Both act the same ? they only read two timesteps. What version of ParaView actually read the three pvtu filesets? Alan From: denis cohen > Date: Monday, March 19, 2018 at 4:49 AM To: W Scott > Cc: "paraview at public.kitware.com" > Subject: Re: [EXTERNAL] [Paraview] state file Hi Scott, Attach a small data set (sorry could not find smaller). The pvsm file was created when the directory had 2 pvtu. The directory has now 3 pvtu files. Still after loading the pvsm file I don't have the 3 pvtu files in paraview . Thanks for your help. Denis On Sat, Mar 17, 2018 at 12:57 AM, Scott, W Alan > wrote: Cory/Utkarsh, If a dataset grows, shouldn?t a state file open the new, whole dataset? Utkarsh, is this an artifact of your work with datasets that live within a directory? This is a bug, right? Dennis, Do you have a simple dataset, that is open, that I can attach to a bug report, assuming this really is a bug? Alan From: ParaView > on behalf of denis cohen > Date: Wednesday, March 14, 2018 at 3:36 AM To: "paraview at public.kitware.com" > Subject: [EXTERNAL] [Paraview] state file Hello, In past versions of paraview, opening a pvsm state file that read several pvtu files resulted in paraview opening all the pvtu files in that directory. Now it only opens the ones saved in the pvsm file. This is annoying when the number of files has increased (like during a long time dependent simulation) and when wanting to use the same pvsm state file. Any ways of getting around that? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Fri Mar 23 19:58:32 2018 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Fri, 23 Mar 2018 19:58:32 -0400 Subject: [Paraview] XML plugin based on programmable filter with a slider In-Reply-To: References: Message-ID: <8fcd2296-fc8f-2d2e-0baa-99e6695d72a0@shuhaowu.com> I've implemented the ordering of the properties based on the order of definition within the class for all supported Python 3 versions. Let me know if it works for you. Cheers, Shuhao On 2018-03-22 05:55 PM, Shuhao Wu wrote: > Hello Alessandro: > > It may be possible but it's not obvious to me. I suspect I can use the > ArrayListDomain xml element but I don't quite understand how it works. I > also don't have time right now to dive into the PV source code. > > I do see from the Threshold filter: > > ????? ??????????????????????????? default_values="0 0" > ??????????????????????????? label="Threshold Range" > ??????????????????????????? name="ThresholdBetween" > ??????????????????????????? number_of_elements="2" > ??????????????????????????? panel_widget="double_range"> > ??????? > ????????? > ??????????? ????????????????????? name="Input" /> > ??????????? ????????????????????? name="SelectInputScalars" /> > ????????? > ??????? > ????? > > Perhaps someone from the Paraview development team can chime in on this > issue? I'll be happy to add it once I understand how it actually works. > > Thanks, > Shuhao > > On 2018-03-22 09:59 AM, Alessandro De Maio wrote: >> Hello? Shuhao, >> ??? thank you for your reply and for your really great job on the >> pvpyfilter. I had already tried it and it's very useful. >> But I'm looking for the possibility to automatically assign the slider >> range (in this case the upper value will be enough) depending on >> information about the input of the programmable filter (in this case the >> number of blocks of a multiblock dataset) and not to set it hardcoded in >> the xml as from your approach. I would like that, if I apply this >> filter to >> a mbdataset with 5 blocks, the slider can choose an int value from 0 >> to 4, >> and if I apply the same filter (without modifying xml) to another >> mbdataset >> with 8 blocks the slider provides an int from 0 to 7. >> >> Cheers >> >> Alessandro >> >> PS With pvpyfilter is there the possibility of decide in the .py file the >> order of the widgets in the property panel? It seems to me that the order >> is random >> >> On Thu, Mar 22, 2018 at 12:39 AM, Shuhao Wu wrote: >> >>> Accidentally hit Reply instead of hit Reply list. The record is below: >>> >>> -------- Forwarded Message -------- >>> Subject: Re: [Paraview] XML plugin based on programmable filter with a >>> slider >>> Date: Wed, 21 Mar 2018 19:38:40 -0400 >>> From: Shuhao Wu >>> To: Alessandro De Maio >>> >>> Hello Alessandro, >>> >>> I just published a library that allows you to do _just this_. See: >>> https://github.com/shuhaowu/pvpyfilter >>> >>> The example covers exactly this and specifically you can use the >>> property: >>> >>> double_slider = Double("double with slider", default=0.5, slider=[0.0, >>> 1.0], help="double with slider between 0.0 and 1.0 and a default of >>> 0.5") >>> >>> Let me know if the library works for you or if you encounter any bug >>> as it >>> is still early days for this library. >>> >>> Cheers, >>> Shuhao >>> >>> On 2018-03-21 01:37 PM, Alessandro De Maio wrote: >>>> Hello, >>>> I'm trying to write a plugin based on a programmable filter in order to >>>> extract a single block from a multiblockdataset (with a single level >>> tree) >>>> in input chosing it through a slider in the property panel. >>>> I need help to automatically set the range of the slider (the higher >>> limit >>>> as the lower is always 0) as the number of blocks of the >>> multiblockdataset >>>> in input, but the XML ServerManager definition of the slider is not >>>> clear >>>> enough for me. >>>> >>>> I'm trying to follow Utkarsh suggestion in >>>> >>>> https://public.kitware.com/pipermail/paraview/2009-March/011599.html >>>> >>>> but I'm missing how to recovery the number of blocks of the input of >>>> the >>>> programmable filter and how to set it as the upper value of the slider >>>> range. >>>> >>>> Thank you in advance for your kind help >>>> >>>> Alessandro >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensou >>> rce/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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >> From utkarsh.ayachit at kitware.com Mon Mar 26 10:14:04 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 26 Mar 2018 10:14:04 -0400 Subject: [Paraview] How to know that the filter was applied? In-Reply-To: References: Message-ID: There's no such thing as "already applied", since even an already applied filter may be re-executed if a filter downstream makes a different request. Whenever a filter is executed, however, `pqPipelineSource::dataUpdated` signal is fired. You can look at the implementation of this signal to see that it's connected to `vtkCommand::DataUpdateEvent` event fired by the vtkSMSourceProxy. Hopefully that helps. Utkarsh On Fri, Mar 23, 2018 at 11:38 AM, Artem Bodrin wrote: > Hello, dear community. > > Does anyone can help me with this question: I'd like to know, if a filter in a pipeline have already been applied/calculated. Maybe there are some observers exists (e.g. vtkSMPProgressObserver)? Or I have to dig into vtkDemandDrivenPipeline? > > The overall task is to modify some GUI elements depending on a pipeline execution state... > > Can anyone push me to a right direction please? > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview From art.bodrin at gmail.com Mon Mar 26 10:18:49 2018 From: art.bodrin at gmail.com (Artem Bodrin) Date: Mon, 26 Mar 2018 17:18:49 +0300 Subject: [Paraview] How to know that the filter was applied? In-Reply-To: References: Message-ID: <20F6A5F1-CB3F-4F28-8C9A-EC35DCCCD107@gmail.com> Hello, Utkarsh Yes, connecting to that signal might do the trick. Thank you very much for a tip :-) > 26 ????? 2018 ?., ? 17:14, Utkarsh Ayachit ???????(?): > > There's no such thing as "already applied", since even an already > applied filter may be re-executed if a filter downstream makes a > different request. Whenever a filter is executed, however, > `pqPipelineSource::dataUpdated` signal is fired. You can look at the > implementation of this signal to see that it's connected to > `vtkCommand::DataUpdateEvent` event fired by the vtkSMSourceProxy. > > Hopefully that helps. > > Utkarsh > From mbeshr1986 at gmail.com Mon Mar 26 10:45:29 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Mon, 26 Mar 2018 10:45:29 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs Message-ID: I have few questions/requests based on my work with Paraview to display CFD data: 1. I tried to use the caching option for the mesh that I had and it works fine when I select ?Snap To TimeSteps? option. This is good. However, a. When I select ?Real Time? option and increase the time, even though it is cached, it still keeps reloading which prevents the VR from working. Is there any potential/possibility to fix this in the meantime or upcoming release? b. When I cache it as a volume (rather than surface, wireframe, or points) on my laptop, it crashed the exe even when I increase the cache memory maximum size. Any thoughts on that? I tested it on a bigger and faster work station and it worked, however, it still has the issue mentioned in the point below. 2. When I get a smaller mesh (4x smaller), I am able to cache it as a volume. However, when playing it back, it keeps reloading while showing the green bar as below at each time step. Is that supposed to happen? Is that rendering? Is there a way to eliminate it or make it faster? Thanks a lot. -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 278391 bytes Desc: not available URL: From carlosemanglanov at gmail.com Mon Mar 26 10:47:50 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 16:47:50 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution Message-ID: Hi everyone! When I postprocess some simulations, less than 900,000 cells, from openfoam, either opening paraview directly or using the parafoam tool, the program crashes giving me the following error message: I/O : uncollated terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. My OS is Ubuntu 16.04, freshly installed. I was getting the same error with Ubuntu 17.10 which I had installed until last night. I am looking for info about "reimplementing QApplication" with no luck. Any suggestions, please? Carlos -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Mon Mar 26 10:51:47 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 26 Mar 2018 10:51:47 -0400 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Hi Carlos, That error message means that an exception was thrown from a Qt event handler. The message about reimplementing QApplication::notify() is just to tell you how to catch the exception if you wanted to. The real problem is the exception. A std::bad_alloc exception happens when the program tries to allocate memory and fails. So you need to figure out why you are running out of memory (that is the most likely cause of the error). HTH, Shawn On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com> wrote: > Hi everyone! > > When I postprocess some simulations, less than 900,000 cells, from > openfoam, either opening paraview directly or using the parafoam tool, the > program crashes giving me the following error message: > > I/O : uncollated > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > Qt has caught an exception thrown from an event handler. Throwing > exceptions from an event handler is not supported in Qt. You must > reimplement QApplication::notify() and catch all exceptions there. > > My OS is Ubuntu 16.04, freshly installed. I was getting the same error > with Ubuntu 17.10 which I had installed until last night. > > I am looking for info about "reimplementing QApplication" with no luck. > > Any suggestions, please? > Carlos > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 10:58:04 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 16:58:04 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Thanks Shawn, I'll try to figure it out, and come back with any updates. Carlos 2018-03-26 16:51 GMT+02:00 Shawn Waldon : > Hi Carlos, > > That error message means that an exception was thrown from a Qt event > handler. The message about reimplementing QApplication::notify() is just > to tell you how to catch the exception if you wanted to. The real problem > is the exception. > > A std::bad_alloc exception happens when the program tries to allocate > memory and fails. So you need to figure out why you are running out of > memory (that is the most likely cause of the error). > > HTH, > Shawn > > On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com> wrote: > >> Hi everyone! >> >> When I postprocess some simulations, less than 900,000 cells, from >> openfoam, either opening paraview directly or using the parafoam tool, the >> program crashes giving me the following error message: >> >> I/O : uncollated >> terminate called after throwing an instance of 'std::bad_alloc' >> what(): std::bad_alloc >> Qt has caught an exception thrown from an event handler. Throwing >> exceptions from an event handler is not supported in Qt. You must >> reimplement QApplication::notify() and catch all exceptions there. >> >> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >> with Ubuntu 17.10 which I had installed until last night. >> >> I am looking for info about "reimplementing QApplication" with no luck. >> >> Any suggestions, please? >> Carlos >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamil.goettlich at gmail.com Mon Mar 26 10:59:35 2018 From: jamil.goettlich at gmail.com (Jamil Goettlich) Date: Mon, 26 Mar 2018 16:59:35 +0200 Subject: [Paraview] ParaView-Superbuild Win10 Errors Message-ID: Hello, I am having Problems building ParaView with ParaView-Superbuild. As Visual Studio is not supported, I tried other build systems and compilers. Unfortunately none of them succeeded. On the other hand I was able to build small HelloWord programs with each of the combinations listed below and without any errors. Here is what I did: First, I cloned from git: git clone --recursive https://gitlab.kitware.com/paraview/paraview-superbuild.git Then cd paraview-superbuild and created new folder (build). The following cases did not work out (Doesnt matter if using Git Bash or VS Command Prompt): Build System: Ninja, Compiler: MinGW command: cmake .. -G "Ninja" Error: CMake Error at superbuild/projects/win32/boost.cmake:5 (message): At least Visual Studio 9.0 is required Call Stack (most recent call first): superbuild/cmake/SuperbuildMacros.cmake:477 (include) superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) Although I have Visual Studio 15 2017 installed it does not seem to work. Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64) Error: The C compiler "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" is not able to compile a simple test program. It fails with the following output: Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f CMakeFiles\cmTC_008b4.dir\build.make /nologo -L CMakeFiles\cmTC_008b4.dir\build Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp testCCompiler.c C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: fatal error C1001: An internal error has occurred in the compiler. (compiler file 'msc1.cpp', line 1507) To work around this problem, try simplifying or changing the program near the locations listed above. Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be prompted to send an error report to Microsoft later. NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' : return code '0x2' Stop. Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64) Here, cmake recognized the compiler, but it throws another error Error: CMake Error at C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeDetermineRCCompiler.cmake:20 (message): Could not find compiler set in environment variable RC: rc. Call Stack (most recent call first): C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC.cmake:323 (enable_language) C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeCInformation.cmake:48 (include) CMakeLists.txt:3 (project) CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage I am out of ideas now. I would be really happy for a detailed build description as I am sure I did not understand something properly. And every hint on how to resolve on of those errors is very welcome too. Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Mon Mar 26 11:21:03 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 26 Mar 2018 11:21:03 -0400 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: Hi Jamil, I'm not sure if this will get you all the way to a build, but here are some pointers: We build with the visual studio compiler but use the Ninja generator since it is significantly faster than VS. VS 2017 may not work. Our binaries are built with 2013 right now and we plan to move to 2015 after the current release cycle. If you want what you are building to be compatible with the Kitware binaries, you will need to use 2013. Also, I believe there are compiler errors if you use 2017 right now. To build with Ninja and VS compilers, you need to be in a visual studio command prompt rather than a normal shell (it sets a bunch of environment vars, which I think is what is missing in your last example). To convert a normal command prompt you run (example is for VS2015, your path may differ) 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64' in your shell and it will set the environment variables for you. If you have the environment set up before running cmake -G Ninja it should just pick the right compiler. HTH, Shawn On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich wrote: > Hello, > > I am having Problems building ParaView with ParaView-Superbuild. As Visual > Studio is not supported, I tried other build systems and compilers. > Unfortunately none of them succeeded. On the other hand I was able to build > small HelloWord programs with each of the combinations listed below and > without any errors. Here is what I did: > > First, I cloned from git: > git clone --recursive https://gitlab.kitware.com/ > paraview/paraview-superbuild.git > Then cd paraview-superbuild and created new folder (build). > > The following cases did not work out (Doesnt matter if using Git Bash or > VS Command Prompt): > Build System: Ninja, Compiler: MinGW > command: cmake .. -G "Ninja" > Error: > CMake Error at superbuild/projects/win32/boost.cmake:5 (message): > At least Visual Studio 9.0 is required > Call Stack (most recent call first): > superbuild/cmake/SuperbuildMacros.cmake:477 (include) > superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) > > Although I have Visual Studio 15 2017 installed it does not seem to work. > > Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program Files > (x86)\Microsoft Visual Studio\2017\Community\VC\ > Tools\MSVC\14.12.25827\bin\Hostx64\x64) > Error: > > The C compiler > "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/ > Tools/MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" > is not able to compile a simple test program. > It fails with the following output: > Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp > Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" > "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\ > Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f > CMakeFiles\cmTC_008b4.dir\build.make /nologo -L CMakeFiles\cmTC_008b4.dir\ > build > > Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj > > C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe > @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp > > testCCompiler.c > > C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: > fatal error C1001: An internal error has occurred in the compiler. > > (compiler file 'msc1.cpp', line 1507) > > To work around this problem, try simplifying or changing the program near > the locations listed above. > > Please choose the Technical Support command on the Visual C++ > > Help menu, or open the Technical Support help file for more information > > Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\ > COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be > prompted to send an error report to Microsoft later. > > NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\ > COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code > '0x2' > > Stop. > > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' > : return code '0x2' > > Stop. > > > Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program Files > (x86)\Microsoft Visual Studio\2017\Community\VC\ > Tools\MSVC\14.12.25827\bin\Hostx64\x64) > > Here, cmake recognized the compiler, but it throws another error > Error: > > CMake Error at C:/Program Files/CMake/share/cmake-3.10/Modules/ > CMakeDetermineRCCompiler.cmake:20 (message): > Could not find compiler set in environment variable RC: > rc. > Call Stack (most recent call first): > C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC.cmake:323 > (enable_language) > C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC-C.cmake:5 > (__windows_compiler_msvc) > C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeCInformation.cmake:48 > (include) > CMakeLists.txt:3 (project) > > CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage > > > I am out of ideas now. > I would be really happy for a detailed build description as I am sure I > did not understand something properly. > > And every hint on how to resolve on of those errors is very welcome too. > > > Thanks in advance! > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbeshr1986 at gmail.com Mon Mar 26 11:24:34 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Mon, 26 Mar 2018 11:24:34 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs Message-ID: I have few questions/requests based on my work with Paraview to display CFD data: 1. I tried to use the caching option for the mesh that I had and it works fine when I select ?Snap To TimeSteps? option. This is good. However, a. When I select ?Real Time? option and increase the time, even though it is cached, it still keeps reloading which prevents the VR from working. Is there any potential/possibility to fix this in the meantime or upcoming release? b. When I cache it as a volume (rather than surface, wireframe, or points) on my laptop, it crashed the exe even when I increase the cache memory maximum size. Any thoughts on that? I tested it on a bigger and faster work station and it worked, however, it still has the issue mentioned in the point below. 2. When I get a smaller mesh (4x smaller), I am able to cache it as a volume. However, when playing it back, it keeps reloading while showing the green bar as below at each time step. Is that supposed to happen? Is that rendering? Is there a way to eliminate it or make it faster? Thanks a lot. -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 278391 bytes Desc: not available URL: From carlosemanglanov at gmail.com Mon Mar 26 11:25:30 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 17:25:30 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Problem solved!!! I opened my tower, fiddled around the memory sticks, and I can use paraview with no problems. At least recreating the steps that have been giving me problems since last week. Thanks for your time Shawn!! Carlos 2018-03-26 16:58 GMT+02:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > Thanks Shawn, > > I'll try to figure it out, and come back with any updates. > > Carlos > > 2018-03-26 16:51 GMT+02:00 Shawn Waldon : > >> Hi Carlos, >> >> That error message means that an exception was thrown from a Qt event >> handler. The message about reimplementing QApplication::notify() is just >> to tell you how to catch the exception if you wanted to. The real problem >> is the exception. >> >> A std::bad_alloc exception happens when the program tries to allocate >> memory and fails. So you need to figure out why you are running out of >> memory (that is the most likely cause of the error). >> >> HTH, >> Shawn >> >> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com> wrote: >> >>> Hi everyone! >>> >>> When I postprocess some simulations, less than 900,000 cells, from >>> openfoam, either opening paraview directly or using the parafoam tool, the >>> program crashes giving me the following error message: >>> >>> I/O : uncollated >>> terminate called after throwing an instance of 'std::bad_alloc' >>> what(): std::bad_alloc >>> Qt has caught an exception thrown from an event handler. Throwing >>> exceptions from an event handler is not supported in Qt. You must >>> reimplement QApplication::notify() and catch all exceptions there. >>> >>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>> with Ubuntu 17.10 which I had installed until last night. >>> >>> I am looking for info about "reimplementing QApplication" with no luck. >>> >>> Any suggestions, please? >>> Carlos >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 14:29:37 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 20:29:37 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: It's me again, I'm sorry, Problem NOT solved!!! ... Hardware looks ok, software and system handling memory looks good too. ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" option selected, before and after clipping ... possible bug?? C. 2018-03-26 16:51 GMT+02:00 Shawn Waldon : > Hi Carlos, > > That error message means that an exception was thrown from a Qt event > handler. The message about reimplementing QApplication::notify() is just > to tell you how to catch the exception if you wanted to. The real problem > is the exception. > > A std::bad_alloc exception happens when the program tries to allocate > memory and fails. So you need to figure out why you are running out of > memory (that is the most likely cause of the error). > > HTH, > Shawn > > On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com> wrote: > >> Hi everyone! >> >> When I postprocess some simulations, less than 900,000 cells, from >> openfoam, either opening paraview directly or using the parafoam tool, the >> program crashes giving me the following error message: >> >> I/O : uncollated >> terminate called after throwing an instance of 'std::bad_alloc' >> what(): std::bad_alloc >> Qt has caught an exception thrown from an event handler. Throwing >> exceptions from an event handler is not supported in Qt. You must >> reimplement QApplication::notify() and catch all exceptions there. >> >> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >> with Ubuntu 17.10 which I had installed until last night. >> >> I am looking for info about "reimplementing QApplication" with no luck. >> >> Any suggestions, please? >> Carlos >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Mar 26 14:36:32 2018 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 26 Mar 2018 14:36:32 -0400 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Carlos, OpenFOAM can produce cells with non planar faces which is not handled by VTK/ParaView. Moreover it appears that current reader implementation can also produce incorrect cells when reading wedge cells. Thanks to a recent rewriting of the polydron clipping algorithm, the clipping/slicing of polyhedron should no more lead to crashes. However,the problems of non planar faces might produce some holes in the result. We are currently working on a patch to better handle this case in the reader. If you want to try the new polyhedron clipping algorithm, you will have to use ParaView >= 5.5 RC1. Best regards, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > It's me again, I'm sorry, > > Problem NOT solved!!! ... Hardware looks ok, software and system handling > memory looks good too. > > ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" > option selected, before and after clipping ... > > possible bug?? > > C. > > 2018-03-26 16:51 GMT+02:00 Shawn Waldon : > >> Hi Carlos, >> >> That error message means that an exception was thrown from a Qt event >> handler. The message about reimplementing QApplication::notify() is just >> to tell you how to catch the exception if you wanted to. The real problem >> is the exception. >> >> A std::bad_alloc exception happens when the program tries to allocate >> memory and fails. So you need to figure out why you are running out of >> memory (that is the most likely cause of the error). >> >> HTH, >> Shawn >> >> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com> wrote: >> >>> Hi everyone! >>> >>> When I postprocess some simulations, less than 900,000 cells, from >>> openfoam, either opening paraview directly or using the parafoam tool, the >>> program crashes giving me the following error message: >>> >>> I/O : uncollated >>> terminate called after throwing an instance of 'std::bad_alloc' >>> what(): std::bad_alloc >>> Qt has caught an exception thrown from an event handler. Throwing >>> exceptions from an event handler is not supported in Qt. You must >>> reimplement QApplication::notify() and catch all exceptions there. >>> >>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>> with Ubuntu 17.10 which I had installed until last night. >>> >>> I am looking for info about "reimplementing QApplication" with no luck. >>> >>> Any suggestions, please? >>> Carlos >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 26 14:39:26 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 26 Mar 2018 18:39:26 +0000 Subject: [Paraview] [EXTERNAL] Re: Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Hi Carlos, As Shawn says, you are running out of memory. As a guess, this isn?t a hardware issue or ParaView issue, but rather a ?too much data in a 5 pound bag? issue. Here are some thoughts: * Run View/ Memory Inspector. As you do stuff, watch memory grow. Does it look like memory is growing until PV dies? * Minimize the size of your dataset. Although you only have a million cells (rounding), how many variables to you have? Don?t load (or don?t create) variables that you don?t need. * How many blocks do you have? If the answer is lots (hundreds?), I believe this creates memory pressure. * Do you have sidesets/ edgesets? Don?t load these unless needed (as you can see, I don?t know openfoam). * Run top. How big is ParaView getting? * Try opening your data with no variables loaded. What is the memory inspector doing? * How much hardware do you have on your computer? If it?s a new computer with 8 GBytes, that is very different than an old converted machine with .25GBytes. * Try looking at your memory footprint (memory inspector, top) BEFORE applying filters. Every filter you use increases memory. * Use filters such as slice (i.e., 2d) rather than clip (3d), and contour (2d) rather than clip by scalar. What I mean here is to create a surface, rather than a solid. Surfaces use less memory. * Don?t volume render. It really sucks memory. That?s what I can think of... Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Carlos E Manglano-Villamarin Sent: Monday, March 26, 2018 12:30 PM To: Waldon, Shawn (External Contacts) Cc: paraview at public.kitware.com Subject: [EXTERNAL] Re: [Paraview] Paraview crashing when clipping an openfoam solution It's me again, I'm sorry, Problem NOT solved!!! ... Hardware looks ok, software and system handling memory looks good too. ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" option selected, before and after clipping ... possible bug?? C. 2018-03-26 16:51 GMT+02:00 Shawn Waldon >: Hi Carlos, That error message means that an exception was thrown from a Qt event handler. The message about reimplementing QApplication::notify() is just to tell you how to catch the exception if you wanted to. The real problem is the exception. A std::bad_alloc exception happens when the program tries to allocate memory and fails. So you need to figure out why you are running out of memory (that is the most likely cause of the error). HTH, Shawn On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin > wrote: Hi everyone! When I postprocess some simulations, less than 900,000 cells, from openfoam, either opening paraview directly or using the parafoam tool, the program crashes giving me the following error message: I/O : uncollated terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. My OS is Ubuntu 16.04, freshly installed. I was getting the same error with Ubuntu 17.10 which I had installed until last night. I am looking for info about "reimplementing QApplication" with no luck. Any suggestions, please? Carlos _______________________________________________ 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: https://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 15:04:27 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 21:04:27 +0200 Subject: [Paraview] [EXTERNAL] Re: Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: > > > - Run View/ Memory Inspector. As you do stuff, watch memory grow. > Does it look like memory is growing until PV dies? *Starting with > 53.6% of RAM free, no swapping.* > > > - Minimize the size of your dataset. Although you only have a million > cells (rounding), how many variables to you have? Don?t load (or don?t > create) variables that you don?t need. *410175 cells, and loading 'p' > and 'U' only* > > > - How many blocks do you have? If the answer is lots (hundreds?), I > believe this creates memory pressure. *blocks? I guess the answer is: > just one block. I reconstruct latestTime after simulation* > > > - Do you have sidesets/ edgesets? Don?t load these unless needed (as > you can see, I don?t know openfoam). *No sets loaded* > > > - Run top. How big is ParaView getting? *Starts with 3.8%. Then it > goes up to 10.4% when loading the *.OpenFOAM file (statistics information > says 82MB) And, system monitor says PV is using 448.4MB. **When I > create a clip, the memory used by PV, as said by System Monitor, goes up to > 519.7MB. Top says PV is using 11.6% of memory.* > > > - Try opening your data with no variables loaded. What is the memory > inspector doing? *System Monitor shows 63.8MB used by paraview before > loading foam case. And, 336.2MB when loading the case with no variables, > just the internalMesh.* > > > - How much hardware do you have on your computer? If it?s a new > computer with 8 GBytes, that is very different than an old converted > machine with .25GBytes. *Motherboard 9 year old computer with 6GB of > RAM, which have not given me ANY problem until last few days.* > > > - Try looking at your memory footprint (memory inspector, top) BEFORE > applying filters. Every filter you use increases memory. *Memory > footprint doesn't increase dangerously.* > > > - Use filters such as slice (i.e., 2d) rather than clip (3d), and > contour (2d) rather than clip by scalar. What I mean here is to create a > surface, rather than a solid. Surfaces use less memory. *That's a > good walk around, thanks!* > > > - Don?t volume render. It really sucks memory. *Volume render? You > mean, like 'streamlines'?* > > *Thank very much Shawn!!! i really appreciate your help.* > Carlos -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 15:04:59 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 21:04:59 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Thanks Joachim, I'll give it a go! C. 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux : > Carlos, > > OpenFOAM can produce cells with non planar faces which is not handled by > VTK/ParaView. Moreover it appears that current reader implementation can > also produce incorrect cells when reading wedge cells. > Thanks to a recent rewriting of the polydron clipping algorithm, the > clipping/slicing of polyhedron should no more lead to crashes. However,the > problems > of non planar faces might produce some holes in the result. > We are currently working on a patch to better handle this case in the > reader. > If you want to try the new polyhedron clipping algorithm, you will have > to use ParaView >= 5.5 RC1. > > Best regards, > Joachim > > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com>: > >> It's me again, I'm sorry, >> >> Problem NOT solved!!! ... Hardware looks ok, software and system handling >> memory looks good too. >> >> ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" >> option selected, before and after clipping ... >> >> possible bug?? >> >> C. >> >> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >> >>> Hi Carlos, >>> >>> That error message means that an exception was thrown from a Qt event >>> handler. The message about reimplementing QApplication::notify() is just >>> to tell you how to catch the exception if you wanted to. The real problem >>> is the exception. >>> >>> A std::bad_alloc exception happens when the program tries to allocate >>> memory and fails. So you need to figure out why you are running out of >>> memory (that is the most likely cause of the error). >>> >>> HTH, >>> Shawn >>> >>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>> carlosemanglanov at gmail.com> wrote: >>> >>>> Hi everyone! >>>> >>>> When I postprocess some simulations, less than 900,000 cells, from >>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>> program crashes giving me the following error message: >>>> >>>> I/O : uncollated >>>> terminate called after throwing an instance of 'std::bad_alloc' >>>> what(): std::bad_alloc >>>> Qt has caught an exception thrown from an event handler. Throwing >>>> exceptions from an event handler is not supported in Qt. You must >>>> reimplement QApplication::notify() and catch all exceptions there. >>>> >>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>>> with Ubuntu 17.10 which I had installed until last night. >>>> >>>> I am looking for info about "reimplementing QApplication" with no luck. >>>> >>>> Any suggestions, please? >>>> Carlos >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Mar 26 15:07:26 2018 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 26 Mar 2018 15:07:26 -0400 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Carlos, For information, here is the merge request that address the wedge issue: https://gitlab.kitware.com/vtk/vtk/merge_requests/4059 This is a simple patch for now, better solution will come. Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > Thanks Joachim, > > I'll give it a go! > > C. > > 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < > joachim.pouderoux at kitware.com>: > >> Carlos, >> >> OpenFOAM can produce cells with non planar faces which is not handled by >> VTK/ParaView. Moreover it appears that current reader implementation can >> also produce incorrect cells when reading wedge cells. >> Thanks to a recent rewriting of the polydron clipping algorithm, the >> clipping/slicing of polyhedron should no more lead to crashes. However,the >> problems >> of non planar faces might produce some holes in the result. >> We are currently working on a patch to better handle this case in the >> reader. >> If you want to try the new polyhedron clipping algorithm, you will have >> to use ParaView >= 5.5 RC1. >> >> Best regards, >> Joachim >> >> >> *Joachim Pouderoux*, PhD >> >> *Technical Expert - Scientific Computing Team* >> *Kitware SAS * >> >> >> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com>: >> >>> It's me again, I'm sorry, >>> >>> Problem NOT solved!!! ... Hardware looks ok, software and system >>> handling memory looks good too. >>> >>> ParaView shuts down if I try to generate a clip with the "VTK >>> Polyhedron" option selected, before and after clipping ... >>> >>> possible bug?? >>> >>> C. >>> >>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>> >>>> Hi Carlos, >>>> >>>> That error message means that an exception was thrown from a Qt event >>>> handler. The message about reimplementing QApplication::notify() is just >>>> to tell you how to catch the exception if you wanted to. The real problem >>>> is the exception. >>>> >>>> A std::bad_alloc exception happens when the program tries to allocate >>>> memory and fails. So you need to figure out why you are running out of >>>> memory (that is the most likely cause of the error). >>>> >>>> HTH, >>>> Shawn >>>> >>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>> carlosemanglanov at gmail.com> wrote: >>>> >>>>> Hi everyone! >>>>> >>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>> program crashes giving me the following error message: >>>>> >>>>> I/O : uncollated >>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>> what(): std::bad_alloc >>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>> exceptions from an event handler is not supported in Qt. You must >>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>> >>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>>>> with Ubuntu 17.10 which I had installed until last night. >>>>> >>>>> I am looking for info about "reimplementing QApplication" with no luck. >>>>> >>>>> Any suggestions, please? >>>>> Carlos >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 15:09:31 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 21:09:31 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Thanks! 2018-03-26 21:07 GMT+02:00 Joachim Pouderoux : > Carlos, > > For information, here is the merge request that address the wedge issue: > https://gitlab.kitware.com/vtk/vtk/merge_requests/4059 > This is a simple patch for now, better solution will come. > > Joachim > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com>: > >> Thanks Joachim, >> >> I'll give it a go! >> >> C. >> >> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < >> joachim.pouderoux at kitware.com>: >> >>> Carlos, >>> >>> OpenFOAM can produce cells with non planar faces which is not handled by >>> VTK/ParaView. Moreover it appears that current reader implementation can >>> also produce incorrect cells when reading wedge cells. >>> Thanks to a recent rewriting of the polydron clipping algorithm, the >>> clipping/slicing of polyhedron should no more lead to crashes. However,the >>> problems >>> of non planar faces might produce some holes in the result. >>> We are currently working on a patch to better handle this case in the >>> reader. >>> If you want to try the new polyhedron clipping algorithm, you will have >>> to use ParaView >= 5.5 RC1. >>> >>> Best regards, >>> Joachim >>> >>> >>> *Joachim Pouderoux*, PhD >>> >>> *Technical Expert - Scientific Computing Team* >>> *Kitware SAS * >>> >>> >>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >>> carlosemanglanov at gmail.com>: >>> >>>> It's me again, I'm sorry, >>>> >>>> Problem NOT solved!!! ... Hardware looks ok, software and system >>>> handling memory looks good too. >>>> >>>> ParaView shuts down if I try to generate a clip with the "VTK >>>> Polyhedron" option selected, before and after clipping ... >>>> >>>> possible bug?? >>>> >>>> C. >>>> >>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>> >>>>> Hi Carlos, >>>>> >>>>> That error message means that an exception was thrown from a Qt event >>>>> handler. The message about reimplementing QApplication::notify() is just >>>>> to tell you how to catch the exception if you wanted to. The real problem >>>>> is the exception. >>>>> >>>>> A std::bad_alloc exception happens when the program tries to allocate >>>>> memory and fails. So you need to figure out why you are running out of >>>>> memory (that is the most likely cause of the error). >>>>> >>>>> HTH, >>>>> Shawn >>>>> >>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>>> carlosemanglanov at gmail.com> wrote: >>>>> >>>>>> Hi everyone! >>>>>> >>>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>>> program crashes giving me the following error message: >>>>>> >>>>>> I/O : uncollated >>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>> what(): std::bad_alloc >>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>> >>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same >>>>>> error with Ubuntu 17.10 which I had installed until last night. >>>>>> >>>>>> I am looking for info about "reimplementing QApplication" with no >>>>>> luck. >>>>>> >>>>>> Any suggestions, please? >>>>>> Carlos >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 15:14:54 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 21:14:54 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Quite interestingly, I have just create a 2D slice in a mesh with 947443 cells, and it has not crashed!! It is showing the "holes" you mentioned before, though. This is puzzling me, some meshes make PV to crash, and others just show the bug you mentiones :-/ C. 2018-03-26 21:07 GMT+02:00 Joachim Pouderoux : > Carlos, > > For information, here is the merge request that address the wedge issue: > https://gitlab.kitware.com/vtk/vtk/merge_requests/4059 > This is a simple patch for now, better solution will come. > > Joachim > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com>: > >> Thanks Joachim, >> >> I'll give it a go! >> >> C. >> >> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < >> joachim.pouderoux at kitware.com>: >> >>> Carlos, >>> >>> OpenFOAM can produce cells with non planar faces which is not handled by >>> VTK/ParaView. Moreover it appears that current reader implementation can >>> also produce incorrect cells when reading wedge cells. >>> Thanks to a recent rewriting of the polydron clipping algorithm, the >>> clipping/slicing of polyhedron should no more lead to crashes. However,the >>> problems >>> of non planar faces might produce some holes in the result. >>> We are currently working on a patch to better handle this case in the >>> reader. >>> If you want to try the new polyhedron clipping algorithm, you will have >>> to use ParaView >= 5.5 RC1. >>> >>> Best regards, >>> Joachim >>> >>> >>> *Joachim Pouderoux*, PhD >>> >>> *Technical Expert - Scientific Computing Team* >>> *Kitware SAS * >>> >>> >>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >>> carlosemanglanov at gmail.com>: >>> >>>> It's me again, I'm sorry, >>>> >>>> Problem NOT solved!!! ... Hardware looks ok, software and system >>>> handling memory looks good too. >>>> >>>> ParaView shuts down if I try to generate a clip with the "VTK >>>> Polyhedron" option selected, before and after clipping ... >>>> >>>> possible bug?? >>>> >>>> C. >>>> >>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>> >>>>> Hi Carlos, >>>>> >>>>> That error message means that an exception was thrown from a Qt event >>>>> handler. The message about reimplementing QApplication::notify() is just >>>>> to tell you how to catch the exception if you wanted to. The real problem >>>>> is the exception. >>>>> >>>>> A std::bad_alloc exception happens when the program tries to allocate >>>>> memory and fails. So you need to figure out why you are running out of >>>>> memory (that is the most likely cause of the error). >>>>> >>>>> HTH, >>>>> Shawn >>>>> >>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>>> carlosemanglanov at gmail.com> wrote: >>>>> >>>>>> Hi everyone! >>>>>> >>>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>>> program crashes giving me the following error message: >>>>>> >>>>>> I/O : uncollated >>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>> what(): std::bad_alloc >>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>> >>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same >>>>>> error with Ubuntu 17.10 which I had installed until last night. >>>>>> >>>>>> I am looking for info about "reimplementing QApplication" with no >>>>>> luck. >>>>>> >>>>>> Any suggestions, please? >>>>>> Carlos >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 26 15:38:21 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 26 Mar 2018 15:38:21 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs In-Reply-To: References: Message-ID: > a. When I select ?Real Time? option and increase the time, even though > it is cached, it still keeps reloading which prevents the VR from working. > Is there any potential/possibility to fix this in the meantime or upcoming > release? Caching cannot work in "real time" mode since there's no guarantee what time each frame will be rendered at. > b. When I cache it as a volume (rather than surface, wireframe, or > points) on my laptop, it crashed the exe even when I increase the cache > memory maximum size. Any thoughts on that? I tested it on a bigger and > faster work station and it worked, however, it still has the issue mentioned > in the point below. I suspect you're just running out of memory on the system, esp since you say smaller mesh works. > 2. When I get a smaller mesh (4x smaller), I am able to cache it as a > volume. However, when playing it back, it keeps reloading while showing the > green bar as below at each time step. Is that supposed to happen? Is that > rendering? Is there a way to eliminate it or make it faster? Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems to me you have unstructured grid which is using the slow path for volume rendering. Another option is to apply "Resample To Image" filter to resample the dataset to an image and volume rendering the result. Then rendering should be much faster. You can also resample and generate the image as a processing stage and save the resampled dataset out and then load and render it in the animation loop. From joachim.pouderoux at kitware.com Mon Mar 26 15:39:37 2018 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 26 Mar 2018 15:39:37 -0400 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Crashes did not occur all the time. It depends on the cell geometry/topology and the slice origin/normal. *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2018-03-26 15:14 GMT-04:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > Quite interestingly, I have just create a 2D slice in a mesh with 947443 > cells, and it has not crashed!! It is showing the "holes" you mentioned > before, though. This is puzzling me, some meshes make PV to crash, and > others just show the bug you mentiones :-/ > > C. > > 2018-03-26 21:07 GMT+02:00 Joachim Pouderoux < > joachim.pouderoux at kitware.com>: > >> Carlos, >> >> For information, here is the merge request that address the wedge issue: >> https://gitlab.kitware.com/vtk/vtk/merge_requests/4059 >> This is a simple patch for now, better solution will come. >> >> Joachim >> >> *Joachim Pouderoux*, PhD >> >> *Technical Expert - Scientific Computing Team* >> *Kitware SAS * >> >> >> 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com>: >> >>> Thanks Joachim, >>> >>> I'll give it a go! >>> >>> C. >>> >>> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < >>> joachim.pouderoux at kitware.com>: >>> >>>> Carlos, >>>> >>>> OpenFOAM can produce cells with non planar faces which is not handled >>>> by VTK/ParaView. Moreover it appears that current reader implementation can >>>> also produce incorrect cells when reading wedge cells. >>>> Thanks to a recent rewriting of the polydron clipping algorithm, the >>>> clipping/slicing of polyhedron should no more lead to crashes. However,the >>>> problems >>>> of non planar faces might produce some holes in the result. >>>> We are currently working on a patch to better handle this case in the >>>> reader. >>>> If you want to try the new polyhedron clipping algorithm, you will >>>> have to use ParaView >= 5.5 RC1. >>>> >>>> Best regards, >>>> Joachim >>>> >>>> >>>> *Joachim Pouderoux*, PhD >>>> >>>> *Technical Expert - Scientific Computing Team* >>>> *Kitware SAS * >>>> >>>> >>>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >>>> carlosemanglanov at gmail.com>: >>>> >>>>> It's me again, I'm sorry, >>>>> >>>>> Problem NOT solved!!! ... Hardware looks ok, software and system >>>>> handling memory looks good too. >>>>> >>>>> ParaView shuts down if I try to generate a clip with the "VTK >>>>> Polyhedron" option selected, before and after clipping ... >>>>> >>>>> possible bug?? >>>>> >>>>> C. >>>>> >>>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>>> >>>>>> Hi Carlos, >>>>>> >>>>>> That error message means that an exception was thrown from a Qt event >>>>>> handler. The message about reimplementing QApplication::notify() is just >>>>>> to tell you how to catch the exception if you wanted to. The real problem >>>>>> is the exception. >>>>>> >>>>>> A std::bad_alloc exception happens when the program tries to allocate >>>>>> memory and fails. So you need to figure out why you are running out of >>>>>> memory (that is the most likely cause of the error). >>>>>> >>>>>> HTH, >>>>>> Shawn >>>>>> >>>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>>>> carlosemanglanov at gmail.com> wrote: >>>>>> >>>>>>> Hi everyone! >>>>>>> >>>>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>>>> program crashes giving me the following error message: >>>>>>> >>>>>>> I/O : uncollated >>>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>>> what(): std::bad_alloc >>>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>>> >>>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same >>>>>>> error with Ubuntu 17.10 which I had installed until last night. >>>>>>> >>>>>>> I am looking for info about "reimplementing QApplication" with no >>>>>>> luck. >>>>>>> >>>>>>> Any suggestions, please? >>>>>>> Carlos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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: >>>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Mon Mar 26 16:13:40 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Mon, 26 Mar 2018 22:13:40 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: <6258C5A6-E165-4E00-A4D9-88ADDE33F1F6@gmail.com> Thanks Joachim, I suspected it was more interesting than ?just? a program bug. > El 26 mar 2018, a las 21:39, Joachim Pouderoux escribi?: > > Crashes did not occur all the time. It depends on the cell geometry/topology and the slice origin/normal. > > Joachim Pouderoux, PhD > Technical Expert - Scientific Computing Team > Kitware SAS > > 2018-03-26 15:14 GMT-04:00 Carlos E Manglano-Villamarin : >> Quite interestingly, I have just create a 2D slice in a mesh with 947443 cells, and it has not crashed!! It is showing the "holes" you mentioned before, though. This is puzzling me, some meshes make PV to crash, and others just show the bug you mentiones :-/ >> >> C. >> >> 2018-03-26 21:07 GMT+02:00 Joachim Pouderoux : >>> Carlos, >>> >>> For information, here is the merge request that address the wedge issue: >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/4059 >>> This is a simple patch for now, better solution will come. >>> >>> Joachim >>> >>> Joachim Pouderoux, PhD >>> Technical Expert - Scientific Computing Team >>> Kitware SAS >>> >>> 2018-03-26 15:04 GMT-04:00 Carlos E Manglano-Villamarin : >>>> Thanks Joachim, >>>> >>>> I'll give it a go! >>>> >>>> C. >>>> >>>> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux : >>>>> Carlos, >>>>> >>>>> OpenFOAM can produce cells with non planar faces which is not handled by VTK/ParaView. Moreover it appears that current reader implementation can >>>>> also produce incorrect cells when reading wedge cells. >>>>> Thanks to a recent rewriting of the polydron clipping algorithm, the clipping/slicing of polyhedron should no more lead to crashes. However,the problems >>>>> of non planar faces might produce some holes in the result. >>>>> We are currently working on a patch to better handle this case in the reader. >>>>> If you want to try the new polyhedron clipping algorithm, you will have to use ParaView >= 5.5 RC1. >>>>> >>>>> Best regards, >>>>> Joachim >>>>> >>>>> >>>>> Joachim Pouderoux, PhD >>>>> Technical Expert - Scientific Computing Team >>>>> Kitware SAS >>>>> >>>>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin : >>>>>> It's me again, I'm sorry, >>>>>> >>>>>> Problem NOT solved!!! ... Hardware looks ok, software and system handling memory looks good too. >>>>>> >>>>>> ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" option selected, before and after clipping ... >>>>>> >>>>>> possible bug?? >>>>>> >>>>>> C. >>>>>> >>>>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>>>>> Hi Carlos, >>>>>>> >>>>>>> That error message means that an exception was thrown from a Qt event handler. The message about reimplementing QApplication::notify() is just to tell you how to catch the exception if you wanted to. The real problem is the exception. >>>>>>> >>>>>>> A std::bad_alloc exception happens when the program tries to allocate memory and fails. So you need to figure out why you are running out of memory (that is the most likely cause of the error). >>>>>>> >>>>>>> HTH, >>>>>>> Shawn >>>>>>> >>>>>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin wrote: >>>>>>>> Hi everyone! >>>>>>>> >>>>>>>> When I postprocess some simulations, less than 900,000 cells, from openfoam, either opening paraview directly or using the parafoam tool, the program crashes giving me the following error message: >>>>>>>> >>>>>>>> I/O : uncollated >>>>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>>>> what(): std::bad_alloc >>>>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>>>> >>>>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error with Ubuntu 17.10 which I had installed until last night. >>>>>>>> >>>>>>>> I am looking for info about "reimplementing QApplication" with no luck. >>>>>>>> >>>>>>>> Any suggestions, please? >>>>>>>> Carlos >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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: >>>>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthewthomas at usgs.gov Mon Mar 26 16:44:44 2018 From: matthewthomas at usgs.gov (Thomas, Matthew) Date: Mon, 26 Mar 2018 14:44:44 -0600 Subject: [Paraview] Paraview GUI display problems Message-ID: Hello, I am running the most current build of Paraview on a Windows 10 machine. I have noticed that there appears to be a slight GUI-based glitch. To mouse click a menu or button, I have to position the cursor well below the intended target to make it clickable. The main menu options (e.g., File, Edit, etc.) are also obscured by the window title pane (see attached). Has anyone else experienced this problem? Is it related to a graphics card / display driver issue? Take care, matt -- Matthew A. Thomas, PhD U.S. Geological Survey, Research Hydrologist (Mendenhall) p: 303.273.8588 <(303)%20273-8588> e: matthewthomas at usgs.gov m: 1711 Illinois Street (Rm. 330), Golden, CO 80401 *https://www.usgs.gov/staff-profiles/matthew-a-thomas * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screenshot.png Type: image/png Size: 125094 bytes Desc: screenshot.png URL: From utkarsh.ayachit at kitware.com Mon Mar 26 20:22:18 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 26 Mar 2018 20:22:18 -0400 Subject: [Paraview] Paraview GUI display problems In-Reply-To: References: Message-ID: It is most likely an Intel driver issue, and an upgrade of the drivers should address it. See discussion here: https://gitlab.kitware.com/paraview/paraview/issues/17499 Utkarsh On Mon, Mar 26, 2018 at 4:44 PM, Thomas, Matthew wrote: > Hello, > > I am running the most current build of Paraview on a Windows 10 machine. I > have noticed that there appears to be a slight GUI-based glitch. To mouse > click a menu or button, I have to position the cursor well below the > intended target to make it clickable. The main menu options (e.g., File, > Edit, etc.) are also obscured by the window title pane (see attached). > > Has anyone else experienced this problem? Is it related to a graphics card / > display driver issue? > > Take care, > matt > > > -- > Matthew A. Thomas, PhD > U.S. Geological Survey, Research Hydrologist (Mendenhall) > > p: 303.273.8588 > e: matthewthomas at usgs.gov > m: 1711 Illinois Street (Rm. 330), Golden, CO 80401 > > https://www.usgs.gov/staff-profiles/matthew-a-thomas > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From mbeshr1986 at gmail.com Tue Mar 27 08:07:05 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Tue, 27 Mar 2018 08:07:05 -0400 Subject: [Paraview] Paraview VR .exe version Message-ID: I am trying to try/use the NVIDIA IndeX plugin on the Paraview VR version. However, this plugin requires/needs a .exe (installed) version of Paraview (I tried it with .exe non-VR versions and it works but not with the extracted .zip VR version). The downloads section only has the .zip version for the VR. Anyone knows of a .exe version in the downloads section? -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Tue Mar 27 09:10:38 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Tue, 27 Mar 2018 15:10:38 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Joachim, Quick question about PV >= 5.5 RC1 ... I have downloaded the RC3, how do I install it? I cannot find any 'make' or 'install' file ... Is it provided to run "out of the box"? Regards, Carlos 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux : > Carlos, > > OpenFOAM can produce cells with non planar faces which is not handled by > VTK/ParaView. Moreover it appears that current reader implementation can > also produce incorrect cells when reading wedge cells. > Thanks to a recent rewriting of the polydron clipping algorithm, the > clipping/slicing of polyhedron should no more lead to crashes. However,the > problems > of non planar faces might produce some holes in the result. > We are currently working on a patch to better handle this case in the > reader. > If you want to try the new polyhedron clipping algorithm, you will have > to use ParaView >= 5.5 RC1. > > Best regards, > Joachim > > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com>: > >> It's me again, I'm sorry, >> >> Problem NOT solved!!! ... Hardware looks ok, software and system handling >> memory looks good too. >> >> ParaView shuts down if I try to generate a clip with the "VTK Polyhedron" >> option selected, before and after clipping ... >> >> possible bug?? >> >> C. >> >> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >> >>> Hi Carlos, >>> >>> That error message means that an exception was thrown from a Qt event >>> handler. The message about reimplementing QApplication::notify() is just >>> to tell you how to catch the exception if you wanted to. The real problem >>> is the exception. >>> >>> A std::bad_alloc exception happens when the program tries to allocate >>> memory and fails. So you need to figure out why you are running out of >>> memory (that is the most likely cause of the error). >>> >>> HTH, >>> Shawn >>> >>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>> carlosemanglanov at gmail.com> wrote: >>> >>>> Hi everyone! >>>> >>>> When I postprocess some simulations, less than 900,000 cells, from >>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>> program crashes giving me the following error message: >>>> >>>> I/O : uncollated >>>> terminate called after throwing an instance of 'std::bad_alloc' >>>> what(): std::bad_alloc >>>> Qt has caught an exception thrown from an event handler. Throwing >>>> exceptions from an event handler is not supported in Qt. You must >>>> reimplement QApplication::notify() and catch all exceptions there. >>>> >>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>>> with Ubuntu 17.10 which I had installed until last night. >>>> >>>> I am looking for info about "reimplementing QApplication" with no luck. >>>> >>>> Any suggestions, please? >>>> Carlos >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Tue Mar 27 09:29:37 2018 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 27 Mar 2018 09:29:37 -0400 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Carlos, What did you download exactly? The sources archive or the binaries? On which platform? Best, *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2018-03-27 9:10 GMT-04:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > Joachim, > > Quick question about PV >= 5.5 RC1 ... I have downloaded the RC3, how do I > install it? I cannot find any 'make' or 'install' file ... Is it provided > to run "out of the box"? > > Regards, > Carlos > > 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < > joachim.pouderoux at kitware.com>: > >> Carlos, >> >> OpenFOAM can produce cells with non planar faces which is not handled by >> VTK/ParaView. Moreover it appears that current reader implementation can >> also produce incorrect cells when reading wedge cells. >> Thanks to a recent rewriting of the polydron clipping algorithm, the >> clipping/slicing of polyhedron should no more lead to crashes. However,the >> problems >> of non planar faces might produce some holes in the result. >> We are currently working on a patch to better handle this case in the >> reader. >> If you want to try the new polyhedron clipping algorithm, you will have >> to use ParaView >= 5.5 RC1. >> >> Best regards, >> Joachim >> >> >> *Joachim Pouderoux*, PhD >> >> *Technical Expert - Scientific Computing Team* >> *Kitware SAS * >> >> >> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com>: >> >>> It's me again, I'm sorry, >>> >>> Problem NOT solved!!! ... Hardware looks ok, software and system >>> handling memory looks good too. >>> >>> ParaView shuts down if I try to generate a clip with the "VTK >>> Polyhedron" option selected, before and after clipping ... >>> >>> possible bug?? >>> >>> C. >>> >>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>> >>>> Hi Carlos, >>>> >>>> That error message means that an exception was thrown from a Qt event >>>> handler. The message about reimplementing QApplication::notify() is just >>>> to tell you how to catch the exception if you wanted to. The real problem >>>> is the exception. >>>> >>>> A std::bad_alloc exception happens when the program tries to allocate >>>> memory and fails. So you need to figure out why you are running out of >>>> memory (that is the most likely cause of the error). >>>> >>>> HTH, >>>> Shawn >>>> >>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>> carlosemanglanov at gmail.com> wrote: >>>> >>>>> Hi everyone! >>>>> >>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>> program crashes giving me the following error message: >>>>> >>>>> I/O : uncollated >>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>> what(): std::bad_alloc >>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>> exceptions from an event handler is not supported in Qt. You must >>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>> >>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same error >>>>> with Ubuntu 17.10 which I had installed until last night. >>>>> >>>>> I am looking for info about "reimplementing QApplication" with no luck. >>>>> >>>>> Any suggestions, please? >>>>> Carlos >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 27 09:39:46 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 27 Mar 2018 09:39:46 -0400 Subject: [Paraview] Paraview VR .exe version In-Reply-To: References: Message-ID: Mohamed, That type of installer for the VR-enabled ParaView is not yet available, I am afraid. I'm not sure anyone has tried the IndeX plugin in VR - it's an interesting idea, for sure. Best regards, Cory On Tue, Mar 27, 2018 at 8:07 AM, Mohamed Beshr wrote: > I am trying to try/use the NVIDIA IndeX plugin on the Paraview VR version. > However, this plugin requires/needs a .exe (installed) version of Paraview > (I tried it with .exe non-VR versions and it works but not with the > extracted .zip VR version). The downloads section only has the .zip version > for the VR. Anyone knows of a .exe version in the downloads section? > > -- > Best Regards, > Mohamed Beshr > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From timothy.a.beach at nasa.gov Tue Mar 27 09:52:49 2018 From: timothy.a.beach at nasa.gov (Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC]) Date: Tue, 27 Mar 2018 13:52:49 +0000 Subject: [Paraview] Integrate variables v 5.4.1 - ??? Message-ID: <1CE3E6F7-221C-4093-8049-8559E16F34D6@contoso.com> I?m using v5.4.1 with PLOT3d type structured data. I noticed that the divide cell data by volume box doesn?t do what I want it to. I don?t know if this constitutes a bug but I made the following change: DivideDataArraysByConstant(output->GetCellData(), true, this->Sum); To DivideDataArraysByConstant(output->GetPointData(), true, this->Sum); That does what I want it too. In my case there is only 1 cell which is volume. The data is in the point field. It works for me. Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Tue Mar 27 10:07:14 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Tue, 27 Mar 2018 10:07:14 -0400 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: Hi Jamil, Please keep replies CCed to the mailing list (Reply All) so others can contribute to the discussion (or find answers to their own problems later in the archives). We use the most recent release of ninja on most of our build machines (so that one should work). I'm not sure why you are getting that error messages from what you have included... maybe others on the list can chime in or you can give more details. Shawn On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich wrote: > Hi Shawn, > > thanks a lot for the tip, configuring worked with the Visual Studio 12.0 > compiler! Now I am getting a lot of build errors though. > > C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning > C4244: '=' : conversion from 'double' to 'float', possible loss of data > [255/256] Linking C shared library bin\hdf5.dll > Creating library bin\hdf5.lib and object bin\hdf5.exp > [256/256] Linking C shared library bin\hdf5_hl.dll > Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp > ninja: build stopped: subcommand failed. > > LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' > [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll > [4/97] Building CXX object client_src\CMakeFiles\vrpn_ > print_messages.dir\vrpn_print_messages.C.obj > [5/97] Building CXX object client_src\CMakeFiles\ff_ > client.dir\ff_client.C.obj > [6/97] Building CXX object client_src\CMakeFiles\phan_ > client.dir\phan_client.C.obj > [7/97] Building CXX object client_src\CMakeFiles\ > printvals.dir\printvals.C.obj > ninja: build stopped: subcommand failed. > CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 > (message): > Failed with exit code 1 > > These are some examples. My it be possible that the ninja version is not > suited either? Do you know what ninja version you were building the > superbuild with? > > Thanks a lot, > Jamil > > 2018-03-26 17:21 GMT+02:00 Shawn Waldon : > >> Hi Jamil, >> >> I'm not sure if this will get you all the way to a build, but here are >> some pointers: >> >> We build with the visual studio compiler but use the Ninja generator >> since it is significantly faster than VS. >> >> VS 2017 may not work. Our binaries are built with 2013 right now and we >> plan to move to 2015 after the current release cycle. If you want what you >> are building to be compatible with the Kitware binaries, you will need to >> use 2013. Also, I believe there are compiler errors if you use 2017 right >> now. >> >> To build with Ninja and VS compilers, you need to be in a visual studio >> command prompt rather than a normal shell (it sets a bunch of environment >> vars, which I think is what is missing in your last example). To convert a >> normal command prompt you run (example is for VS2015, your path may differ) >> 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64' >> in your shell and it will set the environment variables for you. If you >> have the environment set up before running cmake -G Ninja it should just >> pick the right compiler. >> >> HTH, >> >> Shawn >> >> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >> jamil.goettlich at gmail.com> wrote: >> >>> Hello, >>> >>> I am having Problems building ParaView with ParaView-Superbuild. As >>> Visual Studio is not supported, I tried other build systems and compilers. >>> Unfortunately none of them succeeded. On the other hand I was able to build >>> small HelloWord programs with each of the combinations listed below and >>> without any errors. Here is what I did: >>> >>> First, I cloned from git: >>> git clone --recursive https://gitlab.kitware.com/par >>> aview/paraview-superbuild.git >>> Then cd paraview-superbuild and created new folder (build). >>> >>> The following cases did not work out (Doesnt matter if using Git Bash or >>> VS Command Prompt): >>> Build System: Ninja, Compiler: MinGW >>> command: cmake .. -G "Ninja" >>> Error: >>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>> At least Visual Studio 9.0 is required >>> Call Stack (most recent call first): >>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>> >>> Although I have Visual Studio 15 2017 installed it does not seem to work. >>> >>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program Files >>> (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>> \MSVC\14.12.25827\bin\Hostx64\x64) >>> Error: >>> >>> The C compiler >>> "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools >>> /MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" >>> is not able to compile a simple test program. >>> It fails with the following output: >>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>> "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>> \MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f >>> CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>> CMakeFiles\cmTC_008b4.dir\build >>> >>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>> >>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>> >>> testCCompiler.c >>> >>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>> fatal error C1001: An internal error has occurred in the compiler. >>> >>> (compiler file 'msc1.cpp', line 1507) >>> >>> To work around this problem, try simplifying or changing the program >>> near the locations listed above. >>> >>> Please choose the Technical Support command on the Visual C++ >>> >>> Help menu, or open the Technical Support help file for more information >>> >>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>> prompted to send an error report to Microsoft later. >>> >>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code >>> '0x2' >>> >>> Stop. >>> >>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>> : return code '0x2' >>> >>> Stop. >>> >>> >>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>> \MSVC\14.12.25827\bin\Hostx64\x64) >>> >>> Here, cmake recognized the compiler, but it throws another error >>> Error: >>> >>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>> Could not find compiler set in environment variable RC: >>> rc. >>> Call Stack (most recent call first): >>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC.cmake:323 >>> (enable_language) >>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC-C.cmake:5 >>> (__windows_compiler_msvc) >>> C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeCInformation.cmake:48 >>> (include) >>> CMakeLists.txt:3 (project) >>> >>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>> >>> >>> I am out of ideas now. >>> I would be really happy for a detailed build description as I am sure I >>> did not understand something properly. >>> >>> And every hint on how to resolve on of those errors is very welcome too. >>> >>> >>> Thanks in advance! >>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 27 10:18:46 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 27 Mar 2018 10:18:46 -0400 Subject: [Paraview] unknown properties returned by ListProperties? In-Reply-To: <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> Message-ID: Hi Roman, I'm sorry I haven't had a chance to look at this further. Have you made any more progress on this? I apologize for thinking it would be easy to hack ParaView to better support loading multiple state files - it appears to be more difficult than expected after all. Best regards, Cory On Tue, Mar 20, 2018 at 12:13 PM, Grothausmann, Roman Dr. < grothausmann.roman at mh-hannover.de> wrote: > Many thanks Cory for your feedback. Not adding empty (None) properties did > not help (http://github.com/romangrothausmann/ParaView_scripts/ > commit/d3af645dd1af2a). Anyway, "ForceUseCache" has a vector of value 0 > so it seems to me the actual problem still is that ListProperties() returns > properties that are not part of the specific object that is calling > ListProperties(). E.g. help(repr) does not list a property called > "ForceUseCache" but e.g. "Visibility" > > So I decided to only restore the property "Visibility" for a start: > http://github.com/romangrothausmann/ParaView_scripts/commit/ > d1c63f2682e834e > Even though there is no error on execution any more, the resulting PVSM > has only the visibilities set for the last loaded PVSM, i.e. the setting of > the "Visibility" of representations loaded from former PVSMs did not have > any effect. > Is there a need to call some kind of Update() to make the property setting > have any effect? I tried some rendering (http://github.com/romangrotha > usmann/ParaView_scripts/commit/294ff85a0cc7a), but that did not help > either. > > > On 20/03/18 06:12, Cory Quammen wrote: > >> Roman, >> >> Looking at your original problem with the error: >> >> >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", >> line 1296, in SetData >> self.SMProperty.AddProxy(value_proxy) >> TypeError: AddProxy argument 1: method requires a VTK object >> >> >> You are hitting this when attempting to set the DataAxesGrid, which is a >> ProxyProperty. In your dictionary, this entry has value 'None', but it >> looks like setting a property to value 'None' is not handled correctly in >> servermanager.py. As a workaround, I suggest filtering out properties from >> your dictionary that have 'None' as a value, i.e., do not add those >> property values to your dictionary. >> >> HTH, >> Cory >> >> On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr. < >> grothausmann.roman at mh-hannover.de > hannover.de>> wrote: >> >> Hi Cory, >> >> >> Trying to find out what causes the former problems, I inserted a line >> that >> just sets the property that got collected so far: >> https://github.com/romangrothausmann/ParaView_scripts/ >> commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420 >> 278bfff084788b82c715c452eR59 >> > commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420 >> 278bfff084788b82c715c452eR59> >> It already aborts on the first property encountered (ForceUseCache): >> >> > 0x7f7b591fc250> >> ForceUseCache 0 >> Traceback (most recent call last): >> File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in >> >> main() >> File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main >> pvs.SetProperties(repr, **d) >> File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >> view/simple.py", >> line 567, in SetProperties >> raise AttributeError("object has no property %s" % param) >> AttributeError: object has no property ForceUseCache >> >> Is ListProperties() returning properties that are not part of the >> specific >> object that is calling ListProperties()? >> >> Many thanks for any help or hints, >> Roman >> >> On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: >> >> Hi Cory, >> >> On 06/12/17 23:06, Cory Quammen wrote: >> >> Sorry I failed to follow up. Did you find a solution to this >> problem? >> >> >> Many thanks for your reply. No, and I'm still stuck. I tried Your >> suggestion to remove [0] >> (https://github.com/romangrothausmann/ParaView_scripts/ >> commit/e40d1016d698ee363500bb9bf04f29add89b99dd >> > commit/e40d1016d698ee363500bb9bf04f29add89b99dd>), >> >> which changed the reported error from: >> >> File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >> view/servermanager.py", >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >> view/servermanager.py", >> line 803, in SetData >> raise RuntimeError("This property requires %d values." % >> self.GetNumberOfElements()) >> RuntimeError: This property requires 3 values. >> >> to: >> >> File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >> view/servermanager.py", >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File >> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/para >> view/servermanager.py", >> line 1296, in SetData >> self.SMProperty.AddProxy(value_proxy) >> TypeError: AddProxy argument 1: method requires a VTK object >> >> Any ideas on this? >> Would You say it is a general problem in the py-code or could it >> be >> caused by the content of the PVSMs I'm trying to combine? >> >> Many thanks for looking into this. >> Roman >> >> >> This line in your script looks funny to me: >> >> d[props] = pvs.GetProperty(repr, props[0]) >> >> Shouldn't props[0] just be props? >> >> Thanks, >> Cory >> >> On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. >> > > wrote: >> >> Dear Cory, >> >> On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: >> >> >> On 15/09/17 15:14, Cory Quammen wrote: >> >> >> Put a ** in front of reppro[i], e.g., >> >> pvs.SetProperties(repr, **reppro[i]) >> >> >> Hm, I now get: >> TypeError: SetProperties() argument after ** must be a >> mapping, not list >> Do I have to store the dict of object properties in >> another >> dict instead >> of a list? >> >> >> >> With a dict of dicts >> https://github.com/romangrothausmann/ParaView_scripts/ >> commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420 >> 278bfff084788b82c715c452e >> > commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420 >> 278bfff084788b82c715c452e> >> >> I get: >> >> File "/net/home/grothama/paraview/s >> cripts/pvsm-multi.py", >> line 64, in main >> pvs.SetProperties(repr, **reppro[i]); >> File >> "/opt/paraview-5.3.0_GL1/lib/p >> araview-5.3/site-packages/paraview/simple.py", >> line 568, in SetProperties >> setattr(proxy, param, params[param]) >> File >> "/opt/paraview-5.3.0_GL1/lib/p >> araview-5.3/site-packages/paraview/servermanager.py", >> >> line 317, in __setattr__ >> setter(self, value) >> File >> "/opt/paraview-5.3.0_GL1/lib/p >> araview-5.3/site-packages/paraview/servermanager.py", >> >> line 2528, in setProperty >> return self.SetPropertyWithName(propName, value) >> File >> "/opt/paraview-5.3.0_GL1/lib/p >> araview-5.3/site-packages/paraview/servermanager.py", >> >> line 375, in SetPropertyWithName >> prop.SetData(arg) >> File >> "/opt/paraview-5.3.0_GL1/lib/p >> araview-5.3/site-packages/paraview/servermanager.py", >> >> line 803, in SetData >> raise RuntimeError("This property requires %d >> values." % >> self.GetNumberOfElements()) >> RuntimeError: This property requires 3 values. >> >> Any ideas what could still be wrong? >> >> >> On 07/09/17 23:37, Cory Quammen wrote: >> >> >> >> Hi Roman, >> >> It turns out ParaView was not designed >> for this >> use case because of >> certain difficulties discussed here: >> >> https://gitlab.kitware.com/par >> aview/paraview/issues/17442 >> > raview/paraview/issues/17442> >> >> In your Python script, you could manually >> cash >> all the properties of >> the existing representations and restore >> them >> after loading the most >> recent state file. >> >> The functions >> >> reprs = GetRepresentations() >> repr = reprs.values()[0] >> props = repr.ListProperties() >> GetProperty(repr, props[0]) >> >> would be helpful for this. >> >> Cory >> >> >> On Mon, Sep 4, 2017 at 8:42 AM, >> Grothausmann, >> Roman Dr. >> > > >> wrote: >> >> >> >> Dear mailing list members, >> >> >> It seems that PV (and >> paraview.simple.LoadState) by default >> hides >> already >> loaded objects (and resets e.g. their >> coloring) when another >> state-file >> is >> loaded. >> Is there a way to load multiple >> state-files >> after one another without >> hiding >> and resetting already existent >> objects? I.e. >> a way to concatenate >> multiple >> state-files and leave their objects >> in the >> state as they got loaded >> (e.g. >> colored, hidden/visible)? >> I do understand that loading a new >> state-file will reset the camera, >> but >> not >> the rest. >> Here's my initial attempt to achieve >> this >> with pvpython: >> >> >> https://github.com/romangrotha >> usmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea8 >> 2fd6a9e23/pvsm-multi.py >> > ausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea >> 82fd6a9e23/pvsm-multi.py> >> >> >> Any help or hints are very much >> appreciated >> Roman >> >> -- >> Dr. Roman Grothausmann >> >> Tomographie und Digitale >> Bildverarbeitung >> Tomography and Digital Image Analysis >> >> Medizinische Hochschule Hannover >> Institut f?r Funktionelle und >> Angewandte >> Anatomie >> OE 4120, Carl-Neuberg-Str. 1, 30625 >> Hannover, Deutschland >> >> Tel. +49 511 532-2900 >> >> grothausmann.roman at mh-hannover.de >> > hannover.de> >> http://www.mh-hannover.de/anat >> omie.html >> > tomie.html> >> ______________________________ >> _________________ >> Powered by www.kitware.com >> >> >> Visit other Kitware open-source >> projects at >> http://www.kitware.com/opensou >> rce/opensource.html >> > urce/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 >> > =ParaView> >> >> Follow this link to >> subscribe/unsubscribe: >> http://public.kitware.com/mail >> man/listinfo/paraview >> > lman/listinfo/paraview> >> >> >> >> >> >> >> >> -- Dr. Roman >> Grothausmann >> >> Tomographie und Digitale Bildverarbeitung >> Tomography and Digital Image Analysis >> >> Medizinische Hochschule Hannover >> Institut f?r Funktionelle und Angewandte >> Anatomie >> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, >> Deutschland >> >> Tel. +49 511 532-2900 >> >> grothausmann.roman at mh-hannover.de >> >> http://www.mh-hannover.de/anatomie.html >> >> >> >> >> >> >> >> >> -- Dr. Roman Grothausmann >> >> Tomographie und Digitale Bildverarbeitung >> Tomography and Digital Image Analysis >> >> Medizinische Hochschule Hannover >> Institut f?r Funktionelle und Angewandte Anatomie >> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >> >> Tel. +49 511 532-2900 >> grothausmann.roman at mh-hannover.de >> >> http://www.mh-hannover.de/anatomie.html >> >> >> >> >> >> >> >> -- Dr. Roman Grothausmann >> >> Tomographie und Digitale Bildverarbeitung >> Tomography and Digital Image Analysis >> >> Medizinische Hochschule Hannover >> Institut f?r Funktionelle und Angewandte Anatomie >> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland >> >> Tel. +49 511 532-2900 >> grothausmann.roman at mh-hannover.de > hannover.de> >> http://www.mh-hannover.de/anatomie.html >> >> >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > http://www.mh-hannover.de/anatomie.html > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamil.goettlich at gmail.com Tue Mar 27 10:37:00 2018 From: jamil.goettlich at gmail.com (Jamil Goettlich) Date: Tue, 27 Mar 2018 16:37:00 +0200 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: Hi Shawn, thanks a lot for the tip, configuring worked with the Visual Studio 12.0 compiler! Now I am getting a lot of build errors though. C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning C4244: '=' : conversion from 'double' to 'float', possible loss of data [255/256] Linking C shared library bin\hdf5.dll Creating library bin\hdf5.lib and object bin\hdf5.exp [256/256] Linking C shared library bin\hdf5_hl.dll Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp ninja: build stopped: subcommand failed. LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll [4/97] Building CXX object client_src\CMakeFiles\vrpn_ print_messages.dir\vrpn_print_messages.C.obj [5/97] Building CXX object client_src\CMakeFiles\ff_ client.dir\ff_client.C.obj [6/97] Building CXX object client_src\CMakeFiles\phan_ client.dir\phan_client.C.obj [7/97] Building CXX object client_src\CMakeFiles\ printvals.dir\printvals.C.obj ninja: build stopped: subcommand failed. CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 (message): Failed with exit code 1 These are some examples. My it be possible that the ninja version is not suited either? Do you know what ninja version you were building the superbuild with? Thanks a lot, Jamil (P.s. Sorry Shawn for my posting mistake) 2018-03-27 16:07 GMT+02:00 Shawn Waldon : > Hi Jamil, > > Please keep replies CCed to the mailing list (Reply All) so others can > contribute to the discussion (or find answers to their own problems later > in the archives). > > We use the most recent release of ninja on most of our build machines (so > that one should work). I'm not sure why you are getting that error > messages from what you have included... maybe others on the list can chime > in or you can give more details. > > Shawn > > On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < > jamil.goettlich at gmail.com> wrote: > >> Hi Shawn, >> >> thanks a lot for the tip, configuring worked with the Visual Studio 12.0 >> compiler! Now I am getting a lot of build errors though. >> >> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >> C4244: '=' : conversion from 'double' to 'float', possible loss of data >> [255/256] Linking C shared library bin\hdf5.dll >> Creating library bin\hdf5.lib and object bin\hdf5.exp >> [256/256] Linking C shared library bin\hdf5_hl.dll >> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >> ninja: build stopped: subcommand failed. >> >> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >> nt_messages.dir\vrpn_print_messages.C.obj >> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >> t.dir\ff_client.C.obj >> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >> ent.dir\phan_client.C.obj >> [7/97] Building CXX object client_src\CMakeFiles\printval >> s.dir\printvals.C.obj >> ninja: build stopped: subcommand failed. >> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >> (message): >> Failed with exit code 1 >> >> These are some examples. My it be possible that the ninja version is not >> suited either? Do you know what ninja version you were building the >> superbuild with? >> >> Thanks a lot, >> Jamil >> >> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >> >>> Hi Jamil, >>> >>> I'm not sure if this will get you all the way to a build, but here are >>> some pointers: >>> >>> We build with the visual studio compiler but use the Ninja generator >>> since it is significantly faster than VS. >>> >>> VS 2017 may not work. Our binaries are built with 2013 right now and we >>> plan to move to 2015 after the current release cycle. If you want what you >>> are building to be compatible with the Kitware binaries, you will need to >>> use 2013. Also, I believe there are compiler errors if you use 2017 right >>> now. >>> >>> To build with Ninja and VS compilers, you need to be in a visual studio >>> command prompt rather than a normal shell (it sets a bunch of environment >>> vars, which I think is what is missing in your last example). To convert a >>> normal command prompt you run (example is for VS2015, your path may differ) >>> 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64' >>> in your shell and it will set the environment variables for you. If you >>> have the environment set up before running cmake -G Ninja it should just >>> pick the right compiler. >>> >>> HTH, >>> >>> Shawn >>> >>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >>> jamil.goettlich at gmail.com> wrote: >>> >>>> Hello, >>>> >>>> I am having Problems building ParaView with ParaView-Superbuild. As >>>> Visual Studio is not supported, I tried other build systems and compilers. >>>> Unfortunately none of them succeeded. On the other hand I was able to build >>>> small HelloWord programs with each of the combinations listed below and >>>> without any errors. Here is what I did: >>>> >>>> First, I cloned from git: >>>> git clone --recursive https://gitlab.kitware.com/par >>>> aview/paraview-superbuild.git >>>> Then cd paraview-superbuild and created new folder (build). >>>> >>>> The following cases did not work out (Doesnt matter if using Git Bash >>>> or VS Command Prompt): >>>> Build System: Ninja, Compiler: MinGW >>>> command: cmake .. -G "Ninja" >>>> Error: >>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>>> At least Visual Studio 9.0 is required >>>> Call Stack (most recent call first): >>>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>>> >>>> Although I have Visual Studio 15 2017 installed it does not seem to >>>> work. >>>> >>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program >>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>> Error: >>>> >>>> The C compiler >>>> "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools >>>> /MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" >>>> is not able to compile a simple test program. >>>> It fails with the following output: >>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>>> "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>> \MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f >>>> CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>>> CMakeFiles\cmTC_008b4.dir\build >>>> >>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>>> >>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>>> >>>> testCCompiler.c >>>> >>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>>> fatal error C1001: An internal error has occurred in the compiler. >>>> >>>> (compiler file 'msc1.cpp', line 1507) >>>> >>>> To work around this problem, try simplifying or changing the program >>>> near the locations listed above. >>>> >>>> Please choose the Technical Support command on the Visual C++ >>>> >>>> Help menu, or open the Technical Support help file for more information >>>> >>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>>> prompted to send an error report to Microsoft later. >>>> >>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code >>>> '0x2' >>>> >>>> Stop. >>>> >>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>>> : return code '0x2' >>>> >>>> Stop. >>>> >>>> >>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>> >>>> Here, cmake recognized the compiler, but it throws another error >>>> Error: >>>> >>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>>> Could not find compiler set in environment variable RC: >>>> rc. >>>> Call Stack (most recent call first): >>>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC.cmake:323 >>>> (enable_language) >>>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC-C.cmake:5 >>>> (__windows_compiler_msvc) >>>> C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeCInformation.cmake:48 >>>> (include) >>>> CMakeLists.txt:3 (project) >>>> >>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>>> >>>> >>>> I am out of ideas now. >>>> I would be really happy for a detailed build description as I am sure I >>>> did not understand something properly. >>>> >>>> And every hint on how to resolve on of those errors is very welcome too. >>>> >>>> >>>> Thanks in advance! >>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Tue Mar 27 14:24:35 2018 From: aron.helser at kitware.com (Aron Helser) Date: Tue, 27 Mar 2018 14:24:35 -0400 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: Jamil, Make sure you scroll up and find the first error - ninja is a parallel build system, so the build will continue on other threads after the first error. Then maybe you can solve that first error, and others will be fixed. It looks like an earlier error caused 'quat.lib' not to be built, but it's hard to tell.... -Aron On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich wrote: > Hi Shawn, > > thanks a lot for the tip, configuring worked with the Visual Studio 12.0 > compiler! Now I am getting a lot of build errors though. > > C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning > C4244: '=' : conversion from 'double' to 'float', possible loss of data > [255/256] Linking C shared library bin\hdf5.dll > Creating library bin\hdf5.lib and object bin\hdf5.exp > [256/256] Linking C shared library bin\hdf5_hl.dll > Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp > ninja: build stopped: subcommand failed. > > LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' > [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll > [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri > nt_messages.dir\vrpn_print_messages.C.obj > [5/97] Building CXX object client_src\CMakeFiles\ff_clien > t.dir\ff_client.C.obj > [6/97] Building CXX object client_src\CMakeFiles\phan_cli > ent.dir\phan_client.C.obj > [7/97] Building CXX object client_src\CMakeFiles\printval > s.dir\printvals.C.obj > ninja: build stopped: subcommand failed. > CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 > (message): > Failed with exit code 1 > > These are some examples. My it be possible that the ninja version is not > suited either? Do you know what ninja version you were building the > superbuild with? > > Thanks a lot, > Jamil > > (P.s. Sorry Shawn for my posting mistake) > > 2018-03-27 16:07 GMT+02:00 Shawn Waldon : > >> Hi Jamil, >> >> Please keep replies CCed to the mailing list (Reply All) so others can >> contribute to the discussion (or find answers to their own problems later >> in the archives). >> >> We use the most recent release of ninja on most of our build machines (so >> that one should work). I'm not sure why you are getting that error >> messages from what you have included... maybe others on the list can chime >> in or you can give more details. >> >> Shawn >> >> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < >> jamil.goettlich at gmail.com> wrote: >> >>> Hi Shawn, >>> >>> thanks a lot for the tip, configuring worked with the Visual Studio 12.0 >>> compiler! Now I am getting a lot of build errors though. >>> >>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>> [255/256] Linking C shared library bin\hdf5.dll >>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>> [256/256] Linking C shared library bin\hdf5_hl.dll >>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>> ninja: build stopped: subcommand failed. >>> >>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>> nt_messages.dir\vrpn_print_messages.C.obj >>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>> t.dir\ff_client.C.obj >>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>> ent.dir\phan_client.C.obj >>> [7/97] Building CXX object client_src\CMakeFiles\printval >>> s.dir\printvals.C.obj >>> ninja: build stopped: subcommand failed. >>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>> (message): >>> Failed with exit code 1 >>> >>> These are some examples. My it be possible that the ninja version is not >>> suited either? Do you know what ninja version you were building the >>> superbuild with? >>> >>> Thanks a lot, >>> Jamil >>> >>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >>> >>>> Hi Jamil, >>>> >>>> I'm not sure if this will get you all the way to a build, but here are >>>> some pointers: >>>> >>>> We build with the visual studio compiler but use the Ninja generator >>>> since it is significantly faster than VS. >>>> >>>> VS 2017 may not work. Our binaries are built with 2013 right now and >>>> we plan to move to 2015 after the current release cycle. If you want what >>>> you are building to be compatible with the Kitware binaries, you will need >>>> to use 2013. Also, I believe there are compiler errors if you use 2017 >>>> right now. >>>> >>>> To build with Ninja and VS compilers, you need to be in a visual studio >>>> command prompt rather than a normal shell (it sets a bunch of environment >>>> vars, which I think is what is missing in your last example). To convert a >>>> normal command prompt you run (example is for VS2015, your path may differ) >>>> 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64' >>>> in your shell and it will set the environment variables for you. If you >>>> have the environment set up before running cmake -G Ninja it should just >>>> pick the right compiler. >>>> >>>> HTH, >>>> >>>> Shawn >>>> >>>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >>>> jamil.goettlich at gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> I am having Problems building ParaView with ParaView-Superbuild. As >>>>> Visual Studio is not supported, I tried other build systems and compilers. >>>>> Unfortunately none of them succeeded. On the other hand I was able to build >>>>> small HelloWord programs with each of the combinations listed below and >>>>> without any errors. Here is what I did: >>>>> >>>>> First, I cloned from git: >>>>> git clone --recursive https://gitlab.kitware.com/par >>>>> aview/paraview-superbuild.git >>>>> Then cd paraview-superbuild and created new folder (build). >>>>> >>>>> The following cases did not work out (Doesnt matter if using Git Bash >>>>> or VS Command Prompt): >>>>> Build System: Ninja, Compiler: MinGW >>>>> command: cmake .. -G "Ninja" >>>>> Error: >>>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>>>> At least Visual Studio 9.0 is required >>>>> Call Stack (most recent call first): >>>>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>>>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>>>> >>>>> Although I have Visual Studio 15 2017 installed it does not seem to >>>>> work. >>>>> >>>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program >>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>> Error: >>>>> >>>>> The C compiler >>>>> "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools >>>>> /MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" >>>>> is not able to compile a simple test program. >>>>> It fails with the following output: >>>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>>>> "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>> \MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f >>>>> CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>>>> CMakeFiles\cmTC_008b4.dir\build >>>>> >>>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>>>> >>>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>>>> >>>>> testCCompiler.c >>>>> >>>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>>>> fatal error C1001: An internal error has occurred in the compiler. >>>>> >>>>> (compiler file 'msc1.cpp', line 1507) >>>>> >>>>> To work around this problem, try simplifying or changing the program >>>>> near the locations listed above. >>>>> >>>>> Please choose the Technical Support command on the Visual C++ >>>>> >>>>> Help menu, or open the Technical Support help file for more information >>>>> >>>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>>>> prompted to send an error report to Microsoft later. >>>>> >>>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code >>>>> '0x2' >>>>> >>>>> Stop. >>>>> >>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>>>> : return code '0x2' >>>>> >>>>> Stop. >>>>> >>>>> >>>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>> >>>>> Here, cmake recognized the compiler, but it throws another error >>>>> Error: >>>>> >>>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>>>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>>>> Could not find compiler set in environment variable RC: >>>>> rc. >>>>> Call Stack (most recent call first): >>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>> odules/Platform/Windows-MSVC.cmake:323 (enable_language) >>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>> odules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) >>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>> odules/CMakeCInformation.cmake:48 (include) >>>>> CMakeLists.txt:3 (project) >>>>> >>>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>>>> >>>>> >>>>> I am out of ideas now. >>>>> I would be really happy for a detailed build description as I am sure >>>>> I did not understand something properly. >>>>> >>>>> And every hint on how to resolve on of those errors is very welcome >>>>> too. >>>>> >>>>> >>>>> Thanks in advance! >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 27 22:44:53 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 27 Mar 2018 22:44:53 -0400 Subject: [Paraview] pvtu reader error In-Reply-To: References: Message-ID: Jamil, Could you provide some example data and exact steps to reproduce the issue you are seeing? Experimenting with a Sphere Source created when running ParaView in client/server mode with 2 server processes, I can save a .pvtp file that loads as expected in client/server mode, and operations like slicing work as expected. Thanks, Cory On Tue, Mar 20, 2018 at 10:09 AM, Jamil Appa via ParaView < paraview at public.kitware.com> wrote: > Hi > > I am trying to read a pvtu with Paraview 5.4.1 and getting an > unexpected behaviour. > > Using just the client the file reads as expected but when attempting to > read the same file in client server mode it reports the correct number of > cells but any subsequent operations like slice only act on the first piece > in the pvtu file. > > I can have a go at fixing the issue but need a pointer of where to > start looking. > > Thanks > > Jamil > > Example file generated by the VTK writer. > > > header_type="UInt32" compressor="vtkZLibDataCompressor"> > > > > > > > > > > > > > > > *Jamil Appa* | Co-Founder and Director | Zenotech > [image: Papercut] > [image: Tel:] +44 (0)7747 606 788 <+44%207747%20606788> [image: Zenotech > LTD - Simulation Unlimited] > [image: Email:] jamil.appa at zenotech.com > [image: Web:] www.zenotech.com > [image: Papercut] > [image: linkedin:] [image: > Twitter:] [image: Location:] > > > Company Registration No : 07926926 | VAT No : 128198591 > > Registered Office : 1 Larkfield Grove, Chepstow, Monmouthshire, NP16 5UF, > UK > > Address : Bristol & Bath Science Park, Dirac Cres, Emersons Green, Bristol > BS16 7FR > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 27 23:46:01 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 27 Mar 2018 23:46:01 -0400 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: <9E6857B4-4508-429C-A455-A3FE6B9BF8F4@sandia.gov> References: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> <9E6857B4-4508-429C-A455-A3FE6B9BF8F4@sandia.gov> Message-ID: Alan provided the new way to do this that works nicely and relieves you from having to clear ParaView's state and reload a state file. If you do want to clear ParaView's state and reload it with the new files, that will be possible in ParaView 5.5. When you load the state file through File -> Load State menu item, you will see the "Load State Options" dialog. Change the "Load State Data File Options" to "Choose File Names" and click on the ... toolbutton to navigate and select the file series. When you click OK, the new files will appear in the series. Cheers, Cory On Fri, Mar 23, 2018 at 6:48 PM, Scott, W Alan wrote: > OK, I think I figured this one out. Thanks for the example, that helped. > > > > When you load the state file, it will load exactly what was saved. There > is now an option in ParaView called File/ Reload Files. This will give you > the option to load only what was in the state file, or ?find new files? > that belong in this dataset. Click ?Find new files?. Note also that the > time counter is 0 based ? thus, there are now three timesteps, 0, 1 and 2 > (with the maxium being time step 2). > > > > So, I believe this is not a bug, but rather an issue with somewhat > modified features. > > > > Alan > > > > *From: *denis cohen > *Date: *Friday, March 23, 2018 at 3:05 PM > > *To: *W Scott > *Cc: *"paraview at public.kitware.com" > *Subject: *Re: [EXTERNAL] [Paraview] state file > > > > Hi Alan, > > Earlier 4.x.x versions of Paraview were able to read the number of vtu > files in the directory whether 2 or 1000 with the same pvsm file. > > Best, > > Denis > > > > On Fri, Mar 23, 2018 at 9:14 PM, Scott, W Alan wrote: > > Thanks Denis. > > > > I was able to open this state file up with 5.4.1, and 5.5.0-rc3. Both act > the same ? they only read two timesteps. What version of ParaView actually > read the three pvtu filesets? > > > > Alan > > > > *From: *denis cohen > *Date: *Monday, March 19, 2018 at 4:49 AM > *To: *W Scott > *Cc: *"paraview at public.kitware.com" > *Subject: *Re: [EXTERNAL] [Paraview] state file > > > > Hi Scott, > > Attach a small data set (sorry could not find smaller). The pvsm file was > created when the directory had 2 pvtu. The directory has now 3 pvtu files. > > Still after loading the pvsm file I don't have the 3 pvtu files in > paraview . > > Thanks for your help. > > Denis > > > > On Sat, Mar 17, 2018 at 12:57 AM, Scott, W Alan > wrote: > > Cory/Utkarsh, > > If a dataset grows, shouldn?t a state file open the new, whole dataset? > Utkarsh, is this an artifact of your work with datasets that live within a > directory? This is a bug, right? > > > > Dennis, > > Do you have a simple dataset, that is open, that I can attach to a bug > report, assuming this really is a bug? > > > > Alan > > > > > > > > *From: *ParaView on behalf of denis > cohen > *Date: *Wednesday, March 14, 2018 at 3:36 AM > *To: *"paraview at public.kitware.com" > *Subject: *[EXTERNAL] [Paraview] state file > > > > Hello, > > In past versions of paraview, opening a pvsm state file that read several > pvtu files resulted in paraview opening all the pvtu files in that > directory. Now it only opens the ones saved in the pvsm file. This is > annoying when the number of files has increased (like during a long time > dependent simulation) and when wanting to use the same pvsm state file. Any > ways of getting around that? > > Thank you > > Denis > > > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aguirre.utn at gmail.com Wed Mar 28 02:35:55 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Wed, 28 Mar 2018 08:35:55 +0200 Subject: [Paraview] 2D PLOT - AUTOMATIC AXIS TITLES Message-ID: Hello, I would like to know if there is a way to automatically set the axis titles in a 2d plot, based on the parameters already selected for the plot. In fact, in the GUI one has to select the X- and Y-axis parameters to be plotted. So, why not to set these names into the plot in an automatic fashion? Thanks in advance! Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: From grothausmann.roman at mh-hannover.de Wed Mar 28 04:36:12 2018 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Wed, 28 Mar 2018 10:36:12 +0200 Subject: [Paraview] unknown properties returned by ListProperties? In-Reply-To: References: <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de> <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de> <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de> <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de> <08497d6a-25de-4f1a-7215-dc63ed81198f@mh-hannover.de> <1ca3d0f9-164c-d094-7ba1-012eab54b41f@mh-hannover.de> Message-ID: <9f3e5db6-39ed-2b86-adcb-2b745eaf1bf4@mh-hannover.de> Dear Cory, On 27/03/18 16:18, Cory Quammen wrote: > I'm sorry I haven't had a chance to look at this further. Have you made any more > progress on this? I apologize for thinking it would be easy to hack ParaView to > better support loading multiple state files - it appears to be more difficult > than expected after all. Many thanks for your reply. No, problem at all. I am very thankful for Your support. As you give it for free, I've no expectation on response time or any help at all. Should I open a gitlab issue concerning the problem that the setting of representation properties does not seem to have any effect or is my code missing something obvious? I must admit that this is needing internals of PV that were not covered by the PV course I attended some years ago. Best Roman > On Tue, Mar 20, 2018 at 12:13 PM, Grothausmann, Roman Dr. > > > wrote: > > Many thanks Cory for your feedback. Not adding empty (None) properties did > not help > (http://github.com/romangrothausmann/ParaView_scripts/commit/d3af645dd1af2a > ). > Anyway, "ForceUseCache" has a vector of value 0 so it seems to me the actual > problem still is that ListProperties() returns properties that are not part > of the specific object that is calling ListProperties(). E.g. help(repr) > does not list a property called "ForceUseCache" but e.g. "Visibility" > > So I decided to only restore the property "Visibility" for a start: > http://github.com/romangrothausmann/ParaView_scripts/commit/d1c63f2682e834e > > Even though there is no error on execution any more, the resulting PVSM has > only the visibilities set for the last loaded PVSM, i.e. the setting of the > "Visibility" of representations loaded from former PVSMs did not have any > effect. > Is there a need to call some kind of Update() to make the property setting > have any effect? I tried some rendering > (http://github.com/romangrothausmann/ParaView_scripts/commit/294ff85a0cc7a > ), but > that did not help either. > > > On 20/03/18 06:12, Cory Quammen wrote: > > Roman, > > Looking at your original problem with the error: > > > ??? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 375, in SetPropertyWithName > ????? prop.SetData(arg) > ??? File > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > line 1296, in SetData > ????? self.SMProperty.AddProxy(value_proxy) > TypeError: AddProxy argument 1: method requires a VTK object > > > You are hitting this when attempting to set the DataAxesGrid, which is a > ProxyProperty. In your dictionary, this entry has value 'None', but it > looks like setting a property to value 'None' is not handled correctly > in servermanager.py. As a workaround, I suggest filtering out properties > from your dictionary that have 'None' as a value, i.e., do not add those > property values to your dictionary. > > HTH, > Cory > > On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr. > > >> wrote: > > ? ? Hi Cory, > > > ? ? Trying to find out what causes the former problems, I inserted a > line that > ? ? just sets the property that got collected so far: > https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59 > > > > > ? ? It already aborts on the first property encountered (ForceUseCache): > > ? ? 0x7f7b591fc250> > ? ? ForceUseCache 0 > ? ? Traceback (most recent call last): > ? ? ?? File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in > > ? ? ?? ? main() > ? ? ?? File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in main > ? ? ?? ? pvs.SetProperties(repr, **d) > ? ? ?? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", > ? ? line 567, in SetProperties > ? ? ?? ? raise AttributeError("object has no property %s" % param) > ? ? AttributeError: object has no property ForceUseCache > > ? ? Is ListProperties() returning properties that are not part of the > specific > ? ? object that is calling ListProperties()? > > ? ? Many thanks for any help or hints, > ? ? Roman > > ? ? On 21/12/17 16:06, Grothausmann, Roman Dr. wrote: > > ? ? ? ? Hi Cory, > > ? ? ? ? On 06/12/17 23:06, Cory Quammen wrote: > > ? ? ? ? ? ? Sorry I failed to follow up. Did you find a solution to > this problem? > > > ? ? ? ? Many thanks for your reply. No, and I'm still stuck. I tried Your > ? ? ? ? suggestion to remove [0] > > (https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd > > > >), > > ? ? ? ? which changed the reported error from: > > ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > ? ? ? ? line 375, in SetPropertyWithName > ? ? ? ? ????? prop.SetData(arg) > ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > ? ? ? ? line 803, in SetData > ? ? ? ? ????? raise RuntimeError("This property requires %d values." % > ? ? ? ? self.GetNumberOfElements()) > ? ? ? ? RuntimeError: This property requires 3 values. > > ? ? ? ? to: > > ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > ? ? ? ? line 375, in SetPropertyWithName > ? ? ? ? ????? prop.SetData(arg) > ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > ? ? ? ? line 1296, in SetData > ? ? ? ? ????? self.SMProperty.AddProxy(value_proxy) > ? ? ? ? TypeError: AddProxy argument 1: method requires a VTK object > > ? ? ? ? Any ideas on this? > ? ? ? ? Would You say it is a general problem in the py-code or could it be > ? ? ? ? caused by the content of the PVSMs I'm trying to combine? > > ? ? ? ? Many thanks for looking into this. > ? ? ? ? Roman > > > ? ? ? ? ? ? This line in your script looks funny to me: > > ? ? ? ? ? ? d[props] = pvs.GetProperty(repr, props[0]) > > ? ? ? ? ? ? Shouldn't props[0] just be props? > > ? ? ? ? ? ? Thanks, > ? ? ? ? ? ? Cory > > ? ? ? ? ? ? On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr. > ? ? ? ? ? ? > ? ? ? ? ? ? >> wrote: > > ? ? ? ? ? ? ? ? Dear Cory, > > ? ? ? ? ? ? ? ? On 15/09/17 15:27, Grothausmann, Roman Dr. wrote: > > > ? ? ? ? ? ? ? ? ? ? On 15/09/17 15:14, Cory Quammen wrote: > > > ? ? ? ? ? ? ? ? ? ? ? ? Put a ** in front of reppro[i], e.g., > > ? ? ? ? ? ? ? ? ? ? ? ? pvs.SetProperties(repr, **reppro[i]) > > > ? ? ? ? ? ? ? ? ? ? Hm, I now get: > ? ? ? ? ? ? ? ? ? ? TypeError: SetProperties() argument after ** must be a > ? ? ? ? ? ? ? ? ? ? mapping, not list > ? ? ? ? ? ? ? ? ? ? Do I have to store the dict of object properties in > another > ? ? ? ? ? ? ? ? ? ? dict instead > ? ? ? ? ? ? ? ? ? ? of a list? > > > > ? ? ? ? ? ? ? ? With a dict of dicts > https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e > > > > > > ? ? ? ? ? ? ? ? I get: > > ? ? ? ? ? ? ? ? ??? File > "/net/home/grothama/paraview/scripts/pvsm-multi.py", > ? ? ? ? ? ? ? ? line 64, in main > ? ? ? ? ? ? ? ? ????? pvs.SetProperties(repr, **reppro[i]); > ? ? ? ? ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py", > ? ? ? ? ? ? ? ? line 568, in SetProperties > ? ? ? ? ? ? ? ? ????? setattr(proxy, param, params[param]) > ? ? ? ? ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > ? ? ? ? ? ? ? ? line 317, in __setattr__ > ? ? ? ? ? ? ? ? ????? setter(self, value) > ? ? ? ? ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > ? ? ? ? ? ? ? ? line 2528, in setProperty > ? ? ? ? ? ? ? ? ????? return self.SetPropertyWithName(propName, value) > ? ? ? ? ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > ? ? ? ? ? ? ? ? line 375, in SetPropertyWithName > ? ? ? ? ? ? ? ? ????? prop.SetData(arg) > ? ? ? ? ? ? ? ? ??? File > > "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", > > ? ? ? ? ? ? ? ? line 803, in SetData > ? ? ? ? ? ? ? ? ????? raise RuntimeError("This property requires %d > values." % > ? ? ? ? ? ? ? ? self.GetNumberOfElements()) > ? ? ? ? ? ? ? ? RuntimeError: This property requires 3 values. > > ? ? ? ? ? ? ? ? Any ideas what could still be wrong? > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? On 07/09/17 23:37, Cory Quammen wrote: > > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Hi Roman, > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? It turns out ParaView was not designed > for this > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? use case because of > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? certain difficulties discussed here: > > https://gitlab.kitware.com/paraview/paraview/issues/17442 > > > > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? In your Python script, you could > manually cash > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? all the properties of > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? the existing representations and > restore them > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? after loading the most > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? recent state file. > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? The functions > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? reprs = GetRepresentations() > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? repr = reprs.values()[0] > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? props = repr.ListProperties() > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? GetProperty(repr, props[0]) > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? would be helpful for this. > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Cory > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? On Mon, Sep 4, 2017 at 8:42 AM, > Grothausmann, > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Roman Dr. > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > > >> wrote: > > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Dear mailing list members, > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? It seems that PV (and > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? paraview.simple.LoadState) by > default hides > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? already > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? loaded objects (and resets e.g. their > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? coloring) when another > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? state-file > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? is > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? loaded. > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Is there a way to load multiple > state-files > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? after one another without > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? hiding > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? and resetting already existent > objects? I.e. > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? a way to concatenate > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? multiple > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? state-files and leave their objects > in the > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? state as they got loaded > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? (e.g. > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? colored, hidden/visible)? > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? I do understand that loading a new > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? state-file will reset the camera, > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? but > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? not > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? the rest. > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Here's my initial attempt to > achieve this > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? with pvpython: > > > https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py > > > > > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Any help or hints are very much > appreciated > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Roman > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -- > ? ?Dr. Roman Grothausmann > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tomographie und Digitale > Bildverarbeitung > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tomography and Digital Image Analysis > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Medizinische Hochschule Hannover > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Institut f?r Funktionelle und > Angewandte > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Anatomie > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? OE 4120, Carl-Neuberg-Str. 1, 30625 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Hannover, Deutschland > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tel. +49 511 532-2900 > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > grothausmann.roman at mh-hannover.de > > > > http://www.mh-hannover.de/anatomie.html > > > > > > _______________________________________________ > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 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 > > > > > > > > > > > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? --? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Dr. Roman > Grothausmann > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tomographie und Digitale Bildverarbeitung > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tomography and Digital Image Analysis > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Medizinische Hochschule Hannover > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Institut f?r Funktionelle und Angewandte > Anatomie > ? ? ? ? ? ? ? ? ? ? ? ? ? ? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Deutschland > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tel. +49 511 532-2900 > > grothausmann.roman at mh-hannover.de > ? ? ? ? ? ? ? ? ? ? ? ? ? ? > > http://www.mh-hannover.de/anatomie.html > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? > > > > > > > > > ? ? ? ? ? ? ? ? --? ? ? ? ? ? ? ? ?Dr. Roman Grothausmann > > ? ? ? ? ? ? ? ? Tomographie und Digitale Bildverarbeitung > ? ? ? ? ? ? ? ? Tomography and Digital Image Analysis > > ? ? ? ? ? ? ? ? Medizinische Hochschule Hannover > ? ? ? ? ? ? ? ? Institut f?r Funktionelle und Angewandte Anatomie > ? ? ? ? ? ? ? ? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > ? ? ? ? ? ? ? ? Tel. +49 511 532-2900 > > grothausmann.roman at mh-hannover.de > ? ? ? ? ? ? ? ? > > http://www.mh-hannover.de/anatomie.html > > ? ? ? ? ? ? ? ? > > > > > > > > ? ? --? ? ?Dr. Roman Grothausmann > > ? ? Tomographie und Digitale Bildverarbeitung > ? ? Tomography and Digital Image Analysis > > ? ? Medizinische Hochschule Hannover > ? ? Institut f?r Funktionelle und Angewandte Anatomie > ? ? OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > ? ? Tel. +49 511 532-2900 > > grothausmann.roman at mh-hannover.de > > > > http://www.mh-hannover.de/anatomie.html > > ? ? > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > -- > Dr. Roman Grothausmann > > Tomographie und Digitale Bildverarbeitung > Tomography and Digital Image Analysis > > Medizinische Hochschule Hannover > Institut f?r Funktionelle und Angewandte Anatomie > OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland > > Tel. +49 511 532-2900 > grothausmann.roman at mh-hannover.de > http://www.mh-hannover.de/anatomie.html > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Medizinische Hochschule Hannover Institut f?r Funktionelle und Angewandte Anatomie OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland Tel. +49 511 532-2900 grothausmann.roman at mh-hannover.de http://www.mh-hannover.de/anatomie.html From Alexander.Stief at hs-aalen.de Wed Mar 28 07:20:36 2018 From: Alexander.Stief at hs-aalen.de (Stief, Alexander) Date: Wed, 28 Mar 2018 11:20:36 +0000 Subject: [Paraview] png image file size - screenshot vs animation Message-ID: <11BC40335FCF354D99B30918B180F5297A08AFCE@MAIL-1.htw-aalen.de> Hi, PV version is 5.4.1 when making a png screenshot in PV with a resolution of 3840x2160, the file size I get with default settings is ~1.4MB. This is due to the fact that around 80% of the image are plain white space. So far, so normal. However, when I create an animation and export to png images with the exact same default settings for image quality, the image file size for the exact same scene is ~28MB. Only when I dial down the image quality manually to around 60 the file size becomes similar to the png file from the screenshot. And the image quality is not visibly worse than with 100% setting. This must be some kind of bug, I never had this issue with previous versions. tl;dr: png image file size differs greatly between screenshot and animation with the exact same default settings. Regards Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Wed Mar 28 07:41:27 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Wed, 28 Mar 2018 13:41:27 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Hi Joachim, I downloaded the tar.gz file from https://www.paraview.org/download/, under the Release Candidates section. Regards, 2018-03-27 15:29 GMT+02:00 Joachim Pouderoux : > Carlos, > > What did you download exactly? The sources archive or the binaries? On > which platform? > > Best, > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2018-03-27 9:10 GMT-04:00 Carlos E Manglano-Villamarin < > carlosemanglanov at gmail.com>: > >> Joachim, >> >> Quick question about PV >= 5.5 RC1 ... I have downloaded the RC3, how do >> I install it? I cannot find any 'make' or 'install' file ... Is it provided >> to run "out of the box"? >> >> Regards, >> Carlos >> >> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < >> joachim.pouderoux at kitware.com>: >> >>> Carlos, >>> >>> OpenFOAM can produce cells with non planar faces which is not handled by >>> VTK/ParaView. Moreover it appears that current reader implementation can >>> also produce incorrect cells when reading wedge cells. >>> Thanks to a recent rewriting of the polydron clipping algorithm, the >>> clipping/slicing of polyhedron should no more lead to crashes. However,the >>> problems >>> of non planar faces might produce some holes in the result. >>> We are currently working on a patch to better handle this case in the >>> reader. >>> If you want to try the new polyhedron clipping algorithm, you will have >>> to use ParaView >= 5.5 RC1. >>> >>> Best regards, >>> Joachim >>> >>> >>> *Joachim Pouderoux*, PhD >>> >>> *Technical Expert - Scientific Computing Team* >>> *Kitware SAS * >>> >>> >>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >>> carlosemanglanov at gmail.com>: >>> >>>> It's me again, I'm sorry, >>>> >>>> Problem NOT solved!!! ... Hardware looks ok, software and system >>>> handling memory looks good too. >>>> >>>> ParaView shuts down if I try to generate a clip with the "VTK >>>> Polyhedron" option selected, before and after clipping ... >>>> >>>> possible bug?? >>>> >>>> C. >>>> >>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>> >>>>> Hi Carlos, >>>>> >>>>> That error message means that an exception was thrown from a Qt event >>>>> handler. The message about reimplementing QApplication::notify() is just >>>>> to tell you how to catch the exception if you wanted to. The real problem >>>>> is the exception. >>>>> >>>>> A std::bad_alloc exception happens when the program tries to allocate >>>>> memory and fails. So you need to figure out why you are running out of >>>>> memory (that is the most likely cause of the error). >>>>> >>>>> HTH, >>>>> Shawn >>>>> >>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>>> carlosemanglanov at gmail.com> wrote: >>>>> >>>>>> Hi everyone! >>>>>> >>>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>>> program crashes giving me the following error message: >>>>>> >>>>>> I/O : uncollated >>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>> what(): std::bad_alloc >>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>> >>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same >>>>>> error with Ubuntu 17.10 which I had installed until last night. >>>>>> >>>>>> I am looking for info about "reimplementing QApplication" with no >>>>>> luck. >>>>>> >>>>>> Any suggestions, please? >>>>>> Carlos >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlosemanglanov at gmail.com Wed Mar 28 07:55:13 2018 From: carlosemanglanov at gmail.com (Carlos E Manglano-Villamarin) Date: Wed, 28 Mar 2018 13:55:13 +0200 Subject: [Paraview] Paraview crashing when clipping an openfoam solution In-Reply-To: References: Message-ID: Hi again Joachim, I've tried to run ParaView from the executable 'paraview' in the 'bin' directory, and it works quite well. The OpenFOAM cases load pretty quickly, and the clip is done with no itches :-) For now, I just hace to create "by hand" the dummy *.foam file, but that's not a problem at all!! I just got one question at this time: Is it possible to load the cases with VTK Polyhedrons, this option is not shown in the GUI? I need to show the mesh 'as is', and right now it's all "dirty" with the sort-of-triangulation PV creates :-/ Best, 2018-03-28 13:41 GMT+02:00 Carlos E Manglano-Villamarin < carlosemanglanov at gmail.com>: > Hi Joachim, > > I downloaded the tar.gz file from https://www.paraview.org/download/, > under the Release Candidates section. > > Regards, > > 2018-03-27 15:29 GMT+02:00 Joachim Pouderoux < > joachim.pouderoux at kitware.com>: > >> Carlos, >> >> What did you download exactly? The sources archive or the binaries? On >> which platform? >> >> Best, >> >> *Joachim Pouderoux*, PhD >> >> *Technical Expert - Scientific Computing Team* >> *Kitware SAS * >> >> >> 2018-03-27 9:10 GMT-04:00 Carlos E Manglano-Villamarin < >> carlosemanglanov at gmail.com>: >> >>> Joachim, >>> >>> Quick question about PV >= 5.5 RC1 ... I have downloaded the RC3, how do >>> I install it? I cannot find any 'make' or 'install' file ... Is it provided >>> to run "out of the box"? >>> >>> Regards, >>> Carlos >>> >>> 2018-03-26 20:36 GMT+02:00 Joachim Pouderoux < >>> joachim.pouderoux at kitware.com>: >>> >>>> Carlos, >>>> >>>> OpenFOAM can produce cells with non planar faces which is not handled >>>> by VTK/ParaView. Moreover it appears that current reader implementation can >>>> also produce incorrect cells when reading wedge cells. >>>> Thanks to a recent rewriting of the polydron clipping algorithm, the >>>> clipping/slicing of polyhedron should no more lead to crashes. However,the >>>> problems >>>> of non planar faces might produce some holes in the result. >>>> We are currently working on a patch to better handle this case in the >>>> reader. >>>> If you want to try the new polyhedron clipping algorithm, you will >>>> have to use ParaView >= 5.5 RC1. >>>> >>>> Best regards, >>>> Joachim >>>> >>>> >>>> *Joachim Pouderoux*, PhD >>>> >>>> *Technical Expert - Scientific Computing Team* >>>> *Kitware SAS * >>>> >>>> >>>> 2018-03-26 14:29 GMT-04:00 Carlos E Manglano-Villamarin < >>>> carlosemanglanov at gmail.com>: >>>> >>>>> It's me again, I'm sorry, >>>>> >>>>> Problem NOT solved!!! ... Hardware looks ok, software and system >>>>> handling memory looks good too. >>>>> >>>>> ParaView shuts down if I try to generate a clip with the "VTK >>>>> Polyhedron" option selected, before and after clipping ... >>>>> >>>>> possible bug?? >>>>> >>>>> C. >>>>> >>>>> 2018-03-26 16:51 GMT+02:00 Shawn Waldon : >>>>> >>>>>> Hi Carlos, >>>>>> >>>>>> That error message means that an exception was thrown from a Qt event >>>>>> handler. The message about reimplementing QApplication::notify() is just >>>>>> to tell you how to catch the exception if you wanted to. The real problem >>>>>> is the exception. >>>>>> >>>>>> A std::bad_alloc exception happens when the program tries to allocate >>>>>> memory and fails. So you need to figure out why you are running out of >>>>>> memory (that is the most likely cause of the error). >>>>>> >>>>>> HTH, >>>>>> Shawn >>>>>> >>>>>> On Mon, Mar 26, 2018 at 10:47 AM, Carlos E Manglano-Villamarin < >>>>>> carlosemanglanov at gmail.com> wrote: >>>>>> >>>>>>> Hi everyone! >>>>>>> >>>>>>> When I postprocess some simulations, less than 900,000 cells, from >>>>>>> openfoam, either opening paraview directly or using the parafoam tool, the >>>>>>> program crashes giving me the following error message: >>>>>>> >>>>>>> I/O : uncollated >>>>>>> terminate called after throwing an instance of 'std::bad_alloc' >>>>>>> what(): std::bad_alloc >>>>>>> Qt has caught an exception thrown from an event handler. Throwing >>>>>>> exceptions from an event handler is not supported in Qt. You must >>>>>>> reimplement QApplication::notify() and catch all exceptions there. >>>>>>> >>>>>>> My OS is Ubuntu 16.04, freshly installed. I was getting the same >>>>>>> error with Ubuntu 17.10 which I had installed until last night. >>>>>>> >>>>>>> I am looking for info about "reimplementing QApplication" with no >>>>>>> luck. >>>>>>> >>>>>>> Any suggestions, please? >>>>>>> Carlos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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: >>>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamil.goettlich at gmail.com Wed Mar 28 08:23:14 2018 From: jamil.goettlich at gmail.com (Jamil Goettlich) Date: Wed, 28 Mar 2018 14:23:14 +0200 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: Hi Aron, thank you for the reply. Youre right, there was an error way at the beginning concerning quat.lib. It seems like linking vrpn.lib failed because quat.lib cannot be recognized. Here is the full error (Using Win10, Compiler Visual Studio12.0 (cl.exe), ninja build system. Also, I enabled VRPN_USE_HID and disabled VRPN_USE_LOCAL_HIDAPI). [157/254] Linking CXX shared library vrpn.dll FAILED: vrpn.dll vrpn.lib cmd.exe /C "cd . && C:\KermsInstalls\cmake\bin\cmake.exe -E vs_link_dll --intdir=CMakeFiles\vrpn.dir --manifests -- C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe /nologo CMakeFiles\vrpn.dir\vrpn_Analog.C.obj CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj CMakeFiles\vrpn.dir\vrpn_Button.C.obj CMakeFiles\vrpn.dir\vrpn_Connection.C.obj CMakeFiles\vrpn.dir\vrpn_Dial.C.obj CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj CMakeFiles\vrpn.dir\vrpn_FileController.C.obj CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj CMakeFiles\vrpn.dir\vrpn_Imager.C.obj CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj CMakeFiles\vrpn.dir\vrpn_Poser.C.obj CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." LINK: command "C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe /nologo CMakeFiles\vrpn.dir\vrpn_Analog.C.obj CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj CMakeFiles\vrpn.dir\vrpn_Button.C.obj CMakeFiles\vrpn.dir\vrpn_Connection.C.obj CMakeFiles\vrpn.dir\vrpn_Dial.C.obj CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj CMakeFiles\vrpn.dir\vrpn_FileController.C.obj CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj CMakeFiles\vrpn.dir\vrpn_Imager.C.obj CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj CMakeFiles\vrpn.dir\vrpn_Poser.C.obj CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:vrpn.dll.manifest" failed (exit code 1181) with the following output: LINK : fatal error LNK1181: cannot open input file 'quat\quat.lib' [158/254] Linking CXX shared library gpsnmealib\gpsnmea.dll I checked for quat.lib but there is only quat.dll in the superbuild folder. Is there a flag to set for building the quat library statically or to tell vrpn to look for a dll? Thank a lot Jamil 2018-03-27 20:24 GMT+02:00 Aron Helser : > Jamil, > Make sure you scroll up and find the first error - ninja is a parallel > build system, so the build will continue on other threads after the first > error. Then maybe you can solve that first error, and others will be fixed. > > It looks like an earlier error caused 'quat.lib' not to be built, but it's > hard to tell.... > -Aron > > On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich < > jamil.goettlich at gmail.com> wrote: > >> Hi Shawn, >> >> thanks a lot for the tip, configuring worked with the Visual Studio 12.0 >> compiler! Now I am getting a lot of build errors though. >> >> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >> C4244: '=' : conversion from 'double' to 'float', possible loss of data >> [255/256] Linking C shared library bin\hdf5.dll >> Creating library bin\hdf5.lib and object bin\hdf5.exp >> [256/256] Linking C shared library bin\hdf5_hl.dll >> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >> ninja: build stopped: subcommand failed. >> >> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >> nt_messages.dir\vrpn_print_messages.C.obj >> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >> t.dir\ff_client.C.obj >> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >> ent.dir\phan_client.C.obj >> [7/97] Building CXX object client_src\CMakeFiles\printval >> s.dir\printvals.C.obj >> ninja: build stopped: subcommand failed. >> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >> (message): >> Failed with exit code 1 >> >> These are some examples. My it be possible that the ninja version is not >> suited either? Do you know what ninja version you were building the >> superbuild with? >> >> Thanks a lot, >> Jamil >> >> (P.s. Sorry Shawn for my posting mistake) >> >> 2018-03-27 16:07 GMT+02:00 Shawn Waldon : >> >>> Hi Jamil, >>> >>> Please keep replies CCed to the mailing list (Reply All) so others can >>> contribute to the discussion (or find answers to their own problems later >>> in the archives). >>> >>> We use the most recent release of ninja on most of our build machines >>> (so that one should work). I'm not sure why you are getting that error >>> messages from what you have included... maybe others on the list can chime >>> in or you can give more details. >>> >>> Shawn >>> >>> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < >>> jamil.goettlich at gmail.com> wrote: >>> >>>> Hi Shawn, >>>> >>>> thanks a lot for the tip, configuring worked with the Visual Studio >>>> 12.0 compiler! Now I am getting a lot of build errors though. >>>> >>>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>>> [255/256] Linking C shared library bin\hdf5.dll >>>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>>> [256/256] Linking C shared library bin\hdf5_hl.dll >>>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>>> ninja: build stopped: subcommand failed. >>>> >>>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>>> nt_messages.dir\vrpn_print_messages.C.obj >>>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>>> t.dir\ff_client.C.obj >>>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>>> ent.dir\phan_client.C.obj >>>> [7/97] Building CXX object client_src\CMakeFiles\printval >>>> s.dir\printvals.C.obj >>>> ninja: build stopped: subcommand failed. >>>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>>> (message): >>>> Failed with exit code 1 >>>> >>>> These are some examples. My it be possible that the ninja version is >>>> not suited either? Do you know what ninja version you were building the >>>> superbuild with? >>>> >>>> Thanks a lot, >>>> Jamil >>>> >>>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >>>> >>>>> Hi Jamil, >>>>> >>>>> I'm not sure if this will get you all the way to a build, but here are >>>>> some pointers: >>>>> >>>>> We build with the visual studio compiler but use the Ninja generator >>>>> since it is significantly faster than VS. >>>>> >>>>> VS 2017 may not work. Our binaries are built with 2013 right now and >>>>> we plan to move to 2015 after the current release cycle. If you want what >>>>> you are building to be compatible with the Kitware binaries, you will need >>>>> to use 2013. Also, I believe there are compiler errors if you use 2017 >>>>> right now. >>>>> >>>>> To build with Ninja and VS compilers, you need to be in a visual >>>>> studio command prompt rather than a normal shell (it sets a bunch of >>>>> environment vars, which I think is what is missing in your last example). >>>>> To convert a normal command prompt you run (example is for VS2015, your >>>>> path may differ) 'C:/Program Files (x86)/Microsoft Visual Studio >>>>> 14.0/VC/vcvarsall.bat x64' in your shell and it will set the environment >>>>> variables for you. If you have the environment set up before running cmake >>>>> -G Ninja it should just pick the right compiler. >>>>> >>>>> HTH, >>>>> >>>>> Shawn >>>>> >>>>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >>>>> jamil.goettlich at gmail.com> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I am having Problems building ParaView with ParaView-Superbuild. As >>>>>> Visual Studio is not supported, I tried other build systems and compilers. >>>>>> Unfortunately none of them succeeded. On the other hand I was able to build >>>>>> small HelloWord programs with each of the combinations listed below and >>>>>> without any errors. Here is what I did: >>>>>> >>>>>> First, I cloned from git: >>>>>> git clone --recursive https://gitlab.kitware.com/par >>>>>> aview/paraview-superbuild.git >>>>>> Then cd paraview-superbuild and created new folder (build). >>>>>> >>>>>> The following cases did not work out (Doesnt matter if using Git Bash >>>>>> or VS Command Prompt): >>>>>> Build System: Ninja, Compiler: MinGW >>>>>> command: cmake .. -G "Ninja" >>>>>> Error: >>>>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>>>>> At least Visual Studio 9.0 is required >>>>>> Call Stack (most recent call first): >>>>>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>>>>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>>>>> >>>>>> Although I have Visual Studio 15 2017 installed it does not seem to >>>>>> work. >>>>>> >>>>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>> Error: >>>>>> >>>>>> The C compiler >>>>>> "C:/Program Files (x86)/Microsoft Visual >>>>>> Studio/2017/Community/VC/Tools/MSVC/14.12.25827/bin/Hostx86/ >>>>>> x64/cl.exe" >>>>>> is not able to compile a simple test program. >>>>>> It fails with the following output: >>>>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>>>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>>>>> "C:\Program Files (x86)\Microsoft Visual >>>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" >>>>>> -f CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>>>>> CMakeFiles\cmTC_008b4.dir\build >>>>>> >>>>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>>>>> >>>>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>>>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>>>>> >>>>>> testCCompiler.c >>>>>> >>>>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>>>>> fatal error C1001: An internal error has occurred in the compiler. >>>>>> >>>>>> (compiler file 'msc1.cpp', line 1507) >>>>>> >>>>>> To work around this problem, try simplifying or changing the program >>>>>> near the locations listed above. >>>>>> >>>>>> Please choose the Technical Support command on the Visual C++ >>>>>> >>>>>> Help menu, or open the Technical Support help file for more >>>>>> information >>>>>> >>>>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>>>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>>>>> prompted to send an error report to Microsoft later. >>>>>> >>>>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>>>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code >>>>>> '0x2' >>>>>> >>>>>> Stop. >>>>>> >>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >>>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>>>>> : return code '0x2' >>>>>> >>>>>> Stop. >>>>>> >>>>>> >>>>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>> >>>>>> Here, cmake recognized the compiler, but it throws another error >>>>>> Error: >>>>>> >>>>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>>>>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>>>>> Could not find compiler set in environment variable RC: >>>>>> rc. >>>>>> Call Stack (most recent call first): >>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>> odules/Platform/Windows-MSVC.cmake:323 (enable_language) >>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>> odules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) >>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>> odules/CMakeCInformation.cmake:48 (include) >>>>>> CMakeLists.txt:3 (project) >>>>>> >>>>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>>>>> >>>>>> >>>>>> I am out of ideas now. >>>>>> I would be really happy for a detailed build description as I am sure >>>>>> I did not understand something properly. >>>>>> >>>>>> And every hint on how to resolve on of those errors is very welcome >>>>>> too. >>>>>> >>>>>> >>>>>> Thanks in advance! >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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: >>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 28 09:41:33 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Mar 2018 09:41:33 -0400 Subject: [Paraview] 2D PLOT - AUTOMATIC AXIS TITLES In-Reply-To: References: Message-ID: There isn't an automatic way of setting the titles. We don't automatically set the titles since one can plot multiple variables on Y axis, which is very typical, and hence it's unclear what the automatic name should be. Utkarsh On Wed, Mar 28, 2018 at 2:35 AM, Miguel Aguirre wrote: > Hello, > > I would like to know if there is a way to automatically set the axis titles > in a 2d plot, based on the parameters already selected for the plot. In > fact, in the GUI one has to select the X- and Y-axis parameters to be > plotted. So, why not to set these names into the plot in an automatic > fashion? > > Thanks in advance! > > Miguel Angel AGUIRRE > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Mar 28 09:46:30 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Mar 2018 09:46:30 -0400 Subject: [Paraview] VRML animation In-Reply-To: References: Message-ID: To the best of my knowledge, this is not supported currently. Utkarsh On Thu, Mar 22, 2018 at 2:14 PM, GeorgeP S wrote: > Hello all, > > i would like to ask how is it possible to export in vrml but retain the > animation acquired from the models simulation.Is there a specific feature > that i have not found out yet about this kind of thing? > > Thank you! > > > Mail > priva di virus. www.avast.com > > <#m_-1156303584899477793_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 28 09:49:07 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Mar 2018 09:49:07 -0400 Subject: [Paraview] Visualization of parcels in paraview without surface In-Reply-To: References: Message-ID: It's unclear what you're trying to do. If you can share a sample dataset, maybe that'll help. If all your data is coming from the same datasource, may splitting it up into the surface and spray parcels will let you control opacity. Filters like Extract Block, Threshold, Clip, etc can be used to do that -- but depends on your data characteristics. Utkarsh On Tue, Mar 20, 2018 at 3:48 PM, Nitisha Ahuja wrote: > Hello all, > I am trying to visualize a spray simulation in paraview. The problem that > I am facing is as soon as I make the surface completely transparent to look > at the spray parcels, spray parcels also disappear, as shown below. > > How can I visualize these parcels without surface showing in Paraview > > Best regards > Nitisha > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 58548 bytes Desc: not available URL: From salachoris1 at gmail.com Wed Mar 28 10:19:20 2018 From: salachoris1 at gmail.com (GeorgeP S) Date: Wed, 28 Mar 2018 16:19:20 +0200 Subject: [Paraview] VRML animation In-Reply-To: References: Message-ID: Thank you very much for the responce. To your knowledge which program can do a vrml animation by a .vtp file? Thank you again, Salachoris Georgios Panagiotis On Wed, Mar 28, 2018 at 3:46 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > To the best of my knowledge, this is not supported currently. > > Utkarsh > > On Thu, Mar 22, 2018 at 2:14 PM, GeorgeP S wrote: > >> Hello all, >> >> i would like to ask how is it possible to export in vrml but retain the >> animation acquired from the models simulation.Is there a specific feature >> that i have not found out yet about this kind of thing? >> >> Thank you! >> >> >> Mail >> priva di virus. www.avast.com >> >> <#m_-2886712227971363020_m_-1156303584899477793_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Mar 28 10:32:01 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 28 Mar 2018 08:32:01 -0600 Subject: [Paraview] VRML animation In-Reply-To: References: Message-ID: May I ask why VRML? Are you trying to do a time animation of geometry+data/color on the web? What I'm trying to say is that often by narrowing the question you get a perfect answer for it but not a good one for truly solving your problem. So what are you trying to do/solve? Thanks, Seb On Wed, Mar 28, 2018 at 8:19 AM, GeorgeP S wrote: > Thank you very much for the responce. To your knowledge which program can > do a vrml animation by a .vtp file? > > Thank you again, > Salachoris Georgios Panagiotis > > On Wed, Mar 28, 2018 at 3:46 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> To the best of my knowledge, this is not supported currently. >> >> Utkarsh >> >> On Thu, Mar 22, 2018 at 2:14 PM, GeorgeP S wrote: >> >>> Hello all, >>> >>> i would like to ask how is it possible to export in vrml but retain the >>> animation acquired from the models simulation.Is there a specific feature >>> that i have not found out yet about this kind of thing? >>> >>> Thank you! >>> >>> >>> Mail >>> priva di virus. www.avast.com >>> >>> <#m_5815021470817030596_m_-2886712227971363020_m_-1156303584899477793_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Wed Mar 28 10:42:01 2018 From: aron.helser at kitware.com (Aron Helser) Date: Wed, 28 Mar 2018 10:42:01 -0400 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: I don't know how or why vrpn is used by paraview, so I'll have to defer to others... On Wed, Mar 28, 2018 at 8:23 AM, Jamil Goettlich wrote: > Hi Aron, > > thank you for the reply. Youre right, there was an error way at the > beginning concerning quat.lib. > It seems like linking vrpn.lib failed because quat.lib cannot be > recognized. > Here is the full error (Using Win10, Compiler Visual Studio12.0 (cl.exe), > ninja build system. > Also, I enabled VRPN_USE_HID and disabled VRPN_USE_LOCAL_HIDAPI). > > [157/254] Linking CXX shared library vrpn.dll > FAILED: vrpn.dll vrpn.lib > cmd.exe /C "cd . && C:\KermsInstalls\cmake\bin\cmake.exe -E vs_link_dll > --intdir=CMakeFiles\vrpn.dir --manifests -- C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe > /nologo CMakeFiles\vrpn.dir\vrpn_Analog.C.obj CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj > CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj > CMakeFiles\vrpn.dir\vrpn_Button.C.obj CMakeFiles\vrpn.dir\vrpn_Connection.C.obj > CMakeFiles\vrpn.dir\vrpn_Dial.C.obj CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj > CMakeFiles\vrpn.dir\vrpn_FileController.C.obj CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj > CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj > CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj CMakeFiles\vrpn.dir\vrpn_Imager.C.obj > CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj > CMakeFiles\vrpn.dir\vrpn_Poser.C.obj CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj > CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj > CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj > CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj > CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib > /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib > ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib > shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && > cd ." > LINK: command "C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe /nologo > CMakeFiles\vrpn.dir\vrpn_Analog.C.obj CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj > CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj > CMakeFiles\vrpn.dir\vrpn_Button.C.obj CMakeFiles\vrpn.dir\vrpn_Connection.C.obj > CMakeFiles\vrpn.dir\vrpn_Dial.C.obj CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj > CMakeFiles\vrpn.dir\vrpn_FileController.C.obj CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj > CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj > CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj CMakeFiles\vrpn.dir\vrpn_Imager.C.obj > CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj > CMakeFiles\vrpn.dir\vrpn_Poser.C.obj CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj > CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj > CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj > CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj > CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib > /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib > ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib > shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib > /MANIFEST /MANIFESTFILE:vrpn.dll.manifest" failed (exit code 1181) with > the following output: > LINK : fatal error LNK1181: cannot open input file 'quat\quat.lib' > [158/254] Linking CXX shared library gpsnmealib\gpsnmea.dll > > I checked for quat.lib but there is only quat.dll in the superbuild > folder. Is there a flag to set for building the quat library statically or > to tell vrpn to look for a dll? > > Thank a lot > Jamil > > 2018-03-27 20:24 GMT+02:00 Aron Helser : > >> Jamil, >> Make sure you scroll up and find the first error - ninja is a parallel >> build system, so the build will continue on other threads after the first >> error. Then maybe you can solve that first error, and others will be fixed. >> >> It looks like an earlier error caused 'quat.lib' not to be built, but >> it's hard to tell.... >> -Aron >> >> On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich < >> jamil.goettlich at gmail.com> wrote: >> >>> Hi Shawn, >>> >>> thanks a lot for the tip, configuring worked with the Visual Studio 12.0 >>> compiler! Now I am getting a lot of build errors though. >>> >>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>> [255/256] Linking C shared library bin\hdf5.dll >>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>> [256/256] Linking C shared library bin\hdf5_hl.dll >>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>> ninja: build stopped: subcommand failed. >>> >>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>> nt_messages.dir\vrpn_print_messages.C.obj >>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>> t.dir\ff_client.C.obj >>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>> ent.dir\phan_client.C.obj >>> [7/97] Building CXX object client_src\CMakeFiles\printval >>> s.dir\printvals.C.obj >>> ninja: build stopped: subcommand failed. >>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>> (message): >>> Failed with exit code 1 >>> >>> These are some examples. My it be possible that the ninja version is not >>> suited either? Do you know what ninja version you were building the >>> superbuild with? >>> >>> Thanks a lot, >>> Jamil >>> >>> (P.s. Sorry Shawn for my posting mistake) >>> >>> 2018-03-27 16:07 GMT+02:00 Shawn Waldon : >>> >>>> Hi Jamil, >>>> >>>> Please keep replies CCed to the mailing list (Reply All) so others can >>>> contribute to the discussion (or find answers to their own problems later >>>> in the archives). >>>> >>>> We use the most recent release of ninja on most of our build machines >>>> (so that one should work). I'm not sure why you are getting that error >>>> messages from what you have included... maybe others on the list can chime >>>> in or you can give more details. >>>> >>>> Shawn >>>> >>>> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < >>>> jamil.goettlich at gmail.com> wrote: >>>> >>>>> Hi Shawn, >>>>> >>>>> thanks a lot for the tip, configuring worked with the Visual Studio >>>>> 12.0 compiler! Now I am getting a lot of build errors though. >>>>> >>>>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>>>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>>>> [255/256] Linking C shared library bin\hdf5.dll >>>>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>>>> [256/256] Linking C shared library bin\hdf5_hl.dll >>>>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>>>> ninja: build stopped: subcommand failed. >>>>> >>>>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>>>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>>>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>>>> nt_messages.dir\vrpn_print_messages.C.obj >>>>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>>>> t.dir\ff_client.C.obj >>>>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>>>> ent.dir\phan_client.C.obj >>>>> [7/97] Building CXX object client_src\CMakeFiles\printval >>>>> s.dir\printvals.C.obj >>>>> ninja: build stopped: subcommand failed. >>>>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>>>> (message): >>>>> Failed with exit code 1 >>>>> >>>>> These are some examples. My it be possible that the ninja version is >>>>> not suited either? Do you know what ninja version you were building the >>>>> superbuild with? >>>>> >>>>> Thanks a lot, >>>>> Jamil >>>>> >>>>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >>>>> >>>>>> Hi Jamil, >>>>>> >>>>>> I'm not sure if this will get you all the way to a build, but here >>>>>> are some pointers: >>>>>> >>>>>> We build with the visual studio compiler but use the Ninja generator >>>>>> since it is significantly faster than VS. >>>>>> >>>>>> VS 2017 may not work. Our binaries are built with 2013 right now and >>>>>> we plan to move to 2015 after the current release cycle. If you want what >>>>>> you are building to be compatible with the Kitware binaries, you will need >>>>>> to use 2013. Also, I believe there are compiler errors if you use 2017 >>>>>> right now. >>>>>> >>>>>> To build with Ninja and VS compilers, you need to be in a visual >>>>>> studio command prompt rather than a normal shell (it sets a bunch of >>>>>> environment vars, which I think is what is missing in your last example). >>>>>> To convert a normal command prompt you run (example is for VS2015, your >>>>>> path may differ) 'C:/Program Files (x86)/Microsoft Visual Studio >>>>>> 14.0/VC/vcvarsall.bat x64' in your shell and it will set the environment >>>>>> variables for you. If you have the environment set up before running cmake >>>>>> -G Ninja it should just pick the right compiler. >>>>>> >>>>>> HTH, >>>>>> >>>>>> Shawn >>>>>> >>>>>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >>>>>> jamil.goettlich at gmail.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am having Problems building ParaView with ParaView-Superbuild. As >>>>>>> Visual Studio is not supported, I tried other build systems and compilers. >>>>>>> Unfortunately none of them succeeded. On the other hand I was able to build >>>>>>> small HelloWord programs with each of the combinations listed below and >>>>>>> without any errors. Here is what I did: >>>>>>> >>>>>>> First, I cloned from git: >>>>>>> git clone --recursive https://gitlab.kitware.com/par >>>>>>> aview/paraview-superbuild.git >>>>>>> Then cd paraview-superbuild and created new folder (build). >>>>>>> >>>>>>> The following cases did not work out (Doesnt matter if using Git >>>>>>> Bash or VS Command Prompt): >>>>>>> Build System: Ninja, Compiler: MinGW >>>>>>> command: cmake .. -G "Ninja" >>>>>>> Error: >>>>>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>>>>>> At least Visual Studio 9.0 is required >>>>>>> Call Stack (most recent call first): >>>>>>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>>>>>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>>>>>> >>>>>>> Although I have Visual Studio 15 2017 installed it does not seem to >>>>>>> work. >>>>>>> >>>>>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>>> Error: >>>>>>> >>>>>>> The C compiler >>>>>>> "C:/Program Files (x86)/Microsoft Visual >>>>>>> Studio/2017/Community/VC/Tools/MSVC/14.12.25827/bin/Hostx86/ >>>>>>> x64/cl.exe" >>>>>>> is not able to compile a simple test program. >>>>>>> It fails with the following output: >>>>>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>>>>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>>>>>> "C:\Program Files (x86)\Microsoft Visual >>>>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" >>>>>>> -f CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>>>>>> CMakeFiles\cmTC_008b4.dir\build >>>>>>> >>>>>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>>>>>> >>>>>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>>>>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>>>>>> >>>>>>> testCCompiler.c >>>>>>> >>>>>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>>>>>> fatal error C1001: An internal error has occurred in the compiler. >>>>>>> >>>>>>> (compiler file 'msc1.cpp', line 1507) >>>>>>> >>>>>>> To work around this problem, try simplifying or changing the program >>>>>>> near the locations listed above. >>>>>>> >>>>>>> Please choose the Technical Support command on the Visual C++ >>>>>>> >>>>>>> Help menu, or open the Technical Support help file for more >>>>>>> information >>>>>>> >>>>>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>>>>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>>>>>> prompted to send an error report to Microsoft later. >>>>>>> >>>>>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>>>>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return >>>>>>> code '0x2' >>>>>>> >>>>>>> Stop. >>>>>>> >>>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >>>>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>>>>>> : return code '0x2' >>>>>>> >>>>>>> Stop. >>>>>>> >>>>>>> >>>>>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>>> >>>>>>> Here, cmake recognized the compiler, but it throws another error >>>>>>> Error: >>>>>>> >>>>>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>>>>>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>>>>>> Could not find compiler set in environment variable RC: >>>>>>> rc. >>>>>>> Call Stack (most recent call first): >>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>> odules/Platform/Windows-MSVC.cmake:323 (enable_language) >>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>> odules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) >>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>> odules/CMakeCInformation.cmake:48 (include) >>>>>>> CMakeLists.txt:3 (project) >>>>>>> >>>>>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>>>>>> >>>>>>> >>>>>>> I am out of ideas now. >>>>>>> I would be really happy for a detailed build description as I am >>>>>>> sure I did not understand something properly. >>>>>>> >>>>>>> And every hint on how to resolve on of those errors is very welcome >>>>>>> too. >>>>>>> >>>>>>> >>>>>>> Thanks in advance! >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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: >>>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Mar 28 10:50:35 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 28 Mar 2018 08:50:35 -0600 Subject: [Paraview] VRML animation In-Reply-To: References: Message-ID: Putting back the mailing list as other could provide an actual answer to your "immersive question". ParaView can do immersive animation but that would be managed within ParaView. So I'm still not sure to understand what you are trying to do. But maybe other on the mailing list may do... Seb On Wed, Mar 28, 2018 at 8:38 AM, GeorgeP S wrote: > I am trying to set up an environment where i can enter "inside" the > simulation and visualize the animation and the results on a height of eye > level. > Due to the fact that i saw articles about immersive paraview i thought it > could export also the animation. > > Thank you again for the responce, > Salachoris Georgios Panagiotis > > On Wed, Mar 28, 2018 at 4:32 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> May I ask why VRML? Are you trying to do a time animation of >> geometry+data/color on the web? >> What I'm trying to say is that often by narrowing the question you get a >> perfect answer for it but not a good one for truly solving your problem. >> So what are you trying to do/solve? >> >> Thanks, >> >> Seb >> >> On Wed, Mar 28, 2018 at 8:19 AM, GeorgeP S wrote: >> >>> Thank you very much for the responce. To your knowledge which program >>> can do a vrml animation by a .vtp file? >>> >>> Thank you again, >>> Salachoris Georgios Panagiotis >>> >>> On Wed, Mar 28, 2018 at 3:46 PM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> To the best of my knowledge, this is not supported currently. >>>> >>>> Utkarsh >>>> >>>> On Thu, Mar 22, 2018 at 2:14 PM, GeorgeP S >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> i would like to ask how is it possible to export in vrml but retain >>>>> the animation acquired from the models simulation.Is there a specific >>>>> feature that i have not found out yet about this kind of thing? >>>>> >>>>> Thank you! >>>>> >>>>> >>>>> Mail >>>>> priva di virus. www.avast.com >>>>> >>>>> <#m_3492283369435919282_m_-8827445642746360931_m_5815021470817030596_m_-2886712227971363020_m_-1156303584899477793_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Mar 28 10:51:21 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 28 Mar 2018 10:51:21 -0400 Subject: [Paraview] Empty lib/python2.7/lib-dynload In-Reply-To: References: Message-ID: Hi Santiago, Thanks for the report. It looks like readline is not being included in the packaging. I looked briefly in the ParaView superbuild repository to find out why, but did not see the reason immediately. I have filed an issue for this: https://gitlab.kitware.com/paraview/paraview-superbuild/issues/70 Best regards, Cory On Thu, Mar 8, 2018 at 12:02 AM, Santiago Serebrinsky < sserebrinsky at gmail.com> wrote: > I am under Ubuntu 16.04 LTS. > > I have currently two versions of Paraview: > 1. Paraview 5.0.1, installed with apt-get. It is using Python 2.7.12. > 2. ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit, simply expanded. It uses > Python 2.7.11. > > When I use version 2 of pvpython (~/apps/ParaView-5.4.1-Qt5- > OpenGL2-MPI-Linux-64bit/bin/pvpython) I get the error > > import readline > ImportError: No module named readline > > from my ~/.pythonrc. > > In version 1 of pvpython, readline resides in > /usr/lib/python2.7/lib-dynload > >>> readline.__file__ > '/usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so' > . > In version 2 readline is not present anywhere in ~/apps/ParaView-5.4.1-Qt5- > OpenGL2-MPI-Linux-64bit/ > > Why is this? > Can it be fixed? > > PS: directory ~/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/lib-dynload > (where I expected to find readline given version 1) is empty. > Many of the modules which in version 1 reside in /usr/lib/python2.7/lib-dynload, > are present in lib/python2.7, not in lib/python2.7/lib-dynload, in version2: > > >>> import parser > >>> parser.__file__ > '/home/santiago/apps/ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux- > 64bit/lib/python2.7/parser.so' > > But readline is an exception here. > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aguirre.utn at gmail.com Wed Mar 28 10:53:58 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Wed, 28 Mar 2018 16:53:58 +0200 Subject: [Paraview] 2D PLOT - AUTOMATIC AXIS TITLES In-Reply-To: References: Message-ID: Hello, Thanks for your quick answer. I agree with the fact that multiple plots superimposed may difficult the automatic setup. However, I think that it could be a good idea to automatize at least the X-axis label, because there is only one variable accepted for this axis in the setup. Is there a way to add this option by a Programmable Filter? Thanks again, Miguel On Wed, Mar 28, 2018 at 3:41 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > There isn't an automatic way of setting the titles. We don't > automatically set the titles since one can plot multiple variables on > Y axis, which is very typical, and hence it's unclear what the > automatic name should be. > > Utkarsh > > On Wed, Mar 28, 2018 at 2:35 AM, Miguel Aguirre > wrote: > > Hello, > > > > I would like to know if there is a way to automatically set the axis > titles > > in a 2d plot, based on the parameters already selected for the plot. In > > fact, in the GUI one has to select the X- and Y-axis parameters to be > > plotted. So, why not to set these names into the plot in an automatic > > fashion? > > > > Thanks in advance! > > > > Miguel Angel AGUIRRE > > > > > > > > _______________________________________________ > > 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: > > https://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Wed Mar 28 11:00:37 2018 From: denis.cohen at gmail.com (denis cohen) Date: Wed, 28 Mar 2018 17:00:37 +0200 Subject: [Paraview] [EXTERNAL] state file In-Reply-To: References: <42B66B4B-D8D9-4B62-B9EF-64DFE1601501@sandia.gov> <4A7068A3-9D6E-4E7A-BAA8-663746831685@sandia.gov> <9E6857B4-4508-429C-A455-A3FE6B9BF8F4@sandia.gov> Message-ID: Hi Cory, Thanks. I look forward to the new version. Best, Denis On Wed, Mar 28, 2018 at 5:46 AM, Cory Quammen wrote: > Alan provided the new way to do this that works nicely and relieves you > from having to clear ParaView's state and reload a state file. > > If you do want to clear ParaView's state and reload it with the new files, > that will be possible in ParaView 5.5. When you load the state file through > File -> Load State menu item, you will see the "Load State Options" dialog. > Change the "Load State Data File Options" to "Choose File Names" and click > on the ... toolbutton to navigate and select the file series. When you > click OK, the new files will appear in the series. > > Cheers, > Cory > > On Fri, Mar 23, 2018 at 6:48 PM, Scott, W Alan wrote: > >> OK, I think I figured this one out. Thanks for the example, that helped. >> >> >> >> When you load the state file, it will load exactly what was saved. There >> is now an option in ParaView called File/ Reload Files. This will give you >> the option to load only what was in the state file, or ?find new files? >> that belong in this dataset. Click ?Find new files?. Note also that the >> time counter is 0 based ? thus, there are now three timesteps, 0, 1 and 2 >> (with the maxium being time step 2). >> >> >> >> So, I believe this is not a bug, but rather an issue with somewhat >> modified features. >> >> >> >> Alan >> >> >> >> *From: *denis cohen >> *Date: *Friday, March 23, 2018 at 3:05 PM >> >> *To: *W Scott >> *Cc: *"paraview at public.kitware.com" >> *Subject: *Re: [EXTERNAL] [Paraview] state file >> >> >> >> Hi Alan, >> >> Earlier 4.x.x versions of Paraview were able to read the number of vtu >> files in the directory whether 2 or 1000 with the same pvsm file. >> >> Best, >> >> Denis >> >> >> >> On Fri, Mar 23, 2018 at 9:14 PM, Scott, W Alan >> wrote: >> >> Thanks Denis. >> >> >> >> I was able to open this state file up with 5.4.1, and 5.5.0-rc3. Both >> act the same ? they only read two timesteps. What version of ParaView >> actually read the three pvtu filesets? >> >> >> >> Alan >> >> >> >> *From: *denis cohen >> *Date: *Monday, March 19, 2018 at 4:49 AM >> *To: *W Scott >> *Cc: *"paraview at public.kitware.com" >> *Subject: *Re: [EXTERNAL] [Paraview] state file >> >> >> >> Hi Scott, >> >> Attach a small data set (sorry could not find smaller). The pvsm file was >> created when the directory had 2 pvtu. The directory has now 3 pvtu files. >> >> Still after loading the pvsm file I don't have the 3 pvtu files in >> paraview . >> >> Thanks for your help. >> >> Denis >> >> >> >> On Sat, Mar 17, 2018 at 12:57 AM, Scott, W Alan >> wrote: >> >> Cory/Utkarsh, >> >> If a dataset grows, shouldn?t a state file open the new, whole dataset? >> Utkarsh, is this an artifact of your work with datasets that live within a >> directory? This is a bug, right? >> >> >> >> Dennis, >> >> Do you have a simple dataset, that is open, that I can attach to a bug >> report, assuming this really is a bug? >> >> >> >> Alan >> >> >> >> >> >> >> >> *From: *ParaView on behalf of >> denis cohen >> *Date: *Wednesday, March 14, 2018 at 3:36 AM >> *To: *"paraview at public.kitware.com" >> *Subject: *[EXTERNAL] [Paraview] state file >> >> >> >> Hello, >> >> In past versions of paraview, opening a pvsm state file that read several >> pvtu files resulted in paraview opening all the pvtu files in that >> directory. Now it only opens the ones saved in the pvsm file. This is >> annoying when the number of files has increased (like during a long time >> dependent simulation) and when wanting to use the same pvsm state file. Any >> ways of getting around that? >> >> Thank you >> >> Denis >> >> >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.d.rinehart at nasa.gov Wed Mar 28 12:12:02 2018 From: richard.d.rinehart at nasa.gov (Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]) Date: Wed, 28 Mar 2018 16:12:02 +0000 Subject: [Paraview] VRML animation Message-ID: <49F2A13558976D41882241B8CCCCF51B0FCB2A42@NDJSMBX203.ndc.nasa.gov> First time posting here so hope I'm doing it right (from daily summary email:-)) We too are interested in this but don't see it easily possible. We commonly export to VRML for performance reasons (and lots of software seem to digest this format). But to then animate has been custom coding using the VRML output. -rich Message: 2 Date: Wed, 28 Mar 2018 08:50:35 -0600 From: Sebastien Jourdain To: GeorgeP S , paraview Subject: Re: [Paraview] VRML animation Message-ID: Content-Type: text/plain; charset="utf-8" Putting back the mailing list as other could provide an actual answer to your "immersive question". ParaView can do immersive animation but that would be managed within ParaView. So I'm still not sure to understand what you are trying to do. But maybe other on the mailing list may do... Seb On Wed, Mar 28, 2018 at 8:38 AM, GeorgeP S wrote: > I am trying to set up an environment where i can enter "inside" the > simulation and visualize the animation and the results on a height of > eye level. > Due to the fact that i saw articles about immersive paraview i thought > it could export also the animation. > > Thank you again for the responce, > Salachoris Georgios Panagiotis > > On Wed, Mar 28, 2018 at 4:32 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> May I ask why VRML? Are you trying to do a time animation of >> geometry+data/color on the web? >> What I'm trying to say is that often by narrowing the question you >> get a perfect answer for it but not a good one for truly solving your problem. >> So what are you trying to do/solve? >> >> Thanks, >> >> Seb >> >> On Wed, Mar 28, 2018 at 8:19 AM, GeorgeP S wrote: >> >>> Thank you very much for the responce. To your knowledge which >>> program can do a vrml animation by a .vtp file? >>> >>> Thank you again, >>> Salachoris Georgios Panagiotis >>> >>> On Wed, Mar 28, 2018 at 3:46 PM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> To the best of my knowledge, this is not supported currently. >>>> >>>> Utkarsh >>>> >>>> On Thu, Mar 22, 2018 at 2:14 PM, GeorgeP S >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> i would like to ask how is it possible to export in vrml but >>>>> retain the animation acquired from the models simulation.Is there >>>>> a specific feature that i have not found out yet about this kind of thing? >>>>> >>>>> Thank you! >>>>> >>>>> >>>>> >>>> utm_campaign=sig-email&utm_content=webmail> Mail priva di virus. >>>>> www.avast.com >>>>> >>>> utm_campaign=sig-email&utm_content=webmail> >>>>> <#m_3492283369435919282_m_-8827445642746360931_m_58150214708170305 >>>>> 96_m_-2886712227971363020_m_-1156303584899477793_DAB4FAD8-2DD7-40B >>>>> B-A1B8-4E2AA1F9FDF2> >>>>> >>>>> _______________________________________________ >>>>> 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: >>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexander.Stief at hs-aalen.de Wed Mar 28 13:13:41 2018 From: Alexander.Stief at hs-aalen.de (Stief, Alexander) Date: Wed, 28 Mar 2018 17:13:41 +0000 Subject: [Paraview] png image file size - screenshot vs animation In-Reply-To: References: <11BC40335FCF354D99B30918B180F5297A08AFCE@MAIL-1.htw-aalen.de>, Message-ID: <11BC40335FCF354D99B30918B180F5297A08B03C@MAIL-1.htw-aalen.de> This does not fit my observation. Saving as a screenshot, I get a reasonably small png file size. Saving the same scene as an animation instead, I get huge png files instead regardless of the image content. I tried again with a plain white scene and a resolution of 6428x3764 File size using save screenshot (image quality 100): 85.2KiB File size using save animation (image quality 100): 69.3Mib File size using save animation (image quality 80): 327.2Kib Alex, In 5.4, save screenshot didn't compress the images at all. This was done simply to improve the performance since compression took considerable amount of time for larger images. However, it's been changed in 5.5 to a more sensible default for both animations and save screenshots. Also note, with PNG compression doesn't affect image quality since it's always lossless. Utkarsh On Wed, Mar 28, 2018 at 7:20 AM, Stief, Alexander wrote: > Hi, > > PV version is 5.4.1 > when making a png screenshot in PV with a resolution of 3840x2160, the file > size I get with default settings is ~1.4MB. This is due to the fact that > around 80% of the image are plain white space. So far, so normal. > However, when I create an animation and export to png images with the exact > same default settings for image quality, the image file size for the exact > same scene is ~28MB. > Only when I dial down the image quality manually to around 60 the file size > becomes similar to the png file from the screenshot. And the image quality > is not visibly worse than with 100% setting. > This must be some kind of bug, I never had this issue with previous > versions. > > tl;dr: png image file size differs greatly between screenshot and animation > with the exact same default settings. > > Regards > Alex > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Wed Mar 28 13:15:07 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 28 Mar 2018 17:15:07 +0000 Subject: [Paraview] [EXTERNAL] png image file size - screenshot vs animation In-Reply-To: <11BC40335FCF354D99B30918B180F5297A08AFCE@MAIL-1.htw-aalen.de> References: <11BC40335FCF354D99B30918B180F5297A08AFCE@MAIL-1.htw-aalen.de> Message-ID: <044a98f9b33c4909872e579873ffab58@ES01AMSNLNT.srn.sandia.gov> Hi Alex, I just tried this with master (in essence, 5.5.0-rc4 (out Real Soon Now) ). My sizes are exactly the same. I did the following: * Linux, master, remote server. * Opened can.exo. (It's in Examples.) All variables on, apply. * Rotated can so it looks nice. * File/ Save Screenshot with your resolution. Saved as .png. Rest are default settings. File size is 197k. * File/ Save Animation with your resolution. Saved as .png. Rest are default settings. File size is 197k. Mind trying using the 5.5.0-rc3, from the paraview.org website? Also, if you are still seeing weirdnesses, try the new, shiny "Reset to Default Settings" option (and keep a copy of your state files for Kitware, if this is an issue). If you still see issues, mind giving us a list, as above, how to recreate? Thanks, Alan From: ParaView [mailto:paraview-bounces at public.kitware.com] On Behalf Of Stief, Alexander Sent: Wednesday, March 28, 2018 5:21 AM To: paraview at public.kitware.com Subject: [EXTERNAL] [Paraview] png image file size - screenshot vs animation Hi, PV version is 5.4.1 when making a png screenshot in PV with a resolution of 3840x2160, the file size I get with default settings is ~1.4MB. This is due to the fact that around 80% of the image are plain white space. So far, so normal. However, when I create an animation and export to png images with the exact same default settings for image quality, the image file size for the exact same scene is ~28MB. Only when I dial down the image quality manually to around 60 the file size becomes similar to the png file from the screenshot. And the image quality is not visibly worse than with 100% setting. This must be some kind of bug, I never had this issue with previous versions. tl;dr: png image file size differs greatly between screenshot and animation with the exact same default settings. Regards Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 28 13:16:17 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Mar 2018 13:16:17 -0400 Subject: [Paraview] png image file size - screenshot vs animation In-Reply-To: <11BC40335FCF354D99B30918B180F5297A08B03C@MAIL-1.htw-aalen.de> References: <11BC40335FCF354D99B30918B180F5297A08AFCE@MAIL-1.htw-aalen.de> <11BC40335FCF354D99B30918B180F5297A08B03C@MAIL-1.htw-aalen.de> Message-ID: I may have spoken the other way around. In any case, just hold on till 5.5 is out and this will be addressed. Utkarsh On Wed, Mar 28, 2018 at 1:13 PM, Stief, Alexander wrote: > This does not fit my observation. > Saving as a screenshot, I get a reasonably small png file size. > Saving the same scene as an animation instead, I get huge png files instead regardless of the image content. > > I tried again with a plain white scene and a resolution of 6428x3764 > File size using save screenshot (image quality 100): 85.2KiB > File size using save animation (image quality 100): 69.3Mib > File size using save animation (image quality 80): 327.2Kib > > > > Alex, > > In 5.4, save screenshot didn't compress the images at all. This was > done simply to improve the performance since compression took > considerable amount of time for larger images. However, it's been > changed in 5.5 to a more sensible default for both animations and save > screenshots. > > Also note, with PNG compression doesn't affect image quality since > it's always lossless. > > Utkarsh > > On Wed, Mar 28, 2018 at 7:20 AM, Stief, Alexander > wrote: >> Hi, >> >> PV version is 5.4.1 >> when making a png screenshot in PV with a resolution of 3840x2160, the file >> size I get with default settings is ~1.4MB. This is due to the fact that >> around 80% of the image are plain white space. So far, so normal. >> However, when I create an animation and export to png images with the exact >> same default settings for image quality, the image file size for the exact >> same scene is ~28MB. >> Only when I dial down the image quality manually to around 60 the file size >> becomes similar to the png file from the screenshot. And the image quality >> is not visibly worse than with 100% setting. >> This must be some kind of bug, I never had this issue with previous >> versions. >> >> tl;dr: png image file size differs greatly between screenshot and animation >> with the exact same default settings. >> >> Regards >> Alex >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> From mbeshr1986 at gmail.com Wed Mar 28 15:49:37 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Wed, 28 Mar 2018 15:49:37 -0400 Subject: [Paraview] Can Paraview use the GPU instead of the CPU? Message-ID: Is there a way to use the GPU instead of the CPU for: 1. Data rendering in general? 2. Volume rendering? other than using the NVIDIA IndeX plugin? 3. Loading and displaying the data (i.e. data crunching). For example, if I am loading a transient CFD simulation result? Also, is there a way to render-off screen through Paraview GUI? or this needs to be done through code? -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Wed Mar 28 17:43:59 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 28 Mar 2018 17:43:59 -0400 Subject: [Paraview] ParaviewWeb server / client mismatch Message-ID: HI All: I'm trying to switch from ViewPortImageDelivery to VtkImageDelivery so I can see updates to the web client without having to click in the window. But apparently the protocols on the server side are deficient, and I get a client-side error complaining that "viewport.image.animation.fps.max" is an unregistered method. On the python side, tried both of these, but got the same error. self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPortImageDelivery()) self.registerVtkWebProtocol(pv_protocols.vtk_protocols.vtkWebViewPortImageDelivery()) This is using the pvpython that comes with ParaView-5.5.0-RC3. Thank you, -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Mar 28 17:53:24 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 28 Mar 2018 15:53:24 -0600 Subject: [Paraview] ParaviewWeb server / client mismatch In-Reply-To: References: Message-ID: You need to register the following protocol https://github.com/Kitware/visualizer/blob/master/server/pvw-visualizer.py#L196 Then make sure you call: https://github.com/Kitware/visualizer/blob/master/server/pvw-visualizer.py#L208-L209 On Wed, Mar 28, 2018 at 3:43 PM, Sgouros, Thomas wrote: > HI All: > > I'm trying to switch from ViewPortImageDelivery to VtkImageDelivery so I > can see updates to the web client without having to click in the window. > But apparently the protocols on the server side are deficient, and I get a > client-side error complaining that "viewport.image.animation.fps.max" is > an unregistered method. > > On the python side, tried both of these, but got the same error. > > self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPortImageDelive > ry()) > self.registerVtkWebProtocol(pv_protocols.vtk_protocols. > vtkWebViewPortImageDelivery()) > > This is using the pvpython that comes with ParaView-5.5.0-RC3. > > Thank you, > > -Tom > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Wed Mar 28 18:22:06 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 28 Mar 2018 18:22:06 -0400 Subject: [Paraview] ParaviewWeb server / client mismatch In-Reply-To: References: Message-ID: Brilliant. That worked, thank you, and most of the image changes are updated with one click of the button rather than one for the control and one click on the canvas. However, I often (not always) get this: CRITICAL:twisted:Unhandled Error Traceback (most recent call last): File "AMSServer.py", line 220, in server.start_webserver(options=args, protocol=AMSServer) File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", line 238, in start_webserver reactor.run() File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", line 1243, in run self.mainLoop() --- --- File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", line 1249, in mainLoop while self._started: exceptions.UnboundLocalError: local variable 'self' referenced before assignment Traceback (most recent call last): File "AMSServer.py", line 220, in server.start_webserver(options=args, protocol=AMSServer) File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", line 238, in start_webserver reactor.run() File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", line 1243, in run self.mainLoop() File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", line 1247, in mainLoop while self._started: UnboundLocalError: local variable 'self' referenced before assignment Fatal Python error: GC object already tracked Abort trap: 6 I imagine this is related to the fact that the control that is invoked here is a slider, and I set it up so that when the slider is moved, it launches a thread that watches to see when the slider stops moving before doing an update of the model view. So it probably has something to do with the fact that the InvokeEvent('UpdateEvent') call happens in a thread. Maybe I shouldn't do that? The other renderer, with ViewPortImageDelivery, seemed to handle this fine, though you had to click in the window to see the change, which is what I'm trying to fix. Thank you, -Tom p.s. Also thank you for the issue entry. On Wed, Mar 28, 2018 at 5:53 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > You need to register the following protocol > https://github.com/Kitware/visualizer/blob/master/server/ > pvw-visualizer.py#L196 > > Then make sure you call: > https://github.com/Kitware/visualizer/blob/master/server/ > pvw-visualizer.py#L208-L209 > > On Wed, Mar 28, 2018 at 3:43 PM, Sgouros, Thomas > wrote: > >> HI All: >> >> I'm trying to switch from ViewPortImageDelivery to VtkImageDelivery so I >> can see updates to the web client without having to click in the window. >> But apparently the protocols on the server side are deficient, and I get a >> client-side error complaining that "viewport.image.animation.fps.max" is >> an unregistered method. >> >> On the python side, tried both of these, but got the same error. >> >> self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPort >> ImageDelivery()) >> self.registerVtkWebProtocol(pv_protocols.vtk_protocols.vtkWe >> bViewPortImageDelivery()) >> >> This is using the pvpython that comes with ParaView-5.5.0-RC3. >> >> Thank you, >> >> -Tom >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Mar 28 19:35:42 2018 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 28 Mar 2018 17:35:42 -0600 Subject: [Paraview] ParaviewWeb server / client mismatch In-Reply-To: References: Message-ID: Yes threading is bad. I didn't noticed that you were creating threads in your code. On Wed, Mar 28, 2018 at 4:22 PM, Sgouros, Thomas wrote: > Brilliant. That worked, thank you, and most of the image changes are > updated with one click of the button rather than one for the control and > one click on the canvas. However, I often (not always) get this: > > CRITICAL:twisted:Unhandled Error > > Traceback (most recent call last): > > File "AMSServer.py", line 220, in > > server.start_webserver(options=args, protocol=AMSServer) > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", > line 238, in start_webserver > > reactor.run() > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", > line 1243, in run > > self.mainLoop() > > --- --- > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", > line 1249, in mainLoop > > while self._started: > > exceptions.UnboundLocalError: local variable 'self' referenced before > assignment > > > Traceback (most recent call last): > > File "AMSServer.py", line 220, in > > server.start_webserver(options=args, protocol=AMSServer) > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", > line 238, in start_webserver > > reactor.run() > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", > line 1243, in run > > self.mainLoop() > > File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", > line 1247, in mainLoop > > while self._started: > > UnboundLocalError: local variable 'self' referenced before assignment > > Fatal Python error: GC object already tracked > > Abort trap: 6 > > I imagine this is related to the fact that the control that is invoked > here is a slider, and I set it up so that when the slider is moved, it > launches a thread that watches to see when the slider stops moving before > doing an update of the model view. So it probably has something to do with > the fact that the InvokeEvent('UpdateEvent') call happens in a thread. > Maybe I shouldn't do that? The other renderer, with ViewPortImageDelivery, > seemed to handle this fine, though you had to click in the window to see > the change, which is what I'm trying to fix. > > Thank you, > > -Tom > > > p.s. Also thank you for the issue entry. > > > > On Wed, Mar 28, 2018 at 5:53 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> You need to register the following protocol >> https://github.com/Kitware/visualizer/blob/master/server/pvw >> -visualizer.py#L196 >> >> Then make sure you call: >> https://github.com/Kitware/visualizer/blob/master/server/pvw >> -visualizer.py#L208-L209 >> >> On Wed, Mar 28, 2018 at 3:43 PM, Sgouros, Thomas < >> thomas_sgouros at brown.edu> wrote: >> >>> HI All: >>> >>> I'm trying to switch from ViewPortImageDelivery to VtkImageDelivery so I >>> can see updates to the web client without having to click in the window. >>> But apparently the protocols on the server side are deficient, and I get a >>> client-side error complaining that "viewport.image.animation.fps.max" >>> is an unregistered method. >>> >>> On the python side, tried both of these, but got the same error. >>> >>> self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPort >>> ImageDelivery()) >>> self.registerVtkWebProtocol(pv_protocols.vtk_protocols.vtkWe >>> bViewPortImageDelivery()) >>> >>> This is using the pvpython that comes with ParaView-5.5.0-RC3. >>> >>> Thank you, >>> >>> -Tom >>> >>> >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas_sgouros at brown.edu Wed Mar 28 20:53:32 2018 From: thomas_sgouros at brown.edu (Sgouros, Thomas) Date: Wed, 28 Mar 2018 20:53:32 -0400 Subject: [Paraview] ParaviewWeb server / client mismatch In-Reply-To: References: Message-ID: Curses, foiled again. Thank you, -Tom On Wed, Mar 28, 2018 at 7:35 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Yes threading is bad. I didn't noticed that you were creating threads in > your code. > > On Wed, Mar 28, 2018 at 4:22 PM, Sgouros, Thomas > wrote: > >> Brilliant. That worked, thank you, and most of the image changes are >> updated with one click of the button rather than one for the control and >> one click on the canvas. However, I often (not always) get this: >> >> CRITICAL:twisted:Unhandled Error >> >> Traceback (most recent call last): >> >> File "AMSServer.py", line 220, in >> >> server.start_webserver(options=args, protocol=AMSServer) >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", >> line 238, in start_webserver >> >> reactor.run() >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", >> line 1243, in run >> >> self.mainLoop() >> >> --- --- >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", >> line 1249, in mainLoop >> >> while self._started: >> >> exceptions.UnboundLocalError: local variable 'self' referenced before >> assignment >> >> >> Traceback (most recent call last): >> >> File "AMSServer.py", line 220, in >> >> server.start_webserver(options=args, protocol=AMSServer) >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/wslink/server.py", >> line 238, in start_webserver >> >> reactor.run() >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", >> line 1243, in run >> >> self.mainLoop() >> >> File "/Applications/ParaView-5.5.0-RC3.app/Contents/Python/twisted/internet/base.py", >> line 1247, in mainLoop >> >> while self._started: >> >> UnboundLocalError: local variable 'self' referenced before assignment >> >> Fatal Python error: GC object already tracked >> >> Abort trap: 6 >> >> I imagine this is related to the fact that the control that is invoked >> here is a slider, and I set it up so that when the slider is moved, it >> launches a thread that watches to see when the slider stops moving before >> doing an update of the model view. So it probably has something to do with >> the fact that the InvokeEvent('UpdateEvent') call happens in a thread. >> Maybe I shouldn't do that? The other renderer, with ViewPortImageDelivery, >> seemed to handle this fine, though you had to click in the window to see >> the change, which is what I'm trying to fix. >> >> Thank you, >> >> -Tom >> >> >> p.s. Also thank you for the issue entry. >> >> >> >> On Wed, Mar 28, 2018 at 5:53 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> You need to register the following protocol >>> https://github.com/Kitware/visualizer/blob/master/server/pvw >>> -visualizer.py#L196 >>> >>> Then make sure you call: >>> https://github.com/Kitware/visualizer/blob/master/server/pvw >>> -visualizer.py#L208-L209 >>> >>> On Wed, Mar 28, 2018 at 3:43 PM, Sgouros, Thomas < >>> thomas_sgouros at brown.edu> wrote: >>> >>>> HI All: >>>> >>>> I'm trying to switch from ViewPortImageDelivery to VtkImageDelivery so >>>> I can see updates to the web client without having to click in the window. >>>> But apparently the protocols on the server side are deficient, and I get a >>>> client-side error complaining that "viewport.image.animation.fps.max" >>>> is an unregistered method. >>>> >>>> On the python side, tried both of these, but got the same error. >>>> >>>> self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPort >>>> ImageDelivery()) >>>> self.registerVtkWebProtocol(pv_protocols.vtk_protocols.vtkWe >>>> bViewPortImageDelivery()) >>>> >>>> This is using the pvpython that comes with ParaView-5.5.0-RC3. >>>> >>>> Thank you, >>>> >>>> -Tom >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Wed Mar 28 22:41:43 2018 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 29 Mar 2018 04:41:43 +0200 Subject: [Paraview] Can Paraview use the GPU instead of the CPU? In-Reply-To: References: Message-ID: Hello Mohamed, Is there a way to use the GPU instead of the CPU for: > 1. Data rendering in general? > This is the case by default when you are using the paraview binaries, you can check by taking a look into Help->About->OpenGL Renderer > 2. Volume rendering? other than using the NVIDIA IndeX plugin? > This is also the case by default if your GPU suppports it. You can check the "Volume Rendering Mode" in the volume representation property. Smart is the default and will use your gpu if possible. You can set it to "GPU based" if you want to make sure. > 3. Loading and displaying the data (i.e. data crunching). For example, if > I am loading a transient CFD simulation result? > Loading the data using the GPU will not be possible, this is basically lots of IO with the disk and the creation of the geometry. If by displaying you mean rendering, see the first point. > > Also, is there a way to render-off screen through Paraview GUI? or this > needs to be done through code? > Yes there is, but it depends what you mean by off-screen. If you refer to CPU based rendering on an headlees server, please take a look here. [1] If not, please precise your needs. Best regards, Mathieu Westphal [1] : https://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Mar 29 09:01:35 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 29 Mar 2018 09:01:35 -0400 Subject: [Paraview] ParaView-Superbuild Win10 Errors In-Reply-To: References: Message-ID: .lib files on Windows can be static libraries or they can be the symbols needed to link to a .dll (the linker looks at the symbols in the .lib and assumes they are in the dll, it doesn't actually need the dll). The second is what is missing in this case, but I'm not sure why since it should have been created with the .dll. Maybe a CMake option is missing to VRPN's configure? Shawn On Wed, Mar 28, 2018 at 10:42 AM, Aron Helser wrote: > I don't know how or why vrpn is used by paraview, so I'll have to defer to > others... > > On Wed, Mar 28, 2018 at 8:23 AM, Jamil Goettlich < > jamil.goettlich at gmail.com> wrote: > >> Hi Aron, >> >> thank you for the reply. Youre right, there was an error way at the >> beginning concerning quat.lib. >> It seems like linking vrpn.lib failed because quat.lib cannot be >> recognized. >> Here is the full error (Using Win10, Compiler Visual Studio12.0 (cl.exe), >> ninja build system. >> Also, I enabled VRPN_USE_HID and disabled VRPN_USE_LOCAL_HIDAPI). >> >> [157/254] Linking CXX shared library vrpn.dll >> FAILED: vrpn.dll vrpn.lib >> cmd.exe /C "cd . && C:\KermsInstalls\cmake\bin\cmake.exe -E vs_link_dll >> --intdir=CMakeFiles\vrpn.dir --manifests -- C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe >> /nologo CMakeFiles\vrpn.dir\vrpn_Analog.C.obj >> CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj >> CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj >> CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj CMakeFiles\vrpn.dir\vrpn_Button.C.obj >> CMakeFiles\vrpn.dir\vrpn_Connection.C.obj CMakeFiles\vrpn.dir\vrpn_Dial.C.obj >> CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj >> CMakeFiles\vrpn.dir\vrpn_FileController.C.obj >> CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj >> CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj >> CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj >> CMakeFiles\vrpn.dir\vrpn_Imager.C.obj CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj >> CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj CMakeFiles\vrpn.dir\vrpn_Poser.C.obj >> CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj >> CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj >> CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj >> CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj >> CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib >> /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib >> ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib >> shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && >> cd ." >> LINK: command "C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe /nologo >> CMakeFiles\vrpn.dir\vrpn_Analog.C.obj CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj >> CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj >> CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj CMakeFiles\vrpn.dir\vrpn_Button.C.obj >> CMakeFiles\vrpn.dir\vrpn_Connection.C.obj CMakeFiles\vrpn.dir\vrpn_Dial.C.obj >> CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj >> CMakeFiles\vrpn.dir\vrpn_FileController.C.obj >> CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj >> CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj >> CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj >> CMakeFiles\vrpn.dir\vrpn_Imager.C.obj CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj >> CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj CMakeFiles\vrpn.dir\vrpn_Poser.C.obj >> CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj >> CMakeFiles\vrpn.dir\vrpn_Serial.C.obj CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj >> CMakeFiles\vrpn.dir\vrpn_Shared.C.obj CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj >> CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj >> CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib >> /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib >> ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib >> shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib >> /MANIFEST /MANIFESTFILE:vrpn.dll.manifest" failed (exit code 1181) with >> the following output: >> LINK : fatal error LNK1181: cannot open input file 'quat\quat.lib' >> [158/254] Linking CXX shared library gpsnmealib\gpsnmea.dll >> >> I checked for quat.lib but there is only quat.dll in the superbuild >> folder. Is there a flag to set for building the quat library statically or >> to tell vrpn to look for a dll? >> >> Thank a lot >> Jamil >> >> 2018-03-27 20:24 GMT+02:00 Aron Helser : >> >>> Jamil, >>> Make sure you scroll up and find the first error - ninja is a parallel >>> build system, so the build will continue on other threads after the first >>> error. Then maybe you can solve that first error, and others will be fixed. >>> >>> It looks like an earlier error caused 'quat.lib' not to be built, but >>> it's hard to tell.... >>> -Aron >>> >>> On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich < >>> jamil.goettlich at gmail.com> wrote: >>> >>>> Hi Shawn, >>>> >>>> thanks a lot for the tip, configuring worked with the Visual Studio >>>> 12.0 compiler! Now I am getting a lot of build errors though. >>>> >>>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>>> [255/256] Linking C shared library bin\hdf5.dll >>>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>>> [256/256] Linking C shared library bin\hdf5_hl.dll >>>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>>> ninja: build stopped: subcommand failed. >>>> >>>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>>> nt_messages.dir\vrpn_print_messages.C.obj >>>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>>> t.dir\ff_client.C.obj >>>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>>> ent.dir\phan_client.C.obj >>>> [7/97] Building CXX object client_src\CMakeFiles\printval >>>> s.dir\printvals.C.obj >>>> ninja: build stopped: subcommand failed. >>>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>>> (message): >>>> Failed with exit code 1 >>>> >>>> These are some examples. My it be possible that the ninja version is >>>> not suited either? Do you know what ninja version you were building the >>>> superbuild with? >>>> >>>> Thanks a lot, >>>> Jamil >>>> >>>> (P.s. Sorry Shawn for my posting mistake) >>>> >>>> 2018-03-27 16:07 GMT+02:00 Shawn Waldon : >>>> >>>>> Hi Jamil, >>>>> >>>>> Please keep replies CCed to the mailing list (Reply All) so others can >>>>> contribute to the discussion (or find answers to their own problems later >>>>> in the archives). >>>>> >>>>> We use the most recent release of ninja on most of our build machines >>>>> (so that one should work). I'm not sure why you are getting that error >>>>> messages from what you have included... maybe others on the list can chime >>>>> in or you can give more details. >>>>> >>>>> Shawn >>>>> >>>>> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < >>>>> jamil.goettlich at gmail.com> wrote: >>>>> >>>>>> Hi Shawn, >>>>>> >>>>>> thanks a lot for the tip, configuring worked with the Visual Studio >>>>>> 12.0 compiler! Now I am getting a lot of build errors though. >>>>>> >>>>>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>>>>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>>>>> [255/256] Linking C shared library bin\hdf5.dll >>>>>> Creating library bin\hdf5.lib and object bin\hdf5.exp >>>>>> [256/256] Linking C shared library bin\hdf5_hl.dll >>>>>> Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>>>>> ninja: build stopped: subcommand failed. >>>>>> >>>>>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>>>>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>>>>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>>>>> nt_messages.dir\vrpn_print_messages.C.obj >>>>>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>>>>> t.dir\ff_client.C.obj >>>>>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>>>>> ent.dir\phan_client.C.obj >>>>>> [7/97] Building CXX object client_src\CMakeFiles\printval >>>>>> s.dir\printvals.C.obj >>>>>> ninja: build stopped: subcommand failed. >>>>>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>>>>> (message): >>>>>> Failed with exit code 1 >>>>>> >>>>>> These are some examples. My it be possible that the ninja version is >>>>>> not suited either? Do you know what ninja version you were building the >>>>>> superbuild with? >>>>>> >>>>>> Thanks a lot, >>>>>> Jamil >>>>>> >>>>>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >>>>>> >>>>>>> Hi Jamil, >>>>>>> >>>>>>> I'm not sure if this will get you all the way to a build, but here >>>>>>> are some pointers: >>>>>>> >>>>>>> We build with the visual studio compiler but use the Ninja generator >>>>>>> since it is significantly faster than VS. >>>>>>> >>>>>>> VS 2017 may not work. Our binaries are built with 2013 right now >>>>>>> and we plan to move to 2015 after the current release cycle. If you want >>>>>>> what you are building to be compatible with the Kitware binaries, you will >>>>>>> need to use 2013. Also, I believe there are compiler errors if you use >>>>>>> 2017 right now. >>>>>>> >>>>>>> To build with Ninja and VS compilers, you need to be in a visual >>>>>>> studio command prompt rather than a normal shell (it sets a bunch of >>>>>>> environment vars, which I think is what is missing in your last example). >>>>>>> To convert a normal command prompt you run (example is for VS2015, your >>>>>>> path may differ) 'C:/Program Files (x86)/Microsoft Visual Studio >>>>>>> 14.0/VC/vcvarsall.bat x64' in your shell and it will set the environment >>>>>>> variables for you. If you have the environment set up before running cmake >>>>>>> -G Ninja it should just pick the right compiler. >>>>>>> >>>>>>> HTH, >>>>>>> >>>>>>> Shawn >>>>>>> >>>>>>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich < >>>>>>> jamil.goettlich at gmail.com> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I am having Problems building ParaView with ParaView-Superbuild. As >>>>>>>> Visual Studio is not supported, I tried other build systems and compilers. >>>>>>>> Unfortunately none of them succeeded. On the other hand I was able to build >>>>>>>> small HelloWord programs with each of the combinations listed below and >>>>>>>> without any errors. Here is what I did: >>>>>>>> >>>>>>>> First, I cloned from git: >>>>>>>> git clone --recursive https://gitlab.kitware.com/par >>>>>>>> aview/paraview-superbuild.git >>>>>>>> Then cd paraview-superbuild and created new folder (build). >>>>>>>> >>>>>>>> The following cases did not work out (Doesnt matter if using Git >>>>>>>> Bash or VS Command Prompt): >>>>>>>> Build System: Ninja, Compiler: MinGW >>>>>>>> command: cmake .. -G "Ninja" >>>>>>>> Error: >>>>>>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message): >>>>>>>> At least Visual Studio 9.0 is required >>>>>>>> Call Stack (most recent call first): >>>>>>>> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >>>>>>>> superbuild/CMakeLists.txt:145 (_superbuild_discover_projects) >>>>>>>> >>>>>>>> Although I have Visual Studio 15 2017 installed it does not seem to >>>>>>>> work. >>>>>>>> >>>>>>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>>>> Error: >>>>>>>> >>>>>>>> The C compiler >>>>>>>> "C:/Program Files (x86)/Microsoft Visual >>>>>>>> Studio/2017/Community/VC/Tools/MSVC/14.12.25827/bin/Hostx86/ >>>>>>>> x64/cl.exe" >>>>>>>> is not able to compile a simple test program. >>>>>>>> It fails with the following output: >>>>>>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp >>>>>>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast" >>>>>>>> "C:\Program Files (x86)\Microsoft Visual >>>>>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" >>>>>>>> -f CMakeFiles\cmTC_008b4.dir\build.make /nologo -L >>>>>>>> CMakeFiles\cmTC_008b4.dir\build >>>>>>>> >>>>>>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj >>>>>>>> >>>>>>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe >>>>>>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp >>>>>>>> >>>>>>>> testCCompiler.c >>>>>>>> >>>>>>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c: >>>>>>>> fatal error C1001: An internal error has occurred in the compiler. >>>>>>>> >>>>>>>> (compiler file 'msc1.cpp', line 1507) >>>>>>>> >>>>>>>> To work around this problem, try simplifying or changing the >>>>>>>> program near the locations listed above. >>>>>>>> >>>>>>>> Please choose the Technical Support command on the Visual C++ >>>>>>>> >>>>>>>> Help menu, or open the Technical Support help file for more >>>>>>>> information >>>>>>>> >>>>>>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM >>>>>>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be >>>>>>>> prompted to send an error report to Microsoft later. >>>>>>>> >>>>>>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM >>>>>>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return >>>>>>>> code '0x2' >>>>>>>> >>>>>>>> Stop. >>>>>>>> >>>>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft >>>>>>>> Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"' >>>>>>>> : return code '0x2' >>>>>>>> >>>>>>>> Stop. >>>>>>>> >>>>>>>> >>>>>>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program >>>>>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools >>>>>>>> \MSVC\14.12.25827\bin\Hostx64\x64) >>>>>>>> >>>>>>>> Here, cmake recognized the compiler, but it throws another error >>>>>>>> Error: >>>>>>>> >>>>>>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M >>>>>>>> odules/CMakeDetermineRCCompiler.cmake:20 (message): >>>>>>>> Could not find compiler set in environment variable RC: >>>>>>>> rc. >>>>>>>> Call Stack (most recent call first): >>>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>>> odules/Platform/Windows-MSVC.cmake:323 (enable_language) >>>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>>> odules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) >>>>>>>> C:/Program Files/CMake/share/cmake-3.10/M >>>>>>>> odules/CMakeCInformation.cmake:48 (include) >>>>>>>> CMakeLists.txt:3 (project) >>>>>>>> >>>>>>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage >>>>>>>> >>>>>>>> >>>>>>>> I am out of ideas now. >>>>>>>> I would be really happy for a detailed build description as I am >>>>>>>> sure I did not understand something properly. >>>>>>>> >>>>>>>> And every hint on how to resolve on of those errors is very welcome >>>>>>>> too. >>>>>>>> >>>>>>>> >>>>>>>> Thanks in advance! >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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: >>>>>>>> https://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Mar 29 14:01:49 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 29 Mar 2018 14:01:49 -0400 Subject: [Paraview] ParaView 5.5.0-RC4 tagged, binaries available Message-ID: Dear ParaView community, I am pleased to announce that ParaView 5.5.0-RC4 has been tagged (tag "v5.5.0-RC4"). Binaries are also available on the ParaView downloads web page https://www.paraview.org/download/. If your browser doesn't show the 5.5.0-RC4 downloads, you may just need to "hard refresh" the page. On Chrome and Firefox, hold down Shift while pressing Ctrl-R (or Cmd-R on macOS). Please let us know if you encounter any issues with this release candidate. ParaView's superbuild has also been tagged with "v5.5.0-RC4". Thank you, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From mbeshr1986 at gmail.com Thu Mar 29 14:43:32 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Thu, 29 Mar 2018 14:43:32 -0400 Subject: [Paraview] Can Paraview use the GPU instead of the CPU? In-Reply-To: References: Message-ID: Thank you Mathieu for your reply. Regarding point 2 I have few questions: 1. I see the volume rendering mode (which I can switch between smart and CPU based) when I select a wavelet for instance. However, I can't see it when I choose unstructured cell type as the source (and this applies to my data set coming from CFD results). In that latter case, I get the select mapper drop down menu which has the options of projected tetra/z sweep/bunyk ray cast/resample to image. Is there a way to ensure volume rendering is done using the GPUs in that case? 2. In the case described above, when I select resample to image, the color of the model gets messed up (it becomes one color). Is there a way to get it back to normal? Thanks. On Wed, Mar 28, 2018 at 10:41 PM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > Hello Mohamed, > > Is there a way to use the GPU instead of the CPU for: >> 1. Data rendering in general? >> > This is the case by default when you are using the paraview binaries, you > can check by taking a look into Help->About->OpenGL Renderer > > >> 2. Volume rendering? other than using the NVIDIA IndeX plugin? >> > This is also the case by default if your GPU suppports it. You can check > the "Volume Rendering Mode" in the volume representation property. > Smart is the default and will use your gpu if possible. You can set it to > "GPU based" if you want to make sure. > > >> 3. Loading and displaying the data (i.e. data crunching). For example, if >> I am loading a transient CFD simulation result? >> > Loading the data using the GPU will not be possible, this is basically > lots of IO with the disk and the creation of the geometry. > If by displaying you mean rendering, see the first point. > > >> >> Also, is there a way to render-off screen through Paraview GUI? or this >> needs to be done through code? >> > Yes there is, but it depends what you mean by off-screen. > If you refer to CPU based rendering on an headlees server, please take a > look here. [1] > If not, please precise your needs. > > Best regards, > > Mathieu Westphal > > > [1] : https://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D > -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbeshr1986 at gmail.com Thu Mar 29 14:49:21 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Thu, 29 Mar 2018 14:49:21 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs In-Reply-To: References: Message-ID: Thank you for your reply. Yes I have an unstructured grid. Regarding the resample to image filter, when I select it in my case, I get an empty cuboid. Why is that? Is there a way to get the image matching my shape? On Mon, Mar 26, 2018 at 3:38 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > a. When I select ?Real Time? option and increase the time, even > though > > it is cached, it still keeps reloading which prevents the VR from > working. > > Is there any potential/possibility to fix this in the meantime or > upcoming > > release? > > Caching cannot work in "real time" mode since there's no guarantee > what time each frame will be rendered at. > > > b. When I cache it as a volume (rather than surface, wireframe, or > > points) on my laptop, it crashed the exe even when I increase the cache > > memory maximum size. Any thoughts on that? I tested it on a bigger and > > faster work station and it worked, however, it still has the issue > mentioned > > in the point below. > > I suspect you're just running out of memory on the system, esp since > you say smaller mesh works. > > > 2. When I get a smaller mesh (4x smaller), I am able to cache it as > a > > volume. However, when playing it back, it keeps reloading while showing > the > > green bar as below at each time step. Is that supposed to happen? Is that > > rendering? Is there a way to eliminate it or make it faster? > > Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems > to me you have unstructured grid which is using the slow path for > volume rendering. Another option is to apply "Resample To Image" > filter to resample the dataset to an image and volume rendering the > result. Then rendering should be much faster. You can also resample > and generate the image as a processing stage and save the resampled > dataset out and then load and render it in the animation loop. > -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbeshr1986 at gmail.com Thu Mar 29 15:35:16 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Thu, 29 Mar 2018 15:35:16 -0400 Subject: [Paraview] Can Paraview use the GPU instead of the CPU? In-Reply-To: References: Message-ID: " Thank you Mathieu for your reply. Regarding point 2 I have few questions: 1. I see the volume rendering mode (which I can switch between smart and CPU based) when I select a wavelet for instance. However, I can't see it when I choose unstructured cell type as the source (and this applies to my data set coming from CFD results). In that latter case, I get the select mapper drop down menu which has the options of projected tetra/z sweep/bunyk ray cast/resample to image. Is there a way to ensure volume rendering is done using the GPUs in that case? 2. In the case described above, when I select resample to image, the color of the model gets messed up (it becomes one color). Is there a way to get it back to normal? Thanks." Also, a third question regarding this point. If Paraview can do volume rendering using the GPUs. What does the NVIDIA IndeX plugin add on top of that then? On Thu, Mar 29, 2018 at 2:43 PM, Mohamed Beshr wrote: > Thank you Mathieu for your reply. Regarding point 2 I have few questions: > 1. I see the volume rendering mode (which I can switch between smart and > CPU based) when I select a wavelet for instance. However, I can't see it > when I choose unstructured cell type as the source (and this applies to my > data set coming from CFD results). In that latter case, I get the select > mapper drop down menu which has the options of projected tetra/z > sweep/bunyk ray cast/resample to image. Is there a way to ensure volume > rendering is done using the GPUs in that case? > 2. In the case described above, when I select resample to image, the color > of the model gets messed up (it becomes one color). Is there a way to get > it back to normal? > Thanks. > > On Wed, Mar 28, 2018 at 10:41 PM, Mathieu Westphal < > mathieu.westphal at kitware.com> wrote: > >> Hello Mohamed, >> >> Is there a way to use the GPU instead of the CPU for: >>> 1. Data rendering in general? >>> >> This is the case by default when you are using the paraview binaries, you >> can check by taking a look into Help->About->OpenGL Renderer >> >> >>> 2. Volume rendering? other than using the NVIDIA IndeX plugin? >>> >> This is also the case by default if your GPU suppports it. You can check >> the "Volume Rendering Mode" in the volume representation property. >> Smart is the default and will use your gpu if possible. You can set it to >> "GPU based" if you want to make sure. >> >> >>> 3. Loading and displaying the data (i.e. data crunching). For example, >>> if I am loading a transient CFD simulation result? >>> >> Loading the data using the GPU will not be possible, this is basically >> lots of IO with the disk and the creation of the geometry. >> If by displaying you mean rendering, see the first point. >> >> >>> >>> Also, is there a way to render-off screen through Paraview GUI? or this >>> needs to be done through code? >>> >> Yes there is, but it depends what you mean by off-screen. >> If you refer to CPU based rendering on an headlees server, please take a >> look here. [1] >> If not, please precise your needs. >> >> Best regards, >> >> Mathieu Westphal >> >> >> [1] : https://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >> > > > > -- > Best Regards, > Mohamed Beshr > -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 29 17:43:30 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 29 Mar 2018 17:43:30 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs In-Reply-To: References: Message-ID: You're getting an empty cubiod because it's showing as outline. Try changing the "representation" type to Volume from Outline. Is that any better? You may need to adjust your color/opactiy transfer function. On Thu, Mar 29, 2018 at 2:49 PM, Mohamed Beshr wrote: > Thank you for your reply. Yes I have an unstructured grid. Regarding the > resample to image filter, when I select it in my case, I get an empty > cuboid. Why is that? Is there a way to get the image matching my shape? > > On Mon, Mar 26, 2018 at 3:38 PM, Utkarsh Ayachit > wrote: >> >> > a. When I select ?Real Time? option and increase the time, even >> > though >> > it is cached, it still keeps reloading which prevents the VR from >> > working. >> > Is there any potential/possibility to fix this in the meantime or >> > upcoming >> > release? >> >> Caching cannot work in "real time" mode since there's no guarantee >> what time each frame will be rendered at. >> >> > b. When I cache it as a volume (rather than surface, wireframe, or >> > points) on my laptop, it crashed the exe even when I increase the cache >> > memory maximum size. Any thoughts on that? I tested it on a bigger and >> > faster work station and it worked, however, it still has the issue >> > mentioned >> > in the point below. >> >> I suspect you're just running out of memory on the system, esp since >> you say smaller mesh works. >> >> > 2. When I get a smaller mesh (4x smaller), I am able to cache it as >> > a >> > volume. However, when playing it back, it keeps reloading while showing >> > the >> > green bar as below at each time step. Is that supposed to happen? Is >> > that >> > rendering? Is there a way to eliminate it or make it faster? >> >> Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems >> to me you have unstructured grid which is using the slow path for >> volume rendering. Another option is to apply "Resample To Image" >> filter to resample the dataset to an image and volume rendering the >> result. Then rendering should be much faster. You can also resample >> and generate the image as a processing stage and save the resampled >> dataset out and then load and render it in the animation loop. > > > > > -- > Best Regards, > Mohamed Beshr From cory.quammen at kitware.com Thu Mar 29 17:56:04 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 29 Mar 2018 17:56:04 -0400 Subject: [Paraview] Paraview VR .exe version In-Reply-To: References: Message-ID: By the way, ParaView now ships with the OpenVR and IndeX plugins in the default binaries for Windows. They are not loaded by default, so you will have to load them in the plugin manager. You can try it out in ParaView 5.5.0-RC4 which is available at https://www.paraview.org/download. Thanks, Cory On Tue, Mar 27, 2018 at 9:39 AM, Cory Quammen wrote: > Mohamed, > > That type of installer for the VR-enabled ParaView is not yet available, I > am afraid. I'm not sure anyone has tried the IndeX plugin in VR - it's an > interesting idea, for sure. > > Best regards, > Cory > > On Tue, Mar 27, 2018 at 8:07 AM, Mohamed Beshr wrote: >> >> I am trying to try/use the NVIDIA IndeX plugin on the Paraview VR version. >> However, this plugin requires/needs a .exe (installed) version of Paraview >> (I tried it with .exe non-VR versions and it works but not with the >> extracted .zip VR version). The downloads section only has the .zip version >> for the VR. Anyone knows of a .exe version in the downloads section? >> >> >> -- >> Best Regards, >> Mohamed Beshr >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From aguirre.utn at gmail.com Fri Mar 30 02:52:33 2018 From: aguirre.utn at gmail.com (Miguel Aguirre) Date: Fri, 30 Mar 2018 08:52:33 +0200 Subject: [Paraview] How to interrupt macros/Python script ? Message-ID: Hello, I?m testing some macros and Python Shell scripts. One of them requires an iteration: it places the slice plane at several positions in order to integrate values at each position. However, I found that once the macro/script is executed, it is impossible to stop it (which annoys the debugging process). I already tested "exit()" command in the Python Shell but it does not works. There is way to interrupt the process? Thanks in advance. Miguel Angel AGUIRRE -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Fri Mar 30 04:36:13 2018 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 30 Mar 2018 10:36:13 +0200 Subject: [Paraview] How to interrupt macros/Python script ? In-Reply-To: References: Message-ID: Hello Miguel, The simplest way to do that, especially when debugging, is to raise an error. raise ValueError() Best regards, Mathieu Westphal On Fri, Mar 30, 2018 at 8:52 AM, Miguel Aguirre wrote: > Hello, > > > > I?m testing some macros and Python Shell scripts. One of them requires an > iteration: it places the slice plane at several positions in order to > integrate values at each position. However, I found that once the > macro/script is executed, it is impossible to stop it (which annoys the > debugging process). I already tested "exit()" command in the Python Shell > but it does not works. There is way to interrupt the process? > > > > Thanks in advance. > > Miguel Angel AGUIRRE > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tbrandvik at gmail.com Fri Mar 30 07:45:26 2018 From: tbrandvik at gmail.com (Tobias Brandvik) Date: Fri, 30 Mar 2018 13:45:26 +0200 Subject: [Paraview] Python programmable filter with two input ports and vtkCompositeDataSet Message-ID: Hi, I am following the instructions in this thread to create a Python programmable filter with two input ports, both of which expect a vtkCompositeDataSet: https://public.kitware.com/pipermail/paraview/2016-July/037562.html When I apply the filter I get the following error: ERROR: In /home/tbrandvik/Downloads/Paraview-5.4.1/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 297 vtkMultiBlockDataSet (0x190bd160): Structure does not match. You must use CopyStructure before calling this method. This is using Paraview 5.4.1. Any ideas on why this would work for multiple vtkDataSet but not a multiple vtkCompositeDataSet as the inputs would be welcome. Cheers, Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Fri Mar 30 09:57:35 2018 From: aron.helser at kitware.com (Aron Helser) Date: Fri, 30 Mar 2018 09:57:35 -0400 Subject: [Paraview] How to interrupt macros/Python script ? In-Reply-To: References: Message-ID: How does the debugger interact with python scripts in ParaView? In debugging stand-alone scripts, I'll often insert: import pdb; pdb.set_trace() to trigger the debugger. I suspect you might be able to use 'rdbg' and use that connection? -Aron On Fri, Mar 30, 2018 at 4:36 AM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > Hello Miguel, > > The simplest way to do that, especially when debugging, is to raise an > error. > > raise ValueError() > > Best regards, > > Mathieu Westphal > > On Fri, Mar 30, 2018 at 8:52 AM, Miguel Aguirre > wrote: > >> Hello, >> >> >> >> I?m testing some macros and Python Shell scripts. One of them requires an >> iteration: it places the slice plane at several positions in order to >> integrate values at each position. However, I found that once the >> macro/script is executed, it is impossible to stop it (which annoys the >> debugging process). I already tested "exit()" command in the Python Shell >> but it does not works. There is way to interrupt the process? >> >> >> >> Thanks in advance. >> >> Miguel Angel AGUIRRE >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbeshr1986 at gmail.com Fri Mar 30 10:31:19 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Fri, 30 Mar 2018 10:31:19 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs In-Reply-To: References: Message-ID: It is much better now. However, now the tube becomes one solid red color although the legend range is the same (see screenshot below for difference between original and re-sampled view). Please advise how can I fix this (I changed opacity scale shown in the figure between 0 and 1 and still the same). On Thu, Mar 29, 2018 at 5:43 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > You're getting an empty cubiod because it's showing as outline. Try > changing the "representation" type to Volume from Outline. Is that any > better? You may need to adjust your color/opactiy transfer function. > > > > On Thu, Mar 29, 2018 at 2:49 PM, Mohamed Beshr > wrote: > > Thank you for your reply. Yes I have an unstructured grid. Regarding the > > resample to image filter, when I select it in my case, I get an empty > > cuboid. Why is that? Is there a way to get the image matching my shape? > > > > On Mon, Mar 26, 2018 at 3:38 PM, Utkarsh Ayachit > > wrote: > >> > >> > a. When I select ?Real Time? option and increase the time, even > >> > though > >> > it is cached, it still keeps reloading which prevents the VR from > >> > working. > >> > Is there any potential/possibility to fix this in the meantime or > >> > upcoming > >> > release? > >> > >> Caching cannot work in "real time" mode since there's no guarantee > >> what time each frame will be rendered at. > >> > >> > b. When I cache it as a volume (rather than surface, wireframe, > or > >> > points) on my laptop, it crashed the exe even when I increase the > cache > >> > memory maximum size. Any thoughts on that? I tested it on a bigger and > >> > faster work station and it worked, however, it still has the issue > >> > mentioned > >> > in the point below. > >> > >> I suspect you're just running out of memory on the system, esp since > >> you say smaller mesh works. > >> > >> > 2. When I get a smaller mesh (4x smaller), I am able to cache it > as > >> > a > >> > volume. However, when playing it back, it keeps reloading while > showing > >> > the > >> > green bar as below at each time step. Is that supposed to happen? Is > >> > that > >> > rendering? Is there a way to eliminate it or make it faster? > >> > >> Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems > >> to me you have unstructured grid which is using the slow path for > >> volume rendering. Another option is to apply "Resample To Image" > >> filter to resample the dataset to an image and volume rendering the > >> result. Then rendering should be much faster. You can also resample > >> and generate the image as a processing stage and save the resampled > >> dataset out and then load and render it in the animation loop. > > > > > > > > > > -- > > Best Regards, > > Mohamed Beshr > -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 105545 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 140024 bytes Desc: not available URL: From eric.greenwade at gmail.com Fri Mar 30 11:14:39 2018 From: eric.greenwade at gmail.com (eric greenwade) Date: Fri, 30 Mar 2018 08:14:39 -0700 Subject: [Paraview] Alpha Channel for TIFF output Message-ID: Trying to figure out how to have paraview include alpha channel when outputting images, frames which are part of an animation, TIFF in particular. All the online info I've found points to 1) it be included in an upcoming release (a while ago), or 2) mentions controls that do not seem to exist in the 5.5-RC3 version I'm using. Any pointers would be greatly appreciated. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbeshr1986 at gmail.com Fri Mar 30 11:26:56 2018 From: mbeshr1986 at gmail.com (Mohamed Beshr) Date: Fri, 30 Mar 2018 11:26:56 -0400 Subject: [Paraview] Paraview VR .exe version In-Reply-To: References: Message-ID: Thanks a lot for the update Cory. That's nice. I just tested it. The only thing that used to be working in the open VR version but crashes with the VR plugin is the crop plan. I was able to do it in VR nicely and smoothly with the open VR version but with this latest release and open VR plugin, once I select add crop plane, it crashes. On Thu, Mar 29, 2018 at 5:56 PM, Cory Quammen wrote: > By the way, ParaView now ships with the OpenVR and IndeX plugins in > the default binaries for Windows. They are not loaded by default, so > you will have to load them in the plugin manager. You can try it out > in ParaView 5.5.0-RC4 which is available at > https://www.paraview.org/download. > > Thanks, > Cory > > On Tue, Mar 27, 2018 at 9:39 AM, Cory Quammen > wrote: > > Mohamed, > > > > That type of installer for the VR-enabled ParaView is not yet available, > I > > am afraid. I'm not sure anyone has tried the IndeX plugin in VR - it's an > > interesting idea, for sure. > > > > Best regards, > > Cory > > > > On Tue, Mar 27, 2018 at 8:07 AM, Mohamed Beshr > wrote: > >> > >> I am trying to try/use the NVIDIA IndeX plugin on the Paraview VR > version. > >> However, this plugin requires/needs a .exe (installed) version of > Paraview > >> (I tried it with .exe non-VR versions and it works but not with the > >> extracted .zip VR version). The downloads section only has the .zip > version > >> for the VR. Anyone knows of a .exe version in the downloads section? > >> > >> > >> -- > >> Best Regards, > >> Mohamed Beshr > >> > >> _______________________________________________ > >> 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: > >> https://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Best Regards, Mohamed Beshr -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 30 11:39:30 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 30 Mar 2018 11:39:30 -0400 Subject: [Paraview] Alpha Channel for TIFF output In-Reply-To: References: Message-ID: I'd suggest saving out as PNG and then using other image converters to convert to TIFF. On Fri, Mar 30, 2018 at 11:14 AM, eric greenwade wrote: > Trying to figure out how to have paraview include alpha channel when > outputting images, frames which are part of an animation, TIFF in > particular. All the online info I've found points to 1) it be included in an > upcoming release (a while ago), or 2) mentions controls that do not seem to > exist in the 5.5-RC3 version I'm using. > > Any pointers would be greatly appreciated. > > -eric > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Mar 30 11:52:19 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 30 Mar 2018 11:52:19 -0400 Subject: [Paraview] Alpha Channel for TIFF output In-Reply-To: References: Message-ID: > That's fine, but how do I have it include an alpha channel when saving png? > Or is this an option that shows up when selecting png as an output format? In the options dialog, check the **Transparent Background** option. Also, here's an MR to add TIFF support to the save screenshot/save animation dialogs. It'll miss 5.5 release, but will make it into 5.6 slated for later this year. I confirmed that checking the **transparent background** options does indeed save rgba tiff images too after this change. https://gitlab.kitware.com/paraview/paraview/merge_requests/2390 Utkarsh -------------- next part -------------- A non-text attachment was scrubbed... Name: Save Screenshot Options_005.png Type: image/png Size: 33749 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Mar 30 13:24:19 2018 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 30 Mar 2018 13:24:19 -0400 Subject: [Paraview] Volume Rendering Issues/Bugs In-Reply-To: References: Message-ID: Mohamed, If you can share the dataset, it will be easier to point you in the right direction. Feel free to share the data off the mailing list, if needed. Utkarsh On Fri, Mar 30, 2018 at 10:31 AM, Mohamed Beshr wrote: > It is much better now. However, now the tube becomes one solid red color > although the legend range is the same (see screenshot below for difference > between original and re-sampled view). Please advise how can I fix this (I > changed opacity scale shown in the figure between 0 and 1 and still the > same). > > > > > > On Thu, Mar 29, 2018 at 5:43 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> You're getting an empty cubiod because it's showing as outline. Try >> changing the "representation" type to Volume from Outline. Is that any >> better? You may need to adjust your color/opactiy transfer function. >> >> >> >> On Thu, Mar 29, 2018 at 2:49 PM, Mohamed Beshr >> wrote: >> > Thank you for your reply. Yes I have an unstructured grid. Regarding the >> > resample to image filter, when I select it in my case, I get an empty >> > cuboid. Why is that? Is there a way to get the image matching my shape? >> > >> > On Mon, Mar 26, 2018 at 3:38 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> > a. When I select ?Real Time? option and increase the time, even >> >> > though >> >> > it is cached, it still keeps reloading which prevents the VR from >> >> > working. >> >> > Is there any potential/possibility to fix this in the meantime or >> >> > upcoming >> >> > release? >> >> >> >> Caching cannot work in "real time" mode since there's no guarantee >> >> what time each frame will be rendered at. >> >> >> >> > b. When I cache it as a volume (rather than surface, wireframe, >> or >> >> > points) on my laptop, it crashed the exe even when I increase the >> cache >> >> > memory maximum size. Any thoughts on that? I tested it on a bigger >> and >> >> > faster work station and it worked, however, it still has the issue >> >> > mentioned >> >> > in the point below. >> >> >> >> I suspect you're just running out of memory on the system, esp since >> >> you say smaller mesh works. >> >> >> >> > 2. When I get a smaller mesh (4x smaller), I am able to cache >> it as >> >> > a >> >> > volume. However, when playing it back, it keeps reloading while >> showing >> >> > the >> >> > green bar as below at each time step. Is that supposed to happen? Is >> >> > that >> >> > rendering? Is there a way to eliminate it or make it faster? >> >> >> >> Yes, that's rendering. Cache doesn't cache rendering artifacts. Seems >> >> to me you have unstructured grid which is using the slow path for >> >> volume rendering. Another option is to apply "Resample To Image" >> >> filter to resample the dataset to an image and volume rendering the >> >> result. Then rendering should be much faster. You can also resample >> >> and generate the image as a processing stage and save the resampled >> >> dataset out and then load and render it in the animation loop. >> > >> > >> > >> > >> > -- >> > Best Regards, >> > Mohamed Beshr >> > > > > -- > Best Regards, > Mohamed Beshr > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 140024 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 105545 bytes Desc: not available URL: From alexlindsay239 at gmail.com Fri Mar 30 13:59:04 2018 From: alexlindsay239 at gmail.com (Alexander Lindsay) Date: Fri, 30 Mar 2018 11:59:04 -0600 Subject: [Paraview] Fwd: Missing *Hierarchy files in Plugins In-Reply-To: References: Message-ID: Hi, when building paraview from source with either `make` or `ninja` I run into the following type of error: ninja: error: '../Plugins/AnalyzeNIfTIReaderWriter/AnalyzeNIfTIIOHierarchy', needed by 'Plugins/AnalyzeNIfTIReaderWriter/vtkAnalyzeReaderClientServer.cxx', missing and no known rule to make it Sure enough this file doesn't exist. I am currently on the master branch, building on Ubuntu 16.04. I'm guessing/hoping there's an easy fix to this...? Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Fri Mar 30 14:15:06 2018 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 30 Mar 2018 14:15:06 -0400 Subject: [Paraview] Fwd: Missing *Hierarchy files in Plugins In-Reply-To: References: Message-ID: Hi Alexander, There is an easy workaround as long as you don't care about the AnalyzeNIfTIIO plugin: just disable the plugin (set the CMake option PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO to OFF). If you do care about the file formats that that plugin enables, then someone will need to do some more debugging on this. Can you provide more details about which CMake options you are enabling? HTH, Shawn [1]: https://gitlab.kitware.com/paraview/paraview/issues On Fri, Mar 30, 2018 at 1:59 PM, Alexander Lindsay wrote: > Hi, when building paraview from source with either `make` or `ninja` I run > into the following type of error: > > ninja: error: '../Plugins/AnalyzeNIfTIReaderWriter/AnalyzeNIfTIIOHierarchy', > needed by 'Plugins/AnalyzeNIfTIReaderWriter/vtkAnalyzeReaderClientServer.cxx', > missing and no known rule to make it > > Sure enough this file doesn't exist. I am currently on the master branch, > building on Ubuntu 16.04. I'm guessing/hoping there's an easy fix to > this...? > > Alex > > > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexlindsay239 at gmail.com Fri Mar 30 14:27:53 2018 From: alexlindsay239 at gmail.com (Alexander Lindsay) Date: Fri, 30 Mar 2018 12:27:53 -0600 Subject: [Paraview] Fwd: Missing *Hierarchy files in Plugins In-Reply-To: References: Message-ID: I don't care about that plugin, so happy to disable. But if anyone does want to debug, the only option I enabled was `PARAVIEW_USE_MPI` On Fri, Mar 30, 2018 at 12:15 PM, Shawn Waldon wrote: > Hi Alexander, > > There is an easy workaround as long as you don't care about the > AnalyzeNIfTIIO plugin: just disable the plugin (set the CMake option > PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO to OFF). > > If you do care about the file formats that that plugin enables, then > someone will need to do some more debugging on this. Can you provide more > details about which CMake options you are enabling? > > HTH, > Shawn > > [1]: https://gitlab.kitware.com/paraview/paraview/issues > > On Fri, Mar 30, 2018 at 1:59 PM, Alexander Lindsay < > alexlindsay239 at gmail.com> wrote: > >> Hi, when building paraview from source with either `make` or `ninja` I >> run into the following type of error: >> >> ninja: error: '../Plugins/AnalyzeNIfTIReader >> Writer/AnalyzeNIfTIIOHierarchy', needed by 'Plugins/AnalyzeNIfTIReaderWri >> ter/vtkAnalyzeReaderClientServer.cxx', missing and no known rule to make >> it >> >> Sure enough this file doesn't exist. I am currently on the master branch, >> building on Ubuntu 16.04. I'm guessing/hoping there's an easy fix to >> this...? >> >> Alex >> >> >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hng.email at gmail.com Fri Mar 30 15:56:24 2018 From: hng.email at gmail.com (Hom Nath Gharti) Date: Fri, 30 Mar 2018 15:56:24 -0400 Subject: [Paraview] Simple color issue Message-ID: Dear all, I want to make small values to be white, but it appears more like grey as in the attached figure. Is it possible to make small values white in this figure? Thank you for your help. HNG -------------- next part -------------- A non-text attachment was scrubbed... Name: white_color.png Type: image/png Size: 97884 bytes Desc: not available URL: From rccm.kyoshimi at gmail.com Fri Mar 30 23:09:58 2018 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sat, 31 Mar 2018 12:09:58 +0900 Subject: [Paraview] Simple color issue In-Reply-To: References: Message-ID: Hello HNG, The easiest way to solve a dull color problem is to add a headlight. You can find the Lights options by typing "light" in the search bar at the top of the properties panel and clicking the "Edit" button. Then turn on "Additional Headlight" and adjust the headlight intensity in the Lights Editor dialog. Best, 2018-03-31 4:56 GMT+09:00 Hom Nath Gharti : > Dear all, > > I want to make small values to be white, but it appears more like grey > as in the attached figure. Is it possible to make small values white > in this figure? > > Thank you for your help. > HNG > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > From jhaase1 at nd.edu Sat Mar 31 09:14:10 2018 From: jhaase1 at nd.edu (John Haase) Date: Sat, 31 Mar 2018 09:14:10 -0400 Subject: [Paraview] Down sample data? Message-ID: Hello all, I'm trying to down select my data so I can do a grid convergence study. How would I go about doing this? I found an old post ( https://public.kitware.com/pipermail/paraview/2010-November/019453.html) that recomended doing an "extract subset" filter; however that filter is grayed out. Any advice would be appreciated Regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sat Mar 31 14:24:09 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Sat, 31 Mar 2018 14:24:09 -0400 Subject: [Paraview] Down sample data? In-Reply-To: References: Message-ID: Hi John, It depends on what type of grid you have. For image data, rectilinear grid or structured grid the extract subset filter is probably the best (for other grid types it will be grayed out since it's not applicable to those grid types). Otherwise, you can use resample with dataset. Note that both of these will work nicely with point data but for cell data you may want to use the cell data to point data filter first. On Sat, Mar 31, 2018 at 9:14 AM, John Haase wrote: > Hello all, > > I'm trying to down select my data so I can do a grid convergence study. > How would I go about doing this? > > I found an old post (https://public.kitware.com/pipermail/paraview/2010- > November/019453.html) that recomended doing an "extract subset" filter; > however that filter is grayed out. > > Any advice would be appreciated > > Regards, > > John > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Sat Mar 31 14:31:03 2018 From: jhaase1 at nd.edu (John Haase) Date: Sat, 31 Mar 2018 14:31:03 -0400 Subject: [Paraview] Down sample data? In-Reply-To: References: Message-ID: Andy, I found that the "plot over line" filter will allow me to do sampling. However, that has lead me into a second problem. So I feed 2 "plot over line" filters into a "programmable" filter (to take the difference between the two datasets). I then integrate the difference over space using the "integrate variable" filter. Then to extract all the time step values, I try to use the "plot selection over time" filter; however, Paraview crashes when I try to apply the "plot selection over time" filter. Any advice? Regards, John R. Haase jhaase1 at nd.edu On Sat, Mar 31, 2018 at 2:24 PM, Andy Bauer wrote: > Hi John, > > It depends on what type of grid you have. For image data, rectilinear grid > or structured grid the extract subset filter is probably the best (for > other grid types it will be grayed out since it's not applicable to those > grid types). Otherwise, you can use resample with dataset. > > Note that both of these will work nicely with point data but for cell data > you may want to use the cell data to point data filter first. > > On Sat, Mar 31, 2018 at 9:14 AM, John Haase wrote: > >> Hello all, >> >> I'm trying to down select my data so I can do a grid convergence study. >> How would I go about doing this? >> >> I found an old post (https://public.kitware.com/pi >> permail/paraview/2010-November/019453.html) that recomended doing an >> "extract subset" filter; however that filter is grayed out. >> >> Any advice would be appreciated >> >> Regards, >> >> John >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sat Mar 31 14:44:14 2018 From: andy.bauer at kitware.com (Andy Bauer) Date: Sat, 31 Mar 2018 14:44:14 -0400 Subject: [Paraview] Down sample data? In-Reply-To: References: Message-ID: You could try the Append Attributes filter instead of the programmable filter if the geometry is the same for both/all inputs into the Append Attributes filter. To use the Append Attributes filter just select the filters in the Pipeline Browser that you want to compare. Note that for 5.4.1 and earlier you'll need to use something like the Calculator filter to rename the arrays while for the 5.5 release candidate it will do automatic renaming for you. On Sat, Mar 31, 2018 at 2:31 PM, John Haase wrote: > Andy, > > I found that the "plot over line" filter will allow me to do sampling. > However, that has lead me into a second problem. > > So I feed 2 "plot over line" filters into a "programmable" filter (to take > the difference between the two datasets). I then integrate the difference > over space using the "integrate variable" filter. Then to extract all the > time step values, I try to use the "plot selection over time" filter; > however, Paraview crashes when I try to apply the "plot selection over > time" filter. > > Any advice? > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Sat, Mar 31, 2018 at 2:24 PM, Andy Bauer > wrote: > >> Hi John, >> >> It depends on what type of grid you have. For image data, rectilinear >> grid or structured grid the extract subset filter is probably the best (for >> other grid types it will be grayed out since it's not applicable to those >> grid types). Otherwise, you can use resample with dataset. >> >> Note that both of these will work nicely with point data but for cell >> data you may want to use the cell data to point data filter first. >> >> On Sat, Mar 31, 2018 at 9:14 AM, John Haase wrote: >> >>> Hello all, >>> >>> I'm trying to down select my data so I can do a grid convergence study. >>> How would I go about doing this? >>> >>> I found an old post (https://public.kitware.com/pi >>> permail/paraview/2010-November/019453.html) that recomended doing an >>> "extract subset" filter; however that filter is grayed out. >>> >>> Any advice would be appreciated >>> >>> Regards, >>> >>> John >>> >>> _______________________________________________ >>> 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: >>> https://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > 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: > https://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hng.email at gmail.com Sat Mar 31 17:41:45 2018 From: hng.email at gmail.com (Hom Nath Gharti) Date: Sat, 31 Mar 2018 17:41:45 -0400 Subject: [Paraview] Simple color issue In-Reply-To: References: Message-ID: Thank you! Works perfectly! HNG On Fri, Mar 30, 2018 at 11:09 PM, kenichiro yoshimi wrote: > Hello HNG, > > The easiest way to solve a dull color problem is to add a headlight. > You can find the Lights options by typing "light" in the search bar at > the top of the properties panel and clicking the "Edit" button. Then > turn on "Additional Headlight" and adjust the headlight intensity in > the Lights Editor dialog. > > Best, > > 2018-03-31 4:56 GMT+09:00 Hom Nath Gharti : >> Dear all, >> >> I want to make small values to be white, but it appears more like grey >> as in the attached figure. Is it possible to make small values white >> in this figure? >> >> Thank you for your help. >> HNG >> >> _______________________________________________ >> 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: >> https://public.kitware.com/mailman/listinfo/paraview >>