From jeremy.santina at gmail.com Fri Aug 1 05:51:42 2014 From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=) Date: Fri, 1 Aug 2014 11:51:42 +0200 Subject: [Paraview] Bad X server connection Message-ID: Hello, I am using ParaView 4.1.0 RC1 for Linux 64bit. I am connected via ssh and when I am launching pvserver I get this : Waiting for client... Connection URL: cs://diablo.cerfacs.fr:11111 Accepting connection(s): diablo.cerfacs.fr:11111 Thus, the pvserver seems to work fine. But when I am trying to connect to the server, I get this error message : Client connected. No protocol specified ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531 vtkXOpenGLRenderWindow (0x130d6b0): bad X server connection. DISPLAY=:0 No protocol specified ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322 vtkXOpenGLRenderWindow (0x130d6b0): bad X server connection. DISPLAY=:0 Segmentation fault (core dumped) I don't know how to fix this because I don't really know where the problem could come from. I launched a pvserver on an other machine and I could connect without having this issue so I guess the problem doesn't come from my client machine. Do you have any hints about how to solve this ? Thanks. J?r?my -------------- next part -------------- An HTML attachment was scrubbed... URL: From nktasingh at gmail.com Fri Aug 1 12:04:32 2014 From: nktasingh at gmail.com (Nikita Singh) Date: Fri, 1 Aug 2014 12:04:32 -0400 Subject: [Paraview] Screenshot question Message-ID: Hello, I'm using Python's Tkinter to display a screenshot from Paraview. As part of the app, I need to "get" some pixel colors in the screenshot. When I get the screenshot using my own computer's function, the app works correctly. (Just to be explicit, here's the steps involved: 1. Render the vtk file in Paraview 2. Screenshot the image, save as PNG 3. Convert PNG to PPM using an online tool 4. Display the PPM on a Tkinter Canvas 5. "Get" the RGB value at some pixel in the PPM image) However, when the screenshot comes from Parview's own method, the RGB values are always that of the image background - even though I've tested which image coordinates I'm "getting" the pixel colors. Do you have an explanation for why the pixels are only registering as the background image? Or why there's this discrepancy between the two screenshot methods? Thanks! Nikita -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Fri Aug 1 16:56:54 2014 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Fri, 1 Aug 2014 16:56:54 -0400 (EDT) Subject: [Paraview] Extracting closed surfaces from an isosurface In-Reply-To: <274656084.25042808.1406926296870.JavaMail.root@mail.gatech.edu> Message-ID: <346392231.25044167.1406926614912.JavaMail.root@mail.gatech.edu> Hi all, I am working on a programmable filter and I want to extract and analyze data generated by an isosurface. I'm having a hard time coming up with generic data to represent what I mean, but I'll try to describe it. I run my data and generate an isosurface for a single value. The resulting isosurface generates disconnected/independent blobs in space. I've attached an image of what it looks like. I would like to take each of those independent surfaces and manipulate them (compute volume of each, or maximum cross sectional area, or find a central axis, or delete them based on the computed volume, etc) but I can't figure out how to extract the data I need through VTK. I have the vtkPolyData array as well as the normals array, but I cannot figure out how to use that information to isolate and extract the independent surfaces. Does anybody have any suggestions or examples I can look at on how to manipulate the data? Thanks, Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: isosurface.png Type: image/png Size: 105237 bytes Desc: not available URL: From andy.bauer at kitware.com Fri Aug 1 20:36:09 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 1 Aug 2014 20:36:09 -0400 Subject: [Paraview] Extracting closed surfaces from an isosurface In-Reply-To: <346392231.25044167.1406926614912.JavaMail.root@mail.gatech.edu> References: <274656084.25042808.1406926296870.JavaMail.root@mail.gatech.edu> <346392231.25044167.1406926614912.JavaMail.root@mail.gatech.edu> Message-ID: Hi Tim, You can try the Connectivity filter to create RegionId point and cell data arrays to each blob set of cells. From there threshold can be used to pick out individual blobs. You may need to use the merge blocks filter first though if you're starting from a multiblock data set. I'm not sure if this will work in parallel since the Connectivity filter could get algorithmically complex. If you try it in parallel, I'd be interested in knowing if it works or not. Regards, Andy On Fri, Aug 1, 2014 at 4:56 PM, Tim Gallagher wrote: > Hi all, > > I am working on a programmable filter and I want to extract and analyze > data generated by an isosurface. I'm having a hard time coming up with > generic data to represent what I mean, but I'll try to describe it. > > I run my data and generate an isosurface for a single value. The resulting > isosurface generates disconnected/independent blobs in space. I've attached > an image of what it looks like. I would like to take each of those > independent surfaces and manipulate them (compute volume of each, or > maximum cross sectional area, or find a central axis, or delete them based > on the computed volume, etc) but I can't figure out how to extract the data > I need through VTK. I have the vtkPolyData array as well as the normals > array, but I cannot figure out how to use that information to isolate and > extract the independent surfaces. > > Does anybody have any suggestions or examples I can look at on how to > manipulate the data? > > Thanks, > > Tim > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Sat Aug 2 05:34:40 2014 From: denis.cohen at gmail.com (denis cohen) Date: Sat, 2 Aug 2014 11:34:40 +0200 Subject: [Paraview] Writing csv data in python script Message-ID: Hi, New to python scripting. How can one output a csv file inside a python script/macro? I am trying the wiki: >>> writer = CreateWriter(".../foo.csv", source) >>> writer.FieldAssociation = "Points" # or "Cells" >>> writer.UpdatePipeline() >>> del writer But I get: Traceback (most recent call last): File "", line 173, in AttributeError: 'str' object has no attribute 'UpdatePipeline' Thanks for any help. Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Wiesenberger at uibk.ac.at Sat Aug 2 17:56:36 2014 From: Matthias.Wiesenberger at uibk.ac.at (Wiesenberger, Matthias) Date: Sat, 2 Aug 2014 21:56:36 +0000 Subject: [Paraview] netcdf-4 Message-ID: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> Hi, I downloaded and installed paraview via my ubuntu package manager. I then generated some data with my code using a freshly installed netcdf library. Paraview can read and visualize that data without complaints. However, I now want to make use of the parallel I/O features that the new netcdf-4 (enhanced) data model (sometimes called Common Data Model) proviedes. The thing is that paraview obviously can't read the new file format. Every time I want to read data in the new netcdf4/HDF5 data model I get to a list of readers to choose from. I've been trying to find a solution for that for some while now, but I'm at a total loss, is there a hidden option somewhere? Should I reinstall paraview? I can also promise not to use any nasty HDF5 features in my files like groups or new fancy datatypes (there is creation flag for this NC_CLASSIC_MODEL) i.e. use the old data model but the new format if that helps. Can you help me with this? Best Matthias -------------- next part -------------- An HTML attachment was scrubbed... URL: From vanpva at rambler.ru Sun Aug 3 03:04:46 2014 From: vanpva at rambler.ru (Van) Date: Sun, 3 Aug 2014 11:04:46 +0400 Subject: [Paraview] selection by coordinates Message-ID: <1407049486.263118.25860.28147@mail.rambler.ru> I know how to select a cell manually and plot a quantity in the selection over time. After that I can find the selection through "Find Data" menu since "Selection Inspector" is no more available. But what if I know exactly the coordinates of a point which I want to select and I do not want to guest where it is visually? Is it possible? Thank you, Van From mrhyde at stanford.edu Mon Aug 4 03:17:50 2014 From: mrhyde at stanford.edu (D H) Date: Mon, 4 Aug 2014 00:17:50 -0700 (PDT) Subject: [Paraview] Default Options in Export Scene In-Reply-To: <1179019731.9650.1407135764478.JavaMail.zimbra@stanford.edu> Message-ID: <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> Hi all, I have been using File->Export Scene a lot lately to generate EPS/PDF figures. For all of the figures I've been generating, I've wanted to use the same (non-default, advanced) export settings. So each time I export a scene, I find myself clicking four or five buttons to get the correct settings, which gets a bit annoying after the tenth or twentieth image. Of course, this inconvenience isn't too bad, but it would be very cool if there were a way to change the default settings for Export Scene. Or at least have PV remember/default to the last export settings I used, across different instances of the program? I looked and did not find a way to do this already - if this is already a feature and I'm just missing something, I would be grateful for anybody to point out the obvious thing I'm missing. Otherwise, maybe it would be possible to have this considered as a feature request for the next PV release? Thanks very much! David From sebastien.jourdain at kitware.com Mon Aug 4 10:39:11 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 4 Aug 2014 08:39:11 -0600 Subject: [Paraview] Default Options in Export Scene In-Reply-To: <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> References: <1179019731.9650.1407135764478.JavaMail.zimbra@stanford.edu> <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> Message-ID: Hi David, you can also generate a macro that will do it for you. Which will bring down your interaction to 1 click. Seb On Mon, Aug 4, 2014 at 1:17 AM, D H wrote: > Hi all, > > I have been using File->Export Scene a lot lately to generate EPS/PDF > figures. For all of the figures I've been generating, I've wanted to use > the same (non-default, advanced) export settings. So each time I export a > scene, I find myself clicking four or five buttons to get the correct > settings, which gets a bit annoying after the tenth or twentieth image. > > Of course, this inconvenience isn't too bad, but it would be very cool if > there were a way to change the default settings for Export Scene. Or at > least have PV remember/default to the last export settings I used, across > different instances of the program? I looked and did not find a way to do > this already - if this is already a feature and I'm just missing something, > I would be grateful for anybody to point out the obvious thing I'm missing. > Otherwise, maybe it would be possible to have this considered as a feature > request for the next PV release? > > Thanks very much! > > David > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Aug 4 11:10:17 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 4 Aug 2014 11:10:17 -0400 Subject: [Paraview] netcdf-4 In-Reply-To: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> Message-ID: Which version of ParaView does ubuntu provide? True netcdf4 support first appeared in 3.98 as I recall. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias < Matthias.Wiesenberger at uibk.ac.at> wrote: > Hi, > I downloaded and installed paraview via my ubuntu package manager. I then > generated some data with my code using a freshly installed netcdf library. > Paraview can read and visualize that data without complaints. However, I > now want to make use of the parallel I/O features that the new netcdf-4 > (enhanced) data model (sometimes called Common Data Model) proviedes. The > thing is that paraview obviously can't read the new file format. Every time > I want to read data in the new netcdf4/HDF5 data model I get to a list of > readers to choose from. I've been trying to find a solution for that for > some while now, but I'm at a total loss, is there a hidden option > somewhere? Should I reinstall paraview? I can also promise not to use any > nasty HDF5 features in my files like groups or new fancy datatypes (there > is creation flag for this NC_CLASSIC_MODEL) i.e. use the old data model but > the new format if that helps. > Can you help me with this? > Best > Matthias > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Aug 4 11:21:34 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 4 Aug 2014 11:21:34 -0400 Subject: [Paraview] netcdf-4 In-Reply-To: References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> Message-ID: also, it will help if you can share your data (sample one) with us. - Aashish On Mon, Aug 4, 2014 at 11:10 AM, David E DeMarle wrote: > Which version of ParaView does ubuntu provide? > > True netcdf4 support first appeared in 3.98 as I recall. > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias < > Matthias.Wiesenberger at uibk.ac.at> wrote: > >> Hi, >> I downloaded and installed paraview via my ubuntu package manager. I >> then generated some data with my code using a freshly installed netcdf >> library. Paraview can read and visualize that data without complaints. >> However, I now want to make use of the parallel I/O features that the new >> netcdf-4 (enhanced) data model (sometimes called Common Data Model) >> proviedes. The thing is that paraview obviously can't read the new file >> format. Every time I want to read data in the new netcdf4/HDF5 data model I >> get to a list of readers to choose from. I've been trying to find a >> solution for that for some while now, but I'm at a total loss, is there a >> hidden option somewhere? Should I reinstall paraview? I can also promise >> not to use any nasty HDF5 features in my files like groups or new fancy >> datatypes (there is creation flag for this NC_CLASSIC_MODEL) i.e. use the >> old data model but the new format if that helps. >> Can you help me with this? >> Best >> Matthias >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Wiesenberger at uibk.ac.at Mon Aug 4 11:42:37 2014 From: Matthias.Wiesenberger at uibk.ac.at (Matthias Wiesenberger) Date: Mon, 04 Aug 2014 17:42:37 +0200 Subject: [Paraview] netcdf-4 In-Reply-To: References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> Message-ID: <53DFA9ED.7050900@uibk.ac.at> Hi, my paraview is version 4.01 64-bit. I attached a sample file for you. It's generated from one of the netcdf example codes modified only by the additional creation flag NC_NETCDF4. Matthias On 08/04/2014 05:21 PM, Aashish Chaudhary wrote: > also, it will help if you can share your data (sample one) with us. > > - Aashish > > > On Mon, Aug 4, 2014 at 11:10 AM, David E DeMarle > > wrote: > > Which version of ParaView does ubuntu provide? > > True netcdf4 support first appeared in 3.98 as I recall. > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias > > wrote: > > Hi, > I downloaded and installed paraview via my ubuntu package > manager. I then generated some data with my code using a > freshly installed netcdf library. Paraview can read and > visualize that data without complaints. However, I now want to > make use of the parallel I/O features that the new netcdf-4 > (enhanced) data model (sometimes called Common Data Model) > proviedes. The thing is that paraview obviously can't read the > new file format. Every time I want to read data in the new > netcdf4/HDF5 data model I get to a list of readers to choose > from. I've been trying to find a solution for that for some > while now, but I'm at a total loss, is there a hidden option > somewhere? Should I reinstall paraview? I can also promise not > to use any nasty HDF5 features in my files like groups or new > fancy datatypes (there is creation flag for this > NC_CLASSIC_MODEL) i.e. use the old data model but the new format > if that helps. > Can you help me with this? > Best > Matthias > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -- Matthias Wiesenberger University of Innsbruck, Austria Institut f?r Ionen- und angewandte Physik Technikerstrasse 25/3, A-6020 Innsbruck Tel.: +43 (0)512 507 52725 E-Mail: Matthias.Wiesenberger at uibk.ac.at -------------- next part -------------- A non-text attachment was scrubbed... Name: sfc_pres_temp.nc Type: application/x-netcdf Size: 7002 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sfc_pres_temp_wr.c Type: text/x-csrc Size: 5855 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Aug 4 13:03:33 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 4 Aug 2014 13:03:33 -0400 Subject: [Paraview] Default Options in Export Scene In-Reply-To: <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> References: <1179019731.9650.1407135764478.JavaMail.zimbra@stanford.edu> <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> Message-ID: Hi David, We are currently working on making it possible to set custom default values throughout ParaView, and will target the Export Scene settings for the ParaView 4.2 release. For an idea of what this will look like, please see http://www.kitware.com/blog/home/post/702. Thanks, Cory On Mon, Aug 4, 2014 at 3:17 AM, D H wrote: > Hi all, > > I have been using File->Export Scene a lot lately to generate EPS/PDF figures. For all of the figures I've been generating, I've wanted to use the same (non-default, advanced) export settings. So each time I export a scene, I find myself clicking four or five buttons to get the correct settings, which gets a bit annoying after the tenth or twentieth image. > > Of course, this inconvenience isn't too bad, but it would be very cool if there were a way to change the default settings for Export Scene. Or at least have PV remember/default to the last export settings I used, across different instances of the program? I looked and did not find a way to do this already - if this is already a feature and I'm just missing something, I would be grateful for anybody to point out the obvious thing I'm missing. Otherwise, maybe it would be possible to have this considered as a feature request for the next PV release? > > Thanks very much! > > David > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Mon Aug 4 15:01:20 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 04 Aug 2014 21:01:20 +0200 Subject: [Paraview] what if you have two qt-installations? Message-ID: <53DFD880.7070103@xs4all.nl> Hello, On my system, I have 2 installations of QT5. One is the distribution that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other one is a more recent version (5.3.1), which I downloaded and installed in a different location. Using ccmake, setting the QT version to 5, as well as setting QT_QMAKE_EXECUTABLE to qmake of the new location, I still see that ccmake selects of number of qt5-libraries that belong to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, in fact). I can build paraview, though, and it even seems to work (smoketest), but at program exit it segfaults. I wonder how I can tell cmake to configure for 1 qt version. Surely, I don't need to change all the entries by hand? Thanks in advance Bertwim From cory.quammen at kitware.com Mon Aug 4 15:11:48 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 4 Aug 2014 15:11:48 -0400 Subject: [Paraview] Default Options in Export Scene In-Reply-To: <472773557.1001410.1407178235560.JavaMail.zimbra@stanford.edu> References: <1179019731.9650.1407135764478.JavaMail.zimbra@stanford.edu> <608880426.15636.1407136670369.JavaMail.zimbra@stanford.edu> <472773557.1001410.1407178235560.JavaMail.zimbra@stanford.edu> Message-ID: David, The second JSON should be correct. However, these particular settings are currently ignored in the Export Options dialog. I'll fix that. One more thing: I changed the blog post to update the location of this settings file, which should be ~/.config/ParaView/ParaView-UserSettings.json. Thanks, Cory On Mon, Aug 4, 2014 at 2:50 PM, David Hyde wrote: > Thanks for the replies! Seb, I tried to record a macro for setting the options I want (via Tools->Start/Stop Trace), but nothing substantive got recorded in the resulting generated Python script. Can these options (e.g., "Rasterize 3D Geometry") be changed via a macro, and if so, any tips on how to set that up? > > Cory, it's good to hear 4.2 will support custom defaults as described in the blog post - looks good! In the meantime, I followed a link on that blog post to http://kitware.com/blog/home/post/672 , which discusses changing default values by editing ~/.config/ParaView/UserSettings.json . I looked in the ParaView source at ParaView/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml and found the properties that I wanted to change. So I wrote the following UserSettings.json: > > { > "utilities" : { > "exporters" : { > "GL2PSExporterBase" : { > "SetTitle" : "", > "SetOcclusionCull" : 0 > }, > "GL2PSRenderViewExporterBase" : { > "SetSort" : 2, > "Write3DPropsAsRasterImage" : 0 > } > } > } > } > > However, when I opened up ParaView after saving this file, the settings I'd specified were not picked up. I also tried: > > { > "exporters" : { > "GL2PSExporterBase" : { > "SetTitle" : "", > "SetOcclusionCull" : 0 > }, > "GL2PSRenderViewExporterBase" : { > "SetSort" : 2, > "Write3DPropsAsRasterImage" : 0 > } > } > } > > but got the same (no) effect. Are these settings changeable via JSON like I'm trying to do? If so, I would greatly appreciate your help in debugging my JSON and figuring out what's going wrong. > > Thanks again! > > David > > ----- Original Message ----- > From: "Cory Quammen" > To: "D H" > Cc: "ParaView" > Sent: Monday, August 4, 2014 10:03:33 AM > Subject: Re: [Paraview] Default Options in Export Scene > > Hi David, > > We are currently working on making it possible to set custom default > values throughout ParaView, and will target the Export Scene settings > for the ParaView 4.2 release. > > For an idea of what this will look like, please see > http://www.kitware.com/blog/home/post/702. > > Thanks, > Cory > > On Mon, Aug 4, 2014 at 3:17 AM, D H wrote: >> Hi all, >> >> I have been using File->Export Scene a lot lately to generate EPS/PDF figures. For all of the figures I've been generating, I've wanted to use the same (non-default, advanced) export settings. So each time I export a scene, I find myself clicking four or five buttons to get the correct settings, which gets a bit annoying after the tenth or twentieth image. >> >> Of course, this inconvenience isn't too bad, but it would be very cool if there were a way to change the default settings for Export Scene. Or at least have PV remember/default to the last export settings I used, across different instances of the program? I looked and did not find a way to do this already - if this is already a feature and I'm just missing something, I would be grateful for anybody to point out the obvious thing I'm missing. Otherwise, maybe it would be possible to have this considered as a feature request for the next PV release? >> >> Thanks very much! >> >> David >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From dennis_conklin at goodyear.com Mon Aug 4 15:21:20 2014 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 4 Aug 2014 19:21:20 +0000 Subject: [Paraview] Help with Programmable Filter Message-ID: <1407180080018.38754@goodyear.com> I have the following script for a Paraview Programmable filter: import math import numpy # # Gdyr_Principal_Strains_ProgFilter # Rev 0 # Aug 1, 2014 # Dennis Conklin - Engineering Mechanics # # Paraview 4.0.1 Progammable Filter # Adds Cell Variables: # Principal Strains: str_P1, str_P2, str_P3 # max shear strain: tau_max # These can be used for coloring, Spreadsheet view, formulas, threshold, etc # def process_block(block): # # Global coordinate strains # Assume strains loaded in Paraview xx = block.CellData['USTRTOTXX'] yy = block.CellData['USTRTOTYY'] zz = block.CellData['USTRTOTZZ'] xy = block.CellData['USTRTOTXY'] xz = block.CellData['USTRTOTZX'] yz = block.CellData['USTRTOTYZ'] for i in range(block.GetNumberOfCells() sigma = numpy.array([ [xx[i],xy[i],xz[i]], [xy[i],yy[i],yz[i]], [xz[i],yz[i],zz[i]] ]) # isotropic strain matrix iso = 1.0/3.0*numpy.trace(sigma)*numpy.eye(3) # deviatoric strain matrix dev = sigma - iso #principal strains eigvals = list(numpy.linalg.eigvalsh(sigma)) eigvals.sort() eigvals.reverse() P1[i] = eigvals[0] P2[i] = eigvals[1] P3[i] = eigvals[2] # max shear max_shear[i] = (max(eigvals)-min(eigvals))/2.0 block.CellData.append(P1,"P1_strain") block.CellData.append(P2,"P2_strain") block.CellData.append(P3,"P3_strain") block.CellData.append(max_shear,"tauMax") # Loop over blocks in composite (Exodus) data set for block in output: # process each block process_block(block) After running this script, no errors or warnings are issued but the additional quantites (taumax, Px_strain) are not present as element quantities. Any hints as to what I'm doing wrong. Dennis Conklin, PE RDE&Q Senior Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Mon Aug 4 16:04:38 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 04 Aug 2014 13:04:38 -0700 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53DFD880.7070103@xs4all.nl> References: <53DFD880.7070103@xs4all.nl> Message-ID: <53DFE756.4070309@lbl.gov> system install may be first in the linker search path. have you checked? If that's it: rm your build, and in addition to QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run PV do the same. On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: > Hello, > > On my system, I have 2 installations of QT5. One is the distribution > that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other > one is a more recent version (5.3.1), which I downloaded and installed > in a different location. > Using ccmake, setting the QT version to 5, as well as setting > QT_QMAKE_EXECUTABLE to qmake of the new location, > I still see that ccmake selects of number of qt5-libraries that belong > to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, > in fact). I can build paraview, though, and it even seems to work > (smoketest), but at program exit it segfaults. > > I wonder how I can tell cmake to configure for 1 qt version. Surely, I > don't need to change all the entries by hand? > > Thanks in advance > Bertwim > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From simon.m.su.ctr at mail.mil Mon Aug 4 16:29:52 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 4 Aug 2014 20:29:52 +0000 Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, >From a tutorial I attended on ParaView + Catalyst, I sort of get the idea of all the parts involved. However, from effort point of view, on an average case, how many man hours would be estimated to develop a Catalyst Bridge and get it to work in ParaView for a homegrown discrete element method code written in python with some functionality in wrapped fortran, but the data needed for visualization is exposed to python? Just a ballpark guess (min/max would be nice). I want to know how big of a project I am getting myself into... :) Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From tim.gallagher at gatech.edu Mon Aug 4 16:41:40 2014 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Mon, 4 Aug 2014 16:41:40 -0400 (EDT) Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) In-Reply-To: Message-ID: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> Hi Simon, I've gone through the process myself and it actually was not that painful, but how long it takes will depend on how familiar you are with VTK already. It's almost trivial if your code's data structures already use VTK. If they don't, then it's a matter of translating your data into the VTK data structures which isn't too bad in Python. Our code is in Fortran and is a parallel, finite volume, structured, multi-block code. So in some ways it's a bit easier to define the data structures in VTK as they are structured and I don't need to worry about connectivity. I wrote the wrappers and interface code in less than a week with no prior knowledge of VTK but a very strong desire to make it work :) This was a few years back when the documentation on Catalyst wasn't very mature so it was probably harder than it would have been now. I can't be any more specific or give you advice on how long it will take with your code, but it was much easier than I expected it to be when I did it. Tim ----- Original Message ----- From: "Simon M CTR USARMY ARL Su (US)" To: paraview at paraview.org Sent: Monday, August 4, 2014 4:29:52 PM Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Classification: UNCLASSIFIED Caveats: NONE Hello, >From a tutorial I attended on ParaView + Catalyst, I sort of get the idea of all the parts involved. However, from effort point of view, on an average case, how many man hours would be estimated to develop a Catalyst Bridge and get it to work in ParaView for a homegrown discrete element method code written in python with some functionality in wrapped fortran, but the data needed for visualization is exposed to python? Just a ballpark guess (min/max would be nice). I want to know how big of a project I am getting myself into... :) Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From mvanmoer at illinois.edu Mon Aug 4 17:31:37 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Mon, 4 Aug 2014 21:31:37 +0000 Subject: [Paraview] Reader ctors called multiple times? Message-ID: <7F781841FF1E044388AFA42B70703A7A89EF4240@CHIMBX6.ad.uillinois.edu> Ah, is it because the exeutive's ProcessRequest is doing all three of REQUEST_DATA, REQUEST_INFORMATION, and REQUEST_DATA_OBJECT ? From: Vanmoer, Mark W Sent: Monday, August 04, 2014 4:04 PM To: paraview Subject: Reader ctors called multiple times? Hello ParaView, I've inherited a project that writes plugins for ParaView 3.14.1, serial. While debugging I found out that the constructor for one of this project's file readers is called 3 times when loading a file. I thought this was odd, so I tried setting a break point on vtkUnstructuredGridReader's ctor and discovered that it's called twice. However, a constructor for vtk source plugin that I wrote is only called once, as I would have guessed for the others. Is it normal for readers to have their constructors called multiple times when loading a file? Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Mon Aug 4 17:04:27 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Mon, 4 Aug 2014 21:04:27 +0000 Subject: [Paraview] Reader ctors called multiple times? Message-ID: <7F781841FF1E044388AFA42B70703A7A89EF4201@CHIMBX6.ad.uillinois.edu> Hello ParaView, I've inherited a project that writes plugins for ParaView 3.14.1, serial. While debugging I found out that the constructor for one of this project's file readers is called 3 times when loading a file. I thought this was odd, so I tried setting a break point on vtkUnstructuredGridReader's ctor and discovered that it's called twice. However, a constructor for vtk source plugin that I wrote is only called once, as I would have guessed for the others. Is it normal for readers to have their constructors called multiple times when loading a file? Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Mon Aug 4 17:38:18 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 04 Aug 2014 14:38:18 -0700 Subject: [Paraview] Reader ctors called multiple times? In-Reply-To: <7F781841FF1E044388AFA42B70703A7A89EF4240@CHIMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A89EF4240@CHIMBX6.ad.uillinois.edu> Message-ID: <53DFFD4A.3050006@lbl.gov> I thought it was twice. The first one ParaView when creates the reader to call CanReadFile in its search for potential readers of the file. The second one when it builds the pipeline. On 08/04/2014 02:31 PM, Vanmoer, Mark W wrote: > > Ah, is it because the exeutive's ProcessRequest is doing all three of > REQUEST_DATA, REQUEST_INFORMATION, and REQUEST_DATA_OBJECT ? > > *From:* Vanmoer, Mark W > *Sent:* Monday, August 04, 2014 4:04 PM > *To:* paraview > *Subject:* Reader ctors called multiple times? > > Hello ParaView, > > I've inherited a project that writes plugins for ParaView 3.14.1, > serial. While debugging I found out that the constructor for one of > this project's file readers is called 3 times when loading a file. I > thought this was odd, so I tried setting a break point on > vtkUnstructuredGridReader's ctor and discovered that it's called > twice. However, a constructor for vtk source plugin that I wrote is > only called once, as I would have guessed for the others. > > Is it normal for readers to have their constructors called multiple > times when loading a file? > > Thanks, > > Mark > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Aug 4 21:13:50 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 4 Aug 2014 21:13:50 -0400 Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) In-Reply-To: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> References: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> Message-ID: Hi Simon, It can be a fairly wide range to do that. I was able to do it for Chris Kees' Proteus code in an hour. But he already had VTK data structures created for his own internal in situ stuff and it was with Python so even compilation issues were very easy (also, we sat down together to do it so all of the knowledge was there). I generally try to allocate two weeks to do that assuming that I'll do a decent amount of the work figuring out the simulation code on my own as well as waiting some for answers to emails. If the code isn't "cmakeified" then it also adds a bit of time to it as well. If you're not that familiar with the simulation code I suggest focusing on the part of the code that writes out the simulation information (grid and fields) to files. That generally has all of the information you need to know in order to create the VTK data structures to represent their data structures. Regards, Andy On Mon, Aug 4, 2014 at 4:41 PM, Tim Gallagher wrote: > Hi Simon, > > I've gone through the process myself and it actually was not that painful, > but how long it takes will depend on how familiar you are with VTK already. > It's almost trivial if your code's data structures already use VTK. If they > don't, then it's a matter of translating your data into the VTK data > structures which isn't too bad in Python. > > Our code is in Fortran and is a parallel, finite volume, structured, > multi-block code. So in some ways it's a bit easier to define the data > structures in VTK as they are structured and I don't need to worry about > connectivity. I wrote the wrappers and interface code in less than a week > with no prior knowledge of VTK but a very strong desire to make it work :) > This was a few years back when the documentation on Catalyst wasn't very > mature so it was probably harder than it would have been now. > > I can't be any more specific or give you advice on how long it will take > with your code, but it was much easier than I expected it to be when I did > it. > > Tim > > ----- Original Message ----- > From: "Simon M CTR USARMY ARL Su (US)" > To: paraview at paraview.org > Sent: Monday, August 4, 2014 4:29:52 PM > Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) > > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > From a tutorial I attended on ParaView + Catalyst, I sort of get the idea > of > all the parts involved. However, from effort point of view, on an average > case, how many man hours would be estimated to develop a Catalyst Bridge > and > get it to work in ParaView for a homegrown discrete element method code > written in python with some functionality in wrapped fortran, but the data > needed for visualization is exposed to python? Just a ballpark guess > (min/max would be nice). I want to know how big of a project I am getting > myself into... :) > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nagler at lnm.mw.tum.de Tue Aug 5 07:40:06 2014 From: nagler at lnm.mw.tum.de (Andreas Nagler) Date: Tue, 05 Aug 2014 13:40:06 +0200 Subject: [Paraview] Meta File (*.mha, *.mhd) Import: Is header file transformation matrix used correctly? Message-ID: <53E0C296.7090300@lnm.mw.tum.de> Dear community, while loading Meta Image Files (*.mhd *.mha), I noticed that the local coordinate axes of the resulting array stack are aligned to the global coordinate axes, though I would expect that the given transformation matrix within the header part would lead to an arbitrarily aligned spatial configuration. After some testing I discovered that changing the given header Offset vector changes also the imported result, but changing the transformation matrix did not influence the result at all. Is this a bug? Or did I miss a relevant library? I was testing on a precompiled Paraview v3.98 and a self-compiled (64bit Unix, Fedora 16) Paraview v4.1 Thanks for the answer Andreas -- -------------------------------------------------------------- Dipl.-Tech. Math Andreas Nagler Email: nagler at lnm.mw.tum.de Phone: +49 (0) 89 289 15264 Fax: +49 (0) 89 289 15301 www:http://www.lnm.mw.tum.de/staff/andreas-nagler/ From hayannasser at gmail.com Tue Aug 5 08:49:37 2014 From: hayannasser at gmail.com (Hayan Nasser) Date: Tue, 5 Aug 2014 13:49:37 +0100 Subject: [Paraview] Unsupported Cell Attribute Type Error In VTK Legacy File Format Message-ID: Hello, I'm trying to add vector information to an animation frame which is in the VTK Legacy file format. When just including the scalar information, I receive no errors when opening the animation in paraview. However, now when I append the vector information to the file, I receive the following error: ERROR: In /build/buildd/paraview-3.10.1/VTK/IO/vtkDataReader.cxx, line 766 vtkPolyDataReader (0x39b5400): Unsupported cell attribute type: 0 for file: cyl_res20_new/VTK/2D/DC100-material1-boundaryopen-observation10-time1e-09.1.vtk I must be missing something with defining the data set, but I have followed through the VTK file format documentation, and I can't see where I am going wrong! If you could take a quick look and see if I am missing something obvious I would be most grateful! Many Thanks Hayan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DC100-material1-boundaryopen-observation10-time1e-09.1.vtk Type: application/octet-stream Size: 4468 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Tue Aug 5 09:04:58 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 5 Aug 2014 13:04:58 +0000 Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) In-Reply-To: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> References: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Tim, Thanks for the insight. The simulation code already dealing with vtk data structure. With what you mentioned, I feel more comfortable moving forward. Thanks -simon -----Original Message----- From: Tim Gallagher [mailto:tim.gallagher at gatech.edu] Sent: Monday, August 04, 2014 4:42 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Hi Simon, I've gone through the process myself and it actually was not that painful, but how long it takes will depend on how familiar you are with VTK already. It's almost trivial if your code's data structures already use VTK. If they don't, then it's a matter of translating your data into the VTK data structures which isn't too bad in Python. Our code is in Fortran and is a parallel, finite volume, structured, multi-block code. So in some ways it's a bit easier to define the data structures in VTK as they are structured and I don't need to worry about connectivity. I wrote the wrappers and interface code in less than a week with no prior knowledge of VTK but a very strong desire to make it work :) This was a few years back when the documentation on Catalyst wasn't very mature so it was probably harder than it would have been now. I can't be any more specific or give you advice on how long it will take with your code, but it was much easier than I expected it to be when I did it. Tim ----- Original Message ----- From: "Simon M CTR USARMY ARL Su (US)" To: paraview at paraview.org Sent: Monday, August 4, 2014 4:29:52 PM Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Classification: UNCLASSIFIED Caveats: NONE Hello, >From a tutorial I attended on ParaView + Catalyst, I sort of get the idea of all the parts involved. However, from effort point of view, on an average case, how many man hours would be estimated to develop a Catalyst Bridge and get it to work in ParaView for a homegrown discrete element method code written in python with some functionality in wrapped fortran, but the data needed for visualization is exposed to python? Just a ballpark guess (min/max would be nice). I want to know how big of a project I am getting myself into... :) Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Tue Aug 5 09:11:44 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 5 Aug 2014 13:11:44 +0000 Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) In-Reply-To: References: <2064161355.25806019.1407184900394.JavaMail.root@mail.gatech.edu> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Andy, Thanks for your insight.... I will know more on the complexity when I dig more into it. Thanks -simon -----Original Message----- From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Monday, August 04, 2014 9:14 PM To: tim gallagher Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Hi Simon, It can be a fairly wide range to do that. I was able to do it for Chris Kees' Proteus code in an hour. But he already had VTK data structures created for his own internal in situ stuff and it was with Python so even compilation issues were very easy (also, we sat down together to do it so all of the knowledge was there). I generally try to allocate two weeks to do that assuming that I'll do a decent amount of the work figuring out the simulation code on my own as well as waiting some for answers to emails. If the code isn't "cmakeified" then it also adds a bit of time to it as well. If you're not that familiar with the simulation code I suggest focusing on the part of the code that writes out the simulation information (grid and fields) to files. That generally has all of the information you need to know in order to create the VTK data structures to represent their data structures. Regards, Andy On Mon, Aug 4, 2014 at 4:41 PM, Tim Gallagher wrote: Hi Simon, I've gone through the process myself and it actually was not that painful, but how long it takes will depend on how familiar you are with VTK already. It's almost trivial if your code's data structures already use VTK. If they don't, then it's a matter of translating your data into the VTK data structures which isn't too bad in Python. Our code is in Fortran and is a parallel, finite volume, structured, multi-block code. So in some ways it's a bit easier to define the data structures in VTK as they are structured and I don't need to worry about connectivity. I wrote the wrappers and interface code in less than a week with no prior knowledge of VTK but a very strong desire to make it work :) This was a few years back when the documentation on Catalyst wasn't very mature so it was probably harder than it would have been now. I can't be any more specific or give you advice on how long it will take with your code, but it was much easier than I expected it to be when I did it. Tim ----- Original Message ----- From: "Simon M CTR USARMY ARL Su (US)" To: paraview at paraview.org Sent: Monday, August 4, 2014 4:29:52 PM Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED) Classification: UNCLASSIFIED Caveats: NONE Hello, From a tutorial I attended on ParaView + Catalyst, I sort of get the idea of all the parts involved. However, from effort point of view, on an average case, how many man hours would be estimated to develop a Catalyst Bridge and get it to work in ParaView for a homegrown discrete element method code written in python with some functionality in wrapped fortran, but the data needed for visualization is exposed to python? Just a ballpark guess (min/max would be nice). I want to know how big of a project I am getting myself into... :) Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From jeremy.santina at gmail.com Tue Aug 5 10:48:27 2014 From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=) Date: Tue, 5 Aug 2014 16:48:27 +0200 Subject: [Paraview] ParaView can't create the reader Message-ID: Hello, I have written my own reader for ParaView and I am facing with some issues. My version of ParaView is 4.1 for Windows-64 bit and I didn't build it from sources. As the wiki describes, I wrote a Server Manager XML file. Then I set the environment flag PV_PLUGIN_DEBUG. Everything seems to work fine when I load the reader with Plugin Manager as the output messages dialog box indicates : *************************************************** Attempting to load C:\Users\Windows\Documents\Travail\ParaviewProject\VTKReaders\Plugin\TecplotBinaryReader.xml Loading XML plugin Plugin instance located successfully. Now loading components from the plugin instance based on the interfaces it implements. ---------------------------------------------------------------- Plugin Information: Name : TecplotBinaryReader Version : 1.0 ReqOnServer : 1 ReqOnClient : 0 ReqPlugins : ServerManager Plugin : Yes Python Plugin : No But when I try to open a file, ParaView crashes and I get the following error message : ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, line 307 vtkSISourceProxy (000000000B340ED0): Failed to create vtkPTecplotBinaryReader. Aborting for debugging purposes. What am I doing wrong ? Thanks in advance for your help. J?r?my -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 5 11:02:24 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 5 Aug 2014 11:02:24 -0400 Subject: [Paraview] Reader ctors called multiple times? In-Reply-To: <53DFFD4A.3050006@lbl.gov> References: <7F781841FF1E044388AFA42B70703A7A89EF4240@CHIMBX6.ad.uillinois.edu> <53DFFD4A.3050006@lbl.gov> Message-ID: Burlen's got it right. I am curious why the plugin was only called once. Maybe there is no CanReadFile() or no file extension collision of something like that in one case but not the other? Mark: ProcessRequest() calls RDO(), RI(), and RD() (in that order) only after paraview creates the instance that it will actually use to read the file with. All are typically only called once, unless some parameter on the reader changes. If RD is called more often check to see if image based extents are mismatched. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 4, 2014 at 5:38 PM, Burlen Loring wrote: > I thought it was twice. The first one ParaView when creates the reader to > call CanReadFile in its search for potential readers of the file. The > second one when it builds the pipeline. > > > On 08/04/2014 02:31 PM, Vanmoer, Mark W wrote: > > Ah, is it because the exeutive?s ProcessRequest is doing all three of > REQUEST_DATA, REQUEST_INFORMATION, and REQUEST_DATA_OBJECT ? > > > > *From:* Vanmoer, Mark W > *Sent:* Monday, August 04, 2014 4:04 PM > *To:* paraview > *Subject:* Reader ctors called multiple times? > > > > Hello ParaView, > > > > I?ve inherited a project that writes plugins for ParaView 3.14.1, serial. > While debugging I found out that the constructor for one of this project?s > file readers is called 3 times when loading a file. I thought this was odd, > so I tried setting a break point on vtkUnstructuredGridReader?s ctor and > discovered that it?s called twice. However, a constructor for vtk source > plugin that I wrote is only called once, as I would have guessed for the > others. > > > > Is it normal for readers to have their constructors called multiple times > when loading a file? > > > > Thanks, > > Mark > > > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe:http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Aug 5 12:07:56 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 05 Aug 2014 18:07:56 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53DFE756.4070309@lbl.gov> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> Message-ID: <53E1015C.10207@xs4all.nl> Hi Burien, thanks for responding. I have done you suggested, but to no avail. Somehow, the path to the executable qmake is not sufficient to determine all the other QT5 libraries. Having said that, in one of the by now many attempts to get paraview configured, I found that indeed the correct QT5 libraries were selected. That build, however failed (missing symbol, cannot remember which one). In trying to correct this is, the wrong QT5 libraries were selected by ccmake. I just cannot figure out how this cmake thing works, or what I can do to force it. Any suggestions? Kind Regards, Bertwim On 08/04/2014 10:04 PM, Burlen Loring wrote: > system install may be first in the linker search path. have you > checked? If that's it: rm your build, and in addition to > QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to > LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run > PV do the same. > > On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >> Hello, >> >> On my system, I have 2 installations of QT5. One is the distribution >> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >> one is a more recent version (5.3.1), which I downloaded and installed >> in a different location. >> Using ccmake, setting the QT version to 5, as well as setting >> QT_QMAKE_EXECUTABLE to qmake of the new location, >> I still see that ccmake selects of number of qt5-libraries that belong >> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >> in fact). I can build paraview, though, and it even seems to work >> (smoketest), but at program exit it segfaults. >> >> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >> don't need to change all the entries by hand? >> >> Thanks in advance >> Bertwim >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > From simon.m.su.ctr at mail.mil Tue Aug 5 12:00:23 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 5 Aug 2014 16:00:23 +0000 Subject: [Paraview] file size with xdmf3 writer from trunk (paraview version 4.1.0-1212-g781aa0e) Message-ID: Hello, I would like to convert (using "File->Safe Data" option) some pvtp file into xmf file using the new xdmf file exporter in ParaView trunk. The pvtp files were generated while running in parallel using 8 mpi processes, so I have 8 vtp files for every pvtp file. The pvtp file has a list out all the pieces (vtp files). I also have 30 time steps for the data so I have 30 of the pvtp files. When I tried to save it out using xdmf3 writer, the collection of pvtp and vtp files which are a total of 80MB in size grew to 1023MB in h5/xmf format. In another instance, a 817MB pvtp/vtp files grew to 13G when converted to h5/xmf file format. Is there a compression that I can turn on to reduce the size of the file? Or is it something wrong (option not checked) that I am doing that cause the file size to increase more than 10 times? thanks -simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Aug 5 12:40:49 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 5 Aug 2014 16:40:49 +0000 Subject: [Paraview] Movies from my desktop Message-ID: <1258c74853b24eb4ada17f1581242d2a@ES05AMSNLNT.srn.sandia.gov> I want to make a movie of my screen as I interact with ParaView. Since I want to see a user's interactions with ParaView, Save Animation isn't what I want. Does anyone know of a tool that will do this? Windows, Mac or Linux are fine. Thanks! Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Tue Aug 5 12:44:40 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Tue, 5 Aug 2014 16:44:40 +0000 Subject: [Paraview] Movies from my desktop (UNCLASSIFIED) In-Reply-To: <1258c74853b24eb4ada17f1581242d2a@ES05AMSNLNT.srn.sandia.gov> References: <1258c74853b24eb4ada17f1581242d2a@ES05AMSNLNT.srn.sandia.gov> Message-ID: <345817C8A61EA841AAE0120EC1514D955F1CADE8@umechpanz.easf.csd.disa.mil> Classification: UNCLASSIFIED Caveats: NONE "ffmpeg" will do this on Linux. The command looks something like: ffmpeg -f x11grab -s 1680x1050 -r 30 -i :0.0 -sameq /tmp/out.mpg ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Tuesday, August 05, 2014 12:41 PM To: paraview at paraview.org Subject: [Paraview] Movies from my desktop I want to make a movie of my screen as I interact with ParaView. Since I want to see a user's interactions with ParaView, Save Animation isn't what I want. Does anyone know of a tool that will do this? Windows, Mac or Linux are fine. Thanks! Alan Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5627 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Aug 5 12:46:46 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 5 Aug 2014 12:46:46 -0400 Subject: [Paraview] Movies from my desktop In-Reply-To: <1258c74853b24eb4ada17f1581242d2a@ES05AMSNLNT.srn.sandia.gov> References: <1258c74853b24eb4ada17f1581242d2a@ES05AMSNLNT.srn.sandia.gov> Message-ID: <29C4B87F-9CAB-4577-B772-045AC70427A6@kitware.com> I use 'RecordMyDesktop' on Linux and 'QuickTime Player' on Mac. Utkarsh > On Aug 5, 2014, at 12:40 PM, "Scott, W Alan" wrote: > > I want to make a movie of my screen as I interact with ParaView. Since I want to see a user?s interactions with ParaView, Save Animation isn?t what I want. Does anyone know of a tool that will do this? Windows, Mac or Linux are fine. > > Thanks! > > Alan > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Aug 5 12:41:22 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 5 Aug 2014 12:41:22 -0400 Subject: [Paraview] Calculating Wall Height In-Reply-To: References: Message-ID: I think this may have to be a separate filter since there's quite a bit involved in order to do this properly. The closest I can think of for doing this is using the Mesh Quality filter and assuming that the shortest length of a cell is in the normal direction for cells on the boundary of CFD meshes. Additionally, I don't know if the Mesh Quality filter works for prisms either. Regards, Andy On Wed, Jul 30, 2014 at 10:03 PM, Magician wrote: > Hi all, > > > I?d like to get height values of wall cells for calculating oil shear > velocity or y+. > My datasets have no information about wall direction, prism layer or > inside, center of cells. > > Does anyone have good ideas to do it? > > > Magician > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hayannasser at gmail.com Tue Aug 5 12:54:45 2014 From: hayannasser at gmail.com (Hayan Nasser) Date: Tue, 5 Aug 2014 17:54:45 +0100 Subject: [Paraview] Movies from my desktop Message-ID: I've used Camtasia for this in the past. http://www.techsmith.com/camtasia.html This is not a free piece of software, however I believe that older versions of the software can be obtained for free. http://www.techsmith.com/download/oldversions.asp camstudio (http://camstudio.org/) is an open source alternative too. On Tue, Aug 5, 2014 at 5:40 PM, Scott, W Alan wrote: > I want to make a movie of my screen as I interact with ParaView. Since > I want to see a user?s interactions with ParaView, Save Animation isn?t > what I want. Does anyone know of a tool that will do this? Windows, Mac > or Linux are fine. > > Thanks! > > Alan > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 5 13:15:18 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 5 Aug 2014 13:15:18 -0400 Subject: [Paraview] file size with xdmf3 writer from trunk (paraview version 4.1.0-1212-g781aa0e) In-Reply-To: References: Message-ID: Probably a bug and not a case of a missing an option. Can you share the pvtp and vtp files with me off list? Otherwise, please advise me as to how to recreate the behavior with standard sources and/or regression test data sets so I can investigate. Thanks for trying the new reader and reporting the problem! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 5, 2014 at 12:00 PM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Hello, > > I would like to convert (using "File->Safe Data" option) some pvtp file > into xmf file using the new xdmf file exporter in ParaView trunk. The pvtp > files were generated while running in parallel using 8 mpi processes, so I > have 8 vtp files for every pvtp file. The pvtp file has a list out all the > pieces (vtp files). I also have 30 time steps for the data so I have 30 of > the pvtp files. > > When I tried to save it out using xdmf3 writer, the collection of pvtp and > vtp files which are a total of 80MB in size grew to 1023MB in h5/xmf > format. In another instance, a 817MB pvtp/vtp files grew to 13G when > converted to h5/xmf file format. > > Is there a compression that I can turn on to reduce the size of the file? > Or is it something wrong (option not checked) that I am doing that cause > the file size to increase more than 10 times? > > thanks > -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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Tue Aug 5 13:38:37 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Tue, 5 Aug 2014 13:38:37 -0400 Subject: [Paraview] Writing csv data in python script In-Reply-To: References: Message-ID: Denis, You could look here on lines 468-476 for how this is done in VeloView. You can ignore the rotateCSVFile function call. On Sat, Aug 2, 2014 at 5:34 AM, denis cohen wrote: > Hi, > New to python scripting. How can one output a csv file inside a python > script/macro? > I am trying the wiki: > >>> writer = CreateWriter(".../foo.csv", source) > >>> writer.FieldAssociation = "Points" # or "Cells" > >>> writer.UpdatePipeline() > >>> del writer > > But I get: > Traceback (most recent call last): > File "", line 173, in > AttributeError: 'str' object has no attribute 'UpdatePipeline' > > Thanks for any help. > > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 5 14:03:14 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 5 Aug 2014 14:03:14 -0400 Subject: [Paraview] Help with Programmable Filter In-Reply-To: <1407180080018.38754@goodyear.com> References: <1407180080018.38754@goodyear.com> Message-ID: for i in range(block.GetNumberOfCells() > sigma = numpy.array([ [xx[i],xy[i],xz[i]], > [xy[i],yy[i],yz[i]], > [xz[i],yz[i],zz[i]] > ]) > > Missing a ":" here maybe? Try some print debugging to see what is really happening. Also, I recommend using an external editor and copy/pasting the code in or execfile("yourfile.py")'ing to develop for the programmable filter. It's QtTextWidget is a tad deficient as an IDE. :) If not the ":" let us know and we can look further. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 5 14:32:18 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 5 Aug 2014 14:32:18 -0400 Subject: [Paraview] netcdf-4 In-Reply-To: <53DFA9ED.7050900@uibk.ac.at> References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> <53DFA9ED.7050900@uibk.ac.at> Message-ID: In a fresh build of paraview master on a mac, I can read this file without a problem. When I go to open the file I'm given a choice of "CAM NetCDF (Unstructured)" or "NetCDF files generic and CF conventions". Choose netcdf cf and, accept defaults and hit apply and I see the data, curvilinear with 72/91 cells and points and two cell aligned float arrays, pressure and temperature. It is possible to turn OFF support for netcdf4 if VTK_USE_SYSTEM_HDF5 on and HDF5_HL is off that will happen. I am guessing that is what is going on here in ubuntu's ParaView package. You can: try a nightly build from the kitware download site ask the ubuntu packager to turn it on in the future build paraview yourself from source hth David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 4, 2014 at 11:42 AM, Matthias Wiesenberger < Matthias.Wiesenberger at uibk.ac.at> wrote: > Hi, my paraview is version 4.01 64-bit. I attached a sample file for you. > It's generated from one of the netcdf example codes modified only by the > additional creation flag NC_NETCDF4. > Matthias > > > > On 08/04/2014 05:21 PM, Aashish Chaudhary wrote: > >> also, it will help if you can share your data (sample one) with us. >> >> - Aashish >> >> >> On Mon, Aug 4, 2014 at 11:10 AM, David E DeMarle >> > wrote: >> >> Which version of ParaView does ubuntu provide? >> >> True netcdf4 support first appeared in 3.98 as I recall. >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> >> >> On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias >> > > wrote: >> >> Hi, >> I downloaded and installed paraview via my ubuntu package >> manager. I then generated some data with my code using a >> freshly installed netcdf library. Paraview can read and >> visualize that data without complaints. However, I now want to >> make use of the parallel I/O features that the new netcdf-4 >> (enhanced) data model (sometimes called Common Data Model) >> proviedes. The thing is that paraview obviously can't read the >> new file format. Every time I want to read data in the new >> netcdf4/HDF5 data model I get to a list of readers to choose >> from. I've been trying to find a solution for that for some >> while now, but I'm at a total loss, is there a hidden option >> somewhere? Should I reinstall paraview? I can also promise not >> to use any nasty HDF5 features in my files like groups or new >> fancy datatypes (there is creation flag for this >> NC_CLASSIC_MODEL) i.e. use the old data model but the new format >> if that helps. >> Can you help me with this? >> Best >> Matthias >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ >> > > > -- > Matthias Wiesenberger > > University of Innsbruck, Austria > Institut f?r Ionen- und angewandte Physik > Technikerstrasse 25/3, A-6020 Innsbruck > > Tel.: +43 (0)512 507 52725 > E-Mail: Matthias.Wiesenberger at uibk.ac.at > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 5 14:37:31 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 5 Aug 2014 14:37:31 -0400 Subject: [Paraview] Help with Programmable Filter In-Reply-To: <1407263172166.57108@goodyear.com> References: <1407180080018.38754@goodyear.com> <1407263172166.57108@goodyear.com> Message-ID: hmm, should show up in the output messages window and on the console. Start paraview from a command line to see the console. Agreed on the need for an example. p.s. Please "reply all" to keep the discussion on the list so everyone can contribute and benefit (or consider a kitware support contract). David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 5, 2014 at 2:26 PM, Dennis Conklin wrote: > David, > > > The : did not make it work. I hate to be a complete newby, but where > would a Programmable filter print if a Programmable filter has a debugging > print? I'm not getting anything in the Output Messages window. > > > Thanks I feel like a good multi-dataset CellData example is needed in > the wiki - I have a PointData filter working. > > ? > Dennis Conklin, PE > RDE&Q Senior Engineer > Goodyear Innovation Center, 5th Floor South, Pillar M34 > Phone: 330-796-5701 > Email: dennis_conklin at goodyear.com > ------------------------------ > *From:* David E DeMarle > *Sent:* Tuesday, August 05, 2014 2:03 PM > *To:* Dennis Conklin > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Help with Programmable Filter > > for i in range(block.GetNumberOfCells() > >> sigma = numpy.array([ [xx[i],xy[i],xz[i]], >> [xy[i],yy[i],yz[i]], >> [xz[i],yz[i],zz[i]] >> ]) >> >> > Missing a ":" here maybe? > > Try some print debugging to see what is really happening. > > Also, I recommend using an external editor and copy/pasting the code in > or execfile("yourfile.py")'ing to develop for the programmable filter. It's > QtTextWidget is a tad deficient as an IDE. :) > > If not the ":" let us know and we can look further. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.huebl at hzdr.de Tue Aug 5 14:38:15 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Tue, 05 Aug 2014 20:38:15 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53E1015C.10207@xs4all.nl> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> Message-ID: <53E12497.7080301@hzdr.de> Dear Bertwim, have you tried prepending/setting the CMAKE_PREFIX_PATH to your qt5 install dir? Best, Axel On 05.08.2014 18:07, B.W.H. van Beest wrote: > Hi Burien, thanks for responding. > > I have done you suggested, but to no avail. > Somehow, the path to the executable qmake is not sufficient to determine > all the other QT5 libraries. > Having said that, in one of the by now many attempts to get paraview > configured, I found that indeed the correct QT5 libraries were selected. > That build, however failed (missing symbol, cannot remember which one). > In trying to correct this is, the wrong QT5 libraries were selected by > ccmake. I just cannot figure out how this cmake thing works, or what I > can do to force it. > Any suggestions? > > Kind Regards, > Bertwim > > > > On 08/04/2014 10:04 PM, Burlen Loring wrote: >> system install may be first in the linker search path. have you >> checked? If that's it: rm your build, and in addition to >> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >> PV do the same. >> >> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>> Hello, >>> >>> On my system, I have 2 installations of QT5. One is the distribution >>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>> one is a more recent version (5.3.1), which I downloaded and installed >>> in a different location. >>> Using ccmake, setting the QT version to 5, as well as setting >>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>> I still see that ccmake selects of number of qt5-libraries that belong >>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>> in fact). I can build paraview, though, and it even seems to work >>> (smoketest), but at program exit it segfaults. >>> >>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>> don't need to change all the entries by hand? >>> >>> Thanks in advance >>> Bertwim -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5002 bytes Desc: S/MIME Cryptographic Signature URL: From simon.m.su.ctr at mail.mil Tue Aug 5 14:42:56 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 5 Aug 2014 18:42:56 +0000 Subject: [Paraview] file size with xdmf3 writer from trunk (paraview version 4.1.0-1212-g781aa0e) (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Dave, Thanks for looking into this. I will email you the link to download the file in a little bit. Thanks -simon -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Tuesday, August 05, 2014 1:15 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] file size with xdmf3 writer from trunk (paraview version 4.1.0-1212-g781aa0e) Probably a bug and not a case of a missing an option. Can you share the pvtp and vtp files with me off list? Otherwise, please advise me as to how to recreate the behavior with standard sources and/or regression test data sets so I can investigate. Thanks for trying the new reader and reporting the problem! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 5, 2014 at 12:00 PM, Su, Simon M CTR USARMY ARL (US) wrote: Hello, I would like to convert (using "File->Safe Data" option) some pvtp file into xmf file using the new xdmf file exporter in ParaView trunk. The pvtp files were generated while running in parallel using 8 mpi processes, so I have 8 vtp files for every pvtp file. The pvtp file has a list out all the pieces (vtp files). I also have 30 time steps for the data so I have 30 of the pvtp files. When I tried to save it out using xdmf3 writer, the collection of pvtp and vtp files which are a total of 80MB in size grew to 1023MB in h5/xmf format. In another instance, a 817MB pvtp/vtp files grew to 13G when converted to h5/xmf file format. Is there a compression that I can turn on to reduce the size of the file? Or is it something wrong (option not checked) that I am doing that cause the file size to increase more than 10 times? thanks -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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From bwvb at xs4all.nl Tue Aug 5 15:37:52 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 05 Aug 2014 21:37:52 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53E12497.7080301@hzdr.de> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> Message-ID: <53E13290.9000503@xs4all.nl> Dear Axel, No I haven't. To follow-up on your suggestion, I ran ccmake again to set this parameter. No CMAKE_PREFIX_PATH is in the list! What I did try -and what did make a difference, was not only prepending the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin was first in $PATH. This indeed has the result that all libQt5 directories found were the correct ones. Maybe that amounts to the same? However, Now I have a different compile error: CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In function `pqNativeFileDialogEventPlayer::start()': pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to `qt_filedialog_existing_directory_hook' pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to `qt_filedialog_open_filename_hook' pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to `qt_filedialog_open_filenames_hook' pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to `qt_filedialog_save_filename_hook' CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In function `pqNativeFileDialogEventPlayer::stop()': etc. Any ideas? On 08/05/2014 08:38 PM, Huebl, Axel wrote: > Dear Bertwim, > > have you tried prepending/setting the > CMAKE_PREFIX_PATH > > to your qt5 install dir? > > Best, > Axel > On 05.08.2014 18:07, B.W.H. van Beest wrote: >> Hi Burien, thanks for responding. >> >> I have done you suggested, but to no avail. >> Somehow, the path to the executable qmake is not sufficient to determine >> all the other QT5 libraries. >> Having said that, in one of the by now many attempts to get paraview >> configured, I found that indeed the correct QT5 libraries were selected. >> That build, however failed (missing symbol, cannot remember which one). >> In trying to correct this is, the wrong QT5 libraries were selected by >> ccmake. I just cannot figure out how this cmake thing works, or what I >> can do to force it. >> Any suggestions? >> >> Kind Regards, >> Bertwim >> >> >> >> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>> system install may be first in the linker search path. have you >>> checked? If that's it: rm your build, and in addition to >>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>> PV do the same. >>> >>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>> Hello, >>>> >>>> On my system, I have 2 installations of QT5. One is the distribution >>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>> one is a more recent version (5.3.1), which I downloaded and installed >>>> in a different location. >>>> Using ccmake, setting the QT version to 5, as well as setting >>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>> I still see that ccmake selects of number of qt5-libraries that belong >>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>> in fact). I can build paraview, though, and it even seems to work >>>> (smoketest), but at program exit it segfaults. >>>> >>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>> don't need to change all the entries by hand? >>>> >>>> Thanks in advance >>>> Bertwim From Matthias.Wiesenberger at uibk.ac.at Wed Aug 6 05:03:10 2014 From: Matthias.Wiesenberger at uibk.ac.at (Matthias Wiesenberger) Date: Wed, 06 Aug 2014 11:03:10 +0200 Subject: [Paraview] netcdf-4 In-Reply-To: References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> <53DFA9ED.7050900@uibk.ac.at> Message-ID: <53E1EF4E.5000804@uibk.ac.at> Hi David, that helped a lot, thanks very much. I downloaded v4.1 from the paraview site and it opens netcdf-4 as you describe. thanks again Matthias On 08/05/2014 08:32 PM, David E DeMarle wrote: > In a fresh build of paraview master on a mac, I can read this file > without a problem. When I go to open the file I'm given a choice of "CAM > NetCDF (Unstructured)" or "NetCDF files generic and CF conventions". > Choose netcdf cf and, accept defaults and hit apply and I see the data, > curvilinear with 72/91 cells and points and two cell aligned float > arrays, pressure and temperature. > > It is possible to turn OFF support for netcdf4 if VTK_USE_SYSTEM_HDF5 on > and HDF5_HL is off that will happen. I am guessing that is what is going > on here in ubuntu's ParaView package. > > You can: > try a nightly build from the kitware download site > ask the ubuntu packager to turn it on in the future > build paraview yourself from source > > hth > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Mon, Aug 4, 2014 at 11:42 AM, Matthias Wiesenberger > > wrote: > > Hi, my paraview is version 4.01 64-bit. I attached a sample file for > you. It's generated from one of the netcdf example codes modified > only by the additional creation flag NC_NETCDF4. > Matthias > > > > On 08/04/2014 05:21 PM, Aashish Chaudhary wrote: > > also, it will help if you can share your data (sample one) with us. > > - Aashish > > > On Mon, Aug 4, 2014 at 11:10 AM, David E DeMarle > > >> wrote: > > Which version of ParaView does ubuntu provide? > > True netcdf4 support first appeared in 3.98 as I recall. > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > > On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias > > >> wrote: > > Hi, > I downloaded and installed paraview via my ubuntu package > manager. I then generated some data with my code using a > freshly installed netcdf library. Paraview can read and > visualize that data without complaints. However, I now > want to > make use of the parallel I/O features that the new netcdf-4 > (enhanced) data model (sometimes called Common Data Model) > proviedes. The thing is that paraview obviously can't > read the > new file format. Every time I want to read data in the new > netcdf4/HDF5 data model I get to a list of readers to > choose > from. I've been trying to find a solution for that for some > while now, but I'm at a total loss, is there a hidden > option > somewhere? Should I reinstall paraview? I can also > promise not > to use any nasty HDF5 features in my files like groups > or new > fancy datatypes (there is creation flag for this > NC_CLASSIC_MODEL) i.e. use the old data model but the > new format > if that helps. > Can you help me with this? > Best > Matthias > > _________________________________________________ > 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 > > > Follow this link to subscribe/unsubscribe: > http://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 > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/__mailman/listinfo/paraview > > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/__company/team/chaudhary.html/ > > > > > -- > Matthias Wiesenberger > > University of Innsbruck, Austria > Institut f?r Ionen- und angewandte Physik > Technikerstrasse 25/3, A-6020 Innsbruck > > Tel.: +43 (0)512 507 52725 > E-Mail: Matthias.Wiesenberger at uibk.ac.__at > > > -- Matthias Wiesenberger University of Innsbruck, Austria Institut f?r Ionen- und angewandte Physik Technikerstrasse 25/3, A-6020 Innsbruck Tel.: +43 (0)512 507 52725 E-Mail: Matthias.Wiesenberger at uibk.ac.at From a.huebl at hzdr.de Wed Aug 6 05:34:36 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Wed, 06 Aug 2014 11:34:36 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53E13290.9000503@xs4all.nl> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> <53E13290.9000503@xs4all.nl> Message-ID: <53E1F6AC.1090709@hzdr.de> Dear Bertwim, good to hear that. sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and "LD_LIBRARY_PATH" to hint install directories to CMake modules. The compile error still looks like something got mixed - can you try again with the CMAKE_PREFIX_PATH hint? Did you verify all "advanced" variables set from the FindQt module with ccmake? Best, Axel On 05.08.2014 21:37, B.W.H. van Beest wrote: > Dear Axel, > > No I haven't. To follow-up on your suggestion, I ran ccmake again to set > this parameter. No CMAKE_PREFIX_PATH is in the list! > What I did try -and what did make a difference, was not only prepending > the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin > was first in $PATH. This indeed has the result that all libQt5 > directories found were the correct ones. Maybe that amounts to the same? > > However, Now I have a different compile error: > > CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In > function `pqNativeFileDialogEventPlayer::start()': > pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to > `qt_filedialog_existing_directory_hook' > pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to > `qt_filedialog_open_filename_hook' > pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to > `qt_filedialog_open_filenames_hook' > pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to > `qt_filedialog_save_filename_hook' > CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In > function `pqNativeFileDialogEventPlayer::stop()': > > > etc. > > Any ideas? > > > > > > > On 08/05/2014 08:38 PM, Huebl, Axel wrote: >> Dear Bertwim, >> >> have you tried prepending/setting the >> CMAKE_PREFIX_PATH >> >> to your qt5 install dir? >> >> Best, >> Axel >> On 05.08.2014 18:07, B.W.H. van Beest wrote: >>> Hi Burien, thanks for responding. >>> >>> I have done you suggested, but to no avail. >>> Somehow, the path to the executable qmake is not sufficient to determine >>> all the other QT5 libraries. >>> Having said that, in one of the by now many attempts to get paraview >>> configured, I found that indeed the correct QT5 libraries were selected. >>> That build, however failed (missing symbol, cannot remember which one). >>> In trying to correct this is, the wrong QT5 libraries were selected by >>> ccmake. I just cannot figure out how this cmake thing works, or what I >>> can do to force it. >>> Any suggestions? >>> >>> Kind Regards, >>> Bertwim >>> >>> >>> >>> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>>> system install may be first in the linker search path. have you >>>> checked? If that's it: rm your build, and in addition to >>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>>> PV do the same. >>>> >>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>>> Hello, >>>>> >>>>> On my system, I have 2 installations of QT5. One is the distribution >>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>>> one is a more recent version (5.3.1), which I downloaded and installed >>>>> in a different location. >>>>> Using ccmake, setting the QT version to 5, as well as setting >>>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>>> I still see that ccmake selects of number of qt5-libraries that belong >>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>>> in fact). I can build paraview, though, and it even seems to work >>>>> (smoketest), but at program exit it segfaults. >>>>> >>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>>> don't need to change all the entries by hand? >>>>> >>>>> Thanks in advance >>>>> Bertwim > > > -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5002 bytes Desc: S/MIME Cryptographic Signature URL: From dave.demarle at kitware.com Wed Aug 6 08:24:08 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 6 Aug 2014 08:24:08 -0400 Subject: [Paraview] netcdf-4 In-Reply-To: <53E1EF4E.5000804@uibk.ac.at> References: <4E5215E5BFF302498EEEE6D65C76C9B6203B03C1@XMBX4.uibk.ac.at> <53DFA9ED.7050900@uibk.ac.at> <53E1EF4E.5000804@uibk.ac.at> Message-ID: Great! I'll get in contact with the ubuntu manager and help him or her enable it there too. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 6, 2014 at 5:03 AM, Matthias Wiesenberger < Matthias.Wiesenberger at uibk.ac.at> wrote: > Hi David, > > that helped a lot, thanks very much. I downloaded v4.1 from the paraview > site and it opens netcdf-4 as you describe. > > thanks again > Matthias > > > On 08/05/2014 08:32 PM, David E DeMarle wrote: > >> In a fresh build of paraview master on a mac, I can read this file >> without a problem. When I go to open the file I'm given a choice of "CAM >> NetCDF (Unstructured)" or "NetCDF files generic and CF conventions". >> Choose netcdf cf and, accept defaults and hit apply and I see the data, >> curvilinear with 72/91 cells and points and two cell aligned float >> arrays, pressure and temperature. >> >> It is possible to turn OFF support for netcdf4 if VTK_USE_SYSTEM_HDF5 on >> and HDF5_HL is off that will happen. I am guessing that is what is going >> on here in ubuntu's ParaView package. >> >> You can: >> try a nightly build from the kitware download site >> ask the ubuntu packager to turn it on in the future >> build paraview yourself from source >> >> hth >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> >> On Mon, Aug 4, 2014 at 11:42 AM, Matthias Wiesenberger >> > > wrote: >> >> Hi, my paraview is version 4.01 64-bit. I attached a sample file for >> you. It's generated from one of the netcdf example codes modified >> only by the additional creation flag NC_NETCDF4. >> Matthias >> >> >> >> On 08/04/2014 05:21 PM, Aashish Chaudhary wrote: >> >> also, it will help if you can share your data (sample one) with >> us. >> >> - Aashish >> >> >> On Mon, Aug 4, 2014 at 11:10 AM, David E DeMarle >> >> > >> >> wrote: >> >> Which version of ParaView does ubuntu provide? >> >> True netcdf4 support first appeared in 3.98 as I recall. >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 > >> > >> >> >> >> On Sat, Aug 2, 2014 at 5:56 PM, Wiesenberger, Matthias >> > >> > >> >> wrote: >> >> Hi, >> I downloaded and installed paraview via my ubuntu package >> manager. I then generated some data with my code using a >> freshly installed netcdf library. Paraview can read and >> visualize that data without complaints. However, I now >> want to >> make use of the parallel I/O features that the new >> netcdf-4 >> (enhanced) data model (sometimes called Common Data >> Model) >> proviedes. The thing is that paraview obviously can't >> read the >> new file format. Every time I want to read data in the >> new >> netcdf4/HDF5 data model I get to a list of readers to >> choose >> from. I've been trying to find a solution for that for >> some >> while now, but I'm at a total loss, is there a hidden >> option >> somewhere? Should I reinstall paraview? I can also >> promise not >> to use any nasty HDF5 features in my files like groups >> or new >> fancy datatypes (there is creation flag for this >> NC_CLASSIC_MODEL) i.e. use the old data model but the >> new format >> if that helps. >> Can you help me with this? >> Best >> Matthias >> >> _________________________________________________ >> >> 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 >> >> >> >> Follow this link to subscribe/unsubscribe: >> http://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 >> >> >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/__mailman/listinfo/paraview >> >> >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/__company/team/chaudhary.html/ >> >> >> >> >> >> -- >> Matthias Wiesenberger >> >> University of Innsbruck, Austria >> Institut f?r Ionen- und angewandte Physik >> Technikerstrasse 25/3, A-6020 Innsbruck >> >> Tel.: +43 (0)512 507 52725 >> E-Mail: Matthias.Wiesenberger at uibk.ac.__at >> >> >> >> > > -- > Matthias Wiesenberger > > University of Innsbruck, Austria > Institut f?r Ionen- und angewandte Physik > Technikerstrasse 25/3, A-6020 Innsbruck > > Tel.: +43 (0)512 507 52725 > E-Mail: Matthias.Wiesenberger at uibk.ac.at > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno.santos at bluecape.com.pt Wed Aug 6 08:59:21 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Wed, 06 Aug 2014 13:59:21 +0100 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit Message-ID: <53E226A9.8070002@bluecape.com.pt> Greetings to all! We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for Windows 32 and 64-bit, based on the official SuperBuild and respective build options. It's available here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 Instructions on how these packages were built is provided here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 According to our tests, it's possible to use this SDK to build plug-ins and any other associated applications, which will work with the respective official ParaView 4.1.0 builds for Windows. A proof of concept we've used is the vtkPOFFReader plug-in which was successfully built with these SDK packages: https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds Note: We roughly used the same development environment as the original ParaView 4.1.0 binaries for Windows: http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC 2008 C++ Express and did not have a respective FORTRAN compiler (which requires the Professional version either way), which is why we needed to do some adjustments to build Open-MPI with success. Furthermore, here's a bit of a back story and the current status of this endeavour: * Back in January 2012 we at blueCAPE began to try to bring back the development installers of ParaView for Windows, which was last officially available for ParaView 3.8.1. * The overall features available in the development installers we created were still missing important files, because we were still basing ourselves on the infrastructure that was still remnant from ParaView 3.8.1. * Nonetheless, we made available our findings and builds for ParaView 3.12.0, 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was back in January 2013. * ParaView fortunately kept evolving since then. We missed the versions 3.98.1 and 4.0.1, due to time constraints on our side and a few failed builds. * As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure which evolved overtime. The official SuperBuild repository also already provides many of the necessary features for making the SDK releases, at least for the Unix-like environments. * This Summer 2014 we at blueCAPE finally managed to get around back to trying and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK for Windows and believe we have successfully achieved it. The changes have been shared and referenced in the following wiki page at our project: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 * In addition to this, after some reviewing and building tests with the latest commits on the master branch from the SuperBuild repository, we have adapted most of the changes we've developed for the SDK build above and have submitted two commits to Kitware Gerrit, namely: o http://review.source.kitware.com/#/t/4487/ o http://review.source.kitware.com/#/t/4488/ * We haven't managed to create the NSIS and ZIP packages through CMake/CPack, but our main concern has mostly been on having a working SDK. Hopefully this can help bring sooner the ParaView SDK in future versions in a more official way... so that we won't have to look into generating the NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) If anyone has any questions, feel free to ask! Best regards, Bruno Santos PS: I haven't sent this email to the ParaView Developers mailing list simply because previous emails I've sent on this topic have been to this main mailing list. -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Wed Aug 6 15:28:38 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 6 Aug 2014 19:28:38 +0000 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, I would like to run some of my VTK python code under ParaView (pvbatch or pvpython). Where can I find documentation on porting VTK python code to use ParaView python api? I need to create some VTK object in ParaView. Is there a shortcut to this (like being able to use VTK python api within ParaView Python environment)? Or am I not making sense / asking the wrong question. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From andy.bauer at kitware.com Wed Aug 6 15:35:20 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 6 Aug 2014 15:35:20 -0400 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: It may not be possible to do what you want explicitly. ParaView can be viewed in some ways a wrapper around VTK filters. You can try the programmable filter which uses the VTK Python API but is still intended to operate like a filter (i.e. not modifying the input data sets, etc.). Andy On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I would like to run some of my VTK python code under ParaView (pvbatch or > pvpython). Where can I find documentation on porting VTK python code to use > ParaView python api? I need to create some VTK object in ParaView. Is there > a shortcut to this (like being able to use VTK python api within ParaView > Python environment)? Or am I not making sense / asking the wrong question. > > Any help is much appreciated. > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Aug 6 15:45:21 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 6 Aug 2014 13:45:21 -0600 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Hi Simon, if the VTK work that you are targeting is not parallel, you can directly run a vtkpython script inside pvpython or pvbatch. Otherwise Andy is right, you can not mix parallel ParaView and VTK python code. Seb On Wed, Aug 6, 2014 at 1:35 PM, Andy Bauer wrote: > It may not be possible to do what you want explicitly. ParaView can be > viewed in some ways a wrapper around VTK filters. You can try the > programmable filter which uses the VTK Python API but is still intended to > operate like a filter (i.e. not modifying the input data sets, etc.). > > Andy > > > On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) < > simon.m.su.ctr at mail.mil> wrote: > >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> I would like to run some of my VTK python code under ParaView (pvbatch or >> pvpython). Where can I find documentation on porting VTK python code to >> use >> ParaView python api? I need to create some VTK object in ParaView. Is >> there >> a shortcut to this (like being able to use VTK python api within ParaView >> Python environment)? Or am I not making sense / asking the wrong >> question. >> >> Any help is much appreciated. >> >> Thanks >> -simon >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Wed Aug 6 15:46:52 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 6 Aug 2014 19:46:52 +0000 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Andy, I think the filter option may not be viable as the VTK code is the part that creates the VTK data structure (points - vtk.vtkPoints(), triangles - vtk.vtkCellArray, polydata - vtk.vtkPolydata()) using VTK python api. This is actually related to the catalyst question I asked. Luckily the user's code is in python already and Sean Ziegeler mentioned to bypass catalyst and just call ParaView using PV Python api (and run the simulation code python script using pvbath/pvpython). But the user's code is in VTK python and not ParaView python which caused some issue here. In that regards, are there documentation that I can look up on the comparable Python API between VTK and ParaView? Thanks -simon -----Original Message----- From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Wednesday, August 06, 2014 3:35 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) It may not be possible to do what you want explicitly. ParaView can be viewed in some ways a wrapper around VTK filters. You can try the programmable filter which uses the VTK Python API but is still intended to operate like a filter (i.e. not modifying the input data sets, etc.). Andy On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hello, I would like to run some of my VTK python code under ParaView (pvbatch or pvpython). Where can I find documentation on porting VTK python code to use ParaView python api? I need to create some VTK object in ParaView. Is there a shortcut to this (like being able to use VTK python api within ParaView Python environment)? Or am I not making sense / asking the wrong question. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Aug 6 15:51:11 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 6 Aug 2014 15:51:11 -0400 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Adding to what Andy and Seb said, "ParaView can be viewed in some ways a wrapper around VTK filters" + that often exist on remote MPI parallel processes + "." In Paraview client side scripts (tools->Python Shell or pvpython or pvbatch) you create python objects that create proxies that create remote vtk objects somewhere. Which is why it is not typically safe to mix vtk and paraview python code and do things like modifying the input data sets. See python trace and the paraview python wiki page to learn about this level of scripting. Within the python programmable filter and source, you are running inside those remote processes. Here the API is pretty much standard python wrapped VTK. See the wiki page about python programmable filters for starters and standard vtk documentation to learn details about this secondary level of scripting. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 6, 2014 at 3:45 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hi Simon, > > if the VTK work that you are targeting is not parallel, you can directly > run a vtkpython script inside pvpython or pvbatch. > Otherwise Andy is right, you can not mix parallel ParaView and VTK python > code. > > Seb > > > On Wed, Aug 6, 2014 at 1:35 PM, Andy Bauer wrote: > >> It may not be possible to do what you want explicitly. ParaView can be >> viewed in some ways a wrapper around VTK filters. You can try the >> programmable filter which uses the VTK Python API but is still intended to >> operate like a filter (i.e. not modifying the input data sets, etc.). >> >> Andy >> >> >> On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) < >> simon.m.su.ctr at mail.mil> wrote: >> >>> Classification: UNCLASSIFIED >>> Caveats: NONE >>> >>> Hello, >>> >>> I would like to run some of my VTK python code under ParaView (pvbatch or >>> pvpython). Where can I find documentation on porting VTK python code to >>> use >>> ParaView python api? I need to create some VTK object in ParaView. Is >>> there >>> a shortcut to this (like being able to use VTK python api within ParaView >>> Python environment)? Or am I not making sense / asking the wrong >>> question. >>> >>> Any help is much appreciated. >>> >>> Thanks >>> -simon >>> >>> Classification: UNCLASSIFIED >>> Caveats: NONE >>> >>> >>> >>> _______________________________________________ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Aug 6 15:53:32 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 6 Aug 2014 15:53:32 -0400 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Hi Simon, There is more information at http://www.paraview.org/Wiki/Python_Programmable_Filter. The ParaView Python API is meant for the client side of ParaView while the VTK Python API is meant for the server side. You can mix and match a bit by using Fetch() (see http://www.paraview.org/Wiki/ParaView/Python_Scripting for more details) where you start on the client with the ParaView Python API and then "fetch" the output from a filter to the client to be able to do VTK Python API stuff on VTK objects. For big jobs in parallel though this fetch operation can overwhelm the client with memory use. Regards, Andy On Wed, Aug 6, 2014 at 3:46 PM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hi Andy, > > I think the filter option may not be viable as the VTK code is the part > that > creates the VTK data structure (points - vtk.vtkPoints(), triangles - > vtk.vtkCellArray, polydata - vtk.vtkPolydata()) using VTK python api. > > This is actually related to the catalyst question I asked. Luckily the > user's > code is in python already and Sean Ziegeler mentioned to bypass catalyst > and > just call ParaView using PV Python api (and run the simulation code python > script using pvbath/pvpython). But the user's code is in VTK python and not > ParaView python which caused some issue here. > > In that regards, are there documentation that I can look up on the > comparable > Python API between VTK and ParaView? > > Thanks > -simon > > -----Original Message----- > From: Andy Bauer [mailto:andy.bauer at kitware.com] > Sent: Wednesday, August 06, 2014 3:35 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) > > It may not be possible to do what you want explicitly. ParaView can be > viewed > in some ways a wrapper around VTK filters. You can try the programmable > filter > which uses the VTK Python API but is still intended to operate like a > filter > (i.e. not modifying the input data sets, etc.). > > > Andy > > > > On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) > wrote: > > > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I would like to run some of my VTK python code under ParaView > (pvbatch or > pvpython). Where can I find documentation on porting VTK python > code to use > ParaView python api? I need to create some VTK object in ParaView. > Is there > a shortcut to this (like being able to use VTK python api within > ParaView > Python environment)? Or am I not making sense / asking the wrong > question. > > Any help is much appreciated. > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Wed Aug 6 15:59:44 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 6 Aug 2014 19:59:44 +0000 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Seb, Thanks. Good point. I have assumed I am dealing with parallel code. Let me check up on that. Basically the whole purpose of this exercise is to have the simulation code generate the data and visualize the data in real time (ParaView + catalyst). If the code is not parallel, maybe we can just skip ParaView completely and just use VTK to pop up the window and do the rendering when the data is generated? Or if the code is not parallel, we should change all the VTK python code into ParaView python code? And run it with pvpython. Which option would be the right way to do thing? Or if the code is parallel, then the only option is to change the VTK code into ParaView code? Thanks -simon -----Original Message----- From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: Wednesday, August 06, 2014 3:45 PM To: Andy Bauer Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) Hi Simon, if the VTK work that you are targeting is not parallel, you can directly run a vtkpython script inside pvpython or pvbatch. Otherwise Andy is right, you can not mix parallel ParaView and VTK python code. Seb On Wed, Aug 6, 2014 at 1:35 PM, Andy Bauer wrote: It may not be possible to do what you want explicitly. ParaView can be viewed in some ways a wrapper around VTK filters. You can try the programmable filter which uses the VTK Python API but is still intended to operate like a filter (i.e. not modifying the input data sets, etc.). Andy On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hello, I would like to run some of my VTK python code under ParaView (pvbatch or pvpython). Where can I find documentation on porting VTK python code to use ParaView python api? I need to create some VTK object in ParaView. Is there a shortcut to this (like being able to use VTK python api within ParaView Python environment)? Or am I not making sense / asking the wrong question. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Wed Aug 6 16:02:07 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 6 Aug 2014 20:02:07 +0000 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Dave, Thank you for the explanation. I have a better understand now on ParaView python and VTK python. Thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: Wednesday, August 06, 2014 3:51 PM To: Sebastien Jourdain Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) Adding to what Andy and Seb said, "ParaView can be viewed in some ways a wrapper around VTK filters" + that often exist on remote MPI parallel processes + "." In Paraview client side scripts (tools->Python Shell or pvpython or pvbatch) you create python objects that create proxies that create remote vtk objects somewhere. Which is why it is not typically safe to mix vtk and paraview python code and do things like modifying the input data sets. See python trace and the paraview python wiki page to learn about this level of scripting. Within the python programmable filter and source, you are running inside those remote processes. Here the API is pretty much standard python wrapped VTK. See the wiki page about python programmable filters for starters and standard vtk documentation to learn details about this secondary level of scripting. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 6, 2014 at 3:45 PM, Sebastien Jourdain wrote: Hi Simon, if the VTK work that you are targeting is not parallel, you can directly run a vtkpython script inside pvpython or pvbatch. Otherwise Andy is right, you can not mix parallel ParaView and VTK python code. Seb On Wed, Aug 6, 2014 at 1:35 PM, Andy Bauer wrote: It may not be possible to do what you want explicitly. ParaView can be viewed in some ways a wrapper around VTK filters. You can try the programmable filter which uses the VTK Python API but is still intended to operate like a filter (i.e. not modifying the input data sets, etc.). Andy On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hello, I would like to run some of my VTK python code under ParaView (pvbatch or pvpython). Where can I find documentation on porting VTK python code to use ParaView python api? I need to create some VTK object in ParaView. Is there a shortcut to this (like being able to use VTK python api within ParaView Python environment)? Or am I not making sense / asking the wrong question. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://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 Follow this link to subscribe/unsubscribe: http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Wed Aug 6 16:03:14 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 6 Aug 2014 20:03:14 +0000 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Andy, Thanks... I will dig into it... Thanks -simon -----Original Message----- From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Wednesday, August 06, 2014 3:54 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) Hi Simon, There is more information at http://www.paraview.org/Wiki/Python_Programmable_Filter. The ParaView Python API is meant for the client side of ParaView while the VTK Python API is meant for the server side. You can mix and match a bit by using Fetch() (see http://www.paraview.org/Wiki/ParaView/Python_Scripting for more details) where you start on the client with the ParaView Python API and then "fetch" the output from a filter to the client to be able to do VTK Python API stuff on VTK objects. For big jobs in parallel though this fetch operation can overwhelm the client with memory use. Regards, Andy On Wed, Aug 6, 2014 at 3:46 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hi Andy, I think the filter option may not be viable as the VTK code is the part that creates the VTK data structure (points - vtk.vtkPoints(), triangles - vtk.vtkCellArray, polydata - vtk.vtkPolydata()) using VTK python api. This is actually related to the catalyst question I asked. Luckily the user's code is in python already and Sean Ziegeler mentioned to bypass catalyst and just call ParaView using PV Python api (and run the simulation code python script using pvbath/pvpython). But the user's code is in VTK python and not ParaView python which caused some issue here. In that regards, are there documentation that I can look up on the comparable Python API between VTK and ParaView? Thanks -simon -----Original Message----- From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Wednesday, August 06, 2014 3:35 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) It may not be possible to do what you want explicitly. ParaView can be viewed in some ways a wrapper around VTK filters. You can try the programmable filter which uses the VTK Python API but is still intended to operate like a filter (i.e. not modifying the input data sets, etc.). Andy On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hello, I would like to run some of my VTK python code under ParaView (pvbatch or pvpython). Where can I find documentation on porting VTK python code to use ParaView python api? I need to create some VTK object in ParaView. Is there a shortcut to this (like being able to use VTK python api within ParaView Python environment)? Or am I not making sense / asking the wrong question. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From sebastien.jourdain at kitware.com Wed Aug 6 16:10:15 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 6 Aug 2014 14:10:15 -0600 Subject: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) In-Reply-To: References: Message-ID: Hi Simon, Catalyst is a bit different as well. And Andy could provide more info on that. So the answer will greatly depend on which section of the code you are trying to work on. - adapter that fill the trivial producer for catalyst - processing pipeline inside catalyst - ParaView post-processing for live in-situ visualization Seb On Wed, Aug 6, 2014 at 2:03 PM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hi Andy, > > Thanks... I will dig into it... > > Thanks > -simon > > -----Original Message----- > From: Andy Bauer [mailto:andy.bauer at kitware.com] > Sent: Wednesday, August 06, 2014 3:54 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView python vs VTK python api (UNCLASSIFIED) > > Hi Simon, > > > There is more information at > http://www.paraview.org/Wiki/Python_Programmable_Filter. The ParaView > Python > API is meant for the client side of ParaView while the VTK Python API is > meant > for the server side. You can mix and match a bit by using Fetch() (see > http://www.paraview.org/Wiki/ParaView/Python_Scripting for more details) > where > you start on the client with the ParaView Python API and then "fetch" the > output from a filter to the client to be able to do VTK Python API stuff on > VTK objects. For big jobs in parallel though this fetch operation can > overwhelm the client with memory use. > > > Regards, > Andy > > > > On Wed, Aug 6, 2014 at 3:46 PM, Su, Simon M CTR USARMY ARL (US) > wrote: > > > Classification: UNCLASSIFIED > Caveats: NONE > > Hi Andy, > > I think the filter option may not be viable as the VTK code is the > part that > creates the VTK data structure (points - vtk.vtkPoints(), > triangles - > vtk.vtkCellArray, polydata - vtk.vtkPolydata()) using VTK python > api. > > This is actually related to the catalyst question I asked. Luckily > the user's > code is in python already and Sean Ziegeler mentioned to bypass > catalyst and > just call ParaView using PV Python api (and run the simulation > code python > script using pvbath/pvpython). But the user's code is in VTK > python and not > ParaView python which caused some issue here. > > In that regards, are there documentation that I can look up on the > comparable > Python API between VTK and ParaView? > > Thanks > -simon > > > -----Original Message----- > From: Andy Bauer [mailto:andy.bauer at kitware.com] > Sent: Wednesday, August 06, 2014 3:35 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView python vs VTK python api > (UNCLASSIFIED) > > It may not be possible to do what you want explicitly. ParaView > can be viewed > in some ways a wrapper around VTK filters. You can try the > programmable > filter > which uses the VTK Python API but is still intended to operate > like a filter > (i.e. not modifying the input data sets, etc.). > > > Andy > > > > On Wed, Aug 6, 2014 at 3:28 PM, Su, Simon M CTR USARMY ARL (US) > wrote: > > > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I would like to run some of my VTK python code under > ParaView > (pvbatch or > pvpython). Where can I find documentation on porting VTK > python code > to use > ParaView python api? I need to create some VTK object in > ParaView. Is > there > a shortcut to this (like being able to use VTK python api > within > ParaView > Python environment)? Or am I not making sense / asking > the wrong > question. > > Any help is much appreciated. > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Aug 6 17:38:53 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 6 Aug 2014 17:38:53 -0400 Subject: [Paraview] announce: 2014 HPCWire Reader's Choice Award nominations open Message-ID: HPCWire is holding their Annual Reader?s Choice Awards. Please take the time to nominate VTK and ParaView for this year?s awards. All you need to do is to submit the projects, products or solutions you feel should be honored by receiving an award to the appropriate (max of 3) categories before the deadline at: http://www.hpcwire.com/2014-hpcwire-readers-choice-awards/ Anyone may can nominate their project, collaboration, product or solution, and you do not need to fill the entire form out. Only the categories(s) for which you feel your organization is qualified to receive an award. You may submit as many nominations as you like. Those who make it past the nominations will move on to the September elections for selecting this year's finalists by our readers. Recent and near term user visible developments in the lands of VTK and ParaView include: *VTK* * vtkDax, vtkPiston and vtkSMP: bringing GPGPU and multicore speed to VTK. * vtkWeb - VTK based web services simply by enabling VTK_WRAP_PYTHON * vtk.numpy_interface - numpy processing moves beyond arrays into datasets * OpenGL2.1+ rendering - promising both render speed and extensibility improvements *ParaView* * vector graphics screen exports * parallel and composite SurfaceLIC representations of vector fields * streamlined properties and view options panels * the Python View allows just about any Python library to generate images in ParaView views. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.fastl at kcl.ac.uk Wed Aug 6 18:56:23 2014 From: thomas.fastl at kcl.ac.uk (Fastl, Thomas) Date: Wed, 6 Aug 2014 22:56:23 +0000 Subject: [Paraview] Tetrahedral Mesh Quality Message-ID: <1407365783652.88530@kcl.ac.uk> Hello Community, I need to evaluate the quality of my tetrahedral mesh for simulations in structural mechanics and want to apply the filter 'Mesh Quality' using the 'Scaled Jacobian' metric. Paraview (4.0.1) calculates the values providing me with a range of [0.1,1.0] and the 'Histrogram' looks like a Gauss distribution with a mean around 0.6. I wanted to find out more about how this metric is calculated for tetrahedral elements and looked up the 'Verdict Library Reference Manual', which states the following: acceptable range: [0.500 , 0.707] normal range: [-0.707 , 0.707] full range: [-dbl_max , dbl_max] It also states that the 'Scaled Jacobian' for a unit equilateral tetrahedron, in my humble opinion a perfect tetrahedron, is 1. As far as I understand these ranges the full range provides values if some error/problem occurs, the normal range should be the range of mathematically possible values and the acceptable range is where somebody wants his elements to be in. The 'Scaled Jacobian' of a unit equilateral tetrahedron, however, doesn't fall in the acceptable range or even worse, in the normal range. Do I misunderstand the provided ranges? I also tested a equilateral tetrahedron in Paraview and by hand with the 'Scaled Jacobian' metric and I always obtained 1. Thank you for your help! Best, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Wed Aug 6 21:05:11 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 07 Aug 2014 03:05:11 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53E1F6AC.1090709@hzdr.de> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> <53E13290.9000503@xs4all.nl> <53E1F6AC.1090709@hzdr.de> Message-ID: <53E2D0C7.1080507@xs4all.nl> Hi Axel, setting CMAKE_PREFIX_PATH does not make a difference. The special variables left that have a reference to the wrong qt installation are QT_QT3SUPPORT_LIBRARY and QT3SUPPORT_LIBRARY_RELEASE variables. Qt5 does no longer provide Qt4 support . Also QT_QTCORE_LIBRARY and QT_QDBUS and QT_GUI_LIBRARY_ are wrong .... The correspinding HEADER-varinant are ok, though. What does this tell me? Regards, Bertwim On 08/06/2014 11:34 AM, Huebl, Axel wrote: > Dear Bertwim, > > > good to hear that. > > sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and > "LD_LIBRARY_PATH" to hint install directories to CMake modules. > > The compile error still looks like something got mixed - can you try > again with the CMAKE_PREFIX_PATH hint? > Did you verify all "advanced" variables set from the FindQt module with > ccmake? > > > Best, > Axel > > On 05.08.2014 21:37, B.W.H. van Beest wrote: >> Dear Axel, >> >> No I haven't. To follow-up on your suggestion, I ran ccmake again to set >> this parameter. No CMAKE_PREFIX_PATH is in the list! >> What I did try -and what did make a difference, was not only prepending >> the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin >> was first in $PATH. This indeed has the result that all libQt5 >> directories found were the correct ones. Maybe that amounts to the same? >> >> However, Now I have a different compile error: >> >> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >> function `pqNativeFileDialogEventPlayer::start()': >> pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to >> `qt_filedialog_existing_directory_hook' >> pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to >> `qt_filedialog_open_filename_hook' >> pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to >> `qt_filedialog_open_filenames_hook' >> pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to >> `qt_filedialog_save_filename_hook' >> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >> function `pqNativeFileDialogEventPlayer::stop()': >> >> >> etc. >> >> Any ideas? >> >> >> >> >> >> >> On 08/05/2014 08:38 PM, Huebl, Axel wrote: >>> Dear Bertwim, >>> >>> have you tried prepending/setting the >>> CMAKE_PREFIX_PATH >>> >>> to your qt5 install dir? >>> >>> Best, >>> Axel >>> On 05.08.2014 18:07, B.W.H. van Beest wrote: >>>> Hi Burien, thanks for responding. >>>> >>>> I have done you suggested, but to no avail. >>>> Somehow, the path to the executable qmake is not sufficient to determine >>>> all the other QT5 libraries. >>>> Having said that, in one of the by now many attempts to get paraview >>>> configured, I found that indeed the correct QT5 libraries were selected. >>>> That build, however failed (missing symbol, cannot remember which one). >>>> In trying to correct this is, the wrong QT5 libraries were selected by >>>> ccmake. I just cannot figure out how this cmake thing works, or what I >>>> can do to force it. >>>> Any suggestions? >>>> >>>> Kind Regards, >>>> Bertwim >>>> >>>> >>>> >>>> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>>>> system install may be first in the linker search path. have you >>>>> checked? If that's it: rm your build, and in addition to >>>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>>>> PV do the same. >>>>> >>>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>>>> Hello, >>>>>> >>>>>> On my system, I have 2 installations of QT5. One is the distribution >>>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>>>> one is a more recent version (5.3.1), which I downloaded and installed >>>>>> in a different location. >>>>>> Using ccmake, setting the QT version to 5, as well as setting >>>>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>>>> I still see that ccmake selects of number of qt5-libraries that belong >>>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>>>> in fact). I can build paraview, though, and it even seems to work >>>>>> (smoketest), but at program exit it segfaults. >>>>>> >>>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>>>> don't need to change all the entries by hand? >>>>>> >>>>>> Thanks in advance >>>>>> Bertwim >> >> From rpd.toastmasters at gmail.com Thu Aug 7 00:50:13 2014 From: rpd.toastmasters at gmail.com (Rakesh Dhote) Date: Thu, 7 Aug 2014 00:50:13 -0400 Subject: [Paraview] Plot point variable over time Message-ID: Hi, I have a quick question. How to plot a point variable over time? It seems the procedure mentioned in the following mailing list refer to the previous version of the Paraview. http://www.paraview.org/pipermail/paraview/2012-November/026633.html Thank you for your help in advance. Warm regards, Rakesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.huebl at hzdr.de Thu Aug 7 06:00:48 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Thu, 07 Aug 2014 12:00:48 +0200 Subject: [Paraview] what if you have two qt-installations? In-Reply-To: <53E2D0C7.1080507@xs4all.nl> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> <53E13290.9000503@xs4all.nl> <53E1F6AC.1090709@hzdr.de> <53E2D0C7.1080507@xs4all.nl> Message-ID: <53E34E50.9060705@hzdr.de> Hm, looks like the cleanest way to get it running is to remove default installations of qt from the system path(s) and to specificity only one specific installation via environment flags. (I am suggesting something that can be achieved with a module system, e.g. on a cluster) Alternatively you can try to scratch all the advanced flags together that are still wrong and set them by hand. > What does this tell me? Yep, but basically it is still an environment problem. Best, Axel On 07.08.2014 03:05, B.W.H. van Beest wrote: > Hi Axel, > > setting CMAKE_PREFIX_PATH does not make a difference. The special > variables left that have a reference to the wrong qt installation are > QT_QT3SUPPORT_LIBRARY and QT3SUPPORT_LIBRARY_RELEASE variables. Qt5 > does no longer provide Qt4 support . > > Also QT_QTCORE_LIBRARY and QT_QDBUS and QT_GUI_LIBRARY_ are wrong .... > The correspinding HEADER-varinant are ok, though. > What does this tell me? > > Regards, > Bertwim > > > On 08/06/2014 11:34 AM, Huebl, Axel wrote: >> Dear Bertwim, >> >> >> good to hear that. >> >> sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and >> "LD_LIBRARY_PATH" to hint install directories to CMake modules. >> >> The compile error still looks like something got mixed - can you try >> again with the CMAKE_PREFIX_PATH hint? >> Did you verify all "advanced" variables set from the FindQt module with >> ccmake? >> >> >> Best, >> Axel >> >> On 05.08.2014 21:37, B.W.H. van Beest wrote: >>> Dear Axel, >>> >>> No I haven't. To follow-up on your suggestion, I ran ccmake again to set >>> this parameter. No CMAKE_PREFIX_PATH is in the list! >>> What I did try -and what did make a difference, was not only prepending >>> the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin >>> was first in $PATH. This indeed has the result that all libQt5 >>> directories found were the correct ones. Maybe that amounts to the same? >>> >>> However, Now I have a different compile error: >>> >>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>> function `pqNativeFileDialogEventPlayer::start()': >>> pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to >>> `qt_filedialog_existing_directory_hook' >>> pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to >>> `qt_filedialog_open_filename_hook' >>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to >>> `qt_filedialog_open_filenames_hook' >>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to >>> `qt_filedialog_save_filename_hook' >>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>> function `pqNativeFileDialogEventPlayer::stop()': >>> >>> >>> etc. >>> >>> Any ideas? >>> >>> >>> >>> >>> >>> >>> On 08/05/2014 08:38 PM, Huebl, Axel wrote: >>>> Dear Bertwim, >>>> >>>> have you tried prepending/setting the >>>> CMAKE_PREFIX_PATH >>>> >>>> to your qt5 install dir? >>>> >>>> Best, >>>> Axel >>>> On 05.08.2014 18:07, B.W.H. van Beest wrote: >>>>> Hi Burien, thanks for responding. >>>>> >>>>> I have done you suggested, but to no avail. >>>>> Somehow, the path to the executable qmake is not sufficient to determine >>>>> all the other QT5 libraries. >>>>> Having said that, in one of the by now many attempts to get paraview >>>>> configured, I found that indeed the correct QT5 libraries were selected. >>>>> That build, however failed (missing symbol, cannot remember which one). >>>>> In trying to correct this is, the wrong QT5 libraries were selected by >>>>> ccmake. I just cannot figure out how this cmake thing works, or what I >>>>> can do to force it. >>>>> Any suggestions? >>>>> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> >>>>> >>>>> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>>>>> system install may be first in the linker search path. have you >>>>>> checked? If that's it: rm your build, and in addition to >>>>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>>>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>>>>> PV do the same. >>>>>> >>>>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>>>>> Hello, >>>>>>> >>>>>>> On my system, I have 2 installations of QT5. One is the distribution >>>>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>>>>> one is a more recent version (5.3.1), which I downloaded and installed >>>>>>> in a different location. >>>>>>> Using ccmake, setting the QT version to 5, as well as setting >>>>>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>>>>> I still see that ccmake selects of number of qt5-libraries that belong >>>>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>>>>> in fact). I can build paraview, though, and it even seems to work >>>>>>> (smoketest), but at program exit it segfaults. >>>>>>> >>>>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>>>>> don't need to change all the entries by hand? >>>>>>> >>>>>>> Thanks in advance >>>>>>> Bertwim >>> >>> > > > -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5002 bytes Desc: S/MIME Cryptographic Signature URL: From kmorel at sandia.gov Thu Aug 7 09:55:22 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 7 Aug 2014 13:55:22 +0000 Subject: [Paraview] Nightly Downloads for ParaView Lion-Python27 broken Message-ID: The downloads for the nightly Mac OS build of ParaView-Darwin-64bit-Lion-Python27-NIGHTLY.dmg appear to be broken on the paraview.org web page. When I download the file using the "Releases" form, I get what appears to be a 4.1 build instead of the nightly. If I download the file using the "Nightly Builds" form, I get a corrupt or incomplete file. Both methods of downloading the other nightly Mac OS build seem to work fine. -Ken **** Kenneth Moreland *** Sandia National Laboratories *********** *** *** *** email: kmorel at sandia.gov ** *** ** phone: (505) 844-8919 *** web: http://www.sandia.gov/~kmorel -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.maynard at kitware.com Fri Aug 8 10:30:11 2014 From: robert.maynard at kitware.com (Robert Maynard) Date: Fri, 8 Aug 2014 10:30:11 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53E226A9.8070002@bluecape.com.pt> References: <53E226A9.8070002@bluecape.com.pt> Message-ID: This is really cool! We should try to integrate the open mpi changes as those seem really reasonable. As far as building Qt, this is required for two reasons. The first is that the Qt 4.8 series only has 32bit official binaries for windows, and we would need 32 and 64bit. If we moved to Qt 5.X it would be possible to use the official binaries, as long as moved to VS 2010/2012. Now the reason that we currently build with VS 2008 is because of hard requirements in the python build system. I know that people are investigating a new build system for python that supports VS 2010 / VS2012. So if ParaView is ever able to use the new python build system, and officially moves over to Qt 5.X we should transition to use the official Qt binaries for windows. On Wed, Aug 6, 2014 at 8:59 AM, Bruno Santos wrote: > Greetings to all! > > We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for > Windows 32 and 64-bit, based on the official SuperBuild and respective build > options. It's available here: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 > Instructions on how these packages were built is provided here: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 > > According to our tests, it's possible to use this SDK to build plug-ins and > any other associated applications, which will work with the respective > official ParaView 4.1.0 builds for Windows. A proof of concept we've used is > the vtkPOFFReader plug-in which was successfully built with these SDK > packages: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds > > Note: We roughly used the same development environment as the original > ParaView 4.1.0 binaries for Windows: > http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC > 2008 C++ Express and did not have a respective FORTRAN compiler (which > requires the Professional version either way), which is why we needed to do > some adjustments to build Open-MPI with success. > > Furthermore, here's a bit of a back story and the current status of this > endeavour: > > Back in January 2012 we at blueCAPE began to try to bring back the > development installers of ParaView for Windows, which was last officially > available for ParaView 3.8.1. > The overall features available in the development installers we created were > still missing important files, because we were still basing ourselves on the > infrastructure that was still remnant from ParaView 3.8.1. > Nonetheless, we made available our findings and builds for ParaView 3.12.0, > 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was > back in January 2013. > ParaView fortunately kept evolving since then. We missed the versions 3.98.1 > and 4.0.1, due to time constraints on our side and a few failed builds. > As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure > which evolved overtime. The official SuperBuild repository also already > provides many of the necessary features for making the SDK releases, at > least for the Unix-like environments. > This Summer 2014 we at blueCAPE finally managed to get around back to trying > and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK > for Windows and believe we have successfully achieved it. The changes have > been shared and referenced in the following wiki page at our project: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 > In addition to this, after some reviewing and building tests with the latest > commits on the master branch from the SuperBuild repository, we have adapted > most of the changes we've developed for the SDK build above and have > submitted two commits to Kitware Gerrit, namely: > > http://review.source.kitware.com/#/t/4487/ > http://review.source.kitware.com/#/t/4488/ > > We haven't managed to create the NSIS and ZIP packages through CMake/CPack, > but our main concern has mostly been on having a working SDK. > > Hopefully this can help bring sooner the ParaView SDK in future versions in > a more official way... so that we won't have to look into generating the > NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) > > If anyone has any questions, feel free to ask! > > Best regards, > Bruno Santos > > PS: I haven't sent this email to the ParaView Developers mailing list simply > because previous emails I've sent on this topic have been to this main > mailing list. > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Fri Aug 8 11:25:10 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 8 Aug 2014 15:25:10 +0000 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: <53E226A9.8070002@bluecape.com.pt> References: <53E226A9.8070002@bluecape.com.pt> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Bruno, Can I ask why you picked MSVC 2008 C++ Express version over MSVC 2013 C++ Express version to do the compilation? Thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Bruno Santos Sent: Wednesday, August 06, 2014 8:59 AM To: paraview at paraview.org Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit Greetings to all! We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for Windows 32 and 64-bit, based on the official SuperBuild and respective build options. It's available here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#Par aView_4.1.0 Instructions on how these packages were built is provided here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 According to our tests, it's possible to use this SDK to build plug-ins and any other associated applications, which will work with the respective official ParaView 4.1.0 builds for Windows. A proof of concept we've used is the vtkPOFFReader plug-in which was successfully built with these SDK packages: https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReader Builds Note: We roughly used the same development environment as the original ParaView 4.1.0 binaries for Windows: http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC 2008 C++ Express and did not have a respective FORTRAN compiler (which requires the Professional version either way), which is why we needed to do some adjustments to build Open-MPI with success. Furthermore, here's a bit of a back story and the current status of this endeavour: * Back in January 2012 we at blueCAPE began to try to bring back the development installers of ParaView for Windows, which was last officially available for ParaView 3.8.1. * The overall features available in the development installers we created were still missing important files, because we were still basing ourselves on the infrastructure that was still remnant from ParaView 3.8.1. * Nonetheless, we made available our findings and builds for ParaView 3.12.0, 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was back in January 2013. * ParaView fortunately kept evolving since then. We missed the versions 3.98.1 and 4.0.1, due to time constraints on our side and a few failed builds. * As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure which evolved overtime. The official SuperBuild repository also already provides many of the necessary features for making the SDK releases, at least for the Unix-like environments. * This Summer 2014 we at blueCAPE finally managed to get around back to trying and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK for Windows and believe we have successfully achieved it. The changes have been shared and referenced in the following wiki page at our project: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 * In addition to this, after some reviewing and building tests with the latest commits on the master branch from the SuperBuild repository, we have adapted most of the changes we've developed for the SDK build above and have submitted two commits to Kitware Gerrit, namely: * http://review.source.kitware.com/#/t/4487/ * http://review.source.kitware.com/#/t/4488/ * We haven't managed to create the NSIS and ZIP packages through CMake/CPack, but our main concern has mostly been on having a working SDK. Hopefully this can help bring sooner the ParaView SDK in future versions in a more official way... so that we won't have to look into generating the NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) If anyone has any questions, feel free to ask! Best regards, Bruno Santos PS: I haven't sent this email to the ParaView Developers mailing list simply because previous emails I've sent on this topic have been to this main mailing list. Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From denis.cohen at gmail.com Fri Aug 8 11:30:58 2014 From: denis.cohen at gmail.com (denis cohen) Date: Fri, 8 Aug 2014 17:30:58 +0200 Subject: [Paraview] Writing csv data in python script Message-ID: Hi Casey, I've tried this like in your suggestion: SetActiveSource(IntegrateVariables1) DataSetCSVWriter() FileName="foo_points.csv" FieldAssociation = "Points" UpdatePipeline() and other similar commands but none produced a csv file. Any hints? Thanks Denis On Tue, Aug 5, 2014 at 7:38 PM, Casey Goodlett wrote: > Denis, > > You could look here > > on lines 468-476 for how this is done in VeloView. You can ignore the > rotateCSVFile function call. > > > > > On Sat, Aug 2, 2014 at 5:34 AM, denis cohen wrote: > >> Hi, >> New to python scripting. How can one output a csv file inside a python >> script/macro? >> I am trying the wiki: >> >>> writer = CreateWriter(".../foo.csv", source) >> >>> writer.FieldAssociation = "Points" # or "Cells" >> >>> writer.UpdatePipeline() >> >>> del writer >> >> But I get: >> Traceback (most recent call last): >> File "", line 173, in >> AttributeError: 'str' object has no attribute 'UpdatePipeline' >> >> Thanks for any help. >> >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Casey B. Goodlett, Ph.D. > Technical Leader > Kitware, Inc. - North Carolina Office > http://www.kitware.com > (919) 969-6990 x310 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Fri Aug 8 11:40:28 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Fri, 8 Aug 2014 11:40:28 -0400 Subject: [Paraview] Writing csv data in python script In-Reply-To: References: Message-ID: Do you get any error messages in the python console or output window? What type of data does your source produce polydata, unstructured grid, etc? On Fri, Aug 8, 2014 at 11:30 AM, denis cohen wrote: > Hi Casey, > > I've tried this like in your suggestion: > > SetActiveSource(IntegrateVariables1) > DataSetCSVWriter() > FileName="foo_points.csv" > FieldAssociation = "Points" > UpdatePipeline() > > and other similar commands but none produced a csv file. Any hints? > > Thanks > > Denis > > > > > On Tue, Aug 5, 2014 at 7:38 PM, Casey Goodlett > wrote: > >> Denis, >> >> You could look here >> >> on lines 468-476 for how this is done in VeloView. You can ignore the >> rotateCSVFile function call. >> >> >> >> >> On Sat, Aug 2, 2014 at 5:34 AM, denis cohen >> wrote: >> >>> Hi, >>> New to python scripting. How can one output a csv file inside a python >>> script/macro? >>> I am trying the wiki: >>> >>> writer = CreateWriter(".../foo.csv", source) >>> >>> writer.FieldAssociation = "Points" # or "Cells" >>> >>> writer.UpdatePipeline() >>> >>> del writer >>> >>> But I get: >>> Traceback (most recent call last): >>> File "", line 173, in >>> AttributeError: 'str' object has no attribute 'UpdatePipeline' >>> >>> Thanks for any help. >>> >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> -- >> Casey B. Goodlett, Ph.D. >> Technical Leader >> Kitware, Inc. - North Carolina Office >> http://www.kitware.com >> (919) 969-6990 x310 >> > > -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Fri Aug 8 11:43:39 2014 From: denis.cohen at gmail.com (denis cohen) Date: Fri, 8 Aug 2014 17:43:39 +0200 Subject: [Paraview] Writing csv data in python script Message-ID: Hi Casey, I get no error and I read my data with XMLPartitionedUnstructuredGridReader. Denis On Fri, Aug 8, 2014 at 5:40 PM, Casey Goodlett wrote: > Do you get any error messages in the python console or output window? > > What type of data does your source produce polydata, unstructured grid, > etc? > > > On Fri, Aug 8, 2014 at 11:30 AM, denis cohen > wrote: > >> Hi Casey, >> >> I've tried this like in your suggestion: >> >> SetActiveSource(IntegrateVariables1) >> DataSetCSVWriter() >> FileName="foo_points.csv" >> FieldAssociation = "Points" >> UpdatePipeline() >> >> and other similar commands but none produced a csv file. Any hints? >> >> Thanks >> >> Denis >> >> >> >> >> On Tue, Aug 5, 2014 at 7:38 PM, Casey Goodlett < >> casey.goodlett at kitware.com> wrote: >> >>> Denis, >>> >>> You could look here >>> >>> on lines 468-476 for how this is done in VeloView. You can ignore the >>> rotateCSVFile function call. >>> >>> >>> >>> >>> On Sat, Aug 2, 2014 at 5:34 AM, denis cohen >>> wrote: >>> >>>> Hi, >>>> New to python scripting. How can one output a csv file inside a python >>>> script/macro? >>>> I am trying the wiki: >>>> >>> writer = CreateWriter(".../foo.csv", source) >>>> >>> writer.FieldAssociation = "Points" # or "Cells" >>>> >>> writer.UpdatePipeline() >>>> >>> del writer >>>> >>>> But I get: >>>> Traceback (most recent call last): >>>> File "", line 173, in >>>> AttributeError: 'str' object has no attribute 'UpdatePipeline' >>>> >>>> Thanks for any help. >>>> >>>> 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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >>> >>> -- >>> Casey B. Goodlett, Ph.D. >>> Technical Leader >>> Kitware, Inc. - North Carolina Office >>> http://www.kitware.com >>> (919) 969-6990 x310 >>> >> >> > > > -- > Casey B. Goodlett, Ph.D. > Technical Leader > Kitware, Inc. - North Carolina Office > http://www.kitware.com > (919) 969-6990 x310 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Fri Aug 8 11:46:23 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Fri, 8 Aug 2014 11:46:23 -0400 Subject: [Paraview] Writing csv data in python script In-Reply-To: References: Message-ID: I tried this in the binary download of paraview 4.1 >>> s = Sphere() >>> w = DataSetCSVWriter(s, FileName='/tmp/test.csv', FieldAssociation='Points') >>> w.UpdatePipeline() >>> and successfully had a file written. You might try explicitly passing your reader as input to the DataSetCSVWriter rather than relying on the active source. I am not familiar with partitioned unstructured grid to know if any additional steps are needed. good luck On Fri, Aug 8, 2014 at 11:43 AM, denis cohen wrote: > Hi Casey, > > I get no error and I read my data with > XMLPartitionedUnstructuredGridReader. > > Denis > > > > > On Fri, Aug 8, 2014 at 5:40 PM, Casey Goodlett > wrote: > >> Do you get any error messages in the python console or output window? >> >> What type of data does your source produce polydata, unstructured grid, >> etc? >> >> >> On Fri, Aug 8, 2014 at 11:30 AM, denis cohen >> wrote: >> >>> Hi Casey, >>> >>> I've tried this like in your suggestion: >>> >>> SetActiveSource(IntegrateVariables1) >>> DataSetCSVWriter() >>> FileName="foo_points.csv" >>> FieldAssociation = "Points" >>> UpdatePipeline() >>> >>> and other similar commands but none produced a csv file. Any hints? >>> >>> Thanks >>> >>> Denis >>> >>> >>> >>> >>> On Tue, Aug 5, 2014 at 7:38 PM, Casey Goodlett < >>> casey.goodlett at kitware.com> wrote: >>> >>>> Denis, >>>> >>>> You could look here >>>> >>>> on lines 468-476 for how this is done in VeloView. You can ignore the >>>> rotateCSVFile function call. >>>> >>>> >>>> >>>> >>>> On Sat, Aug 2, 2014 at 5:34 AM, denis cohen >>>> wrote: >>>> >>>>> Hi, >>>>> New to python scripting. How can one output a csv file inside a python >>>>> script/macro? >>>>> I am trying the wiki: >>>>> >>> writer = CreateWriter(".../foo.csv", source) >>>>> >>> writer.FieldAssociation = "Points" # or "Cells" >>>>> >>> writer.UpdatePipeline() >>>>> >>> del writer >>>>> >>>>> But I get: >>>>> Traceback (most recent call last): >>>>> File "", line 173, in >>>>> AttributeError: 'str' object has no attribute 'UpdatePipeline' >>>>> >>>>> Thanks for any help. >>>>> >>>>> 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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>>> >>>> -- >>>> Casey B. Goodlett, Ph.D. >>>> Technical Leader >>>> Kitware, Inc. - North Carolina Office >>>> http://www.kitware.com >>>> (919) 969-6990 x310 >>>> >>> >>> >> >> >> -- >> Casey B. Goodlett, Ph.D. >> Technical Leader >> Kitware, Inc. - North Carolina Office >> http://www.kitware.com >> (919) 969-6990 x310 >> > > -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Fri Aug 8 12:01:36 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 8 Aug 2014 16:01:36 +0000 Subject: [Paraview] Writing csv data in python script (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Casey, On a somewhat related topic, >>> s = Sphere() >>> sum = 2 + 1 >>> w = DataSetCSVWriter(s, FileName='/tmp/test.csv', >>> FieldAssociation='Points') >>> w.UpdatePipeline() If I want to just write the value of variable sum to a csv file, how would that be done? Thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Casey Goodlett Sent: Friday, August 08, 2014 11:46 AM To: denis cohen Cc: paraview Subject: Re: [Paraview] Writing csv data in python script I tried this in the binary download of paraview 4.1 >>> s = Sphere() >>> w = DataSetCSVWriter(s, FileName='/tmp/test.csv', >>> FieldAssociation='Points') >>> w.UpdatePipeline() >>> and successfully had a file written. You might try explicitly passing your reader as input to the DataSetCSVWriter rather than relying on the active source. I am not familiar with partitioned unstructured grid to know if any additional steps are needed. good luck On Fri, Aug 8, 2014 at 11:43 AM, denis cohen wrote: Hi Casey, I get no error and I read my data with XMLPartitionedUnstructuredGridReader. Denis On Fri, Aug 8, 2014 at 5:40 PM, Casey Goodlett wrote: Do you get any error messages in the python console or output window? What type of data does your source produce polydata, unstructured grid, etc? On Fri, Aug 8, 2014 at 11:30 AM, denis cohen wrote: Hi Casey, I've tried this like in your suggestion: SetActiveSource(IntegrateVariables1) DataSetCSVWriter() FileName="foo_points.csv" FieldAssociation = "Points" UpdatePipeline() and other similar commands but none produced a csv file. Any hints? Thanks Denis On Tue, Aug 5, 2014 at 7:38 PM, Casey Goodlett wrote: Denis, You could look here on lines 468-476 for how this is done in VeloView. You can ignore the rotateCSVFile function call. On Sat, Aug 2, 2014 at 5:34 AM, denis cohen wrote: Hi, New to python scripting. How can one output a csv file inside a python script/macro? I am trying the wiki: >>> writer = CreateWriter(".../foo.csv", source) >>> writer.FieldAssociation = "Points" # or "Cells" >>> writer.UpdatePipeline() >>> del writer But I get: Traceback (most recent call last): File "", line 173, in AttributeError: 'str' object has no attribute 'UpdatePipeline' Thanks for any help. 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From bloring at lbl.gov Fri Aug 8 12:21:10 2014 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 08 Aug 2014 09:21:10 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> Message-ID: <53E4F8F6.2060703@lbl.gov> OpenMPI dropped support for windows some time ago. Would it not make sense to use MS MPI? https://www.open-mpi.org/software/ompi/v1.6/ms-windows.php http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx On 08/08/2014 07:30 AM, Robert Maynard wrote: > This is really cool! We should try to integrate the open mpi changes > as those seem really reasonable. > > > As far as building Qt, this is required for two reasons. The first is > that the Qt 4.8 series only has 32bit official binaries for windows, > and we would need 32 and 64bit. If we moved to Qt 5.X it would be > possible to use the official binaries, as long as moved to VS > 2010/2012. > > Now the reason that we currently build with VS 2008 is because of hard > requirements in the python build system. I know that people are > investigating a new build system for python that supports VS 2010 / > VS2012. So if ParaView is ever able to use the new python build > system, and officially moves over to Qt 5.X we should transition to > use the official Qt binaries for windows. > > On Wed, Aug 6, 2014 at 8:59 AM, Bruno Santos > wrote: >> Greetings to all! >> >> We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for >> Windows 32 and 64-bit, based on the official SuperBuild and respective build >> options. It's available here: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 >> Instructions on how these packages were built is provided here: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >> >> According to our tests, it's possible to use this SDK to build plug-ins and >> any other associated applications, which will work with the respective >> official ParaView 4.1.0 builds for Windows. A proof of concept we've used is >> the vtkPOFFReader plug-in which was successfully built with these SDK >> packages: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds >> >> Note: We roughly used the same development environment as the original >> ParaView 4.1.0 binaries for Windows: >> http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC >> 2008 C++ Express and did not have a respective FORTRAN compiler (which >> requires the Professional version either way), which is why we needed to do >> some adjustments to build Open-MPI with success. >> >> Furthermore, here's a bit of a back story and the current status of this >> endeavour: >> >> Back in January 2012 we at blueCAPE began to try to bring back the >> development installers of ParaView for Windows, which was last officially >> available for ParaView 3.8.1. >> The overall features available in the development installers we created were >> still missing important files, because we were still basing ourselves on the >> infrastructure that was still remnant from ParaView 3.8.1. >> Nonetheless, we made available our findings and builds for ParaView 3.12.0, >> 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was >> back in January 2013. >> ParaView fortunately kept evolving since then. We missed the versions 3.98.1 >> and 4.0.1, due to time constraints on our side and a few failed builds. >> As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure >> which evolved overtime. The official SuperBuild repository also already >> provides many of the necessary features for making the SDK releases, at >> least for the Unix-like environments. >> This Summer 2014 we at blueCAPE finally managed to get around back to trying >> and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK >> for Windows and believe we have successfully achieved it. The changes have >> been shared and referenced in the following wiki page at our project: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >> In addition to this, after some reviewing and building tests with the latest >> commits on the master branch from the SuperBuild repository, we have adapted >> most of the changes we've developed for the SDK build above and have >> submitted two commits to Kitware Gerrit, namely: >> >> http://review.source.kitware.com/#/t/4487/ >> http://review.source.kitware.com/#/t/4488/ >> >> We haven't managed to create the NSIS and ZIP packages through CMake/CPack, >> but our main concern has mostly been on having a working SDK. >> >> Hopefully this can help bring sooner the ParaView SDK in future versions in >> a more official way... so that we won't have to look into generating the >> NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) >> >> If anyone has any questions, feel free to ask! >> >> Best regards, >> Bruno Santos >> >> PS: I haven't sent this email to the ParaView Developers mailing list simply >> because previous emails I've sent on this topic have been to this main >> mailing list. >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno.santos at bluecape.com.pt Fri Aug 8 12:22:31 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Fri, 08 Aug 2014 17:22:31 +0100 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> Message-ID: <53E4F947.9000203@bluecape.com.pt> Greetings Simon, The reason is simple: because the official builds of ParaView are usually done with MSVC 2008: http://www.paraview.org/Wiki/ParaView_Binaries If we didn't use that version, it would lead to conflicts with the runtime libraries used by the official ParaView binaries versus the plug-ins built using the SDK we've provided. Best regards, Bruno On 08-08-2014 16:25, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hi Bruno, > > Can I ask why you picked MSVC 2008 C++ Express version over MSVC 2013 C++ > Express version to do the compilation? > > Thanks > -simon > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Bruno > Santos > Sent: Wednesday, August 06, 2014 8:59 AM > To: paraview at paraview.org > Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 > and 64-bit > > Greetings to all! > > We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for > Windows 32 and 64-bit, based on the official SuperBuild and respective build > options. It's available here: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#Par > aView_4.1.0 > Instructions on how these packages were built is provided here: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 > > According to our tests, it's possible to use this SDK to build plug-ins and > any other associated applications, which will work with the respective > official ParaView 4.1.0 builds for Windows. A proof of concept we've used is > the vtkPOFFReader plug-in which was successfully built with these SDK > packages: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReader > Builds > > Note: We roughly used the same development environment as the original > ParaView 4.1.0 binaries for Windows: > http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC > 2008 C++ Express and did not have a respective FORTRAN compiler (which > requires the Professional version either way), which is why we needed to do > some adjustments to build Open-MPI with success. > > Furthermore, here's a bit of a back story and the current status of this > endeavour: > > > * Back in January 2012 we at blueCAPE began to try to bring back the > development installers of ParaView for Windows, which was last officially > available for ParaView 3.8.1. > * The overall features available in the development installers we > created were still missing important files, because we were still basing > ourselves on the infrastructure that was still remnant from ParaView 3.8.1. > * Nonetheless, we made available our findings and builds for ParaView > 3.12.0, 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to > build was back in January 2013. > > * ParaView fortunately kept evolving since then. We missed the > versions 3.98.1 and 4.0.1, due to time constraints on our side and a few > failed builds. > * As far as we can see, ParaView 4.1.0 already has a pretty good SDK > structure which evolved overtime. The official SuperBuild repository also > already provides many of the necessary features for making the SDK releases, > at least for the Unix-like environments. > * This Summer 2014 we at blueCAPE finally managed to get around back > to trying and adjust the SuperBuild settings to build and deliver a ParaView > 4.1.0 SDK for Windows and believe we have successfully achieved it. The > changes have been shared and referenced in the following wiki page at our > project: > https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 > * In addition to this, after some reviewing and building tests with > the latest commits on the master branch from the SuperBuild repository, we > have adapted most of the changes we've developed for the SDK build above and > have submitted two commits to Kitware Gerrit, namely: > > > * http://review.source.kitware.com/#/t/4487/ > * http://review.source.kitware.com/#/t/4488/ > > * We haven't managed to create the NSIS and ZIP packages through > CMake/CPack, but our main concern has mostly been on having a working SDK. > > Hopefully this can help bring sooner the ParaView SDK in future versions in > a more official way... so that we won't have to look into generating the > NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) > > If anyone has any questions, feel free to ask! > > Best regards, > Bruno Santos > > PS: I haven't sent this email to the ParaView Developers mailing list simply > because previous emails I've sent on this topic have been to this main > mailing list. > > > Classification: UNCLASSIFIED > Caveats: NONE > > -- http://www.bluecape.com.pt blueCAPE at Facebook blueCAPE at LinkedIn blueCAPE at Twitter blueCAPE at Google+ blueCAPE at YouTube blueCAPE RSS blueCAPE Lda - CAE solutions Rua Fonte dos Corvos, n.29 Casais da Serra 2665-305 Milharado PORTUGAL (+351) 219 755 345 Tel. (+351) 219 755 345 Fax (+351) 926 008 657 Mob. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hegbjhec.png Type: image/png Size: 2391 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: eifhbjfj.png Type: image/png Size: 2420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: efcceehf.png Type: image/png Size: 2535 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aiiiaaci.png Type: image/png Size: 3100 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ieigbbcf.png Type: image/png Size: 2870 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ihhdabig.png Type: image/png Size: 2815 bytes Desc: not available URL: From bruno.santos at bluecape.com.pt Fri Aug 8 12:31:42 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Fri, 08 Aug 2014 17:31:42 +0100 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> Message-ID: <53E4FB6E.3080005@bluecape.com.pt> Greetings Robert, Thanks for the feedback! Then perhaps I should give it a spin to also SuperBuild with Qt 4.8.6 and provide the changes/hacks necessary to include the Qt SDK in the ParaView SDK... Which reminds me: can the Python version be bumped up at least from 2.7.3 to 2.7.8 in the next ParaView version? I haven't reported this as a feature request nor Gerrit commit for review, since it's possible that there is also some other limitation on your side, possibly regarding multi-platform compatibility or the same MSVC version issue? Best regards, Bruno On 08-08-2014 15:30, Robert Maynard wrote: > This is really cool! We should try to integrate the open mpi changes > as those seem really reasonable. > > > As far as building Qt, this is required for two reasons. The first is > that the Qt 4.8 series only has 32bit official binaries for windows, > and we would need 32 and 64bit. If we moved to Qt 5.X it would be > possible to use the official binaries, as long as moved to VS > 2010/2012. > > Now the reason that we currently build with VS 2008 is because of hard > requirements in the python build system. I know that people are > investigating a new build system for python that supports VS 2010 / > VS2012. So if ParaView is ever able to use the new python build > system, and officially moves over to Qt 5.X we should transition to > use the official Qt binaries for windows. > > On Wed, Aug 6, 2014 at 8:59 AM, Bruno Santos > wrote: >> Greetings to all! >> >> We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for >> Windows 32 and 64-bit, based on the official SuperBuild and respective build >> options. It's available here: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 >> Instructions on how these packages were built is provided here: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >> >> According to our tests, it's possible to use this SDK to build plug-ins and >> any other associated applications, which will work with the respective >> official ParaView 4.1.0 builds for Windows. A proof of concept we've used is >> the vtkPOFFReader plug-in which was successfully built with these SDK >> packages: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds >> >> Note: We roughly used the same development environment as the original >> ParaView 4.1.0 binaries for Windows: >> http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC >> 2008 C++ Express and did not have a respective FORTRAN compiler (which >> requires the Professional version either way), which is why we needed to do >> some adjustments to build Open-MPI with success. >> >> Furthermore, here's a bit of a back story and the current status of this >> endeavour: >> >> Back in January 2012 we at blueCAPE began to try to bring back the >> development installers of ParaView for Windows, which was last officially >> available for ParaView 3.8.1. >> The overall features available in the development installers we created were >> still missing important files, because we were still basing ourselves on the >> infrastructure that was still remnant from ParaView 3.8.1. >> Nonetheless, we made available our findings and builds for ParaView 3.12.0, >> 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was >> back in January 2013. >> ParaView fortunately kept evolving since then. We missed the versions 3.98.1 >> and 4.0.1, due to time constraints on our side and a few failed builds. >> As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure >> which evolved overtime. The official SuperBuild repository also already >> provides many of the necessary features for making the SDK releases, at >> least for the Unix-like environments. >> This Summer 2014 we at blueCAPE finally managed to get around back to trying >> and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK >> for Windows and believe we have successfully achieved it. The changes have >> been shared and referenced in the following wiki page at our project: >> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >> In addition to this, after some reviewing and building tests with the latest >> commits on the master branch from the SuperBuild repository, we have adapted >> most of the changes we've developed for the SDK build above and have >> submitted two commits to Kitware Gerrit, namely: >> >> http://review.source.kitware.com/#/t/4487/ >> http://review.source.kitware.com/#/t/4488/ >> >> We haven't managed to create the NSIS and ZIP packages through CMake/CPack, >> but our main concern has mostly been on having a working SDK. >> >> Hopefully this can help bring sooner the ParaView SDK in future versions in >> a more official way... so that we won't have to look into generating the >> NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) >> >> If anyone has any questions, feel free to ask! >> >> Best regards, >> Bruno Santos >> >> PS: I haven't sent this email to the ParaView Developers mailing list simply >> because previous emails I've sent on this topic have been to this main >> mailing list. >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From simon.m.su.ctr at mail.mil Fri Aug 8 12:36:19 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 8 Aug 2014 16:36:19 +0000 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: <53E4F947.9000203@bluecape.com.pt> References: <53E226A9.8070002@bluecape.com.pt> <53E4F947.9000203@bluecape.com.pt> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Greetings Bruno, Thanks. And per Robert, ParaView binaries are done with vs2008 due to Python build system. I tried to build python 2.7.8 (the very last dependency library) with vs2013 express but failed miserably (even with what Gerson Kurz how to list to build python 3.3.4 with Visual Studio 2013). Thankfully I was able to find the link to download vs2008 express iso. Thanks -simon -----Original Message----- From: Bruno Santos [mailto:bruno.santos at bluecape.com.pt] Sent: Friday, August 08, 2014 12:23 PM To: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) Greetings Simon, The reason is simple: because the official builds of ParaView are usually done with MSVC 2008: http://www.paraview.org/Wiki/ParaView_Binaries If we didn't use that version, it would lead to conflicts with the runtime libraries used by the official ParaView binaries versus the plug-ins built using the SDK we've provided. Best regards, Bruno On 08-08-2014 16:25, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hi Bruno, Can I ask why you picked MSVC 2008 C++ Express version over MSVC 2013 C++ Express version to do the compilation? Thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Bruno Santos Sent: Wednesday, August 06, 2014 8:59 AM To: paraview at paraview.org Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit Greetings to all! We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for Windows 32 and 64-bit, based on the official SuperBuild and respective build options. It's available here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#Par aView_4.1.0 Instructions on how these packages were built is provided here: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 According to our tests, it's possible to use this SDK to build plug-ins and any other associated applications, which will work with the respective official ParaView 4.1.0 builds for Windows. A proof of concept we've used is the vtkPOFFReader plug-in which was successfully built with these SDK packages: https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReader Builds Note: We roughly used the same development environment as the original ParaView 4.1.0 binaries for Windows: http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC 2008 C++ Express and did not have a respective FORTRAN compiler (which requires the Professional version either way), which is why we needed to do some adjustments to build Open-MPI with success. Furthermore, here's a bit of a back story and the current status of this endeavour: * Back in January 2012 we at blueCAPE began to try to bring back the development installers of ParaView for Windows, which was last officially available for ParaView 3.8.1. * The overall features available in the development installers we created were still missing important files, because we were still basing ourselves on the infrastructure that was still remnant from ParaView 3.8.1. * Nonetheless, we made available our findings and builds for ParaView 3.12.0, 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was back in January 2013. * ParaView fortunately kept evolving since then. We missed the versions 3.98.1 and 4.0.1, due to time constraints on our side and a few failed builds. * As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure which evolved overtime. The official SuperBuild repository also already provides many of the necessary features for making the SDK releases, at least for the Unix-like environments. * This Summer 2014 we at blueCAPE finally managed to get around back to trying and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK for Windows and believe we have successfully achieved it. The changes have been shared and referenced in the following wiki page at our project: https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 * In addition to this, after some reviewing and building tests with the latest commits on the master branch from the SuperBuild repository, we have adapted most of the changes we've developed for the SDK build above and have submitted two commits to Kitware Gerrit, namely: * http://review.source.kitware.com/#/t/4487/ * http://review.source.kitware.com/#/t/4488/ * We haven't managed to create the NSIS and ZIP packages through CMake/CPack, but our main concern has mostly been on having a working SDK. Hopefully this can help bring sooner the ParaView SDK in future versions in a more official way... so that we won't have to look into generating the NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) If anyone has any questions, feel free to ask! Best regards, Bruno Santos PS: I haven't sent this email to the ParaView Developers mailing list simply because previous emails I've sent on this topic have been to this main mailing list. Classification: UNCLASSIFIED Caveats: NONE -- http://www.bluecape.com.pt blueCAPE at Facebook blueCAPE at LinkedIn blueCAPE at Twitter blueCAPE at Google+ blueCAPE at YouTube blueCAPE RSS blueCAPE Lda - CAE solutions Rua Fonte dos Corvos, n.29 Casais da Serra 2665-305 Milharado PORTUGAL (+351) 219 755 345 Tel. (+351) 219 755 345 Fax (+351) 926 008 657 Mob. Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From bruno.santos at bluecape.com.pt Fri Aug 8 12:49:30 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Fri, 08 Aug 2014 17:49:30 +0100 Subject: [Paraview] ParaView can't create the reader In-Reply-To: References: Message-ID: <53E4FF9A.1020907@bluecape.com.pt> Greetings J?r?my, If you had provided the XML file, it would have been a bit easier to diagnose this ourselves. Nonetheless, it seems to me that the issue is that the class/library "vtkPTecplotBinaryReader" is simply not loadable. A bit of searching online and in ParaView's source code leads me to believe that only the class "vtkTecplotReader" is available for loading through an XML only plug-in. If the class "vtkPTecplotBinaryReader" is a custom library you've built/created from source code, then have a look at a recent email I sent to this very same mailing list: http://public.kitware.com/pipermail/paraview/2014-August/031817.html Best regards, Bruno On 05-08-2014 15:48, J?r?my Santina wrote: > Hello, > > I have written my own reader for ParaView and I am facing with some > issues. > > My version of ParaView is 4.1 for Windows-64 bit and I didn't build it > from sources. > > As the wiki > > describes, I wrote a Server Manager XML file. > Then I set the environment flag PV_PLUGIN_DEBUG. > > Everything seems to work fine when I load the reader with Plugin > Manager as the output messages dialog box indicates : > > *************************************************** > > Attempting to load > C:\Users\Windows\Documents\Travail\ParaviewProject\VTKReaders\Plugin\TecplotBinaryReader.xml > > Loading XML plugin > > Plugin instance located successfully. Now loading components from the > plugin instance based on the interfaces it implements. > > ---------------------------------------------------------------- > > Plugin Information: > > Name : TecplotBinaryReader > > Version : 1.0 > > ReqOnServer : 1 > > ReqOnClient : 0 > > ReqPlugins : > > ServerManager Plugin : Yes > > Python Plugin : No > > > But when I try to open a file, ParaView crashes and I get the > following error message : > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, > line 307 > > vtkSISourceProxy (000000000B340ED0): Failed to create > vtkPTecplotBinaryReader. Aborting for debugging purposes. > > > What am I doing wrong ? > > > Thanks in advance for your help. > > > J?r?my > > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno.santos at bluecape.com.pt Fri Aug 8 12:59:52 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Fri, 08 Aug 2014 17:59:52 +0100 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53E4F8F6.2060703@lbl.gov> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> Message-ID: <53E50208.3040306@bluecape.com.pt> As far as I can understand/deduce: 1. The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, precisely because the support was dropped. I guess the 1.4.4 version provided a more stable'ish working version than 1.6.2. 2. MS-MPI originated from MPICH2 source code for Windows. And MPICH2 is no longer supported on Windows, because MS-MPI is the go-to build of MPICH2 for Windows. 3. Problem is that the source code for the current MS-MPI builds does not seem to be publicly available, which might be why ParaView isn't linking to it in the first place. Although I vaguely remember a ParaView version that was linked to a stub MPI, possibly because of that... On 08-08-2014 17:21, Burlen Loring wrote: > OpenMPI dropped support for windows some time ago. Would it not make > sense to use MS MPI? > > https://www.open-mpi.org/software/ompi/v1.6/ms-windows.php > http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx > > > On 08/08/2014 07:30 AM, Robert Maynard wrote: >> This is really cool! We should try to integrate the open mpi changes >> as those seem really reasonable. >> >> >> As far as building Qt, this is required for two reasons. The first is >> that the Qt 4.8 series only has 32bit official binaries for windows, >> and we would need 32 and 64bit. If we moved to Qt 5.X it would be >> possible to use the official binaries, as long as moved to VS >> 2010/2012. >> >> Now the reason that we currently build with VS 2008 is because of hard >> requirements in the python build system. I know that people are >> investigating a new build system for python that supports VS 2010 / >> VS2012. So if ParaView is ever able to use the new python build >> system, and officially moves over to Qt 5.X we should transition to >> use the official Qt binaries for windows. >> >> On Wed, Aug 6, 2014 at 8:59 AM, Bruno Santos >> wrote: >>> Greetings to all! >>> >>> We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for >>> Windows 32 and 64-bit, based on the official SuperBuild and respective build >>> options. It's available here: >>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 >>> Instructions on how these packages were built is provided here: >>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >>> >>> According to our tests, it's possible to use this SDK to build plug-ins and >>> any other associated applications, which will work with the respective >>> official ParaView 4.1.0 builds for Windows. A proof of concept we've used is >>> the vtkPOFFReader plug-in which was successfully built with these SDK >>> packages: >>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds >>> >>> Note: We roughly used the same development environment as the original >>> ParaView 4.1.0 binaries for Windows: >>> http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC >>> 2008 C++ Express and did not have a respective FORTRAN compiler (which >>> requires the Professional version either way), which is why we needed to do >>> some adjustments to build Open-MPI with success. >>> >>> Furthermore, here's a bit of a back story and the current status of this >>> endeavour: >>> >>> Back in January 2012 we at blueCAPE began to try to bring back the >>> development installers of ParaView for Windows, which was last officially >>> available for ParaView 3.8.1. >>> The overall features available in the development installers we created were >>> still missing important files, because we were still basing ourselves on the >>> infrastructure that was still remnant from ParaView 3.8.1. >>> Nonetheless, we made available our findings and builds for ParaView 3.12.0, >>> 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was >>> back in January 2013. >>> ParaView fortunately kept evolving since then. We missed the versions 3.98.1 >>> and 4.0.1, due to time constraints on our side and a few failed builds. >>> As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure >>> which evolved overtime. The official SuperBuild repository also already >>> provides many of the necessary features for making the SDK releases, at >>> least for the Unix-like environments. >>> This Summer 2014 we at blueCAPE finally managed to get around back to trying >>> and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK >>> for Windows and believe we have successfully achieved it. The changes have >>> been shared and referenced in the following wiki page at our project: >>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >>> In addition to this, after some reviewing and building tests with the latest >>> commits on the master branch from the SuperBuild repository, we have adapted >>> most of the changes we've developed for the SDK build above and have >>> submitted two commits to Kitware Gerrit, namely: >>> >>> http://review.source.kitware.com/#/t/4487/ >>> http://review.source.kitware.com/#/t/4488/ >>> >>> We haven't managed to create the NSIS and ZIP packages through CMake/CPack, >>> but our main concern has mostly been on having a working SDK. >>> >>> Hopefully this can help bring sooner the ParaView SDK in future versions in >>> a more official way... so that we won't have to look into generating the >>> NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) >>> >>> If anyone has any questions, feel free to ask! >>> >>> Best regards, >>> Bruno Santos >>> >>> PS: I haven't sent this email to the ParaView Developers mailing list simply >>> because previous emails I've sent on this topic have been to this main >>> mailing list. >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Aug 8 14:20:59 2014 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 08 Aug 2014 11:20:59 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53E50208.3040306@bluecape.com.pt> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> Message-ID: <53E5150B.9030802@lbl.gov> > The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, > precisely because the support was dropped. I'm not sure about this, Kitware folks could clarify. If ParaView developers are picking an MPI implementation, then it should probably be MS MPI. It's the only option going forward, as other porjects have dropped support some time ago. Using the aging versions of OpenMPI/MPICH are going to be problematic as windows platform compilers etc evolves. > Problem is that the source code for the current MS-MPI builds does not > seem to be publicly available, Is that really a problem? On 08/08/2014 09:59 AM, Bruno Santos wrote: > As far as I can understand/deduce: > > 1. The ParaView dev team switched from Open-MPI 1.6.2 backwards to > 1.4.4, precisely because the support was dropped. I guess the > 1.4.4 version provided a more stable'ish working version than 1.6.2. > 2. MS-MPI originated from MPICH2 source code for Windows. And MPICH2 > is no longer supported on Windows, because MS-MPI is the go-to > build of MPICH2 for Windows. > 3. Problem is that the source code for the current MS-MPI builds does > not seem to be publicly available, which might be why ParaView > isn't linking to it in the first place. Although I vaguely > remember a ParaView version that was linked to a stub MPI, > possibly because of that... > > On 08-08-2014 17:21, Burlen Loring wrote: >> OpenMPI dropped support for windows some time ago. Would it not make >> sense to use MS MPI? >> >> https://www.open-mpi.org/software/ompi/v1.6/ms-windows.php >> http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx >> >> >> On 08/08/2014 07:30 AM, Robert Maynard wrote: >>> This is really cool! We should try to integrate the open mpi changes >>> as those seem really reasonable. >>> >>> >>> As far as building Qt, this is required for two reasons. The first is >>> that the Qt 4.8 series only has 32bit official binaries for windows, >>> and we would need 32 and 64bit. If we moved to Qt 5.X it would be >>> possible to use the official binaries, as long as moved to VS >>> 2010/2012. >>> >>> Now the reason that we currently build with VS 2008 is because of hard >>> requirements in the python build system. I know that people are >>> investigating a new build system for python that supports VS 2010 / >>> VS2012. So if ParaView is ever able to use the new python build >>> system, and officially moves over to Qt 5.X we should transition to >>> use the official Qt binaries for windows. >>> >>> On Wed, Aug 6, 2014 at 8:59 AM, Bruno Santos >>> wrote: >>>> Greetings to all! >>>> >>>> We at blueCAPE have made available an unofficial SDK of ParaView 4.1.0 for >>>> Windows 32 and 64-bit, based on the official SuperBuild and respective build >>>> options. It's available here: >>>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0 >>>> Instructions on how these packages were built is provided here: >>>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >>>> >>>> According to our tests, it's possible to use this SDK to build plug-ins and >>>> any other associated applications, which will work with the respective >>>> official ParaView 4.1.0 builds for Windows. A proof of concept we've used is >>>> the vtkPOFFReader plug-in which was successfully built with these SDK >>>> packages: >>>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds >>>> >>>> Note: We roughly used the same development environment as the original >>>> ParaView 4.1.0 binaries for Windows: >>>> http://www.paraview.org/Wiki/ParaView_Binaries - although we've used MSVC >>>> 2008 C++ Express and did not have a respective FORTRAN compiler (which >>>> requires the Professional version either way), which is why we needed to do >>>> some adjustments to build Open-MPI with success. >>>> >>>> Furthermore, here's a bit of a back story and the current status of this >>>> endeavour: >>>> >>>> Back in January 2012 we at blueCAPE began to try to bring back the >>>> development installers of ParaView for Windows, which was last officially >>>> available for ParaView 3.8.1. >>>> The overall features available in the development installers we created were >>>> still missing important files, because we were still basing ourselves on the >>>> infrastructure that was still remnant from ParaView 3.8.1. >>>> Nonetheless, we made available our findings and builds for ParaView 3.12.0, >>>> 3.14.0, 3.14.1 and 3.98.0, where the last release we managed to build was >>>> back in January 2013. >>>> ParaView fortunately kept evolving since then. We missed the versions 3.98.1 >>>> and 4.0.1, due to time constraints on our side and a few failed builds. >>>> As far as we can see, ParaView 4.1.0 already has a pretty good SDK structure >>>> which evolved overtime. The official SuperBuild repository also already >>>> provides many of the necessary features for making the SDK releases, at >>>> least for the Unix-like environments. >>>> This Summer 2014 we at blueCAPE finally managed to get around back to trying >>>> and adjust the SuperBuild settings to build and deliver a ParaView 4.1.0 SDK >>>> for Windows and believe we have successfully achieved it. The changes have >>>> been shared and referenced in the following wiki page at our project: >>>> https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410 >>>> In addition to this, after some reviewing and building tests with the latest >>>> commits on the master branch from the SuperBuild repository, we have adapted >>>> most of the changes we've developed for the SDK build above and have >>>> submitted two commits to Kitware Gerrit, namely: >>>> >>>> http://review.source.kitware.com/#/t/4487/ >>>> http://review.source.kitware.com/#/t/4488/ >>>> >>>> We haven't managed to create the NSIS and ZIP packages through CMake/CPack, >>>> but our main concern has mostly been on having a working SDK. >>>> >>>> Hopefully this can help bring sooner the ParaView SDK in future versions in >>>> a more official way... so that we won't have to look into generating the >>>> NSIS/ZIP packages ourselves, nor build Qt 4.8.6 ;) >>>> >>>> If anyone has any questions, feel free to ask! >>>> >>>> Best regards, >>>> Bruno Santos >>>> >>>> PS: I haven't sent this email to the ParaView Developers mailing list simply >>>> because previous emails I've sent on this topic have been to this main >>>> mailing list. >>>> >>>> >>>> _______________________________________________ >>>> Powered bywww.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.cohen at gmail.com Fri Aug 8 17:57:16 2014 From: denis.cohen at gmail.com (denis cohen) Date: Fri, 8 Aug 2014 23:57:16 +0200 Subject: [Paraview] Variable in Calculator Filter in batch script Message-ID: Hi, I'd like to pass a variable name to the Calculator Filter in a batch script, something like A=500 Calculator1.Function = 'min(coordsZ,A)' This gives an error message: "...Syntax error: expecting a variable name...". What's the correct form? Thank you Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Aug 8 20:29:02 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 8 Aug 2014 20:29:02 -0400 Subject: [Paraview] Variable in Calculator Filter in batch script In-Reply-To: References: Message-ID: I think the following should work: A = 500 Calculator1.Function = 'min(coordsZ,'+str(A)+')' On Fri, Aug 8, 2014 at 5:57 PM, denis cohen wrote: > Hi, > > I'd like to pass a variable name to the Calculator Filter in a batch > script, something like > A=500 > Calculator1.Function = 'min(coordsZ,A)' > > This gives an error message: > "...Syntax error: expecting a variable name...". > > What's the correct form? > > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maillist.alan at gmail.com Fri Aug 8 21:03:57 2014 From: maillist.alan at gmail.com (Alan TaN) Date: Sat, 9 Aug 2014 13:03:57 +1200 Subject: [Paraview] CLASP 2014: The 2014 International Workshop on Advances in Cloud Computing Legislation, Accountability, Security and Privacy, London, Deadline:24th Aug Message-ID: <194e801cfb36d$ced4e660$6c7eb320$@gmail.com> [Please accept our apologies if you have received multiple copies of this message.] [CALL FOR PAPERS] ********************************************************************* CLASP 2014: The 2014 International Workshop on Advances in Cloud Computing Legislation, Accountability, Security and Privacy In conjunction with the 7th IEEE/ACM IEEE/ACM International Conference on Utility and Cloud Computing (UCC 2014) Link: https://crow.org.nz/clasp2014.html ********************************************************************* Date: 8-11 December 2014 Location: London, UKB Important dates: Paper submission due: 24 August 2014 (PST midnight) Notification of acceptance: 15 September 2014 Early registration deadline: 29 September 2014 Overview The success of cloud computing hinges on striking an effective balance between security, trust and privacy concerns. In addition, governments have to ensure that both domestic and international legislations align with the evolving challenges resulting from the maturity of cloud computing as a mainstream IT business model. The nature of a trusted third party (e.g. an offshore cloud service provider) has also pushed policy making to the limits. For example, what should institutions consider when they are employing a cloud service provider, which hosts their data in an offshore data center? There are many technical and policy aspects relating to this research area, and in this workshop, we seek to provide a platform for the engagement and discussion of this interesting, multi-disciplinary topic. We also welcome emerging innovative concepts and analysis which will shape the cloud computing landscape from a technical perspective. Topics of Interest We welcome technical-, policy- and/or legal-oriented submissions related to (but not limited to) the following: -Cloud accountability -Cloud data analytics -Cloud data governance -Cloud forensics -Cloud privacy -Cloud provenance -Cloud security (e.g. cryptographic techniques and protocols) -Cloud trust -Cloud visualizations We also welcome survey papers as well as novel proposals for a paradigm shift on one or more of the above topics. For submission details, please refer to the web page (link provided at the top) for more information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lingdeer at gmail.com Mon Aug 11 01:55:47 2014 From: lingdeer at gmail.com (Elaine Tang) Date: Mon, 11 Aug 2014 01:55:47 -0400 Subject: [Paraview] Using time in Python script Message-ID: Hi, I have data in time that has time points like {0.02124,0.04248,0.06372,0.08496, etc.} I wrote a python script to loop through these time points with time increment of 0.02124 and export as .csv. ---------------------------------------------- for x in range(1, 4): currentT = x*deltaT AnimationScene1 = GetAnimationScene() RenderView1 = GetRenderView() AnimationScene1.AnimationTime = currentT RenderView1.ViewTime = currentT RenderView1.CacheKey = currentT RenderView1.UseCache = 1 RenderView1.UseCache = 0 SetActiveSource(data) writer = CreateWriter("output.csv") writer.FieldAssociation = "Points" writer.UpdatePipeline() del writer Render() ------------------------------------------ When I played the macro, some time points were not correctly read. (e.g. the 4th time point spreadsheet saved data that belong to the 3rd time point.) I used "start trace" to see how paraview handles time, and here is what I caught: -------------------------------------------------------- try: paraview.simple except: from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() AnimationScene1 = GetAnimationScene() RenderView1 = GetRenderView() AnimationScene1.AnimationTime = 0.021239999681711197 RenderView1.ViewTime = 0.021239999681711197 RenderView1.CacheKey = 0.021239999681711197 RenderView1.UseCache = 1 AnimationScene1.AnimationTime = 0.042479999363422394 RenderView1.ViewTime = 0.042479999363422394 RenderView1.CacheKey = 0.042479999363422394 RenderView1.UseCache = 1 AnimationScene1.AnimationTime = 0.06372000277042389 RenderView1.ViewTime = 0.06372000277042389 RenderView1.CacheKey = 0.06372000277042389 RenderView1.UseCache = 1 AnimationScene1.AnimationTime = 0.08495999872684479 RenderView1.ViewTime = 0.08495999872684479 RenderView1.CacheKey = 0.08495999872684479 RenderView1.UseCache = 1 RenderView1.UseCache = 0 Render() -------------------------------------------------------- Then I realized, if I tried to read data at 0.08496, it will read data from the previous time point instead. If I explicitly specify in my script to read data at time 0.08495999872684479, then it will read the correct data. Anyone has any insights? Thanks in advance!!! -- Elaine -------------- next part -------------- An HTML attachment was scrubbed... URL: From nmiri127 at gmail.com Mon Aug 11 10:05:51 2014 From: nmiri127 at gmail.com (Nabil Miri) Date: Mon, 11 Aug 2014 11:35:51 -0230 Subject: [Paraview] Use Stream Tracer to show path of moving object. Message-ID: Hi, I was wondering if it was possible to use the Stream Tracer filter to show the path of moving objects in a simulation? The objects were created in Yade and they simply fall to a surface and exhibit buoyancy. Thanks, -Nabil -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 11 11:03:27 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 11 Aug 2014 11:03:27 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53E5150B.9030802@lbl.gov> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> Message-ID: > The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, > precisely because the support was dropped. That is correct. That's precisely why we've stuck with 1.4.4. I spent a lot of time trying to packing 1.6.* on Windows to no success and then decided to just stick with 1.4.4. > Problem is that the source code for the current MS-MPI builds does not seem > to be publicly available, The problem with using MS-MPI is two fold: 1. I can't remember if its support MPIv2 API. I don't think so, but I may be wrong. 2. The license (at least when I checked) doesn't allow us to packing the dlls in our binaries. In other words, we would always have to have the user manually install using the installer distributed by MS. Utkarsh From utkarsh.ayachit at kitware.com Mon Aug 11 11:29:21 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 11 Aug 2014 11:29:21 -0400 Subject: [Paraview] Plot point variable over time In-Reply-To: References: Message-ID: Rakesh, The dataset you included doesn't have any timesteps. Nor I do I see any variable named "displacement". The only variables available are "uvw". To plot over time, you select the cells or point that you want plot over time and the create the "Plot Over Time" filter. That would show you a plot of the attributes for the selected elements over time. Utkarsh On Thu, Aug 7, 2014 at 12:50 AM, Rakesh Dhote wrote: > Hi, > > > I have a quick question. > How to plot a point variable over time? > > It seems the procedure mentioned in the following mailing list refer to the > previous version of the Paraview. > http://www.paraview.org/pipermail/paraview/2012-November/026633.html > > Thank you for your help in advance. > > Warm regards, > Rakesh > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From jeremy.santina at gmail.com Mon Aug 11 12:01:57 2014 From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=) Date: Mon, 11 Aug 2014 18:01:57 +0200 Subject: [Paraview] ParaView can't create the reader In-Reply-To: <53E4FF9A.1020907@bluecape.com.pt> References: <53E4FF9A.1020907@bluecape.com.pt> Message-ID: Thank you very much for your answer. I am sorry for my awful English and I hope you'll understand what I am writing. I read the email you sent and I tried to build my reader following the instructions provided here : https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds First of all, I downloaded this archive : ParaView-4.1.0-win64-complete_dev-r2.exe Then I installed Qt 4.8.2 from here : https://code.google.com/p/qt-msvc-installer/. Finally when I am trying to configure my reader with the CMake GUI, the QT_MAKE_EXECUTABLE can't be found even if I select qmake.exe directly from the path. In fact I am a beginner and I don't really know how to use CMake. I modified the CMakeLists.txt that I found here : http://sourceforge.net/p/of-interfaces/code/HEAD/tree/trunk/vtkPOFFReader/ but I am not sure about what I wrote. My CMakeLists file is joined with this message. Besides, I noticed that when I am executing *qt-win64-opensource-4.8.2-vs2008.exe, *a dialog box with the following message is opened : *A installation of Visual Studio 2008 was not found in the registry , guessing path...* In spite of that, the installation seems to work perfectly fine but : I have Visual C++ Express 2008 on my computer so is it normal to get this message ? To finish, I would like to ask you one last question : Given I didn't develop any GUI feature for my reader, do I still need QT ? I thank you again for your help. J?r?my 2014-08-08 18:49 GMT+02:00 Bruno Santos : > Greetings J?r?my, > > If you had provided the XML file, it would have been a bit easier to > diagnose this ourselves. > Nonetheless, it seems to me that the issue is that the class/library > "vtkPTecplotBinaryReader" is simply not loadable. A bit of searching online > and in ParaView's source code leads me to believe that only the class > "vtkTecplotReader" is available for loading through an XML only plug-in. > > If the class "vtkPTecplotBinaryReader" is a custom library you've > built/created from source code, then have a look at a recent email I sent > to this very same mailing list: > http://public.kitware.com/pipermail/paraview/2014-August/031817.html > > Best regards, > Bruno > > > On 05-08-2014 15:48, J?r?my Santina wrote: > > Hello, > > I have written my own reader for ParaView and I am facing with some > issues. > > My version of ParaView is 4.1 for Windows-64 bit and I didn't build it > from sources. > > As the wiki > > describes, I wrote a Server Manager XML file. > Then I set the environment flag PV_PLUGIN_DEBUG. > > Everything seems to work fine when I load the reader with Plugin Manager > as the output messages dialog box indicates : > > *************************************************** > > Attempting to load > C:\Users\Windows\Documents\Travail\ParaviewProject\VTKReaders\Plugin\TecplotBinaryReader.xml > > Loading XML plugin > > Plugin instance located successfully. Now loading components from the > plugin instance based on the interfaces it implements. > > ---------------------------------------------------------------- > > Plugin Information: > > Name : TecplotBinaryReader > > Version : 1.0 > > ReqOnServer : 1 > > ReqOnClient : 0 > > ReqPlugins : > > ServerManager Plugin : Yes > > Python Plugin : No > > But when I try to open a file, ParaView crashes and I get the following > error message : > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, > line 307 > > vtkSISourceProxy (000000000B340ED0): Failed to create > vtkPTecplotBinaryReader. Aborting for debugging purposes. > > > What am I doing wrong ? > > > Thanks in advance for your help. > > > J?r?my > > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- #/*========================================================================= # # Copyright (c) 2008-2010 Takuya OSHIMA . # All rights reserved. # See License_v1.2.txt for details. # # This software is distributed WITHOUT ANY WARRANTY; without even # the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR # PURPOSE. See the above copyright notice for more information. # #=========================================================================*/ CMAKE_MINIMUM_REQUIRED(VERSION 2.6) SET(CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS TRUE) # Find a ParaView build first in order to get its configuration IF(ParaView_SOURCE_DIR) SET(INSOURCE_PLUGIN TRUE) ELSE() SET(INSOURCE_PLUGIN FALSE) FIND_PACKAGE(ParaView REQUIRED) INCLUDE(${PARAVIEW_USE_FILE}) ENDIF() # Construct version number string and check IF(NOT DEFINED PARAVIEW_VERSION) SET(PARAVIEW_VERSION "${PARAVIEW_VERSION_MAJOR}.${PARAVIEW_VERSION_MINOR}") ENDIF() IF(PARAVIEW_VERSION VERSION_LESS "3.10") MESSAGE(FATAL_ERROR "ParaView version ${PARAVIEW_VERSION} is too old." " The package only supports ParaView 3.10 or later.") ENDIF() IF(NOT INSOURCE_PLUGIN) # Set default installation directory IF(PARAVIEW_LIBRARY_DIRS) IF(CMAKE_INSTALL_PREFIX STREQUAL "/usr/local" OR CMAKE_INSTALL_PREFIX STREQUAL "C:/Program Files/Project" OR CMAKE_INSTALL_PREFIX STREQUAL "C:/Program Files (x86)/Project") IF(DEFINED ENV{PV_PLUGIN_PATH}) # Installing to plugin path defined by PV_PLUGIN_PATH SET(CMAKE_INSTALL_PREFIX "$ENV{PV_PLUGIN_PATH}") ELSE() IF(ParaView_BINARY_DIR MATCHES ".*/bin") # Installing to the development install of ParaView IF(APPLE) SET(CMAKE_INSTALL_PREFIX "${ParaView_BINARY_DIR}/Plugins") ELSEIF(DEFINED CMAKE_BUILD_TYPE) SET(CMAKE_INSTALL_PREFIX "${ParaView_BINARY_DIR}/plugins") ELSE() # This is not checked yet; may be wrong SET(CMAKE_INSTALL_PREFIX "${PARAVIEW_BINARY_DIR}/Release/plugins") ENDIF() ELSE() # Installing to the build directory of ParaView IF(APPLE) SET(CMAKE_INSTALL_PREFIX "${PARAVIEW_LIBRARY_DIRS}/Plugins") ELSEIF(DEFINED CMAKE_BUILD_TYPE) SET(CMAKE_INSTALL_PREFIX "${PARAVIEW_LIBRARY_DIRS}/plugins") ELSE() SET(CMAKE_INSTALL_PREFIX "${PARAVIEW_LIBRARY_DIRS}/Release/plugins") ENDIF() ENDIF() ENDIF() SET(CMAKE_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}" CACHE PATH "Install path prefix, prepended onto install directories." FORCE) ENDIF() ENDIF() # Set default build type to Release if Makefile-based build system is used IF(DEFINED CMAKE_BUILD_TYPE AND NOT CMAKE_BUILD_TYPE) SET(CMAKE_BUILD_TYPE Release CACHE STRING "Choose the type of build, options are: None Debug Release RelWithDebInfo MinSizeRel." FORCE) ENDIF() ENDIF() # THE SERVER SIDE ############################################################# # Add include directories IF(INSOURCE_PLUGIN) INCLUDE_DIRECTORIES(${PARAVIEW_INCLUDE_DIRS} ${VTK_INCLUDE_DIR}) ENDIF() # Server side plugin ADD_PARAVIEW_PLUGIN( TecplotBinaryReaderPlugin "1.0" REQUIRED_ON_SERVER SERVER_MANAGER_XML TecplotBinaryReader.xml SERVER_MANAGER_SOURCES vtkPTecplotBinaryReader.cxx ) # Set installation destination IF(NOT INSOURCE_PLUGIN) # ParaView 3.6.2 has been modified after release so that plugins are # built without manifests if MSVC is used. With the modification # there seems to be no way to tell exactly whether plugins are built # as SHARED or MODULE so there seems to be no way to tell whether # RUNTIME or LIBRARY target should be specified either. INSTALL(TARGETS TecplotBinaryReaderPlugin DESTINATION "${CMAKE_INSTALL_PREFIX}") ENDIF() # THE CLIENT SIDE ############################################################# IF(PARAVIEW_BUILD_QT_GUI) # Set installation destination IF(NOT INSOURCE_PLUGIN) # ParaView 3.6.2 has been modified after release so that plugins # are built without manifests if MSVC is used. With the # modification there seems to be no way to tell exactly whether # plugins are built as SHARED or MODULE so there seems to be no # way to tell whether RUNTIME or LIBRARY target should be # specified either. INSTALL(TARGETS TecplotBinaryReaderPlugin DESTINATION "${CMAKE_INSTALL_PREFIX}") ENDIF() ENDIF() -------------- next part -------------- A non-text attachment was scrubbed... Name: TecplotBinaryReader.xml Type: text/xml Size: 817 bytes Desc: not available URL: From bloring at lbl.gov Mon Aug 11 12:46:18 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 11 Aug 2014 09:46:18 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> Message-ID: <53E8F35A.3050600@lbl.gov> Hi Utkarsh, I think it does implement MPI2. At least my codes make heavy use of MPI 2 and it works fine. However, I'll look into it and report back. Microsoft's documentation says: You may also redistribute this MS-MPI installation package with your own applications, to facilitate having an application that can run on a stand-alone workstation and easily take advantage of an HPC Pack 2012 R2-based cluster. Please refer to the license agreement for additional details. Sounds like if you use an installer it could handle the dependency. Burlen On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >> precisely because the support was dropped. > That is correct. That's precisely why we've stuck with 1.4.4. I spent > a lot of time trying to packing 1.6.* on Windows to no success and > then decided to just stick with 1.4.4. > >> Problem is that the source code for the current MS-MPI builds does not seem >> to be publicly available, > The problem with using MS-MPI is two fold: > 1. I can't remember if its support MPIv2 API. I don't think so, but I > may be wrong. > 2. The license (at least when I checked) doesn't allow us to packing > the dlls in our binaries. In other words, we would always have to have > the user manually install using the installer distributed by MS. > > Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 11 12:53:43 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 11 Aug 2014 12:53:43 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53E8F35A.3050600@lbl.gov> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> Message-ID: Additionally, you need to run the installer as admin since it installs a daemon (I believe). I think it would make sense to put out two version of Windows binaries (without MPI and with MS MPI) and then include the MSMPI installer as a part of the installation process, esp. since no other Windows MPI is officially supported any more. Something to think about for 4.3, not sure I want to make the plunge for 4.2 -- but we'll keep the options open :). Utkarsh On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: > Hi Utkarsh, > > I think it does implement MPI2. At least my codes make heavy use of MPI 2 > and it works fine. However, I'll look into it and report back. > > Microsoft's documentation says: > > You may also redistribute this MS-MPI installation package with your own > applications, to facilitate having an application that can run on a > stand-alone workstation and easily take advantage of an HPC Pack 2012 > R2-based cluster. Please refer to the license agreement for additional > details. > > > Sounds like if you use an installer it could handle the dependency. > > Burlen > > > On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: > > The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, > precisely because the support was dropped. > > That is correct. That's precisely why we've stuck with 1.4.4. I spent > a lot of time trying to packing 1.6.* on Windows to no success and > then decided to just stick with 1.4.4. > > Problem is that the source code for the current MS-MPI builds does not seem > to be publicly available, > > The problem with using MS-MPI is two fold: > 1. I can't remember if its support MPIv2 API. I don't think so, but I > may be wrong. > 2. The license (at least when I checked) doesn't allow us to packing > the dlls in our binaries. In other words, we would always have to have > the user manually install using the installer distributed by MS. > > Utkarsh > > From bwvb at xs4all.nl Tue Aug 12 04:46:20 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 12 Aug 2014 10:46:20 +0200 Subject: [Paraview] Support for QT5 broken with qt 5.3.X? In-Reply-To: <53E34E50.9060705@hzdr.de> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> <53E13290.9000503@xs4all.nl> <53E1F6AC.1090709@hzdr.de> <53E2D0C7.1080507@xs4all.nl> <53E34E50.9060705@hzdr.de> Message-ID: <53E9D45C.3020105@xs4all.nl> Could it be that the support for Qt 5.3.x is broken in Paraview? When I upgraded from Qt5.2.1 to Qt5.3.1 recompiled paraview, I always get link errors as described below. On inspection, I noticed that symbols like 'qt_filedialog_existing_directory_hook' are no longer found in Qt5.3.1, whereas they still are there in Qt5.2.1. I don't know how how ParaView implicitly uses these symbols, perhaps knows more on this. Kind Regadds, Bertwim On 08/07/2014 12:00 PM, Huebl, Axel wrote: > Hm, looks like the cleanest way to get it running is to remove default > installations of qt from the system path(s) and to specificity only one > specific installation via environment flags. > > (I am suggesting something that can be achieved with a module system, > e.g. on a cluster) > > Alternatively you can try to scratch all the advanced flags together > that are still wrong and set them by hand. > >> What does this tell me? > Yep, but basically it is still an environment problem. > > Best, > Axel > > On 07.08.2014 03:05, B.W.H. van Beest wrote: >> Hi Axel, >> >> setting CMAKE_PREFIX_PATH does not make a difference. The special >> variables left that have a reference to the wrong qt installation are >> QT_QT3SUPPORT_LIBRARY and QT3SUPPORT_LIBRARY_RELEASE variables. Qt5 >> does no longer provide Qt4 support . >> >> Also QT_QTCORE_LIBRARY and QT_QDBUS and QT_GUI_LIBRARY_ are wrong .... >> The correspinding HEADER-varinant are ok, though. >> What does this tell me? >> >> Regards, >> Bertwim >> >> >> On 08/06/2014 11:34 AM, Huebl, Axel wrote: >>> Dear Bertwim, >>> >>> >>> good to hear that. >>> >>> sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and >>> "LD_LIBRARY_PATH" to hint install directories to CMake modules. >>> >>> The compile error still looks like something got mixed - can you try >>> again with the CMAKE_PREFIX_PATH hint? >>> Did you verify all "advanced" variables set from the FindQt module with >>> ccmake? >>> >>> >>> Best, >>> Axel >>> >>> On 05.08.2014 21:37, B.W.H. van Beest wrote: >>>> Dear Axel, >>>> >>>> No I haven't. To follow-up on your suggestion, I ran ccmake again to set >>>> this parameter. No CMAKE_PREFIX_PATH is in the list! >>>> What I did try -and what did make a difference, was not only prepending >>>> the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin >>>> was first in $PATH. This indeed has the result that all libQt5 >>>> directories found were the correct ones. Maybe that amounts to the same? >>>> >>>> However, Now I have a different compile error: >>>> >>>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>>> function `pqNativeFileDialogEventPlayer::start()': >>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to >>>> `qt_filedialog_existing_directory_hook' >>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to >>>> `qt_filedialog_open_filename_hook' >>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to >>>> `qt_filedialog_open_filenames_hook' >>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to >>>> `qt_filedialog_save_filename_hook' >>>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>>> function `pqNativeFileDialogEventPlayer::stop()': >>>> >>>> >>>> etc. >>>> >>>> Any ideas? >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 08/05/2014 08:38 PM, Huebl, Axel wrote: >>>>> Dear Bertwim, >>>>> >>>>> have you tried prepending/setting the >>>>> CMAKE_PREFIX_PATH >>>>> >>>>> to your qt5 install dir? >>>>> >>>>> Best, >>>>> Axel >>>>> On 05.08.2014 18:07, B.W.H. van Beest wrote: >>>>>> Hi Burien, thanks for responding. >>>>>> >>>>>> I have done you suggested, but to no avail. >>>>>> Somehow, the path to the executable qmake is not sufficient to determine >>>>>> all the other QT5 libraries. >>>>>> Having said that, in one of the by now many attempts to get paraview >>>>>> configured, I found that indeed the correct QT5 libraries were selected. >>>>>> That build, however failed (missing symbol, cannot remember which one). >>>>>> In trying to correct this is, the wrong QT5 libraries were selected by >>>>>> ccmake. I just cannot figure out how this cmake thing works, or what I >>>>>> can do to force it. >>>>>> Any suggestions? >>>>>> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> >>>>>> >>>>>> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>>>>>> system install may be first in the linker search path. have you >>>>>>> checked? If that's it: rm your build, and in addition to >>>>>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>>>>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>>>>>> PV do the same. >>>>>>> >>>>>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> On my system, I have 2 installations of QT5. One is the distribution >>>>>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>>>>>> one is a more recent version (5.3.1), which I downloaded and installed >>>>>>>> in a different location. >>>>>>>> Using ccmake, setting the QT version to 5, as well as setting >>>>>>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>>>>>> I still see that ccmake selects of number of qt5-libraries that belong >>>>>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>>>>>> in fact). I can build paraview, though, and it even seems to work >>>>>>>> (smoketest), but at program exit it segfaults. >>>>>>>> >>>>>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>>>>>> don't need to change all the entries by hand? >>>>>>>> >>>>>>>> Thanks in advance >>>>>>>> Bertwim >>>> >> >> From david.thompson at kitware.com Tue Aug 12 09:37:21 2014 From: david.thompson at kitware.com (David Thompson) Date: Tue, 12 Aug 2014 09:37:21 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F947.9000203@bluecape.com.pt> Message-ID: > Thanks. And per Robert, ParaView binaries are done with vs2008 due to Python > build system. I tried to build python 2.7.8 (the very last dependency > library) with vs2013 express but failed miserably (even with what Gerson > Kurz how to list to build python 3.3.4 with Visual Studio 2013). Thankfully > I was able to find the link to download vs2008 express iso. David Sansome and JC Fillion-Robin have created a CMake-ified version of Python that will build with other versions of VS: https://github.com/davidsansome/python-cmake-buildsystem/ but currently (as of a month ago) it does not support debug builds -- which is something we most probably require before moving ParaView to use it. David From bruno.santos at bluecape.com.pt Tue Aug 12 11:36:44 2014 From: bruno.santos at bluecape.com.pt (Bruno Santos) Date: Tue, 12 Aug 2014 16:36:44 +0100 Subject: [Paraview] ParaView can't create the reader In-Reply-To: References: <53E4FF9A.1020907@bluecape.com.pt> Message-ID: <53EA348C.9070808@bluecape.com.pt> First of all, your English looks pretty good! OK, let's see if I can address all of the issues: 1. Make sure you downloaded the 3 files that were needed for installing Qt 4.8.2, namely the file "qt-win64-opensource-4.8.2-vs2008.exe" and the two associated "*.bin" files. The 3 files should be placed in the same folder before running the installer. 2. In CMake, define the variable "QT_MAKE_EXECUTABLE" to use the path "C:/Qt/4.8.2_x64/bin/qmake.exe" (adjust accordingly if necessary) and then click on "Configure" once again. Hopefully it will now pick up everything related to Qt. 1. Mmm... still regarding this point, if you in fact gave the correct path, it might not work properly if the Qt installation is somehow incomplete. This happened to me when I tried to configure the project with CMake, while I was still midway of the installation of Qt. 2. Furthermore, there was a detail I forgot to write on the wiki page, but when using MSVC 2008 Express, by default it does not provide the ability to compile 64-bit applications. Instructions on how to do so can be found online, for example here: https://github.com/enGits/engrid/wiki/Configure-Microsoft-Visual-Studio-2008-Express-to-also-build-for-Windows-x64 3. And there is yet another import detail: when you configure the project in CMake's GUI for the first time, it asks you which compiler to use. Make sure you pick "Visual Studio 9 2008 Win64". If you pick the standard non-Win64, it's natural that the 64-bit "qmake.exe" is incompatible with the 32-bit Visual Studio build options. 3. Regarding the files you've provided in attachment: 1. The XML looks OK. I only have some experience with creating these types of XML file, so I'm not yet able to point out any major flaws without looking into ParaView's own XML filter/reader files. The complete XML file I'm referring to is in the folder "ParaViewCore\ServerManager\SMApplication\Resources" in ParaView's source code. 2. The "CMakeLists.txt" looks OK as well, but again, I don't have enough experience on this. Only by trial and error would I be able to see if your file is working properly. 3. I suggest that you first try building the plug-in "vtkPOFFReader", just to confirm if you have a working building environment. This way it'll be easier to isolate the origin of any problems. 4. "I have Visual C++ Express 2008 on my computer so is it normal to get this message ?"*/ /* * Yes, it's normal. It happens to me as well and it works without any problems. 5. Due to how ParaView was built in this case, I think it's best to use Qt 4.8.2 (namely with the respective architecture), just in case. I say this because there are a lot of library dependencies that are automatically configured and it might get a bit complicated to push aside the existing dependencies on Qt. I hope I didn't miss anything. Best regards, Bruno On 11-08-2014 17:01, J?r?my Santina wrote: > Thank you very much for your answer. > > I am sorry for my awful English and I hope you'll understand what I am > writing. > > I read the email you sent and I tried to build my reader following the > instructions provided here : > https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds > > First of all, I downloaded this archive : > ParaView-4.1.0-win64-complete_dev-r2.exe > > Then I installed Qt 4.8.2 from here : > https://code.google.com/p/qt-msvc-installer/. Finally when I am trying > to configure my reader with the CMake GUI, the QT_MAKE_EXECUTABLE > can't be found even if I select qmake.exe directly from the path. > > In fact I am a beginner and I don't really know how to use CMake. I > modified the CMakeLists.txt that I found here : > http://sourceforge.net/p/of-interfaces/code/HEAD/tree/trunk/vtkPOFFReader/ > but I am not sure about what I wrote. My CMakeLists file is joined > with this message. > > Besides, I noticed that when I am executing > /qt-win64-opensource-4.8.2-vs2008.exe, /a dialog box with the > following message is opened : > > /A installation of Visual Studio 2008 was not found in the registry , > guessing path.../ > > In spite of that, the installation seems to work perfectly fine but : > I have Visual C++ Express 2008 on my computer so is it normal to get > this message ? > > To finish, I would like to ask you one last question : > Given I didn't develop any GUI feature for my reader, do I still need QT ? > > I thank you again for your help. > > J?r?my > > > 2014-08-08 18:49 GMT+02:00 Bruno Santos >: > > Greetings J?r?my, > > If you had provided the XML file, it would have been a bit easier > to diagnose this ourselves. > Nonetheless, it seems to me that the issue is that the > class/library "vtkPTecplotBinaryReader" is simply not loadable. A > bit of searching online and in ParaView's source code leads me to > believe that only the class "vtkTecplotReader" is available for > loading through an XML only plug-in. > > If the class "vtkPTecplotBinaryReader" is a custom library you've > built/created from source code, then have a look at a recent email > I sent to this very same mailing list: > http://public.kitware.com/pipermail/paraview/2014-August/031817.html > > Best regards, > Bruno > > > On 05-08-2014 15:48, J?r?my Santina wrote: >> Hello, >> >> I have written my own reader for ParaView and I am facing with >> some issues. >> >> My version of ParaView is 4.1 for Windows-64 bit and I didn't >> build it from sources. >> >> As the wiki >> >> describes, I wrote a Server Manager XML file. >> Then I set the environment flag PV_PLUGIN_DEBUG. >> >> Everything seems to work fine when I load the reader with Plugin >> Manager as the output messages dialog box indicates : >> >> *************************************************** >> >> Attempting to load >> C:\Users\Windows\Documents\Travail\ParaviewProject\VTKReaders\Plugin\TecplotBinaryReader.xml >> >> Loading XML plugin >> >> Plugin instance located successfully. Now loading components from >> the plugin instance based on the interfaces it implements. >> >> ---------------------------------------------------------------- >> >> Plugin Information: >> >> Name : TecplotBinaryReader >> >> Version : 1.0 >> >> ReqOnServer : 1 >> >> ReqOnClient : 0 >> >> ReqPlugins : >> >> ServerManager Plugin : Yes >> >> Python Plugin : No >> >> >> But when I try to open a file, ParaView crashes and I get the >> following error message : >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, >> line 307 >> >> vtkSISourceProxy (000000000B340ED0): Failed to create >> vtkPTecplotBinaryReader. Aborting for debugging purposes. >> >> >> What am I doing wrong ? >> >> >> Thanks in advance for your help. >> >> >> J?r?my >> >> >> >> >> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcrocker at uvm.edu Tue Aug 12 14:29:21 2014 From: rcrocker at uvm.edu (Ryan Crocker) Date: Tue, 12 Aug 2014 11:29:21 -0700 Subject: [Paraview] streamlines on 2D plane from 3D data Message-ID: <4B369AEB-431A-4D49-B379-C1588DE94AB2@uvm.edu> Hi, I'm using paraview 4.1.0-64bit and i'm trying to simply add streamlines from a 3D flow to a slice. This happens automatically if i start with 2D data but i cannot seem to make it work with 3D data. I've tried using the surface LIC plugin, but i when i activate it and try to use it as a representation nothing happens, the slice looks like it does without surface LIC. I changed all the parameters to what should be applicable to my data and still, nothing happens. Paraview is not even asking if i would like to apply the changes. The second approach i tried was to use this tutorial: http://www.paraview.org/Wiki/ParaView/Custom_Filters but i'm not even sure how that is stared, is there a more step by step approach where they do this from initial raw data to the final form. I cannot get this to work. This seems like something that should be pretty straight forward. The flow i'm trying to visualize is a 3D convective cell. thanks for the help, Ryan Crocker University of Vermont, School of Engineering Mechanical Engineering Department rcrocker at uvm.edu 315-212-7331 -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Tue Aug 12 16:56:30 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Tue, 12 Aug 2014 13:56:30 -0700 Subject: [Paraview] streamlines on 2D plane from 3D data In-Reply-To: <4B369AEB-431A-4D49-B379-C1588DE94AB2@uvm.edu> References: <4B369AEB-431A-4D49-B379-C1588DE94AB2@uvm.edu> Message-ID: <53EA7F7E.7000808@gmail.com> Hi Ryan, Try using Surface Vectors filter to remove the out of surface component from the vector field, and make sure your seeds are exactly on the surface. As far as surface lic, are you sure you selected the right vector field? If yes, please share the data and I'll see if I can duplicate the issue. Burlen On 08/12/2014 11:29 AM, Ryan Crocker wrote: > Hi, > > I'm using paraview 4.1.0-64bit and i'm trying to simply add > streamlines from a 3D flow to a slice. This happens automatically if > i start with 2D data but i cannot seem to make it work with 3D data. > I've tried using the surface LIC plugin, but i when i activate it and > try to use it as a representation nothing happens, the slice looks > like it does without surface LIC. I changed all the parameters to > what should be applicable to my data and still, nothing happens. > Paraview is not even asking if i would like to apply the changes. > > The second approach i tried was to use this tutorial: > > http://www.paraview.org/Wiki/ParaView/Custom_Filters > > but i'm not even sure how that is stared, is there a more step by step > approach where they do this from initial raw data to the final form. I > cannot get this to work. This seems like something that should be > pretty straight forward. > > The flow i'm trying to visualize is a 3D convective cell. > > > thanks for the help, > > Ryan Crocker > University of Vermont, School of Engineering > Mechanical Engineering Department > rcrocker at uvm.edu > 315-212-7331 > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Tue Aug 12 17:26:05 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Tue, 12 Aug 2014 17:26:05 -0400 Subject: [Paraview] Help with Programmable Filter In-Reply-To: <1407180080018.38754@goodyear.com> References: <1407180080018.38754@goodyear.com> Message-ID: Hi Dennis, I took a look at the filter to see what might be wrong, but I seem to be missing a couple of things: 1) Are you using the "Copy Arrays" option of the programmable filter? Otherwise you will need to reference the input data as well. 2) Where are the P1,P2,P3, etc vectors created? What type are they? The below script worked for me if Copy Arrays is enabled. I used the can.ex2 example dataset from paraview and ensured the "Object Ids" cell data was selected in the reader. for oblock in output: oid = oblock.CellData['ObjectId'] o2 = oid + 10 oblock.CellData.append(o2, 'newdata') Hope that helps On Mon, Aug 4, 2014 at 3:21 PM, Dennis Conklin wrote: > I have the following script for a Paraview Programmable filter: > > > import math > import numpy > > # > # Gdyr_Principal_Strains_ProgFilter > # Rev 0 > # Aug 1, 2014 > # Dennis Conklin - Engineering Mechanics > # > # Paraview 4.0.1 Progammable Filter > # Adds Cell Variables: > # Principal Strains: str_P1, str_P2, str_P3 > # max shear strain: tau_max > # These can be used for coloring, Spreadsheet view, formulas, threshold, > etc > # > def process_block(block): > # > # Global coordinate strains > # Assume strains loaded in Paraview > xx = block.CellData['USTRTOTXX'] > yy = block.CellData['USTRTOTYY'] > zz = block.CellData['USTRTOTZZ'] > xy = block.CellData['USTRTOTXY'] > xz = block.CellData['USTRTOTZX'] > yz = block.CellData['USTRTOTYZ'] > > for i in range(block.GetNumberOfCells() > sigma = numpy.array([ [xx[i],xy[i],xz[i]], > [xy[i],yy[i],yz[i]], > [xz[i],yz[i],zz[i]] > ]) > > # isotropic strain matrix > iso = 1.0/3.0*numpy.trace(sigma)*numpy.eye(3) > # deviatoric strain matrix > dev = sigma - iso > > #principal strains > eigvals = list(numpy.linalg.eigvalsh(sigma)) > eigvals.sort() > eigvals.reverse() > P1[i] = eigvals[0] > P2[i] = eigvals[1] > P3[i] = eigvals[2] > # max shear > max_shear[i] = (max(eigvals)-min(eigvals))/2.0 > > block.CellData.append(P1,"P1_strain") > block.CellData.append(P2,"P2_strain") > block.CellData.append(P3,"P3_strain") > block.CellData.append(max_shear,"tauMax") > > > # Loop over blocks in composite (Exodus) data set > for block in output: > # process each block > process_block(block) > > After running this script, no errors or warnings are issued but the > additional quantites (taumax, Px_strain) are not present as element > quantities. > > Any hints as to what I'm doing wrong. > > > Dennis Conklin, PE > RDE&Q Senior Engineer > Goodyear Innovation Center, 5th Floor South, Pillar M34 > Phone: 330-796-5701 > Email: dennis_conklin at goodyear.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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Tue Aug 12 17:41:27 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Tue, 12 Aug 2014 17:41:27 -0400 Subject: [Paraview] Writing csv data in python script (UNCLASSIFIED) In-Reply-To: References: Message-ID: I am not aware of any paraview specific way to do that. You could try the standard python csv module https://docs.python.org/2/library/csv.html or use numpy savetxt for arrays http://docs.scipy.org/doc/numpy/reference/generated/numpy.savetxt.html. -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Aug 12 18:49:42 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 12 Aug 2014 22:49:42 +0000 Subject: [Paraview] Map scalars, User question Message-ID: <0bc08bc54d554e389e65536a760a9090@ES05AMSNLNT.srn.sandia.gov> I have a user that is trying to do the following: I am trying to do something very similar to what is shown under "Visualizing the Microstructure" at the following site: http://dream3d.bluequartz.net/Documentation/DREAM3D/tutorialebsdreconstruction.html I believe they essentially associate IPFColor_Z with red, green, and blue colors in the XDMF file. Then, they load the file into Paraview and when they disable the "Map Scalars" option, Paraview just displays the proper RGB color for IPFColor_Z. Is this possible with exodus instead of XDMF? So far I have been unsuccessful. Anyone have any ideas? I have been able to create a .vtk file, with a UInt8 array. When I turn off Map Scalars, this variable correctly paints from black to white. But, if I try to create three UInt8's, for RGB, I can't get it to work. I even tried creating an array in the calculator. So, I believe the part that concerns ParaView is as follows - how to I create a dataset that has 0xRRGGBBAA type data, that Paraview will just display as its color? For instance, if I have 0xff000000, I want to see red. Ideas? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Aug 12 19:40:13 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 12 Aug 2014 23:40:13 +0000 Subject: [Paraview] [EXTERNAL] Map scalars, User question In-Reply-To: <0bc08bc54d554e389e65536a760a9090@ES05AMSNLNT.srn.sandia.gov> References: <0bc08bc54d554e389e65536a760a9090@ES05AMSNLNT.srn.sandia.gov> Message-ID: I figured it out. Thanks. The block of VTK that works is as follows. Makes a 3 component array of UInt8's. 0 0 0 255 0 0 0 255 0 0 0 255 255 255 0 255 0 255 255 255 0 255 255 255 64 64 64 128 128 128 Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Tuesday, August 12, 2014 4:50 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Map scalars, User question I have a user that is trying to do the following: I am trying to do something very similar to what is shown under "Visualizing the Microstructure" at the following site: http://dream3d.bluequartz.net/Documentation/DREAM3D/tutorialebsdreconstruction.html I believe they essentially associate IPFColor_Z with red, green, and blue colors in the XDMF file. Then, they load the file into Paraview and when they disable the "Map Scalars" option, Paraview just displays the proper RGB color for IPFColor_Z. Is this possible with exodus instead of XDMF? So far I have been unsuccessful. Anyone have any ideas? I have been able to create a .vtk file, with a UInt8 array. When I turn off Map Scalars, this variable correctly paints from black to white. But, if I try to create three UInt8's, for RGB, I can't get it to work. I even tried creating an array in the calculator. So, I believe the part that concerns ParaView is as follows - how to I create a dataset that has 0xRRGGBBAA type data, that Paraview will just display as its color? For instance, if I have 0xff000000, I want to see red. Ideas? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Tue Aug 12 23:50:36 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Tue, 12 Aug 2014 20:50:36 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> Message-ID: <53EAE08C.7080106@gmail.com> Ahh, that may be, I wouldn't have noticed it since I have admin on my account. as far as the version of the standard implemented by MS MPI in HPC Pack 2012 (internal ver 256), it's 2.0. The TestSystemCaps regression test has the code to report. On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: > Additionally, you need to run the installer as admin since it installs > a daemon (I believe). I think it would make sense to put out two > version of Windows binaries (without MPI and with MS MPI) and then > include the MSMPI installer as a part of the installation process, > esp. since no other Windows MPI is officially supported any more. > > Something to think about for 4.3, not sure I want to make the plunge > for 4.2 -- but we'll keep the options open :). > > Utkarsh > > > > > > On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >> Hi Utkarsh, >> >> I think it does implement MPI2. At least my codes make heavy use of MPI 2 >> and it works fine. However, I'll look into it and report back. >> >> Microsoft's documentation says: >> >> You may also redistribute this MS-MPI installation package with your own >> applications, to facilitate having an application that can run on a >> stand-alone workstation and easily take advantage of an HPC Pack 2012 >> R2-based cluster. Please refer to the license agreement for additional >> details. >> >> >> Sounds like if you use an installer it could handle the dependency. >> >> Burlen >> >> >> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >> >> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >> precisely because the support was dropped. >> >> That is correct. That's precisely why we've stuck with 1.4.4. I spent >> a lot of time trying to packing 1.6.* on Windows to no success and >> then decided to just stick with 1.4.4. >> >> Problem is that the source code for the current MS-MPI builds does not seem >> to be publicly available, >> >> The problem with using MS-MPI is two fold: >> 1. I can't remember if its support MPIv2 API. I don't think so, but I >> may be wrong. >> 2. The license (at least when I checked) doesn't allow us to packing >> the dlls in our binaries. In other words, we would always have to have >> the user manually install using the installer distributed by MS. >> >> 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Wed Aug 13 10:07:32 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Aug 2014 10:07:32 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53EAE08C.7080106@gmail.com> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> Message-ID: Good to know. I think we'll make the switch at the same time when we upgrade the VS compiler we're using for the binaries. We are switching to using CMakified Python soon and then we wouldn't need to use VS2008. Any thoughts on which is the most common VS compiler? Qt distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 :). On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: > Ahh, that may be, I wouldn't have noticed it since I have admin on my > account. > > as far as the version of the standard implemented by MS MPI in HPC Pack 2012 > (internal ver 256), it's 2.0. The TestSystemCaps regression test has the > code to report. > > > On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >> >> Additionally, you need to run the installer as admin since it installs >> a daemon (I believe). I think it would make sense to put out two >> version of Windows binaries (without MPI and with MS MPI) and then >> include the MSMPI installer as a part of the installation process, >> esp. since no other Windows MPI is officially supported any more. >> >> Something to think about for 4.3, not sure I want to make the plunge >> for 4.2 -- but we'll keep the options open :). >> >> Utkarsh >> >> >> >> >> >> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>> >>> Hi Utkarsh, >>> >>> I think it does implement MPI2. At least my codes make heavy use of MPI 2 >>> and it works fine. However, I'll look into it and report back. >>> >>> Microsoft's documentation says: >>> >>> You may also redistribute this MS-MPI installation package with your own >>> applications, to facilitate having an application that can run on a >>> stand-alone workstation and easily take advantage of an HPC Pack 2012 >>> R2-based cluster. Please refer to the license agreement for additional >>> details. >>> >>> >>> Sounds like if you use an installer it could handle the dependency. >>> >>> Burlen >>> >>> >>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>> >>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >>> precisely because the support was dropped. >>> >>> That is correct. That's precisely why we've stuck with 1.4.4. I spent >>> a lot of time trying to packing 1.6.* on Windows to no success and >>> then decided to just stick with 1.4.4. >>> >>> Problem is that the source code for the current MS-MPI builds does not >>> seem >>> to be publicly available, >>> >>> The problem with using MS-MPI is two fold: >>> 1. I can't remember if its support MPIv2 API. I don't think so, but I >>> may be wrong. >>> 2. The license (at least when I checked) doesn't allow us to packing >>> the dlls in our binaries. In other words, we would always have to have >>> the user manually install using the installer distributed by MS. >>> >>> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > From dennis_conklin at goodyear.com Wed Aug 13 10:45:13 2014 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 13 Aug 2014 14:45:13 +0000 Subject: [Paraview] Help with Programmable Filter In-Reply-To: References: <1407180080018.38754@goodyear.com>, Message-ID: <1407941113062.3442@goodyear.com> ?Casey, I am trying to get back to this among all the other firedrills. Yes, I am using Copy Arrays I also tried a simple filter where I just assigned values and that worked as well. It seems the area that isn't working is: for i in range(block.GetNumberOfElements()): sigma = numpy.array([ [xx[i],xy[i],xz[i]], [xy[i],yy[i],yz[i]], [xz[i],yz[i],zz[i]] ]) # isotropic strain matrix iso = 1.0/3.0*numpy.trace(sigma)*numpy.eye(3) # deviatoric strain matrix dev = sigma - iso #principal strains eigvals = list(numpy.linalg.eigvalsh(sigma)) eigvals.sort() eigvals.reverse() P1[i] = eigvals[0] P2[i] = eigvals[1] P3[i] = eigvals[2] # max shear max_shear[i] = (max(eigvals)-min(eigvals))/2.0 I wasn't sure if I had to convert to numpy arrays for this to work so I tried xx = vtkDataArrayToVTKArray(block.CellData['USTRTOTXX']) ... to get numpy arrays to use in sigma, but that doesn't work either. P1,P2 and P3 are not declared anywhere before they are first used - could that be the problem? ? Also, how do I get debug prints to show up somewhere - I'm not getting any error messages in the console or the Output Window. thanks Dennis Conklin, PE RDE&Q Principal Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.com ________________________________ From: Casey Goodlett Sent: Tuesday, August 12, 2014 5:26 PM To: Dennis Conklin Cc: paraview at paraview.org Subject: Re: [Paraview] Help with Programmable Filter Hi Dennis, I took a look at the filter to see what might be wrong, but I seem to be missing a couple of things: 1) Are you using the "Copy Arrays" option of the programmable filter? Otherwise you will need to reference the input data as well. 2) Where are the P1,P2,P3, etc vectors created? What type are they? The below script worked for me if Copy Arrays is enabled. I used the can.ex2 example dataset from paraview and ensured the "Object Ids" cell data was selected in the reader. for oblock in output: oid = oblock.CellData['ObjectId'] o2 = oid + 10 oblock.CellData.append(o2, 'newdata') Hope that helps On Mon, Aug 4, 2014 at 3:21 PM, Dennis Conklin > wrote: I have the following script for a Paraview Programmable filter: import math import numpy # # Gdyr_Principal_Strains_ProgFilter # Rev 0 # Aug 1, 2014 # Dennis Conklin - Engineering Mechanics # # Paraview 4.0.1 Progammable Filter # Adds Cell Variables: # Principal Strains: str_P1, str_P2, str_P3 # max shear strain: tau_max # These can be used for coloring, Spreadsheet view, formulas, threshold, etc # def process_block(block): # # Global coordinate strains # Assume strains loaded in Paraview xx = block.CellData['USTRTOTXX'] yy = block.CellData['USTRTOTYY'] zz = block.CellData['USTRTOTZZ'] xy = block.CellData['USTRTOTXY'] xz = block.CellData['USTRTOTZX'] yz = block.CellData['USTRTOTYZ'] for i in range(block.GetNumberOfCells() sigma = numpy.array([ [xx[i],xy[i],xz[i]], [xy[i],yy[i],yz[i]], [xz[i],yz[i],zz[i]] ]) # isotropic strain matrix iso = 1.0/3.0*numpy.trace(sigma)*numpy.eye(3) # deviatoric strain matrix dev = sigma - iso #principal strains eigvals = list(numpy.linalg.eigvalsh(sigma)) eigvals.sort() eigvals.reverse() P1[i] = eigvals[0] P2[i] = eigvals[1] P3[i] = eigvals[2] # max shear max_shear[i] = (max(eigvals)-min(eigvals))/2.0 block.CellData.append(P1,"P1_strain") block.CellData.append(P2,"P2_strain") block.CellData.append(P3,"P3_strain") block.CellData.append(max_shear,"tauMax") # Loop over blocks in composite (Exodus) data set for block in output: # process each block process_block(block) After running this script, no errors or warnings are issued but the additional quantites (taumax, Px_strain) are not present as element quantities. Any hints as to what I'm doing wrong. Dennis Conklin, PE RDE&Q Senior Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Wed Aug 13 10:56:11 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 13 Aug 2014 07:56:11 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> Message-ID: <53EB7C8B.50709@gmail.com> makes me wonder if the installer could also install python binaries? ;-) I'm not sure which compiler you should use, I tend to think the newer compiler would potentially generate better code, but I don't know if there are other factors that you need to consider when creating binaries. On 08/13/2014 07:07 AM, Utkarsh Ayachit wrote: > Good to know. I think we'll make the switch at the same time when we > upgrade the VS compiler we're using for the binaries. We are switching > to using CMakified Python soon and then we wouldn't need to use > VS2008. Any thoughts on which is the most common VS compiler? Qt > distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 > :). > > On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: >> Ahh, that may be, I wouldn't have noticed it since I have admin on my >> account. >> >> as far as the version of the standard implemented by MS MPI in HPC Pack 2012 >> (internal ver 256), it's 2.0. The TestSystemCaps regression test has the >> code to report. >> >> >> On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >>> Additionally, you need to run the installer as admin since it installs >>> a daemon (I believe). I think it would make sense to put out two >>> version of Windows binaries (without MPI and with MS MPI) and then >>> include the MSMPI installer as a part of the installation process, >>> esp. since no other Windows MPI is officially supported any more. >>> >>> Something to think about for 4.3, not sure I want to make the plunge >>> for 4.2 -- but we'll keep the options open :). >>> >>> Utkarsh >>> >>> >>> >>> >>> >>> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>>> Hi Utkarsh, >>>> >>>> I think it does implement MPI2. At least my codes make heavy use of MPI 2 >>>> and it works fine. However, I'll look into it and report back. >>>> >>>> Microsoft's documentation says: >>>> >>>> You may also redistribute this MS-MPI installation package with your own >>>> applications, to facilitate having an application that can run on a >>>> stand-alone workstation and easily take advantage of an HPC Pack 2012 >>>> R2-based cluster. Please refer to the license agreement for additional >>>> details. >>>> >>>> >>>> Sounds like if you use an installer it could handle the dependency. >>>> >>>> Burlen >>>> >>>> >>>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>>> >>>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >>>> precisely because the support was dropped. >>>> >>>> That is correct. That's precisely why we've stuck with 1.4.4. I spent >>>> a lot of time trying to packing 1.6.* on Windows to no success and >>>> then decided to just stick with 1.4.4. >>>> >>>> Problem is that the source code for the current MS-MPI builds does not >>>> seem >>>> to be publicly available, >>>> >>>> The problem with using MS-MPI is two fold: >>>> 1. I can't remember if its support MPIv2 API. I don't think so, but I >>>> may be wrong. >>>> 2. The license (at least when I checked) doesn't allow us to packing >>>> the dlls in our binaries. In other words, we would always have to have >>>> the user manually install using the installer distributed by MS. >>>> >>>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> From utkarsh.ayachit at kitware.com Wed Aug 13 10:59:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Aug 2014 10:59:22 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53EB7C8B.50709@gmail.com> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <53EB7C8B.50709@gmail.com> Message-ID: On Wed, Aug 13, 2014 at 10:56 AM, Burlen Loring wrote: > makes me wonder if the installer could also install python binaries? ;-) Haha! Me wonders too .. the problem is if the user installed Python in some location, then he'd need to setup PATH before paraview could run. From bloring at lbl.gov Wed Aug 13 11:06:40 2014 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 13 Aug 2014 08:06:40 -0700 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <53EB7C8B.50709@gmail.com> Message-ID: <53EB7F00.40300@lbl.gov> I was thinking along the lines that the ParaView installer, could leverage the python official installer behind the scenes, but direct it into the ParaView specific location... On 08/13/2014 07:59 AM, Utkarsh Ayachit wrote: > On Wed, Aug 13, 2014 at 10:56 AM, Burlen Loring wrote: >> makes me wonder if the installer could also install python binaries? ;-) > Haha! Me wonders too .. the problem is if the user installed Python in > some location, then he'd need to setup PATH before paraview could run. From dennis_conklin at goodyear.com Wed Aug 13 11:08:05 2014 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 13 Aug 2014 15:08:05 +0000 Subject: [Paraview] Help with Programmable Filter In-Reply-To: References: <1407180080018.38754@goodyear.com>, Message-ID: <1407942485797.52757@goodyear.com> P.S. P1, P2, P3 and max_shear are each just scalar numbers (value of Principal strains) - the P1[] is just a value for each element in the block Dennis Conklin, PE RDE&Q Principal Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.com ________________________________ From: Casey Goodlett Sent: Tuesday, August 12, 2014 5:26 PM To: Dennis Conklin Cc: paraview at paraview.org Subject: Re: [Paraview] Help with Programmable Filter Hi Dennis, I took a look at the filter to see what might be wrong, but I seem to be missing a couple of things: 1) Are you using the "Copy Arrays" option of the programmable filter? Otherwise you will need to reference the input data as well. 2) Where are the P1,P2,P3, etc vectors created? What type are they? The below script worked for me if Copy Arrays is enabled. I used the can.ex2 example dataset from paraview and ensured the "Object Ids" cell data was selected in the reader. for oblock in output: oid = oblock.CellData['ObjectId'] o2 = oid + 10 oblock.CellData.append(o2, 'newdata') Hope that helps On Mon, Aug 4, 2014 at 3:21 PM, Dennis Conklin > wrote: I have the following script for a Paraview Programmable filter: import math import numpy # # Gdyr_Principal_Strains_ProgFilter # Rev 0 # Aug 1, 2014 # Dennis Conklin - Engineering Mechanics # # Paraview 4.0.1 Progammable Filter # Adds Cell Variables: # Principal Strains: str_P1, str_P2, str_P3 # max shear strain: tau_max # These can be used for coloring, Spreadsheet view, formulas, threshold, etc # def process_block(block): # # Global coordinate strains # Assume strains loaded in Paraview xx = block.CellData['USTRTOTXX'] yy = block.CellData['USTRTOTYY'] zz = block.CellData['USTRTOTZZ'] xy = block.CellData['USTRTOTXY'] xz = block.CellData['USTRTOTZX'] yz = block.CellData['USTRTOTYZ'] for i in range(block.GetNumberOfCells() sigma = numpy.array([ [xx[i],xy[i],xz[i]], [xy[i],yy[i],yz[i]], [xz[i],yz[i],zz[i]] ]) # isotropic strain matrix iso = 1.0/3.0*numpy.trace(sigma)*numpy.eye(3) # deviatoric strain matrix dev = sigma - iso #principal strains eigvals = list(numpy.linalg.eigvalsh(sigma)) eigvals.sort() eigvals.reverse() P1[i] = eigvals[0] P2[i] = eigvals[1] P3[i] = eigvals[2] # max shear max_shear[i] = (max(eigvals)-min(eigvals))/2.0 block.CellData.append(P1,"P1_strain") block.CellData.append(P2,"P2_strain") block.CellData.append(P3,"P3_strain") block.CellData.append(max_shear,"tauMax") # Loop over blocks in composite (Exodus) data set for block in output: # process each block process_block(block) After running this script, no errors or warnings are issued but the additional quantites (taumax, Px_strain) are not present as element quantities. Any hints as to what I'm doing wrong. Dennis Conklin, PE RDE&Q Senior Engineer Goodyear Innovation Center, 5th Floor South, Pillar M34 Phone: 330-796-5701 Email: dennis_conklin at goodyear.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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Wed Aug 13 11:11:29 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Wed, 13 Aug 2014 11:11:29 -0400 Subject: [Paraview] Help with Programmable Filter In-Reply-To: <1407941113062.3442@goodyear.com> References: <1407180080018.38754@goodyear.com> <1407941113062.3442@goodyear.com> Message-ID: > I wasn't sure if I had to convert to numpy arrays for this to work so I > tried > xx = vtkDataArrayToVTKArray(block.CellData['USTRTOTXX']) > ... > > to get numpy arrays to use in sigma, but that doesn't work either. > > I do not think you should need that when you access the cell data as you are with block.CellData['XX'] > P1,P2 and P3 are not declared anywhere before they are first used - > could that be the problem? > ? > Yes that would be a problem when you try to assign an element to an array. For example try using the python shell in paraview and executing "P1[0] = 2.0". You should get an error message. The list should be created prior to element assignment like import numpy P1 = numpy.zeros(1) P1[0] = 2.0 > Also, how do I get debug prints to show up somewhere - I'm not getting > any error messages in the console or the Output Window. > > I have not seen this problem before so I do not have many suggestions. Solving this first should help you debug the rest. Have you tried putting some print statements in the very first lines of the filter? Maybe try this in a new programmable filter in case there is a syntax error in the code and that is obscuring the printouts? Can you confirm the output window you are looking at is the one you find in the Tools section of the menu? Hope that helps. -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 13 11:12:26 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Aug 2014 11:12:26 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <53EB7F00.40300@lbl.gov> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <53EB7C8B.50709@gmail.com> <53EB7F00.40300@lbl.gov> Message-ID: On Wed, Aug 13, 2014 at 11:06 AM, Burlen Loring wrote: > I was thinking along the lines that the ParaView installer, could leverage > the python official installer behind the scenes, but direct it into the > ParaView specific location... Ah! I wonder if that's doable, but it is, yea -- unless that brings back the manifest issues -- grr...makes me shudder. Post 4.2, not before that, definitely :) From Michael.M.Stephens at erdc.dren.mil Wed Aug 13 11:24:14 2014 From: Michael.M.Stephens at erdc.dren.mil (Stephens, Michael M ERDC-RDE-ITL-MS) Date: Wed, 13 Aug 2014 15:24:14 +0000 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> Message-ID: <4EBFE0C75EDFCB4EA50E6496FB1072C052174F3C@MS-EX2VKS.erdc.dren.mil> Classification: UNCLASSIFIED Caveats: FOUO some food for thought on this subject. VS run time system for VS2010 and earlier has a bug in it that doesn't allow XML flavored files (vtu, vtp, etc) over 4 GB (or was it 2 GB?) to be read correctly. it has an fseek error. I think this was reported a while back when I first stumbled on it. I've HEARD that this was fixed in VS2012/2013 but have not verified it personally. -m -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Wednesday, August 13, 2014 9:08 AM To: Burlen Loring Cc: paraview at paraview.org Subject: Re: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit Good to know. I think we'll make the switch at the same time when we upgrade the VS compiler we're using for the binaries. We are switching to using CMakified Python soon and then we wouldn't need to use VS2008. Any thoughts on which is the most common VS compiler? Qt distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 :). On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: > Ahh, that may be, I wouldn't have noticed it since I have admin on my > account. > > as far as the version of the standard implemented by MS MPI in HPC > Pack 2012 (internal ver 256), it's 2.0. The TestSystemCaps regression > test has the code to report. > > > On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >> >> Additionally, you need to run the installer as admin since it >> installs a daemon (I believe). I think it would make sense to put out >> two version of Windows binaries (without MPI and with MS MPI) and >> then include the MSMPI installer as a part of the installation >> process, esp. since no other Windows MPI is officially supported any more. >> >> Something to think about for 4.3, not sure I want to make the plunge >> for 4.2 -- but we'll keep the options open :). >> >> Utkarsh >> >> >> >> >> >> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>> >>> Hi Utkarsh, >>> >>> I think it does implement MPI2. At least my codes make heavy use of >>> MPI 2 and it works fine. However, I'll look into it and report back. >>> >>> Microsoft's documentation says: >>> >>> You may also redistribute this MS-MPI installation package with your >>> own applications, to facilitate having an application that can run >>> on a stand-alone workstation and easily take advantage of an HPC >>> Pack 2012 R2-based cluster. Please refer to the license agreement >>> for additional details. >>> >>> >>> Sounds like if you use an installer it could handle the dependency. >>> >>> Burlen >>> >>> >>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>> >>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to >>> 1.4.4, precisely because the support was dropped. >>> >>> That is correct. That's precisely why we've stuck with 1.4.4. I >>> spent a lot of time trying to packing 1.6.* on Windows to no success >>> and then decided to just stick with 1.4.4. >>> >>> Problem is that the source code for the current MS-MPI builds does >>> not seem to be publicly available, >>> >>> The problem with using MS-MPI is two fold: >>> 1. I can't remember if its support MPIv2 API. I don't think so, but >>> I may be wrong. >>> 2. The license (at least when I checked) doesn't allow us to packing >>> the dlls in our binaries. In other words, we would always have to >>> have the user manually install using the installer distributed by MS. >>> >>> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: FOUO From simon.m.su.ctr at mail.mil Wed Aug 13 12:27:25 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 13 Aug 2014 16:27:25 +0000 Subject: [Paraview] Writing csv data in python script (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE I will give it a try. Thanks Casey, -simon -----Original Message----- From: Casey Goodlett [mailto:casey.goodlett at kitware.com] Sent: Tuesday, August 12, 2014 5:41 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview Subject: Re: [Paraview] Writing csv data in python script (UNCLASSIFIED) I am not aware of any paraview specific way to do that. You could try the standard python csv module https://docs.python.org/2/library/csv.html or use numpy savetxt for arrays http://docs.scipy.org/doc/numpy/reference/generated/numpy.savetxt.html. -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From robert.maynard at kitware.com Wed Aug 13 13:28:03 2014 From: robert.maynard at kitware.com (Robert Maynard) Date: Wed, 13 Aug 2014 13:28:03 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: <4EBFE0C75EDFCB4EA50E6496FB1072C052174F3C@MS-EX2VKS.erdc.dren.mil> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <4EBFE0C75EDFCB4EA50E6496FB1072C052174F3C@MS-EX2VKS.erdc.dren.mil> Message-ID: The fseek/ftell issue has two potential causes. 1. Somebody is using the fseek / ftell function on windows instead of _fseeki64 / _ftelli64 which are the only way I am aware of seeking inside files that are larger than 2GB using the C fread functions. 2. You are using std::fstream with VisualStudio 2010 or less, seekg contains a bug where internally it casts all offsets to signed long values, which on windows are at most 32bits. This has been fixed in VS 2012. For more information on this bug is, this SO thread is a good starting spot: http://stackoverflow.com/questions/13837810/seekg-cannot-handle-file-of-4294967295-bytes-properly On Wed, Aug 13, 2014 at 11:24 AM, Stephens, Michael M ERDC-RDE-ITL-MS wrote: > Classification: UNCLASSIFIED > Caveats: FOUO > > some food for thought on this subject. > VS run time system for VS2010 and earlier has a bug in it that doesn't allow XML flavored files (vtu, vtp, etc) over 4 GB (or was it 2 GB?) to be read correctly. > it has an fseek error. I think this was reported a while back when I first stumbled on it. > > I've HEARD that this was fixed in VS2012/2013 but have not verified it personally. > > -m > > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit > Sent: Wednesday, August 13, 2014 9:08 AM > To: Burlen Loring > Cc: paraview at paraview.org > Subject: Re: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit > > Good to know. I think we'll make the switch at the same time when we upgrade the VS compiler we're using for the binaries. We are switching to using CMakified Python soon and then we wouldn't need to use VS2008. Any thoughts on which is the most common VS compiler? Qt distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 :). > > On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: >> Ahh, that may be, I wouldn't have noticed it since I have admin on my >> account. >> >> as far as the version of the standard implemented by MS MPI in HPC >> Pack 2012 (internal ver 256), it's 2.0. The TestSystemCaps regression >> test has the code to report. >> >> >> On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >>> >>> Additionally, you need to run the installer as admin since it >>> installs a daemon (I believe). I think it would make sense to put out >>> two version of Windows binaries (without MPI and with MS MPI) and >>> then include the MSMPI installer as a part of the installation >>> process, esp. since no other Windows MPI is officially supported any more. >>> >>> Something to think about for 4.3, not sure I want to make the plunge >>> for 4.2 -- but we'll keep the options open :). >>> >>> Utkarsh >>> >>> >>> >>> >>> >>> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>>> >>>> Hi Utkarsh, >>>> >>>> I think it does implement MPI2. At least my codes make heavy use of >>>> MPI 2 and it works fine. However, I'll look into it and report back. >>>> >>>> Microsoft's documentation says: >>>> >>>> You may also redistribute this MS-MPI installation package with your >>>> own applications, to facilitate having an application that can run >>>> on a stand-alone workstation and easily take advantage of an HPC >>>> Pack 2012 R2-based cluster. Please refer to the license agreement >>>> for additional details. >>>> >>>> >>>> Sounds like if you use an installer it could handle the dependency. >>>> >>>> Burlen >>>> >>>> >>>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>>> >>>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to >>>> 1.4.4, precisely because the support was dropped. >>>> >>>> That is correct. That's precisely why we've stuck with 1.4.4. I >>>> spent a lot of time trying to packing 1.6.* on Windows to no success >>>> and then decided to just stick with 1.4.4. >>>> >>>> Problem is that the source code for the current MS-MPI builds does >>>> not seem to be publicly available, >>>> >>>> The problem with using MS-MPI is two fold: >>>> 1. I can't remember if its support MPIv2 API. I don't think so, but >>>> I may be wrong. >>>> 2. The license (at least when I checked) doesn't allow us to packing >>>> the dlls in our binaries. In other words, we would always have to >>>> have the user manually install using the installer distributed by MS. >>>> >>>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > Classification: UNCLASSIFIED > Caveats: FOUO > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Wed Aug 13 13:42:39 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Aug 2014 13:42:39 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit (UNCLASSIFIED) In-Reply-To: <4EBFE0C75EDFCB4EA50E6496FB1072C052174F3C@MS-EX2VKS.erdc.dren.mil> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <4EBFE0C75EDFCB4EA50E6496FB1072C052174F3C@MS-EX2VKS.erdc.dren.mil> Message-ID: Good to know. On Wed, Aug 13, 2014 at 11:24 AM, Stephens, Michael M ERDC-RDE-ITL-MS wrote: > Classification: UNCLASSIFIED > Caveats: FOUO > > some food for thought on this subject. > VS run time system for VS2010 and earlier has a bug in it that doesn't allow XML flavored files (vtu, vtp, etc) over 4 GB (or was it 2 GB?) to be read correctly. > it has an fseek error. I think this was reported a while back when I first stumbled on it. > > I've HEARD that this was fixed in VS2012/2013 but have not verified it personally. > > -m > > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit > Sent: Wednesday, August 13, 2014 9:08 AM > To: Burlen Loring > Cc: paraview at paraview.org > Subject: Re: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit > > Good to know. I think we'll make the switch at the same time when we upgrade the VS compiler we're using for the binaries. We are switching to using CMakified Python soon and then we wouldn't need to use VS2008. Any thoughts on which is the most common VS compiler? Qt distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 :). > > On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: >> Ahh, that may be, I wouldn't have noticed it since I have admin on my >> account. >> >> as far as the version of the standard implemented by MS MPI in HPC >> Pack 2012 (internal ver 256), it's 2.0. The TestSystemCaps regression >> test has the code to report. >> >> >> On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >>> >>> Additionally, you need to run the installer as admin since it >>> installs a daemon (I believe). I think it would make sense to put out >>> two version of Windows binaries (without MPI and with MS MPI) and >>> then include the MSMPI installer as a part of the installation >>> process, esp. since no other Windows MPI is officially supported any more. >>> >>> Something to think about for 4.3, not sure I want to make the plunge >>> for 4.2 -- but we'll keep the options open :). >>> >>> Utkarsh >>> >>> >>> >>> >>> >>> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>>> >>>> Hi Utkarsh, >>>> >>>> I think it does implement MPI2. At least my codes make heavy use of >>>> MPI 2 and it works fine. However, I'll look into it and report back. >>>> >>>> Microsoft's documentation says: >>>> >>>> You may also redistribute this MS-MPI installation package with your >>>> own applications, to facilitate having an application that can run >>>> on a stand-alone workstation and easily take advantage of an HPC >>>> Pack 2012 R2-based cluster. Please refer to the license agreement >>>> for additional details. >>>> >>>> >>>> Sounds like if you use an installer it could handle the dependency. >>>> >>>> Burlen >>>> >>>> >>>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>>> >>>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to >>>> 1.4.4, precisely because the support was dropped. >>>> >>>> That is correct. That's precisely why we've stuck with 1.4.4. I >>>> spent a lot of time trying to packing 1.6.* on Windows to no success >>>> and then decided to just stick with 1.4.4. >>>> >>>> Problem is that the source code for the current MS-MPI builds does >>>> not seem to be publicly available, >>>> >>>> The problem with using MS-MPI is two fold: >>>> 1. I can't remember if its support MPIv2 API. I don't think so, but >>>> I may be wrong. >>>> 2. The license (at least when I checked) doesn't allow us to packing >>>> the dlls in our binaries. In other words, we would always have to >>>> have the user manually install using the installer distributed by MS. >>>> >>>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > Classification: UNCLASSIFIED > Caveats: FOUO > From mike.jackson at bluequartz.net Wed Aug 13 23:22:22 2014 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Wed, 13 Aug 2014 23:22:22 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> Message-ID: <3BB5F022-CCA0-400B-9FE0-8AF3E5315B49@bluequartz.net> The only 64 bit Qt 5.x binaries are for VS2013 if you plan on supporting 64 bit paraview by using the prebuilt Qt Binaries. So my vote would be for the newest/latest compiler if possible. Mike Jackson On Aug 13, 2014, at 10:07 AM, Utkarsh Ayachit wrote: > Good to know. I think we'll make the switch at the same time when we > upgrade the VS compiler we're using for the binaries. We are switching > to using CMakified Python soon and then we wouldn't need to use > VS2008. Any thoughts on which is the most common VS compiler? Qt > distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 > :). > > On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: >> Ahh, that may be, I wouldn't have noticed it since I have admin on my >> account. >> >> as far as the version of the standard implemented by MS MPI in HPC Pack 2012 >> (internal ver 256), it's 2.0. The TestSystemCaps regression test has the >> code to report. >> >> >> On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >>> >>> Additionally, you need to run the installer as admin since it installs >>> a daemon (I believe). I think it would make sense to put out two >>> version of Windows binaries (without MPI and with MS MPI) and then >>> include the MSMPI installer as a part of the installation process, >>> esp. since no other Windows MPI is officially supported any more. >>> >>> Something to think about for 4.3, not sure I want to make the plunge >>> for 4.2 -- but we'll keep the options open :). >>> >>> Utkarsh >>> >>> >>> >>> >>> >>> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>>> >>>> Hi Utkarsh, >>>> >>>> I think it does implement MPI2. At least my codes make heavy use of MPI 2 >>>> and it works fine. However, I'll look into it and report back. >>>> >>>> Microsoft's documentation says: >>>> >>>> You may also redistribute this MS-MPI installation package with your own >>>> applications, to facilitate having an application that can run on a >>>> stand-alone workstation and easily take advantage of an HPC Pack 2012 >>>> R2-based cluster. Please refer to the license agreement for additional >>>> details. >>>> >>>> >>>> Sounds like if you use an installer it could handle the dependency. >>>> >>>> Burlen >>>> >>>> >>>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>>> >>>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >>>> precisely because the support was dropped. >>>> >>>> That is correct. That's precisely why we've stuck with 1.4.4. I spent >>>> a lot of time trying to packing 1.6.* on Windows to no success and >>>> then decided to just stick with 1.4.4. >>>> >>>> Problem is that the source code for the current MS-MPI builds does not >>>> seem >>>> to be publicly available, >>>> >>>> The problem with using MS-MPI is two fold: >>>> 1. I can't remember if its support MPIv2 API. I don't think so, but I >>>> may be wrong. >>>> 2. The license (at least when I checked) doesn't allow us to packing >>>> the dlls in our binaries. In other words, we would always have to have >>>> the user manually install using the installer distributed by MS. >>>> >>>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From jeremy.santina at gmail.com Thu Aug 14 03:22:25 2014 From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=) Date: Thu, 14 Aug 2014 09:22:25 +0200 Subject: [Paraview] ParaView can't create the reader In-Reply-To: <53EA348C.9070808@bluecape.com.pt> References: <53E4FF9A.1020907@bluecape.com.pt> <53EA348C.9070808@bluecape.com.pt> Message-ID: Again, thank you. I am currently facing with some issues configuring MSVC 2008 Express in order to compile 64-bit applications. I will try to fix it. Best regards, J?r?my 2014-08-12 17:36 GMT+02:00 Bruno Santos : > First of all, your English looks pretty good! > > OK, let's see if I can address all of the issues: > > 1. Make sure you downloaded the 3 files that were needed for > installing Qt 4.8.2, namely the file "qt-win64-opensource-4.8.2-vs2008.exe" > and the two associated "*.bin" files. The 3 files should be placed in the > same folder before running the installer. > 2. In CMake, define the variable "QT_MAKE_EXECUTABLE" to use the path > "C:/Qt/4.8.2_x64/bin/qmake.exe" (adjust accordingly if necessary) and then > click on "Configure" once again. Hopefully it will now pick up everything > related to Qt. > 1. Mmm... still regarding this point, if you in fact gave the > correct path, it might not work properly if the Qt installation is somehow > incomplete. This happened to me when I tried to configure the project with > CMake, while I was still midway of the installation of Qt. > 2. Furthermore, there was a detail I forgot to write on the wiki > page, but when using MSVC 2008 Express, by default it does not provide the > ability to compile 64-bit applications. Instructions on how to do so can be > found online, for example here: > https://github.com/enGits/engrid/wiki/Configure-Microsoft-Visual-Studio-2008-Express-to-also-build-for-Windows-x64 > 3. And there is yet another import detail: when you configure the > project in CMake's GUI for the first time, it asks you which compiler to > use. Make sure you pick "Visual Studio 9 2008 Win64". If you pick the > standard non-Win64, it's natural that the 64-bit "qmake.exe" is > incompatible with the 32-bit Visual Studio build options. > 3. Regarding the files you've provided in attachment: > 1. The XML looks OK. I only have some experience with creating > these types of XML file, so I'm not yet able to point out any major flaws > without looking into ParaView's own XML filter/reader files. The complete > XML file I'm referring to is in the folder > "ParaViewCore\ServerManager\SMApplication\Resources" in ParaView's source > code. > 2. The "CMakeLists.txt" looks OK as well, but again, I don't have > enough experience on this. Only by trial and error would I be able to see > if your file is working properly. > 3. I suggest that you first try building the plug-in > "vtkPOFFReader", just to confirm if you have a working building > environment. This way it'll be easier to isolate the origin of any problems. > 4. "I have Visual C++ Express 2008 on my computer so is it normal > to get this message ?" > - Yes, it's normal. It happens to me as well and it works without any > problems. > 5. Due to how ParaView was built in this case, I think it's best to > use Qt 4.8.2 (namely with the respective architecture), just in case. I say > this because there are a lot of library dependencies that are automatically > configured and it might get a bit complicated to push aside the existing > dependencies on Qt. > > I hope I didn't miss anything. > > Best regards, > Bruno > > > On 11-08-2014 17:01, J?r?my Santina wrote: > > Thank you very much for your answer. > > I am sorry for my awful English and I hope you'll understand what I am > writing. > > I read the email you sent and I tried to build my reader following the > instructions provided here : > https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds > > First of all, I downloaded this archive : > ParaView-4.1.0-win64-complete_dev-r2.exe > > Then I installed Qt 4.8.2 from here : > https://code.google.com/p/qt-msvc-installer/. Finally when I am trying to > configure my reader with the CMake GUI, the QT_MAKE_EXECUTABLE can't be > found even if I select qmake.exe directly from the path. > > In fact I am a beginner and I don't really know how to use CMake. I > modified the CMakeLists.txt that I found here : > http://sourceforge.net/p/of-interfaces/code/HEAD/tree/trunk/vtkPOFFReader/ > but I am not sure about what I wrote. My CMakeLists file is joined with > this message. > > Besides, I noticed that when I am executing *qt-win64-opensource-4.8.2-vs2008.exe, > *a dialog box with the following message is opened : > > *A installation of Visual Studio 2008 was not found in the registry , > guessing path...* > > In spite of that, the installation seems to work perfectly fine but : I > have Visual C++ Express 2008 on my computer so is it normal to get this > message ? > > To finish, I would like to ask you one last question : > Given I didn't develop any GUI feature for my reader, do I still need QT ? > > I thank you again for your help. > > J?r?my > > > 2014-08-08 18:49 GMT+02:00 Bruno Santos : > >> Greetings J?r?my, >> >> If you had provided the XML file, it would have been a bit easier to >> diagnose this ourselves. >> Nonetheless, it seems to me that the issue is that the class/library >> "vtkPTecplotBinaryReader" is simply not loadable. A bit of searching online >> and in ParaView's source code leads me to believe that only the class >> "vtkTecplotReader" is available for loading through an XML only plug-in. >> >> If the class "vtkPTecplotBinaryReader" is a custom library you've >> built/created from source code, then have a look at a recent email I sent >> to this very same mailing list: >> http://public.kitware.com/pipermail/paraview/2014-August/031817.html >> >> Best regards, >> Bruno >> >> >> On 05-08-2014 15:48, J?r?my Santina wrote: >> >> Hello, >> >> I have written my own reader for ParaView and I am facing with some >> issues. >> >> My version of ParaView is 4.1 for Windows-64 bit and I didn't build it >> from sources. >> >> As the wiki >> >> describes, I wrote a Server Manager XML file. >> Then I set the environment flag PV_PLUGIN_DEBUG. >> >> Everything seems to work fine when I load the reader with Plugin Manager >> as the output messages dialog box indicates : >> >> *************************************************** >> >> Attempting to load >> C:\Users\Windows\Documents\Travail\ParaviewProject\VTKReaders\Plugin\TecplotBinaryReader.xml >> >> Loading XML plugin >> >> Plugin instance located successfully. Now loading components from the >> plugin instance based on the interfaces it implements. >> >> ---------------------------------------------------------------- >> >> Plugin Information: >> >> Name : TecplotBinaryReader >> >> Version : 1.0 >> >> ReqOnServer : 1 >> >> ReqOnClient : 0 >> >> ReqPlugins : >> >> ServerManager Plugin : Yes >> >> Python Plugin : No >> >> But when I try to open a file, ParaView crashes and I get the following >> error message : >> >> ERROR: In >> C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, >> line 307 >> >> vtkSISourceProxy (000000000B340ED0): Failed to create >> vtkPTecplotBinaryReader. Aborting for debugging purposes. >> >> >> What am I doing wrong ? >> >> >> Thanks in advance for your help. >> >> >> J?r?my >> >> >> >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcus.hanwell at kitware.com Thu Aug 14 16:19:15 2014 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Thu, 14 Aug 2014 16:19:15 -0400 Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32 and 64-bit In-Reply-To: <3BB5F022-CCA0-400B-9FE0-8AF3E5315B49@bluequartz.net> References: <53E226A9.8070002@bluecape.com.pt> <53E4F8F6.2060703@lbl.gov> <53E50208.3040306@bluecape.com.pt> <53E5150B.9030802@lbl.gov> <53E8F35A.3050600@lbl.gov> <53EAE08C.7080106@gmail.com> <3BB5F022-CCA0-400B-9FE0-8AF3E5315B49@bluequartz.net> Message-ID: If we want the newest/latest compiler we need to make sure everything in the superbuild will compile there too. It would be great to use the Qt and Python installers though if that was possible, it would even reduce the build time for our superbuilds. If we can, why not move to the latest compiler version available? Marcus On Wed, Aug 13, 2014 at 11:22 PM, Michael Jackson wrote: > The only 64 bit Qt 5.x binaries are for VS2013 if you plan on supporting 64 bit paraview by using the prebuilt Qt Binaries. So my vote would be for the newest/latest compiler if possible. > > Mike Jackson > > > On Aug 13, 2014, at 10:07 AM, Utkarsh Ayachit wrote: > >> Good to know. I think we'll make the switch at the same time when we >> upgrade the VS compiler we're using for the binaries. We are switching >> to using CMakified Python soon and then we wouldn't need to use >> VS2008. Any thoughts on which is the most common VS compiler? Qt >> distributes binaries for 2010, 2012, 2013. I suppose we can pick 2012 >> :). >> >> On Tue, Aug 12, 2014 at 11:50 PM, Burlen Loring wrote: >>> Ahh, that may be, I wouldn't have noticed it since I have admin on my >>> account. >>> >>> as far as the version of the standard implemented by MS MPI in HPC Pack 2012 >>> (internal ver 256), it's 2.0. The TestSystemCaps regression test has the >>> code to report. >>> >>> >>> On 8/11/2014 9:53 AM, Utkarsh Ayachit wrote: >>>> >>>> Additionally, you need to run the installer as admin since it installs >>>> a daemon (I believe). I think it would make sense to put out two >>>> version of Windows binaries (without MPI and with MS MPI) and then >>>> include the MSMPI installer as a part of the installation process, >>>> esp. since no other Windows MPI is officially supported any more. >>>> >>>> Something to think about for 4.3, not sure I want to make the plunge >>>> for 4.2 -- but we'll keep the options open :). >>>> >>>> Utkarsh >>>> >>>> >>>> >>>> >>>> >>>> On Mon, Aug 11, 2014 at 12:46 PM, Burlen Loring wrote: >>>>> >>>>> Hi Utkarsh, >>>>> >>>>> I think it does implement MPI2. At least my codes make heavy use of MPI 2 >>>>> and it works fine. However, I'll look into it and report back. >>>>> >>>>> Microsoft's documentation says: >>>>> >>>>> You may also redistribute this MS-MPI installation package with your own >>>>> applications, to facilitate having an application that can run on a >>>>> stand-alone workstation and easily take advantage of an HPC Pack 2012 >>>>> R2-based cluster. Please refer to the license agreement for additional >>>>> details. >>>>> >>>>> >>>>> Sounds like if you use an installer it could handle the dependency. >>>>> >>>>> Burlen >>>>> >>>>> >>>>> On 08/11/2014 08:03 AM, Utkarsh Ayachit wrote: >>>>> >>>>> The ParaView dev team switched from Open-MPI 1.6.2 backwards to 1.4.4, >>>>> precisely because the support was dropped. >>>>> >>>>> That is correct. That's precisely why we've stuck with 1.4.4. I spent >>>>> a lot of time trying to packing 1.6.* on Windows to no success and >>>>> then decided to just stick with 1.4.4. >>>>> >>>>> Problem is that the source code for the current MS-MPI builds does not >>>>> seem >>>>> to be publicly available, >>>>> >>>>> The problem with using MS-MPI is two fold: >>>>> 1. I can't remember if its support MPIv2 API. I don't think so, but I >>>>> may be wrong. >>>>> 2. The license (at least when I checked) doesn't allow us to packing >>>>> the dlls in our binaries. In other words, we would always have to have >>>>> the user manually install using the installer distributed by MS. >>>>> >>>>> 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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From marcus.hanwell at kitware.com Thu Aug 14 16:36:41 2014 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Thu, 14 Aug 2014 16:36:41 -0400 Subject: [Paraview] Volume focused application for materials STEM tomography Message-ID: Hi, We have been working on a branded ParaView-based application, called tomviz. The focus is on STEM tomography at atomic resolutions for materials, but it is also exploring how to make a focused application that enables visualization and analysis of volumes. http://www.tomviz.org/ We are developing out the concept of data processing in Python to enable researchers to easily develop new data analysis, reconstruction, and transformation techniques leveraging things like numpy. It was presented at M&M two weeks ago, and we will be adding some alignment and reconstruction capabilities in the next release. Thanks, Marcus From mvanmoer at illinois.edu Thu Aug 14 18:43:03 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Thu, 14 Aug 2014 22:43:03 +0000 Subject: [Paraview] Reader ctors called multiple times? In-Reply-To: References: <7F781841FF1E044388AFA42B70703A7A89EF4240@CHIMBX6.ad.uillinois.edu> <53DFFD4A.3050006@lbl.gov> Message-ID: <7F781841FF1E044388AFA42B70703A7A89EF6C12@CHIMBX6.ad.uillinois.edu> Thanks guys, I had to put this aside for a week. For the ?constructor being called three times case? there?re some things in the backtraces for the first two that might be it. The first has a call to vtkSMReaderFactory::GetReaders, also, both have calls to CanReadFile, but not from the plugin, from vtkSMReaderFactory. I should be seeing the plugin?s CanReadFile method, right? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Tuesday, August 05, 2014 10:02 AM To: Burlen Loring Cc: Vanmoer, Mark W; paraview Subject: Re: [Paraview] Reader ctors called multiple times? Burlen's got it right. I am curious why the plugin was only called once. Maybe there is no CanReadFile() or no file extension collision of something like that in one case but not the other? Mark: ProcessRequest() calls RDO(), RI(), and RD() (in that order) only after paraview creates the instance that it will actually use to read the file with. All are typically only called once, unless some parameter on the reader changes. If RD is called more often check to see if image based extents are mismatched. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Aug 4, 2014 at 5:38 PM, Burlen Loring > wrote: I thought it was twice. The first one ParaView when creates the reader to call CanReadFile in its search for potential readers of the file. The second one when it builds the pipeline. On 08/04/2014 02:31 PM, Vanmoer, Mark W wrote: Ah, is it because the exeutive?s ProcessRequest is doing all three of REQUEST_DATA, REQUEST_INFORMATION, and REQUEST_DATA_OBJECT ? From: Vanmoer, Mark W Sent: Monday, August 04, 2014 4:04 PM To: paraview Subject: Reader ctors called multiple times? Hello ParaView, I?ve inherited a project that writes plugins for ParaView 3.14.1, serial. While debugging I found out that the constructor for one of this project?s file readers is called 3 times when loading a file. I thought this was odd, so I tried setting a break point on vtkUnstructuredGridReader?s ctor and discovered that it?s called twice. However, a constructor for vtk source plugin that I wrote is only called once, as I would have guessed for the others. Is it normal for readers to have their constructors called multiple times when loading a file? Thanks, Mark _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From keerti.bhamidipati at us.af.mil Thu Aug 14 20:17:23 2014 From: keerti.bhamidipati at us.af.mil (BHAMIDIPATI, KEERTI K NH-03 USAF AFMC 812 TSS/ENTT) Date: Fri, 15 Aug 2014 00:17:23 +0000 Subject: [Paraview] How to run pvbatch on Windows Message-ID: <0D0AE069E87FC24F8A55D22C589C4A4F130827CD@52ZHTX-D03-03C.area52.afnoapps.usaf.mil> Apologies if this question was already asked. Has anyone successfully run pvbatch using one of the Kitware provided Paraview Windows binaries? I am using the Paraview 4.1.0 Kitware compiled binary on a Windows 7 64-bit computer. I would like to debug a script using pvbatch, before uploading it to the supercomputer to post-process. The following syntax seems to kind of work, but the 'mpirun' pop-up window closes before I can see whatever output is shown. Trying to run 'pvbatch' without using 'mpirun' results in a bunch of MPI errors even when the '--no-mpi' flag is specified. Command Syntax: 'C:\Program Files (x86)\ParaView 4.1.0\bin\pvbatch.exe' -np 2 'C:\Program Files (x86)\ParaView 4.1.0\bin\pvbatch.exe' .\script.py Thanks, Keerti From genet at biomed.ee.ethz.ch Fri Aug 15 11:22:55 2014 From: genet at biomed.ee.ethz.ch (Martin Genet) Date: Fri, 15 Aug 2014 17:22:55 +0200 Subject: [Paraview] RGB color coding Message-ID: <53EE25CF.4020203@biomed.ee.ethz.ch> Dear ParaView people, I have a vector field V defined on some mesh, and I am trying to color-code it following the scheme: - R = |V.x| - G = |V.y| - B = |V.z| Does that make sense? Is there a way to do so? Thanks! Martin From brady.aydelotte at gmail.com Fri Aug 15 11:27:22 2014 From: brady.aydelotte at gmail.com (brady.aydelotte) Date: Fri, 15 Aug 2014 11:27:22 -0400 Subject: [Paraview] Color Map issues with Labels and Title Text Placement Message-ID: The Color Map has Labels on the left and Annotations on the right and they can be edited using the "Edit Color Legend Parameters" popup menu. The Labels appear in user specified increments, but I they do not display the max and min values of the range, leaving ugly white space at the top and bottom of the color bar. Annotations can display the max and min, but they are on the right side of the color bar, making the whole color bar mess twice as wide. How can I get the max and min label values to be displayed on the same side as the labels and how can I do it on either side of the color bar? The title text at the top of the colorbar is always right justified. This forces the user to move the colorbar very far into the image if the colorbar is put on the right side. Is there an option for justification control of the title text? I am a novice Paraview user and my question pertains to using Paraview 4.1.0 64 bit on a Mac workstation. -- Thanks Brady Aydelotte -- Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may or may not contain sensitive and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. From cory.quammen at kitware.com Fri Aug 15 11:41:22 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 15 Aug 2014 11:41:22 -0400 Subject: [Paraview] Color Map issues with Labels and Title Text Placement In-Reply-To: References: Message-ID: Hi Brady, I think you will be happy to hear that the features you request are coming in ParaView 4.2. You can get them now by downloading the Nightly build of ParaView (selectable in the Version menu). Check out the new "Add Range Labels" and "Title Justification" options. Thanks, Cory On Fri, Aug 15, 2014 at 11:27 AM, brady.aydelotte wrote: > The Color Map has Labels on the left and Annotations on the right and > they can be edited using the "Edit Color Legend Parameters" popup > menu. The Labels appear in user specified increments, but I they do > not display the max and min values of the range, leaving ugly white > space at the top and bottom of the color bar. Annotations can display > the max and min, but they are on the right side of the color bar, > making the whole color bar mess twice as wide. How can I get the max > and min label values to be displayed on the same side as the labels > and how can I do it on either side of the color bar? > > The title text at the top of the colorbar is always right justified. > This forces the user to move the colorbar very far into the image if > the colorbar is put on the right side. Is there an option for > justification control of the title text? > > I am a novice Paraview user and my question pertains to using Paraview > 4.1.0 64 bit on a Mac workstation. > > > -- > Thanks > > Brady Aydelotte > > -- > Confidentiality Notice: This email message, including any > attachments, is for the sole use of the intended recipient(s) and may > or may not contain sensitive and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply email and destroy all copies of the original message. > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From dave.demarle at kitware.com Fri Aug 15 18:34:38 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 15 Aug 2014 18:34:38 -0400 Subject: [Paraview] RGB color coding In-Reply-To: <53EE25CF.4020203@biomed.ee.ethz.ch> References: <53EE25CF.4020203@biomed.ee.ethz.ch> Message-ID: I'ld use the python programmable filter. In the filter: copy the input across make a new three component wide unsigned char array and give it a name iterate over all the points (or cells) get the vector for the point (or cell) scale and bias each component down to 0..255 and store in the new array add the new array to the output point (or cell) array container see: http://www.paraview.org/Wiki/Python_Programmable_Filter for starter examples David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Aug 15, 2014 at 11:22 AM, Martin Genet wrote: > Dear ParaView people, > > I have a vector field V defined on some mesh, and I am trying to > color-code it following the scheme: > - R = |V.x| > - G = |V.y| > - B = |V.z| > Does that make sense? Is there a way to do so? Thanks! > > Martin > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ehsan.saei at gmail.com Mon Aug 18 05:52:49 2014 From: ehsan.saei at gmail.com (ehsan saei) Date: Mon, 18 Aug 2014 11:52:49 +0200 Subject: [Paraview] A Forward Connection Over two ssh Tunnel Message-ID: Hi all, I'm new to paraview. I try to run pvserver on a cluster. The problem is that I need to ssh twice to get access to the cluster. To use pvserver I submit a job on the cluster and then I run pvserver using the command "mpirun -np 12 pvserver" then I pick the name and port from terminal and use it in paraview client. but paraview can't find the pvserver. Is there any way to establish a connection via these two ssh tunnels? Thanks in advance, Ehsan -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.bilke at ufz.de Mon Aug 18 09:42:13 2014 From: lars.bilke at ufz.de (Lars Bilke) Date: Mon, 18 Aug 2014 15:42:13 +0200 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found Message-ID: Dear ParaView users, I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output: Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254 Non-app bundle in install directory not supported Error: Could not import vtkCommonComputationalGeometryPython Error: Could not import vtkRenderingCorePython Error: Cannot import vtkPVServerManagerDefaultPython Error: Cannot import vtkPVServerManagerRenderingPython Error: Cannot import vtkPVAnimationPython ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565 vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found. Traceback (most recent call last): File "", line 2, in File "Slice.py", line 73, in DoCoProcessing File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers self.CreatePipeline(datadescription) File "Slice.py", line 29, in CreatePipeline File "Slice.py", line 17, in _CreatePipeline File "Slice.py", line 23, in Pipeline File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter return self.RegisterWriter(writer, filename, freq) File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter writer, filename, freq) File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy proxy.GetProperty("Input").SetInputConnection( AttributeError: 'NoneType' object has no attribute ?GetProperty' Why is the writer proxy searched in the filters group? It should be in the writers group right? Thanks for your help! -------------- next part -------------- A non-text attachment was scrubbed... Name: manifest.json Type: application/json Size: 5282 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Slice.py Type: text/x-python-script Size: 3123 bytes Desc: not available URL: From andy.bauer at kitware.com Mon Aug 18 10:26:52 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 18 Aug 2014 10:26:52 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: Message-ID: Hi, I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work? Regards, Andy On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: > Dear ParaView users, > I have created a custom catalyst edition (see attached manifest). It is > basically the same as the Extras-edition with some parts removed. I have > integrated a catalyst adaptor into my application. Everything builds and > links fine. Now I want to use a python coprocessing pipeline (see attached > script). When running I get the following output: > > Generic Warning: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, > line 254 > Non-app bundle in install directory not supported > > Error: Could not import vtkCommonComputationalGeometryPython > Error: Could not import vtkRenderingCorePython > Error: Cannot import vtkPVServerManagerDefaultPython > Error: Cannot import vtkPVServerManagerRenderingPython > Error: Cannot import vtkPVAnimationPython > ERROR: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 565 > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: > group=filters and proxy=XMLPPolyDataWriter were found. > > Traceback (most recent call last): > File "", line 2, in > File "Slice.py", line 73, in DoCoProcessing > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 103, in UpdateProducers > self.CreatePipeline(datadescription) > File "Slice.py", line 29, in CreatePipeline > File "Slice.py", line 17, in _CreatePipeline > File "Slice.py", line 23, in Pipeline > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 280, in CreateWriter > return self.RegisterWriter(writer, filename, freq) > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 234, in RegisterWriter > writer, filename, freq) > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 252, in WriterParametersProxy > proxy.GetProperty("Input").SetInputConnection( > AttributeError: 'NoneType' object has no attribute ?GetProperty' > > > Why is the writer proxy searched in the filters group? It should be in the > writers group right? > > Thanks for your help! > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 18 10:28:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 10:28:44 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: Message-ID: Andy, I'll let you look into it, but I suspect it's due to the fact that catalyst needs to "tell" exactly where the py (and other ParaView shared libraries) are since the usual mechanism of determine their locations based on the location of the executable don't apply to Catalyst. Utkarsh On Mon, Aug 18, 2014 at 10:26 AM, Andy Bauer wrote: > Hi, > > I will look at this a bit more but I'm wondering if you tried doing the same > with just a full ParaView build and if you did, how did it work? > > Regards, > Andy > > > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: >> >> Dear ParaView users, >> I have created a custom catalyst edition (see attached manifest). It is >> basically the same as the Extras-edition with some parts removed. I have >> integrated a catalyst adaptor into my application. Everything builds and >> links fine. Now I want to use a python coprocessing pipeline (see attached >> script). When running I get the following output: >> >> Generic Warning: In >> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, >> line 254 >> Non-app bundle in install directory not supported >> >> Error: Could not import vtkCommonComputationalGeometryPython >> Error: Could not import vtkRenderingCorePython >> Error: Cannot import vtkPVServerManagerDefaultPython >> Error: Cannot import vtkPVServerManagerRenderingPython >> Error: Cannot import vtkPVAnimationPython >> ERROR: In >> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >> line 565 >> vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: >> group=filters and proxy=XMLPPolyDataWriter were found. >> >> Traceback (most recent call last): >> File "", line 2, in >> File "Slice.py", line 73, in DoCoProcessing >> File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 103, in UpdateProducers >> self.CreatePipeline(datadescription) >> File "Slice.py", line 29, in CreatePipeline >> File "Slice.py", line 17, in _CreatePipeline >> File "Slice.py", line 23, in Pipeline >> File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 280, in CreateWriter >> return self.RegisterWriter(writer, filename, freq) >> File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 234, in RegisterWriter >> writer, filename, freq) >> File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 252, in WriterParametersProxy >> proxy.GetProperty("Input").SetInputConnection( >> AttributeError: 'NoneType' object has no attribute ?GetProperty' >> >> >> Why is the writer proxy searched in the filters group? It should be in the >> writers group right? >> >> Thanks for your help! >> >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Mon Aug 18 10:29:29 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 10:29:29 -0400 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: Message-ID: This may be of help: http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding Utkarsh On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei wrote: > Hi all, > > I'm new to paraview. I try to run pvserver on a cluster. The problem is that > I need to ssh twice to get access to the cluster. To use pvserver I submit a > job on the cluster and then I run pvserver using the command > "mpirun -np 12 pvserver" > then I pick the name and port from terminal and use it in paraview client. > but paraview can't find the pvserver. Is there any way to establish a > connection via these two ssh tunnels? > > Thanks in advance, > Ehsan > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Mon Aug 18 11:18:51 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 11:18:51 -0400 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: Message-ID: It does boil down to using reverse connection and setting up recursive tunnels so that the pvserver and tunnel back to the client. See the following on the need for portfwd and how it could potentially be helpful here. http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei wrote: > Dear Utkarsh, > Thanks for your respond. I tried the section : " A forward connection over > an ssh tunnel " > but it doesn't work. The problem is that I have to ssh to one system and > then ssh to the cluster again and finally I can submit a job. Do you have > any other suggestions? > > thanks in advance, > Ehsan > > > On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit > wrote: >> >> This may be of help: >> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >> >> Utkarsh >> >> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei wrote: >> > Hi all, >> > >> > I'm new to paraview. I try to run pvserver on a cluster. The problem is >> > that >> > I need to ssh twice to get access to the cluster. To use pvserver I >> > submit a >> > job on the cluster and then I run pvserver using the command >> > "mpirun -np 12 pvserver" >> > then I pick the name and port from terminal and use it in paraview >> > client. >> > but paraview can't find the pvserver. Is there any way to establish a >> > connection via these two ssh tunnels? >> > >> > Thanks in advance, >> > Ehsan >> > >> > _______________________________________________ >> > 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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > From bloring at lbl.gov Mon Aug 18 12:37:45 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 18 Aug 2014 09:37:45 -0700 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: Message-ID: <53F22BD9.1020207@lbl.gov> Hi Ehsan, As Utkarsh says you need to use a reverse connection. I suggest ncat instead of portfwd because portfwd is a long dead project with no support and it's failed to compile on some systems I used. Here's a schematic of the setup [work station] [ login node ] [ compute node ] [ paraview ]<-- ssh -R --<[ ncat+ncat-l]<-----[ pvserver -rc ] in more detail: in your pvsc on the client ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... on the login node in a shell script referenced by the client's pvsc: let LOGIN_PORT=${PORT}+1 ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & qsub ... on the compute nodein your batch script mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} --server-port ${LOGIN_PORT} ... You could skip ncat if you have control over the sshd config, you need to enable GatewayPorts. Burlen On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: > It does boil down to using reverse connection and setting up recursive > tunnels so that the pvserver and tunnel back to the client. See the > following on the need for portfwd and how it could potentially be > helpful here. > > http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd > > On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei wrote: >> Dear Utkarsh, >> Thanks for your respond. I tried the section : " A forward connection over >> an ssh tunnel " >> but it doesn't work. The problem is that I have to ssh to one system and >> then ssh to the cluster again and finally I can submit a job. Do you have >> any other suggestions? >> >> thanks in advance, >> Ehsan >> >> >> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >> wrote: >>> This may be of help: >>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>> >>> Utkarsh >>> >>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei wrote: >>>> Hi all, >>>> >>>> I'm new to paraview. I try to run pvserver on a cluster. The problem is >>>> that >>>> I need to ssh twice to get access to the cluster. To use pvserver I >>>> submit a >>>> job on the cluster and then I run pvserver using the command >>>> "mpirun -np 12 pvserver" >>>> then I pick the name and port from terminal and use it in paraview >>>> client. >>>> but paraview can't find the pvserver. Is there any way to establish a >>>> connection via these two ssh tunnels? >>>> >>>> Thanks in advance, >>>> Ehsan >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Eliot at awe.co.uk Mon Aug 18 12:58:48 2014 From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk) Date: Mon, 18 Aug 2014 16:58:48 +0000 Subject: [Paraview] Error on server disconnect Message-ID: <201408181658.s7IGwnVJ013827@msw2.awe.co.uk> Good afternoon all, I have built ParaView 4.1.0 using Superbuild. During testing I noticed that if the Server Connection is highlighted in the Pipeline Browser when I click Disconnect, I see four error messages in the Output Messages window like that shown below: ERROR: In /paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 832 vtkPVSessionCore (0x666320): No object with global-id: 33157 I do not see these error messages if the server is not highlighted in the Pipeline browser during disconnection. I am building on Linux using gcc 4.5.2 and mpich2 1.2.1. I am launching the server on localhost using: mpirun -n 8 -envall /pvserver --server-port=11111 --use-offscreen-rendering I have tested this in 4.0.1 and error messages are not displayed. Is this a problem with my build? Has anyone else seen this issue? Is this a bug in ParaView? Kind regards, Jim Jim Eliot High Performance Computing Group AWE, Aldermaston, Reading, RG7 4PR ___________________________________________________ ____________________________ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.bilke at ufz.de Mon Aug 18 14:22:07 2014 From: lars.bilke at ufz.de (Lars Bilke) Date: Mon, 18 Aug 2014 20:22:07 +0200 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: Message-ID: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Hi Andy, thanks for looking into it. I further noticed that the same error occurs when I use the official Extras-edition (plus Enable-Python). When using the Rendering-Base-Python edition everything works. Best, Lars Am 18.08.2014 um 16:26 schrieb Andy Bauer : > Hi, > > I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work? > > Regards, > Andy > > > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: > Dear ParaView users, > I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output: > > Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254 > Non-app bundle in install directory not supported > > Error: Could not import vtkCommonComputationalGeometryPython > Error: Could not import vtkRenderingCorePython > Error: Cannot import vtkPVServerManagerDefaultPython > Error: Cannot import vtkPVServerManagerRenderingPython > Error: Cannot import vtkPVAnimationPython > ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565 > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found. > > Traceback (most recent call last): > File "", line 2, in > File "Slice.py", line 73, in DoCoProcessing > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers > self.CreatePipeline(datadescription) > File "Slice.py", line 29, in CreatePipeline > File "Slice.py", line 17, in _CreatePipeline > File "Slice.py", line 23, in Pipeline > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter > return self.RegisterWriter(writer, filename, freq) > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter > writer, filename, freq) > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy > proxy.GetProperty("Input").SetInputConnection( > AttributeError: 'NoneType' object has no attribute ?GetProperty' > > > Why is the writer proxy searched in the filters group? It should be in the writers group right? > > Thanks for your help! > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From wascott at sandia.gov Mon Aug 18 14:38:30 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 18 Aug 2014 18:38:30 +0000 Subject: [Paraview] [EXTERNAL] Error on server disconnect In-Reply-To: <201408181658.s7IGwnVJ013827@msw2.awe.co.uk> References: <201408181658.s7IGwnVJ013827@msw2.awe.co.uk> Message-ID: Thanks Jim - I wrote it up. It is bug 14950. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jim.Eliot at awe.co.uk Sent: Monday, August 18, 2014 10:59 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Error on server disconnect Good afternoon all, I have built ParaView 4.1.0 using Superbuild. During testing I noticed that if the Server Connection is highlighted in the Pipeline Browser when I click Disconnect, I see four error messages in the Output Messages window like that shown below: ERROR: In /paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 832 vtkPVSessionCore (0x666320): No object with global-id: 33157 I do not see these error messages if the server is not highlighted in the Pipeline browser during disconnection. I am building on Linux using gcc 4.5.2 and mpich2 1.2.1. I am launching the server on localhost using: mpirun -n 8 -envall /pvserver --server-port=11111 --use-offscreen-rendering I have tested this in 4.0.1 and error messages are not displayed. Is this a problem with my build? Has anyone else seen this issue? Is this a bug in ParaView? Kind regards, Jim Jim Eliot High Performance Computing Group AWE, Aldermaston, Reading, RG7 4PR ___________________________________________________ ____________________________ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Aug 18 14:39:40 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 18 Aug 2014 14:39:40 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Lars, When you run pvpython can you create the XMLPPolyDataWriter ? To test this just do: from paraview.simple import * w = XMLPPolyDataWriter() The safest way to test this stuff is to try it with a "normal" ParaView build with MPI and Python enabled. If you can link and run against this then it has to do with your edition which you can then check on issues by using pvpython. We don't do a lot of testing on the generated Catalyst editions yet so it's possible that something snuck in to them. Also, what version of ParaView are you using? Andy On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke wrote: > Hi Andy, > > thanks for looking into it. > > I further noticed that the same error occurs when I use the official > Extras-edition (plus Enable-Python). When using the Rendering-Base-Python > edition everything works. > > Best, > Lars > > Am 18.08.2014 um 16:26 schrieb Andy Bauer : > > > Hi, > > > > I will look at this a bit more but I'm wondering if you tried doing the > same with just a full ParaView build and if you did, how did it work? > > > > Regards, > > Andy > > > > > > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: > > Dear ParaView users, > > I have created a custom catalyst edition (see attached manifest). It is > basically the same as the Extras-edition with some parts removed. I have > integrated a catalyst adaptor into my application. Everything builds and > links fine. Now I want to use a python coprocessing pipeline (see attached > script). When running I get the following output: > > > > Generic Warning: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, > line 254 > > Non-app bundle in install directory not supported > > > > Error: Could not import vtkCommonComputationalGeometryPython > > Error: Could not import vtkRenderingCorePython > > Error: Cannot import vtkPVServerManagerDefaultPython > > Error: Cannot import vtkPVServerManagerRenderingPython > > Error: Cannot import vtkPVAnimationPython > > ERROR: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 565 > > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: > group=filters and proxy=XMLPPolyDataWriter were found. > > > > Traceback (most recent call last): > > File "", line 2, in > > File "Slice.py", line 73, in DoCoProcessing > > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 103, in UpdateProducers > > self.CreatePipeline(datadescription) > > File "Slice.py", line 29, in CreatePipeline > > File "Slice.py", line 17, in _CreatePipeline > > File "Slice.py", line 23, in Pipeline > > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 280, in CreateWriter > > return self.RegisterWriter(writer, filename, freq) > > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 234, in RegisterWriter > > writer, filename, freq) > > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 252, in WriterParametersProxy > > proxy.GetProperty("Input").SetInputConnection( > > AttributeError: 'NoneType' object has no attribute ?GetProperty' > > > > > > Why is the writer proxy searched in the filters group? It should be in > the writers group right? > > > > Thanks for your help! > > > > > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 18 16:36:31 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 16:36:31 -0400 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: <53F22BD9.1020207@lbl.gov> References: <53F22BD9.1020207@lbl.gov> Message-ID: Burlen, Very cool. When you get the chance, mind updating the Wiki? Thanks Utkarsh On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: > Hi Ehsan, > > As Utkarsh says you need to use a reverse connection. I suggest ncat instead > of portfwd because portfwd is a long dead project with no support and it's > failed to compile on some systems I used. Here's a schematic of the setup > > [work station] [ login node ] [ compute node ] > [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] > > in more detail: > in your pvsc on the client > ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... > > on the login node in a shell script referenced by the client's pvsc: > let LOGIN_PORT=${PORT}+1 > ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & > qsub ... > > on the compute node in your batch script > mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} > --server-port ${LOGIN_PORT} ... > > You could skip ncat if you have control over the sshd config, you need to > enable GatewayPorts. > > Burlen > > > On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: > > It does boil down to using reverse connection and setting up recursive > tunnels so that the pvserver and tunnel back to the client. See the > following on the need for portfwd and how it could potentially be > helpful here. > > http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd > > On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei wrote: > > Dear Utkarsh, > Thanks for your respond. I tried the section : " A forward connection over > an ssh tunnel " > but it doesn't work. The problem is that I have to ssh to one system and > then ssh to the cluster again and finally I can submit a job. Do you have > any other suggestions? > > thanks in advance, > Ehsan > > > On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit > wrote: > > This may be of help: > http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding > > Utkarsh > > On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei wrote: > > Hi all, > > I'm new to paraview. I try to run pvserver on a cluster. The problem is > that > I need to ssh twice to get access to the cluster. To use pvserver I > submit a > job on the cluster and then I run pvserver using the command > "mpirun -np 12 pvserver" > then I pick the name and port from terminal and use it in paraview > client. > but paraview can't find the pvserver. Is there any way to establish a > connection via these two ssh tunnels? > > Thanks in advance, > Ehsan > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From burlen.loring at gmail.com Mon Aug 18 16:43:45 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Mon, 18 Aug 2014 13:43:45 -0700 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: <53F22BD9.1020207@lbl.gov> Message-ID: <53F26581.3080008@gmail.com> Hi Utkarsh, Sure I can do that. Burlen On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: > Burlen, > > Very cool. When you get the chance, mind updating the Wiki? > > Thanks > Utkarsh > > On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: >> Hi Ehsan, >> >> As Utkarsh says you need to use a reverse connection. I suggest ncat instead >> of portfwd because portfwd is a long dead project with no support and it's >> failed to compile on some systems I used. Here's a schematic of the setup >> >> [work station] [ login node ] [ compute node ] >> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >> >> in more detail: >> in your pvsc on the client >> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >> >> on the login node in a shell script referenced by the client's pvsc: >> let LOGIN_PORT=${PORT}+1 >> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & >> qsub ... >> >> on the compute node in your batch script >> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >> --server-port ${LOGIN_PORT} ... >> >> You could skip ncat if you have control over the sshd config, you need to >> enable GatewayPorts. >> >> Burlen >> >> >> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >> >> It does boil down to using reverse connection and setting up recursive >> tunnels so that the pvserver and tunnel back to the client. See the >> following on the need for portfwd and how it could potentially be >> helpful here. >> >> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >> >> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei wrote: >> >> Dear Utkarsh, >> Thanks for your respond. I tried the section : " A forward connection over >> an ssh tunnel " >> but it doesn't work. The problem is that I have to ssh to one system and >> then ssh to the cluster again and finally I can submit a job. Do you have >> any other suggestions? >> >> thanks in advance, >> Ehsan >> >> >> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >> wrote: >> >> This may be of help: >> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >> >> Utkarsh >> >> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei wrote: >> >> Hi all, >> >> I'm new to paraview. I try to run pvserver on a cluster. The problem is >> that >> I need to ssh twice to get access to the cluster. To use pvserver I >> submit a >> job on the cluster and then I run pvserver using the command >> "mpirun -np 12 pvserver" >> then I pick the name and port from terminal and use it in paraview >> client. >> but paraview can't find the pvserver. Is there any way to establish a >> connection via these two ssh tunnels? >> >> Thanks in advance, >> Ehsan >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From a.huebl at hzdr.de Mon Aug 18 18:12:27 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Tue, 19 Aug 2014 00:12:27 +0200 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: <53F26581.3080008@gmail.com> References: <53F22BD9.1020207@lbl.gov> <53F26581.3080008@gmail.com> Message-ID: <53F27A4B.2010907@hzdr.de> Dear Ehsan, I use a similar setup as Burlen, tunneling twice over a login node to our cluster's head node. It also needs `GatewayPorts clientspecified` in the head node's sshd_config to work with maximum comfort. Feel free to check our wiki: https://github.com/ComputationalRadiationPhysics/picongpu/wiki/ParaView Best, Axel On 18.08.2014 22:43, Burlen Loring wrote: > Hi Utkarsh, > > Sure I can do that. > > Burlen > > On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: >> Burlen, >> >> Very cool. When you get the chance, mind updating the Wiki? >> >> Thanks >> Utkarsh >> >> On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: >>> Hi Ehsan, >>> >>> As Utkarsh says you need to use a reverse connection. I suggest ncat >>> instead >>> of portfwd because portfwd is a long dead project with no support and >>> it's >>> failed to compile on some systems I used. Here's a schematic of the >>> setup >>> >>> [work station] [ login node ] [ compute node ] >>> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >>> >>> in more detail: >>> in your pvsc on the client >>> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >>> >>> on the login node in a shell script referenced by the client's pvsc: >>> let LOGIN_PORT=${PORT}+1 >>> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & >>> qsub ... >>> >>> on the compute node in your batch script >>> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >>> --server-port ${LOGIN_PORT} ... >>> >>> You could skip ncat if you have control over the sshd config, you >>> need to >>> enable GatewayPorts. >>> >>> Burlen >>> >>> >>> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >>> >>> It does boil down to using reverse connection and setting up recursive >>> tunnels so that the pvserver and tunnel back to the client. See the >>> following on the need for portfwd and how it could potentially be >>> helpful here. >>> >>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >>> >>> >>> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei >>> wrote: >>> >>> Dear Utkarsh, >>> Thanks for your respond. I tried the section : " A forward connection >>> over >>> an ssh tunnel " >>> but it doesn't work. The problem is that I have to ssh to one system and >>> then ssh to the cluster again and finally I can submit a job. Do you >>> have >>> any other suggestions? >>> >>> thanks in advance, >>> Ehsan >>> >>> >>> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >>> wrote: >>> >>> This may be of help: >>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>> >>> Utkarsh >>> >>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei >>> wrote: >>> >>> Hi all, >>> >>> I'm new to paraview. I try to run pvserver on a cluster. The problem is >>> that >>> I need to ssh twice to get access to the cluster. To use pvserver I >>> submit a >>> job on the cluster and then I run pvserver using the command >>> "mpirun -np 12 pvserver" >>> then I pick the name and port from terminal and use it in paraview >>> client. >>> but paraview can't find the pvserver. Is there any way to establish a >>> connection via these two ssh tunnels? >>> >>> Thanks in advance, >>> Ehsan >>> >>> _______________________________________________ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5002 bytes Desc: S/MIME Cryptographic Signature URL: From utkarsh.ayachit at kitware.com Mon Aug 18 23:56:47 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 23:56:47 -0400 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: <53F27A4B.2010907@hzdr.de> References: <53F22BD9.1020207@lbl.gov> <53F26581.3080008@gmail.com> <53F27A4B.2010907@hzdr.de> Message-ID: Very cool! Thanks for sharing, Axel. It will be nice to link this page from the Wiki as a reference/example, if that's okay. Utkarsh On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: > Dear Ehsan, > > I use a similar setup as Burlen, tunneling twice over a login node to > our cluster's head node. > > It also needs `GatewayPorts clientspecified` in the head node's > sshd_config to work with maximum comfort. > Feel free to check our wiki: > > https://github.com/ComputationalRadiationPhysics/picongpu/wiki/ParaView > > Best, > Axel > > On 18.08.2014 22:43, Burlen Loring wrote: >> Hi Utkarsh, >> >> Sure I can do that. >> >> Burlen >> >> On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: >>> Burlen, >>> >>> Very cool. When you get the chance, mind updating the Wiki? >>> >>> Thanks >>> Utkarsh >>> >>> On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: >>>> Hi Ehsan, >>>> >>>> As Utkarsh says you need to use a reverse connection. I suggest ncat >>>> instead >>>> of portfwd because portfwd is a long dead project with no support and >>>> it's >>>> failed to compile on some systems I used. Here's a schematic of the >>>> setup >>>> >>>> [work station] [ login node ] [ compute node ] >>>> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >>>> >>>> in more detail: >>>> in your pvsc on the client >>>> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >>>> >>>> on the login node in a shell script referenced by the client's pvsc: >>>> let LOGIN_PORT=${PORT}+1 >>>> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & >>>> qsub ... >>>> >>>> on the compute node in your batch script >>>> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >>>> --server-port ${LOGIN_PORT} ... >>>> >>>> You could skip ncat if you have control over the sshd config, you >>>> need to >>>> enable GatewayPorts. >>>> >>>> Burlen >>>> >>>> >>>> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >>>> >>>> It does boil down to using reverse connection and setting up recursive >>>> tunnels so that the pvserver and tunnel back to the client. See the >>>> following on the need for portfwd and how it could potentially be >>>> helpful here. >>>> >>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >>>> >>>> >>>> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei >>>> wrote: >>>> >>>> Dear Utkarsh, >>>> Thanks for your respond. I tried the section : " A forward connection >>>> over >>>> an ssh tunnel " >>>> but it doesn't work. The problem is that I have to ssh to one system and >>>> then ssh to the cluster again and finally I can submit a job. Do you >>>> have >>>> any other suggestions? >>>> >>>> thanks in advance, >>>> Ehsan >>>> >>>> >>>> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >>>> wrote: >>>> >>>> This may be of help: >>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>>> >>>> Utkarsh >>>> >>>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei >>>> wrote: >>>> >>>> Hi all, >>>> >>>> I'm new to paraview. I try to run pvserver on a cluster. The problem is >>>> that >>>> I need to ssh twice to get access to the cluster. To use pvserver I >>>> submit a >>>> job on the cluster and then I run pvserver using the command >>>> "mpirun -np 12 pvserver" >>>> then I pick the name and port from terminal and use it in paraview >>>> client. >>>> but paraview can't find the pvserver. Is there any way to establish a >>>> connection via these two ssh tunnels? >>>> >>>> Thanks in advance, >>>> Ehsan >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > -- > > Axel Huebl > Diploma Student > Phone +49 351 260 3582 > https://www.hzdr.de/crp > Computational Radiation Physics > Laser Particle Acceleration Division > Helmholtz-Zentrum Dresden - Rossendorf e.V. > > Bautzner Landstrasse 400, 01328 Dresden > POB 510119, D-01314 Dresden > Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey > Prof. Dr.Dr.h.c. P. Joehnk > VR 1693 beim Amtsgericht Dresden > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From lars.bilke at ufz.de Tue Aug 19 03:02:34 2014 From: lars.bilke at ufz.de (Lars Bilke) Date: Tue, 19 Aug 2014 09:02:34 +0200 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Andy, I can create XMLPPolyDataWriter in pvpython without errors. With a normal ParaView build as well as with the Rendering-Base-Python edition it works but I wanted to have a small custom edition. I am using the next branch from yesterday (79f7fdc). Best, Lars Am 18.08.2014 um 20:39 schrieb Andy Bauer : > Hi Lars, > > When you run pvpython can you create the XMLPPolyDataWriter ? > > To test this just do: > from paraview.simple import * > w = XMLPPolyDataWriter() > > The safest way to test this stuff is to try it with a "normal" ParaView build with MPI and Python enabled. If you can link and run against this then it has to do with your edition which you can then check on issues by using pvpython. We don't do a lot of testing on the generated Catalyst editions yet so it's possible that something snuck in to them. > > Also, what version of ParaView are you using? > > Andy > > > > > On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke wrote: > Hi Andy, > > thanks for looking into it. > > I further noticed that the same error occurs when I use the official Extras-edition (plus Enable-Python). When using the Rendering-Base-Python edition everything works. > > Best, > Lars > > Am 18.08.2014 um 16:26 schrieb Andy Bauer : > > > Hi, > > > > I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work? > > > > Regards, > > Andy > > > > > > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: > > Dear ParaView users, > > I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output: > > > > Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254 > > Non-app bundle in install directory not supported > > > > Error: Could not import vtkCommonComputationalGeometryPython > > Error: Could not import vtkRenderingCorePython > > Error: Cannot import vtkPVServerManagerDefaultPython > > Error: Cannot import vtkPVServerManagerRenderingPython > > Error: Cannot import vtkPVAnimationPython > > ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565 > > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found. > > > > Traceback (most recent call last): > > File "", line 2, in > > File "Slice.py", line 73, in DoCoProcessing > > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers > > self.CreatePipeline(datadescription) > > File "Slice.py", line 29, in CreatePipeline > > File "Slice.py", line 17, in _CreatePipeline > > File "Slice.py", line 23, in Pipeline > > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter > > return self.RegisterWriter(writer, filename, freq) > > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter > > writer, filename, freq) > > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy > > proxy.GetProperty("Input").SetInputConnection( > > AttributeError: 'NoneType' object has no attribute ?GetProperty' > > > > > > Why is the writer proxy searched in the filters group? It should be in the writers group right? > > > > Thanks for your help! > > > > > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > From Patrick.Begou at legi.grenoble-inp.fr Tue Aug 19 03:28:33 2014 From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou) Date: Tue, 19 Aug 2014 09:28:33 +0200 Subject: [Paraview] [SOLVED] Paraview 3.98, Pvserver and Intel graphic HD 4600 In-Reply-To: <53CE1E22.80008@legi.grenoble-inp.fr> References: <53CE1E22.80008@legi.grenoble-inp.fr> Message-ID: <53F2FCA1.3060709@legi.grenoble-inp.fr> I just wont to give a feedback about this problem and how I solved it: I've donwloaded and installed more recent versions: Mesa-10.2.2 (MesaLib-10.2.2.tar.gz) and ParaView-v4.1.0 (ParaView-v4.1.0-source.tar.gz) It has requested an update of llvm on my server: llvm-devel-3.4-10.el6.x86_64 llvm-libs-3.4-10.el6.x86_64.rpm llvm-3.4-10.el6.x86_64.rpm I've build Mesa-10.2.2 with: ./configure CXXFLAGS="-O3 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" CFLAGS="-O3 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" --disable-xvmc --disable-glx --disable-dri --with-dri-drivers="" --with-gallium-drivers="swrast" --enable-texture-float --disable-shared-glapi --disable-egl --with-egl-platforms="" --enable-gallium-osmesa --enable-gallium-llvm=yes --prefix=/share/apps/osmesa-10-2-2-GCC48 gmake su make install I've build a recent ffmpeg: tar xvfz ffmpeg-2.3.tar.gz cd ffmpeg-2.3 ./configure --prefix=/share/apps/ffmpeg-2.3-GCC48 --enable-nonfree --enable-shared --disable-avx --disable-yasm make su make install Then I've build ParaView-v4.1.0 with tar xvfz ParaView-v4.1.0-source.tar.gz cd ParaView-v4.1.0 mkdir build cd build ccmake28 -Wno-dev -DQT_QMAKE_EXECUTABLE=/share/apps/qt4.8.8/bin/qmake \ -DCMAKE_BUILD_TYPE=release \ -DCMAKE_INSTALL_PREFIX=/share/apps/paraView-server-4.1.0 \ -DPARAVIEW_USE_MPI=ON \ -DPARAVIEW_ENABLE_PYTHON=ON \ -DVTK_USE_LARGE_DATA=ON \ -DPARAVIEW_ENABLE_FFMPEG=ON \ -DCMAKE_VERBOSE_MAKEFILE=ON \ -DOPENGL_INCLUDE_DIR=/share/apps/osmesa-10-2-2-GCC48/include \ -DVTK_OPENGL_HAS_OSMESA=ON \ -DVTK_USE_X=OFF \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DOPENGL_gl_LIBRARY="" \ -DOSMESA_LIBRARY=/share/apps/osmesa-10-2-2-GCC48/lib/libOSMesa.so \ -DFFMPEG_INCLUDE_DIR=/share/apps/ffmpeg-2.3-GCC48/include \ -DFFMPEG_avcodec_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavcodec.so \ -DFFMPEG_avformat_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavformat.so \ -DFFMPEG_avutil_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavutil.so \ -DFFMPEG_swscale_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libswscale.so \ -DXDMF_USE_BZIP2=ON \ -DXDMF_USE_GZIP=ON \ -DCMAKE_SHARED_LINKER_FLAGS_RELEASE="-lz"\ -DCMAKE_EXE_LINKER_FLAGS_RELEASE="-Wl,-rpath,/share/apps/ffmpeg-2.3-GCC48/lib -lz" \ -DCMAKE_MODULE_LINKER_FLAGS=-ldl \ -DCMAKE_SHARED_LINKER_FLAGS=-ldl \ .. make su make install System is Rocks Cluster 6.1 (Emerald Boa). Thanks all for your answers on this very strange problem, may be more mesa related than Paraview. Patrick -- =================================================================== | Equipe M.O.S.T. | | | Patrick BEGOU | mailto:Patrick.Begou at grenoble-inp.fr | | LEGI | | | BP 53 X | Tel 04 76 82 51 35 | | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 | =================================================================== From utkarsh.ayachit at kitware.com Tue Aug 19 09:47:15 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 19 Aug 2014 09:47:15 -0400 Subject: [Paraview] [SOLVED] Paraview 3.98, Pvserver and Intel graphic HD 4600 In-Reply-To: <53F2FCA1.3060709@legi.grenoble-inp.fr> References: <53CE1E22.80008@legi.grenoble-inp.fr> <53F2FCA1.3060709@legi.grenoble-inp.fr> Message-ID: Thanks for posting back. Highly appreciated. Utkarsh On Tue, Aug 19, 2014 at 3:28 AM, Patrick Begou wrote: > I just wont to give a feedback about this problem and how I solved it: I've > donwloaded and installed more recent versions: > Mesa-10.2.2 (MesaLib-10.2.2.tar.gz) and ParaView-v4.1.0 > (ParaView-v4.1.0-source.tar.gz) > > It has requested an update of llvm on my server: > llvm-devel-3.4-10.el6.x86_64 > llvm-libs-3.4-10.el6.x86_64.rpm > llvm-3.4-10.el6.x86_64.rpm > > I've build Mesa-10.2.2 with: > ./configure CXXFLAGS="-O3 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" CFLAGS="-O3 > -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" --disable-xvmc --disable-glx > --disable-dri --with-dri-drivers="" --with-gallium-drivers="swrast" > --enable-texture-float --disable-shared-glapi --disable-egl > --with-egl-platforms="" --enable-gallium-osmesa --enable-gallium-llvm=yes > --prefix=/share/apps/osmesa-10-2-2-GCC48 > gmake > su > make install > > I've build a recent ffmpeg: > tar xvfz ffmpeg-2.3.tar.gz > cd ffmpeg-2.3 > ./configure --prefix=/share/apps/ffmpeg-2.3-GCC48 --enable-nonfree > --enable-shared --disable-avx --disable-yasm > make > su > make install > > Then I've build ParaView-v4.1.0 with > tar xvfz ParaView-v4.1.0-source.tar.gz > cd ParaView-v4.1.0 > mkdir build > cd build > ccmake28 -Wno-dev -DQT_QMAKE_EXECUTABLE=/share/apps/qt4.8.8/bin/qmake \ > -DCMAKE_BUILD_TYPE=release \ > -DCMAKE_INSTALL_PREFIX=/share/apps/paraView-server-4.1.0 \ > -DPARAVIEW_USE_MPI=ON \ > -DPARAVIEW_ENABLE_PYTHON=ON \ > -DVTK_USE_LARGE_DATA=ON \ > -DPARAVIEW_ENABLE_FFMPEG=ON \ > -DCMAKE_VERBOSE_MAKEFILE=ON \ > -DOPENGL_INCLUDE_DIR=/share/apps/osmesa-10-2-2-GCC48/include \ > -DVTK_OPENGL_HAS_OSMESA=ON \ > -DVTK_USE_X=OFF \ > -DPARAVIEW_BUILD_QT_GUI=OFF \ > -DOPENGL_gl_LIBRARY="" \ > -DOSMESA_LIBRARY=/share/apps/osmesa-10-2-2-GCC48/lib/libOSMesa.so \ > -DFFMPEG_INCLUDE_DIR=/share/apps/ffmpeg-2.3-GCC48/include \ > -DFFMPEG_avcodec_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavcodec.so \ > -DFFMPEG_avformat_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavformat.so \ > -DFFMPEG_avutil_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libavutil.so \ > -DFFMPEG_swscale_LIBRARY=/share/apps/ffmpeg-2.3-GCC48/lib/libswscale.so \ > -DXDMF_USE_BZIP2=ON \ > -DXDMF_USE_GZIP=ON \ > -DCMAKE_SHARED_LINKER_FLAGS_RELEASE="-lz"\ > > -DCMAKE_EXE_LINKER_FLAGS_RELEASE="-Wl,-rpath,/share/apps/ffmpeg-2.3-GCC48/lib > -lz" \ > -DCMAKE_MODULE_LINKER_FLAGS=-ldl \ > -DCMAKE_SHARED_LINKER_FLAGS=-ldl \ > .. > make > su > make install > > System is Rocks Cluster 6.1 (Emerald Boa). > > Thanks all for your answers on this very strange problem, may be more mesa > related than Paraview. > > > Patrick > > -- > =================================================================== > | Equipe M.O.S.T. | | > | Patrick BEGOU | mailto:Patrick.Begou at grenoble-inp.fr | > | LEGI | | > | BP 53 X | Tel 04 76 82 51 35 | > | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 | > =================================================================== > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Aug 19 10:08:43 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 19 Aug 2014 10:08:43 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Yup, this indeed points to the issue I was alluding do. Andy, feel free to stop by if you need more info. Utkarsh On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote: > Hi Andy, > > I can create XMLPPolyDataWriter in pvpython without errors. With a normal ParaView build as well as with the Rendering-Base-Python edition it works but I wanted to have a small custom edition. > > I am using the next branch from yesterday (79f7fdc). > > Best, > Lars > > Am 18.08.2014 um 20:39 schrieb Andy Bauer : > >> Hi Lars, >> >> When you run pvpython can you create the XMLPPolyDataWriter ? >> >> To test this just do: >> from paraview.simple import * >> w = XMLPPolyDataWriter() >> >> The safest way to test this stuff is to try it with a "normal" ParaView build with MPI and Python enabled. If you can link and run against this then it has to do with your edition which you can then check on issues by using pvpython. We don't do a lot of testing on the generated Catalyst editions yet so it's possible that something snuck in to them. >> >> Also, what version of ParaView are you using? >> >> Andy >> >> >> >> >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke wrote: >> Hi Andy, >> >> thanks for looking into it. >> >> I further noticed that the same error occurs when I use the official Extras-edition (plus Enable-Python). When using the Rendering-Base-Python edition everything works. >> >> Best, >> Lars >> >> Am 18.08.2014 um 16:26 schrieb Andy Bauer : >> >> > Hi, >> > >> > I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work? >> > >> > Regards, >> > Andy >> > >> > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: >> > Dear ParaView users, >> > I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output: >> > >> > Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254 >> > Non-app bundle in install directory not supported >> > >> > Error: Could not import vtkCommonComputationalGeometryPython >> > Error: Could not import vtkRenderingCorePython >> > Error: Cannot import vtkPVServerManagerDefaultPython >> > Error: Cannot import vtkPVServerManagerRenderingPython >> > Error: Cannot import vtkPVAnimationPython >> > ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565 >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found. >> > >> > Traceback (most recent call last): >> > File "", line 2, in >> > File "Slice.py", line 73, in DoCoProcessing >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers >> > self.CreatePipeline(datadescription) >> > File "Slice.py", line 29, in CreatePipeline >> > File "Slice.py", line 17, in _CreatePipeline >> > File "Slice.py", line 23, in Pipeline >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter >> > return self.RegisterWriter(writer, filename, freq) >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter >> > writer, filename, freq) >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy >> > proxy.GetProperty("Input").SetInputConnection( >> > AttributeError: 'NoneType' object has no attribute ?GetProperty' >> > >> > >> > Why is the writer proxy searched in the filters group? It should be in the writers group right? >> > >> > Thanks for your help! >> > >> > >> > >> > _______________________________________________ >> > 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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From Matthias.Wiesenberger at uibk.ac.at Tue Aug 19 10:50:31 2014 From: Matthias.Wiesenberger at uibk.ac.at (Matthias Wiesenberger) Date: Tue, 19 Aug 2014 16:50:31 +0200 Subject: [Paraview] vector in netcdf files Message-ID: <53F36437.20207@uibk.ac.at> Hi guys, it's probably a simple question, but I can't find any information on the web (or I don't know where to look for). How do I write (time-dependent) data in netcdf-4 such that paraview recognizes it as a vector field. I tried to write it in a single 5-dimensional dataset and also tried to write the components seperately but I think I am missing the proper attribute names or something. With the 5D array paraview tells me that there are too many dimensions and I don't know how to tell paraview that three scalar datasets are the components of a vector field. Can you help me? Best Matthias -- Matthias Wiesenberger University of Innsbruck, Austria Institut f?r Ionen- und angewandte Physik Technikerstrasse 25/3, A-6020 Innsbruck Tel.: +43 (0)512 507 52725 E-Mail: Matthias.Wiesenberger at uibk.ac.at From andy.bauer at kitware.com Tue Aug 19 11:17:15 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 19 Aug 2014 11:17:15 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Lars, When you tried pvpython and creating an XMLPPolyDataWriter, did you do that with the pvpython that was built with your custom edition? That's what I meant before even though I didn't state the explicitly. Is there a reason you're using the next branch for this? In general you should use the master branch since it is more stable. Another question, are you linking your code to a developer installed location of Catalyst or the build location of Catalyst? If you're using the developer installed location you should try and see if you can use the build location to see if it works there. For a full ParaView build and install with developer information I was able to successfully run a Catalyst example that was linked to the installed location but maybe there's something missing with the Catalyst editions that don't install everything as needed. Regards, Andy On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Yup, this indeed points to the issue I was alluding do. Andy, feel > free to stop by if you need more info. > > Utkarsh > > On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote: > > Hi Andy, > > > > I can create XMLPPolyDataWriter in pvpython without errors. With a > normal ParaView build as well as with the Rendering-Base-Python edition it > works but I wanted to have a small custom edition. > > > > I am using the next branch from yesterday (79f7fdc). > > > > Best, > > Lars > > > > Am 18.08.2014 um 20:39 schrieb Andy Bauer : > > > >> Hi Lars, > >> > >> When you run pvpython can you create the XMLPPolyDataWriter ? > >> > >> To test this just do: > >> from paraview.simple import * > >> w = XMLPPolyDataWriter() > >> > >> The safest way to test this stuff is to try it with a "normal" ParaView > build with MPI and Python enabled. If you can link and run against this > then it has to do with your edition which you can then check on issues by > using pvpython. We don't do a lot of testing on the generated Catalyst > editions yet so it's possible that something snuck in to them. > >> > >> Also, what version of ParaView are you using? > >> > >> Andy > >> > >> > >> > >> > >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke wrote: > >> Hi Andy, > >> > >> thanks for looking into it. > >> > >> I further noticed that the same error occurs when I use the official > Extras-edition (plus Enable-Python). When using the Rendering-Base-Python > edition everything works. > >> > >> Best, > >> Lars > >> > >> Am 18.08.2014 um 16:26 schrieb Andy Bauer : > >> > >> > Hi, > >> > > >> > I will look at this a bit more but I'm wondering if you tried doing > the same with just a full ParaView build and if you did, how did it work? > >> > > >> > Regards, > >> > Andy > >> > > >> > > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke > wrote: > >> > Dear ParaView users, > >> > I have created a custom catalyst edition (see attached manifest). It > is basically the same as the Extras-edition with some parts removed. I have > integrated a catalyst adaptor into my application. Everything builds and > links fine. Now I want to use a python coprocessing pipeline (see attached > script). When running I get the following output: > >> > > >> > Generic Warning: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, > line 254 > >> > Non-app bundle in install directory not supported > >> > > >> > Error: Could not import vtkCommonComputationalGeometryPython > >> > Error: Could not import vtkRenderingCorePython > >> > Error: Cannot import vtkPVServerManagerDefaultPython > >> > Error: Cannot import vtkPVServerManagerRenderingPython > >> > Error: Cannot import vtkPVAnimationPython > >> > ERROR: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 565 > >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: > group=filters and proxy=XMLPPolyDataWriter were found. > >> > > >> > Traceback (most recent call last): > >> > File "", line 2, in > >> > File "Slice.py", line 73, in DoCoProcessing > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 103, in UpdateProducers > >> > self.CreatePipeline(datadescription) > >> > File "Slice.py", line 29, in CreatePipeline > >> > File "Slice.py", line 17, in _CreatePipeline > >> > File "Slice.py", line 23, in Pipeline > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 280, in CreateWriter > >> > return self.RegisterWriter(writer, filename, freq) > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 234, in RegisterWriter > >> > writer, filename, freq) > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 252, in WriterParametersProxy > >> > proxy.GetProperty("Input").SetInputConnection( > >> > AttributeError: 'NoneType' object has no attribute ?GetProperty' > >> > > >> > > >> > Why is the writer proxy searched in the filters group? It should be > in the writers group right? > >> > > >> > Thanks for your help! > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.bilke at ufz.de Tue Aug 19 11:23:57 2014 From: lars.bilke at ufz.de (Lars Bilke) Date: Tue, 19 Aug 2014 17:23:57 +0200 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Andy, thanks for your efforts! > When you tried pvpython and creating an XMLPPolyDataWriter, did you do that with the pvpython that was built with your custom edition? Yes. > Is there a reason you're using the next branch for this? I also tried the master branch before. > Another question, are you linking your code to a developer installed location of Catalyst or the build location of Catalyst? If you're using the developer installed location you should try and see if you can use the build location to see if it works there. I just used the build location. > For a full ParaView build and install with developer information I was able to successfully run a Catalyst example that was linked to the installed location but maybe there's something missing with the Catalyst editions that don't install everything as needed. Yes I know. It is also ok for me do use the full ParaView build. But maybe in the future when I finished the Catalyst stuff it would be nice for other developers to just have to build a small subset of ParaView. But until then I do not want to waste your time! Thanks a lot, Lars > > Regards, > Andy > > > On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit wrote: > Yup, this indeed points to the issue I was alluding do. Andy, feel > free to stop by if you need more info. > > Utkarsh > > On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote: > > Hi Andy, > > > > I can create XMLPPolyDataWriter in pvpython without errors. With a normal ParaView build as well as with the Rendering-Base-Python edition it works but I wanted to have a small custom edition. > > > > I am using the next branch from yesterday (79f7fdc). > > > > Best, > > Lars > > > > Am 18.08.2014 um 20:39 schrieb Andy Bauer : > > > >> Hi Lars, > >> > >> When you run pvpython can you create the XMLPPolyDataWriter ? > >> > >> To test this just do: > >> from paraview.simple import * > >> w = XMLPPolyDataWriter() > >> > >> The safest way to test this stuff is to try it with a "normal" ParaView build with MPI and Python enabled. If you can link and run against this then it has to do with your edition which you can then check on issues by using pvpython. We don't do a lot of testing on the generated Catalyst editions yet so it's possible that something snuck in to them. > >> > >> Also, what version of ParaView are you using? > >> > >> Andy > >> > >> > >> > >> > >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke wrote: > >> Hi Andy, > >> > >> thanks for looking into it. > >> > >> I further noticed that the same error occurs when I use the official Extras-edition (plus Enable-Python). When using the Rendering-Base-Python edition everything works. > >> > >> Best, > >> Lars > >> > >> Am 18.08.2014 um 16:26 schrieb Andy Bauer : > >> > >> > Hi, > >> > > >> > I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work? > >> > > >> > Regards, > >> > Andy > >> > > >> > > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke wrote: > >> > Dear ParaView users, > >> > I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output: > >> > > >> > Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254 > >> > Non-app bundle in install directory not supported > >> > > >> > Error: Could not import vtkCommonComputationalGeometryPython > >> > Error: Could not import vtkRenderingCorePython > >> > Error: Cannot import vtkPVServerManagerDefaultPython > >> > Error: Cannot import vtkPVServerManagerRenderingPython > >> > Error: Cannot import vtkPVAnimationPython > >> > ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565 > >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found. > >> > > >> > Traceback (most recent call last): > >> > File "", line 2, in > >> > File "Slice.py", line 73, in DoCoProcessing > >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers > >> > self.CreatePipeline(datadescription) > >> > File "Slice.py", line 29, in CreatePipeline > >> > File "Slice.py", line 17, in _CreatePipeline > >> > File "Slice.py", line 23, in Pipeline > >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter > >> > return self.RegisterWriter(writer, filename, freq) > >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter > >> > writer, filename, freq) > >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy > >> > proxy.GetProperty("Input").SetInputConnection( > >> > AttributeError: 'NoneType' object has no attribute ?GetProperty' > >> > > >> > > >> > Why is the writer proxy searched in the filters group? It should be in the writers group right? > >> > > >> > Thanks for your help! > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > From andy.bauer at kitware.com Tue Aug 19 11:29:59 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 19 Aug 2014 11:29:59 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Lars, Thanks for sticking with this. The Catalyst editions are a bit tricky and we haven't had enough people testing them out so there's a lot of space for mistakes so it takes me a bit of effort to try and figure out how to narrow down where the problem could be. I think I have enough information now to proceed. I should be able to spend a bit of time on this today. Thanks, Andy On Tue, Aug 19, 2014 at 11:23 AM, Lars Bilke wrote: > Hi Andy, > > thanks for your efforts! > > > When you tried pvpython and creating an XMLPPolyDataWriter, did you do > that with the pvpython that was built with your custom edition? > > Yes. > > > Is there a reason you're using the next branch for this? > > I also tried the master branch before. > > > Another question, are you linking your code to a developer installed > location of Catalyst or the build location of Catalyst? If you're using the > developer installed location you should try and see if you can use the > build location to see if it works there. > > I just used the build location. > > > For a full ParaView build and install with developer information I was > able to successfully run a Catalyst example that was linked to the > installed location but maybe there's something missing with the Catalyst > editions that don't install everything as needed. > > Yes I know. It is also ok for me do use the full ParaView build. But maybe > in the future when I finished the Catalyst stuff it would be nice for other > developers to just have to build a small subset of ParaView. > > But until then I do not want to waste your time! > > Thanks a lot, > Lars > > > > > Regards, > > Andy > > > > > > On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > > Yup, this indeed points to the issue I was alluding do. Andy, feel > > free to stop by if you need more info. > > > > Utkarsh > > > > On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote: > > > Hi Andy, > > > > > > I can create XMLPPolyDataWriter in pvpython without errors. With a > normal ParaView build as well as with the Rendering-Base-Python edition it > works but I wanted to have a small custom edition. > > > > > > I am using the next branch from yesterday (79f7fdc). > > > > > > Best, > > > Lars > > > > > > Am 18.08.2014 um 20:39 schrieb Andy Bauer : > > > > > >> Hi Lars, > > >> > > >> When you run pvpython can you create the XMLPPolyDataWriter ? > > >> > > >> To test this just do: > > >> from paraview.simple import * > > >> w = XMLPPolyDataWriter() > > >> > > >> The safest way to test this stuff is to try it with a "normal" > ParaView build with MPI and Python enabled. If you can link and run against > this then it has to do with your edition which you can then check on issues > by using pvpython. We don't do a lot of testing on the generated Catalyst > editions yet so it's possible that something snuck in to them. > > >> > > >> Also, what version of ParaView are you using? > > >> > > >> Andy > > >> > > >> > > >> > > >> > > >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke > wrote: > > >> Hi Andy, > > >> > > >> thanks for looking into it. > > >> > > >> I further noticed that the same error occurs when I use the official > Extras-edition (plus Enable-Python). When using the Rendering-Base-Python > edition everything works. > > >> > > >> Best, > > >> Lars > > >> > > >> Am 18.08.2014 um 16:26 schrieb Andy Bauer : > > >> > > >> > Hi, > > >> > > > >> > I will look at this a bit more but I'm wondering if you tried doing > the same with just a full ParaView build and if you did, how did it work? > > >> > > > >> > Regards, > > >> > Andy > > >> > > > >> > > > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke > wrote: > > >> > Dear ParaView users, > > >> > I have created a custom catalyst edition (see attached manifest). > It is basically the same as the Extras-edition with some parts removed. I > have integrated a catalyst adaptor into my application. Everything builds > and links fine. Now I want to use a python coprocessing pipeline (see > attached script). When running I get the following output: > > >> > > > >> > Generic Warning: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, > line 254 > > >> > Non-app bundle in install directory not supported > > >> > > > >> > Error: Could not import vtkCommonComputationalGeometryPython > > >> > Error: Could not import vtkRenderingCorePython > > >> > Error: Cannot import vtkPVServerManagerDefaultPython > > >> > Error: Cannot import vtkPVServerManagerRenderingPython > > >> > Error: Cannot import vtkPVAnimationPython > > >> > ERROR: In > /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 565 > > >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that > matches: group=filters and proxy=XMLPPolyDataWriter were found. > > >> > > > >> > Traceback (most recent call last): > > >> > File "", line 2, in > > >> > File "Slice.py", line 73, in DoCoProcessing > > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 103, in UpdateProducers > > >> > self.CreatePipeline(datadescription) > > >> > File "Slice.py", line 29, in CreatePipeline > > >> > File "Slice.py", line 17, in _CreatePipeline > > >> > File "Slice.py", line 23, in Pipeline > > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 280, in CreateWriter > > >> > return self.RegisterWriter(writer, filename, freq) > > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 234, in RegisterWriter > > >> > writer, filename, freq) > > >> > File > "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", > line 252, in WriterParametersProxy > > >> > proxy.GetProperty("Input").SetInputConnection( > > >> > AttributeError: 'NoneType' object has no attribute ?GetProperty' > > >> > > > >> > > > >> > Why is the writer proxy searched in the filters group? It should be > in the writers group right? > > >> > > > >> > Thanks for your help! > > >> > > > >> > > > >> > > > >> > _______________________________________________ > > >> > 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 > > >> > > > >> > Follow this link to subscribe/unsubscribe: > > >> > http://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 > > > > > > Follow this link to subscribe/unsubscribe: > > > http://public.kitware.com/mailman/listinfo/paraview > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Tue Aug 19 13:17:57 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 19 Aug 2014 17:17:57 +0000 Subject: [Paraview] vector in netcdf files In-Reply-To: <53F36437.20207@uibk.ac.at> Message-ID: Matthias, There are several netCDF readers. I think the one most relevant to you is the one that reads the CF convention, which is the most general. This is listed as "NetCDF files generic and CF conventions". Unfortunately, it looks like the CF convention does not specify a mechanism for defining vector fields, so it does not seem directly supported by the reader. Your best bet for now is to define the components as separate fields and then using the calculator filter to combine them into a vector. -Ken On 8/19/14 8:50 AM, "Matthias Wiesenberger" wrote: >Hi guys, > >it's probably a simple question, but I can't find any information on the >web (or I don't know where to look for). How do I write (time-dependent) >data in netcdf-4 such that paraview recognizes it as a vector field. I >tried to write it in a single 5-dimensional dataset and also tried to >write the components seperately but I think I am missing the proper >attribute names or something. With the 5D array paraview tells me that >there are too many dimensions and I don't know how to tell paraview that >three scalar datasets are the components of a vector field. >Can you help me? >Best >Matthias > >-- >Matthias Wiesenberger > >University of Innsbruck, Austria >Institut f?r Ionen- und angewandte Physik >Technikerstrasse 25/3, A-6020 Innsbruck > >Tel.: +43 (0)512 507 52725 >E-Mail: Matthias.Wiesenberger at uibk.ac.at >_______________________________________________ >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 > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From wascott at sandia.gov Tue Aug 19 14:55:11 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Aug 2014 18:55:11 +0000 Subject: [Paraview] Bounding box information with python Message-ID: <5ab1842e7987447488a62af9334678ac@ES05AMSNLNT.srn.sandia.gov> Is there a way to get bounding box information via Python? I'd like to determine the min/max extents of different parts via a script. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Tue Aug 19 14:56:25 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Tue, 19 Aug 2014 11:56:25 -0700 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: <53F22BD9.1020207@lbl.gov> <53F26581.3080008@gmail.com> <53F27A4B.2010907@hzdr.de> Message-ID: <53F39DD9.6030600@gmail.com> One thing to be aware of is the additional overhead of ssh compared to something like ncat or portfwd. ssh encrypts/unencrypts it's data which adds unnecessary overhead. I ran the 2 ssh tunnel solution at nersc for a while on Hopper. The performance was noticeably better with ncat which pipes data through untouched. The issue in large part because of the heavy loading and heavy network traffic on mom nodes where second tunnel ran. this is cray thing, you may not notice the difference between ssh and ncat on a typical cluster or if the system is not hammered by 1000's of simultaneous users as ours are. Still I think ncat is the best practice. On 08/18/2014 08:56 PM, Utkarsh Ayachit wrote: > Very cool! Thanks for sharing, Axel. It will be nice to link this page > from the Wiki as a reference/example, if that's okay. > > Utkarsh > > On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: >> Dear Ehsan, >> >> I use a similar setup as Burlen, tunneling twice over a login node to >> our cluster's head node. >> >> It also needs `GatewayPorts clientspecified` in the head node's >> sshd_config to work with maximum comfort. >> Feel free to check our wiki: >> >> https://github.com/ComputationalRadiationPhysics/picongpu/wiki/ParaView >> >> Best, >> Axel >> >> On 18.08.2014 22:43, Burlen Loring wrote: >>> Hi Utkarsh, >>> >>> Sure I can do that. >>> >>> Burlen >>> >>> On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: >>>> Burlen, >>>> >>>> Very cool. When you get the chance, mind updating the Wiki? >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: >>>>> Hi Ehsan, >>>>> >>>>> As Utkarsh says you need to use a reverse connection. I suggest ncat >>>>> instead >>>>> of portfwd because portfwd is a long dead project with no support and >>>>> it's >>>>> failed to compile on some systems I used. Here's a schematic of the >>>>> setup >>>>> >>>>> [work station] [ login node ] [ compute node ] >>>>> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >>>>> >>>>> in more detail: >>>>> in your pvsc on the client >>>>> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >>>>> >>>>> on the login node in a shell script referenced by the client's pvsc: >>>>> let LOGIN_PORT=${PORT}+1 >>>>> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & >>>>> qsub ... >>>>> >>>>> on the compute node in your batch script >>>>> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >>>>> --server-port ${LOGIN_PORT} ... >>>>> >>>>> You could skip ncat if you have control over the sshd config, you >>>>> need to >>>>> enable GatewayPorts. >>>>> >>>>> Burlen >>>>> >>>>> >>>>> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >>>>> >>>>> It does boil down to using reverse connection and setting up recursive >>>>> tunnels so that the pvserver and tunnel back to the client. See the >>>>> following on the need for portfwd and how it could potentially be >>>>> helpful here. >>>>> >>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >>>>> >>>>> >>>>> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei >>>>> wrote: >>>>> >>>>> Dear Utkarsh, >>>>> Thanks for your respond. I tried the section : " A forward connection >>>>> over >>>>> an ssh tunnel " >>>>> but it doesn't work. The problem is that I have to ssh to one system and >>>>> then ssh to the cluster again and finally I can submit a job. Do you >>>>> have >>>>> any other suggestions? >>>>> >>>>> thanks in advance, >>>>> Ehsan >>>>> >>>>> >>>>> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >>>>> wrote: >>>>> >>>>> This may be of help: >>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>>>> >>>>> Utkarsh >>>>> >>>>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei >>>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I'm new to paraview. I try to run pvserver on a cluster. The problem is >>>>> that >>>>> I need to ssh twice to get access to the cluster. To use pvserver I >>>>> submit a >>>>> job on the cluster and then I run pvserver using the command >>>>> "mpirun -np 12 pvserver" >>>>> then I pick the name and port from terminal and use it in paraview >>>>> client. >>>>> but paraview can't find the pvserver. Is there any way to establish a >>>>> connection via these two ssh tunnels? >>>>> >>>>> Thanks in advance, >>>>> Ehsan >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> -- >> >> Axel Huebl >> Diploma Student >> Phone +49 351 260 3582 >> https://www.hzdr.de/crp >> Computational Radiation Physics >> Laser Particle Acceleration Division >> Helmholtz-Zentrum Dresden - Rossendorf e.V. >> >> Bautzner Landstrasse 400, 01328 Dresden >> POB 510119, D-01314 Dresden >> Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey >> Prof. Dr.Dr.h.c. P. Joehnk >> VR 1693 beim Amtsgericht Dresden >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From sebastien.jourdain at kitware.com Tue Aug 19 15:16:56 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 19 Aug 2014 13:16:56 -0600 Subject: [Paraview] Bounding box information with python In-Reply-To: <5ab1842e7987447488a62af9334678ac@ES05AMSNLNT.srn.sandia.gov> References: <5ab1842e7987447488a62af9334678ac@ES05AMSNLNT.srn.sandia.gov> Message-ID: dataInfo = proxy.GetDataInformation() bounds = dataInfo.DataInformation.GetBounds() On Tue, Aug 19, 2014 at 12:55 PM, Scott, W Alan wrote: > Is there a way to get bounding box information via Python? I'd like to > determine the min/max extents of different parts via a script. > > Thanks, > > Alan > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Aug 19 15:41:55 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Aug 2014 19:41:55 +0000 Subject: [Paraview] [EXTERNAL] Re: Bounding box information with python In-Reply-To: References: <5ab1842e7987447488a62af9334678ac@ES05AMSNLNT.srn.sandia.gov> Message-ID: <433b56ace19344889a39b5baffe7d8fb@ES05AMSNLNT.srn.sandia.gov> Thanks, I believe that was what my user is looking for! Alan From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: Tuesday, August 19, 2014 1:17 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Bounding box information with python dataInfo = proxy.GetDataInformation() bounds = dataInfo.DataInformation.GetBounds() On Tue, Aug 19, 2014 at 12:55 PM, Scott, W Alan > wrote: Is there a way to get bounding box information via Python? I'd like to determine the min/max extents of different parts via a script. Thanks, Alan _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Aug 19 15:42:16 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Aug 2014 19:42:16 +0000 Subject: [Paraview] Zoom to data is not correctly captured in a python trace. Message-ID: <088d0ddbb2664bba8100a2a892e4c895@ES05AMSNLNT.srn.sandia.gov> >From a user: I'm trying to create a Python script which will loop through a set of Exodus block IDs and will output an image for each block. I started the trace and tried to use the "Zoom to Data" button, but this didn't translate well into the python script - instead I got a discrete camera view, which doesn't lend well to a general script. Is there a command I can pass to zoom to whatever data I'd like? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 19 15:56:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 19 Aug 2014 15:56:07 -0400 Subject: [Paraview] Zoom to data is not correctly captured in a python trace. In-Reply-To: <088d0ddbb2664bba8100a2a892e4c895@ES05AMSNLNT.srn.sandia.gov> References: <088d0ddbb2664bba8100a2a892e4c895@ES05AMSNLNT.srn.sandia.gov> Message-ID: Alan, With git/master, it translates to something like this: renderView1.ResetCamera(-10.0, 10.0, -10.0, 10.0, -10.0, 10.0) Where the values are indeed the current data bounds. But I think we can add API to "ZoomTOData" in Python using a data source rather that current bounds. Feel free to add a bug/feature request. Utkarsh On Tue, Aug 19, 2014 at 3:42 PM, Scott, W Alan wrote: > From a user: > > I'm trying to create a Python script which will loop through a set of Exodus > block IDs and will output an image for each block. I started the trace and > tried to use the "Zoom to Data" button, but this didn't translate well into > the python script - instead I got a discrete camera view, which doesn't lend > well to a general script. Is there a command I can pass to zoom to whatever > data I'd like? > > Thanks, > > Alan > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Tue Aug 19 15:57:32 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Aug 2014 19:57:32 +0000 Subject: [Paraview] [EXTERNAL] Re: Zoom to data is not correctly captured in a python trace. In-Reply-To: References: <088d0ddbb2664bba8100a2a892e4c895@ES05AMSNLNT.srn.sandia.gov> Message-ID: Thanks for the reply, I will let my user know and add a bug. Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, August 19, 2014 1:56 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Zoom to data is not correctly captured in a python trace. Alan, With git/master, it translates to something like this: renderView1.ResetCamera(-10.0, 10.0, -10.0, 10.0, -10.0, 10.0) Where the values are indeed the current data bounds. But I think we can add API to "ZoomTOData" in Python using a data source rather that current bounds. Feel free to add a bug/feature request. Utkarsh On Tue, Aug 19, 2014 at 3:42 PM, Scott, W Alan wrote: > From a user: > > I'm trying to create a Python script which will loop through a set of > Exodus block IDs and will output an image for each block. I started > the trace and tried to use the "Zoom to Data" button, but this didn't > translate well into the python script - instead I got a discrete > camera view, which doesn't lend well to a general script. Is there a > command I can pass to zoom to whatever data I'd like? > > Thanks, > > Alan > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Tue Aug 19 18:10:02 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Aug 2014 22:10:02 +0000 Subject: [Paraview] Transparent (alpha based) backgrounds Message-ID: <8fda3578f77e4013951726d6cba896c0@ES05AMSNLNT.srn.sandia.gov> Although Alpha channel based transparent backgrounds will be announced in Kitware's upcoming release notes, I have an example I just used for testing. Here is what our new save animation and save screenshot can create. ParaView master. Edit/ Settings/ General/ Set whether screenshots use an alpha... should be ON. I then saved two datasets - can and bake. One version of bake has had colors reversed. Using gimp, I then added a world map as the background, and added the two datasets on top. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newLayers0.jpg Type: image/jpeg Size: 144512 bytes Desc: newLayers0.jpg URL: From andy.bauer at kitware.com Tue Aug 19 21:22:44 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 19 Aug 2014 21:22:44 -0400 Subject: [Paraview] Zoom to data is not correctly captured in a python trace. In-Reply-To: References: <088d0ddbb2664bba8100a2a892e4c895@ES05AMSNLNT.srn.sandia.gov> Message-ID: I see in coprocessing.py it does: if view.IsA("vtkSMRenderViewProxy") == True: view.ResetCamera() elif view.IsA("vtkSMContextViewProxy") == True: view.ResetDisplay() The first is for standard 2D and 3D views and the second one is for plots. I'm not sure if this is any more helpful than what Utkarsh said. On Tue, Aug 19, 2014 at 3:56 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Alan, > > With git/master, it translates to something like this: > > renderView1.ResetCamera(-10.0, 10.0, -10.0, 10.0, -10.0, 10.0) > > Where the values are indeed the current data bounds. But I think we > can add API to "ZoomTOData" in Python using a data source rather that > current bounds. Feel free to add a bug/feature request. > > Utkarsh > > On Tue, Aug 19, 2014 at 3:42 PM, Scott, W Alan wrote: > > From a user: > > > > I'm trying to create a Python script which will loop through a set of > Exodus > > block IDs and will output an image for each block. I started the trace > and > > tried to use the "Zoom to Data" button, but this didn't translate well > into > > the python script - instead I got a discrete camera view, which doesn't > lend > > well to a general script. Is there a command I can pass to zoom to > whatever > > data I'd like? > > > > Thanks, > > > > Alan > > > > > > > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.huebl at hzdr.de Wed Aug 20 01:57:19 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Wed, 20 Aug 2014 07:57:19 +0200 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: References: <53F22BD9.1020207@lbl.gov> <53F26581.3080008@gmail.com> <53F27A4B.2010907@hzdr.de> Message-ID: <53F438BF.3050308@hzdr.de> Thanks! Sure, you can link it. Just tell me if you spot some improvements. Our stand-alone pvsc file does some more automated and rather "dark magic" to build the described the tunnels up with one click. Its linked there too. Axel On 19.08.2014 05:56, Utkarsh Ayachit wrote: > Very cool! Thanks for sharing, Axel. It will be nice to link this page > from the Wiki as a reference/example, if that's okay. > > Utkarsh > > On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: >> Dear Ehsan, >> >> I use a similar setup as Burlen, tunneling twice over a login node to >> our cluster's head node. >> >> It also needs `GatewayPorts clientspecified` in the head node's >> sshd_config to work with maximum comfort. >> Feel free to check our wiki: >> >> https://github.com/ComputationalRadiationPhysics/picongpu/wiki/ParaView >> >> Best, >> Axel >> >> On 18.08.2014 22:43, Burlen Loring wrote: >>> Hi Utkarsh, >>> >>> Sure I can do that. >>> >>> Burlen >>> >>> On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: >>>> Burlen, >>>> >>>> Very cool. When you get the chance, mind updating the Wiki? >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring wrote: >>>>> Hi Ehsan, >>>>> >>>>> As Utkarsh says you need to use a reverse connection. I suggest ncat >>>>> instead >>>>> of portfwd because portfwd is a long dead project with no support and >>>>> it's >>>>> failed to compile on some systems I used. Here's a schematic of the >>>>> setup >>>>> >>>>> [work station] [ login node ] [ compute node ] >>>>> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >>>>> >>>>> in more detail: >>>>> in your pvsc on the client >>>>> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >>>>> >>>>> on the login node in a shell script referenced by the client's pvsc: >>>>> let LOGIN_PORT=${PORT}+1 >>>>> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost $PORT" & >>>>> qsub ... >>>>> >>>>> on the compute node in your batch script >>>>> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >>>>> --server-port ${LOGIN_PORT} ... >>>>> >>>>> You could skip ncat if you have control over the sshd config, you >>>>> need to >>>>> enable GatewayPorts. >>>>> >>>>> Burlen >>>>> >>>>> >>>>> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >>>>> >>>>> It does boil down to using reverse connection and setting up recursive >>>>> tunnels so that the pvserver and tunnel back to the client. See the >>>>> following on the need for portfwd and how it could potentially be >>>>> helpful here. >>>>> >>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >>>>> >>>>> >>>>> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei >>>>> wrote: >>>>> >>>>> Dear Utkarsh, >>>>> Thanks for your respond. I tried the section : " A forward connection >>>>> over >>>>> an ssh tunnel " >>>>> but it doesn't work. The problem is that I have to ssh to one system and >>>>> then ssh to the cluster again and finally I can submit a job. Do you >>>>> have >>>>> any other suggestions? >>>>> >>>>> thanks in advance, >>>>> Ehsan >>>>> >>>>> >>>>> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >>>>> wrote: >>>>> >>>>> This may be of help: >>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>>>> >>>>> Utkarsh >>>>> >>>>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei >>>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I'm new to paraview. I try to run pvserver on a cluster. The problem is >>>>> that >>>>> I need to ssh twice to get access to the cluster. To use pvserver I >>>>> submit a >>>>> job on the cluster and then I run pvserver using the command >>>>> "mpirun -np 12 pvserver" >>>>> then I pick the name and port from terminal and use it in paraview >>>>> client. >>>>> but paraview can't find the pvserver. Is there any way to establish a >>>>> connection via these two ssh tunnels? >>>>> >>>>> Thanks in advance, >>>>> Ehsan >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> -- >> >> Axel Huebl >> Diploma Student >> Phone +49 351 260 3582 >> https://www.hzdr.de/crp >> Computational Radiation Physics >> Laser Particle Acceleration Division >> Helmholtz-Zentrum Dresden - Rossendorf e.V. >> >> Bautzner Landstrasse 400, 01328 Dresden >> POB 510119, D-01314 Dresden >> Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey >> Prof. Dr.Dr.h.c. P. Joehnk >> VR 1693 beim Amtsgericht Dresden >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5002 bytes Desc: S/MIME Cryptographic Signature URL: From rgirish28 at gmail.com Wed Aug 20 09:37:11 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Wed, 20 Aug 2014 15:37:11 +0200 Subject: [Paraview] Populating a servermanager list widget with string array Message-ID: Hi, I would like to use the panel_widget option in the servermanager XML with a String Array, but whenever I try to do it, it doesn't display anything. So, I'm wondering how it can be done even though it works with a normal StringVectorProperty for the default widget. Thank you. The XML and screenshot is given below. XML: This property specifies the CPO on the UAL Database. Screenshot of option working with default widget: https://imageshack.com/i/eyhM3mFKp Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.david.jones at gmail.com Wed Aug 20 10:01:50 2014 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Wed, 20 Aug 2014 10:01:50 -0400 Subject: [Paraview] Where to find error logs Message-ID: Hi, I am working on an application which writes a VTP file. We recently did a huge code merge and now our VTP writer is outputting files which cause Paraview to crash upon load. I am trying to debug this but it's difficult since Paraview doesn't give an error message, it just crashes. Does Paraview write errors out to a log? This is with Paraview 4.1.0 on Windows 64bit. Cheers, Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 20 10:05:49 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 10:05:49 -0400 Subject: [Paraview] Where to find error logs In-Reply-To: References: Message-ID: The best way is to rebuild ParaView in debug mode and then use the debugger, I'm afraid. On Wed, Aug 20, 2014 at 10:01 AM, Bruce Jones wrote: > Hi, > > I am working on an application which writes a VTP file. We recently did a > huge code merge and now our VTP writer is outputting files which cause > Paraview to crash upon load. I am trying to debug this but it's difficult > since Paraview doesn't give an error message, it just crashes. Does Paraview > write errors out to a log? > > This is with Paraview 4.1.0 on Windows 64bit. > > Cheers, > Bruce > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From dave.demarle at kitware.com Wed Aug 20 10:15:48 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 20 Aug 2014 10:15:48 -0400 Subject: [Paraview] announce: last call for 2014 HPCWire Reader's Choice Award nominations Message-ID: Vote for your favorite HPC applications, innovations, collaborations and practices. Especially VTK and ParaView of course! :) Nominations will close on August 22, 2014 at 11:59pm. Winners will be announced at IEEE SC14. cheers David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 6, 2014 at 5:38 PM, David E DeMarle wrote: > HPCWire is holding their Annual Reader?s Choice Awards. Please take > the time to nominate VTK and ParaView for this year?s awards. > > All you need to do is to submit the projects, products or solutions > you feel should be honored by receiving an award to the appropriate > (max of 3) categories before the deadline at: > http://www.hpcwire.com/2014-hpcwire-readers-choice-awards/ > > Anyone may can nominate their project, collaboration, product or > solution, and you do not need to fill the entire form out. Only the > categories(s) for which you feel your organization is qualified to > receive an award. You may submit as many nominations as you like. > Those who make it past the nominations will move on to the September > elections for selecting this year's finalists by our readers. > > Recent and near term user visible developments in the lands of VTK and > ParaView include: > > > *VTK* > > > * vtkDax, vtkPiston and vtkSMP: bringing GPGPU and multicore speed to > VTK. > > * vtkWeb - VTK based web services simply by enabling VTK_WRAP_PYTHON > > * vtk.numpy_interface - numpy processing moves beyond arrays into datasets > > * OpenGL2.1+ rendering - promising both render speed and extensibility > improvements > > *ParaView* > > * vector graphics screen exports > * parallel and composite SurfaceLIC representations of vector fields > * streamlined properties and view options panels > * the Python View allows just about any Python library to generate images > in ParaView views. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.david.jones at gmail.com Wed Aug 20 10:21:13 2014 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Wed, 20 Aug 2014 10:21:13 -0400 Subject: [Paraview] Where to find error logs In-Reply-To: References: Message-ID: Ok, I haven't had much luck building paraview in the past but will give it another go. I have uploaded the file that is causing problems here , if anyone could run this through in debug mode and let me know what the problem is it would be greatly appreciated. In the mean time I've attached a VS2013 debugger to the process. It complains of a divide by zero in vtkOXMLParser. We are using the vtkZLibDataCompressor compressor, so I can't vouch for the binary data that's being written, but the XML tags are all essentially the same as another file which is working. Cheers, Bruce On Wed, Aug 20, 2014 at 10:05 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > The best way is to rebuild ParaView in debug mode and then use the > debugger, I'm afraid. > > On Wed, Aug 20, 2014 at 10:01 AM, Bruce Jones > wrote: > > Hi, > > > > I am working on an application which writes a VTP file. We recently did a > > huge code merge and now our VTP writer is outputting files which cause > > Paraview to crash upon load. I am trying to debug this but it's difficult > > since Paraview doesn't give an error message, it just crashes. Does > Paraview > > write errors out to a log? > > > > This is with Paraview 4.1.0 on Windows 64bit. > > > > Cheers, > > Bruce > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: two_particle_normal_140701_aa_0000.vtp Type: application/octet-stream Size: 1944 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Aug 20 11:22:14 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 11:22:14 -0400 Subject: [Paraview] Where to find error logs In-Reply-To: References: Message-ID: The binary data for "Hydrodynamic Force" is invalid. If you remove the entry, the segfault goes away. On Wed, Aug 20, 2014 at 10:21 AM, Bruce Jones wrote: > Ok, I haven't had much luck building paraview in the past but will give it > another go. I have uploaded the file that is causing problems here, if > anyone could run this through in debug mode and let me know what the problem > is it would be greatly appreciated. > > In the mean time I've attached a VS2013 debugger to the process. It > complains of a divide by zero in vtkOXMLParser. We are using the > vtkZLibDataCompressor compressor, so I can't vouch for the binary data > that's being written, but the XML tags are all essentially the same as > another file which is working. > > Cheers, > Bruce > > > On Wed, Aug 20, 2014 at 10:05 AM, Utkarsh Ayachit > wrote: >> >> The best way is to rebuild ParaView in debug mode and then use the >> debugger, I'm afraid. >> >> On Wed, Aug 20, 2014 at 10:01 AM, Bruce Jones >> wrote: >> > Hi, >> > >> > I am working on an application which writes a VTP file. We recently did >> > a >> > huge code merge and now our VTP writer is outputting files which cause >> > Paraview to crash upon load. I am trying to debug this but it's >> > difficult >> > since Paraview doesn't give an error message, it just crashes. Does >> > Paraview >> > write errors out to a log? >> > >> > This is with Paraview 4.1.0 on Windows 64bit. >> > >> > Cheers, >> > Bruce >> > >> > _______________________________________________ >> > 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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > From bruce.david.jones at gmail.com Wed Aug 20 11:23:15 2014 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Wed, 20 Aug 2014 11:23:15 -0400 Subject: [Paraview] Where to find error logs In-Reply-To: References: Message-ID: Fantastic, thanks Utkarsh! Bruce On Wed, Aug 20, 2014 at 11:22 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > The binary data for "Hydrodynamic Force" is invalid. If you remove the > entry, the segfault goes away. > > On Wed, Aug 20, 2014 at 10:21 AM, Bruce Jones > wrote: > > Ok, I haven't had much luck building paraview in the past but will give > it > > another go. I have uploaded the file that is causing problems here, if > > anyone could run this through in debug mode and let me know what the > problem > > is it would be greatly appreciated. > > > > In the mean time I've attached a VS2013 debugger to the process. It > > complains of a divide by zero in vtkOXMLParser. We are using the > > vtkZLibDataCompressor compressor, so I can't vouch for the binary data > > that's being written, but the XML tags are all essentially the same as > > another file which is working. > > > > Cheers, > > Bruce > > > > > > On Wed, Aug 20, 2014 at 10:05 AM, Utkarsh Ayachit > > wrote: > >> > >> The best way is to rebuild ParaView in debug mode and then use the > >> debugger, I'm afraid. > >> > >> On Wed, Aug 20, 2014 at 10:01 AM, Bruce Jones > >> wrote: > >> > Hi, > >> > > >> > I am working on an application which writes a VTP file. We recently > did > >> > a > >> > huge code merge and now our VTP writer is outputting files which cause > >> > Paraview to crash upon load. I am trying to debug this but it's > >> > difficult > >> > since Paraview doesn't give an error message, it just crashes. Does > >> > Paraview > >> > write errors out to a log? > >> > > >> > This is with Paraview 4.1.0 on Windows 64bit. > >> > > >> > Cheers, > >> > Bruce > >> > > >> > _______________________________________________ > >> > 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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Wed Aug 20 15:05:50 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Wed, 20 Aug 2014 19:05:50 +0000 Subject: [Paraview] build trouble on LLNL clusters Message-ID: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Aug 20 15:11:54 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 20 Aug 2014 19:11:54 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> Message-ID: Master source pull, or PV 4.1? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Wednesday, August 20, 2014 1:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Wed Aug 20 15:19:15 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Wed, 20 Aug 2014 19:19:15 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> Message-ID: Hi Alan It?s from a tarball called "ParaView-v4.1.0-source.tar.gz? which I downloaded a while ago. I?m not sure if I pulled from a repo at the time, but I don?t think so. Checksum is rcook at rzgpu52 (paraview-4.1.0 ): sum ParaView-v4.1.0-source.tar.gz 47281 49278 On Aug 20, 2014, at 12:11 PM, Scott, W Alan > wrote: Master source pull, or PV 4.1? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Wednesday, August 20, 2014 1:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Aug 20 15:30:20 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 20 Aug 2014 19:30:20 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> , <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> Message-ID: Or your environment (i.e., path)? Alan From: Angelini, Richard C (Rick) CIV USARMY ARL (US) [mailto:richard.c.angelini.civ at mail.mil] Sent: Wednesday, August 20, 2014 1:29 PM To: Cook, Rich D (External Contacts); Scott, W Alan Cc: paraview at paraview.org Subject: RE: [Paraview] [EXTERNAL] build trouble on LLNL clusters So, what changed on the system-side? New GL development libraries, or maybe they were accidentally removed, or something like that? It's probably not you, your source code or your build script ..... ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Phone: 410-278-6266 ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Cook, Rich [cook47 at llnl.gov] Sent: Wednesday, August 20, 2014 3:19 PM To: Alan Scott Cc: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] build trouble on LLNL clusters Hi Alan It?s from a tarball called "ParaView-v4.1.0-source.tar.gz? which I downloaded a while ago. I?m not sure if I pulled from a repo at the time, but I don?t think so. Checksum is rcook at rzgpu52 (paraview-4.1.0 ): sum ParaView-v4.1.0-source.tar.gz 47281 49278 On Aug 20, 2014, at 12:11 PM, Scott, W Alan > wrote: Master source pull, or PV 4.1? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Wednesday, August 20, 2014 1:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Wed Aug 20 15:28:32 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Wed, 20 Aug 2014 19:28:32 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> , Message-ID: <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> So, what changed on the system-side? New GL development libraries, or maybe they were accidentally removed, or something like that? It's probably not you, your source code or your build script ..... ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Phone: 410-278-6266 ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Cook, Rich [cook47 at llnl.gov] Sent: Wednesday, August 20, 2014 3:19 PM To: Alan Scott Cc: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] build trouble on LLNL clusters Hi Alan It?s from a tarball called "ParaView-v4.1.0-source.tar.gz? which I downloaded a while ago. I?m not sure if I pulled from a repo at the time, but I don?t think so. Checksum is rcook at rzgpu52 (paraview-4.1.0 ): sum ParaView-v4.1.0-source.tar.gz 47281 49278 On Aug 20, 2014, at 12:11 PM, Scott, W Alan > wrote: Master source pull, or PV 4.1? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Wednesday, August 20, 2014 1:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Wed Aug 20 15:43:45 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Wed, 20 Aug 2014 19:43:45 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> , <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> Message-ID: <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> I don?t know. It is too hard a question to answer as I do not have a snapshot from a time when it built to compare against. I hope that I can simply answer, ?Why doesn?t this build work as is, given the error I?m seeing?? ? Rich On Aug 20, 2014, at 12:30 PM, Scott, W Alan > wrote: Or your environment (i.e., path)? Alan From: Angelini, Richard C (Rick) CIV USARMY ARL (US) [mailto:richard.c.angelini.civ at mail.mil] Sent: Wednesday, August 20, 2014 1:29 PM To: Cook, Rich D (External Contacts); Scott, W Alan Cc: paraview at paraview.org Subject: RE: [Paraview] [EXTERNAL] build trouble on LLNL clusters So, what changed on the system-side? New GL development libraries, or maybe they were accidentally removed, or something like that? It's probably not you, your source code or your build script ..... ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Phone: 410-278-6266 ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Cook, Rich [cook47 at llnl.gov] Sent: Wednesday, August 20, 2014 3:19 PM To: Alan Scott Cc: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] build trouble on LLNL clusters Hi Alan It?s from a tarball called "ParaView-v4.1.0-source.tar.gz? which I downloaded a while ago. I?m not sure if I pulled from a repo at the time, but I don?t think so. Checksum is rcook at rzgpu52 (paraview-4.1.0 ): sum ParaView-v4.1.0-source.tar.gz 47281 49278 On Aug 20, 2014, at 12:11 PM, Scott, W Alan > wrote: Master source pull, or PV 4.1? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Wednesday, August 20, 2014 1:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] build trouble on LLNL clusters Hello, I?m seeing this new error on our machines, which is mysterious as I have not changed my build process at all. Can someone help me spot the source of my woes here? Thanks! [ 5%] cd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype && /usr/local/tools/gcc-4.4.6/bin/gcc -DFT2_BUILD_LIBRARY -DVTK_IN_VTK -Dvtkfreetype_EXPORTS -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include -w -w -g -fPIC -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/zlib -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/include -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/src -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype -I/tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty/freetype/vtkfreetype/include -o CMakeFiles/vtkfreetype.dir/builds/unix/ftsystem.c.o -c /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/freetype/vtkfreetype/builds/unix/ftsystem.c [ 5%] [ 5%] CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psAddText': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:886: undefined reference to `glGetBooleanv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:889: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:907: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:918: undefined reference to `glPassThrough' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPostScriptBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3154: undefined reference to `glRenderMode' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3166: undefined reference to `glGetFloatv' /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3169: undefined reference to `glGetIntegerv' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintTeXBeginViewport': /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0/VTK/ThirdParty/gl2ps/vtkgl2ps/gl2ps.c:3346: undefined reference to `glRenderMode' CMakeFiles/vtkgl2ps.dir/gl2ps.c.o: In function `gl2psPrintPDFBeginViewport?: etc. etc. etc. Here is how I build. /usr/local/tools/cmake-2.8.10/bin/cmake.real \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON '\ -DOSMESA_LIBRARY:FILEPATH='\''/usr/lib64/libOSMesa.so'\''' \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DVTK_USE_X:BOOL=OFF \ -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/g++ \ -DCMAKE_C_COMPILER:FILEPATH=/usr/local/tools/gcc-4.4.6/bin/gcc \ -DPARAVIEW_USE_MPI:BOOL=OFF \ -DPARAVIEW_USE_MPI_SSEND:BOOL=OFF \ -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/tools/qt-4.8.3/bin/qmake.real \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DCMAKE_INSTALL_PREFIX:PATH=//usr/local/tools/paraview-osmesa-4.1.0 \ -DPARAVIEW_USE_BOOST:BOOL=ON \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DVISIT_BUILD_READER_CGNS:BOOL=ON \ -DVISIT_BUILD_READER_Mili:BOOL=ON \ -DVISIT_BUILD_READER_Silo:BOOL=ON \ -DCGNS_INCLUDE_DIR:PATH=/usr/local/tools/cgnslib-3.1.3-4/include '\ -DCGNS_LIBRARY:FILEPATH=/usr/local/tools/cgnslib-3.1.3-4/lib/libcgns.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DMILI_INCLUDE_DIR:PATH=/usr/local/tools/mili-1.11.1/include '\ -DMILI_LIBRARY:FILEPATH=/usr/local/tools/mili-1.11.1/lib/libmili.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DSILO_INCLUDE_DIR:PATH=/usr/local/tools/silo-4.8/include;/usr/local/tools/mili-1.11.1/include' '\ -DSILO_LIBRARY:FILEPATH=/usr/local/tools/silo-4.8/lib/libsiloh5.a;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBoost_INCLUDE_DIR:PATH=/usr/local/tools/boost-nompi-1.55.0/include \ -DBoost_LIBRARY_DIRS:FILEPATH=/usr/local/tools/boost-nompi-1.55.0/lib '\ -DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=-Wl,-rpath,$ORIGIN:$ORIGIN/../lib:/usr/local/lib' '\ -DCMAKE_CXX_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' '\ -DCMAKE_C_FLAGS:STRING= -I/usr/local/tools/mili-1.11.1/include -I/usr/local/tools/hdf5-gnu-serial-1.8.8/include -I/usr/local/include ' \ -DVTK_USE_SYSTEM_HDF5:BOOL=ON \ -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \ -DHDF5_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8 \ -DHDF5_C_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include \ -DHDF5_HL_INCLUDE_DIR:PATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/include '\ -DHDF5_hdf5_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' '\ -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/tools/hdf5-gnu-serial-1.8.8/lib/libhdf5_hl.so;/usr/local/tools/szip-2.0/lib/libsz.so;/usr/lib64/libz.so' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 20 16:08:19 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 16:08:19 -0400 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> Message-ID: Rich, The problem seems to be in ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeLists.txt. To make it easier, can you post all the files/directories under the following directory in the build directory? That will have generated makefiles will help determine the includes, libraries it's linking against. ParaViewBuild/VTK/ThirdParty/gl2ps/ An "ls" in this directory should look something like this "CMakeFiles cmake_install.cmake CTestTestfile.cmake Makefile vtkgl2ps vtk_gl2ps.h" Utkarsh From cook47 at llnl.gov Wed Aug 20 16:22:30 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Wed, 20 Aug 2014 20:22:30 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> Message-ID: <82F971DC-6F99-49C6-A277-5ADEB523D24E@llnl.gov> Hi, I think you are asking me to literally send you all those files by email, so I am attaching that directory as a compressed tarball. rcook at rzgpu52 (gl2ps ): ls -l total 16 drwxr-xr-x 2 rcook rcook 100 Aug 20 10:56 CMakeFiles -rw-r--r-- 1 rcook rcook 6295 Aug 20 10:56 Makefile -rw-r--r-- 1 rcook rcook 1466 Aug 20 10:56 cmake_install.cmake -rw-r--r-- 1 rcook rcook 806 Aug 20 10:55 vtk_gl2ps.h drwxr-xr-x 3 rcook rcook 100 Aug 20 10:56 vtkgl2ps Also note there is no file in gl2ps called CMakeLists.txt: rcook at rzgpu52 (ThirdParty ): pwd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty rcook at rzgpu52 (ThirdParty ): find gl2ps -name CMakeLists.txt rcook at rzgpu52 (ThirdParty ) Tarball attached (77kb). On Aug 20, 2014, at 1:08 PM, Utkarsh Ayachit wrote: > Rich, > > The problem seems to be in > ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeLists.txt. To make it > easier, can you post all the files/directories under the following > directory in the build directory? That will have generated makefiles > will help determine the includes, libraries it's linking against. > > ParaViewBuild/VTK/ThirdParty/gl2ps/ > > An "ls" in this directory should look something like this "CMakeFiles > cmake_install.cmake CTestTestfile.cmake Makefile vtkgl2ps > vtk_gl2ps.h" > > Utkarsh -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gl2ps.tgz Type: application/octet-stream Size: 76608 bytes Desc: gl2ps.tgz URL: From cook47 at llnl.gov Wed Aug 20 16:24:32 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Wed, 20 Aug 2014 20:24:32 +0000 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: <82F971DC-6F99-49C6-A277-5ADEB523D24E@llnl.gov> References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> <82F971DC-6F99-49C6-A277-5ADEB523D24E@llnl.gov> Message-ID: <19C4CCC2-F943-453A-A737-AEF877B073B9@llnl.gov> As a followup, I?m also sending my entire build log with verbosity turned on. Thanks! On Aug 20, 2014, at 1:22 PM, Cook, Rich > wrote: Hi, I think you are asking me to literally send you all those files by email, so I am attaching that directory as a compressed tarball. rcook at rzgpu52 (gl2ps ): ls -l total 16 drwxr-xr-x 2 rcook rcook 100 Aug 20 10:56 CMakeFiles -rw-r--r-- 1 rcook rcook 6295 Aug 20 10:56 Makefile -rw-r--r-- 1 rcook rcook 1466 Aug 20 10:56 cmake_install.cmake -rw-r--r-- 1 rcook rcook 806 Aug 20 10:55 vtk_gl2ps.h drwxr-xr-x 3 rcook rcook 100 Aug 20 10:56 vtkgl2ps Also note there is no file in gl2ps called CMakeLists.txt: rcook at rzgpu52 (ThirdParty ): pwd /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty rcook at rzgpu52 (ThirdParty ): find gl2ps -name CMakeLists.txt rcook at rzgpu52 (ThirdParty ) Tarball attached (77kb). On Aug 20, 2014, at 1:08 PM, Utkarsh Ayachit > wrote: > Rich, > > The problem seems to be in > ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeLists.txt. To make it > easier, can you post all the files/directories under the following > directory in the build directory? That will have generated makefiles > will help determine the includes, libraries it's linking against. > > ParaViewBuild/VTK/ThirdParty/gl2ps/ > > An "ls" in this directory should look something like this "CMakeFiles > cmake_install.cmake CTestTestfile.cmake Makefile vtkgl2ps > vtk_gl2ps.h" > > Utkarsh -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build.log.tgz Type: application/octet-stream Size: 123261 bytes Desc: build.log.tgz URL: From utkarsh.ayachit at kitware.com Wed Aug 20 16:37:28 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 16:37:28 -0400 Subject: [Paraview] [EXTERNAL] build trouble on LLNL clusters In-Reply-To: <19C4CCC2-F943-453A-A737-AEF877B073B9@llnl.gov> References: <4D962AA2-EADC-4BB8-95D8-0CAFF051C153@llnl.gov> <345817C8A61EA841AAE0120EC1514D955F2130B2@umechpanz.easf.csd.disa.mil> <0BA1FED5-C7B4-4C22-9D62-64D831621AE0@llnl.gov> <82F971DC-6F99-49C6-A277-5ADEB523D24E@llnl.gov> <19C4CCC2-F943-453A-A737-AEF877B073B9@llnl.gov> Message-ID: Thanks, yup, that's what I was looking for indeed. I was suspecting that vtkgl2ps is not linking against libOSMesa due to some bug in the CMakeLists.txt. What I confirmed that the vtkgl2ps library is indeed linking against libOSMesa.so. Now the glGetFloatv etc. should have indeed been defined in libOSMesa. Which version of Mesa is this? Mind attaching/sharing the libOSMesa.so? Let's see if that reveals anything. Utkarsh On Wed, Aug 20, 2014 at 4:24 PM, Cook, Rich wrote: > As a followup, I?m also sending my entire build log with verbosity turned > on. > > Thanks! > > On Aug 20, 2014, at 1:22 PM, Cook, Rich wrote: > > Hi, I think you are asking me to literally send you all those files by > email, so I am attaching that directory as a compressed tarball. > rcook at rzgpu52 (gl2ps ): ls -l > total 16 > drwxr-xr-x 2 rcook rcook 100 Aug 20 10:56 CMakeFiles > -rw-r--r-- 1 rcook rcook 6295 Aug 20 10:56 Makefile > -rw-r--r-- 1 rcook rcook 1466 Aug 20 10:56 cmake_install.cmake > -rw-r--r-- 1 rcook rcook 806 Aug 20 10:55 vtk_gl2ps.h > drwxr-xr-x 3 rcook rcook 100 Aug 20 10:56 vtkgl2ps > > Also note there is no file in gl2ps called CMakeLists.txt: > rcook at rzgpu52 (ThirdParty ): pwd > /tmp/dpkg-mkdeb.GU7yE8BBEM/src/ParaView-v4.1.0-Build/VTK/ThirdParty > rcook at rzgpu52 (ThirdParty ): find gl2ps -name CMakeLists.txt > rcook at rzgpu52 (ThirdParty ) > > Tarball attached (77kb). > > > > > > > On Aug 20, 2014, at 1:08 PM, Utkarsh Ayachit > wrote: > >> Rich, >> >> The problem seems to be in >> ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeLists.txt. To make it >> easier, can you post all the files/directories under the following >> directory in the build directory? That will have generated makefiles >> will help determine the includes, libraries it's linking against. >> >> ParaViewBuild/VTK/ThirdParty/gl2ps/ >> >> An "ls" in this directory should look something like this "CMakeFiles >> cmake_install.cmake CTestTestfile.cmake Makefile vtkgl2ps >> vtk_gl2ps.h" >> >> Utkarsh > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > From utkarsh.ayachit at kitware.com Wed Aug 20 16:49:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 16:49:22 -0400 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: Try modeling this on "Point/Cell" array selection properties provided by readers (in readers.xml). You'd need to use the ArraySelectionDomain, the StringListDomain won't work. e.g. This property lists which point-centered arrays to read. On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh wrote: > Hi, > > I would like to use the panel_widget option in the servermanager XML with a > String Array, but whenever I try to do it, it doesn't display anything. So, > I'm wondering how it can be done even though it works with a normal > StringVectorProperty for the default widget. Thank you. The XML and > screenshot is given below. > > XML: > > name="CPOList" > label="CPOList" > command="SetCPOList" > number_of_elements="1" > panel_visibility="default" > panel_widget="list"> > > > name="CPOListInfo"/> > > > > This property specifies the CPO on the UAL Database. > > > > > name="CPOListInfo" > label="CPOListInfo" > command="GetCPOList" > information_only="1"> > > > > Screenshot of option working with default widget: > > https://imageshack.com/i/eyhM3mFKp > > Regards, > Girish > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From rgirish28 at gmail.com Thu Aug 21 08:25:14 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 14:25:14 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: Dear Utkarsh, Thank you for the email. I tried modelling it along the example mentioned. This is the code that I have written but it segfaults for no reason that is apparent to me. C++ Code: ReadUALGrid::ReadUALGrid() { //this->FileName = NULL; this->SetNumberOfInputPorts(0); this->SetNumberOfOutputPorts(1); this->trial=vtkSmartPointer::New(); this->trial->AddArray("hello"); this->trial->AddArray("world"); this->trial->EnableAllArrays(); } } vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ return this->trial.GetPointer(); } int ReadUALGrid::GetCPOListArrayStatus(char *name){ return this->trial->GetArraySetting(name); } void ReadUALGrid::SetCPOListArrayStatus(const char * name, int status){ if (status){ this->trial->EnableArray(name); } else{ this->trial->DisableArray(name); } } int ReadUALGrid::GetNumberOfCPOListArrays(){ return this->trial->GetNumberOfArrays(); } const char * ReadUALGrid::GetCPOListArrayName(int index){ return this->trial->GetArrayName(index); } XML: This property specifies the CPO on the UAL Database. Any idea where I am making the mistake? Can I initialize a DataArraySelection that way? Thanks. Regards, Girish On 20 August 2014 22:49, Utkarsh Ayachit wrote: > Try modeling this on "Point/Cell" array selection properties provided > by readers (in readers.xml). You'd need to use the > ArraySelectionDomain, the StringListDomain won't work. > > e.g. > element_types="2 0" > information_property="PointArrayInfo" > label="Point Arrays" > name="PointArrayStatus" > number_of_elements="0" > number_of_elements_per_command="2" > repeat_command="1"> > > > name="PointArrayInfo" /> > > > This property lists which point-centered arrays to > read. > > > > > On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh > wrote: > > Hi, > > > > I would like to use the panel_widget option in the servermanager XML > with a > > String Array, but whenever I try to do it, it doesn't display anything. > So, > > I'm wondering how it can be done even though it works with a normal > > StringVectorProperty for the default widget. Thank you. The XML and > > screenshot is given below. > > > > XML: > > > > > name="CPOList" > > label="CPOList" > > command="SetCPOList" > > number_of_elements="1" > > panel_visibility="default" > > panel_widget="list"> > > > > > > > name="CPOListInfo"/> > > > > > > > > This property specifies the CPO on the UAL Database. > > > > > > > > > > > name="CPOListInfo" > > label="CPOListInfo" > > command="GetCPOList" > > information_only="1"> > > > > > > > > Screenshot of option working with default widget: > > > > https://imageshack.com/i/eyhM3mFKp > > > > Regards, > > Girish > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 21 08:30:59 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 08:30:59 -0400 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: I'd suggest looking at in the debugger and the tracking the segfault down. Not sure where it could be going wrong. Utkarsh On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh wrote: > Dear Utkarsh, > > Thank you for the email. I tried modelling it along the example mentioned. > This is the code that I have written but it segfaults for no reason that is > apparent to me. > > C++ Code: > > ReadUALGrid::ReadUALGrid() > { > //this->FileName = NULL; > this->SetNumberOfInputPorts(0); > this->SetNumberOfOutputPorts(1); > this->trial=vtkSmartPointer::New(); > this->trial->AddArray("hello"); > this->trial->AddArray("world"); > this->trial->EnableAllArrays(); > } > > > } > > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ > > return this->trial.GetPointer(); > } > > > int ReadUALGrid::GetCPOListArrayStatus(char *name){ > > return this->trial->GetArraySetting(name); > } > > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int status){ > > if (status){ > this->trial->EnableArray(name); > } > else{ > this->trial->DisableArray(name); > } > > > } > > > int ReadUALGrid::GetNumberOfCPOListArrays(){ > > > return this->trial->GetNumberOfArrays(); > } > > > const char * ReadUALGrid::GetCPOListArrayName(int index){ > > return this->trial->GetArrayName(index); > > } > > > XML: > > name="CPOList" > label="CPOList" > command="SetCPOListArrayStatus" > number_of_elements="0" > number_of_elements_per_command="2" > element_types="2 0" > information_property="CPOListArrayStatus" > panel_visibility="default"> > > > > name="CPOListArrayStatus"/> > > > > > This property specifies the CPO on the UAL Database. > > > > > name="CPOListArrayStatus" > information_only="1"> > > > > > Any idea where I am making the mistake? Can I initialize a > DataArraySelection that way? Thanks. > > Regards, > Girish > > > On 20 August 2014 22:49, Utkarsh Ayachit > wrote: >> >> Try modeling this on "Point/Cell" array selection properties provided >> by readers (in readers.xml). You'd need to use the >> ArraySelectionDomain, the StringListDomain won't work. >> >> e.g. >> > element_types="2 0" >> information_property="PointArrayInfo" >> label="Point Arrays" >> name="PointArrayStatus" >> number_of_elements="0" >> number_of_elements_per_command="2" >> repeat_command="1"> >> >> >> > name="PointArrayInfo" /> >> >> >> This property lists which point-centered arrays to >> read. >> >> >> >> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh >> wrote: >> > Hi, >> > >> > I would like to use the panel_widget option in the servermanager XML >> > with a >> > String Array, but whenever I try to do it, it doesn't display anything. >> > So, >> > I'm wondering how it can be done even though it works with a normal >> > StringVectorProperty for the default widget. Thank you. The XML and >> > screenshot is given below. >> > >> > XML: >> > >> > > > name="CPOList" >> > label="CPOList" >> > command="SetCPOList" >> > number_of_elements="1" >> > panel_visibility="default" >> > panel_widget="list"> >> > >> > >> > > > name="CPOListInfo"/> >> > >> > >> > >> > This property specifies the CPO on the UAL Database. >> > >> > >> > >> > >> > > > name="CPOListInfo" >> > label="CPOListInfo" >> > command="GetCPOList" >> > information_only="1"> >> > >> > >> > >> > Screenshot of option working with default widget: >> > >> > https://imageshack.com/i/eyhM3mFKp >> > >> > Regards, >> > Girish >> > >> > _______________________________________________ >> > 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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > From rgirish28 at gmail.com Thu Aug 21 08:35:27 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 14:35:27 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: This is the error that is printed out. I dunno what the problem is. I think it is to do with the vtkDataArraySelection being returned. It was atleast loading the ServerManager GUI before I added the function for returning the Selection. Any thoughts? Thank you and sorry for being a bother. ------------------- *** glibc detected *** /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: double free or corruption (!prev): 0x0000000000b6f720 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] ======= Memory map: ======== 00400000-008bb000 r-xp 00000000 00:19 102783069 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview 00abb000-00abc000 r--p 004bb000 00:19 102783069 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview 00abc000-00abd000 rw-p 004bc000 00:19 102783069 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview 00abd000-01fc4000 rw-p 00000000 00:00 0 [heap] 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 /lib64/ld-2.11.3.so 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 /lib64/ld-2.11.3.so 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 /lib64/ld-2.11.3.so 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 On 21 August 2014 14:30, Utkarsh Ayachit wrote: > I'd suggest looking at in the debugger and the tracking the segfault > down. Not sure where it could be going wrong. > > Utkarsh > > On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh > wrote: > > Dear Utkarsh, > > > > Thank you for the email. I tried modelling it along the example > mentioned. > > This is the code that I have written but it segfaults for no reason that > is > > apparent to me. > > > > C++ Code: > > > > ReadUALGrid::ReadUALGrid() > > { > > //this->FileName = NULL; > > this->SetNumberOfInputPorts(0); > > this->SetNumberOfOutputPorts(1); > > this->trial=vtkSmartPointer::New(); > > this->trial->AddArray("hello"); > > this->trial->AddArray("world"); > > this->trial->EnableAllArrays(); > > } > > > > > > } > > > > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ > > > > return this->trial.GetPointer(); > > } > > > > > > int ReadUALGrid::GetCPOListArrayStatus(char *name){ > > > > return this->trial->GetArraySetting(name); > > } > > > > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int status){ > > > > if (status){ > > this->trial->EnableArray(name); > > } > > else{ > > this->trial->DisableArray(name); > > } > > > > > > } > > > > > > int ReadUALGrid::GetNumberOfCPOListArrays(){ > > > > > > return this->trial->GetNumberOfArrays(); > > } > > > > > > const char * ReadUALGrid::GetCPOListArrayName(int index){ > > > > return this->trial->GetArrayName(index); > > > > } > > > > > > XML: > > > > > name="CPOList" > > label="CPOList" > > command="SetCPOListArrayStatus" > > number_of_elements="0" > > number_of_elements_per_command="2" > > element_types="2 0" > > information_property="CPOListArrayStatus" > > panel_visibility="default"> > > > > > > > > > name="CPOListArrayStatus"/> > > > > > > > > > > This property specifies the CPO on the UAL Database. > > > > > > > > > > > name="CPOListArrayStatus" > > information_only="1"> > > > > > > > > > > Any idea where I am making the mistake? Can I initialize a > > DataArraySelection that way? Thanks. > > > > Regards, > > Girish > > > > > > On 20 August 2014 22:49, Utkarsh Ayachit > > wrote: > >> > >> Try modeling this on "Point/Cell" array selection properties provided > >> by readers (in readers.xml). You'd need to use the > >> ArraySelectionDomain, the StringListDomain won't work. > >> > >> e.g. > >> >> element_types="2 0" > >> information_property="PointArrayInfo" > >> label="Point Arrays" > >> name="PointArrayStatus" > >> number_of_elements="0" > >> number_of_elements_per_command="2" > >> repeat_command="1"> > >> > >> > >> >> name="PointArrayInfo" /> > >> > >> > >> This property lists which point-centered arrays > to > >> read. > >> > >> > >> > >> > >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh > >> wrote: > >> > Hi, > >> > > >> > I would like to use the panel_widget option in the servermanager XML > >> > with a > >> > String Array, but whenever I try to do it, it doesn't display > anything. > >> > So, > >> > I'm wondering how it can be done even though it works with a normal > >> > StringVectorProperty for the default widget. Thank you. The XML and > >> > screenshot is given below. > >> > > >> > XML: > >> > > >> > >> > name="CPOList" > >> > label="CPOList" > >> > command="SetCPOList" > >> > number_of_elements="1" > >> > panel_visibility="default" > >> > panel_widget="list"> > >> > > >> > > >> > >> > name="CPOListInfo"/> > >> > > >> > > >> > > >> > This property specifies the CPO on the UAL Database. > >> > > >> > > >> > > >> > > >> > >> > name="CPOListInfo" > >> > label="CPOListInfo" > >> > command="GetCPOList" > >> > information_only="1"> > >> > > >> > > >> > > >> > Screenshot of option working with default widget: > >> > > >> > https://imageshack.com/i/eyhM3mFKp > >> > > >> > Regards, > >> > Girish > >> > > >> > _______________________________________________ > >> > 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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Thu Aug 21 08:42:42 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 14:42:42 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: The Plugin loads fine according to the debugger, so it is something to do with the loading of the vtkDataArraySelector. I'm completely lost on where my code is messing up. I hope you can help Utkarsh. Thanks. Regards, Girish On 21 August 2014 14:35, Girish Ramesh wrote: > This is the error that is printed out. I dunno what the problem is. I > think it is to do with the vtkDataArraySelection being returned. It was > atleast loading the ServerManager GUI before I added the function for > returning the Selection. Any thoughts? Thank you and sorry for being a > bother. > > > > ------------------- > > *** glibc detected *** > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: > double free or corruption (!prev): 0x0000000000b6f720 *** > ======= Backtrace: > ========= > > /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] > > /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] > /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] > /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] > /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] > /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] > ======= Memory map: ======== > 00400000-008bb000 r-xp 00000000 00:19 102783069 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > 00abb000-00abc000 r--p 004bb000 00:19 102783069 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > 00abc000-00abd000 rw-p 004bc000 00:19 102783069 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > 00abd000-01fc4000 rw-p 00000000 00:00 0 > [heap] > 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 > /lib64/ld-2.11.3.so > 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 > 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 > /lib64/ld-2.11.3.so > 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 > /lib64/ld-2.11.3.so > 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 > 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 > > > On 21 August 2014 14:30, Utkarsh Ayachit > wrote: > >> I'd suggest looking at in the debugger and the tracking the segfault >> down. Not sure where it could be going wrong. >> >> Utkarsh >> >> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh >> wrote: >> > Dear Utkarsh, >> > >> > Thank you for the email. I tried modelling it along the example >> mentioned. >> > This is the code that I have written but it segfaults for no reason >> that is >> > apparent to me. >> > >> > C++ Code: >> > >> > ReadUALGrid::ReadUALGrid() >> > { >> > //this->FileName = NULL; >> > this->SetNumberOfInputPorts(0); >> > this->SetNumberOfOutputPorts(1); >> > this->trial=vtkSmartPointer::New(); >> > this->trial->AddArray("hello"); >> > this->trial->AddArray("world"); >> > this->trial->EnableAllArrays(); >> > } >> > >> > >> > } >> > >> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ >> > >> > return this->trial.GetPointer(); >> > } >> > >> > >> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ >> > >> > return this->trial->GetArraySetting(name); >> > } >> > >> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int status){ >> > >> > if (status){ >> > this->trial->EnableArray(name); >> > } >> > else{ >> > this->trial->DisableArray(name); >> > } >> > >> > >> > } >> > >> > >> > int ReadUALGrid::GetNumberOfCPOListArrays(){ >> > >> > >> > return this->trial->GetNumberOfArrays(); >> > } >> > >> > >> > const char * ReadUALGrid::GetCPOListArrayName(int index){ >> > >> > return this->trial->GetArrayName(index); >> > >> > } >> > >> > >> > XML: >> > >> > > > name="CPOList" >> > label="CPOList" >> > command="SetCPOListArrayStatus" >> > number_of_elements="0" >> > number_of_elements_per_command="2" >> > element_types="2 0" >> > information_property="CPOListArrayStatus" >> > panel_visibility="default"> >> > >> > >> > >> > > > name="CPOListArrayStatus"/> >> > >> > >> > >> > >> > This property specifies the CPO on the UAL Database. >> > >> > >> > >> > >> > > > name="CPOListArrayStatus" >> > information_only="1"> >> > >> > >> > >> > >> > Any idea where I am making the mistake? Can I initialize a >> > DataArraySelection that way? Thanks. >> > >> > Regards, >> > Girish >> > >> > >> > On 20 August 2014 22:49, Utkarsh Ayachit >> > wrote: >> >> >> >> Try modeling this on "Point/Cell" array selection properties provided >> >> by readers (in readers.xml). You'd need to use the >> >> ArraySelectionDomain, the StringListDomain won't work. >> >> >> >> e.g. >> >> > >> element_types="2 0" >> >> information_property="PointArrayInfo" >> >> label="Point Arrays" >> >> name="PointArrayStatus" >> >> number_of_elements="0" >> >> number_of_elements_per_command="2" >> >> repeat_command="1"> >> >> >> >> >> >> > >> name="PointArrayInfo" /> >> >> >> >> >> >> This property lists which point-centered arrays >> to >> >> read. >> >> >> >> >> >> >> >> >> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh >> >> wrote: >> >> > Hi, >> >> > >> >> > I would like to use the panel_widget option in the servermanager XML >> >> > with a >> >> > String Array, but whenever I try to do it, it doesn't display >> anything. >> >> > So, >> >> > I'm wondering how it can be done even though it works with a normal >> >> > StringVectorProperty for the default widget. Thank you. The XML and >> >> > screenshot is given below. >> >> > >> >> > XML: >> >> > >> >> > > >> > name="CPOList" >> >> > label="CPOList" >> >> > command="SetCPOList" >> >> > number_of_elements="1" >> >> > panel_visibility="default" >> >> > panel_widget="list"> >> >> > >> >> > >> >> > > >> > name="CPOListInfo"/> >> >> > >> >> > >> >> > >> >> > This property specifies the CPO on the UAL Database. >> >> > >> >> > >> >> > >> >> > >> >> > > >> > name="CPOListInfo" >> >> > label="CPOListInfo" >> >> > command="GetCPOList" >> >> > information_only="1"> >> >> > >> >> > >> >> > >> >> > Screenshot of option working with default widget: >> >> > >> >> > https://imageshack.com/i/eyhM3mFKp >> >> > >> >> > Regards, >> >> > Girish >> >> > >> >> > _______________________________________________ >> >> > 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 >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> > >> > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 21 09:16:37 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 09:16:37 -0400 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: I think the segfault is happening in SetUserEPK(). On Thu, Aug 21, 2014 at 8:42 AM, Girish Ramesh wrote: > The Plugin loads fine according to the debugger, so it is something to do > with the loading of the vtkDataArraySelector. I'm completely lost on where > my code is messing up. I hope you can help Utkarsh. Thanks. > > Regards, > Girish > > > On 21 August 2014 14:35, Girish Ramesh wrote: >> >> This is the error that is printed out. I dunno what the problem is. I >> think it is to do with the vtkDataArraySelection being returned. It was >> atleast loading the ServerManager GUI before I added the function for >> returning the Selection. Any thoughts? Thank you and sorry for being a >> bother. >> >> >> >> ------------------- >> >> *** glibc detected *** >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: >> double free or corruption (!prev): 0x0000000000b6f720 *** >> ======= Backtrace: ========= >> /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] >> /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] >> /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] >> /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] >> /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] >> /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] >> ======= Memory map: ======== >> 00400000-008bb000 r-xp 00000000 00:19 102783069 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> 00abb000-00abc000 r--p 004bb000 00:19 102783069 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> 00abc000-00abd000 rw-p 004bc000 00:19 102783069 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> 00abd000-01fc4000 rw-p 00000000 00:00 0 >> [heap] >> 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 >> /lib64/ld-2.11.3.so >> 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 >> 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 >> /lib64/ld-2.11.3.so >> 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 >> /lib64/ld-2.11.3.so >> 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 >> 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 >> >> >> On 21 August 2014 14:30, Utkarsh Ayachit >> wrote: >>> >>> I'd suggest looking at in the debugger and the tracking the segfault >>> down. Not sure where it could be going wrong. >>> >>> Utkarsh >>> >>> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh >>> wrote: >>> > Dear Utkarsh, >>> > >>> > Thank you for the email. I tried modelling it along the example >>> > mentioned. >>> > This is the code that I have written but it segfaults for no reason >>> > that is >>> > apparent to me. >>> > >>> > C++ Code: >>> > >>> > ReadUALGrid::ReadUALGrid() >>> > { >>> > //this->FileName = NULL; >>> > this->SetNumberOfInputPorts(0); >>> > this->SetNumberOfOutputPorts(1); >>> > this->trial=vtkSmartPointer::New(); >>> > this->trial->AddArray("hello"); >>> > this->trial->AddArray("world"); >>> > this->trial->EnableAllArrays(); >>> > } >>> > >>> > >>> > } >>> > >>> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ >>> > >>> > return this->trial.GetPointer(); >>> > } >>> > >>> > >>> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ >>> > >>> > return this->trial->GetArraySetting(name); >>> > } >>> > >>> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int status){ >>> > >>> > if (status){ >>> > this->trial->EnableArray(name); >>> > } >>> > else{ >>> > this->trial->DisableArray(name); >>> > } >>> > >>> > >>> > } >>> > >>> > >>> > int ReadUALGrid::GetNumberOfCPOListArrays(){ >>> > >>> > >>> > return this->trial->GetNumberOfArrays(); >>> > } >>> > >>> > >>> > const char * ReadUALGrid::GetCPOListArrayName(int index){ >>> > >>> > return this->trial->GetArrayName(index); >>> > >>> > } >>> > >>> > >>> > XML: >>> > >>> > >> > name="CPOList" >>> > label="CPOList" >>> > command="SetCPOListArrayStatus" >>> > number_of_elements="0" >>> > number_of_elements_per_command="2" >>> > element_types="2 0" >>> > information_property="CPOListArrayStatus" >>> > panel_visibility="default"> >>> > >>> > >>> > >>> > >> > name="CPOListArrayStatus"/> >>> > >>> > >>> > >>> > >>> > This property specifies the CPO on the UAL Database. >>> > >>> > >>> > >>> > >>> > >> > name="CPOListArrayStatus" >>> > information_only="1"> >>> > >>> > >>> > >>> > >>> > Any idea where I am making the mistake? Can I initialize a >>> > DataArraySelection that way? Thanks. >>> > >>> > Regards, >>> > Girish >>> > >>> > >>> > On 20 August 2014 22:49, Utkarsh Ayachit >>> > wrote: >>> >> >>> >> Try modeling this on "Point/Cell" array selection properties provided >>> >> by readers (in readers.xml). You'd need to use the >>> >> ArraySelectionDomain, the StringListDomain won't work. >>> >> >>> >> e.g. >>> >> >> >> element_types="2 0" >>> >> information_property="PointArrayInfo" >>> >> label="Point Arrays" >>> >> name="PointArrayStatus" >>> >> number_of_elements="0" >>> >> number_of_elements_per_command="2" >>> >> repeat_command="1"> >>> >> >>> >> >>> >> >> >> name="PointArrayInfo" /> >>> >> >>> >> >>> >> This property lists which point-centered arrays >>> >> to >>> >> read. >>> >> >>> >> >>> >> >>> >> >>> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > I would like to use the panel_widget option in the servermanager XML >>> >> > with a >>> >> > String Array, but whenever I try to do it, it doesn't display >>> >> > anything. >>> >> > So, >>> >> > I'm wondering how it can be done even though it works with a normal >>> >> > StringVectorProperty for the default widget. Thank you. The XML and >>> >> > screenshot is given below. >>> >> > >>> >> > XML: >>> >> > >>> >> > >> >> > name="CPOList" >>> >> > label="CPOList" >>> >> > command="SetCPOList" >>> >> > number_of_elements="1" >>> >> > panel_visibility="default" >>> >> > panel_widget="list"> >>> >> > >>> >> > >>> >> > >> >> > name="CPOListInfo"/> >>> >> > >>> >> > >>> >> > >>> >> > This property specifies the CPO on the UAL Database. >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >> >> > name="CPOListInfo" >>> >> > label="CPOListInfo" >>> >> > command="GetCPOList" >>> >> > information_only="1"> >>> >> > >>> >> > >>> >> > >>> >> > Screenshot of option working with default widget: >>> >> > >>> >> > https://imageshack.com/i/eyhM3mFKp >>> >> > >>> >> > Regards, >>> >> > Girish >>> >> > >>> >> > _______________________________________________ >>> >> > 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 >>> >> > >>> >> > Follow this link to subscribe/unsubscribe: >>> >> > http://public.kitware.com/mailman/listinfo/paraview >>> >> > >>> > >>> > >> >> > From rgirish28 at gmail.com Thu Aug 21 09:21:44 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 15:21:44 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: Ok, now it is not segfaulting but it is also not loading the DataArraySelection functions as none of the debug macros are triggered when the plugin is loaded and any output statements that i have in the functions are not printed out. This is confusing! On 21 August 2014 15:16, Utkarsh Ayachit wrote: > I think the segfault is happening in SetUserEPK(). > > On Thu, Aug 21, 2014 at 8:42 AM, Girish Ramesh > wrote: > > The Plugin loads fine according to the debugger, so it is something to do > > with the loading of the vtkDataArraySelector. I'm completely lost on > where > > my code is messing up. I hope you can help Utkarsh. Thanks. > > > > Regards, > > Girish > > > > > > On 21 August 2014 14:35, Girish Ramesh wrote: > >> > >> This is the error that is printed out. I dunno what the problem is. I > >> think it is to do with the vtkDataArraySelection being returned. It was > >> atleast loading the ServerManager GUI before I added the function for > >> returning the Selection. Any thoughts? Thank you and sorry for being a > >> bother. > >> > >> > >> > >> ------------------- > >> > >> *** glibc detected *** > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: > >> double free or corruption (!prev): 0x0000000000b6f720 *** > >> ======= Backtrace: ========= > >> /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] > >> /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] > >> > /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] > >> /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] > >> > /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] > >> /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] > >> > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] > >> ======= Memory map: ======== > >> 00400000-008bb000 r-xp 00000000 00:19 102783069 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >> 00abb000-00abc000 r--p 004bb000 00:19 102783069 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >> 00abc000-00abd000 rw-p 004bc000 00:19 102783069 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >> 00abd000-01fc4000 rw-p 00000000 00:00 0 > >> [heap] > >> 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 > >> /lib64/ld-2.11.3.so > >> 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 > >> 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 > >> /lib64/ld-2.11.3.so > >> 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 > >> /lib64/ld-2.11.3.so > >> 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 > >> 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >> 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >> 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 > >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >> 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 > >> > >> > >> On 21 August 2014 14:30, Utkarsh Ayachit > >> wrote: > >>> > >>> I'd suggest looking at in the debugger and the tracking the segfault > >>> down. Not sure where it could be going wrong. > >>> > >>> Utkarsh > >>> > >>> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh > >>> wrote: > >>> > Dear Utkarsh, > >>> > > >>> > Thank you for the email. I tried modelling it along the example > >>> > mentioned. > >>> > This is the code that I have written but it segfaults for no reason > >>> > that is > >>> > apparent to me. > >>> > > >>> > C++ Code: > >>> > > >>> > ReadUALGrid::ReadUALGrid() > >>> > { > >>> > //this->FileName = NULL; > >>> > this->SetNumberOfInputPorts(0); > >>> > this->SetNumberOfOutputPorts(1); > >>> > this->trial=vtkSmartPointer::New(); > >>> > this->trial->AddArray("hello"); > >>> > this->trial->AddArray("world"); > >>> > this->trial->EnableAllArrays(); > >>> > } > >>> > > >>> > > >>> > } > >>> > > >>> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ > >>> > > >>> > return this->trial.GetPointer(); > >>> > } > >>> > > >>> > > >>> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ > >>> > > >>> > return this->trial->GetArraySetting(name); > >>> > } > >>> > > >>> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int > status){ > >>> > > >>> > if (status){ > >>> > this->trial->EnableArray(name); > >>> > } > >>> > else{ > >>> > this->trial->DisableArray(name); > >>> > } > >>> > > >>> > > >>> > } > >>> > > >>> > > >>> > int ReadUALGrid::GetNumberOfCPOListArrays(){ > >>> > > >>> > > >>> > return this->trial->GetNumberOfArrays(); > >>> > } > >>> > > >>> > > >>> > const char * ReadUALGrid::GetCPOListArrayName(int index){ > >>> > > >>> > return this->trial->GetArrayName(index); > >>> > > >>> > } > >>> > > >>> > > >>> > XML: > >>> > > >>> > >>> > name="CPOList" > >>> > label="CPOList" > >>> > command="SetCPOListArrayStatus" > >>> > number_of_elements="0" > >>> > number_of_elements_per_command="2" > >>> > element_types="2 0" > >>> > information_property="CPOListArrayStatus" > >>> > panel_visibility="default"> > >>> > > >>> > > >>> > > >>> > >>> > name="CPOListArrayStatus"/> > >>> > > >>> > > >>> > > >>> > > >>> > This property specifies the CPO on the UAL Database. > >>> > > >>> > > >>> > > >>> > > >>> > >>> > name="CPOListArrayStatus" > >>> > information_only="1"> > >>> > > >>> > > >>> > > >>> > > >>> > Any idea where I am making the mistake? Can I initialize a > >>> > DataArraySelection that way? Thanks. > >>> > > >>> > Regards, > >>> > Girish > >>> > > >>> > > >>> > On 20 August 2014 22:49, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> > >>> > wrote: > >>> >> > >>> >> Try modeling this on "Point/Cell" array selection properties > provided > >>> >> by readers (in readers.xml). You'd need to use the > >>> >> ArraySelectionDomain, the StringListDomain won't work. > >>> >> > >>> >> e.g. > >>> >> >>> >> element_types="2 0" > >>> >> information_property="PointArrayInfo" > >>> >> label="Point Arrays" > >>> >> name="PointArrayStatus" > >>> >> number_of_elements="0" > >>> >> number_of_elements_per_command="2" > >>> >> repeat_command="1"> > >>> >> > >>> >> > >>> >> >>> >> name="PointArrayInfo" /> > >>> >> > >>> >> > >>> >> This property lists which point-centered > arrays > >>> >> to > >>> >> read. > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh > > >>> >> wrote: > >>> >> > Hi, > >>> >> > > >>> >> > I would like to use the panel_widget option in the servermanager > XML > >>> >> > with a > >>> >> > String Array, but whenever I try to do it, it doesn't display > >>> >> > anything. > >>> >> > So, > >>> >> > I'm wondering how it can be done even though it works with a > normal > >>> >> > StringVectorProperty for the default widget. Thank you. The XML > and > >>> >> > screenshot is given below. > >>> >> > > >>> >> > XML: > >>> >> > > >>> >> > >>> >> > name="CPOList" > >>> >> > label="CPOList" > >>> >> > command="SetCPOList" > >>> >> > number_of_elements="1" > >>> >> > panel_visibility="default" > >>> >> > panel_widget="list"> > >>> >> > > >>> >> > > >>> >> > >>> >> > name="CPOListInfo"/> > >>> >> > > >>> >> > > >>> >> > > >>> >> > This property specifies the CPO on the UAL Database. > >>> >> > > >>> >> > > >>> >> > > >>> >> > > >>> >> > >>> >> > name="CPOListInfo" > >>> >> > label="CPOListInfo" > >>> >> > command="GetCPOList" > >>> >> > information_only="1"> > >>> >> > > >>> >> > > >>> >> > > >>> >> > Screenshot of option working with default widget: > >>> >> > > >>> >> > https://imageshack.com/i/eyhM3mFKp > >>> >> > > >>> >> > Regards, > >>> >> > Girish > >>> >> > > >>> >> > _______________________________________________ > >>> >> > 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 > >>> >> > > >>> >> > Follow this link to subscribe/unsubscribe: > >>> >> > http://public.kitware.com/mailman/listinfo/paraview > >>> >> > > >>> > > >>> > > >> > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Thu Aug 21 09:30:34 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 15:30:34 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: Yes, I got it working. It was a simple repeat_command="1" which was missing. What does that do if I may ask? Does it call the getselection function repeatedly whenever there is an update? Thanks anyway! On 21 August 2014 15:21, Girish Ramesh wrote: > Ok, now it is not segfaulting but it is also not loading the > DataArraySelection functions as none of the debug macros are triggered when > the plugin is loaded and any output statements that i have in the functions > are not printed out. This is confusing! > > > On 21 August 2014 15:16, Utkarsh Ayachit > wrote: > >> I think the segfault is happening in SetUserEPK(). >> >> On Thu, Aug 21, 2014 at 8:42 AM, Girish Ramesh >> wrote: >> > The Plugin loads fine according to the debugger, so it is something to >> do >> > with the loading of the vtkDataArraySelector. I'm completely lost on >> where >> > my code is messing up. I hope you can help Utkarsh. Thanks. >> > >> > Regards, >> > Girish >> > >> > >> > On 21 August 2014 14:35, Girish Ramesh wrote: >> >> >> >> This is the error that is printed out. I dunno what the problem is. I >> >> think it is to do with the vtkDataArraySelection being returned. It was >> >> atleast loading the ServerManager GUI before I added the function for >> >> returning the Selection. Any thoughts? Thank you and sorry for being a >> >> bother. >> >> >> >> >> >> >> >> ------------------- >> >> >> >> *** glibc detected *** >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: >> >> double free or corruption (!prev): 0x0000000000b6f720 *** >> >> ======= Backtrace: ========= >> >> /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] >> >> /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] >> >> >> /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] >> >> /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] >> >> >> /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] >> >> /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] >> >> >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] >> >> ======= Memory map: ======== >> >> 00400000-008bb000 r-xp 00000000 00:19 102783069 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> >> 00abb000-00abc000 r--p 004bb000 00:19 102783069 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> >> 00abc000-00abd000 rw-p 004bc000 00:19 102783069 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >> >> 00abd000-01fc4000 rw-p 00000000 00:00 0 >> >> [heap] >> >> 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 >> >> /lib64/ld-2.11.3.so >> >> 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 >> >> 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 >> >> /lib64/ld-2.11.3.so >> >> 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 >> >> /lib64/ld-2.11.3.so >> >> 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 >> >> 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> >> 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> >> 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 >> >> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >> >> 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 >> >> >> >> >> >> On 21 August 2014 14:30, Utkarsh Ayachit >> >> wrote: >> >>> >> >>> I'd suggest looking at in the debugger and the tracking the segfault >> >>> down. Not sure where it could be going wrong. >> >>> >> >>> Utkarsh >> >>> >> >>> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh >> >>> wrote: >> >>> > Dear Utkarsh, >> >>> > >> >>> > Thank you for the email. I tried modelling it along the example >> >>> > mentioned. >> >>> > This is the code that I have written but it segfaults for no reason >> >>> > that is >> >>> > apparent to me. >> >>> > >> >>> > C++ Code: >> >>> > >> >>> > ReadUALGrid::ReadUALGrid() >> >>> > { >> >>> > //this->FileName = NULL; >> >>> > this->SetNumberOfInputPorts(0); >> >>> > this->SetNumberOfOutputPorts(1); >> >>> > this->trial=vtkSmartPointer::New(); >> >>> > this->trial->AddArray("hello"); >> >>> > this->trial->AddArray("world"); >> >>> > this->trial->EnableAllArrays(); >> >>> > } >> >>> > >> >>> > >> >>> > } >> >>> > >> >>> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ >> >>> > >> >>> > return this->trial.GetPointer(); >> >>> > } >> >>> > >> >>> > >> >>> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ >> >>> > >> >>> > return this->trial->GetArraySetting(name); >> >>> > } >> >>> > >> >>> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int >> status){ >> >>> > >> >>> > if (status){ >> >>> > this->trial->EnableArray(name); >> >>> > } >> >>> > else{ >> >>> > this->trial->DisableArray(name); >> >>> > } >> >>> > >> >>> > >> >>> > } >> >>> > >> >>> > >> >>> > int ReadUALGrid::GetNumberOfCPOListArrays(){ >> >>> > >> >>> > >> >>> > return this->trial->GetNumberOfArrays(); >> >>> > } >> >>> > >> >>> > >> >>> > const char * ReadUALGrid::GetCPOListArrayName(int index){ >> >>> > >> >>> > return this->trial->GetArrayName(index); >> >>> > >> >>> > } >> >>> > >> >>> > >> >>> > XML: >> >>> > >> >>> > > >>> > name="CPOList" >> >>> > label="CPOList" >> >>> > command="SetCPOListArrayStatus" >> >>> > number_of_elements="0" >> >>> > number_of_elements_per_command="2" >> >>> > element_types="2 0" >> >>> > information_property="CPOListArrayStatus" >> >>> > panel_visibility="default"> >> >>> > >> >>> > >> >>> > >> >>> > > >>> > name="CPOListArrayStatus"/> >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > This property specifies the CPO on the UAL Database. >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > > >>> > name="CPOListArrayStatus" >> >>> > information_only="1"> >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > Any idea where I am making the mistake? Can I initialize a >> >>> > DataArraySelection that way? Thanks. >> >>> > >> >>> > Regards, >> >>> > Girish >> >>> > >> >>> > >> >>> > On 20 August 2014 22:49, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> >> >>> > wrote: >> >>> >> >> >>> >> Try modeling this on "Point/Cell" array selection properties >> provided >> >>> >> by readers (in readers.xml). You'd need to use the >> >>> >> ArraySelectionDomain, the StringListDomain won't work. >> >>> >> >> >>> >> e.g. >> >>> >> > >>> >> element_types="2 0" >> >>> >> information_property="PointArrayInfo" >> >>> >> label="Point Arrays" >> >>> >> name="PointArrayStatus" >> >>> >> number_of_elements="0" >> >>> >> number_of_elements_per_command="2" >> >>> >> repeat_command="1"> >> >>> >> >> >>> >> >> >>> >> > >>> >> name="PointArrayInfo" /> >> >>> >> >> >>> >> >> >>> >> This property lists which point-centered >> arrays >> >>> >> to >> >>> >> read. >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh < >> rgirish28 at gmail.com> >> >>> >> wrote: >> >>> >> > Hi, >> >>> >> > >> >>> >> > I would like to use the panel_widget option in the servermanager >> XML >> >>> >> > with a >> >>> >> > String Array, but whenever I try to do it, it doesn't display >> >>> >> > anything. >> >>> >> > So, >> >>> >> > I'm wondering how it can be done even though it works with a >> normal >> >>> >> > StringVectorProperty for the default widget. Thank you. The XML >> and >> >>> >> > screenshot is given below. >> >>> >> > >> >>> >> > XML: >> >>> >> > >> >>> >> > > >>> >> > name="CPOList" >> >>> >> > label="CPOList" >> >>> >> > command="SetCPOList" >> >>> >> > number_of_elements="1" >> >>> >> > panel_visibility="default" >> >>> >> > panel_widget="list"> >> >>> >> > >> >>> >> > >> >>> >> > > >>> >> > name="CPOListInfo"/> >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > This property specifies the CPO on the UAL Database. >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > > >>> >> > name="CPOListInfo" >> >>> >> > label="CPOListInfo" >> >>> >> > command="GetCPOList" >> >>> >> > information_only="1"> >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > Screenshot of option working with default widget: >> >>> >> > >> >>> >> > https://imageshack.com/i/eyhM3mFKp >> >>> >> > >> >>> >> > Regards, >> >>> >> > Girish >> >>> >> > >> >>> >> > _______________________________________________ >> >>> >> > 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 >> >>> >> > >> >>> >> > Follow this link to subscribe/unsubscribe: >> >>> >> > http://public.kitware.com/mailman/listinfo/paraview >> >>> >> > >> >>> > >> >>> > >> >> >> >> >> > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 21 09:32:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 09:32:07 -0400 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMVectorProperty.html#af8cb120cc1a06704cdd1cc25122d2eca On Thu, Aug 21, 2014 at 9:30 AM, Girish Ramesh wrote: > Yes, I got it working. It was a simple repeat_command="1" which was missing. > What does that do if I may ask? Does it call the getselection function > repeatedly whenever there is an update? Thanks anyway! > > > On 21 August 2014 15:21, Girish Ramesh wrote: >> >> Ok, now it is not segfaulting but it is also not loading the >> DataArraySelection functions as none of the debug macros are triggered when >> the plugin is loaded and any output statements that i have in the functions >> are not printed out. This is confusing! >> >> >> On 21 August 2014 15:16, Utkarsh Ayachit >> wrote: >>> >>> I think the segfault is happening in SetUserEPK(). >>> >>> On Thu, Aug 21, 2014 at 8:42 AM, Girish Ramesh >>> wrote: >>> > The Plugin loads fine according to the debugger, so it is something to >>> > do >>> > with the loading of the vtkDataArraySelector. I'm completely lost on >>> > where >>> > my code is messing up. I hope you can help Utkarsh. Thanks. >>> > >>> > Regards, >>> > Girish >>> > >>> > >>> > On 21 August 2014 14:35, Girish Ramesh wrote: >>> >> >>> >> This is the error that is printed out. I dunno what the problem is. I >>> >> think it is to do with the vtkDataArraySelection being returned. It >>> >> was >>> >> atleast loading the ServerManager GUI before I added the function for >>> >> returning the Selection. Any thoughts? Thank you and sorry for being a >>> >> bother. >>> >> >>> >> >>> >> >>> >> ------------------- >>> >> >>> >> *** glibc detected *** >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: >>> >> double free or corruption (!prev): 0x0000000000b6f720 *** >>> >> ======= Backtrace: ========= >>> >> /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] >>> >> /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] >>> >> >>> >> /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] >>> >> /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] >>> >> >>> >> /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] >>> >> /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] >>> >> >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] >>> >> ======= Memory map: ======== >>> >> 00400000-008bb000 r-xp 00000000 00:19 102783069 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >>> >> 00abb000-00abc000 r--p 004bb000 00:19 102783069 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >>> >> 00abc000-00abd000 rw-p 004bc000 00:19 102783069 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview >>> >> 00abd000-01fc4000 rw-p 00000000 00:00 0 >>> >> [heap] >>> >> 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 >>> >> /lib64/ld-2.11.3.so >>> >> 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 >>> >> 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 >>> >> /lib64/ld-2.11.3.so >>> >> 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 >>> >> /lib64/ld-2.11.3.so >>> >> 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 >>> >> 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >>> >> 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >>> >> 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 >>> >> >>> >> /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 >>> >> 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 >>> >> >>> >> >>> >> On 21 August 2014 14:30, Utkarsh Ayachit >>> >> wrote: >>> >>> >>> >>> I'd suggest looking at in the debugger and the tracking the segfault >>> >>> down. Not sure where it could be going wrong. >>> >>> >>> >>> Utkarsh >>> >>> >>> >>> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh >>> >>> wrote: >>> >>> > Dear Utkarsh, >>> >>> > >>> >>> > Thank you for the email. I tried modelling it along the example >>> >>> > mentioned. >>> >>> > This is the code that I have written but it segfaults for no reason >>> >>> > that is >>> >>> > apparent to me. >>> >>> > >>> >>> > C++ Code: >>> >>> > >>> >>> > ReadUALGrid::ReadUALGrid() >>> >>> > { >>> >>> > //this->FileName = NULL; >>> >>> > this->SetNumberOfInputPorts(0); >>> >>> > this->SetNumberOfOutputPorts(1); >>> >>> > this->trial=vtkSmartPointer::New(); >>> >>> > this->trial->AddArray("hello"); >>> >>> > this->trial->AddArray("world"); >>> >>> > this->trial->EnableAllArrays(); >>> >>> > } >>> >>> > >>> >>> > >>> >>> > } >>> >>> > >>> >>> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ >>> >>> > >>> >>> > return this->trial.GetPointer(); >>> >>> > } >>> >>> > >>> >>> > >>> >>> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ >>> >>> > >>> >>> > return this->trial->GetArraySetting(name); >>> >>> > } >>> >>> > >>> >>> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int >>> >>> > status){ >>> >>> > >>> >>> > if (status){ >>> >>> > this->trial->EnableArray(name); >>> >>> > } >>> >>> > else{ >>> >>> > this->trial->DisableArray(name); >>> >>> > } >>> >>> > >>> >>> > >>> >>> > } >>> >>> > >>> >>> > >>> >>> > int ReadUALGrid::GetNumberOfCPOListArrays(){ >>> >>> > >>> >>> > >>> >>> > return this->trial->GetNumberOfArrays(); >>> >>> > } >>> >>> > >>> >>> > >>> >>> > const char * ReadUALGrid::GetCPOListArrayName(int index){ >>> >>> > >>> >>> > return this->trial->GetArrayName(index); >>> >>> > >>> >>> > } >>> >>> > >>> >>> > >>> >>> > XML: >>> >>> > >>> >>> > >> >>> > name="CPOList" >>> >>> > label="CPOList" >>> >>> > command="SetCPOListArrayStatus" >>> >>> > number_of_elements="0" >>> >>> > number_of_elements_per_command="2" >>> >>> > element_types="2 0" >>> >>> > information_property="CPOListArrayStatus" >>> >>> > panel_visibility="default"> >>> >>> > >>> >>> > >>> >>> > >>> >>> > >> >>> > name="CPOListArrayStatus"/> >>> >>> > >>> >>> > >>> >>> > >>> >>> > >>> >>> > This property specifies the CPO on the UAL Database. >>> >>> > >>> >>> > >>> >>> > >>> >>> > >>> >>> > >> >>> > name="CPOListArrayStatus" >>> >>> > information_only="1"> >>> >>> > >>> >>> > >>> >>> > >>> >>> > >>> >>> > Any idea where I am making the mistake? Can I initialize a >>> >>> > DataArraySelection that way? Thanks. >>> >>> > >>> >>> > Regards, >>> >>> > Girish >>> >>> > >>> >>> > >>> >>> > On 20 August 2014 22:49, Utkarsh Ayachit >>> >>> > >>> >>> > wrote: >>> >>> >> >>> >>> >> Try modeling this on "Point/Cell" array selection properties >>> >>> >> provided >>> >>> >> by readers (in readers.xml). You'd need to use the >>> >>> >> ArraySelectionDomain, the StringListDomain won't work. >>> >>> >> >>> >>> >> e.g. >>> >>> >> >> >>> >> element_types="2 0" >>> >>> >> information_property="PointArrayInfo" >>> >>> >> label="Point Arrays" >>> >>> >> name="PointArrayStatus" >>> >>> >> number_of_elements="0" >>> >>> >> number_of_elements_per_command="2" >>> >>> >> repeat_command="1"> >>> >>> >> >>> >>> >> >>> >>> >> >> >>> >> name="PointArrayInfo" /> >>> >>> >> >>> >>> >> >>> >>> >> This property lists which point-centered >>> >>> >> arrays >>> >>> >> to >>> >>> >> read. >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh >>> >>> >> >>> >>> >> wrote: >>> >>> >> > Hi, >>> >>> >> > >>> >>> >> > I would like to use the panel_widget option in the servermanager >>> >>> >> > XML >>> >>> >> > with a >>> >>> >> > String Array, but whenever I try to do it, it doesn't display >>> >>> >> > anything. >>> >>> >> > So, >>> >>> >> > I'm wondering how it can be done even though it works with a >>> >>> >> > normal >>> >>> >> > StringVectorProperty for the default widget. Thank you. The XML >>> >>> >> > and >>> >>> >> > screenshot is given below. >>> >>> >> > >>> >>> >> > XML: >>> >>> >> > >>> >>> >> > >> >>> >> > name="CPOList" >>> >>> >> > label="CPOList" >>> >>> >> > command="SetCPOList" >>> >>> >> > number_of_elements="1" >>> >>> >> > panel_visibility="default" >>> >>> >> > panel_widget="list"> >>> >>> >> > >>> >>> >> > >>> >>> >> > >> >>> >> > name="CPOListInfo"/> >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > This property specifies the CPO on the UAL Database. >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >> >>> >> > name="CPOListInfo" >>> >>> >> > label="CPOListInfo" >>> >>> >> > command="GetCPOList" >>> >>> >> > information_only="1"> >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > Screenshot of option working with default widget: >>> >>> >> > >>> >>> >> > https://imageshack.com/i/eyhM3mFKp >>> >>> >> > >>> >>> >> > Regards, >>> >>> >> > Girish >>> >>> >> > >>> >>> >> > _______________________________________________ >>> >>> >> > 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 >>> >>> >> > >>> >>> >> > Follow this link to subscribe/unsubscribe: >>> >>> >> > http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > >>> >>> > >>> >>> > >>> >> >>> >> >>> > >> >> > From rgirish28 at gmail.com Thu Aug 21 09:33:22 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Thu, 21 Aug 2014 15:33:22 +0200 Subject: [Paraview] Populating a servermanager list widget with string array In-Reply-To: References: Message-ID: Thanks Utkarsh :) On 21 August 2014 15:32, Utkarsh Ayachit wrote: > > http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMVectorProperty.html#af8cb120cc1a06704cdd1cc25122d2eca > > On Thu, Aug 21, 2014 at 9:30 AM, Girish Ramesh > wrote: > > Yes, I got it working. It was a simple repeat_command="1" which was > missing. > > What does that do if I may ask? Does it call the getselection function > > repeatedly whenever there is an update? Thanks anyway! > > > > > > On 21 August 2014 15:21, Girish Ramesh wrote: > >> > >> Ok, now it is not segfaulting but it is also not loading the > >> DataArraySelection functions as none of the debug macros are triggered > when > >> the plugin is loaded and any output statements that i have in the > functions > >> are not printed out. This is confusing! > >> > >> > >> On 21 August 2014 15:16, Utkarsh Ayachit > >> wrote: > >>> > >>> I think the segfault is happening in SetUserEPK(). > >>> > >>> On Thu, Aug 21, 2014 at 8:42 AM, Girish Ramesh > >>> wrote: > >>> > The Plugin loads fine according to the debugger, so it is something > to > >>> > do > >>> > with the loading of the vtkDataArraySelector. I'm completely lost on > >>> > where > >>> > my code is messing up. I hope you can help Utkarsh. Thanks. > >>> > > >>> > Regards, > >>> > Girish > >>> > > >>> > > >>> > On 21 August 2014 14:35, Girish Ramesh wrote: > >>> >> > >>> >> This is the error that is printed out. I dunno what the problem is. > I > >>> >> think it is to do with the vtkDataArraySelection being returned. It > >>> >> was > >>> >> atleast loading the ServerManager GUI before I added the function > for > >>> >> returning the Selection. Any thoughts? Thank you and sorry for > being a > >>> >> bother. > >>> >> > >>> >> > >>> >> > >>> >> ------------------- > >>> >> > >>> >> *** glibc detected *** > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview: > >>> >> double free or corruption (!prev): 0x0000000000b6f720 *** > >>> >> ======= Backtrace: ========= > >>> >> /lib64/libc.so.6(+0x76808)[0x2b6ce2c97808] > >>> >> /lib64/libc.so.6(cfree+0x6c)[0x2b6ce2c9c84c] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_ZN11ReadUALGrid7SetUserEPKc+0x21d)[0x2b6ced506fdb] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/libReadUALGrid.so(_Z18ReadUALGridCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x8ae)[0x2b6ced5088c1] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x158)[0x2b6cd58551c8] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x192)[0x2b6cd5859102] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x2b6)[0x2b6cd5858746] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x2b6cd585880d] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN13vtkSIProperty14ProcessMessageER21vtkClientServerStream+0x3b)[0x2b6cd1e751bb] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty4PushERKNS_18vtkVectorOfStringsE+0x247)[0x2b6cd1e8aad7] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN25vtkSIStringVectorProperty17ReadXMLAttributesEP10vtkSIProxyP15vtkPVXMLElement+0x2c1)[0x2b6cd1e8b431] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy15ReadXMLPropertyEP15vtkPVXMLElement+0x1a2)[0x2b6cd1e77832] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x18f)[0x2b6cd1e7649f] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy17ReadXMLAttributesEP15vtkPVXMLElement+0x19)[0x2b6cd1e87809] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x6b2)[0x2b6cd1e76e12] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkSISourceProxy16CreateVTKObjectsEPN17paraview_protobuf7MessageE+0x65)[0x2b6cd1e89765] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN10vtkSIProxy4PushEPN17paraview_protobuf7MessageE+0x1d)[0x2b6cd1e7609d] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore17PushStateInternalEPN17paraview_protobuf7MessageE+0x1f2)[0x2b6cd1e5ae32] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore9PushStateEPN17paraview_protobuf7MessageE+0x37)[0x2b6cd1e592e7] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionBase9PushStateEPN17paraview_protobuf7MessageE+0x2d)[0x2b6cd1e56b2d] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN10vtkSMProxy16CreateVTKObjectsEv+0x363)[0x2b6cd195b663] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN16vtkSMSourceProxy16CreateVTKObjectsEv+0x15)[0x2b6cd199b7e5] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1(_ZN24vtkSMSessionProxyManager13RegisterProxyEPKcS1_P10vtkSMProxy+0x532)[0x2b6cd19908f2] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder19createProxyInternalERK7QStringS2_P8pqServerS2_S2_RK4QMapIS0_8QVariantE+0x3bb)[0x2b6ccf16451b] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1(_ZN15pqObjectBuilder12createSourceERK7QStringS2_P8pqServer+0x99)[0x2b6ccf160d09] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN21pqSourcesMenuReaction12createSourceERK7QStringS2_+0xfa)[0x2b6cce6ec38a] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredERK7QStringS2_+0x27)[0x2b6cce7042a7] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1(_ZN23pqProxyGroupMenuManager9triggeredEv+0x117)[0x2b6cce6db9a7] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x2bf)[0x2b6ce213d9bf] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction9triggeredEb+0x32)[0x2b6ce116bda2] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x70)[0x2b6ce116bf90] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x64b3b3)[0x2b6ce15a23b3] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x6517c9)[0x2b6ce15a87c9] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x929)[0x2b6ce11c1a99] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x5b)[0x2b6ce15a9b0b] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x2b6ce1171fac] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3eb)[0x2b6ce11766db] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x2b6ce21284de] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14b)[0x2b6ce1172deb] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x29677c)[0x2b6ce11ed77c] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xaf1)[0x2b6ce11ec651] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bb322)[0x2b6ce1212322] > >>> >> > >>> >> > /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a)[0x2b6ce8dad60a] > >>> >> /usr/lib64/libglib-2.0.so.0(+0x3ee88)[0x2b6ce8db0e88] > >>> >> > >>> >> > /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x2b6ce8db103c] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x2b6ce2156ac6] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4(+0x2bafae)[0x2b6ce1211fae] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x2b6ce21270df] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x138)[0x2b6ce2127368] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88)[0x2b6ce212c248] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview(main+0x185)[0x407ac5] > >>> >> /lib64/libc.so.6(__libc_start_main+0xe6)[0x2b6ce2c3fc16] > >>> >> > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview[0x407879] > >>> >> ======= Memory map: ======== > >>> >> 00400000-008bb000 r-xp 00000000 00:19 102783069 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >>> >> 00abb000-00abc000 r--p 004bb000 00:19 102783069 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >>> >> 00abc000-00abd000 rw-p 004bc000 00:19 102783069 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/paraview > >>> >> 00abd000-01fc4000 rw-p 00000000 00:00 0 > >>> >> [heap] > >>> >> 2b6cce41f000-2b6cce43e000 r-xp 00000000 fd:01 16791 > >>> >> /lib64/ld-2.11.3.so > >>> >> 2b6cce43e000-2b6cce440000 rw-p 00000000 00:00 0 > >>> >> 2b6cce63d000-2b6cce63e000 r--p 0001e000 fd:01 16791 > >>> >> /lib64/ld-2.11.3.so > >>> >> 2b6cce63e000-2b6cce63f000 rw-p 0001f000 fd:01 16791 > >>> >> /lib64/ld-2.11.3.so > >>> >> 2b6cce63f000-2b6cce640000 rw-p 00000000 00:00 0 > >>> >> 2b6cce640000-2b6cce743000 r-xp 00000000 00:19 67479375 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >>> >> 2b6cce743000-2b6cce943000 ---p 00103000 00:19 67479375 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >>> >> 2b6cce943000-2b6cce94d000 r--p 00103000 00:19 67479375 > >>> >> > >>> >> > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > >>> >> 2b6cce94d000-2b6cce950000 rw-p 0010d000 00:19 6 > >>> >> > >>> >> > >>> >> On 21 August 2014 14:30, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> > >>> >> wrote: > >>> >>> > >>> >>> I'd suggest looking at in the debugger and the tracking the > segfault > >>> >>> down. Not sure where it could be going wrong. > >>> >>> > >>> >>> Utkarsh > >>> >>> > >>> >>> On Thu, Aug 21, 2014 at 8:25 AM, Girish Ramesh < > rgirish28 at gmail.com> > >>> >>> wrote: > >>> >>> > Dear Utkarsh, > >>> >>> > > >>> >>> > Thank you for the email. I tried modelling it along the example > >>> >>> > mentioned. > >>> >>> > This is the code that I have written but it segfaults for no > reason > >>> >>> > that is > >>> >>> > apparent to me. > >>> >>> > > >>> >>> > C++ Code: > >>> >>> > > >>> >>> > ReadUALGrid::ReadUALGrid() > >>> >>> > { > >>> >>> > //this->FileName = NULL; > >>> >>> > this->SetNumberOfInputPorts(0); > >>> >>> > this->SetNumberOfOutputPorts(1); > >>> >>> > this->trial=vtkSmartPointer::New(); > >>> >>> > this->trial->AddArray("hello"); > >>> >>> > this->trial->AddArray("world"); > >>> >>> > this->trial->EnableAllArrays(); > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > } > >>> >>> > > >>> >>> > vtkDataArraySelection * ReadUALGrid::GetCPOListSelection(){ > >>> >>> > > >>> >>> > return this->trial.GetPointer(); > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > int ReadUALGrid::GetCPOListArrayStatus(char *name){ > >>> >>> > > >>> >>> > return this->trial->GetArraySetting(name); > >>> >>> > } > >>> >>> > > >>> >>> > void ReadUALGrid::SetCPOListArrayStatus(const char * name, int > >>> >>> > status){ > >>> >>> > > >>> >>> > if (status){ > >>> >>> > this->trial->EnableArray(name); > >>> >>> > } > >>> >>> > else{ > >>> >>> > this->trial->DisableArray(name); > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > int ReadUALGrid::GetNumberOfCPOListArrays(){ > >>> >>> > > >>> >>> > > >>> >>> > return this->trial->GetNumberOfArrays(); > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > const char * ReadUALGrid::GetCPOListArrayName(int index){ > >>> >>> > > >>> >>> > return this->trial->GetArrayName(index); > >>> >>> > > >>> >>> > } > >>> >>> > > >>> >>> > > >>> >>> > XML: > >>> >>> > > >>> >>> > >>> >>> > name="CPOList" > >>> >>> > label="CPOList" > >>> >>> > command="SetCPOListArrayStatus" > >>> >>> > number_of_elements="0" > >>> >>> > number_of_elements_per_command="2" > >>> >>> > element_types="2 0" > >>> >>> > information_property="CPOListArrayStatus" > >>> >>> > panel_visibility="default"> > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > >>> >>> > name="CPOListArrayStatus"/> > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > This property specifies the CPO on the UAL Database. > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > >>> >>> > name="CPOListArrayStatus" > >>> >>> > information_only="1"> > >>> >>> > attribute_name="CPOList"/> > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > Any idea where I am making the mistake? Can I initialize a > >>> >>> > DataArraySelection that way? Thanks. > >>> >>> > > >>> >>> > Regards, > >>> >>> > Girish > >>> >>> > > >>> >>> > > >>> >>> > On 20 August 2014 22:49, Utkarsh Ayachit > >>> >>> > > >>> >>> > wrote: > >>> >>> >> > >>> >>> >> Try modeling this on "Point/Cell" array selection properties > >>> >>> >> provided > >>> >>> >> by readers (in readers.xml). You'd need to use the > >>> >>> >> ArraySelectionDomain, the StringListDomain won't work. > >>> >>> >> > >>> >>> >> e.g. > >>> >>> >> >>> >>> >> element_types="2 0" > >>> >>> >> > information_property="PointArrayInfo" > >>> >>> >> label="Point Arrays" > >>> >>> >> name="PointArrayStatus" > >>> >>> >> number_of_elements="0" > >>> >>> >> number_of_elements_per_command="2" > >>> >>> >> repeat_command="1"> > >>> >>> >> > >>> >>> >> > >>> >>> >> >>> >>> >> name="PointArrayInfo" /> > >>> >>> >> > >>> >>> >> > >>> >>> >> This property lists which point-centered > >>> >>> >> arrays > >>> >>> >> to > >>> >>> >> read. > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> On Wed, Aug 20, 2014 at 9:37 AM, Girish Ramesh > >>> >>> >> > >>> >>> >> wrote: > >>> >>> >> > Hi, > >>> >>> >> > > >>> >>> >> > I would like to use the panel_widget option in the > servermanager > >>> >>> >> > XML > >>> >>> >> > with a > >>> >>> >> > String Array, but whenever I try to do it, it doesn't display > >>> >>> >> > anything. > >>> >>> >> > So, > >>> >>> >> > I'm wondering how it can be done even though it works with a > >>> >>> >> > normal > >>> >>> >> > StringVectorProperty for the default widget. Thank you. The > XML > >>> >>> >> > and > >>> >>> >> > screenshot is given below. > >>> >>> >> > > >>> >>> >> > XML: > >>> >>> >> > > >>> >>> >> > >>> >>> >> > name="CPOList" > >>> >>> >> > label="CPOList" > >>> >>> >> > command="SetCPOList" > >>> >>> >> > number_of_elements="1" > >>> >>> >> > panel_visibility="default" > >>> >>> >> > panel_widget="list"> > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > >>> >>> >> > name="CPOListInfo"/> > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > This property specifies the CPO on the UAL Database. > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > >>> >>> >> > name="CPOListInfo" > >>> >>> >> > label="CPOListInfo" > >>> >>> >> > command="GetCPOList" > >>> >>> >> > information_only="1"> > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > Screenshot of option working with default widget: > >>> >>> >> > > >>> >>> >> > https://imageshack.com/i/eyhM3mFKp > >>> >>> >> > > >>> >>> >> > Regards, > >>> >>> >> > Girish > >>> >>> >> > > >>> >>> >> > _______________________________________________ > >>> >>> >> > 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 > >>> >>> >> > > >>> >>> >> > Follow this link to subscribe/unsubscribe: > >>> >>> >> > http://public.kitware.com/mailman/listinfo/paraview > >>> >>> >> > > >>> >>> > > >>> >>> > > >>> >> > >>> >> > >>> > > >> > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Aug 21 11:47:18 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 21 Aug 2014 11:47:18 -0400 Subject: [Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found In-Reply-To: References: <0CEBBA51-BEFB-4F29-B1DF-F91316740090@ufz.de> Message-ID: Hi Lars, I was testing this out a bit more and am getting confused again. Can you send me a copy of your custom edition with everything in it as well as the command you used to create the Catalyst source? Thanks, Andy On Tue, Aug 19, 2014 at 11:29 AM, Andy Bauer wrote: > Hi Lars, > > Thanks for sticking with this. The Catalyst editions are a bit tricky and > we haven't had enough people testing them out so there's a lot of space for > mistakes so it takes me a bit of effort to try and figure out how to narrow > down where the problem could be. I think I have enough information now to > proceed. I should be able to spend a bit of time on this today. > > Thanks, > Andy > > > On Tue, Aug 19, 2014 at 11:23 AM, Lars Bilke wrote: > >> Hi Andy, >> >> thanks for your efforts! >> >> > When you tried pvpython and creating an XMLPPolyDataWriter, did you do >> that with the pvpython that was built with your custom edition? >> >> Yes. >> >> > Is there a reason you're using the next branch for this? >> >> I also tried the master branch before. >> >> > Another question, are you linking your code to a developer installed >> location of Catalyst or the build location of Catalyst? If you're using the >> developer installed location you should try and see if you can use the >> build location to see if it works there. >> >> I just used the build location. >> >> > For a full ParaView build and install with developer information I was >> able to successfully run a Catalyst example that was linked to the >> installed location but maybe there's something missing with the Catalyst >> editions that don't install everything as needed. >> >> Yes I know. It is also ok for me do use the full ParaView build. But >> maybe in the future when I finished the Catalyst stuff it would be nice for >> other developers to just have to build a small subset of ParaView. >> >> But until then I do not want to waste your time! >> >> Thanks a lot, >> Lars >> >> > >> > Regards, >> > Andy >> > >> > >> > On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> > Yup, this indeed points to the issue I was alluding do. Andy, feel >> > free to stop by if you need more info. >> > >> > Utkarsh >> > >> > On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote: >> > > Hi Andy, >> > > >> > > I can create XMLPPolyDataWriter in pvpython without errors. With a >> normal ParaView build as well as with the Rendering-Base-Python edition it >> works but I wanted to have a small custom edition. >> > > >> > > I am using the next branch from yesterday (79f7fdc). >> > > >> > > Best, >> > > Lars >> > > >> > > Am 18.08.2014 um 20:39 schrieb Andy Bauer : >> > > >> > >> Hi Lars, >> > >> >> > >> When you run pvpython can you create the XMLPPolyDataWriter ? >> > >> >> > >> To test this just do: >> > >> from paraview.simple import * >> > >> w = XMLPPolyDataWriter() >> > >> >> > >> The safest way to test this stuff is to try it with a "normal" >> ParaView build with MPI and Python enabled. If you can link and run against >> this then it has to do with your edition which you can then check on issues >> by using pvpython. We don't do a lot of testing on the generated Catalyst >> editions yet so it's possible that something snuck in to them. >> > >> >> > >> Also, what version of ParaView are you using? >> > >> >> > >> Andy >> > >> >> > >> >> > >> >> > >> >> > >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke >> wrote: >> > >> Hi Andy, >> > >> >> > >> thanks for looking into it. >> > >> >> > >> I further noticed that the same error occurs when I use the official >> Extras-edition (plus Enable-Python). When using the Rendering-Base-Python >> edition everything works. >> > >> >> > >> Best, >> > >> Lars >> > >> >> > >> Am 18.08.2014 um 16:26 schrieb Andy Bauer : >> > >> >> > >> > Hi, >> > >> > >> > >> > I will look at this a bit more but I'm wondering if you tried >> doing the same with just a full ParaView build and if you did, how did it >> work? >> > >> > >> > >> > Regards, >> > >> > Andy >> > >> > >> > >> > >> > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke >> wrote: >> > >> > Dear ParaView users, >> > >> > I have created a custom catalyst edition (see attached manifest). >> It is basically the same as the Extras-edition with some parts removed. I >> have integrated a catalyst adaptor into my application. Everything builds >> and links fine. Now I want to use a python coprocessing pipeline (see >> attached script). When running I get the following output: >> > >> > >> > >> > Generic Warning: In >> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, >> line 254 >> > >> > Non-app bundle in install directory not supported >> > >> > >> > >> > Error: Could not import vtkCommonComputationalGeometryPython >> > >> > Error: Could not import vtkRenderingCorePython >> > >> > Error: Cannot import vtkPVServerManagerDefaultPython >> > >> > Error: Cannot import vtkPVServerManagerRenderingPython >> > >> > Error: Cannot import vtkPVAnimationPython >> > >> > ERROR: In >> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >> line 565 >> > >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that >> matches: group=filters and proxy=XMLPPolyDataWriter were found. >> > >> > >> > >> > Traceback (most recent call last): >> > >> > File "", line 2, in >> > >> > File "Slice.py", line 73, in DoCoProcessing >> > >> > File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 103, in UpdateProducers >> > >> > self.CreatePipeline(datadescription) >> > >> > File "Slice.py", line 29, in CreatePipeline >> > >> > File "Slice.py", line 17, in _CreatePipeline >> > >> > File "Slice.py", line 23, in Pipeline >> > >> > File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 280, in CreateWriter >> > >> > return self.RegisterWriter(writer, filename, freq) >> > >> > File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 234, in RegisterWriter >> > >> > writer, filename, freq) >> > >> > File >> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", >> line 252, in WriterParametersProxy >> > >> > proxy.GetProperty("Input").SetInputConnection( >> > >> > AttributeError: 'NoneType' object has no attribute ?GetProperty' >> > >> > >> > >> > >> > >> > Why is the writer proxy searched in the filters group? It should >> be in the writers group right? >> > >> > >> > >> > Thanks for your help! >> > >> > >> > >> > >> > >> > >> > >> > _______________________________________________ >> > >> > 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 >> > >> > >> > >> > Follow this link to subscribe/unsubscribe: >> > >> > http://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 >> > > >> > > Follow this link to subscribe/unsubscribe: >> > > http://public.kitware.com/mailman/listinfo/paraview >> > >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 21 12:39:30 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 12:39:30 -0400 Subject: [Paraview] Dropping Snow Leopard OsX binaries for ParaView Message-ID: Folks, I wanted to get a quick survey if anyone cares if we drop support for distributing ParaVIew binaries compatible with Snow Leopard. Lion on wards will still be supported. There are two OsX binaries for ParaView currently and it can be a little confusing which one to use and why and hence this change. Utkarsh From leonardopessanha74 at gmail.com Thu Aug 21 15:45:30 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Thu, 21 Aug 2014 16:45:30 -0300 Subject: [Paraview] Camera - Interpolate Camera Locations Message-ID: Hi, In the animation view, i have added a camera with the Interpolate Camera Locations mode. My goal is to create an animation that goes along the X axis but stops at some points It has 30 seconds I have marked the following times {0, 5, 10, 15, 20, 25, 30} 0 to 5 increasing the position in the X axis 5 to 10 stopped 10 to 15 increasing the position in the X axis 15 to 20 stopped 20 to 25 increasing the position in the X axis 25 to 30 stopped I tried to stop the camera by putting the same camera values in: "Position" "Focal Point" "View Angle" "View Up" "Parallel Scale" but the camera is not steady, the camera performs a little movement around the point How can i stop the camera completely? Att, Leonardo Pessanha -------------- next part -------------- An HTML attachment was scrubbed... URL: From nivdstee at vub.ac.be Fri Aug 22 08:25:17 2014 From: nivdstee at vub.ac.be (Nils Van den Steen) Date: Fri, 22 Aug 2014 14:25:17 +0200 Subject: [Paraview] Fwd: 1D and 2D meshes in 3D space In-Reply-To: References: Message-ID: When opening a vtk file, resulting from a simulation in 1D and 2D meshes but in a 3D space (x, y and z coordinates are/can be different from 0). Paraview doesn't show anything. Only when volumes are defined in the mesh, results are shown (but these aren't very significant). The mesh I'm using consists of two parallel surfaces, connected with 1D lines (2.5 dimensional mesh). Kind regards, Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Fri Aug 22 09:21:46 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Fri, 22 Aug 2014 13:21:46 +0000 Subject: [Paraview] Dropping Snow Leopard OsX binaries for ParaView (UNCLASSIFIED) Message-ID: <345817C8A61EA841AAE0120EC1514D955F293E35@umechpanz.easf.csd.disa.mil> Classification: UNCLASSIFIED Caveats: NONE Utkarsh - unfortunately, we still have a number of Macs that are still running 10.6 and are using ParaView. We'd like to use the pre-built binaries for the next ParaView release on these machines if possible. We currently don't build from source for the Macs, so that could be a real challenge for us if we needed to start doing that ..... We're pushing hard to get these 10.6 systems either replaced or upgraded in the near future, but not soon enough. ----------------------------------------------------------------- Folks, I wanted to get a quick survey if anyone cares if we drop support for distributing ParaVIew binaries compatible with Snow Leopard. Lion on wards will still be supported. There are two OsX binaries for ParaView currently and it can be a little confusing which one to use and why and hence this change. Utkarsh ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5627 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Aug 22 10:37:51 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Aug 2014 10:37:51 -0400 Subject: [Paraview] Dropping Snow Leopard OsX binaries for ParaView (UNCLASSIFIED) In-Reply-To: <345817C8A61EA841AAE0120EC1514D955F293E35@umechpanz.easf.csd.disa.mil> References: <345817C8A61EA841AAE0120EC1514D955F293E35@umechpanz.easf.csd.disa.mil> Message-ID: Sounds good, Rick. I'll shelve this proposal for now. We can revisit for 4.3. I'll look into renaming the OsX binaries to minimize confusion. Utkarsh On Fri, Aug 22, 2014 at 9:21 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Utkarsh - unfortunately, we still have a number of Macs that are still > running 10.6 and are using ParaView. We'd like to use the pre-built > binaries for the next ParaView release on these machines if possible. We > currently don't build from source for the Macs, so that could be a real > challenge for us if we needed to start doing that ..... We're pushing > hard to get these 10.6 systems either replaced or upgraded in the near > future, but not soon enough. > > ----------------------------------------------------------------- > > Folks, > > I wanted to get a quick survey if anyone cares if we drop support for > distributing ParaVIew binaries compatible with Snow Leopard. Lion on > wards will still be supported. > > There are two OsX binaries for ParaView currently and it can be a > little confusing which one to use and why and hence this change. > > Utkarsh > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Fri Aug 22 11:44:44 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 22 Aug 2014 15:44:44 +0000 Subject: [Paraview] loading temporally distributed (one time step per file) Exodus (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, I am able to load spatially distributed Exodus file ok with ParaView. However, when I load a temporally distributed Exodus file, I am missing all the time step. What would be a proper way to load temporally distributed Exodus file? I just picked the grouping that ParaView has when loading the files. Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From a.huebl at hzdr.de Fri Aug 22 14:18:58 2014 From: a.huebl at hzdr.de (Huebl, Axel) Date: Fri, 22 Aug 2014 20:18:58 +0200 Subject: [Paraview] A Forward Connection Over two ssh Tunnel In-Reply-To: <53F39DD9.6030600@gmail.com> References: <53F22BD9.1020207@lbl.gov> <53F26581.3080008@gmail.com> <53F27A4B.2010907@hzdr.de> <53F39DD9.6030600@gmail.com> Message-ID: <53F78992.7040805@hzdr.de> Burlen, thanks you pointed that out, I totally agree. I will give it a try next time! Axel On 19.08.2014 20:56, Burlen Loring wrote: > One thing to be aware of is the additional overhead of ssh compared to > something like ncat or portfwd. ssh encrypts/unencrypts it's data which > adds unnecessary overhead. I ran the 2 ssh tunnel solution at nersc for > a while on Hopper. The performance was noticeably better with ncat which > pipes data through untouched. The issue in large part because of the > heavy loading and heavy network traffic on mom nodes where second tunnel > ran. this is cray thing, you may not notice the difference between ssh > and ncat on a typical cluster or if the system is not hammered by 1000's > of simultaneous users as ours are. Still I think ncat is the best practice. > > On 08/18/2014 08:56 PM, Utkarsh Ayachit wrote: >> Very cool! Thanks for sharing, Axel. It will be nice to link this page >> from the Wiki as a reference/example, if that's okay. >> >> Utkarsh >> >> On Mon, Aug 18, 2014 at 6:12 PM, Huebl, Axel wrote: >>> Dear Ehsan, >>> >>> I use a similar setup as Burlen, tunneling twice over a login node to >>> our cluster's head node. >>> >>> It also needs `GatewayPorts clientspecified` in the head node's >>> sshd_config to work with maximum comfort. >>> Feel free to check our wiki: >>> >>> https://github.com/ComputationalRadiationPhysics/picongpu/wiki/ParaView >>> >>> Best, >>> Axel >>> >>> On 18.08.2014 22:43, Burlen Loring wrote: >>>> Hi Utkarsh, >>>> >>>> Sure I can do that. >>>> >>>> Burlen >>>> >>>> On 08/18/2014 01:36 PM, Utkarsh Ayachit wrote: >>>>> Burlen, >>>>> >>>>> Very cool. When you get the chance, mind updating the Wiki? >>>>> >>>>> Thanks >>>>> Utkarsh >>>>> >>>>> On Mon, Aug 18, 2014 at 12:37 PM, Burlen Loring >>>>> wrote: >>>>>> Hi Ehsan, >>>>>> >>>>>> As Utkarsh says you need to use a reverse connection. I suggest ncat >>>>>> instead >>>>>> of portfwd because portfwd is a long dead project with no support and >>>>>> it's >>>>>> failed to compile on some systems I used. Here's a schematic of the >>>>>> setup >>>>>> >>>>>> [work station] [ login node ] [ compute node ] >>>>>> [ paraview ]<-- ssh -R --<[ ncat + ncat -l ]<-----[ pvserver -rc ] >>>>>> >>>>>> in more detail: >>>>>> in your pvsc on the client >>>>>> ssh -R ${PORT}:localhost:${PORT} ${LOGIN_HOST} ... >>>>>> >>>>>> on the login node in a shell script referenced by the client's pvsc: >>>>>> let LOGIN_PORT=${PORT}+1 >>>>>> ncat -l ${LOGIN_HOST} ${LOGIN_PORT} --sh-exec="ncat localhost >>>>>> $PORT" & >>>>>> qsub ... >>>>>> >>>>>> on the compute node in your batch script >>>>>> mpirun ... pvserver --reverse-connection --client-host ${LOGIN_HOST} >>>>>> --server-port ${LOGIN_PORT} ... >>>>>> >>>>>> You could skip ncat if you have control over the sshd config, you >>>>>> need to >>>>>> enable GatewayPorts. >>>>>> >>>>>> Burlen >>>>>> >>>>>> >>>>>> On 08/18/2014 08:18 AM, Utkarsh Ayachit wrote: >>>>>> >>>>>> It does boil down to using reverse connection and setting up >>>>>> recursive >>>>>> tunnels so that the pvserver and tunnel back to the client. See the >>>>>> following on the need for portfwd and how it could potentially be >>>>>> helpful here. >>>>>> >>>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_over_a_Reverse_ssh_Tunnel_with_portfwd >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Aug 18, 2014 at 11:15 AM, ehsan saei >>>>>> wrote: >>>>>> >>>>>> Dear Utkarsh, >>>>>> Thanks for your respond. I tried the section : " A forward connection >>>>>> over >>>>>> an ssh tunnel " >>>>>> but it doesn't work. The problem is that I have to ssh to one >>>>>> system and >>>>>> then ssh to the cluster again and finally I can submit a job. Do you >>>>>> have >>>>>> any other suggestions? >>>>>> >>>>>> thanks in advance, >>>>>> Ehsan >>>>>> >>>>>> >>>>>> On Mon, Aug 18, 2014 at 4:29 PM, Utkarsh Ayachit >>>>>> wrote: >>>>>> >>>>>> This may be of help: >>>>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding >>>>>> >>>>>> Utkarsh >>>>>> >>>>>> On Mon, Aug 18, 2014 at 5:52 AM, ehsan saei >>>>>> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> I'm new to paraview. I try to run pvserver on a cluster. The >>>>>> problem is >>>>>> that >>>>>> I need to ssh twice to get access to the cluster. To use pvserver I >>>>>> submit a >>>>>> job on the cluster and then I run pvserver using the command >>>>>> "mpirun -np 12 pvserver" >>>>>> then I pick the name and port from terminal and use it in paraview >>>>>> client. >>>>>> but paraview can't find the pvserver. Is there any way to establish a >>>>>> connection via these two ssh tunnels? >>>>>> >>>>>> Thanks in advance, >>>>>> Ehsan >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://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 >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> -- >>> >>> Axel Huebl >>> Diploma Student >>> Phone +49 351 260 3582 >>> https://www.hzdr.de/crp >>> Computational Radiation Physics >>> Laser Particle Acceleration Division >>> Helmholtz-Zentrum Dresden - Rossendorf e.V. >>> >>> Bautzner Landstrasse 400, 01328 Dresden >>> POB 510119, D-01314 Dresden >>> Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey >>> Prof. Dr.Dr.h.c. P. Joehnk >>> VR 1693 beim Amtsgericht Dresden >>> >>> >>> _______________________________________________ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > -- Axel Huebl Diploma Student Phone +49 351 260 3582 https://www.hzdr.de/crp Computational Radiation Physics Laser Particle Acceleration Division Helmholtz-Zentrum Dresden - Rossendorf e.V. Bautzner Landstrasse 400, 01328 Dresden POB 510119, D-01314 Dresden Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey Prof. Dr.Dr.h.c. P. Joehnk VR 1693 beim Amtsgericht Dresden -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5099 bytes Desc: S/MIME Cryptographic Signature URL: From jlih at masonlive.gmu.edu Sun Aug 24 02:31:17 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Sun, 24 Aug 2014 06:31:17 +0000 Subject: [Paraview] Usage of Octree, AMR Message-ID: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> Hi all, I have a question regarding the usage of the octree. Is it possible to create an octree structure for an array (e.g., an array from a NetCDF file)? >From the Source, I can select octree which creates a "template" octree structure. I'd like to use the octree structure to reorganize the 3D NetCDF data to make the rendering more efficient. If using octree is not possible, how about using AMR? Thanks in advance. Jing? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Sun Aug 24 06:58:41 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Sun, 24 Aug 2014 10:58:41 +0000 Subject: [Paraview] Parallel volume rendering for multiresolution data Message-ID: <1408877914655.82993@masonlive.gmu.edu> Dear all, I am wondering if Paraview supports parallel volume rendering for multi-resolution data (e.g., AMR, Multiblock). Here is what I have found so far: http://www.paraview.org/ParaView/index.php/Multi-Resolution_Rendering_with_Overlapping_AMR "When running in parallel, currently volume rendering for AMR is only supported when client-side rendering is forced i.e. we haven't added support for distributed volume rendering of AMR datasets yet. " If I want to perform parallel volume rendering for multiresolution data, what is the best solution then? Thanks, Jing -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenyiaero at gmail.com Mon Aug 25 17:30:36 2014 From: chenyiaero at gmail.com (Yi Chen) Date: Mon, 25 Aug 2014 16:30:36 -0500 Subject: [Paraview] Strange opacity behavior Message-ID: Howdy, I am using paraview 4.1.0 64bit on Ubuntu and when I play with the opacity of overlaid objects I found the behavior is interesting. Basically I would like to see the sphere through several overlaid planes (along the normal direction of the planes) , as shown below. I first uses 4 planes. [image: Inline image 1] When the sphere has an opacity of 1.0, the effect looks correct, as shown below [image: Inline image 2] But if I lower the sphere opacity for a tiny bit ( like opacity = 0.999 ), the sphere is not visible at all, as shown below [image: Inline image 3] More strangely, when I use 3 planes instead of 4. The behavior looks normal. I mean when I adjust the sphere opacity I can always see the sphere unless the opacity is too low. [image: Inline image 4] Anyone has similar experience and happens to know why? Thanks! Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 60283 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 134156 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 20997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 47124 bytes Desc: not available URL: From kmorel at sandia.gov Mon Aug 25 18:05:55 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 25 Aug 2014 22:05:55 +0000 Subject: [Paraview] Strange opacity behavior In-Reply-To: References: Message-ID: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> Yi, I can explain exactly why this is happening. ParaView uses a technique called depth peeling to render transparent surfaces. The basic idea is to render multiple times, peeling away the top layer every time. The more peels you do, the more time it takes to render, so ParaView has a limit to the number of peels it will do for a render. By default, the number of peels is set to 4. That number is somewhat arbitrary but usually works OK. What is happening to you is that because you have 4 planes, you are using all of your peels on those planes. When the sphere is completely opaque, it does not participate in depth peeling and is always rendered. When you add even a little bit of transparency, it becomes part of the depth peeling, and then gets dumped after the 4 planes. When you reduce the number of planes to 3, the depth peeling makes it all the way to the sphere. You can control the depth of the depth peeling by going to ParaView settings under Rendering -> General. You will see an option named Number of Peels that is set to 4. Increase it to 5 to see the sphere. Increase it to 6 to see the back of the sphere. -Ken Kenneth Moreland Sandia National Laboratories email: kmorel at sandia.gov phone: (505) 844-8919 web: http://www.sandia.gov/~kmorel ________________________________ From: ParaView on behalf of Yi Chen Sent: Monday, August 25, 2014 3:30 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Strange opacity behavior Howdy, I am using paraview 4.1.0 64bit on Ubuntu and when I play with the opacity of overlaid objects I found the behavior is interesting. Basically I would like to see the sphere through several overlaid planes (along the normal direction of the planes) , as shown below. I first uses 4 planes. [Inline image 1] When the sphere has an opacity of 1.0, the effect looks correct, as shown below [Inline image 2] But if I lower the sphere opacity for a tiny bit ( like opacity = 0.999 ), the sphere is not visible at all, as shown below [Inline image 3] More strangely, when I use 3 planes instead of 4. The behavior looks normal. I mean when I adjust the sphere opacity I can always see the sphere unless the opacity is too low. [Inline image 4] Anyone has similar experience and happens to know why? Thanks! Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 60283 bytes Desc: image.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 134156 bytes Desc: image.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 20997 bytes Desc: image.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 47124 bytes Desc: image.png URL: From chenyiaero at gmail.com Mon Aug 25 18:57:35 2014 From: chenyiaero at gmail.com (Yi Chen) Date: Mon, 25 Aug 2014 17:57:35 -0500 Subject: [Paraview] Strange opacity behavior In-Reply-To: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> References: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> Message-ID: Hi Ken, Thanks a lot for your fascinating answer. In my application of visualizing multi-floor buildings a higher peel number is necessary. However, I found I can enable or disable Depth Peeling but not to adjust the Number ( tried both Ubuntu and Windows ) [image: Inline image 1] Should I use the nightly build instead of 4.10? It seems that it is adjustable on Mac since I found the following figure on wiki, [image: Inline image 2] Yi ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 8538 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 73610 bytes Desc: not available URL: From bloring at lbl.gov Mon Aug 25 19:09:23 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 25 Aug 2014 16:09:23 -0700 Subject: [Paraview] Strange opacity behavior In-Reply-To: References: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> Message-ID: <53FBC223.4030407@lbl.gov> I have the same issue, I reported back in may http://public.kitware.com/pipermail/paraview/2014-May/031007.html On 08/25/2014 03:57 PM, Yi Chen wrote: > Hi Ken, > > Thanks a lot for your fascinating answer. In my application of > visualizing multi-floor buildings a higher peel number is necessary. > However, I found I can enable or disable Depth Peeling but not to > adjust the Number ( tried both Ubuntu and Windows ) > > Inline image 1 > > Should I use the nightly build instead of 4.10? It seems that it is > adjustable on Mac since I found the following figure on wiki, > > Inline image 2 > > Yi > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8538 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 73610 bytes Desc: not available URL: From chenyiaero at gmail.com Mon Aug 25 19:21:08 2014 From: chenyiaero at gmail.com (Yi Chen) Date: Mon, 25 Aug 2014 18:21:08 -0500 Subject: [Paraview] Strange opacity behavior In-Reply-To: <53FBC223.4030407@lbl.gov> References: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> <53FBC223.4030407@lbl.gov> Message-ID: I just tried the nightly build and now the number of peeling is adjustable. However, the rendering is not impacted at all. I guess there is a bug that the number typed here is not actually used in the code. [image: Inline image 1] On Mon, Aug 25, 2014 at 6:09 PM, Burlen Loring wrote: > I have the same issue, I reported back in may > http://public.kitware.com/pipermail/paraview/2014-May/031007.html > > > > On 08/25/2014 03:57 PM, Yi Chen wrote: > > Hi Ken, > > Thanks a lot for your fascinating answer. In my application of > visualizing multi-floor buildings a higher peel number is necessary. > However, I found I can enable or disable Depth Peeling but not to adjust > the Number ( tried both Ubuntu and Windows ) > > [image: Inline image 1] > > Should I use the nightly build instead of 4.10? It seems that it is > adjustable on Mac since I found the following figure on wiki, > > [image: Inline image 2] > > Yi > > > ? > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > -- Yi Chen, Ph.D. Senior CFD Development Engineer Altair Engineering, Inc. Austin, Texas (512) 467-0618 ext 776 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 21361 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 73610 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8538 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Aug 25 19:56:11 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 25 Aug 2014 19:56:11 -0400 Subject: [Paraview] Strange opacity behavior In-Reply-To: References: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> <53FBC223.4030407@lbl.gov> Message-ID: I verified that it does indeed work with the nightly version. Did you hit "Apply"/"Ok" on the dialog? Open Python shell and type the following: >>> v = GetActiveView() >>> print v.DepthPeeling >>> print v.MaximumNumberOfPeels What does that say? Utkarsh On Mon, Aug 25, 2014 at 7:21 PM, Yi Chen wrote: > I just tried the nightly build and now the number of peeling is > adjustable. However, the rendering is not impacted at all. I guess there is > a bug that the number typed here is not actually used in the code. > > [image: Inline image 1] > > > > On Mon, Aug 25, 2014 at 6:09 PM, Burlen Loring wrote: > >> I have the same issue, I reported back in may >> http://public.kitware.com/pipermail/paraview/2014-May/031007.html >> >> >> >> On 08/25/2014 03:57 PM, Yi Chen wrote: >> >> Hi Ken, >> >> Thanks a lot for your fascinating answer. In my application of >> visualizing multi-floor buildings a higher peel number is necessary. >> However, I found I can enable or disable Depth Peeling but not to adjust >> the Number ( tried both Ubuntu and Windows ) >> >> [image: Inline image 1] >> >> Should I use the nightly build instead of 4.10? It seems that it is >> adjustable on Mac since I found the following figure on wiki, >> >> [image: Inline image 2] >> >> Yi >> >> >> ? >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview >> >> >> > > > -- > Yi Chen, Ph.D. > Senior CFD Development Engineer > Altair Engineering, Inc. > Austin, Texas > (512) 467-0618 ext 776 > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 73610 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8538 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 21361 bytes Desc: not available URL: From chenyiaero at gmail.com Mon Aug 25 20:30:31 2014 From: chenyiaero at gmail.com (Yi Chen) Date: Mon, 25 Aug 2014 19:30:31 -0500 Subject: [Paraview] Strange opacity behavior In-Reply-To: References: <581e89be5cd24ddf82fbe9d4c268b070@ES02AMSNLNT.srn.sandia.gov> <53FBC223.4030407@lbl.gov> Message-ID: Hi Utkarsh, It seems that I didn't delete the original Paraview directory before unzip the nightly build. I redid it and now everything works like a charm. The print commands return 1 and the No. of peelings I set. Thank you again! Yi [image: Inline image 1] On Mon, Aug 25, 2014 at 6:56 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > I verified that it does indeed work with the nightly version. Did you hit > "Apply"/"Ok" on the dialog? Open Python shell and type the following: > > >>> v = GetActiveView() > >>> print v.DepthPeeling > >>> print v.MaximumNumberOfPeels > > What does that say? > > Utkarsh > > > On Mon, Aug 25, 2014 at 7:21 PM, Yi Chen wrote: > >> I just tried the nightly build and now the number of peeling is >> adjustable. However, the rendering is not impacted at all. I guess there is >> a bug that the number typed here is not actually used in the code. >> >> [image: Inline image 1] >> >> >> >> On Mon, Aug 25, 2014 at 6:09 PM, Burlen Loring wrote: >> >>> I have the same issue, I reported back in may >>> http://public.kitware.com/pipermail/paraview/2014-May/031007.html >>> >>> >>> >>> On 08/25/2014 03:57 PM, Yi Chen wrote: >>> >>> Hi Ken, >>> >>> Thanks a lot for your fascinating answer. In my application of >>> visualizing multi-floor buildings a higher peel number is necessary. >>> However, I found I can enable or disable Depth Peeling but not to adjust >>> the Number ( tried both Ubuntu and Windows ) >>> >>> [image: Inline image 1] >>> >>> Should I use the nightly build instead of 4.10? It seems that it is >>> adjustable on Mac since I found the following figure on wiki, >>> >>> [image: Inline image 2] >>> >>> Yi >>> >>> >>> ? >>> >>> >>> _______________________________________________ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >> >> >> -- >> Yi Chen, Ph.D. >> Senior CFD Development Engineer >> Altair Engineering, Inc. >> Austin, Texas >> (512) 467-0618 ext 776 >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -- Yi Chen, Ph.D. Senior CFD Development Engineer Altair Engineering, Inc. Austin, Texas (512) 467-0618 ext 776 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 73610 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 89092 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 21361 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8538 bytes Desc: not available URL: From fspaolo at gmail.com Mon Aug 25 22:11:57 2014 From: fspaolo at gmail.com (Fernando Paolo) Date: Mon, 25 Aug 2014 19:11:57 -0700 Subject: [Paraview] Independent text in Comparative View Message-ID: Hello, Is it possible to annotate independent text on each of the windows in Comparative View mode? Thank you, -fernando -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego web: fspaolo.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Tue Aug 26 03:40:29 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 26 Aug 2014 07:40:29 +0000 Subject: [Paraview] Catalyst question Message-ID: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> Dear Catalyst people I dragged out an old simulation demo I created some time ago and got it working with paraview/catalyst from git master branch - my plan was to test a live visualization of the simulation with the paraview GUI connected to the simulation. I had thought this capability was now possible, but I have not been following development closely and it looks like I was mistaken. Is it possible to visualize the simulation live - rather than just generate images (which works fine). (I had a quick skim through the user manual, but didn't see this feature mentioned). Thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Aug 26 09:33:57 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 26 Aug 2014 09:33:57 -0400 Subject: [Paraview] Catalyst question In-Reply-To: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> Message-ID: Hi John, This live capability is now available and recently has been cleaned up quite a bit. There are still a couple more small changes that are waiting a code review process before they go into the master branch. The user's guide needs an update for a bunch of new information (live, catalyst editions, zero-copy arrays) that's important for Catalyst. We're also doing some preliminary testing with a newly developed ADIOS writer for better IO performance as well. Getting back to the live viz stuff, when you create a Catalyst Python script and export it using the wizard you'll have the option to enable live viz (it's the same wizard page as the screenshot output specification). Then, while your simulation is running use the Catalyst->Connect option to connect. There are two tests (pv.CatalystLiveSetBreakpoint and pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live functionality which now includes the option to set a breakpoint in the simulation. If you get a chance to try it out, let me know what you think. Andy On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. wrote: > Dear Catalyst people > > > > I dragged out an old simulation demo I created some time ago and got it > working with paraview/catalyst from git master branch - my plan was to test > a live visualization of the simulation with the paraview GUI connected to > the simulation. I had thought this capability was now possible, but I have > not been following development closely and it looks like I was mistaken. > > > > Is it possible to visualize the simulation live - rather than just > generate images (which works fine). (I had a quick skim through the user > manual, but didn?t see this feature mentioned). > > > > Thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Tue Aug 26 09:39:32 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 26 Aug 2014 13:39:32 +0000 Subject: [Paraview] Catalyst question In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509916BFF0CE@MBX210.d.ethz.ch> Andy Thanks for the info, great news that the live stuff is ongoing. My current test uses cxx only, so I didn?t play with the python pipelines and hadn?t noticed the live viz option. I will experiment and get back to you. I saw a bunch of questions recently about doing GPU based stuff inside catalyst and it is my aim to get my cuda/piston based renderers working in-situ. I?ll let you know how I get on. If there are commits on branches you think I might want to test, please say. thanks again JB From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: 26 August 2014 15:34 To: Biddiscombe, John A. Cc: paraview at paraview.org Subject: Re: [Paraview] Catalyst question Hi John, This live capability is now available and recently has been cleaned up quite a bit. There are still a couple more small changes that are waiting a code review process before they go into the master branch. The user's guide needs an update for a bunch of new information (live, catalyst editions, zero-copy arrays) that's important for Catalyst. We're also doing some preliminary testing with a newly developed ADIOS writer for better IO performance as well. Getting back to the live viz stuff, when you create a Catalyst Python script and export it using the wizard you'll have the option to enable live viz (it's the same wizard page as the screenshot output specification). Then, while your simulation is running use the Catalyst->Connect option to connect. There are two tests (pv.CatalystLiveSetBreakpoint and pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live functionality which now includes the option to set a breakpoint in the simulation. If you get a chance to try it out, let me know what you think. Andy On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: Dear Catalyst people I dragged out an old simulation demo I created some time ago and got it working with paraview/catalyst from git master branch - my plan was to test a live visualization of the simulation with the paraview GUI connected to the simulation. I had thought this capability was now possible, but I have not been following development closely and it looks like I was mistaken. Is it possible to visualize the simulation live - rather than just generate images (which works fine). (I had a quick skim through the user manual, but didn?t see this feature mentioned). Thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Tue Aug 26 09:41:28 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 15:41:28 +0200 Subject: [Paraview] Segmentation fault Message-ID: Hi, I am writing my own plugin but each time I try to add another check box, the plugin suddenly segfaults. I have no idea why. The XML and C++ code are attached. XML: The values of this property sets the run number. C++: public: vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); void PrintSelf(ostream& os, vtkIndent indent); static ReadUALGrid *New(); vtkGetMacro(Shot,int) vtkSetMacro(Shot,int); vtkGetMacro(Run,int); vtkSetMacro(Run,int); vtkGetMacro(RefRun,int); vtkSetMacro(RefRun,int); vtkGetMacro(CPOLoad,int); vtkSetMacro(CPOLoad,int); vtkGetMacro(FieldLoadStatus,int); vtkSetMacro(FieldLoadStatus,int); protected: ReadUALGrid(); ~ReadUALGrid(){} int Shot; int Run; int RefRun; int CPOLoad; int FieldLoadStatus; I have no idea why because it worked perfectly for other check boxes. Thank you. Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 26 09:49:00 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 26 Aug 2014 09:49:00 -0400 Subject: [Paraview] [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: Girish, Can you run ParaView with your plugin through a debugger to find out where it is segfaulting? That will point out where the segfault occurs which is often a clue to why it is occurring. Thanks, Cory On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh wrote: > Hi, > > I am writing my own plugin but each time I try to add another check box, the > plugin suddenly segfaults. I have no idea why. The XML and C++ code are > attached. > > XML: > > name="FieldLoadStatus" > command="SetFieldLoadStatus" > number_of_elements="1" > default_values="0" > panel_visibility="default" > > > > The values of this property sets the run number. > > > C++: > > public: > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > void PrintSelf(ostream& os, vtkIndent indent); > > static ReadUALGrid *New(); > > vtkGetMacro(Shot,int) > vtkSetMacro(Shot,int); > > vtkGetMacro(Run,int); > vtkSetMacro(Run,int); > > vtkGetMacro(RefRun,int); > vtkSetMacro(RefRun,int); > > vtkGetMacro(CPOLoad,int); > vtkSetMacro(CPOLoad,int); > > vtkGetMacro(FieldLoadStatus,int); > vtkSetMacro(FieldLoadStatus,int); > > protected: > ReadUALGrid(); > ~ReadUALGrid(){} > > int Shot; > int Run; > int RefRun; > int CPOLoad; > int FieldLoadStatus; > > I have no idea why because it worked perfectly for other check boxes. Thank > you. > > Regards, > Girish > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Tue Aug 26 09:56:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 26 Aug 2014 09:56:22 -0400 Subject: [Paraview] Independent text in Comparative View In-Reply-To: References: Message-ID: Ah! No, alas. Mind adding a feature request to the bug tracker ( http://paraview.org/Bug. I'll see what we can do. Utkarsh On Mon, Aug 25, 2014 at 10:11 PM, Fernando Paolo wrote: > Hello, > > Is it possible to annotate independent text on each of the windows in > Comparative View mode? > > Thank you, > -fernando > > > -- > Fernando Paolo > Institute of Geophysics & Planetary Physics > Scripps Institution of Oceanography > University of California, San Diego > > web: fspaolo.net > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Tue Aug 26 09:59:51 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 15:59:51 +0200 Subject: [Paraview] [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: This is the backtrace i get when I run through gdb. Output: Program received signal SIGSEGV, Segmentation fault. 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 (gdb) bt full #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 No symbol table info available. #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, _arg=0x1b2ab39 "diy") at /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 No locals. #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, ob=0x10e3c10, method=0x1b2ab29 "SetUser", msg=..., resultStream=...) at /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 temp0 = 0x1b2ab39 "diy" op = 0x10e3c10 vtkmsg = #3 0x00002aaab1ee11c8 in vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #4 0x00002aaab1ee5102 in vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #5 0x00002aaab1ee4746 in vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #6 0x00002aaab1ee480d in vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #7 0x00002aaaae5011bb in vtkSIProperty::ProcessMessage(vtkClientServerStream&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #8 0x00002aaaae516ad7 in vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #9 0x00002aaaae517431 in vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #11 0x00002aaaae50249f in vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #12 0x00002aaaae513809 in vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #13 0x00002aaaae502e12 in vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () ---Type to continue, or q to quit--- from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #14 0x00002aaaae515765 in vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #16 0x00002aaaae4e6e32 in vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #17 0x00002aaaae4e52e7 in vtkPVSessionCore::PushState(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #18 0x00002aaaae4e2b2d in vtkPVSessionBase::PushState(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char const*, char const*, vtkSMProxy*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString const&, QString const&, pqServer*, QString const&, QString const&, QMap const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 No symbol table info available. #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, QString const&, pqServer*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 No symbol table info available. #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString const&, QString const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString const&, QString const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () ---Type to continue, or q to quit--- from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #31 0x00002aaabdc2e3b3 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #32 0x00002aaabdc347c9 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #39 0x00002aaabd87977c in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #41 0x00002aaabd89e322 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #42 0x00002aaac543960a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #44 0x00002aaac543d03c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #45 0x00002aaabe7e2ac6 in QEventDispatcherGlib::processEvents(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #46 0x00002aaabd89dfae in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 ---Type to continue, or q to quit--- No symbol table info available. #47 0x00002aaabe7b30df in QEventLoop::processEvents(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #48 0x00002aaabe7b3368 in QEventLoop::exec(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #50 0x0000000000407ac5 in main () No symbol table info available. No idea what's happening. Please help. Regards, Girish On 26 August 2014 15:49, Cory Quammen wrote: > Girish, > > Can you run ParaView with your plugin through a debugger to find out > where it is segfaulting? That will point out where the segfault occurs > which is often a clue to why it is occurring. > > Thanks, > Cory > > On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh > wrote: > > Hi, > > > > I am writing my own plugin but each time I try to add another check box, > the > > plugin suddenly segfaults. I have no idea why. The XML and C++ code are > > attached. > > > > XML: > > > > > name="FieldLoadStatus" > > command="SetFieldLoadStatus" > > number_of_elements="1" > > default_values="0" > > panel_visibility="default" > > > > > > > The values of this property sets the run number. > > > > > > C++: > > > > public: > > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > > void PrintSelf(ostream& os, vtkIndent indent); > > > > static ReadUALGrid *New(); > > > > vtkGetMacro(Shot,int) > > vtkSetMacro(Shot,int); > > > > vtkGetMacro(Run,int); > > vtkSetMacro(Run,int); > > > > vtkGetMacro(RefRun,int); > > vtkSetMacro(RefRun,int); > > > > vtkGetMacro(CPOLoad,int); > > vtkSetMacro(CPOLoad,int); > > > > vtkGetMacro(FieldLoadStatus,int); > > vtkSetMacro(FieldLoadStatus,int); > > > > protected: > > ReadUALGrid(); > > ~ReadUALGrid(){} > > > > int Shot; > > int Run; > > int RefRun; > > int CPOLoad; > > int FieldLoadStatus; > > > > I have no idea why because it worked perfectly for other check boxes. > Thank > > you. > > > > Regards, > > Girish > > > > _______________________________________________ > > Paraview-developers mailing list > > Paraview-developers at paraview.org > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Tue Aug 26 09:57:22 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 26 Aug 2014 09:57:22 -0400 Subject: [Paraview] Usage of Octree, AMR In-Reply-To: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> References: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> Message-ID: Hi Jing, So that I understand, does your NetCDF file already contain some sort of hierarchy or are you after adaptively rendering it by creating the hierarchy on the fly? Best, -berk On Sun, Aug 24, 2014 at 2:31 AM, jlih wrote: > Hi all, > > I have a question regarding the usage of the octree. Is it possible to > create an octree structure for an array (e.g., an array from a NetCDF > file)? From the Source, I can select octree which creates a > "template" octree structure. I'd like to use the octree structure to > reorganize the 3D NetCDF data to make the rendering more efficient. If > using octree is not possible, how about using AMR? > > > Thanks in advance. > > Jing? > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 26 10:09:43 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 26 Aug 2014 10:09:43 -0400 Subject: [Paraview] [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: My guess is that you have a member variable in RealUALGrid called "User" that is a char *, but you aren't initializing it to NULL in the constructor. When RealUALGrid::SetUser() is called, it checks whether the parameter string passed in is the same as the "User" member variable. Since "User" is initialized to an invalid pointer, you get the segmentation fault Cory On Tue, Aug 26, 2014 at 9:59 AM, Girish Ramesh wrote: > This is the backtrace i get when I run through gdb. > > Output: > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > (gdb) bt full > #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > No symbol table info available. > #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, > _arg=0x1b2ab39 "diy") > at > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 > No locals. > #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, ob=0x10e3c10, > method=0x1b2ab29 "SetUser", msg=..., resultStream=...) > at > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 > temp0 = 0x1b2ab39 "diy" > op = 0x10e3c10 > vtkmsg = > #3 0x00002aaab1ee11c8 in > vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, > char const*, vtkClientServerStream const&, vtkClientServerStream&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #4 0x00002aaab1ee5102 in > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #5 0x00002aaab1ee4746 in > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #6 0x00002aaab1ee480d in > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #7 0x00002aaaae5011bb in > vtkSIProperty::ProcessMessage(vtkClientServerStream&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #8 0x00002aaaae516ad7 in > vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings > const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #9 0x00002aaaae517431 in > vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, vtkPVXMLElement*) > () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #11 0x00002aaaae50249f in vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #12 0x00002aaaae513809 in > vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #13 0x00002aaaae502e12 in > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () > ---Type to continue, or q to quit--- > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #14 0x00002aaaae515765 in > vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #16 0x00002aaaae4e6e32 in > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #17 0x00002aaaae4e52e7 in > vtkPVSessionCore::PushState(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #18 0x00002aaaae4e2b2d in > vtkPVSessionBase::PushState(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char > const*, char const*, vtkSMProxy*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString > const&, QString const&, pqServer*, QString const&, QString const&, > QMap const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > No symbol table info available. > #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, > QString const&, pqServer*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > No symbol table info available. > #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString > const&, QString const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString const&, > QString const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () > ---Type to continue, or q to quit--- > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #31 0x00002aaabdc2e3b3 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #32 0x00002aaabdc347c9 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, > QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #39 0x00002aaabd87977c in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #41 0x00002aaabd89e322 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #42 0x00002aaac543960a in g_main_context_dispatch () from > /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #44 0x00002aaac543d03c in g_main_context_iteration () from > /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #45 0x00002aaabe7e2ac6 in > QEventDispatcherGlib::processEvents(QFlags) > () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #46 0x00002aaabd89dfae in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > ---Type to continue, or q to quit--- > No symbol table info available. > #47 0x00002aaabe7b30df in > QEventLoop::processEvents(QFlags) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #48 0x00002aaabe7b3368 in > QEventLoop::exec(QFlags) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #50 0x0000000000407ac5 in main () > No symbol table info available. > > > No idea what's happening. Please help. > > Regards, > Girish > > > On 26 August 2014 15:49, Cory Quammen wrote: >> >> Girish, >> >> Can you run ParaView with your plugin through a debugger to find out >> where it is segfaulting? That will point out where the segfault occurs >> which is often a clue to why it is occurring. >> >> Thanks, >> Cory >> >> On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh >> wrote: >> > Hi, >> > >> > I am writing my own plugin but each time I try to add another check box, >> > the >> > plugin suddenly segfaults. I have no idea why. The XML and C++ code are >> > attached. >> > >> > XML: >> > >> > > > name="FieldLoadStatus" >> > command="SetFieldLoadStatus" >> > number_of_elements="1" >> > default_values="0" >> > panel_visibility="default" > >> > >> > >> > The values of this property sets the run number. >> > >> > >> > C++: >> > >> > public: >> > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); >> > void PrintSelf(ostream& os, vtkIndent indent); >> > >> > static ReadUALGrid *New(); >> > >> > vtkGetMacro(Shot,int) >> > vtkSetMacro(Shot,int); >> > >> > vtkGetMacro(Run,int); >> > vtkSetMacro(Run,int); >> > >> > vtkGetMacro(RefRun,int); >> > vtkSetMacro(RefRun,int); >> > >> > vtkGetMacro(CPOLoad,int); >> > vtkSetMacro(CPOLoad,int); >> > >> > vtkGetMacro(FieldLoadStatus,int); >> > vtkSetMacro(FieldLoadStatus,int); >> > >> > protected: >> > ReadUALGrid(); >> > ~ReadUALGrid(){} >> > >> > int Shot; >> > int Run; >> > int RefRun; >> > int CPOLoad; >> > int FieldLoadStatus; >> > >> > I have no idea why because it worked perfectly for other check boxes. >> > Thank >> > you. >> > >> > Regards, >> > Girish >> > >> > _______________________________________________ >> > Paraview-developers mailing list >> > Paraview-developers at paraview.org >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > From rgirish28 at gmail.com Tue Aug 26 10:17:40 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 16:17:40 +0200 Subject: [Paraview] [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: Oh thanks Cory. A very silly error! Sorry I missed that and thanks for pointing it out. Regards, Girish On 26 August 2014 16:09, Cory Quammen wrote: > My guess is that you have a member variable in RealUALGrid called > "User" that is a char *, but you aren't initializing it to NULL in the > constructor. When RealUALGrid::SetUser() is called, it checks whether > the parameter string passed in is the same as the "User" member > variable. Since "User" is initialized to an invalid pointer, you get > the segmentation fault > > Cory > > On Tue, Aug 26, 2014 at 9:59 AM, Girish Ramesh > wrote: > > This is the backtrace i get when I run through gdb. > > > > Output: > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > > (gdb) bt full > > #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > > No symbol table info available. > > #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, > > _arg=0x1b2ab39 "diy") > > at > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 > > No locals. > > #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, > ob=0x10e3c10, > > method=0x1b2ab29 "SetUser", msg=..., resultStream=...) > > at > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 > > temp0 = 0x1b2ab39 "diy" > > op = 0x10e3c10 > > vtkmsg = > > #3 0x00002aaab1ee11c8 in > > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, > > char const*, vtkClientServerStream const&, vtkClientServerStream&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #4 0x00002aaab1ee5102 in > > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > > const&, int) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #5 0x00002aaab1ee4746 in > > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream > const&, > > int) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #6 0x00002aaab1ee480d in > > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #7 0x00002aaaae5011bb in > > vtkSIProperty::ProcessMessage(vtkClientServerStream&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #8 0x00002aaaae516ad7 in > > > vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings > > const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #9 0x00002aaaae517431 in > > vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, > vtkPVXMLElement*) > > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #11 0x00002aaaae50249f in > vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #12 0x00002aaaae513809 in > > vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #13 0x00002aaaae502e12 in > > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () > > ---Type to continue, or q to quit--- > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #14 0x00002aaaae515765 in > > vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #16 0x00002aaaae4e6e32 in > > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #17 0x00002aaaae4e52e7 in > > vtkPVSessionCore::PushState(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #18 0x00002aaaae4e2b2d in > > vtkPVSessionBase::PushState(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char > > const*, char const*, vtkSMProxy*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString > > const&, QString const&, pqServer*, QString const&, QString const&, > > QMap const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > > No symbol table info available. > > #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, > > QString const&, pqServer*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > > No symbol table info available. > > #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString > > const&, QString const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > > const*, int, void**) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString > const&, > > QString const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () > > ---Type to continue, or q to quit--- > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > > const*, int, void**) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #31 0x00002aaabdc2e3b3 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #32 0x00002aaabdc347c9 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, > > QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, > > QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, > > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () > > from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #39 0x00002aaabd87977c in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #41 0x00002aaabd89e322 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #42 0x00002aaac543960a in g_main_context_dispatch () from > > /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #44 0x00002aaac543d03c in g_main_context_iteration () from > > /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #45 0x00002aaabe7e2ac6 in > > > QEventDispatcherGlib::processEvents(QFlags) > > () > > from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #46 0x00002aaabd89dfae in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > ---Type to continue, or q to quit--- > > No symbol table info available. > > #47 0x00002aaabe7b30df in > > QEventLoop::processEvents(QFlags) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #48 0x00002aaabe7b3368 in > > QEventLoop::exec(QFlags) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #50 0x0000000000407ac5 in main () > > No symbol table info available. > > > > > > No idea what's happening. Please help. > > > > Regards, > > Girish > > > > > > On 26 August 2014 15:49, Cory Quammen wrote: > >> > >> Girish, > >> > >> Can you run ParaView with your plugin through a debugger to find out > >> where it is segfaulting? That will point out where the segfault occurs > >> which is often a clue to why it is occurring. > >> > >> Thanks, > >> Cory > >> > >> On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh > >> wrote: > >> > Hi, > >> > > >> > I am writing my own plugin but each time I try to add another check > box, > >> > the > >> > plugin suddenly segfaults. I have no idea why. The XML and C++ code > are > >> > attached. > >> > > >> > XML: > >> > > >> > >> > name="FieldLoadStatus" > >> > command="SetFieldLoadStatus" > >> > number_of_elements="1" > >> > default_values="0" > >> > panel_visibility="default" > > >> > > >> > > >> > The values of this property sets the run number. > >> > > >> > > >> > C++: > >> > > >> > public: > >> > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > >> > void PrintSelf(ostream& os, vtkIndent indent); > >> > > >> > static ReadUALGrid *New(); > >> > > >> > vtkGetMacro(Shot,int) > >> > vtkSetMacro(Shot,int); > >> > > >> > vtkGetMacro(Run,int); > >> > vtkSetMacro(Run,int); > >> > > >> > vtkGetMacro(RefRun,int); > >> > vtkSetMacro(RefRun,int); > >> > > >> > vtkGetMacro(CPOLoad,int); > >> > vtkSetMacro(CPOLoad,int); > >> > > >> > vtkGetMacro(FieldLoadStatus,int); > >> > vtkSetMacro(FieldLoadStatus,int); > >> > > >> > protected: > >> > ReadUALGrid(); > >> > ~ReadUALGrid(){} > >> > > >> > int Shot; > >> > int Run; > >> > int RefRun; > >> > int CPOLoad; > >> > int FieldLoadStatus; > >> > > >> > I have no idea why because it worked perfectly for other check boxes. > >> > Thank > >> > you. > >> > > >> > Regards, > >> > Girish > >> > > >> > _______________________________________________ > >> > Paraview-developers mailing list > >> > Paraview-developers at paraview.org > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Tue Aug 26 10:24:06 2014 From: jlih at masonlive.gmu.edu (Jing Li) Date: Tue, 26 Aug 2014 22:24:06 +0800 Subject: [Paraview] Usage of Octree, AMR In-Reply-To: References: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> Message-ID: Hi Berk, Thanks for your reply. The original Netcdf file is a regular spaced 3D dataset with a lot of filled values. I plan to reorganize the data with AMR or some other more efficient structures for rendering. I am developing Python functions to resample Netcdf files but I am not sure if this is the right direction. Any suggestions are highly appreciated. Jing > On Aug 26, 2014, at 9:57 PM, Berk Geveci wrote: > > Hi Jing, > > So that I understand, does your NetCDF file already contain some sort of hierarchy or are you after adaptively rendering it by creating the hierarchy on the fly? > > Best, > -berk > > > > >> On Sun, Aug 24, 2014 at 2:31 AM, jlih wrote: >> Hi all, >> I have a question regarding the usage of the octree. Is it possible to create an octree structure for an array (e.g., an array from a NetCDF file)? From the Source, I can select octree which creates a "template" octree structure. I'd like to use the octree structure to reorganize the 3D NetCDF data to make the rendering more efficient. If using octree is not possible, how about using AMR? >> >> Thanks in advance. >> Jing? >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rcrocker at uvm.edu Tue Aug 26 12:50:12 2014 From: rcrocker at uvm.edu (Ryan Crocker) Date: Tue, 26 Aug 2014 09:50:12 -0700 Subject: [Paraview] Iso-surfaces Message-ID: <66A355AF-6525-4F03-B46D-D277E9629A78@uvm.edu> Hi, I wanted to add a contour surface, to a contour isosurface, that is linked to my grid. So it is say, an iso-surface of Pressure = 0 but it is contour colored by hight in y. How would i go about doing that. thanks, Ryan Crocker University of Vermont, School of Engineering Mechanical Engineering Department rcrocker at uvm.edu 315-212-7331 From kmorel at sandia.gov Tue Aug 26 13:10:22 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 26 Aug 2014 17:10:22 +0000 Subject: [Paraview] Iso-surfaces In-Reply-To: <66A355AF-6525-4F03-B46D-D277E9629A78@uvm.edu> Message-ID: Ryan, I'm not sure I understand what you want, but it sounds like you want to check the box next to "Compute Scalars." If this option is on, the output of contour will contain all of the scalar fields. From there you can color by another field or apply a second contour to the surface to get curves. -Ken On 8/26/14 10:50 AM, "Ryan Crocker" wrote: >Hi, > >I wanted to add a contour surface, to a contour isosurface, that is >linked to my grid. So it is say, an iso-surface of Pressure = 0 but it >is contour colored by hight in y. How would i go about doing that. > >thanks, > >Ryan Crocker >University of Vermont, School of Engineering >Mechanical Engineering Department >rcrocker at uvm.edu >315-212-7331 > >_______________________________________________ >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 > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From kmorel at sandia.gov Tue Aug 26 14:38:55 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 26 Aug 2014 18:38:55 +0000 Subject: [Paraview] Quadrature Points filters Message-ID: In the nightly builds of ParaView I notice that there is a new filter category named Quadrature Points. Can someone briefly explain what these filters do? -Ken **** Kenneth Moreland *** Sandia National Laboratories *********** *** *** *** email: kmorel at sandia.gov ** *** ** phone: (505) 844-8919 *** web: http://www.sandia.gov/~kmorel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Tue Aug 26 15:30:25 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 26 Aug 2014 12:30:25 -0700 Subject: [Paraview] Quadrature Points filters In-Reply-To: References: Message-ID: <53FCE051.3060402@lbl.gov> Hi Ken, Those are for visualizing data at locations used internally by FE solvers. The menu category was added a while back (3.98?) when I fixed a couple of bugs reported here on the user list. The filters themselves have been around for a while. http://www.vtk.org/Wiki/images/7/78/VTK-Quadrature-Point-Design-Doc.pdf Burlen On 08/26/2014 11:38 AM, Moreland, Kenneth wrote: > In the nightly builds of ParaView I notice that there is a new filter > category named Quadrature Points. Can someone briefly explain what > these filters do? > > -Ken > > **** Kenneth Moreland > *** Sandia National Laboratories > *********** > *** *** *** email: kmorel at sandia.gov > ** *** ** phone: (505) 844-8919 > *** web: http://www.sandia.gov/~kmorel > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 27 11:23:13 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 11:23:13 -0400 Subject: [Paraview] New blog posts for ParaView Message-ID: Folks, Since I'm not sure everyone here it tracking the blog, here're a few new posts that talk about new features in ParaView posted this past month: * Improvements to Python script editors (syntax coloring, and more) [1] * ParaView technique: Curved and nicely spaced arrow glyphs [2] * Histogram View and linked selections [3] * Python Trace On-the-fly [4] * VTK/ParaView NumPy Integration [5]-[11] [1] http://www.kitware.com/blog/home/post/715 [2] http://www.kitware.com/blog/home/post/718 [3] http://www.kitware.com/blog/home/post/719 [4] http://www.kitware.com/blog/home/post/717 [5] http://www.kitware.com/blog/home/post/709 [6] http://www.kitware.com/blog/home/post/713 [7] http://www.kitware.com/blog/home/post/714 [8] http://www.kitware.com/blog/home/post/716 [9] http://www.kitware.com/blog/home/post/720 [10] http://www.kitware.com/blog/home/post/721 [11] http://www.kitware.com/blog/home/post/723 Utkarsh From utkarsh.ayachit at kitware.com Wed Aug 27 22:34:39 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 22:34:39 -0400 Subject: [Paraview] loading temporally distributed (one time step per file) Exodus (UNCLASSIFIED) In-Reply-To: References: Message-ID: I believe that should have worked. Any sample dataset that you can share? Utkarsh On Fri, Aug 22, 2014 at 11:44 AM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I am able to load spatially distributed Exodus file ok with ParaView. > However, when I load a temporally distributed Exodus file, I am missing all > the time step. What would be a proper way to load temporally distributed > Exodus file? I just picked the grouping that ParaView has when loading the > files. > > Any help is much appreciated. > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Aug 27 22:47:10 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 22:47:10 -0400 Subject: [Paraview] Support for QT5 broken with qt 5.3.X? In-Reply-To: <53E9D45C.3020105@xs4all.nl> References: <53DFD880.7070103@xs4all.nl> <53DFE756.4070309@lbl.gov> <53E1015C.10207@xs4all.nl> <53E12497.7080301@hzdr.de> <53E13290.9000503@xs4all.nl> <53E1F6AC.1090709@hzdr.de> <53E2D0C7.1080507@xs4all.nl> <53E34E50.9060705@hzdr.de> <53E9D45C.3020105@xs4all.nl> Message-ID: Qt 5 isn't officially supported yet. We've started making the changes and currently have dashboards that build against Qt 5.0/5.2. On Tue, Aug 12, 2014 at 4:46 AM, B.W.H. van Beest wrote: > Could it be that the support for Qt 5.3.x is broken in Paraview? > > When I upgraded from Qt5.2.1 to Qt5.3.1 recompiled paraview, I always > get link errors as described below. > On inspection, I noticed that symbols like > > 'qt_filedialog_existing_directory_hook' are no longer found in Qt5.3.1, whereas they still are there in Qt5.2.1. > I don't know how how ParaView implicitly uses these symbols, perhaps knows more on this. > > Kind Regadds, > Bertwim > > > > > > > On 08/07/2014 12:00 PM, Huebl, Axel wrote: >> Hm, looks like the cleanest way to get it running is to remove default >> installations of qt from the system path(s) and to specificity only one >> specific installation via environment flags. >> >> (I am suggesting something that can be achieved with a module system, >> e.g. on a cluster) >> >> Alternatively you can try to scratch all the advanced flags together >> that are still wrong and set them by hand. >> >>> What does this tell me? >> Yep, but basically it is still an environment problem. >> >> Best, >> Axel >> >> On 07.08.2014 03:05, B.W.H. van Beest wrote: >>> Hi Axel, >>> >>> setting CMAKE_PREFIX_PATH does not make a difference. The special >>> variables left that have a reference to the wrong qt installation are >>> QT_QT3SUPPORT_LIBRARY and QT3SUPPORT_LIBRARY_RELEASE variables. Qt5 >>> does no longer provide Qt4 support . >>> >>> Also QT_QTCORE_LIBRARY and QT_QDBUS and QT_GUI_LIBRARY_ are wrong .... >>> The correspinding HEADER-varinant are ok, though. >>> What does this tell me? >>> >>> Regards, >>> Bertwim >>> >>> >>> On 08/06/2014 11:34 AM, Huebl, Axel wrote: >>>> Dear Bertwim, >>>> >>>> >>>> good to hear that. >>>> >>>> sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and >>>> "LD_LIBRARY_PATH" to hint install directories to CMake modules. >>>> >>>> The compile error still looks like something got mixed - can you try >>>> again with the CMAKE_PREFIX_PATH hint? >>>> Did you verify all "advanced" variables set from the FindQt module with >>>> ccmake? >>>> >>>> >>>> Best, >>>> Axel >>>> >>>> On 05.08.2014 21:37, B.W.H. van Beest wrote: >>>>> Dear Axel, >>>>> >>>>> No I haven't. To follow-up on your suggestion, I ran ccmake again to set >>>>> this parameter. No CMAKE_PREFIX_PATH is in the list! >>>>> What I did try -and what did make a difference, was not only prepending >>>>> the path to qt5/lib to LD_LIBRARY_PATH, but also ensuring that qt/bin >>>>> was first in $PATH. This indeed has the result that all libQt5 >>>>> directories found were the correct ones. Maybe that amounts to the same? >>>>> >>>>> However, Now I have a different compile error: >>>>> >>>>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>>>> function `pqNativeFileDialogEventPlayer::start()': >>>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to >>>>> `qt_filedialog_existing_directory_hook' >>>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to >>>>> `qt_filedialog_open_filename_hook' >>>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to >>>>> `qt_filedialog_open_filenames_hook' >>>>> pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to >>>>> `qt_filedialog_save_filename_hook' >>>>> CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In >>>>> function `pqNativeFileDialogEventPlayer::stop()': >>>>> >>>>> >>>>> etc. >>>>> >>>>> Any ideas? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 08/05/2014 08:38 PM, Huebl, Axel wrote: >>>>>> Dear Bertwim, >>>>>> >>>>>> have you tried prepending/setting the >>>>>> CMAKE_PREFIX_PATH >>>>>> >>>>>> to your qt5 install dir? >>>>>> >>>>>> Best, >>>>>> Axel >>>>>> On 05.08.2014 18:07, B.W.H. van Beest wrote: >>>>>>> Hi Burien, thanks for responding. >>>>>>> >>>>>>> I have done you suggested, but to no avail. >>>>>>> Somehow, the path to the executable qmake is not sufficient to determine >>>>>>> all the other QT5 libraries. >>>>>>> Having said that, in one of the by now many attempts to get paraview >>>>>>> configured, I found that indeed the correct QT5 libraries were selected. >>>>>>> That build, however failed (missing symbol, cannot remember which one). >>>>>>> In trying to correct this is, the wrong QT5 libraries were selected by >>>>>>> ccmake. I just cannot figure out how this cmake thing works, or what I >>>>>>> can do to force it. >>>>>>> Any suggestions? >>>>>>> >>>>>>> Kind Regards, >>>>>>> Bertwim >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 08/04/2014 10:04 PM, Burlen Loring wrote: >>>>>>>> system install may be first in the linker search path. have you >>>>>>>> checked? If that's it: rm your build, and in addition to >>>>>>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to >>>>>>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run >>>>>>>> PV do the same. >>>>>>>> >>>>>>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> On my system, I have 2 installations of QT5. One is the distribution >>>>>>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other >>>>>>>>> one is a more recent version (5.3.1), which I downloaded and installed >>>>>>>>> in a different location. >>>>>>>>> Using ccmake, setting the QT version to 5, as well as setting >>>>>>>>> QT_QMAKE_EXECUTABLE to qmake of the new location, >>>>>>>>> I still see that ccmake selects of number of qt5-libraries that belong >>>>>>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more, >>>>>>>>> in fact). I can build paraview, though, and it even seems to work >>>>>>>>> (smoketest), but at program exit it segfaults. >>>>>>>>> >>>>>>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I >>>>>>>>> don't need to change all the entries by hand? >>>>>>>>> >>>>>>>>> Thanks in advance >>>>>>>>> Bertwim >>>>> >>> >>> > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Wed Aug 27 22:55:13 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 22:55:13 -0400 Subject: [Paraview] Using time in Python script In-Reply-To: References: Message-ID: You need to call either RenderView1.StillRender() or RenderView1.Update() to ensure that the view updates all pipelines shown in it after changing the AnimationTime. Utkarsh On Mon, Aug 11, 2014 at 1:55 AM, Elaine Tang wrote: > Hi, > > I have data in time that has time points like > {0.02124,0.04248,0.06372,0.08496, etc.} > > I wrote a python script to loop through these time points with time > increment of 0.02124 and export as .csv. > > ---------------------------------------------- > > for x in range(1, 4): > > currentT = x*deltaT > AnimationScene1 = GetAnimationScene() > RenderView1 = GetRenderView() > AnimationScene1.AnimationTime = currentT > RenderView1.ViewTime = currentT > RenderView1.CacheKey = currentT > RenderView1.UseCache = 1 > RenderView1.UseCache = 0 > > SetActiveSource(data) > writer = CreateWriter("output.csv") > writer.FieldAssociation = "Points" > writer.UpdatePipeline() > del writer > > Render() > > ------------------------------------------ > > When I played the macro, some time points were not correctly read. (e.g. > the 4th time point spreadsheet saved data that belong to the 3rd time > point.) > > I used "start trace" to see how paraview handles time, and here is what I > caught: > > -------------------------------------------------------- > try: paraview.simple > except: from paraview.simple import * > paraview.simple._DisableFirstRenderCameraReset() > > AnimationScene1 = GetAnimationScene() > RenderView1 = GetRenderView() > AnimationScene1.AnimationTime = 0.021239999681711197 > > RenderView1.ViewTime = 0.021239999681711197 > RenderView1.CacheKey = 0.021239999681711197 > RenderView1.UseCache = 1 > > AnimationScene1.AnimationTime = 0.042479999363422394 > > RenderView1.ViewTime = 0.042479999363422394 > RenderView1.CacheKey = 0.042479999363422394 > RenderView1.UseCache = 1 > > AnimationScene1.AnimationTime = 0.06372000277042389 > > RenderView1.ViewTime = 0.06372000277042389 > RenderView1.CacheKey = 0.06372000277042389 > RenderView1.UseCache = 1 > > AnimationScene1.AnimationTime = 0.08495999872684479 > > RenderView1.ViewTime = 0.08495999872684479 > RenderView1.CacheKey = 0.08495999872684479 > RenderView1.UseCache = 1 > > RenderView1.UseCache = 0 > > Render() > -------------------------------------------------------- > Then I realized, if I tried to read data at 0.08496, it will read data from > the previous time point instead. If I explicitly specify in my script to > read data at time 0.08495999872684479, then it will read the correct data. > > Anyone has any insights? > Thanks in advance!!! > > -- > Elaine > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Aug 27 23:03:03 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 23:03:03 -0400 Subject: [Paraview] Nightly Downloads for ParaView Lion-Python27 broken In-Reply-To: References: Message-ID: Ken, I just confirmed that this seems to be working again. Let me know if that not the case still. Utkarsh On Thu, Aug 7, 2014 at 9:55 AM, Moreland, Kenneth wrote: > The downloads for the nightly Mac OS build of > ParaView-Darwin-64bit-Lion-Python27-NIGHTLY.dmg appear to be broken on the > paraview.org web page. When I download the file using the "Releases" form, I > get what appears to be a 4.1 build instead of the nightly. If I download the > file using the "Nightly Builds" form, I get a corrupt or incomplete file. > > Both methods of downloading the other nightly Mac OS build seem to work > fine. > > -Ken > > **** Kenneth Moreland > *** Sandia National Laboratories > *********** > *** *** *** email: kmorel at sandia.gov > ** *** ** phone: (505) 844-8919 > *** web: http://www.sandia.gov/~kmorel > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Thu Aug 28 01:14:46 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 01:14:46 -0400 Subject: [Paraview] ParaView using Homebrew for OsX Message-ID: Folks, As an experiment, homebrew build script for ParaView available at https://github.com/utkarshayachit/paraview-homebrew Haven't really tested it throughly or added options like building the SDK (which I think will be very useful) etc. Figured I'd put it out there, have people test it and then update it as needed before contributing it to homebrew-science. Utkarsh From berk.geveci at kitware.com Thu Aug 28 10:25:43 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 28 Aug 2014 10:25:43 -0400 Subject: [Paraview] Usage of Octree, AMR In-Reply-To: References: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> Message-ID: Hi Jing, I did not drop this. I will get back to you soon with some info. Best, -berk On Tue, Aug 26, 2014 at 10:24 AM, Jing Li wrote: > Hi Berk, > Thanks for your reply. The original Netcdf file is a regular spaced 3D > dataset with a lot of filled values. I plan to reorganize the data with > AMR or some other more efficient structures for rendering. I am developing > Python functions to resample Netcdf files but I am not sure if this is the > right direction. > > Any suggestions are highly appreciated. > > Jing > > On Aug 26, 2014, at 9:57 PM, Berk Geveci wrote: > > Hi Jing, > > So that I understand, does your NetCDF file already contain some sort of > hierarchy or are you after adaptively rendering it by creating the > hierarchy on the fly? > > Best, > -berk > > > > > On Sun, Aug 24, 2014 at 2:31 AM, jlih wrote: > >> Hi all, >> >> I have a question regarding the usage of the octree. Is it possible to >> create an octree structure for an array (e.g., an array from a NetCDF >> file)? From the Source, I can select octree which creates a >> "template" octree structure. I'd like to use the octree structure to >> reorganize the 3D NetCDF data to make the rendering more efficient. If >> using octree is not possible, how about using AMR? >> >> >> Thanks in advance. >> >> Jing? >> >> >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Aug 28 10:40:51 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 28 Aug 2014 14:40:51 +0000 Subject: [Paraview] Nightly Downloads for ParaView Lion-Python27 broken In-Reply-To: Message-ID: Yup. That build looks like it is being updated now. I haven't checked the other ParaView binary, though. -Ken On 8/27/14 9:03 PM, "Utkarsh Ayachit" wrote: >Ken, > >I just confirmed that this seems to be working again. Let me know if >that not the case still. > >Utkarsh > >On Thu, Aug 7, 2014 at 9:55 AM, Moreland, Kenneth >wrote: >> The downloads for the nightly Mac OS build of >> ParaView-Darwin-64bit-Lion-Python27-NIGHTLY.dmg appear to be broken on >>the >> paraview.org web page. When I download the file using the "Releases" >>form, I >> get what appears to be a 4.1 build instead of the nightly. If I >>download the >> file using the "Nightly Builds" form, I get a corrupt or incomplete >>file. >> >> Both methods of downloading the other nightly Mac OS build seem to work >> fine. >> >> -Ken >> >> **** Kenneth Moreland >> *** Sandia National Laboratories >> *********** >> *** *** *** email: kmorel at sandia.gov >> ** *** ** phone: (505) 844-8919 >> *** web: http://www.sandia.gov/~kmorel >> >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From ganesh.iitm at gmail.com Thu Aug 28 11:53:00 2014 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Thu, 28 Aug 2014 11:53:00 -0400 Subject: [Paraview] Programmable filter works on Slice but not on original data set Message-ID: Hello, My original dataset is an xdmf file that points to some hdf5 files. I have this piece of code in a programmable filter. It seems to work on a Slice of the original dataset, but won't work on the dataset as a whole. The original dataset is cell centered and I then pass it through a "CellDataToPointData" filter. Could anyone tell me why? I'm running Paraview 4.1 - 64 bit on a server-client mode with the server using 16 cores. I thought it might be related to the dataset being multiblock or something (I don't understand this very well). So I tried the piece of code here http://www.paraview.org/Wiki/Python_Programmable_Filter#Dealing_with_Composite_Datasets This also works on the slice.. but not on the whole dataset. #Programmable filter code below import numpy as np from paraview import vtk from paraview.vtk.dataset_adapter import numpyTovtkDataArray from scipy.interpolate import interp1d initrLoc = array([0, 2.8667, 5.6, 8.3333, 11.75, 15.85, 19.95, 24.05, 28.15, 32.25, 36.35, 40.45, 44.55, 48.65, 52.75, 56.1667, 58.9, \ 61.633, 62.9, 300.0]) initaeroTwist = array([13.308, 13.308, 13.308, 13.308, 13.308, 11.48, 10.162, 9.011, 7.795, 6.544, 5.361, 4.188, 3.125, 2.319, 1.526, \ 0.863, 0.37, 0.106, 0, 0.0]) pitch = 8.7 aeroTwistInterp = interp1d(initrLoc, initaeroTwist+pitch) uxym = np.loadtxt('uxym') umeanInterp = interp1d(uxym[:,2], uxym[:,0]*cos(21.6*np.pi/180. 0) + uxym[:,1]*sin(21.6*np.pi/180.0)) vmeanInterp = interp1d(uxym[:,2], -uxym[:,0]*sin(21.6*np.pi/180.0) + uxym[:,1]*cos(21.6*np.pi/180.0)) input = self.GetInput() output = self.GetOutput() output.ShallowCopy(input) points = inputs[0].Points[:,:] nPoints = np.size(points,0) vel = inputs[0].PointData['U'] uPrime = np.empty(np.shape(vel)) AoACyl = np.empty(np.size(vel,0)) omega = (12.0 * 2 * np.pi / 60.0) * array([1,0,0]) for i in range(nPoints): uPrime[i] = array([umeanInterp(points[i,2]),vmeanInterp(points[i,2]), 0.0]) r = array([0, 15, 0]) localTwist = aeroTwistInterp(15) newVel = vel[i] - np.cross(omega, r) AoACyl[i] = arctan2(newVel[0,1],-newVel[0,2])*180/np.pi - localTwist uPrimeVTK = numpyTovtkDataArray(uPrime) uPrimeVTK.SetName('uPrime') output.GetPointData().AddArray(uPrimeVTK) AoACylVTK = numpyTovtkDataArray(AoACyl) AoACylVTK.SetName('AoACyl') output.GetPointData().AddArray(AoACylVTK) -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 28 11:58:53 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 11:58:53 -0400 Subject: [Paraview] selection by coordinates In-Reply-To: <1407049486.263118.25860.28147@mail.rambler.ru> References: <1407049486.263118.25860.28147@mail.rambler.ru> Message-ID: That is indeed a thing that's lost currently. I'm planning to add it back for 4.2. Utkarsh On Sun, Aug 3, 2014 at 3:04 AM, Van wrote: > > I know how to select a cell manually and plot a quantity in the selection > over time. > After that I can find the selection through "Find Data" menu since > "Selection Inspector" is no more available. > > But what if I know exactly the coordinates of a point which I want to select > and I do not want to guest where it is visually? > Is it possible? > > Thank you, > Van > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From simon.m.su.ctr at mail.mil Thu Aug 28 12:22:49 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 28 Aug 2014 16:22:49 +0000 Subject: [Paraview] ParaView Web not compiling Message-ID: Hello, while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not superbuild, I am not able to make it through all the way if I don't disable ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. Is qt version (I am using qt version 4.8.5) an issue here? If so, what is the qt version that I should be using? or this is just a temporary state that will eventually go away in the next PV release? If I turn off ParaView web, what feature will not be available? Will catalyst be affected? I saw a demo once of catalyst via ParaView web. thanks -simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 28 12:51:55 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 12:51:55 -0400 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: Simon, What errors are you getting? It is definitely a temporary issue and will be fixed, however we're not seeing it on the dashboards so would help to see the errors. Qt version is certainly not the issue. 4.8.5 is indeed supported Disabling Web will not affect catalyst. The ParaViewWeb+Catalyst demo also is a little independent since the catalyst part in that case doesn't really need the web components. Utkarsh On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Hello, > > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not > superbuild, I am not able to make it through all the way if I don't disable > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. > > Is qt version (I am using qt version 4.8.5) an issue here? If so, what is > the qt version that I should be using? or this is just a temporary state > that will eventually go away in the next PV release? > > If I turn off ParaView web, what feature will not be available? Will > catalyst be affected? I saw a demo once of catalyst via ParaView web. > > thanks > -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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From andy.bauer at kitware.com Thu Aug 28 12:57:43 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 28 Aug 2014 12:57:43 -0400 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: I was getting similar errors on a Cray machine. It seemed to be Python related, if I remember correctly. When I turned off building ParaView Web it went away. For me it was building without the Qt GUI. My CMake settings for the build were: ========= cmake -DCMAKE_C_COMPILER:FILEPATH=/ opt/gcc/4.8.2/bin/gcc \ -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ -DBUILD_SHARED_LIBS:BOOL=OFF \ -DBUILD_TESTING:BOOL=OFF \ -DCMAKE_BUILD_TYPE:STRING=Release \ -DOSMESA_INCLUDE_DIR:PATH=/ usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a \ -DVISIT_BUILD_READER_GMV:BOOL=OFF \ -DENABLE_MPI4PY:BOOL=ON \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DPARAVIEW_USE_MPI:BOOL=ON \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a \ -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ ../ParaView ============ On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Simon, > > What errors are you getting? It is definitely a temporary issue and > will be fixed, however we're not seeing it on the dashboards so would > help to see the errors. Qt version is certainly not the issue. 4.8.5 > is indeed supported Disabling Web will not affect catalyst. The > ParaViewWeb+Catalyst demo also is a little independent since the > catalyst part in that case doesn't really need the web components. > > Utkarsh > > > On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) > wrote: > > Hello, > > > > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not > > superbuild, I am not able to make it through all the way if I don't > disable > > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. > > > > Is qt version (I am using qt version 4.8.5) an issue here? If so, what is > > the qt version that I should be using? or this is just a temporary state > > that will eventually go away in the next PV release? > > > > If I turn off ParaView web, what feature will not be available? Will > > catalyst be affected? I saw a demo once of catalyst via ParaView web. > > > > thanks > > -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 > > > > Follow this link to subscribe/unsubscribe: > > http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 28 13:00:26 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 13:00:26 -0400 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: Andy, Can you elaborate on what the errors were? We should fix those. Utkarsh On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer wrote: > I was getting similar errors on a Cray machine. It seemed to be Python > related, if I remember correctly. When I turned off building ParaView Web it > went away. For me it was building without the Qt GUI. My CMake settings for > the build were: > ========= > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > opt/gcc/4.8.2/bin/gcc \ > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ > -DBUILD_SHARED_LIBS:BOOL=OFF \ > -DBUILD_TESTING:BOOL=OFF \ > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DOSMESA_INCLUDE_DIR:PATH=/ > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > \ > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > -DENABLE_MPI4PY:BOOL=ON \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > \ > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > \ > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > \ > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > ../ParaView > ============ > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > wrote: >> >> Simon, >> >> What errors are you getting? It is definitely a temporary issue and >> will be fixed, however we're not seeing it on the dashboards so would >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >> is indeed supported Disabling Web will not affect catalyst. The >> ParaViewWeb+Catalyst demo also is a little independent since the >> catalyst part in that case doesn't really need the web components. >> >> Utkarsh >> >> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >> wrote: >> > Hello, >> > >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not >> > superbuild, I am not able to make it through all the way if I don't >> > disable >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >> > >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what >> > is >> > the qt version that I should be using? or this is just a temporary >> > state >> > that will eventually go away in the next PV release? >> > >> > If I turn off ParaView web, what feature will not be available? Will >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. >> > >> > thanks >> > -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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > From sebastien.jourdain at kitware.com Thu Aug 28 13:11:54 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 28 Aug 2014 11:11:54 -0600 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: Just out of curiosity, do you try to build ParaView with Python 2.6? If that's the case, that could make sense as ParaViewWeb require Python 2.7 but I've only saw that error at run time. Seeing the error could certainly help. Seb On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Andy, > > Can you elaborate on what the errors were? We should fix those. > > Utkarsh > > On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer > wrote: > > I was getting similar errors on a Cray machine. It seemed to be Python > > related, if I remember correctly. When I turned off building ParaView > Web it > > went away. For me it was building without the Qt GUI. My CMake settings > for > > the build were: > > ========= > > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > > opt/gcc/4.8.2/bin/gcc \ > > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ > > -DBUILD_SHARED_LIBS:BOOL=OFF \ > > -DBUILD_TESTING:BOOL=OFF \ > > -DCMAKE_BUILD_TYPE:STRING=Release \ > > -DOSMESA_INCLUDE_DIR:PATH=/ > > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > > > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > > \ > > > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > > -DENABLE_MPI4PY:BOOL=ON \ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > > -DPARAVIEW_USE_MPI:BOOL=ON \ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > > > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > > \ > > > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > > > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ > > > > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > > \ > > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > > > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > > \ > > > > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > > ../ParaView > > ============ > > > > > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > > wrote: > >> > >> Simon, > >> > >> What errors are you getting? It is definitely a temporary issue and > >> will be fixed, however we're not seeing it on the dashboards so would > >> help to see the errors. Qt version is certainly not the issue. 4.8.5 > >> is indeed supported Disabling Web will not affect catalyst. The > >> ParaViewWeb+Catalyst demo also is a little independent since the > >> catalyst part in that case doesn't really need the web components. > >> > >> Utkarsh > >> > >> > >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) > >> wrote: > >> > Hello, > >> > > >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - > not > >> > superbuild, I am not able to make it through all the way if I don't > >> > disable > >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. > >> > > >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what > >> > is > >> > the qt version that I should be using? or this is just a temporary > >> > state > >> > that will eventually go away in the next PV release? > >> > > >> > If I turn off ParaView web, what feature will not be available? Will > >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. > >> > > >> > thanks > >> > -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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://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 > >> > >> Follow this link to subscribe/unsubscribe: > >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Thu Aug 28 13:18:24 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 28 Aug 2014 17:18:24 +0000 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: , Message-ID: Sorry to have call qt out... I also think it is Python.. I have Python 2.6.6 on my desktop and Python 2.6.9 on the new crays (lightning) at afrl that I am running the build. If Python 2.7 is a must, is there a work around? I doubt that they will update python on the crays just because I asked.... :) but garnet also has Python 2.6.9 and Andy was able to build ok? Andy? ============================= error on crays with mesa build ========== [ 5%] Compiling Python package 'web' Listing /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web ... Compiling /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py ... SyntaxError: ('invalid syntax', ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Sebastien Jourdain [sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 1:11 PM To: Utkarsh Ayachit Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling Just out of curiosity, do you try to build ParaView with Python 2.6? If that's the case, that could make sense as ParaViewWeb require Python 2.7 but I've only saw that error at run time. Seeing the error could certainly help. Seb On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit > wrote: Andy, Can you elaborate on what the errors were? We should fix those. Utkarsh On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer > wrote: > I was getting similar errors on a Cray machine. It seemed to be Python > related, if I remember correctly. When I turned off building ParaView Web it > went away. For me it was building without the Qt GUI. My CMake settings for > the build were: > ========= > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > opt/gcc/4.8.2/bin/gcc \ > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ > -DBUILD_SHARED_LIBS:BOOL=OFF \ > -DBUILD_TESTING:BOOL=OFF \ > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DOSMESA_INCLUDE_DIR:PATH=/ > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > \ > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > -DENABLE_MPI4PY:BOOL=ON \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > \ > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > \ > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > \ > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > ../ParaView > ============ > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > > wrote: >> >> Simon, >> >> What errors are you getting? It is definitely a temporary issue and >> will be fixed, however we're not seeing it on the dashboards so would >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >> is indeed supported Disabling Web will not affect catalyst. The >> ParaViewWeb+Catalyst demo also is a little independent since the >> catalyst part in that case doesn't really need the web components. >> >> Utkarsh >> >> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >> > wrote: >> > Hello, >> > >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not >> > superbuild, I am not able to make it through all the way if I don't >> > disable >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >> > >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what >> > is >> > the qt version that I should be using? or this is just a temporary >> > state >> > that will eventually go away in the next PV release? >> > >> > If I turn off ParaView web, what feature will not be available? Will >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. >> > >> > thanks >> > -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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Aug 28 13:32:02 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 28 Aug 2014 11:32:02 -0600 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: Are you targeting ParaViewWeb server on your Cray? If not, you can safely disable it. Otherwise, you may need to build your own Python along ParaView like we do in our ParaView binaries. Seb On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Sorry to have call qt out... I also think it is Python.. I have Python > 2.6.6 on my desktop and > Python 2.6.9 on the new crays (lightning) at afrl that I am running the > build. > > If Python 2.7 is a must, is there a work around? I doubt that they will > update python on the crays just because I asked.... :) > > but garnet also has Python 2.6.9 and Andy was able to build ok? Andy? > > ============================= error on crays with mesa build ========== > > [ 5%] Compiling Python package 'web' > Listing > /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web > ... > Compiling > /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py > ... > SyntaxError: ('invalid syntax', > ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', > 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in > enumerate(test_module_browsers)})\n')) > > gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 > gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2 > gmake[4]: *** Waiting for unfinished jobs.... > > > > ------------------------------ > *From:* ParaView [paraview-bounces at paraview.org] on behalf of Sebastien > Jourdain [sebastien.jourdain at kitware.com] > *Sent:* Thursday, August 28, 2014 1:11 PM > *To:* Utkarsh Ayachit > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] ParaView Web not compiling > > Just out of curiosity, do you try to build ParaView with Python 2.6? > > If that's the case, that could make sense as ParaViewWeb require Python > 2.7 but I've only saw that error at run time. > > Seeing the error could certainly help. > > Seb > > > On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Andy, >> >> Can you elaborate on what the errors were? We should fix those. >> >> Utkarsh >> >> On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer >> wrote: >> > I was getting similar errors on a Cray machine. It seemed to be Python >> > related, if I remember correctly. When I turned off building ParaView >> Web it >> > went away. For me it was building without the Qt GUI. My CMake settings >> for >> > the build were: >> > ========= >> > cmake -DCMAKE_C_COMPILER:FILEPATH=/ >> > opt/gcc/4.8.2/bin/gcc \ >> > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ >> > -DBUILD_SHARED_LIBS:BOOL=OFF \ >> > -DBUILD_TESTING:BOOL=OFF \ >> > -DCMAKE_BUILD_TYPE:STRING=Release \ >> > -DOSMESA_INCLUDE_DIR:PATH=/ >> > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ >> > >> > >> -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a >> > \ >> > >> > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ >> > -DENABLE_MPI4PY:BOOL=ON \ >> > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ >> > -DPARAVIEW_USE_MPI:BOOL=ON \ >> > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ >> > >> > >> -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include >> > \ >> > >> > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ >> > >> > >> -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ >> > >> > >> -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so >> > \ >> > -DOPENGL_gl_LIBRARY:FILEPATH= \ >> > >> > >> -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a >> > \ >> > >> > >> -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include >> > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ >> > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ >> > ../ParaView >> > ============ >> > >> > >> > >> > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> Simon, >> >> >> >> What errors are you getting? It is definitely a temporary issue and >> >> will be fixed, however we're not seeing it on the dashboards so would >> >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >> >> is indeed supported Disabling Web will not affect catalyst. The >> >> ParaViewWeb+Catalyst demo also is a little independent since the >> >> catalyst part in that case doesn't really need the web components. >> >> >> >> Utkarsh >> >> >> >> >> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >> >> wrote: >> >> > Hello, >> >> > >> >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - >> not >> >> > superbuild, I am not able to make it through all the way if I don't >> >> > disable >> >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >> >> > >> >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, >> what >> >> > is >> >> > the qt version that I should be using? or this is just a temporary >> >> > state >> >> > that will eventually go away in the next PV release? >> >> > >> >> > If I turn off ParaView web, what feature will not be available? Will >> >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. >> >> > >> >> > thanks >> >> > -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 >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://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 >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Thu Aug 28 13:43:37 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 28 Aug 2014 17:43:37 +0000 Subject: [Paraview] ParaView Web not compiling (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Seb, Nope. I think we are good to disable ParaViewWeb from the compile for now. By "building your own Python", do you mean doing the superbuild? I think I am doing the superbuild on lightning. I will try again with -DUSE_SYSTEM_python=OFF Thanks -simon -----Original Message----- From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 1:32 PM To: Su, Simon M CTR USARMY ARL (US) Cc: Utkarsh Ayachit; Andy Bauer [andy.bauer at kitware.com]; paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling Are you targeting ParaViewWeb server on your Cray? If not, you can safely disable it. Otherwise, you may need to build your own Python along ParaView like we do in our ParaView binaries. Seb On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) wrote: Sorry to have call qt out... I also think it is Python.. I have Python 2.6.6 on my desktop and Python 2.6.9 on the new crays (lightning) at afrl that I am running the build. If Python 2.7 is a must, is there a work around? I doubt that they will update python on the crays just because I asked.... :) but garnet also has Python 2.6.9 and Andy was able to build ok? Andy? ============================= error on crays with mesa build ========== [ 5%] Compiling Python package 'web' Listing /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web ... Compiling /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py ... SyntaxError: ('invalid syntax', ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Sebastien Jourdain [sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 1:11 PM To: Utkarsh Ayachit Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling Just out of curiosity, do you try to build ParaView with Python 2.6? If that's the case, that could make sense as ParaViewWeb require Python 2.7 but I've only saw that error at run time. Seeing the error could certainly help. Seb On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit wrote: Andy, Can you elaborate on what the errors were? We should fix those. Utkarsh On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer wrote: > I was getting similar errors on a Cray machine. It seemed to be Python > related, if I remember correctly. When I turned off building ParaView Web it > went away. For me it was building without the Qt GUI. My CMake settings for > the build were: > ========= > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > opt/gcc/4.8.2/bin/gcc \ > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ > -DBUILD_SHARED_LIBS:BOOL=OFF \ > -DBUILD_TESTING:BOOL=OFF \ > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DOSMESA_INCLUDE_DIR:PATH=/ > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > \ > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > -DENABLE_MPI4PY:BOOL=ON \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > \ > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > \ > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > \ > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > ../ParaView > ============ > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > wrote: >> >> Simon, >> >> What errors are you getting? It is definitely a temporary issue and >> will be fixed, however we're not seeing it on the dashboards so would >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >> is indeed supported Disabling Web will not affect catalyst. The >> ParaViewWeb+Catalyst demo also is a little independent since the >> catalyst part in that case doesn't really need the web components. >> >> Utkarsh >> >> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >> wrote: >> > Hello, >> > >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not >> > superbuild, I am not able to make it through all the way if I don't >> > disable >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >> > >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what >> > is >> > the qt version that I should be using? or this is just a temporary >> > state >> > that will eventually go away in the next PV release? >> > >> > If I turn off ParaView web, what feature will not be available? Will >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. >> > >> > thanks >> > -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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From sebastien.jourdain at kitware.com Thu Aug 28 14:13:38 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 28 Aug 2014 12:13:38 -0600 Subject: [Paraview] ParaView Web not compiling (UNCLASSIFIED) In-Reply-To: References: Message-ID: Hi Simon, You are correct that's what I meant. However, I was wondering if you are doing a static build of ParaView. We are investigating that issue and see how we can smooth (automate) that process. Thanks, Seb On Thu, Aug 28, 2014 at 11:43 AM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hi Seb, > > Nope. I think we are good to disable ParaViewWeb from the compile for now. > > By "building your own Python", do you mean doing the superbuild? I think I > am > doing the superbuild on lightning. I will try again > with -DUSE_SYSTEM_python=OFF > > > Thanks > -simon > > -----Original Message----- > From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] > Sent: Thursday, August 28, 2014 1:32 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: Utkarsh Ayachit; Andy Bauer [andy.bauer at kitware.com]; > paraview at paraview.org > Subject: Re: [Paraview] ParaView Web not compiling > > Are you targeting ParaViewWeb server on your Cray? If not, you can safely > disable it. > > Otherwise, you may need to build your own Python along ParaView like we do > in > our ParaView binaries. > > Seb > > > On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) > wrote: > > > Sorry to have call qt out... I also think it is Python.. I have > Python 2.6.6 > on my desktop and > Python 2.6.9 on the new crays (lightning) at afrl that I am > running the > build. > > If Python 2.7 is a must, is there a work around? I doubt that they > will > update python on the crays just because I asked.... :) > > but garnet also has Python 2.6.9 and Andy was able to build ok? > Andy? > > ============================= error on crays with mesa build > ========== > > [ 5%] Compiling Python package 'web' > Listing > > /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web > ... > Compiling > > /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py > ... > SyntaxError: ('invalid syntax', > > ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', > 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in > enumerate(test_module_browsers)})\n')) > > gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 > gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] > Error 2 > gmake[4]: *** Waiting for unfinished jobs.... > > > > > ________________________________ > > From: ParaView [paraview-bounces at paraview.org] on behalf of > Sebastien > Jourdain [sebastien.jourdain at kitware.com] > Sent: Thursday, August 28, 2014 1:11 PM > To: Utkarsh Ayachit > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView Web not compiling > > > Just out of curiosity, do you try to build ParaView with Python > 2.6? > > If that's the case, that could make sense as ParaViewWeb require > Python 2.7 > but I've only saw that error at run time. > > Seeing the error could certainly help. > > Seb > > > On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit > wrote: > > > Andy, > > Can you elaborate on what the errors were? We should fix > those. > > Utkarsh > > > On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer < > andy.bauer at kitware.com> wrote: > > I was getting similar errors on a Cray machine. It > seemed to be Python > > related, if I remember correctly. When I turned off > building ParaView Web > it > > went away. For me it was building without the Qt GUI. My > CMake settings > for > > the build were: > > ========= > > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > > opt/gcc/4.8.2/bin/gcc \ > > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ > \ > > -DBUILD_SHARED_LIBS:BOOL=OFF \ > > -DBUILD_TESTING:BOOL=OFF \ > > -DCMAKE_BUILD_TYPE:STRING=Release \ > > -DOSMESA_INCLUDE_DIR:PATH=/ > > > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > > > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > > \ > > > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > > -DENABLE_MPI4PY:BOOL=ON \ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > > -DPARAVIEW_USE_MPI:BOOL=ON \ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > > > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > > \ > > > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > > > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include > \ > > > > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > > \ > > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > > > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > > \ > > > > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > > ../ParaView > > ============ > > > > > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > > wrote: > >> > >> Simon, > >> > >> What errors are you getting? It is definitely a > temporary issue and > >> will be fixed, however we're not seeing it on the > dashboards so would > >> help to see the errors. Qt version is certainly not the > issue. 4.8.5 > >> is indeed supported Disabling Web will not affect > catalyst. The > >> ParaViewWeb+Catalyst demo also is a little independent > since the > >> catalyst part in that case doesn't really need the web > components. > >> > >> Utkarsh > >> > >> > >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR > USARMY ARL (US) > >> wrote: > >> > Hello, > >> > > >> > while compiling the latest ParaView for git > (4.1.0-1560-gf37ec5f) - not > >> > superbuild, I am not able to make it through all the > way if I don't > >> > disable > >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on > my cmake line. > >> > > >> > Is qt version (I am using qt version 4.8.5) an issue > here? If so, what > >> > is > >> > the qt version that I should be using? or this is > just a temporary > >> > state > >> > that will eventually go away in the next PV release? > >> > > >> > If I turn off ParaView web, what feature will not be > available? Will > >> > catalyst be affected? I saw a demo once of catalyst > via ParaView web. > >> > > >> > thanks > >> > -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 > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://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 > >> > >> Follow this link to subscribe/unsubscribe: > >> http://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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Aug 28 14:19:10 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 28 Aug 2014 14:19:10 -0400 Subject: [Paraview] ParaView Web not compiling In-Reply-To: References: Message-ID: FYI: the error I get is for the configuration I emailed with previously was: [ 99%] Compiling Python package 'web' Listing /work/acbauer/MainPVDir/build/lib/site-packages/vtk/web ... Compiling /work/acbauer/MainPVDir/build/lib/site-packages/vtk/web/testing.py ... SyntaxError: ('invalid syntax', ('/work/acbauer/MainPVDir/build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) This is for Python v2.6.8 which is the system version on Copper. I was able to get it to build properly for a similar system (Garnet) with Python v2.6.9, if that helps out. Note that I think my full CMake options didn't make it in last time. They are: =========== cmake -DCMAKE_C_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/gcc \ -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ -DBUILD_SHARED_LIBS:BOOL=OFF \ -DBUILD_TESTING:BOOL=OFF \ -DCMAKE_BUILD_TYPE:STRING=Release \ -DOSMESA_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a \ -DVISIT_BUILD_READER_GMV:BOOL=OFF \ -DENABLE_MPI4PY:BOOL=ON \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DPARAVIEW_USE_MPI:BOOL=ON \ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include \ -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so \ -DOPENGL_gl_LIBRARY:FILEPATH= \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a \ -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ -DVTK_USE_OFFSCREEN:BOOL=ON \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \ -DVTK_USE_X:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_ForceTime:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_Moments:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_Nektar:BOOL=FALSE \ -DPARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_PacMan:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=TRUE \ -DPARAVIEW_BUILD_PLUGIN_QuadView:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=OFF \ -DPARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE \ -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python2.6 \ -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.6.so \ -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ ../ParaView ================ On Thu, Aug 28, 2014 at 1:32 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Are you targeting ParaViewWeb server on your Cray? If not, you can safely > disable it. > > Otherwise, you may need to build your own Python along ParaView like we do > in our ParaView binaries. > > Seb > > > On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) < > simon.m.su.ctr at mail.mil> wrote: > >> Sorry to have call qt out... I also think it is Python.. I have Python >> 2.6.6 on my desktop and >> Python 2.6.9 on the new crays (lightning) at afrl that I am running the >> build. >> >> If Python 2.7 is a must, is there a work around? I doubt that they will >> update python on the crays just because I asked.... :) >> >> but garnet also has Python 2.6.9 and Andy was able to build ok? Andy? >> >> ============================= error on crays with mesa build ========== >> >> [ 5%] Compiling Python package 'web' >> Listing >> /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web >> ... >> Compiling >> /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py >> ... >> SyntaxError: ('invalid syntax', >> ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', >> 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in >> enumerate(test_module_browsers)})\n')) >> >> gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 >> gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2 >> gmake[4]: *** Waiting for unfinished jobs.... >> >> >> >> ------------------------------ >> *From:* ParaView [paraview-bounces at paraview.org] on behalf of Sebastien >> Jourdain [sebastien.jourdain at kitware.com] >> *Sent:* Thursday, August 28, 2014 1:11 PM >> *To:* Utkarsh Ayachit >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] ParaView Web not compiling >> >> Just out of curiosity, do you try to build ParaView with Python 2.6? >> >> If that's the case, that could make sense as ParaViewWeb require Python >> 2.7 but I've only saw that error at run time. >> >> Seeing the error could certainly help. >> >> Seb >> >> >> On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Andy, >>> >>> Can you elaborate on what the errors were? We should fix those. >>> >>> Utkarsh >>> >>> On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer >>> wrote: >>> > I was getting similar errors on a Cray machine. It seemed to be Python >>> > related, if I remember correctly. When I turned off building ParaView >>> Web it >>> > went away. For me it was building without the Qt GUI. My CMake >>> settings for >>> > the build were: >>> > ========= >>> > cmake -DCMAKE_C_COMPILER:FILEPATH=/ >>> > opt/gcc/4.8.2/bin/gcc \ >>> > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ >>> > -DBUILD_SHARED_LIBS:BOOL=OFF \ >>> > -DBUILD_TESTING:BOOL=OFF \ >>> > -DCMAKE_BUILD_TYPE:STRING=Release \ >>> > -DOSMESA_INCLUDE_DIR:PATH=/ >>> > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ >>> > >>> > >>> -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a >>> > \ >>> > >>> > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ >>> > -DENABLE_MPI4PY:BOOL=ON \ >>> > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ >>> > -DPARAVIEW_USE_MPI:BOOL=ON \ >>> > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ >>> > >>> > >>> -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include >>> > \ >>> > >>> > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ >>> > >>> > >>> -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ >>> > >>> > >>> -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so >>> > \ >>> > -DOPENGL_gl_LIBRARY:FILEPATH= \ >>> > >>> > >>> -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a >>> > \ >>> > >>> > >>> -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include >>> > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ >>> > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ >>> > ../ParaView >>> > ============ >>> > >>> > >>> > >>> > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit >>> > wrote: >>> >> >>> >> Simon, >>> >> >>> >> What errors are you getting? It is definitely a temporary issue and >>> >> will be fixed, however we're not seeing it on the dashboards so would >>> >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >>> >> is indeed supported Disabling Web will not affect catalyst. The >>> >> ParaViewWeb+Catalyst demo also is a little independent since the >>> >> catalyst part in that case doesn't really need the web components. >>> >> >>> >> Utkarsh >>> >> >>> >> >>> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >>> >> wrote: >>> >> > Hello, >>> >> > >>> >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - >>> not >>> >> > superbuild, I am not able to make it through all the way if I don't >>> >> > disable >>> >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >>> >> > >>> >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, >>> what >>> >> > is >>> >> > the qt version that I should be using? or this is just a temporary >>> >> > state >>> >> > that will eventually go away in the next PV release? >>> >> > >>> >> > If I turn off ParaView web, what feature will not be available? Will >>> >> > catalyst be affected? I saw a demo once of catalyst via ParaView >>> web. >>> >> > >>> >> > thanks >>> >> > -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 >>> >> > >>> >> > Follow this link to subscribe/unsubscribe: >>> >> > http://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 >>> >> >>> >> Follow this link to subscribe/unsubscribe: >>> >> http://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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aur.marsan at gmail.com Thu Aug 28 16:22:32 2014 From: aur.marsan at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Marsan?=) Date: Thu, 28 Aug 2014 16:22:32 -0400 Subject: [Paraview] Triangular prismatic cells not supported ? Message-ID: Dear Paraview user's, I work with an unstructured mesh, composed of tetrahedron, and prisms in the vicinity of the walls. I would like to compute the gradient of different quantities. This doesn't work, and it seems to me that this is due to the triangular prismatic cells. Do triangular prismatic cells are supported in Paraview / VTK ? Regards, Aur?lien -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Thu Aug 28 16:22:59 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 28 Aug 2014 20:22:59 +0000 Subject: [Paraview] ParaView Web not compiling (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Seb, Setting -DUSE_SYSTEM_python=OFF appears to be working now (60% done) since I got past the compile error I was having. I am not doing a static build. Yes Andy kept me in the loop for the static build and Rick is running point on that. Thanks -simon -----Original Message----- From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 2:14 PM To: Su, Simon M CTR USARMY ARL (US) Cc: Utkarsh Ayachit; Andy Bauer [andy.bauer at kitware.com]; paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling (UNCLASSIFIED) Hi Simon, You are correct that's what I meant. However, I was wondering if you are doing a static build of ParaView. We are investigating that issue and see how we can smooth (automate) that process. Thanks, Seb On Thu, Aug 28, 2014 at 11:43 AM, Su, Simon M CTR USARMY ARL (US) wrote: Classification: UNCLASSIFIED Caveats: NONE Hi Seb, Nope. I think we are good to disable ParaViewWeb from the compile for now. By "building your own Python", do you mean doing the superbuild? I think I am doing the superbuild on lightning. I will try again with -DUSE_SYSTEM_python=OFF Thanks -simon -----Original Message----- From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 1:32 PM To: Su, Simon M CTR USARMY ARL (US) Cc: Utkarsh Ayachit; Andy Bauer [andy.bauer at kitware.com]; paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling Are you targeting ParaViewWeb server on your Cray? If not, you can safely disable it. Otherwise, you may need to build your own Python along ParaView like we do in our ParaView binaries. Seb On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) wrote: Sorry to have call qt out... I also think it is Python.. I have Python 2.6.6 on my desktop and Python 2.6.9 on the new crays (lightning) at afrl that I am running the build. If Python 2.7 is a must, is there a work around? I doubt that they will update python on the crays just because I asked.... :) but garnet also has Python 2.6.9 and Andy was able to build ok? Andy? ============================= error on crays with mesa build ========== [ 5%] Compiling Python package 'web' Listing /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web ... Compiling /home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py ... SyntaxError: ('invalid syntax', ('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1 gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Sebastien Jourdain [sebastien.jourdain at kitware.com] Sent: Thursday, August 28, 2014 1:11 PM To: Utkarsh Ayachit Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Web not compiling Just out of curiosity, do you try to build ParaView with Python 2.6? If that's the case, that could make sense as ParaViewWeb require Python 2.7 but I've only saw that error at run time. Seeing the error could certainly help. Seb On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit wrote: Andy, Can you elaborate on what the errors were? We should fix those. Utkarsh On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer wrote: > I was getting similar errors on a Cray machine. It seemed to be Python > related, if I remember correctly. When I turned off building ParaView Web it > went away. For me it was building without the Qt GUI. My CMake settings for > the build were: > ========= > cmake -DCMAKE_C_COMPILER:FILEPATH=/ > opt/gcc/4.8.2/bin/gcc \ > -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \ > -DBUILD_SHARED_LIBS:BOOL=OFF \ > -DBUILD_TESTING:BOOL=OFF \ > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DOSMESA_INCLUDE_DIR:PATH=/ > usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \ > > -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a > \ > > -DVISIT_BUILD_READER_GMV:BOOL=OFF \ > -DENABLE_MPI4PY:BOOL=ON \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > > -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include > \ > > -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \ > > -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include \ > > -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so > \ > -DOPENGL_gl_LIBRARY:FILEPATH= \ > > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a > \ > > -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include > \ -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \ > ../ParaView > ============ > > > > On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit > wrote: >> >> Simon, >> >> What errors are you getting? It is definitely a temporary issue and >> will be fixed, however we're not seeing it on the dashboards so would >> help to see the errors. Qt version is certainly not the issue. 4.8.5 >> is indeed supported Disabling Web will not affect catalyst. The >> ParaViewWeb+Catalyst demo also is a little independent since the >> catalyst part in that case doesn't really need the web components. >> >> Utkarsh >> >> >> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US) >> wrote: >> > Hello, >> > >> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not >> > superbuild, I am not able to make it through all the way if I don't >> > disable >> > ParaView web using -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line. >> > >> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what >> > is >> > the qt version that I should be using? or this is just a temporary >> > state >> > that will eventually go away in the next PV release? >> > >> > If I turn off ParaView web, what feature will not be available? Will >> > catalyst be affected? I saw a demo once of catalyst via ParaView web. >> > >> > thanks >> > -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 >> > >> > Follow this link to subscribe/unsubscribe: >> > http://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 >> >> Follow this link to subscribe/unsubscribe: >> http://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 Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From ganesh.iitm at gmail.com Thu Aug 28 16:24:07 2014 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Thu, 28 Aug 2014 16:24:07 -0400 Subject: [Paraview] Programmable filter works on Slice but not on original data set In-Reply-To: References: Message-ID: Hello, I figured out that the input data set is of type vtkImage while the Slice is type Polygonal. Hence my script seems to work on the Polygonal data set. This is how you get add a vector array to a Cell based vtkImage dataset. import numpy as np from paraview.vtk.dataset_adapter import numpyTovtkDataArray output = self.GetImageDataOutput() u = inputs[0].CellData["U"] d = inputs[0].GetDimensions() dz = 2048/256.0 uPrime = np.empty([d[2],d[1],d[0],3]) print d for i in range(d[0]): for j in range(d[1]): for k in range(d[2]): uPrime[k,j,i] = np.array([0,0,k*dz + 4.0]) uPrime = uPrime.reshape((d[0]*d[1]*d[2],3)) uPrimeVTK = numpyTovtkDataArray(uPrime) uPrimeVTK.SetName('uPrime') output.GetCellData().AddArray(uPrimeVTK) On Thu, Aug 28, 2014 at 11:53 AM, Ganesh Vijayakumar wrote: > Hello, > > > My original dataset is an xdmf file that points to some hdf5 files. I > have this piece of code in a programmable filter. It seems to work on a > Slice of the original dataset, but won't work on the dataset as a whole. > The original dataset is cell centered and I then pass it through a > "CellDataToPointData" filter. Could anyone tell me why? I'm running > Paraview 4.1 - 64 bit on a server-client mode with the server using 16 > cores. I thought it might be related to the dataset being multiblock or > something (I don't understand this very well). So I tried the piece of code > here > > > http://www.paraview.org/Wiki/Python_Programmable_Filter#Dealing_with_Composite_Datasets > > This also works on the slice.. but not on the whole dataset. > > > #Programmable filter code below > > import numpy as np > from paraview import vtk > from paraview.vtk.dataset_adapter import numpyTovtkDataArray > from scipy.interpolate import interp1d > > initrLoc = array([0, 2.8667, 5.6, 8.3333, 11.75, 15.85, 19.95, 24.05, > 28.15, 32.25, 36.35, 40.45, 44.55, 48.65, 52.75, 56.1667, 58.9, \ > 61.633, 62.9, 300.0]) > initaeroTwist = array([13.308, 13.308, 13.308, 13.308, 13.308, 11.48, > 10.162, 9.011, 7.795, 6.544, 5.361, 4.188, 3.125, 2.319, 1.526, \ > 0.863, 0.37, 0.106, 0, 0.0]) > pitch = 8.7 > aeroTwistInterp = interp1d(initrLoc, initaeroTwist+pitch) > > > uxym = np.loadtxt('uxym') > umeanInterp = interp1d(uxym[:,2], uxym[:,0]*cos(21.6*np.pi/180. > 0) + uxym[:,1]*sin(21.6*np.pi/180.0)) > vmeanInterp = interp1d(uxym[:,2], -uxym[:,0]*sin(21.6*np.pi/180.0) + > uxym[:,1]*cos(21.6*np.pi/180.0)) > > input = self.GetInput() > output = self.GetOutput() > output.ShallowCopy(input) > points = inputs[0].Points[:,:] > nPoints = np.size(points,0) > vel = inputs[0].PointData['U'] > uPrime = np.empty(np.shape(vel)) > AoACyl = np.empty(np.size(vel,0)) > omega = (12.0 * 2 * np.pi / 60.0) * array([1,0,0]) > for i in range(nPoints): > uPrime[i] = array([umeanInterp(points[i,2]),vmeanInterp(points[i,2]), > 0.0]) > r = array([0, 15, 0]) > localTwist = aeroTwistInterp(15) > newVel = vel[i] - np.cross(omega, r) > AoACyl[i] = arctan2(newVel[0,1],-newVel[0,2])*180/np.pi - localTwist > > uPrimeVTK = numpyTovtkDataArray(uPrime) > uPrimeVTK.SetName('uPrime') > output.GetPointData().AddArray(uPrimeVTK) > > AoACylVTK = numpyTovtkDataArray(AoACyl) > AoACylVTK.SetName('AoACyl') > output.GetPointData().AddArray(AoACylVTK) > > > -- > ganesh > -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.mangeri at uconn.edu Thu Aug 28 17:02:44 2014 From: john.mangeri at uconn.edu (John Mangeri) Date: Thu, 28 Aug 2014 17:02:44 -0400 Subject: [Paraview] How to call a specifc data set from a multi-block ExodusII data set? Message-ID: I'm currently trying to do something simple. I have a ElementVariable q in my .e file. I read them into the pipeline with reader = ExodusIIReader(FileName = 'out.e') I want to use histogram = Histogram(q,BinCount=30) but I recieve the following error: Traceback (most recent call last): File "", line 1, in NameError: name 'q' is not defined What is going on here? Thanks John -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Aug 28 17:12:39 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 28 Aug 2014 21:12:39 +0000 Subject: [Paraview] How to call a specifc data set from a multi-block ExodusII data set? In-Reply-To: Message-ID: That's not how you use the Python Histogram function. First of all, it doesn't just assume that the first argument is the name of the input array. Second, input arrays are specified with identifiers contained in strings. The Python interpreter thinks q is the Python variable q, not the field name. Your script should look something like the following. reader = ExodusIIReader(Filename='out.e') histogram = Histogram() histogram.SelectInputArray = 'q' histogram.BinCount = 30 Try using the stack trace if you are having trouble determining the right Python functions to call. -Ken From: John Mangeri > Date: Thursday, August 28, 2014 3:02 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] How to call a specifc data set from a multi-block ExodusII data set? I'm currently trying to do something simple. I have a ElementVariable q in my .e file. I read them into the pipeline with reader = ExodusIIReader(FileName = 'out.e') I want to use histogram = Histogram(q,BinCount=30) but I recieve the following error: Traceback (most recent call last): File "", line 1, in NameError: name 'q' is not defined What is going on here? Thanks John -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 29 09:22:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 09:22:44 -0400 Subject: [Paraview] Fwd: 1D and 2D meshes in 3D space In-Reply-To: References: Message-ID: Can you provide a sample dataset? It's hard to gauge what could be going wrong from your description. Thanks Utkarsh On Fri, Aug 22, 2014 at 8:25 AM, Nils Van den Steen wrote: > When opening a vtk file, resulting from a simulation in 1D and 2D meshes but > in a 3D space (x, y and z coordinates are/can be different from 0). Paraview > doesn't show anything. Only when volumes are defined in the mesh, results > are shown (but these aren't very significant). > > The mesh I'm using consists of two parallel surfaces, connected with 1D > lines (2.5 dimensional mesh). > > Kind regards, > Nils > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Aug 29 09:26:35 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 09:26:35 -0400 Subject: [Paraview] Bad X server connection In-Reply-To: References: Message-ID: The problem is arising because your login on the remote server you're connected to doesn't have access to the X server. Is there an X server running on that system? If so, do you have access to it? If so, is your DISPLAY environment setup to point to the right display? Maybe try running a xserver of your own is possible using xvfb or vncserver. Alternatively, you can build ParaView using offscreen Mesa support (http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D). Hope that helps. Utkarsh On Fri, Aug 1, 2014 at 5:51 AM, J?r?my Santina wrote: > Hello, > > I am using ParaView 4.1.0 RC1 for Linux 64bit. I am connected via ssh and > when I am launching pvserver I get this : > > Waiting for client... > Connection URL: cs://diablo.cerfacs.fr:11111 > Accepting connection(s): diablo.cerfacs.fr:11111 > > Thus, the pvserver seems to work fine. > > But when I am trying to connect to the server, I get this error message : > > > Client connected. > No protocol specified > ERROR: In > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, > line 531 > vtkXOpenGLRenderWindow (0x130d6b0): bad X server connection. DISPLAY=:0 > > No protocol specified > ERROR: In > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, > line 322 > vtkXOpenGLRenderWindow (0x130d6b0): bad X server connection. DISPLAY=:0 > > Segmentation fault (core dumped) > > > I don't know how to fix this because I don't really know where the problem > could come from. I launched a pvserver on an other machine and I could > connect without having this issue so I guess the problem doesn't come from > my client machine. > > Do you have any hints about how to solve this ? > > Thanks. > > J?r?my > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From nivdstee at vub.ac.be Fri Aug 29 09:57:47 2014 From: nivdstee at vub.ac.be (Nils Van den Steen) Date: Fri, 29 Aug 2014 15:57:47 +0200 Subject: [Paraview] Fwd: 1D and 2D meshes in 3D space In-Reply-To: References: Message-ID: The file included as an attachment consists of 255 points. But none of them are shown in paraview. The grid consists of surfaces (2D) and lines (1D) in a 3D space. Kind regards, Nils 2014-08-29 15:22 GMT+02:00 Utkarsh Ayachit : > Can you provide a sample dataset? It's hard to gauge what could be > going wrong from your description. > > Thanks > Utkarsh > > On Fri, Aug 22, 2014 at 8:25 AM, Nils Van den Steen > wrote: > > When opening a vtk file, resulting from a simulation in 1D and 2D meshes > but > > in a 3D space (x, y and z coordinates are/can be different from 0). > Paraview > > doesn't show anything. Only when volumes are defined in the mesh, results > > are shown (but these aren't very significant). > > > > The mesh I'm using consists of two parallel surfaces, connected with 1D > > lines (2.5 dimensional mesh). > > > > Kind regards, > > Nils > > > > > > _______________________________________________ > > 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 > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview_2-5D_255points.vtk Type: application/octet-stream Size: 6520 bytes Desc: not available URL: From kmorel at sandia.gov Fri Aug 29 10:34:12 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 29 Aug 2014 14:34:12 +0000 Subject: [Paraview] Fwd: 1D and 2D meshes in 3D space In-Reply-To: Message-ID: Nils, Your problems have nothing to do with the dimensionality of your data. Rather, the problem is that your file does not define any cells, only points. The render view in ParaView shows the cells, which are defined on points, not the points themselves. To solve your problem, either add cells to your data or use the Glyph filter to create vertex cells. Change the Glyph Type to "2D Glyph", and then the glyph type of the 2D glyph as "Vertex". -Ken From: Nils Van den Steen > Date: Friday, August 29, 2014 7:57 AM To: Utkarsh Ayachit > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] Fwd: 1D and 2D meshes in 3D space The file included as an attachment consists of 255 points. But none of them are shown in paraview. The grid consists of surfaces (2D) and lines (1D) in a 3D space. Kind regards, Nils 2014-08-29 15:22 GMT+02:00 Utkarsh Ayachit >: Can you provide a sample dataset? It's hard to gauge what could be going wrong from your description. Thanks Utkarsh On Fri, Aug 22, 2014 at 8:25 AM, Nils Van den Steen > wrote: > When opening a vtk file, resulting from a simulation in 1D and 2D meshes but > in a 3D space (x, y and z coordinates are/can be different from 0). Paraview > doesn't show anything. Only when volumes are defined in the mesh, results > are shown (but these aren't very significant). > > The mesh I'm using consists of two parallel surfaces, connected with 1D > lines (2.5 dimensional mesh). > > Kind regards, > Nils > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 29 11:34:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 11:34:02 -0400 Subject: [Paraview] Unsupported Cell Attribute Type Error In VTK Legacy File Format In-Reply-To: References: Message-ID: You have too many values for "current" array. Only 104 values are expected. Everything starting with line number 386 in the line is extra. The reader reads that like and gets a "0" as the "tag" and hence it gives that error. Attached is the modified version that loads without the error. On Tue, Aug 5, 2014 at 8:49 AM, Hayan Nasser wrote: > Hello, > > I'm trying to add vector information to an animation frame which is > in the VTK Legacy file format. > > When just including the scalar information, I receive no errors when opening > the animation in paraview. > > However, now when I append the vector information to the file, I receive the > following > error: > > ERROR: In /build/buildd/paraview-3.10.1/VTK/IO/vtkDataReader.cxx, line 766 > > vtkPolyDataReader (0x39b5400): Unsupported cell attribute type: 0 for file: > cyl_res20_new/VTK/2D/DC100-material1-boundaryopen-observation10-time1e-09.1.vtk > > > I must be missing something with defining the data set, but I have followed > through the VTK file format documentation, and I can't see where I am going > wrong! > > If you could take a quick look and see if I am missing something obvious I > would be most grateful! > > Many Thanks > Hayan > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: DC100-material1-boundaryopen-observation10-time1e-09.1.vtk Type: application/x-extension-vtk Size: 3670 bytes Desc: not available URL: From andy.john.parker at googlemail.com Fri Aug 29 13:17:21 2014 From: andy.john.parker at googlemail.com (Andrew Parker) Date: Fri, 29 Aug 2014 18:17:21 +0100 Subject: [Paraview] Potential bug in vtkPolygon normal and area calculations Message-ID: Dear all, This is driving me round the bend. When I have a meshing coming from a rectilinear source, I get NANs from my normal and face area calculations. When all other input meshes are used, i.e. unstructured, the results are correct. To test this I've written the following test code which makes a single cell mesh and produces the NANs. I then demonstrate that by using the transform classes, with zero rotation, I can then extract the same mesh back as a structured grid, and the errors disappear. I can also apply a non-zero rotation and the errors disappear too. Note I apply a rotation, zero or otherwise, because my hypothesis having stepped through 6.1 in the debugger, is that the vtk_pixel cell type (axis aligned) coming from the rectilinear grid does not play well with the normal calculation. But I can't find the bug, only that all entries of the normal are zero and the rest of the function fails. Clearly, and more likely, is that I could also not be using the classes correctly, and if so please let me know?? Hope somebody can find the bug, I've got nowhere on this after a day of looking. Again, anything non-axis aligned and or non vtk_pixel would appear to work as expected. Help appreciated, Cheers again, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- cmake_minimum_required(VERSION 2.8) PROJECT(weird) set(CMAKE_COLOR_MAKEFILE ON) set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wextra -Wall -Wconversion -pedantic -Wuninitialized -std=c++11 -Wno-extra-semi") FIND_PACKAGE(VTK REQUIRED NO_MODULE) INCLUDE(${VTK_USE_FILE}) find_package(Qt5Widgets REQUIRED) set(SOURCES main.cxx) ADD_EXECUTABLE(weird ${SOURCES}) TARGET_LINK_LIBRARIES(weird ${VTK_LIBRARIES}) -------------- next part -------------- A non-text attachment was scrubbed... Name: main.cxx Type: text/x-c++src Size: 3883 bytes Desc: not available URL: From casey.goodlett at kitware.com Fri Aug 29 15:11:18 2014 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Fri, 29 Aug 2014 15:11:18 -0400 Subject: [Paraview] RGB color coding In-Reply-To: References: <53EE25CF.4020203@biomed.ee.ethz.ch> Message-ID: Hi all, I often do something similar when reading data originally from a text table. In this case I need to turn 3 arrays into a single 3-component uchar array for the purpose of RGB coloring. I found that I can also use the following python calculator expression to accomplish this goal (assuming the arrays are named 'R', 'G', 'B' respectively). This assumes the values are already scaled between 0-255. hstack([inputs[0].PointData['R'], inputs[0].PointData['G'], inputs[0].PointData['B']]).astype(uint8) -- Casey B. Goodlett, Ph.D. Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Aug 29 15:16:21 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 29 Aug 2014 15:16:21 -0400 Subject: [Paraview] RGB color coding In-Reply-To: References: <53EE25CF.4020203@biomed.ee.ethz.ch> Message-ID: FYI: With PV 4.2 you'll need to use make_vector() instead of hstack. On Fri, Aug 29, 2014 at 3:11 PM, Casey Goodlett wrote: > Hi all, > > I often do something similar when reading data originally from a text > table. In this case I need to turn 3 arrays into a single 3-component > uchar array for the purpose of RGB coloring. I found that I can also use > the following python calculator expression to accomplish this goal > (assuming the arrays are named 'R', 'G', 'B' respectively). This assumes > the values are already scaled between 0-255. > > hstack([inputs[0].PointData['R'], inputs[0].PointData['G'], > inputs[0].PointData['B']]).astype(uint8) > > -- > Casey B. Goodlett, Ph.D. > Technical Leader > Kitware, Inc. - North Carolina Office > http://www.kitware.com > (919) 969-6990 x310 > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amirsmol at gmail.com Fri Aug 29 16:49:54 2014 From: amirsmol at gmail.com (Amir Sohrabi Mollayousef) Date: Fri, 29 Aug 2014 15:49:54 -0500 Subject: [Paraview] About changing size of the font in the legend label Message-ID: Hi, I like to change the font of a label in legend in paraview. I found this nice article for customizing the legend: http://www.kitware.com/blog/home/post/578 It does give information about how numbers in legend are formatted. However, it does not give instruction how to font size for the labels in legend. Thanks -- Amir Sohrabi, PhD Student Mechanical Engineering Department Texas A&M University College Station, TX - 77843, USA -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 29 17:03:39 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 17:03:39 -0400 Subject: [Paraview] About changing size of the font in the legend label In-Reply-To: References: Message-ID: If you look at Figure 3, it has things like "Title Font Properties", "Text/Annotation Font Properties". Those would be the things to use to set the font size. On Fri, Aug 29, 2014 at 4:49 PM, Amir Sohrabi Mollayousef wrote: > Hi, > > I like to change the font of a label in legend in paraview. > I found this nice article for customizing the legend: > > http://www.kitware.com/blog/home/post/578 > > It does give information about how numbers in legend are formatted. However, > it does not give instruction how to font size for the labels in legend. > > Thanks > -- > Amir Sohrabi, PhD Student > Mechanical Engineering Department > Texas A&M University > College Station, TX - 77843, USA > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview >