From houssen at ipgp.fr Wed Mar 1 05:40:40 2017 From: houssen at ipgp.fr (houssen) Date: Wed, 01 Mar 2017 11:40:40 +0100 Subject: [Paraview-developers] =?utf-8?q?How_to_valgrind_a_paraview_plugin?= =?utf-8?q?_=3F?= Message-ID: <0c5930615e339e60719be1a9cffaec46@imap.ipgp.fr> How to valgrind a paraview plugin ? I have a paraview plugin (filter) : I would like to get an MLK analysis of it (to know about memory leaks, and more importantly, about invalid read / write). I wrote a as-short-as-possible python script (open_filter.py) that open a XDMF file and apply the filter on it. For a try, I started with: ~> valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --track-fds=yes --track-origins=yes --log-file=log.out pvbatch open_filter.py pvbatch ends the script in less than 10 seconds, but I get nothing relevant (no error) in the log.out because, as you noticed, trace children is missing (also tested with --child-silent-after-fork but it does not help: same result, no error reported). Now I add the --trace-children=yes switch to the previous command line : this fills log.out but takes more than an hour to run a so small fraction (1/8 I would say !?) of the full scenario. Conclusion: this seems to work but make the whole thing impossible to use ! I tried without success to play with --trace-children-skip. According to valgrind man (--trace-children-skip says it deals with exec), I straced the command line delegated to valgrind : ~> strace pvbatch open_filter.py I get stuffs like : execve("/path/to/pvbatch", ["pvbatch", "open_filter.py"], [/* 52 vars */]) = 0 But all shared object (plugins are .so) involved seem to be straced by an open (not a exec) : open("/lib/x86_64-linux-gnu/libc.so.6") So my understanding is that it makes --trace-children-skip not doing what I expected (not a kernel expert). Is there a way to valgrind "only plugins" (= a subset of paraview) ?... An efficient way ! Are there best pratices on the topic ? Magic command line or switch ? Documentation about that ? Any other clue ? Franck From mathieu.westphal at kitware.com Thu Mar 2 03:46:15 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 2 Mar 2017 09:46:15 +0100 Subject: [Paraview-developers] How to valgrind a paraview plugin ? In-Reply-To: <0c5930615e339e60719be1a9cffaec46@imap.ipgp.fr> References: <0c5930615e339e60719be1a9cffaec46@imap.ipgp.fr> Message-ID: Hi When valgrinding a plugin, i usually go with the full application. There is some valgrind suppression files in paraview/CMake/ParaViewValgrindSuppressions.sup It can be a bit slow, but in two/three minutes you should be able to run ParaView, load and test your plugin. If your plugin is simple a vtk filter and associated xml, you can also write a vtk code using it. Mush smaller in this case. Regards, Mathieu Westphal On Wed, Mar 1, 2017 at 11:40 AM, houssen wrote: > How to valgrind a paraview plugin ? > > I have a paraview plugin (filter) : I would like to get an MLK analysis of > it (to know about memory leaks, and more importantly, about invalid read / > write). > > I wrote a as-short-as-possible python script (open_filter.py) that open a > XDMF file and apply the filter on it. For a try, I started with: > ~> valgrind --tool=memcheck --leak-check=yes --show-reachable=yes > --track-fds=yes --track-origins=yes --log-file=log.out pvbatch > open_filter.py > pvbatch ends the script in less than 10 seconds, but I get nothing > relevant (no error) in the log.out because, as you noticed, trace children > is missing (also tested with --child-silent-after-fork but it does not > help: same result, no error reported). > > Now I add the --trace-children=yes switch to the previous command line : > this fills log.out but takes more than an hour to run a so small fraction > (1/8 I would say !?) of the full scenario. Conclusion: this seems to work > but make the whole thing impossible to use ! > > I tried without success to play with --trace-children-skip. According to > valgrind man (--trace-children-skip says it deals with exec), I straced the > command line delegated to valgrind : > ~> strace pvbatch open_filter.py > I get stuffs like : > execve("/path/to/pvbatch", ["pvbatch", "open_filter.py"], [/* 52 vars > */]) = 0 > But all shared object (plugins are .so) involved seem to be straced by an > open (not a exec) : > open("/lib/x86_64-linux-gnu/libc.so.6") > So my understanding is that it makes --trace-children-skip not doing what > I expected (not a kernel expert). > > Is there a way to valgrind "only plugins" (= a subset of paraview) ?... An > efficient way ! > Are there best pratices on the topic ? Magic command line or switch ? > Documentation about that ? Any other clue ? > > Franck > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 2 08:05:49 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Mar 2017 08:05:49 -0500 Subject: [Paraview-developers] How to valgrind a paraview plugin ? In-Reply-To: References: <0c5930615e339e60719be1a9cffaec46@imap.ipgp.fr> Message-ID: Franck, To add to what Mathieu said, the executable bin/paraview in an installed version of ParaView is simply a shared-forwarding executable that execs the executable lib/paraview-/paraview. If you do `./bin/paraview --print`, it will show the LD_LIBRARY_PATH values it sets. You can set those manually and then directly launch the ./lib/paraview-/paraview executable. Hopefully that will help clean up the log. Utkarsh On Thu, Mar 2, 2017 at 3:46 AM, Mathieu Westphal wrote: > Hi > > When valgrinding a plugin, i usually go with the full application. There is > some valgrind suppression files in > paraview/CMake/ParaViewValgrindSuppressions.sup > It can be a bit slow, but in two/three minutes you should be able to run > ParaView, load and test your plugin. > > If your plugin is simple a vtk filter and associated xml, you can also write > a vtk code using it. Mush smaller in this case. > > Regards, > > Mathieu Westphal > > On Wed, Mar 1, 2017 at 11:40 AM, houssen wrote: >> >> How to valgrind a paraview plugin ? >> >> I have a paraview plugin (filter) : I would like to get an MLK analysis of >> it (to know about memory leaks, and more importantly, about invalid read / >> write). >> >> I wrote a as-short-as-possible python script (open_filter.py) that open a >> XDMF file and apply the filter on it. For a try, I started with: >> ~> valgrind --tool=memcheck --leak-check=yes --show-reachable=yes >> --track-fds=yes --track-origins=yes --log-file=log.out pvbatch >> open_filter.py >> pvbatch ends the script in less than 10 seconds, but I get nothing >> relevant (no error) in the log.out because, as you noticed, trace children >> is missing (also tested with --child-silent-after-fork but it does not help: >> same result, no error reported). >> >> Now I add the --trace-children=yes switch to the previous command line : >> this fills log.out but takes more than an hour to run a so small fraction >> (1/8 I would say !?) of the full scenario. Conclusion: this seems to work >> but make the whole thing impossible to use ! >> >> I tried without success to play with --trace-children-skip. According to >> valgrind man (--trace-children-skip says it deals with exec), I straced the >> command line delegated to valgrind : >> ~> strace pvbatch open_filter.py >> I get stuffs like : >> execve("/path/to/pvbatch", ["pvbatch", "open_filter.py"], [/* 52 vars >> */]) = 0 >> But all shared object (plugins are .so) involved seem to be straced by an >> open (not a exec) : >> open("/lib/x86_64-linux-gnu/libc.so.6") >> So my understanding is that it makes --trace-children-skip not doing what >> I expected (not a kernel expert). >> >> Is there a way to valgrind "only plugins" (= a subset of paraview) ?... An >> efficient way ! >> Are there best pratices on the topic ? Magic command line or switch ? >> Documentation about that ? Any other clue ? >> >> Franck >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From orion at cora.nwra.com Thu Mar 2 11:14:05 2017 From: orion at cora.nwra.com (Orion Poplawski) Date: Thu, 2 Mar 2017 09:14:05 -0700 Subject: [Paraview-developers] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: <20170228134208.GA22906@megas.kitware.com> References: <20170224202044.GA12651@megas.kitware.com> <7752149c-5a47-4938-e556-d3328e9dbcb9@cora.nwra.com> <20170224203956.GA30571@megas.kitware.com> <20170224204958.GA30924@megas.kitware.com> <20170228134208.GA22906@megas.kitware.com> Message-ID: <8bbf31bd-890c-1974-380e-da4fd2ec7f8c@cora.nwra.com> On 02/28/2017 06:42 AM, Ben Boeckel wrote: > On Tue, Feb 28, 2017 at 11:38:44 +0100, Mathieu Westphal wrote: >> FYI, I have another user with the same issue. > > The `EXCLUDE_FROM_ALL` flag can be added to the `install()` command, but > this means that users who previously got the documentation are now going > to need to specifically specify that they want the documentation > installed (because ParaView has this same root problem), so I don't know > that it is a better solution. The current solution is that if you have > documentation enabled, the DoxygenDoc target must be built as well > before installation will work (same as ParaViewDoxygenDoc has been since > its beginning AFAICT). > > --Ben > I finally figured this out for the Fedora package build - I set -DBUILD_DOCUMENTATION:BOOL=ON for the serial and mpi builds, but only built the docs for the serial build. I'm now setting that only for the serial build, and have added the DoxygenDoc target to the build. Thanks. -- Orion Poplawski Technical Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 http://www.nwra.com From houssen at ipgp.fr Thu Mar 2 12:02:14 2017 From: houssen at ipgp.fr (houssen) Date: Thu, 02 Mar 2017 18:02:14 +0100 Subject: [Paraview-developers] =?utf-8?q?How_to_valgrind_a_paraview_plugin?= =?utf-8?q?_=3F?= In-Reply-To: References: <0c5930615e339e60719be1a9cffaec46@imap.ipgp.fr> Message-ID: Thanks guys, hope to get something that sounds possible with that ! :D Franck Le 2017-03-02 14:05, Utkarsh Ayachit a ?crit?: > Franck, > > To add to what Mathieu said, the executable bin/paraview in an > installed version of ParaView is simply a shared-forwarding > executable > that execs the executable lib/paraview-/paraview. If you do > `./bin/paraview --print`, it will show the LD_LIBRARY_PATH values it > sets. You can set those manually and then directly launch the > ./lib/paraview-/paraview executable. Hopefully that will > help clean up the log. > > Utkarsh > > On Thu, Mar 2, 2017 at 3:46 AM, Mathieu Westphal > wrote: >> Hi >> >> When valgrinding a plugin, i usually go with the full application. >> There is >> some valgrind suppression files in >> paraview/CMake/ParaViewValgrindSuppressions.sup >> It can be a bit slow, but in two/three minutes you should be able to >> run >> ParaView, load and test your plugin. >> >> If your plugin is simple a vtk filter and associated xml, you can >> also write >> a vtk code using it. Mush smaller in this case. >> >> Regards, >> >> Mathieu Westphal >> >> On Wed, Mar 1, 2017 at 11:40 AM, houssen wrote: >>> >>> How to valgrind a paraview plugin ? >>> >>> I have a paraview plugin (filter) : I would like to get an MLK >>> analysis of >>> it (to know about memory leaks, and more importantly, about invalid >>> read / >>> write). >>> >>> I wrote a as-short-as-possible python script (open_filter.py) that >>> open a >>> XDMF file and apply the filter on it. For a try, I started with: >>> ~> valgrind --tool=memcheck --leak-check=yes --show-reachable=yes >>> --track-fds=yes --track-origins=yes --log-file=log.out pvbatch >>> open_filter.py >>> pvbatch ends the script in less than 10 seconds, but I get nothing >>> relevant (no error) in the log.out because, as you noticed, trace >>> children >>> is missing (also tested with --child-silent-after-fork but it does >>> not help: >>> same result, no error reported). >>> >>> Now I add the --trace-children=yes switch to the previous command >>> line : >>> this fills log.out but takes more than an hour to run a so small >>> fraction >>> (1/8 I would say !?) of the full scenario. Conclusion: this seems >>> to work >>> but make the whole thing impossible to use ! >>> >>> I tried without success to play with --trace-children-skip. >>> According to >>> valgrind man (--trace-children-skip says it deals with exec), I >>> straced the >>> command line delegated to valgrind : >>> ~> strace pvbatch open_filter.py >>> I get stuffs like : >>> execve("/path/to/pvbatch", ["pvbatch", "open_filter.py"], [/* 52 >>> vars >>> */]) = 0 >>> But all shared object (plugins are .so) involved seem to be straced >>> by an >>> open (not a exec) : >>> open("/lib/x86_64-linux-gnu/libc.so.6") >>> So my understanding is that it makes --trace-children-skip not >>> doing what >>> I expected (not a kernel expert). >>> >>> Is there a way to valgrind "only plugins" (= a subset of paraview) >>> ?... An >>> efficient way ! >>> Are there best pratices on the topic ? Magic command line or switch >>> ? >>> Documentation about that ? Any other clue ? >>> >>> Franck >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From ben.boeckel at kitware.com Thu Mar 2 15:05:47 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 2 Mar 2017 15:05:47 -0500 Subject: [Paraview-developers] Code formatting checks Message-ID: <20170302200547.GA23677@megas.kitware.com> Hi there, Once this merge request has been merged: https://gitlab.kitware.com/paraview/paraview/merge_requests/1431 branches built on top of it will be checked for using `clang-format`. This will only affect branches which are based on `master` after it has been merged, so older branches may contain formatting problems that will only show up when the file is changed in a future merge request. For the next few weeks, once a week, I'll reformat `master` using the scripts to help clean up any issues that creep in due to older branches, but after that, branches should be rebased to just have this as part of its history. In the meantime, if you'd like to clean up formatting of your merge requests, there is the `Utilities/Scripts/clang-format.bash` which contains documentation on how to fix up a merge request. Note that ParaView's configuration requires a newer `clang-format` (3.8). We'll be testing the support of the robot to do reformatting for you if you'd like, but it needs some more verification before we deploy it on ParaView itself. Thanks, --Ben From christophe.bourcier.pv at gmail.com Fri Mar 3 11:11:53 2017 From: christophe.bourcier.pv at gmail.com (Christophe Bourcier) Date: Fri, 3 Mar 2017 17:11:53 +0100 Subject: [Paraview-developers] End of python 2 support? Message-ID: Hi, We would like to know if dropping python 2 support is in the roadmap of Paraview and when? So that we start thinking to migrate to Python 3 for our application based on Paraview. Thanks, Christophe From utkarsh.ayachit at kitware.com Fri Mar 3 11:21:41 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 3 Mar 2017 11:21:41 -0500 Subject: [Paraview-developers] End of python 2 support? In-Reply-To: References: Message-ID: There's no immediate plan to drop Python 2 support. The upcoming ParaView 5.3 is the first release that supports Python 3 officially (except for ParaViewWeb components). So I'd expect we're at least a couple of releases away, if not more, before we drop Python 2 support entirely. Python 2 is still the Python version used in binaries that will be distributed for ParaView 5.3. What's more near term in dropping support for would be legacy OpenGL rendering backend and Qt 4 (not necessarily in that order). Utkarsh On Fri, Mar 3, 2017 at 11:11 AM, Christophe Bourcier < christophe.bourcier.pv at gmail.com> wrote: > Hi, > > We would like to know if dropping python 2 support is in the roadmap > of Paraview and when? So that we start thinking to migrate to Python 3 > for our application based on Paraview. > > Thanks, > > Christophe > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 3 16:19:51 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 3 Mar 2017 16:19:51 -0500 Subject: [Paraview-developers] ParaView 5.3.0 tagging will be delayed Message-ID: Hi ParaView developers, Due to some important issues identified since the second release candidate of 5.3.0, we plan to tag a third release candidate by this upcoming Monday, March 6. We will have binaries early next week - I will post an announcement when they are ready. Version 5.3.0 final is now scheduled for tagging on March 10. Thank you, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From christophe.bourcier.pv at gmail.com Mon Mar 6 02:35:18 2017 From: christophe.bourcier.pv at gmail.com (Christophe Bourcier) Date: Mon, 6 Mar 2017 08:35:18 +0100 Subject: [Paraview-developers] End of python 2 support? In-Reply-To: References: Message-ID: Thank you for your answer. Christophe 2017-03-03 17:21 GMT+01:00 Utkarsh Ayachit : > There's no immediate plan to drop Python 2 support. The upcoming ParaView > 5.3 is the first release that supports Python 3 officially (except for > ParaViewWeb components). So I'd expect we're at least a couple of releases > away, if not more, before we drop Python 2 support entirely. Python 2 is > still the Python version used in binaries that will be distributed for > ParaView 5.3. > > What's more near term in dropping support for would be legacy OpenGL > rendering backend and Qt 4 (not necessarily in that order). > > Utkarsh > > On Fri, Mar 3, 2017 at 11:11 AM, Christophe Bourcier > wrote: >> >> Hi, >> >> We would like to know if dropping python 2 support is in the roadmap >> of Paraview and when? So that we start thinking to migrate to Python 3 >> for our application based on Paraview. >> >> Thanks, >> >> Christophe >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > From cory.quammen at kitware.com Mon Mar 6 11:20:41 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 6 Mar 2017 11:20:41 -0500 Subject: [Paraview-developers] ParaView 5.3.0-RC3 tagged Message-ID: Folks, ParaView v5.3.0-RC3 has been tagged. Please do not merge anything into `master` until the dashboards have cycled through and built the binaries for this version. I'll send an email when it is okay to merge to `master` again. Thanks, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From sur.chiranjib at gmail.com Tue Mar 7 04:31:51 2017 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Tue, 7 Mar 2017 15:01:51 +0530 Subject: [Paraview-developers] Add "text" in the property panel display fields Message-ID: Hi, I am developing a plugin and while doing so, I thought of putting "units system" to the numeric fields in the property panel. For example, the in the below screenshot I want to add " in cm" after the numeric field. [image: Inline image 1] Currently, I can extract the numeric value of these quantities by using " vtkSMPropertyHelper" like vtkSMPropertyHelper( proxy(), "Height" ).GetAsDouble(); This utility I want to retain. I am wondering, how can I add strings like " cm" etc in the display menu without reading them using vtkSMPropertyHelper. Any clue? Thanks in advance. Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5263 bytes Desc: not available URL: From mathieu.westphal at kitware.com Tue Mar 7 04:41:42 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 7 Mar 2017 10:41:42 +0100 Subject: [Paraview-developers] Add "text" in the property panel display fields In-Reply-To: References: Message-ID: Hello I suposed you may already have thought of that, but the easiest way to go would be to label you property "Height (cm)" Regards Mathieu Westphal On Tue, Mar 7, 2017 at 10:31 AM, Chiranjib Sur wrote: > Hi, > I am developing a plugin and while doing so, I thought of putting "units > system" to the numeric fields in the property panel. For example, the in > the below screenshot I want to add " in cm" after the numeric field. > > [image: Inline image 1] > > Currently, I can extract the numeric value of these quantities by using " > vtkSMPropertyHelper" like > > vtkSMPropertyHelper( proxy(), "Height" ).GetAsDouble(); > > This utility I want to retain. I am wondering, how can I add strings like " > cm" etc in the display menu without reading them using vtkSMPropertyHelper > . > > Any clue? > > Thanks in advance. > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5263 bytes Desc: not available URL: From mathieu.westphal at kitware.com Tue Mar 7 05:44:17 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 7 Mar 2017 11:44:17 +0100 Subject: [Paraview-developers] Add "text" in the property panel display fields In-Reply-To: References: Message-ID: Let's take this back to the ml so everyone can see. This looks like a Box Widget panel, and it is not generated from xml, but from a specific .ui file ./Qt/ApplicationComponents/Resources/UI/pqBoxPropertyWidget.ui To use it from a xml file, you have to specify a specific panel usage panel_widget="InteractiveBox" see ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml:668 vtkPVBox xml declaration. Regards, Mathieu Westphal On Tue, Mar 7, 2017 at 11:33 AM, Chiranjib Sur wrote: > Thanks once again. This is very helpful. I come up with questions as I > explore more (and when you answer :)). > > Where can I find the source (xml) which creates the following panel for > the transformation filter > > [image: Inline image 1] > > Chiranjib > > On Tue, Mar 7, 2017 at 3:52 PM, Mathieu Westphal < > mathieu.westphal at kitware.com> wrote: > >> filters.xml can be found here : >> ParaViewCore/ServerManager/SMApplication/Resources/filters.xml >> >> Generally speaking, if one wants to find the xml and vtk classes of a >> filter used in paraview : >> - Click on Help button in Properties Dock Widget -> Open the help for the >> filter >> - On top of the help page is the label and name of the filter >> - Then open ParaViewCore/ServerManager/SMApplication/Resources/*.xml >> file and search for the name of the filter >> - once the xml declaration of the filter is found, look for >> class="vtkClassName", this is the name of the vtkClass >> >> Another way to only get the vtk class name would be using the python >> shell this way : >> - Select filter >> - Open python shell >> - GetActiveSource().SMProxy.GetVTKClassName() >> >> Regards, >> >> Mathieu Westphal >> >> On Tue, Mar 7, 2017 at 11:14 AM, Chiranjib Sur >> wrote: >> >>> Thanks again. Can you spare me the path of the file "filters.xml". That >>> would be very helpful. >>> >>> I have another question. Typically, where to find the source for the >>> Filters and the corresponding servermanager.xml file? >>> >>> Chiranjib >>> >>> >>> On Tue, Mar 7, 2017 at 3:32 PM, Mathieu Westphal < >>> mathieu.westphal at kitware.com> wrote: >>> >>>> You can diferentiate between the name of the property, and it's label. >>>> see filters.xml:6081 vtkWarpVector -> SelectInputVectors property. >>>> >>>> Mathieu Westphal >>>> >>>> On Tue, Mar 7, 2017 at 11:00 AM, Chiranjib Sur >>> > wrote: >>>> >>>>> Thank Mathieu. >>>>> Yes, I thought about that. In that case I resolve the value using: >>>>> >>>>> vtkSMPropertyHelper( proxy(), "Height (in cm)" ).GetAsDouble(); >>>>> >>>>> But I wanted to make it more clean without adding the "units" to the >>>>> label. >>>>> >>>>> Thanks, >>>>> Chiranjib >>>>> >>>>> On Tue, Mar 7, 2017 at 3:11 PM, Mathieu Westphal < >>>>> mathieu.westphal at kitware.com> wrote: >>>>> >>>>>> Hello >>>>>> >>>>>> I suposed you may already have thought of that, but >>>>>> the easiest way to go would be to label you property "Height (cm)" >>>>>> >>>>>> Regards >>>>>> >>>>>> Mathieu Westphal >>>>>> >>>>>> On Tue, Mar 7, 2017 at 10:31 AM, Chiranjib Sur < >>>>>> sur.chiranjib at gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> I am developing a plugin and while doing so, I thought of putting "units >>>>>>> system" to the numeric fields in the property panel. For example, >>>>>>> the in the below screenshot I want to add " in cm" after the >>>>>>> numeric field. >>>>>>> >>>>>>> [image: Inline image 1] >>>>>>> >>>>>>> Currently, I can extract the numeric value of these quantities by >>>>>>> using "vtkSMPropertyHelper" like >>>>>>> >>>>>>> vtkSMPropertyHelper( proxy(), "Height" ).GetAsDouble(); >>>>>>> >>>>>>> This utility I want to retain. I am wondering, how can I add strings >>>>>>> like "cm" etc in the display menu without reading them using >>>>>>> vtkSMPropertyHelper. >>>>>>> >>>>>>> Any clue? >>>>>>> >>>>>>> Thanks in advance. >>>>>>> Chiranjib >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>> Paraview-developers >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 23940 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5263 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Mar 7 11:00:07 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 7 Mar 2017 11:00:07 -0500 Subject: [Paraview-developers] ParaView 5.3.0-RC3 tagged In-Reply-To: References: Message-ID: The ParaView 5.3.0-RC3 binaries have been created. Please feel free to merge to `master` again. Thanks, Cory On Mon, Mar 6, 2017 at 11:20 AM, Cory Quammen wrote: > Folks, > > ParaView v5.3.0-RC3 has been tagged. Please do not merge anything into > `master` until the dashboards have cycled through and built the > binaries for this version. > > I'll send an email when it is okay to merge to `master` again. > > Thanks, > Cory > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Tue Mar 7 18:50:03 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 7 Mar 2017 23:50:03 +0000 Subject: [Paraview-developers] Ply writer Message-ID: I thought we could write out time data as a series of .ply files. How can we do this? In other words, instead of a screenshot, I want an animation. How do I do this? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 7 22:58:57 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 7 Mar 2017 22:58:57 -0500 Subject: [Paraview-developers] Ply writer In-Reply-To: References: Message-ID: Alan, Turns out we can't write a PLY series. However, I wrote up an issue [1] and enabled writing a PLY series in a merge request [2]. Thanks, Cory [1] https://gitlab.kitware.com/paraview/paraview/issues/17251 [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/1449 On Tue, Mar 7, 2017 at 6:50 PM, Scott, W Alan wrote: > I thought we could write out time data as a series of .ply files. How can > we do this? In other words, instead of a screenshot, I want an animation. > How do I do this? > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science, the one that heralds new > discoveries, > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Mar 8 10:54:40 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 8 Mar 2017 10:54:40 -0500 Subject: [Paraview-developers] Ply writer In-Reply-To: References: Message-ID: Alan, You should now be able to write PLY file series in ParaView master. Thanks, Cory On Tue, Mar 7, 2017 at 10:58 PM, Cory Quammen wrote: > Alan, > > Turns out we can't write a PLY series. However, I wrote up an issue [1] and > enabled writing a PLY series in a merge request [2]. > > Thanks, > Cory > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17251 > [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/1449 > > On Tue, Mar 7, 2017 at 6:50 PM, Scott, W Alan wrote: >> >> I thought we could write out time data as a series of .ply files. How can >> we do this? In other words, instead of a screenshot, I want an animation. >> How do I do this? >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0822 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> >> >> The most exciting phrase to hear in science, the one that heralds new >> discoveries, >> >> is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Wed Mar 8 11:44:49 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 8 Mar 2017 11:44:49 -0500 Subject: [Paraview-developers] ParaView 5.3.0 Release Candidate 3 binaries are available for download Message-ID: I am happy to announce that binaries and source code zip files and tar balls for ParaView 5.3.0 Release Candidate 3 are now available for download from http://www.paraview.org/download/ Please let us know if you run into any problems with this release candidate. The ParaView issue tracker is located at https://gitlab.kitware.com/paraview/paraview/issues Sincerely, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Wed Mar 8 13:30:30 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 8 Mar 2017 18:30:30 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Ply writer In-Reply-To: References: Message-ID: Excellent, that was quick. I assume this will be in PV 5.4? > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Wednesday, March 8, 2017 8:55 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Ply writer > > Alan, > > You should now be able to write PLY file series in ParaView master. > > Thanks, > Cory > > On Tue, Mar 7, 2017 at 10:58 PM, Cory Quammen > wrote: > > Alan, > > > > Turns out we can't write a PLY series. However, I wrote up an issue > > [1] and enabled writing a PLY series in a merge request [2]. > > > > Thanks, > > Cory > > > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17251 > > [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/1449 > > > > On Tue, Mar 7, 2017 at 6:50 PM, Scott, W Alan > wrote: > >> > >> I thought we could write out time data as a series of .ply files. > >> How can we do this? In other words, instead of a screenshot, I want an > animation. > >> How do I do this? > >> > >> > >> > >> Thanks, > >> > >> > >> > >> Alan > >> > >> > >> > >> -------------------------------------------------------- > >> > >> W. Alan Scott > >> > >> ParaView Support Manager > >> > >> > >> > >> SAIC > >> > >> Sandia National Laboratories, MS 0822 > >> > >> Org 9326 - Building 880 A1-K > >> > >> (505) 284-0932 FAX (505) 284-5619 > >> > >> > >> > >> The most exciting phrase to hear in science, the one that heralds new > >> discoveries, > >> > >> is not "Eureka!" but "That's funny..." -- Isaac Asimov > >> > >> --------------------------------------------------------- > >> > >> > >> > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > > > > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From cory.quammen at kitware.com Wed Mar 8 13:33:33 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 8 Mar 2017 13:33:33 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Ply writer In-Reply-To: References: Message-ID: Yes, it will be in 5.4. On Wed, Mar 8, 2017 at 1:30 PM, Scott, W Alan wrote: > Excellent, that was quick. I assume this will be in PV 5.4? > >> -----Original Message----- >> From: Cory Quammen [mailto:cory.quammen at kitware.com] >> Sent: Wednesday, March 8, 2017 8:55 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Ply writer >> >> Alan, >> >> You should now be able to write PLY file series in ParaView master. >> >> Thanks, >> Cory >> >> On Tue, Mar 7, 2017 at 10:58 PM, Cory Quammen >> wrote: >> > Alan, >> > >> > Turns out we can't write a PLY series. However, I wrote up an issue >> > [1] and enabled writing a PLY series in a merge request [2]. >> > >> > Thanks, >> > Cory >> > >> > [1] https://gitlab.kitware.com/paraview/paraview/issues/17251 >> > [2] https://gitlab.kitware.com/paraview/paraview/merge_requests/1449 >> > >> > On Tue, Mar 7, 2017 at 6:50 PM, Scott, W Alan >> wrote: >> >> >> >> I thought we could write out time data as a series of .ply files. >> >> How can we do this? In other words, instead of a screenshot, I want an >> animation. >> >> How do I do this? >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> >> >> Alan >> >> >> >> >> >> >> >> -------------------------------------------------------- >> >> >> >> W. Alan Scott >> >> >> >> ParaView Support Manager >> >> >> >> >> >> >> >> SAIC >> >> >> >> Sandia National Laboratories, MS 0822 >> >> >> >> Org 9326 - Building 880 A1-K >> >> >> >> (505) 284-0932 FAX (505) 284-5619 >> >> >> >> >> >> >> >> The most exciting phrase to hear in science, the one that heralds new >> >> discoveries, >> >> >> >> is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> >> >> --------------------------------------------------------- >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Search the list archives at: >> >> http://markmail.org/search/?q=Paraview-developers >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> > >> > >> > >> > -- >> > Cory Quammen >> > Staff R&D Engineer >> > Kitware, Inc. >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From kriolog at gmail.com Wed Mar 8 17:55:25 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Wed, 8 Mar 2017 17:55:25 -0500 Subject: [Paraview-developers] Custom paraview plugin linker issue (missing shared library) Message-ID: Hello, I'm trying to compile on Debian the code of a custom paraview plugin which can be compiled on Windows. The filter also depends on ITK and I tried to copy all the custom Paraview/ITK build cmake parameters from Windows to Linux. The error is following: Linking CXX shared library libitkImageRegistrationMethodBSplineFilter.so /usr/bin/ld: cannot find -lvtkPVServerManagerApplicationCS collect2: error: ld returned 1 exit status CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/build.make:408: recipe for target 'libitkImageRegistrationMethodBSplineFilter.so' failed make[2]: *** [libitkImageRegistrationMethodBSplineFilter.so] Error 1 CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/all' failed make[1]: *** [CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/all] Error 2 Makefile:83: recipe for target 'all' failed make: *** [all] Error 2Linking CXX shared libr I haven't found any shared (.so) library vtkPVServerManagerApplicationCS into my paraview binaries, only a static one (.a). Regards, Maxim From joseph.g.hennessey2.ctr at mail.mil Thu Mar 9 16:36:37 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Thu, 9 Mar 2017 21:36:37 +0000 Subject: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Hello, What is the minimum nvidia driver level that works with ParaView 5.3.0-RC3? We have been trying version 352.68 and have been getting segfaults with /usr/lib64/libnvidia-glcore.so.352.68 Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From mathieu.westphal at kitware.com Fri Mar 10 08:14:32 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Mar 2017 14:14:32 +0100 Subject: [Paraview-developers] A suggestion to improve buildbots errors and warnings handling Message-ID: Hi All As usual, our buildbots are reporting a few errors and warnings on master. Should we have a place to report these, and note the why and the how, and if somebady plans to tackles it ? paraview/paraview/issues comes to mind. What do you think ? Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Mar 10 09:18:06 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 10 Mar 2017 09:18:06 -0500 Subject: [Paraview-developers] A suggestion to improve buildbots errors and warnings handling In-Reply-To: References: Message-ID: Mathieu, It couldn't hurt to file issues, particularly for warnings/errors that are tricky to resolve, which I believe is the case with most of the warnings and errors that remain. Thanks, Cory On Fri, Mar 10, 2017 at 8:14 AM, Mathieu Westphal wrote: > Hi All > > As usual, our buildbots are reporting a few errors and warnings on master. > Should we have a place to report these, and note the why and the how, and if > somebady plans to tackles it ? > > paraview/paraview/issues comes to mind. > > What do you think ? > > Mathieu Westphal > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Fri Mar 10 10:06:12 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 10:06:12 -0500 Subject: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe, I believe no one has answered since it's a hard question to answer -- for me, anyways :). Is it possible to do a debug build of ParaView and see where it's segfaulting? Utkarsh On Thu, Mar 9, 2017 at 4:36 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > What is the minimum nvidia driver level that works with ParaView 5.3.0-RC3? > > We have been trying version 352.68 and have been getting segfaults with > > /usr/lib64/libnvidia-glcore.so.352.68 > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From joseph.g.hennessey2.ctr at mail.mil Fri Mar 10 10:43:56 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Fri, 10 Mar 2017 15:43:56 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Utkarsh, As you can see from the stack trace of the problem point below Inside of vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow this->DestroyWindow(); is being called Then inside of void vtkXOpenGLRenderWindow::DestroyWindow() glXMakeCurrent(this->DisplayId, None, NULL); is being called with this->DisplayId = (Display *) 0x1db0940 It then ultimately segfaults in /usr/lib64/libnvidia-glcore.so.352.68 Here is my gdb data including a backtrace. Thanks, Joe (gdb) frame 8 #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow (this= 0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:741 741 glXMakeCurrent(this->DisplayId, None, NULL); (gdb) print this-?DisplayId A syntax error in expression, near `?DisplayId'. (gdb) ptype this->DisplayId type = struct _XDisplay { } * (gdb) ptype this->Internal->ContextId type = struct __GLXcontextRec { } * (gdb) ptype this->OwnContext type = int (gdb) print this->DisplayId $1 = (Display *) 0x1db0940 (gdb) print this->Internal->ContextId $2 = (GLXContext) 0x1dc1680 (gdb) print this->OwnContext $3 = 1 (gdb) backtrace #0 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 #1 0x00002aaad5d2e69f in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 #3 0x00002aaaaad01dc6 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #4 0x00002aaaaad04f84 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #5 0x00002aaaaad06559 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #6 0x00002aaaaad0726e in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #7 0x00002aaaaacf5e80 in glXMakeCurrent () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow (this= 0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:741 #9 0x00002aaab1cabd72 in vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2177 #10 0x00002aaab1d46a52 in vtkXOpenGLRenderWindow::DestroyOffScreenWindow (this= 0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:849 #11 0x00002aaab1d499f4 in vtkXOpenGLRenderWindow::SetOffScreenRendering (this= 0x1daf9a0, i=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize (this=0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:930 #13 0x00002aaab1d44b9c in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow ( this=0x1daf9a0, __in_chrg=) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:357 #14 0x00002aaab1d44c7a in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow ( this=0x1daf9a0, __in_chrg=) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:368 #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal (this=0x1daf9a0, check=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:240 #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal (this=0x1daf9a0, o= 0x0, check=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:900 #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf9a0, o=0x0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:197 #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf9a0, o=0x0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:1420 #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf9a0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:142 #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL (this= 0x1dae860) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2338 #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject (this= 0xd37c80) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal (this= 0x8c6d70, information=0xd37c80, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:783 #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation (this=0x8c6d70, location=4, information=0xd37c80, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:821 #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation (this=0xb27240, location=4, information=0xd37c80, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:243 #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation (this= 0xb25e60, server=0xe552b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqDefaultViewBehavior.cxx:119 #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall (_o= 0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/ApplicationComponents/moc_pqDefaultViewBehavior.cxx:54 #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded (this=0x8acd90, _t1=0xe552b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:218 #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated (this= 0x8acd90, id=1) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerModel.cxx:503 #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall (_o= 0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:160 #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated (this= 0x8c8a80, _t1=1) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerObserver.cxx:170 #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated (this= 0x8c8a80, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerObserver.cxx:110 #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall (_o= 0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqS---Type to continue, or q to quit--- erverManagerObserver.cxx:90 #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, _t1= 0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISupport/Qt/moc_vtkQtConnection.cxx:103 #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, caller= 0x912420, e=67, call_data=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:72 #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback (vtk_obj=0x912420, event= 67, client_data=0x84c030, call_data=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:62 #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, caller= 0x912420, event=67, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkCallbackCommand.cxx:42 #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent (this=0x84bec0, event= 67, callData=0x912460, self=0x912420) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:616 #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, event=67, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:785 #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession (this=0x912420, session=0xb27240) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:378 #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMSession.cxx:308 #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer (this=0x8acc70, resource=...) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObjectBuilder.cxx:656 #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck (this= 0xb24d00) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:81 #47 0x00002aaaaaf7a8d6 in pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior (this=0xb24d00, parentObject=0xb19b40) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:52 #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors (this= 0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqParaViewBehaviors.cxx:157 #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow (this= 0x8ff0b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/ParaView/ParaViewMainWindow.cxx:249 #50 0x000000000040accb in pqparaviewInitializer::Initialize (this= 0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/pqparaviewInitializer.cxx:122 #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/paraview_main.cxx:117 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 10, 2017 10:06 AM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Joe, I believe no one has answered since it's a hard question to answer -- for me, anyways :). Is it possible to do a debug build of ParaView and see where it's segfaulting? Utkarsh On Thu, Mar 9, 2017 at 4:36 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > What is the minimum nvidia driver level that works with ParaView 5.3.0-RC3? > > We have been trying version 352.68 and have been getting segfaults > with > > /usr/lib64/libnvidia-glcore.so.352.68 > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by Caution-www.kitware.com > > Visit other Kitware open-source projects at > Caution-http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > Caution-http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Mar 10 11:46:37 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 11:46:37 -0500 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe, Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the environment and see if it goes further? Thanks Utkarsh From joseph.g.hennessey2.ctr at mail.mil Fri Mar 10 12:02:20 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Fri, 10 Mar 2017 17:02:20 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Utkarsh, It fails at the same point with the variable set. Here is the backtrace. (It is I think the same) Thanks, Joe Program received signal SIGSEGV, Segmentation fault. 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 (gdb) backtrace #0 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 #1 0x00002aaad5d2e69f in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 #3 0x00002aaaaad01dc6 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #4 0x00002aaaaad04f84 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #5 0x00002aaaaad06559 in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #6 0x00002aaaaad0726e in ?? () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #7 0x00002aaaaacf5e80 in glXMakeCurrent () from /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow (this=0x1daf950) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:741 #9 0x00002aaab1cabd72 in vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2177 #10 0x00002aaab1d46a52 in vtkXOpenGLRenderWindow::DestroyOffScreenWindow (this=0x1daf950) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:849 #11 0x00002aaab1d499f4 in vtkXOpenGLRenderWindow::SetOffScreenRendering (this=0x1daf950, i=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize (this=0x1daf950) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:930 #13 0x00002aaab1d44b9c in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow (this=0x1daf950, __in_chrg=) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:357 #14 0x00002aaab1d44c7a in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow (this=0x1daf950, __in_chrg=) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:368 #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal (this=0x1daf950, check=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:240 #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal (this=0x1daf950, o=0x0, check=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:900 #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, o=0x0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:197 #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf950, o=0x0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:1420 #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:142 #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL (this=0x1dae810) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2338 #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject (this=0xd36d30) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal (this=0x8c6d70, information=0xd36d30, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:783 #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:821 #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation (this=0xb27240, location=4, information=0xd36d30, globalid=0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:243 #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation (this=0xb25e60, server=0xe552b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqDefaultViewBehavior.cxx:119 #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/ApplicationComponents/moc_pqDefaultViewBehavior.cxx:54 #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded (this=0x8acd90, _t1=0xe552b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:218 #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated (this=0x8acd90, id=1) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerModel.cxx:503 #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:160 #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated (this=0x8c8a80, _t1=1) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerObserver.cxx:170 #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated (this=0x8c8a80, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerObserver.cxx:110 #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerObserver.cxx:90 #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISupport/Qt/moc_vtkQtConnection.cxx:103 #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, caller=0x912420, e=67, call_data=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:72 #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:62 #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, caller=0x912420, event=67, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkCallbackCommand.cxx:42 #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent (this=0x84bec0, event=67, callData=0x912460, self=0x912420) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:616 #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, event=67, callData=0x912460) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:785 #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession (this=0x912420, session=0xb27240) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:378 #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMSession.cxx:308 #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer (this=0x8acc70, resource=...) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObjectBuilder.cxx:656 #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck (this=0xb24d00) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:81 #47 0x00002aaaaaf7a8d6 in pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior (this=0xb24d00, parentObject=0xb19b40) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:52 #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqParaViewBehaviors.cxx:157 #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow (this=0x8ff0b0) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/ParaView/ParaViewMainWindow.cxx:249 #50 0x000000000040accb in pqparaviewInitializer::Initialize (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/pqparaviewInitializer.cxx:122 #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/paraview_main.cxx:117 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 10, 2017 11:47 AM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) Joe, Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the environment and see if it goes further? Thanks Utkarsh CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Mar 10 12:09:38 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 12:09:38 -0500 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe, Something's not correct. If you look at the code in vtkPVDisplayInformation [1], it should not even get to line #108 if the environment variable was set correctly. Utkarsh [1] https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Utkarsh, > > It fails at the same point with the variable set. > Here is the backtrace. (It is I think the same) > > Thanks, > > Joe > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 > (gdb) backtrace > #0 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 > #1 0x00002aaad5d2e69f in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 > #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 > #3 0x00002aaaaad01dc6 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #4 0x00002aaaaad04f84 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #5 0x00002aaaaad06559 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #6 0x00002aaaaad0726e in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #7 0x00002aaaaacf5e80 in glXMakeCurrent () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:741 > #9 0x00002aaab1cabd72 in > vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2177 > #10 0x00002aaab1d46a52 in vtkXOpenGLRenderWindow::DestroyOffScreenWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:849 > #11 0x00002aaab1d499f4 in vtkXOpenGLRenderWindow::SetOffScreenRendering > (this=0x1daf950, i=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 > #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:930 > #13 0x00002aaab1d44b9c in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:357 > #14 0x00002aaab1d44c7a in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:368 > #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal (this=0x1daf950, > check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:240 > #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal (this=0x1daf950, > o=0x0, check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:900 > #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, o=0x0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:197 > #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf950, o=0x0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:1420 > #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObjectBase.cxx:142 > #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL > (this=0x1dae810) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2338 > #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 > #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject > (this=0xd36d30) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 > #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal > (this=0x8c6d70, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:783 > #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation (this=0x8c6d70, > location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:821 > #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation (this=0xb27240, > location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:243 > #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation > (this=0xb25e60, server=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqDefaultViewBehavior.cxx:119 > #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall > (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/ApplicationComponents/moc_pqDefaultViewBehavior.cxx:54 > #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded (this=0x8acd90, > _t1=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:218 > #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated > (this=0x8acd90, id=1) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerModel.cxx:503 > #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall > (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerModel.cxx:160 > #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, _t1=1) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerObserver.cxx:170 > #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServerManagerObserver.cxx:110 > #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall > (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_pqServerManagerObserver.cxx:90 > #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, > _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISupport/Qt/moc_vtkQtConnection.cxx:103 > #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, > caller=0x912420, e=67, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:72 > #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback (vtk_obj=0x912420, > event=67, client_data=0x84c030, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport/Qt/vtkQtConnection.cxx:62 > #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, > caller=0x912420, event=67, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkCallbackCommand.cxx:42 > #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent (this=0x84bec0, > event=67, callData=0x912460, self=0x912420) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:616 > #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, event=67, > callData=0x912460) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Core/vtkObject.cxx:785 > #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession (this=0x912420, > session=0xb27240) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:378 > #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMSession.cxx:308 > #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer (this=0x8acc70, > resource=...) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObjectBuilder.cxx:656 > #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck > (this=0xb24d00) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:81 > #47 0x00002aaaaaf7a8d6 in pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior > (this=0xb24d00, parentObject=0xb19b40) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:52 > #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors > (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/ApplicationComponents/pqParaViewBehaviors.cxx:157 > #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow > (this=0x8ff0b0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/ParaView/ParaViewMainWindow.cxx:249 > #50 0x000000000040accb in pqparaviewInitializer::Initialize > (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/pqparaviewInitializer.cxx:122 > #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications/ParaView/paraview_main.cxx:117 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 11:47 AM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > Joe, > > Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the > environment and see if it goes further? > > Thanks > Utkarsh > > > CLASSIFICATION: UNCLASSIFIED From joseph.g.hennessey2.ctr at mail.mil Fri Mar 10 12:29:03 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Fri, 10 Mar 2017 17:29:03 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Utkarsh, You are correct, I had set the variable but not exported it. When I correctly exported the variable then ParaView 5.3.0-RC3 correctly launched without segfaulting. So, now I have a workaround at least. Is there anything else I should check for you? Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Voice: 410-278-3619 Fax: 410-278-8799 Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 10, 2017 12:10 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Joe, Something's not correct. If you look at the code in vtkPVDisplayInformation [1], it should not even get to line #108 if the environment variable was set correctly. Utkarsh [1] Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Utkarsh, > > It fails at the same point with the variable set. > Here is the backtrace. (It is I think the same) > > Thanks, > > Joe > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 > (gdb) backtrace > #0 0x00002aaad5d2e2af in ?? () from > /usr/lib64/libnvidia-glcore.so.352.68 > #1 0x00002aaad5d2e69f in ?? () from > /usr/lib64/libnvidia-glcore.so.352.68 > #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 > #3 0x00002aaaaad01dc6 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #4 0x00002aaaaad04f84 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #5 0x00002aaaaad06559 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #6 0x00002aaaaad0726e in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #7 0x00002aaaaacf5e80 in glXMakeCurrent () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:741 > #9 0x00002aaab1cabd72 in > vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkOpenGLRenderWindow.cxx:2177 > #10 0x00002aaab1d46a52 in > vtkXOpenGLRenderWindow::DestroyOffScreenWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:849 > #11 0x00002aaab1d499f4 in > vtkXOpenGLRenderWindow::SetOffScreenRendering > (this=0x1daf950, i=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 > #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize > (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:930 > #13 0x00002aaab1d44b9c in > vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:357 > #14 0x00002aaab1d44c7a in > vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:368 > #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal > (this=0x1daf950, > check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:240 > #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal > (this=0x1daf950, o=0x0, check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:900 > #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, > o=0x0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:197 > #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf950, > o=0x0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > Core/vtkRenderWindow.cxx:1420 > #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:142 > #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL > (this=0x1dae810) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkOpenGLRenderWindow.cxx:2338 > #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 > #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject > (this=0xd36d30) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 > #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal > (this=0x8c6d70, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionCore.cxx:783 > #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation > (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionCore.cxx:821 > #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation > (this=0xb27240, location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionBase.cxx:243 > #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation > (this=0xb25e60, server=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqDefaultViewBehavior.cxx:119 > #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall > (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applicati > onComponents/moc_pqDefaultViewBehavior.cxx:54 > #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded > (this=0x8acd90, > _t1=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerModel.cxx:218 > #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated > (this=0x8acd90, id=1) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ > erManagerModel.cxx:503 > #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall > (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerModel.cxx:160 > #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, _t1=1) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerObserver.cxx:170 > #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ > erManagerObserver.cxx:110 > #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall > (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerObserver.cxx:90 > #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, > _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISuppo > rt/Qt/moc_vtkQtConnection.cxx:103 > #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, > caller=0x912420, e=67, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport > /Qt/vtkQtConnection.cxx:72 > #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback > (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport > /Qt/vtkQtConnection.cxx:62 > #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, > caller=0x912420, event=67, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkCallbackCommand.cxx:42 > #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent > (this=0x84bec0, event=67, callData=0x912460, self=0x912420) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:616 > #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, > event=67, > callData=0x912460) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:785 > #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession > (this=0x912420, > session=0xb27240) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Core/vtkProcessModule.cxx:378 > #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverManager/Core/vtkSMSession.cxx:308 > #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer > (this=0x8acc70, > resource=...) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObje > ctBuilder.cxx:656 > #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck > (this=0xb24d00) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqAlwaysConnectedBehavior.cxx:81 > #47 0x00002aaaaaf7a8d6 in > pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior > (this=0xb24d00, parentObject=0xb19b40) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqAlwaysConnectedBehavior.cxx:52 > #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors > (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqParaViewBehaviors.cxx:157 > #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow > (this=0x8ff0b0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/P > araView/ParaViewMainWindow.cxx:249 > #50 0x000000000040accb in pqparaviewInitializer::Initialize > (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications > /ParaView/pqparaviewInitializer.cxx:122 > #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications > /ParaView/paraview_main.cxx:117 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > -----Original Message----- > From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 11:47 AM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > minimum nvidia driver level that works with ParaView 5.3.0 > (UNCLASSIFIED) > > Joe, > > Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the > environment and see if it goes further? > > Thanks > Utkarsh > > > CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From simon.m.su.civ at mail.mil Fri Mar 10 12:38:02 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Fri, 10 Mar 2017 17:38:02 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> Message-ID: CLASSIFICATION: UNCLASSIFIED Utkarsh, What does this mean? What would be the way to address the problem? Thanks -simon -----Original Message----- From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Sent: Friday, March 10, 2017 12:29 PM To: Utkarsh Ayachit Cc: ParaView Developers Subject: Re: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- CLASSIFICATION: UNCLASSIFIED Utkarsh, You are correct, I had set the variable but not exported it. When I correctly exported the variable then ParaView 5.3.0-RC3 correctly launched without segfaulting. So, now I have a workaround at least. Is there anything else I should check for you? Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Voice: 410-278-3619 Fax: 410-278-8799 Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 10, 2017 12:10 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Joe, Something's not correct. If you look at the code in vtkPVDisplayInformation [1], it should not even get to line #108 if the environment variable was set correctly. Utkarsh [1] Caution-Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Utkarsh, > > It fails at the same point with the variable set. > Here is the backtrace. (It is I think the same) > > Thanks, > > Joe > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 > (gdb) backtrace > #0 0x00002aaad5d2e2af in ?? () from > /usr/lib64/libnvidia-glcore.so.352.68 > #1 0x00002aaad5d2e69f in ?? () from > /usr/lib64/libnvidia-glcore.so.352.68 > #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 > #3 0x00002aaaaad01dc6 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #4 0x00002aaaaad04f84 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #5 0x00002aaaaad06559 in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #6 0x00002aaaaad0726e in ?? () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #7 0x00002aaaaacf5e80 in glXMakeCurrent () from > /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:741 > #9 0x00002aaab1cabd72 in > vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkOpenGLRenderWindow.cxx:2177 > #10 0x00002aaab1d46a52 in > vtkXOpenGLRenderWindow::DestroyOffScreenWindow > (this=0x1daf950) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:849 > #11 0x00002aaab1d499f4 in > vtkXOpenGLRenderWindow::SetOffScreenRendering > (this=0x1daf950, i=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 > #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize > (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:930 > #13 0x00002aaab1d44b9c in > vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:357 > #14 0x00002aaab1d44c7a in > vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > (this=0x1daf950, __in_chrg=) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkXOpenGLRenderWindow.cxx:368 > #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal > (this=0x1daf950, > check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:240 > #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal > (this=0x1daf950, o=0x0, check=0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:900 > #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, > o=0x0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:197 > #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf950, > o=0x0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > Core/vtkRenderWindow.cxx:1420 > #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObjectBase.cxx:142 > #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL > (this=0x1dae810) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ > OpenGL2/vtkOpenGLRenderWindow.cxx:2338 > #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 > #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject > (this=0xd36d30) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 > #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal > (this=0x8c6d70, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionCore.cxx:783 > #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation > (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionCore.cxx:821 > #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation > (this=0xb27240, location=4, information=0xd36d30, globalid=0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverImplementation/Core/vtkPVSessionBase.cxx:243 > #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation > (this=0xb25e60, server=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqDefaultViewBehavior.cxx:119 > #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall > (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applicati > onComponents/moc_pqDefaultViewBehavior.cxx:54 > #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded > (this=0x8acd90, > _t1=0xe552b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerModel.cxx:218 > #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated > (this=0x8acd90, id=1) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ > erManagerModel.cxx:503 > #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall > (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerModel.cxx:160 > #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, _t1=1) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerObserver.cxx:170 > #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated > (this=0x8c8a80, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ > erManagerObserver.cxx:110 > #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall > (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ > pqServerManagerObserver.cxx:90 > #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, > _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISuppo > rt/Qt/moc_vtkQtConnection.cxx:103 > #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, > caller=0x912420, e=67, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport > /Qt/vtkQtConnection.cxx:72 > #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback > (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport > /Qt/vtkQtConnection.cxx:62 > #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, > caller=0x912420, event=67, callData=0x912460) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkCallbackCommand.cxx:42 > #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent > (this=0x84bec0, event=67, callData=0x912460, self=0x912420) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:616 > #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, > event=67, > callData=0x912460) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor > e/vtkObject.cxx:785 > #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession > (this=0x912420, > session=0xb27240) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C > lientServerCore/Core/vtkProcessModule.cxx:378 > #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S > erverManager/Core/vtkSMSession.cxx:308 > #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer > (this=0x8acc70, > resource=...) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObje > ctBuilder.cxx:656 > #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck > (this=0xb24d00) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqAlwaysConnectedBehavior.cxx:81 > #47 0x00002aaaaaf7a8d6 in > pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior > (this=0xb24d00, parentObject=0xb19b40) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqAlwaysConnectedBehavior.cxx:52 > #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors > (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application > Components/pqParaViewBehaviors.cxx:157 > #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow > (this=0x8ff0b0) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/P > araView/ParaViewMainWindow.cxx:249 > #50 0x000000000040accb in pqparaviewInitializer::Initialize > (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) > at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications > /ParaView/pqparaviewInitializer.cxx:122 > #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at > /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications > /ParaView/paraview_main.cxx:117 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > -----Original Message----- > From: Utkarsh Ayachit > [Caution-Caution-mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 11:47 AM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > minimum nvidia driver level that works with ParaView 5.3.0 > (UNCLASSIFIED) > > Joe, > > Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the > environment and see if it goes further? > > Thanks > Utkarsh > > > CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED From wascott at sandia.gov Fri Mar 10 14:19:28 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 10 Mar 2017 19:19:28 +0000 Subject: [Paraview-developers] ParaView 6.0 Message-ID: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> Cory/Utkarsh/Ken, I tested PV 5.3.0 yesterday, and decided to do it with Auto Apply on. This worked surprisingly well. I did have a bit of issue in the calculator (state problem that cleared after a close and reopen), and the known issues with readers. I would like to propose that we make this coming falls (SC17) release of PV have Auto Apply default on. Further, this may be a large enough change that we should call it PV 6.0. Thoughts? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 10 14:34:30 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 14:34:30 -0500 Subject: [Paraview-developers] ParaView 6.0 In-Reply-To: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> Message-ID: I vote we delay it till the following happens: 1. common filters in ParaView are quietly using VTK-m so that those operations are fast. 2. we iron out the UI/workflow changes Ken suggested for filters/readers that "require" user input before "Apply". While we can tackle (2) if we decided to by SC17, I am not sure (1) will be addressed by then. Utkarsh On Fri, Mar 10, 2017 at 2:19 PM, Scott, W Alan wrote: > Cory/Utkarsh/Ken, > > > > I tested PV 5.3.0 yesterday, and decided to do it with Auto Apply on. This > worked surprisingly well. I did have a bit of issue in the calculator > (state problem that cleared after a close and reopen), and the known issues > with readers. > > > > I would like to propose that we make this coming falls (SC17) release of PV > have Auto Apply default on. Further, this may be a large enough change that > we should call it PV 6.0. > > > > Thoughts? > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science, the one that heralds new > discoveries, > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From cory.quammen at kitware.com Fri Mar 10 14:55:04 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 10 Mar 2017 14:55:04 -0500 Subject: [Paraview-developers] ParaView 5.3.0 final tagged Message-ID: Folks, ParaView 5.3.0 has been tagged. Binaries are being generated as I type and should be available for download by Monday. Thanks, Cory p.s. Merging to master is fine as we are using a different method to generate binaries for the final release. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Fri Mar 10 15:09:30 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 10 Mar 2017 15:09:30 -0500 Subject: [Paraview-developers] ParaView 6.0 In-Reply-To: References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> Message-ID: There's been suggestions to improve the descriptions of somethings (e.g. the names for filters with multiple inputs, poorly named stuff like High Resolution Line Source with a default of 100 points). I would like to see that change make it into PV 6.0 too. On Fri, Mar 10, 2017 at 2:34 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > I vote we delay it till the following happens: > 1. common filters in ParaView are quietly using VTK-m so that those > operations are fast. > 2. we iron out the UI/workflow changes Ken suggested for > filters/readers that "require" user input before "Apply". > > While we can tackle (2) if we decided to by SC17, I am not sure (1) > will be addressed by then. > > Utkarsh > > On Fri, Mar 10, 2017 at 2:19 PM, Scott, W Alan wrote: > > Cory/Utkarsh/Ken, > > > > > > > > I tested PV 5.3.0 yesterday, and decided to do it with Auto Apply on. > This > > worked surprisingly well. I did have a bit of issue in the calculator > > (state problem that cleared after a close and reopen), and the known > issues > > with readers. > > > > > > > > I would like to propose that we make this coming falls (SC17) release of > PV > > have Auto Apply default on. Further, this may be a large enough change > that > > we should call it PV 6.0. > > > > > > > > Thoughts? > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science, the one that heralds new > > discoveries, > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 10 15:16:57 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 10 Mar 2017 20:16:57 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 In-Reply-To: References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> Message-ID: <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> Makes sense. OK, let me ask this. Could we/ should we do 2) below in one of the 5.* releases for SC? And yes, Ken's suggestions for filters/ readers has my support. Or, am I somewhat rushing things? It's just that auto apply on is so nice, and if it isn't the default, it doesn't get tested and improved. Alan > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 12:35 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] ParaView 6.0 > > I vote we delay it till the following happens: > 1. common filters in ParaView are quietly using VTK-m so that those > operations are fast. > 2. we iron out the UI/workflow changes Ken suggested for filters/readers > that "require" user input before "Apply". > > While we can tackle (2) if we decided to by SC17, I am not sure (1) will be > addressed by then. > > Utkarsh > > On Fri, Mar 10, 2017 at 2:19 PM, Scott, W Alan wrote: > > Cory/Utkarsh/Ken, > > > > > > > > I tested PV 5.3.0 yesterday, and decided to do it with Auto Apply on. > > This worked surprisingly well. I did have a bit of issue in the > > calculator (state problem that cleared after a close and reopen), and > > the known issues with readers. > > > > > > > > I would like to propose that we make this coming falls (SC17) release > > of PV have Auto Apply default on. Further, this may be a large enough > > change that we should call it PV 6.0. > > > > > > > > Thoughts? > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science, the one that heralds new > > discoveries, > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > From wascott at sandia.gov Fri Mar 10 21:29:34 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 11 Mar 2017 02:29:34 +0000 Subject: [Paraview-developers] Edit/ Dictation and Emoji Message-ID: <21FBA302-3A4C-4C22-A22D-392F082795B4@sandia.gov> Hi all, What are the two lines I now see in ParaView Edit Menu, that say Start Dictation and Emoji & Symbols? Mind giving me a usecase? I see this with 5.3.0 RC3, on my Mac. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 10 21:36:15 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 11 Mar 2017 02:36:15 +0000 Subject: [Paraview-developers] [EXTERNAL] Edit/ Dictation and Emoji In-Reply-To: <21FBA302-3A4C-4C22-A22D-392F082795B4@sandia.gov> References: <21FBA302-3A4C-4C22-A22D-392F082795B4@sandia.gov> Message-ID: I answered my own question. It?s a Mac system thing, not ParaView. Alan From: Paraview-developers on behalf of W Scott Date: Friday, March 10, 2017 at 7:29 PM To: "paraview-developers at paraview.org" Subject: [EXTERNAL] [Paraview-developers] Edit/ Dictation and Emoji Hi all, What are the two lines I now see in ParaView Edit Menu, that say Start Dictation and Emoji & Symbols? Mind giving me a usecase? I see this with 5.3.0 RC3, on my Mac. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Mon Mar 13 12:10:57 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 13 Mar 2017 17:10:57 +0100 Subject: [Paraview-developers] A suggestion to improve buildbots errors and warnings handling In-Reply-To: References: Message-ID: Hi All I've started adding Warnings and Errors from the buildbots in gitlab. They are all tagged with triage:buildbot tag. https://gitlab.kitware.com/paraview/paraview/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=triage%3Abuildbot The idea is to be able to refer to this when something comes up in our MR, and of course to try to fix them at some point. Thanks, Mathieu Westphal On Fri, Mar 10, 2017 at 3:18 PM, Cory Quammen wrote: > Mathieu, > > It couldn't hurt to file issues, particularly for warnings/errors that > are tricky to resolve, which I believe is the case with most of the > warnings and errors that remain. > > Thanks, > Cory > > On Fri, Mar 10, 2017 at 8:14 AM, Mathieu Westphal > wrote: > > Hi All > > > > As usual, our buildbots are reporting a few errors and warnings on > master. > > Should we have a place to report these, and note the why and the how, > and if > > somebady plans to tackles it ? > > > > paraview/paraview/issues comes to mind. > > > > What do you think ? > > > > Mathieu Westphal > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Mar 13 12:57:23 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Mar 2017 12:57:23 -0400 Subject: [Paraview-developers] ParaView 5.3.0 released Message-ID: On behalf of the ParaView team, I am happy to announce that ParaView 5.3.0 has been released and is ready to download from http://www.paraview.org/download Release notes for ParaView 5.3.0 are available at https://blog.kitware.com/paraview-5-3-0-release-notes/ Thank you, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Tue Mar 14 10:29:29 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Mar 2017 10:29:29 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 In-Reply-To: <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> Message-ID: > Makes sense. OK, let me ask this. Could we/ should we do 2) below in one of the 5.* releases for SC? I think not. It doesn't make sense to change the workflow, unless "Auto Apply" is the only (not just default) behavior. From utkarsh.ayachit at kitware.com Tue Mar 14 10:35:51 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Mar 2017 10:35:51 -0400 Subject: [Paraview-developers] Custom paraview plugin linker issue (missing shared library) In-Reply-To: References: Message-ID: Maxim, Something is odd. Plugins don't generally need to link with vtkPVServerManagerApplicationCS. Are any other plugins e.g. the ones included in ParaView itself, building correctly for you? On Wed, Mar 8, 2017 at 5:55 PM, Maxim Torgonskiy wrote: > Hello, > > I'm trying to compile on Debian the code of a custom paraview plugin > which can be compiled on Windows. The filter also depends on ITK and I > tried to copy all the custom Paraview/ITK build cmake parameters from > Windows to Linux. > > The error is following: > Linking CXX shared library libitkImageRegistrationMethodBSplineFilter.so > /usr/bin/ld: cannot find -lvtkPVServerManagerApplicationCS > collect2: error: ld returned 1 exit status > CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/build.make:408: > recipe for target 'libitkImageRegistrationMethodBSplineFilter.so' > failed > make[2]: *** [libitkImageRegistrationMethodBSplineFilter.so] Error 1 > CMakeFiles/Makefile2:67: recipe for target > 'CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/all' failed > make[1]: *** [CMakeFiles/itkImageRegistrationMethodBSplineFilter.dir/all] > Error 2 > Makefile:83: recipe for target 'all' failed > make: *** [all] Error 2Linking CXX shared libr > > I haven't found any shared (.so) library > vtkPVServerManagerApplicationCS into my paraview binaries, only a > static one (.a). > > Regards, > Maxim > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From bastien.jacquet at kitware.com Tue Mar 14 10:36:49 2017 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Tue, 14 Mar 2017 15:36:49 +0100 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 In-Reply-To: References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hey, As far as "Auto Apply" currently works, filters having multiple parameters are recomputed multiple times while the user is modifying each parameters (eg. slice normal or origin, ... ). This seems to me like a no-go with huge datasets. Am I alone having this concern ? Just my two cents, Bastien On Tue, Mar 14, 2017 at 3:29 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > Makes sense. OK, let me ask this. Could we/ should we do 2) below in > one of the 5.* releases for SC? > > I think not. It doesn't make sense to change the workflow, unless > "Auto Apply" is the only (not just default) behavior. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 14 14:43:45 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 14 Mar 2017 14:43:45 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 In-Reply-To: References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> Message-ID: The intention isn't to make auto-apply the only option, just by default to have it enabled instead of disabled. Users will still be able to enable and disable it as needed. On Tue, Mar 14, 2017 at 10:36 AM, Bastien Jacquet < bastien.jacquet at kitware.com> wrote: > Hey, > > As far as "Auto Apply" currently works, filters having multiple parameters > are recomputed multiple times while the user is modifying each parameters > (eg. slice normal or origin, ... ). > This seems to me like a no-go with huge datasets. Am I alone having this > concern ? > Just my two cents, > Bastien > > On Tue, Mar 14, 2017 at 3:29 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> > Makes sense. OK, let me ask this. Could we/ should we do 2) below in >> one of the 5.* releases for SC? >> >> I think not. It doesn't make sense to change the workflow, unless >> "Auto Apply" is the only (not just default) behavior. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 14 14:45:44 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 14 Mar 2017 18:45:44 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 In-Reply-To: References: <32c4afa1e48e48279088e7d96c0b9327@ES01AMSNLNT.srn.sandia.gov> <8b2fbb3db04d4f589008194a9a151edc@ES01AMSNLNT.srn.sandia.gov> Message-ID: <13ec6ebbe8f741c6a720dbec6c143c44@ES01AMSNLNT.srn.sandia.gov> Yes, what Andy says is my thoughts... From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Andy Bauer Sent: Tuesday, March 14, 2017 12:44 PM To: Bastien Jacquet Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: ParaView 6.0 The intention isn't to make auto-apply the only option, just by default to have it enabled instead of disabled. Users will still be able to enable and disable it as needed. On Tue, Mar 14, 2017 at 10:36 AM, Bastien Jacquet > wrote: Hey, As far as "Auto Apply" currently works, filters having multiple parameters are recomputed multiple times while the user is modifying each parameters (eg. slice normal or origin, ... ). This seems to me like a no-go with huge datasets. Am I alone having this concern ? Just my two cents, Bastien On Tue, Mar 14, 2017 at 3:29 PM, Utkarsh Ayachit > wrote: > Makes sense. OK, let me ask this. Could we/ should we do 2) below in one of the 5.* releases for SC? I think not. It doesn't make sense to change the workflow, unless "Auto Apply" is the only (not just default) behavior. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 15 11:13:31 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 11:13:31 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe, Can you see if you close all views, split views and/or create new views if it still works? I wonder if you're running to some GL/GLX issue with creating multiple OpenGL contexts. There's also some known issue with creation of the offscreen context, or so I am told, that encounters some issues on certain linuxes..you may be running into that. Utkarsh On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Utkarsh, > > You are correct, I had set the variable but not exported it. > When I correctly exported the variable then ParaView 5.3.0-RC3 > correctly launched without segfaulting. > > So, now I have a workaround at least. > Is there anything else I should check for you? > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 > Fax: 410-278-8799 > Email: joseph.g.hennessey2.ctr at mail.mil > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 12:10 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links contained > within the message prior to copying and pasting the address to a Web browser. > > > > > ---- > > Joe, > > Something's not correct. If you look at the code in vtkPVDisplayInformation > [1], it should not even get to line #108 if the environment variable was set > correctly. > > Utkarsh > > [1] > Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 > > On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) wrote: >> CLASSIFICATION: UNCLASSIFIED >> >> Utkarsh, >> >> It fails at the same point with the variable set. >> Here is the backtrace. (It is I think the same) >> >> Thanks, >> >> Joe >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00002aaad5d2e2af in ?? () from /usr/lib64/libnvidia-glcore.so.352.68 >> (gdb) backtrace >> #0 0x00002aaad5d2e2af in ?? () from >> /usr/lib64/libnvidia-glcore.so.352.68 >> #1 0x00002aaad5d2e69f in ?? () from >> /usr/lib64/libnvidia-glcore.so.352.68 >> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >> #3 0x00002aaaaad01dc6 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #4 0x00002aaaaad04f84 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #5 0x00002aaaaad06559 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #6 0x00002aaaaad0726e in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >> (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >> #9 0x00002aaab1cabd72 in >> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >> #10 0x00002aaab1d46a52 in >> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >> (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >> #11 0x00002aaab1d499f4 in >> vtkXOpenGLRenderWindow::SetOffScreenRendering >> (this=0x1daf950, i=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >> (this=0x1daf950) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >> #13 0x00002aaab1d44b9c in >> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >> (this=0x1daf950, __in_chrg=) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >> #14 0x00002aaab1d44c7a in >> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >> (this=0x1daf950, __in_chrg=) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >> (this=0x1daf950, >> check=0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObjectBase.cxx:240 >> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >> (this=0x1daf950, o=0x0, check=0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObject.cxx:900 >> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >> o=0x0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObjectBase.cxx:197 >> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister (this=0x1daf950, >> o=0x0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> Core/vtkRenderWindow.cxx:1420 >> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObjectBase.cxx:142 >> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >> (this=0x1dae810) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering/ >> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C >> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >> (this=0xd36d30) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C >> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >> #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal >> (this=0x8c6d70, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S >> erverImplementation/Core/vtkPVSessionCore.cxx:783 >> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S >> erverImplementation/Core/vtkPVSessionCore.cxx:821 >> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S >> erverImplementation/Core/vtkPVSessionBase.cxx:243 >> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >> (this=0xb25e60, server=0xe552b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application >> Components/pqDefaultViewBehavior.cxx:119 >> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applicati >> onComponents/moc_pqDefaultViewBehavior.cxx:54 >> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >> (this=0x8acd90, >> _t1=0xe552b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ >> pqServerManagerModel.cxx:218 >> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >> (this=0x8acd90, id=1) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ >> erManagerModel.cxx:503 >> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ >> pqServerManagerModel.cxx:160 >> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >> (this=0x8c8a80, _t1=1) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ >> pqServerManagerObserver.cxx:170 >> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >> (this=0x8c8a80, callData=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqServ >> erManagerObserver.cxx:110 >> #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall >> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc_ >> pqServerManagerObserver.cxx:90 >> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute (this=0x84c030, >> _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISuppo >> rt/Qt/moc_vtkQtConnection.cxx:103 >> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >> caller=0x912420, e=67, call_data=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport >> /Qt/vtkQtConnection.cxx:72 >> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISupport >> /Qt/vtkQtConnection.cxx:62 >> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, >> caller=0x912420, event=67, callData=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkCallbackCommand.cxx:42 >> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObject.cxx:616 >> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >> event=67, >> callData=0x912460) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Cor >> e/vtkObject.cxx:785 >> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >> (this=0x912420, >> session=0xb27240) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/C >> lientServerCore/Core/vtkProcessModule.cxx:378 >> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/S >> erverManager/Core/vtkSMSession.cxx:308 >> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >> (this=0x8acc70, >> resource=...) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObje >> ctBuilder.cxx:656 >> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >> (this=0xb24d00) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application >> Components/pqAlwaysConnectedBehavior.cxx:81 >> #47 0x00002aaaaaf7a8d6 in >> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >> (this=0xb24d00, parentObject=0xb19b40) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application >> Components/pqAlwaysConnectedBehavior.cxx:52 >> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Application >> Components/pqParaViewBehaviors.cxx:157 >> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >> (this=0x8ff0b0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/P >> araView/ParaViewMainWindow.cxx:249 >> #50 0x000000000040accb in pqparaviewInitializer::Initialize >> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications >> /ParaView/pqparaviewInitializer.cxx:122 >> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applications >> /ParaView/paraview_main.cxx:117 >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, March 10, 2017 11:47 AM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> Joe, >> >> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the >> environment and see if it goes further? >> >> Thanks >> Utkarsh >> >> >> CLASSIFICATION: UNCLASSIFIED > > > CLASSIFICATION: UNCLASSIFIED From joseph.g.hennessey2.ctr at mail.mil Thu Mar 16 14:15:43 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Thu, 16 Mar 2017 18:15:43 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> Utkarsh, I have tested on Excalibur and close all views, split views and/or create new views all work as long as the environment variable PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 On another system the ARL utility server, it has the same behavior, segfaulting unless the environment variable is set to 1. Again, it works fine with close all views, split views and/or create new views as long as the environment variable is set. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Voice: 410-278-3619 Fax: 410-278-8799 Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Wednesday, March 15, 2017 11:14 AM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) Joe, Can you see if you close all views, split views and/or create new views if it still works? I wonder if you're running to some GL/GLX issue with creating multiple OpenGL contexts. There's also some known issue with creation of the offscreen context, or so I am told, that encounters some issues on certain linuxes..you may be running into that. Utkarsh On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Utkarsh, > > You are correct, I had set the variable but not exported it. > When I correctly exported the variable then ParaView 5.3.0-RC3 > correctly launched without segfaulting. > > So, now I have a workaround at least. > Is there anything else I should check for you? > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 > Fax: 410-278-8799 > Email: joseph.g.hennessey2.ctr at mail.mil > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 10, 2017 12:10 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > minimum nvidia driver level that works with ParaView 5.3.0 > (UNCLASSIFIED) > > All active links contained in this email were disabled. Please verify > the identity of the sender, and confirm the authenticity of all links > contained within the message prior to copying and pasting the address to a > Web browser. > > > > > ---- > > Joe, > > Something's not correct. If you look at the code in > vtkPVDisplayInformation [1], it should not even get to line #108 if > the environment variable was set correctly. > > Utkarsh > > [1] > Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/ParaV > iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 > > On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY > RDECOM ARL > (US) wrote: >> CLASSIFICATION: UNCLASSIFIED >> >> Utkarsh, >> >> It fails at the same point with the variable set. >> Here is the backtrace. (It is I think the same) >> >> Thanks, >> >> Joe >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00002aaad5d2e2af in ?? () from >> /usr/lib64/libnvidia-glcore.so.352.68 >> (gdb) backtrace >> #0 0x00002aaad5d2e2af in ?? () from >> /usr/lib64/libnvidia-glcore.so.352.68 >> #1 0x00002aaad5d2e69f in ?? () from >> /usr/lib64/libnvidia-glcore.so.352.68 >> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >> #3 0x00002aaaaad01dc6 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #4 0x00002aaaaad04f84 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #5 0x00002aaaaad06559 in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #6 0x00002aaaaad0726e in ?? () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >> (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >> #9 0x00002aaab1cabd72 in >> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >> #10 0x00002aaab1d46a52 in >> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >> (this=0x1daf950) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >> #11 0x00002aaab1d499f4 in >> vtkXOpenGLRenderWindow::SetOffScreenRendering >> (this=0x1daf950, i=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >> (this=0x1daf950) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >> #13 0x00002aaab1d44b9c in >> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >> (this=0x1daf950, __in_chrg=) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >> #14 0x00002aaab1d44c7a in >> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >> (this=0x1daf950, __in_chrg=) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >> (this=0x1daf950, >> check=0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObjectBase.cxx:240 >> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >> (this=0x1daf950, o=0x0, check=0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObject.cxx:900 >> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >> o=0x0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObjectBase.cxx:197 >> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister >> (this=0x1daf950, >> o=0x0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> Core/vtkRenderWindow.cxx:1420 >> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObjectBase.cxx:142 >> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >> (this=0x1dae810) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >> / >> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> C >> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >> (this=0xd36d30) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> C >> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >> #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal >> (this=0x8c6d70, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> S >> erverImplementation/Core/vtkPVSessionCore.cxx:783 >> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> S >> erverImplementation/Core/vtkPVSessionCore.cxx:821 >> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> S >> erverImplementation/Core/vtkPVSessionBase.cxx:243 >> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >> (this=0xb25e60, server=0xe552b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >> n >> Components/pqDefaultViewBehavior.cxx:119 >> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applicat >> i >> onComponents/moc_pqDefaultViewBehavior.cxx:54 >> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >> (this=0x8acd90, >> _t1=0xe552b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >> _ >> pqServerManagerModel.cxx:218 >> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >> (this=0x8acd90, id=1) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSer >> v >> erManagerModel.cxx:503 >> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >> _ >> pqServerManagerModel.cxx:160 >> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >> (this=0x8c8a80, _t1=1) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >> _ >> pqServerManagerObserver.cxx:170 >> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >> (this=0x8c8a80, callData=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSer >> v >> erManagerObserver.cxx:110 >> #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall >> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >> _ >> pqServerManagerObserver.cxx:90 >> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >> const*, int, void**) () from >> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute >> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISupp >> o >> rt/Qt/moc_vtkQtConnection.cxx:103 >> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >> caller=0x912420, e=67, call_data=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppor >> t >> /Qt/vtkQtConnection.cxx:72 >> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppor >> t >> /Qt/vtkQtConnection.cxx:62 >> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, >> caller=0x912420, event=67, callData=0x912460) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkCallbackCommand.cxx:42 >> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObject.cxx:616 >> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >> event=67, >> callData=0x912460) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >> r >> e/vtkObject.cxx:785 >> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >> (this=0x912420, >> session=0xb27240) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> C >> lientServerCore/Core/vtkProcessModule.cxx:378 >> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >> S >> erverManager/Core/vtkSMSession.cxx:308 >> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >> (this=0x8acc70, >> resource=...) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObj >> e >> ctBuilder.cxx:656 >> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >> (this=0xb24d00) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >> n >> Components/pqAlwaysConnectedBehavior.cxx:81 >> #47 0x00002aaaaaf7a8d6 in >> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >> (this=0xb24d00, parentObject=0xb19b40) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >> n >> Components/pqAlwaysConnectedBehavior.cxx:52 >> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >> n >> Components/pqParaViewBehaviors.cxx:157 >> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >> (this=0x8ff0b0) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/ >> P >> araView/ParaViewMainWindow.cxx:249 >> #50 0x000000000040accb in pqparaviewInitializer::Initialize >> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >> at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Application >> s >> /ParaView/pqparaviewInitializer.cxx:122 >> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Application >> s >> /ParaView/paraview_main.cxx:117 >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, March 10, 2017 11:47 AM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> Joe, >> >> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the >> environment and see if it goes further? >> >> Thanks >> Utkarsh >> >> >> CLASSIFICATION: UNCLASSIFIED > > > CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 16 14:22:20 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Mar 2017 14:22:20 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> Message-ID: Another thing to confirm (that I forgot to mention), you're forcing remoting rendering ie.. from Edit | Settings | Render View, ensure Remote Render Threshold is set to 0. On Thu, Mar 16, 2017 at 2:15 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > Utkarsh, > > I have tested on Excalibur and close all views, split views > and/or create new views all work as long as the environment variable > > PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 > > On another system the ARL utility server, it has the same behavior, > segfaulting unless the environment variable is set to 1. > Again, it works fine with close all views, split views > and/or create new views as long as the environment variable is set. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 > Fax: 410-278-8799 > Email: joseph.g.hennessey2.ctr at mail.mil > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Wednesday, March 15, 2017 11:14 AM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > Joe, > > Can you see if you close all views, split views and/or create new views if it > still works? I wonder if you're running to some GL/GLX issue with creating > multiple OpenGL contexts. > > There's also some known issue with creation of the offscreen context, or so I > am told, that encounters some issues on certain linuxes..you may be running > into that. > > Utkarsh > > On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) wrote: >> CLASSIFICATION: UNCLASSIFIED >> >> Utkarsh, >> >> You are correct, I had set the variable but not exported it. >> When I correctly exported the variable then ParaView 5.3.0-RC3 >> correctly launched without segfaulting. >> >> So, now I have a workaround at least. >> Is there anything else I should check for you? >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> Aberdeen Proving Ground, MD 21005 >> Voice: 410-278-3619 >> Fax: 410-278-8799 >> Email: joseph.g.hennessey2.ctr at mail.mil >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, March 10, 2017 12:10 PM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> All active links contained in this email were disabled. Please verify >> the identity of the sender, and confirm the authenticity of all links >> contained within the message prior to copying and pasting the address to a >> Web browser. >> >> >> >> >> ---- >> >> Joe, >> >> Something's not correct. If you look at the code in >> vtkPVDisplayInformation [1], it should not even get to line #108 if >> the environment variable was set correctly. >> >> Utkarsh >> >> [1] >> Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/ParaV >> iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 >> >> On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY >> RDECOM ARL >> (US) wrote: >>> CLASSIFICATION: UNCLASSIFIED >>> >>> Utkarsh, >>> >>> It fails at the same point with the variable set. >>> Here is the backtrace. (It is I think the same) >>> >>> Thanks, >>> >>> Joe >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> 0x00002aaad5d2e2af in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> (gdb) backtrace >>> #0 0x00002aaad5d2e2af in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> #1 0x00002aaad5d2e69f in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >>> #3 0x00002aaaaad01dc6 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #4 0x00002aaaaad04f84 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #5 0x00002aaaaad06559 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #6 0x00002aaaaad0726e in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >>> (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >>> #9 0x00002aaab1cabd72 in >>> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >>> #10 0x00002aaab1d46a52 in >>> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >>> (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >>> #11 0x00002aaab1d499f4 in >>> vtkXOpenGLRenderWindow::SetOffScreenRendering >>> (this=0x1daf950, i=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >>> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >>> (this=0x1daf950) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >>> #13 0x00002aaab1d44b9c in >>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>> (this=0x1daf950, __in_chrg=) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >>> #14 0x00002aaab1d44c7a in >>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>> (this=0x1daf950, __in_chrg=) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >>> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >>> (this=0x1daf950, >>> check=0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObjectBase.cxx:240 >>> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >>> (this=0x1daf950, o=0x0, check=0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObject.cxx:900 >>> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >>> o=0x0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObjectBase.cxx:197 >>> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister >>> (this=0x1daf950, >>> o=0x0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> Core/vtkRenderWindow.cxx:1420 >>> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObjectBase.cxx:142 >>> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >>> (this=0x1dae810) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Rendering >>> / >>> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >>> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally () >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> C >>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >>> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >>> (this=0xd36d30) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> C >>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >>> #23 0x00002aaaaefdb966 in vtkPVSessionCore::GatherInformationInternal >>> (this=0x8c6d70, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> S >>> erverImplementation/Core/vtkPVSessionCore.cxx:783 >>> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >>> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> S >>> erverImplementation/Core/vtkPVSessionCore.cxx:821 >>> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >>> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> S >>> erverImplementation/Core/vtkPVSessionBase.cxx:243 >>> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >>> (this=0xb25e60, server=0xe552b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >>> n >>> Components/pqDefaultViewBehavior.cxx:119 >>> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >>> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applicat >>> i >>> onComponents/moc_pqDefaultViewBehavior.cxx:54 >>> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >>> const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >>> (this=0x8acd90, >>> _t1=0xe552b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >>> _ >>> pqServerManagerModel.cxx:218 >>> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >>> (this=0x8acd90, id=1) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSer >>> v >>> erManagerModel.cxx:503 >>> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >>> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >>> _ >>> pqServerManagerModel.cxx:160 >>> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >>> const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >>> (this=0x8c8a80, _t1=1) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >>> _ >>> pqServerManagerObserver.cxx:170 >>> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >>> (this=0x8c8a80, callData=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSer >>> v >>> erManagerObserver.cxx:110 >>> #35 0x00002aaaacbd01d2 in pqServerManagerObserver::qt_static_metacall >>> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/moc >>> _ >>> pqServerManagerObserver.cxx:90 >>> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, QMetaObject >>> const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute >>> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISupp >>> o >>> rt/Qt/moc_vtkQtConnection.cxx:103 >>> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >>> caller=0x912420, e=67, call_data=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppor >>> t >>> /Qt/vtkQtConnection.cxx:72 >>> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >>> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppor >>> t >>> /Qt/vtkQtConnection.cxx:62 >>> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute (this=0x88b020, >>> caller=0x912420, event=67, callData=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkCallbackCommand.cxx:42 >>> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >>> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObject.cxx:616 >>> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >>> event=67, >>> callData=0x912460) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/Co >>> r >>> e/vtkObject.cxx:785 >>> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >>> (this=0x912420, >>> session=0xb27240) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> C >>> lientServerCore/Core/vtkProcessModule.cxx:378 >>> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore/ >>> S >>> erverManager/Core/vtkSMSession.cxx:308 >>> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >>> (this=0x8acc70, >>> resource=...) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqObj >>> e >>> ctBuilder.cxx:656 >>> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >>> (this=0xb24d00) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >>> n >>> Components/pqAlwaysConnectedBehavior.cxx:81 >>> #47 0x00002aaaaaf7a8d6 in >>> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >>> (this=0xb24d00, parentObject=0xb19b40) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >>> n >>> Components/pqAlwaysConnectedBehavior.cxx:52 >>> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >>> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicatio >>> n >>> Components/pqParaViewBehaviors.cxx:157 >>> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >>> (this=0x8ff0b0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications/ >>> P >>> araView/ParaViewMainWindow.cxx:249 >>> #50 0x000000000040accb in pqparaviewInitializer::Initialize >>> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Application >>> s >>> /ParaView/pqparaviewInitializer.cxx:122 >>> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Application >>> s >>> /ParaView/paraview_main.cxx:117 >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Joseph G. Hennessey Ph.D., SAIC >>> Team SAIC >>> Army Research Lab >>> DOD Supercomputing Resource Center >>> >>> >>> -----Original Message----- >>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] >>> Sent: Friday, March 10, 2017 11:47 AM >>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>> >>> Cc: ParaView Developers >>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>> minimum nvidia driver level that works with ParaView 5.3.0 >>> (UNCLASSIFIED) >>> >>> Joe, >>> >>> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in the >>> environment and see if it goes further? >>> >>> Thanks >>> Utkarsh >>> >>> >>> CLASSIFICATION: UNCLASSIFIED >> >> >> CLASSIFICATION: UNCLASSIFIED From joseph.g.hennessey2.ctr at mail.mil Thu Mar 16 15:56:31 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Thu, 16 Mar 2017 19:56:31 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E4F60C@UCOLHPUD.easf.csd.disa.mil> Utkarsh, I tried it with forcing remoting rendering ie.. from Edit | Settings | Render View, ensure Remote Render Threshold is set to 0 and with the value set to 20 (the default) and it does not seem to affect the operation. I have tried it under SRD in client mode and in client server mode and it still works fine as long as that variable is set. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Voice: 410-278-3619 Fax: 410-278-8799 Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Thursday, March 16, 2017 2:22 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers ; Su, Simon M CIV USARMY RDECOM ARL (US) Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) Another thing to confirm (that I forgot to mention), you're forcing remoting rendering ie.. from Edit | Settings | Render View, ensure Remote Render Threshold is set to 0. On Thu, Mar 16, 2017 at 2:15 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > Utkarsh, > > I have tested on Excalibur and close all views, split views and/or > create new views all work as long as the environment variable > > PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 > > On another system the ARL utility server, it has the same behavior, > segfaulting unless the environment variable is set to 1. > Again, it works fine with close all views, split views and/or create > new views as long as the environment variable is set. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 > Fax: 410-278-8799 > Email: joseph.g.hennessey2.ctr at mail.mil > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Wednesday, March 15, 2017 11:14 AM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > minimum nvidia driver level that works with ParaView 5.3.0 > (UNCLASSIFIED) > > Joe, > > Can you see if you close all views, split views and/or create new > views if it still works? I wonder if you're running to some GL/GLX > issue with creating multiple OpenGL contexts. > > There's also some known issue with creation of the offscreen context, > or so I am told, that encounters some issues on certain linuxes..you > may be running into that. > > Utkarsh > > On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY > RDECOM ARL > (US) wrote: >> CLASSIFICATION: UNCLASSIFIED >> >> Utkarsh, >> >> You are correct, I had set the variable but not exported it. >> When I correctly exported the variable then ParaView 5.3.0-RC3 >> correctly launched without segfaulting. >> >> So, now I have a workaround at least. >> Is there anything else I should check for you? >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> Aberdeen Proving Ground, MD 21005 >> Voice: 410-278-3619 >> Fax: 410-278-8799 >> Email: joseph.g.hennessey2.ctr at mail.mil >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, March 10, 2017 12:10 PM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> All active links contained in this email were disabled. Please >> verify the identity of the sender, and confirm the authenticity of >> all links contained within the message prior to copying and pasting >> the address to a Web browser. >> >> >> >> >> ---- >> >> Joe, >> >> Something's not correct. If you look at the code in >> vtkPVDisplayInformation [1], it should not even get to line #108 if >> the environment variable was set correctly. >> >> Utkarsh >> >> [1] >> Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/Para >> V >> iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 >> >> On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY >> RDECOM ARL >> (US) wrote: >>> CLASSIFICATION: UNCLASSIFIED >>> >>> Utkarsh, >>> >>> It fails at the same point with the variable set. >>> Here is the backtrace. (It is I think the same) >>> >>> Thanks, >>> >>> Joe >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> 0x00002aaad5d2e2af in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> (gdb) backtrace >>> #0 0x00002aaad5d2e2af in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> #1 0x00002aaad5d2e69f in ?? () from >>> /usr/lib64/libnvidia-glcore.so.352.68 >>> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >>> #3 0x00002aaaaad01dc6 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #4 0x00002aaaaad04f84 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #5 0x00002aaaaad06559 in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #6 0x00002aaaaad0726e in ?? () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >>> (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >>> #9 0x00002aaab1cabd72 in >>> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >>> #10 0x00002aaab1d46a52 in >>> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >>> (this=0x1daf950) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >>> #11 0x00002aaab1d499f4 in >>> vtkXOpenGLRenderWindow::SetOffScreenRendering >>> (this=0x1daf950, i=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >>> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >>> (this=0x1daf950) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >>> #13 0x00002aaab1d44b9c in >>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>> (this=0x1daf950, __in_chrg=) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >>> #14 0x00002aaab1d44c7a in >>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>> (this=0x1daf950, __in_chrg=) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >>> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >>> (this=0x1daf950, >>> check=0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObjectBase.cxx:240 >>> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >>> (this=0x1daf950, o=0x0, check=0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObject.cxx:900 >>> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >>> o=0x0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObjectBase.cxx:197 >>> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister >>> (this=0x1daf950, >>> o=0x0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> Core/vtkRenderWindow.cxx:1420 >>> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObjectBase.cxx:142 >>> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >>> (this=0x1dae810) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>> g >>> / >>> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >>> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally >>> () >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> C >>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >>> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >>> (this=0xd36d30) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> C >>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >>> #23 0x00002aaaaefdb966 in >>> vtkPVSessionCore::GatherInformationInternal >>> (this=0x8c6d70, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> S >>> erverImplementation/Core/vtkPVSessionCore.cxx:783 >>> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >>> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> S >>> erverImplementation/Core/vtkPVSessionCore.cxx:821 >>> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >>> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> S >>> erverImplementation/Core/vtkPVSessionBase.cxx:243 >>> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >>> (this=0xb25e60, server=0xe552b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>> o >>> n >>> Components/pqDefaultViewBehavior.cxx:119 >>> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >>> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applica >>> t >>> i >>> onComponents/moc_pqDefaultViewBehavior.cxx:54 >>> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>> QMetaObject const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >>> (this=0x8acd90, >>> _t1=0xe552b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>> c >>> _ >>> pqServerManagerModel.cxx:218 >>> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >>> (this=0x8acd90, id=1) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>> r >>> v >>> erManagerModel.cxx:503 >>> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >>> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>> c >>> _ >>> pqServerManagerModel.cxx:160 >>> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>> QMetaObject const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >>> (this=0x8c8a80, _t1=1) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>> c >>> _ >>> pqServerManagerObserver.cxx:170 >>> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >>> (this=0x8c8a80, callData=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>> r >>> v >>> erManagerObserver.cxx:110 >>> #35 0x00002aaaacbd01d2 in >>> pqServerManagerObserver::qt_static_metacall >>> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>> c >>> _ >>> pqServerManagerObserver.cxx:90 >>> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>> QMetaObject const*, int, void**) () from >>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute >>> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISup >>> p >>> o >>> rt/Qt/moc_vtkQtConnection.cxx:103 >>> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >>> caller=0x912420, e=67, call_data=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>> r >>> t >>> /Qt/vtkQtConnection.cxx:72 >>> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >>> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>> r >>> t >>> /Qt/vtkQtConnection.cxx:62 >>> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute >>> (this=0x88b020, caller=0x912420, event=67, callData=0x912460) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkCallbackCommand.cxx:42 >>> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >>> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObject.cxx:616 >>> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >>> event=67, >>> callData=0x912460) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>> o >>> r >>> e/vtkObject.cxx:785 >>> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >>> (this=0x912420, >>> session=0xb27240) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> C >>> lientServerCore/Core/vtkProcessModule.cxx:378 >>> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>> / >>> S >>> erverManager/Core/vtkSMSession.cxx:308 >>> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >>> (this=0x8acc70, >>> resource=...) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqOb >>> j >>> e >>> ctBuilder.cxx:656 >>> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >>> (this=0xb24d00) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>> o >>> n >>> Components/pqAlwaysConnectedBehavior.cxx:81 >>> #47 0x00002aaaaaf7a8d6 in >>> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >>> (this=0xb24d00, parentObject=0xb19b40) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>> o >>> n >>> Components/pqAlwaysConnectedBehavior.cxx:52 >>> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >>> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>> o >>> n >>> Components/pqParaViewBehaviors.cxx:157 >>> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >>> (this=0x8ff0b0) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications >>> / >>> P >>> araView/ParaViewMainWindow.cxx:249 >>> #50 0x000000000040accb in pqparaviewInitializer::Initialize >>> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >>> at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>> n >>> s >>> /ParaView/pqparaviewInitializer.cxx:122 >>> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>> n >>> s >>> /ParaView/paraview_main.cxx:117 >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Joseph G. Hennessey Ph.D., SAIC >>> Team SAIC >>> Army Research Lab >>> DOD Supercomputing Resource Center >>> >>> >>> -----Original Message----- >>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] >>> Sent: Friday, March 10, 2017 11:47 AM >>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>> >>> Cc: ParaView Developers >>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>> minimum nvidia driver level that works with ParaView 5.3.0 >>> (UNCLASSIFIED) >>> >>> Joe, >>> >>> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in >>> the environment and see if it goes further? >>> >>> Thanks >>> Utkarsh >>> >>> >>> CLASSIFICATION: UNCLASSIFIED >> >> >> CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 16 16:01:21 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Mar 2017 16:01:21 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E4F60C@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F60C@UCOLHPUD.easf.csd.disa.mil> Message-ID: Hmm okay. In which case it may indeed be the issue with offscreen buffer creation. I'll follow up with Ken and let you know when those fixes are merged in so we can try again. On Thu, Mar 16, 2017 at 3:56 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > Utkarsh, > > I tried it with forcing remoting rendering ie.. from Edit | Settings | Render > View, ensure Remote Render Threshold is set to 0 > and with the value set to 20 (the default) and it does not seem to affect the > operation. I have tried it under SRD in client mode > and in client server mode and it still works fine as long as that variable is > set. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 > Fax: 410-278-8799 > Email: joseph.g.hennessey2.ctr at mail.mil > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Thursday, March 16, 2017 2:22 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: ParaView Developers ; Su, Simon M CIV > USARMY RDECOM ARL (US) > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > Another thing to confirm (that I forgot to mention), you're forcing remoting > rendering ie.. from Edit | Settings | Render View, ensure Remote Render > Threshold is set to 0. > > On Thu, Mar 16, 2017 at 2:15 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) wrote: >> Utkarsh, >> >> I have tested on Excalibur and close all views, split views and/or >> create new views all work as long as the environment variable >> >> PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 >> >> On another system the ARL utility server, it has the same behavior, >> segfaulting unless the environment variable is set to 1. >> Again, it works fine with close all views, split views and/or create >> new views as long as the environment variable is set. >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> Aberdeen Proving Ground, MD 21005 >> Voice: 410-278-3619 >> Fax: 410-278-8799 >> Email: joseph.g.hennessey2.ctr at mail.mil >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Wednesday, March 15, 2017 11:14 AM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> Joe, >> >> Can you see if you close all views, split views and/or create new >> views if it still works? I wonder if you're running to some GL/GLX >> issue with creating multiple OpenGL contexts. >> >> There's also some known issue with creation of the offscreen context, >> or so I am told, that encounters some issues on certain linuxes..you >> may be running into that. >> >> Utkarsh >> >> On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY >> RDECOM ARL >> (US) wrote: >>> CLASSIFICATION: UNCLASSIFIED >>> >>> Utkarsh, >>> >>> You are correct, I had set the variable but not exported it. >>> When I correctly exported the variable then ParaView 5.3.0-RC3 >>> correctly launched without segfaulting. >>> >>> So, now I have a workaround at least. >>> Is there anything else I should check for you? >>> >>> Thanks, >>> >>> Joe >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Joseph G. Hennessey Ph.D., SAIC >>> Team SAIC >>> Army Research Lab >>> DOD Supercomputing Resource Center >>> Aberdeen Proving Ground, MD 21005 >>> Voice: 410-278-3619 >>> Fax: 410-278-8799 >>> Email: joseph.g.hennessey2.ctr at mail.mil >>> >>> >>> -----Original Message----- >>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> Sent: Friday, March 10, 2017 12:10 PM >>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>> >>> Cc: ParaView Developers >>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>> minimum nvidia driver level that works with ParaView 5.3.0 >>> (UNCLASSIFIED) >>> >>> All active links contained in this email were disabled. Please >>> verify the identity of the sender, and confirm the authenticity of >>> all links contained within the message prior to copying and pasting >>> the address to a Web browser. >>> >>> >>> >>> >>> ---- >>> >>> Joe, >>> >>> Something's not correct. If you look at the code in >>> vtkPVDisplayInformation [1], it should not even get to line #108 if >>> the environment variable was set correctly. >>> >>> Utkarsh >>> >>> [1] >>> Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/Para >>> V >>> iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 >>> >>> On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY >>> RDECOM ARL >>> (US) wrote: >>>> CLASSIFICATION: UNCLASSIFIED >>>> >>>> Utkarsh, >>>> >>>> It fails at the same point with the variable set. >>>> Here is the backtrace. (It is I think the same) >>>> >>>> Thanks, >>>> >>>> Joe >>>> >>>> Program received signal SIGSEGV, Segmentation fault. >>>> 0x00002aaad5d2e2af in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> (gdb) backtrace >>>> #0 0x00002aaad5d2e2af in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> #1 0x00002aaad5d2e69f in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >>>> #3 0x00002aaaaad01dc6 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #4 0x00002aaaaad04f84 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #5 0x00002aaaaad06559 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #6 0x00002aaaaad0726e in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >>>> (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >>>> #9 0x00002aaab1cabd72 in >>>> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >>>> #10 0x00002aaab1d46a52 in >>>> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >>>> (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >>>> #11 0x00002aaab1d499f4 in >>>> vtkXOpenGLRenderWindow::SetOffScreenRendering >>>> (this=0x1daf950, i=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >>>> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >>>> (this=0x1daf950) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >>>> #13 0x00002aaab1d44b9c in >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>>> (this=0x1daf950, __in_chrg=) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >>>> #14 0x00002aaab1d44c7a in >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>>> (this=0x1daf950, __in_chrg=) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >>>> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >>>> (this=0x1daf950, >>>> check=0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:240 >>>> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >>>> (this=0x1daf950, o=0x0, check=0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:900 >>>> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >>>> o=0x0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:197 >>>> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister >>>> (this=0x1daf950, >>>> o=0x0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> Core/vtkRenderWindow.cxx:1420 >>>> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:142 >>>> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >>>> (this=0x1dae810) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >>>> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally >>>> () >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >>>> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >>>> (this=0xd36d30) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >>>> #23 0x00002aaaaefdb966 in >>>> vtkPVSessionCore::GatherInformationInternal >>>> (this=0x8c6d70, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionCore.cxx:783 >>>> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >>>> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionCore.cxx:821 >>>> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >>>> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionBase.cxx:243 >>>> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >>>> (this=0xb25e60, server=0xe552b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqDefaultViewBehavior.cxx:119 >>>> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >>>> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applica >>>> t >>>> i >>>> onComponents/moc_pqDefaultViewBehavior.cxx:54 >>>> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >>>> (this=0x8acd90, >>>> _t1=0xe552b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerModel.cxx:218 >>>> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >>>> (this=0x8acd90, id=1) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>>> r >>>> v >>>> erManagerModel.cxx:503 >>>> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >>>> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerModel.cxx:160 >>>> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >>>> (this=0x8c8a80, _t1=1) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerObserver.cxx:170 >>>> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >>>> (this=0x8c8a80, callData=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>>> r >>>> v >>>> erManagerObserver.cxx:110 >>>> #35 0x00002aaaacbd01d2 in >>>> pqServerManagerObserver::qt_static_metacall >>>> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerObserver.cxx:90 >>>> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute >>>> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISup >>>> p >>>> o >>>> rt/Qt/moc_vtkQtConnection.cxx:103 >>>> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >>>> caller=0x912420, e=67, call_data=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>>> r >>>> t >>>> /Qt/vtkQtConnection.cxx:72 >>>> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >>>> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>>> r >>>> t >>>> /Qt/vtkQtConnection.cxx:62 >>>> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute >>>> (this=0x88b020, caller=0x912420, event=67, callData=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkCallbackCommand.cxx:42 >>>> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >>>> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:616 >>>> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >>>> event=67, >>>> callData=0x912460) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:785 >>>> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >>>> (this=0x912420, >>>> session=0xb27240) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Core/vtkProcessModule.cxx:378 >>>> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverManager/Core/vtkSMSession.cxx:308 >>>> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >>>> (this=0x8acc70, >>>> resource=...) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqOb >>>> j >>>> e >>>> ctBuilder.cxx:656 >>>> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >>>> (this=0xb24d00) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqAlwaysConnectedBehavior.cxx:81 >>>> #47 0x00002aaaaaf7a8d6 in >>>> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >>>> (this=0xb24d00, parentObject=0xb19b40) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqAlwaysConnectedBehavior.cxx:52 >>>> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >>>> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqParaViewBehaviors.cxx:157 >>>> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >>>> (this=0x8ff0b0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications >>>> / >>>> P >>>> araView/ParaViewMainWindow.cxx:249 >>>> #50 0x000000000040accb in pqparaviewInitializer::Initialize >>>> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>>> n >>>> s >>>> /ParaView/pqparaviewInitializer.cxx:122 >>>> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>>> n >>>> s >>>> /ParaView/paraview_main.cxx:117 >>>> >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> Joseph G. Hennessey Ph.D., SAIC >>>> Team SAIC >>>> Army Research Lab >>>> DOD Supercomputing Resource Center >>>> >>>> >>>> -----Original Message----- >>>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] >>>> Sent: Friday, March 10, 2017 11:47 AM >>>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>>> >>>> Cc: ParaView Developers >>>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>>> minimum nvidia driver level that works with ParaView 5.3.0 >>>> (UNCLASSIFIED) >>>> >>>> Joe, >>>> >>>> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in >>>> the environment and see if it goes further? >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> >>>> CLASSIFICATION: UNCLASSIFIED >>> >>> >>> CLASSIFICATION: UNCLASSIFIED From chuck.atkins at kitware.com Fri Mar 17 15:38:56 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Fri, 17 Mar 2017 15:38:56 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F60C@UCOLHPUD.easf.csd.disa.mil> Message-ID: Since you're running it under SRD, I don't think you're actually getting a connection to the GPU. I suspect it's likely an issue with VirtualGL and VNC and how it's forwarding things on to the underlying GPU. Not that I have any idea how to fix it right now but that's probably a good place to start looking. - Chuck On Thu, Mar 16, 2017 at 4:01 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Hmm okay. In which case it may indeed be the issue with offscreen > buffer creation. I'll follow up with Ken and let you know when those > fixes are merged in so we can try again. > > On Thu, Mar 16, 2017 at 3:56 PM, Hennessey, Joseph G CTR USARMY RDECOM > ARL (US) wrote: > > Utkarsh, > > > > I tried it with forcing remoting rendering ie.. from Edit | Settings | > Render > > View, ensure Remote Render Threshold is set to 0 > > and with the value set to 20 (the default) and it does not seem to > affect the > > operation. I have tried it under SRD in client mode > > and in client server mode and it still works fine as long as that > variable is > > set. > > > > Thanks, > > > > Joe > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Joseph G. Hennessey Ph.D., SAIC > > Team SAIC > > Army Research Lab > > DOD Supercomputing Resource Center > > Aberdeen Proving Ground, MD 21005 > > Voice: 410-278-3619 > > Fax: 410-278-8799 > > Email: joseph.g.hennessey2.ctr at mail.mil > > > > > > -----Original Message----- > > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > > Sent: Thursday, March 16, 2017 2:22 PM > > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > > > Cc: ParaView Developers ; Su, Simon M > CIV > > USARMY RDECOM ARL (US) > > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > minimum > > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > > > Another thing to confirm (that I forgot to mention), you're forcing > remoting > > rendering ie.. from Edit | Settings | Render View, ensure Remote Render > > Threshold is set to 0. > > > > On Thu, Mar 16, 2017 at 2:15 PM, Hennessey, Joseph G CTR USARMY RDECOM > ARL > > (US) wrote: > >> Utkarsh, > >> > >> I have tested on Excalibur and close all views, split views and/or > >> create new views all work as long as the environment variable > >> > >> PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 > >> > >> On another system the ARL utility server, it has the same behavior, > >> segfaulting unless the environment variable is set to 1. > >> Again, it works fine with close all views, split views and/or create > >> new views as long as the environment variable is set. > >> > >> Thanks, > >> > >> Joe > >> > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> Joseph G. Hennessey Ph.D., SAIC > >> Team SAIC > >> Army Research Lab > >> DOD Supercomputing Resource Center > >> Aberdeen Proving Ground, MD 21005 > >> Voice: 410-278-3619 > >> Fax: 410-278-8799 > >> Email: joseph.g.hennessey2.ctr at mail.mil > >> > >> > >> -----Original Message----- > >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Sent: Wednesday, March 15, 2017 11:14 AM > >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > >> > >> Cc: ParaView Developers > >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > >> minimum nvidia driver level that works with ParaView 5.3.0 > >> (UNCLASSIFIED) > >> > >> Joe, > >> > >> Can you see if you close all views, split views and/or create new > >> views if it still works? I wonder if you're running to some GL/GLX > >> issue with creating multiple OpenGL contexts. > >> > >> There's also some known issue with creation of the offscreen context, > >> or so I am told, that encounters some issues on certain linuxes..you > >> may be running into that. > >> > >> Utkarsh > >> > >> On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY > >> RDECOM ARL > >> (US) wrote: > >>> CLASSIFICATION: UNCLASSIFIED > >>> > >>> Utkarsh, > >>> > >>> You are correct, I had set the variable but not exported it. > >>> When I correctly exported the variable then ParaView 5.3.0-RC3 > >>> correctly launched without segfaulting. > >>> > >>> So, now I have a workaround at least. > >>> Is there anything else I should check for you? > >>> > >>> Thanks, > >>> > >>> Joe > >>> > >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >>> Joseph G. Hennessey Ph.D., SAIC > >>> Team SAIC > >>> Army Research Lab > >>> DOD Supercomputing Resource Center > >>> Aberdeen Proving Ground, MD 21005 > >>> Voice: 410-278-3619 > >>> Fax: 410-278-8799 > >>> Email: joseph.g.hennessey2.ctr at mail.mil > >>> > >>> > >>> -----Original Message----- > >>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >>> Sent: Friday, March 10, 2017 12:10 PM > >>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > >>> > >>> Cc: ParaView Developers > >>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > >>> minimum nvidia driver level that works with ParaView 5.3.0 > >>> (UNCLASSIFIED) > >>> > >>> All active links contained in this email were disabled. Please > >>> verify the identity of the sender, and confirm the authenticity of > >>> all links contained within the message prior to copying and pasting > >>> the address to a Web browser. > >>> > >>> > >>> > >>> > >>> ---- > >>> > >>> Joe, > >>> > >>> Something's not correct. If you look at the code in > >>> vtkPVDisplayInformation [1], it should not even get to line #108 if > >>> the environment variable was set correctly. > >>> > >>> Utkarsh > >>> > >>> [1] > >>> Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/Para > >>> V > >>> iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 > >>> > >>> On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY > >>> RDECOM ARL > >>> (US) wrote: > >>>> CLASSIFICATION: UNCLASSIFIED > >>>> > >>>> Utkarsh, > >>>> > >>>> It fails at the same point with the variable set. > >>>> Here is the backtrace. (It is I think the same) > >>>> > >>>> Thanks, > >>>> > >>>> Joe > >>>> > >>>> Program received signal SIGSEGV, Segmentation fault. > >>>> 0x00002aaad5d2e2af in ?? () from > >>>> /usr/lib64/libnvidia-glcore.so.352.68 > >>>> (gdb) backtrace > >>>> #0 0x00002aaad5d2e2af in ?? () from > >>>> /usr/lib64/libnvidia-glcore.so.352.68 > >>>> #1 0x00002aaad5d2e69f in ?? () from > >>>> /usr/lib64/libnvidia-glcore.so.352.68 > >>>> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 > >>>> #3 0x00002aaaaad01dc6 in ?? () from > >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > >>>> #4 0x00002aaaaad04f84 in ?? () from > >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > >>>> #5 0x00002aaaaad06559 in ?? () from > >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > >>>> #6 0x00002aaaaad0726e in ?? () from > >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > >>>> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from > >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so > >>>> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow > >>>> (this=0x1daf950) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 > >>>> #9 0x00002aaab1cabd72 in > >>>> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow > (this=0x1daf950) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 > >>>> #10 0x00002aaab1d46a52 in > >>>> vtkXOpenGLRenderWindow::DestroyOffScreenWindow > >>>> (this=0x1daf950) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 > >>>> #11 0x00002aaab1d499f4 in > >>>> vtkXOpenGLRenderWindow::SetOffScreenRendering > >>>> (this=0x1daf950, i=0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 > >>>> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize > >>>> (this=0x1daf950) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 > >>>> #13 0x00002aaab1d44b9c in > >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > >>>> (this=0x1daf950, __in_chrg=) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 > >>>> #14 0x00002aaab1d44c7a in > >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow > >>>> (this=0x1daf950, __in_chrg=) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 > >>>> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal > >>>> (this=0x1daf950, > >>>> check=0) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObjectBase.cxx:240 > >>>> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal > >>>> (this=0x1daf950, o=0x0, check=0) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObject.cxx:900 > >>>> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, > >>>> o=0x0) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObjectBase.cxx:197 > >>>> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister > >>>> (this=0x1daf950, > >>>> o=0x0) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> Core/vtkRenderWindow.cxx:1420 > >>>> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObjectBase.cxx:142 > >>>> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL > >>>> (this=0x1dae810) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin > >>>> g > >>>> / > >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 > >>>> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation:: > SupportsOpenGLLocally > >>>> () > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> C > >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 > >>>> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject > >>>> (this=0xd36d30) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> C > >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 > >>>> #23 0x00002aaaaefdb966 in > >>>> vtkPVSessionCore::GatherInformationInternal > >>>> (this=0x8c6d70, information=0xd36d30, globalid=0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> S > >>>> erverImplementation/Core/vtkPVSessionCore.cxx:783 > >>>> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation > >>>> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> S > >>>> erverImplementation/Core/vtkPVSessionCore.cxx:821 > >>>> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation > >>>> (this=0xb27240, location=4, information=0xd36d30, globalid=0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> S > >>>> erverImplementation/Core/vtkPVSessionBase.cxx:243 > >>>> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation > >>>> (this=0xb25e60, server=0xe552b0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati > >>>> o > >>>> n > >>>> Components/pqDefaultViewBehavior.cxx:119 > >>>> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall > >>>> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, > _a=0x7fffffff6e80) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applica > >>>> t > >>>> i > >>>> onComponents/moc_pqDefaultViewBehavior.cxx:54 > >>>> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, > >>>> QMetaObject const*, int, void**) () from > >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > >>>> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded > >>>> (this=0x8acd90, > >>>> _t1=0xe552b0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo > >>>> c > >>>> _ > >>>> pqServerManagerModel.cxx:218 > >>>> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated > >>>> (this=0x8acd90, id=1) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe > >>>> r > >>>> v > >>>> erManagerModel.cxx:503 > >>>> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall > >>>> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, > _a=0x7fffffff7080) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo > >>>> c > >>>> _ > >>>> pqServerManagerModel.cxx:160 > >>>> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, > >>>> QMetaObject const*, int, void**) () from > >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > >>>> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated > >>>> (this=0x8c8a80, _t1=1) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo > >>>> c > >>>> _ > >>>> pqServerManagerObserver.cxx:170 > >>>> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated > >>>> (this=0x8c8a80, callData=0x912460) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe > >>>> r > >>>> v > >>>> erManagerObserver.cxx:110 > >>>> #35 0x00002aaaacbd01d2 in > >>>> pqServerManagerObserver::qt_static_metacall > >>>> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, > _a=0x7fffffff7290) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo > >>>> c > >>>> _ > >>>> pqServerManagerObserver.cxx:90 > >>>> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, > >>>> QMetaObject const*, int, void**) () from > >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 > >>>> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute > >>>> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, > _t5=0x88b020) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISup > >>>> p > >>>> o > >>>> rt/Qt/moc_vtkQtConnection.cxx:103 > >>>> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, > >>>> caller=0x912420, e=67, call_data=0x912460) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo > >>>> r > >>>> t > >>>> /Qt/vtkQtConnection.cxx:72 > >>>> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback > >>>> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo > >>>> r > >>>> t > >>>> /Qt/vtkQtConnection.cxx:62 > >>>> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute > >>>> (this=0x88b020, caller=0x912420, event=67, callData=0x912460) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkCallbackCommand.cxx:42 > >>>> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent > >>>> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObject.cxx:616 > >>>> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, > >>>> event=67, > >>>> callData=0x912460) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C > >>>> o > >>>> r > >>>> e/vtkObject.cxx:785 > >>>> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession > >>>> (this=0x912420, > >>>> session=0xb27240) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> C > >>>> lientServerCore/Core/vtkProcessModule.cxx:378 > >>>> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore > >>>> / > >>>> S > >>>> erverManager/Core/vtkSMSession.cxx:308 > >>>> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer > >>>> (this=0x8acc70, > >>>> resource=...) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqOb > >>>> j > >>>> e > >>>> ctBuilder.cxx:656 > >>>> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck > >>>> (this=0xb24d00) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati > >>>> o > >>>> n > >>>> Components/pqAlwaysConnectedBehavior.cxx:81 > >>>> #47 0x00002aaaaaf7a8d6 in > >>>> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior > >>>> (this=0xb24d00, parentObject=0xb19b40) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati > >>>> o > >>>> n > >>>> Components/pqAlwaysConnectedBehavior.cxx:52 > >>>> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors > >>>> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati > >>>> o > >>>> n > >>>> Components/pqParaViewBehaviors.cxx:157 > >>>> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow > >>>> (this=0x8ff0b0) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications > >>>> / > >>>> P > >>>> araView/ParaViewMainWindow.cxx:249 > >>>> #50 0x000000000040accb in pqparaviewInitializer::Initialize > >>>> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) > >>>> at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio > >>>> n > >>>> s > >>>> /ParaView/pqparaviewInitializer.cxx:122 > >>>> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at > >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio > >>>> n > >>>> s > >>>> /ParaView/paraview_main.cxx:117 > >>>> > >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >>>> Joseph G. Hennessey Ph.D., SAIC > >>>> Team SAIC > >>>> Army Research Lab > >>>> DOD Supercomputing Resource Center > >>>> > >>>> > >>>> -----Original Message----- > >>>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com] > >>>> Sent: Friday, March 10, 2017 11:47 AM > >>>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > >>>> > >>>> Cc: ParaView Developers > >>>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the > >>>> minimum nvidia driver level that works with ParaView 5.3.0 > >>>> (UNCLASSIFIED) > >>>> > >>>> Joe, > >>>> > >>>> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in > >>>> the environment and see if it goes further? > >>>> > >>>> Thanks > >>>> Utkarsh > >>>> > >>>> > >>>> CLASSIFICATION: UNCLASSIFIED > >>> > >>> > >>> CLASSIFICATION: UNCLASSIFIED > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Fri Mar 17 15:50:27 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Fri, 17 Mar 2017 15:50:27 -0400 Subject: [Paraview-developers] Unload a loaded plugin Message-ID: Hello, I'm currently working on a custom paraview version and now I'm trying to dynamicallyreplace xml python plugins by their newer versions but I didn't find any remove / unload function in the interface of plugin managers (pqPluginManager, vtkSMPluginManager) except pqPluginManager::hidePlugin which doesn't do what I want. There's only a function vtkPVPluginLoader::PluginLibraryUnloaded which's called in the destructor of every plugin via a macro in pqParaViewPlugin.cxx.in . Can I use it in my case? If not, is there any other solution? Thanks, Maxim From joseph.g.hennessey2.ctr at mail.mil Fri Mar 17 15:43:31 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Fri, 17 Mar 2017 19:43:31 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4091C@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40ACD@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40B75@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E40BCE@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F5CF@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E4F60C@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E50CA0@UCOLHPUD.easf.csd.disa.mil> Chuck, I have tested it on Excalibur SRD graphic nodes which are using hardware acceleration of the video cards. I have also tested it on the ARL utility server SRD nodes, which I do not believe are hardware accelerated. Both types of SRD nodes are segfaulting on startup if that environment variable is not set. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Voice: 410-278-3619 Fax: 410-278-8799 Email: joseph.g.hennessey2.ctr at mail.mil -----Original Message----- From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Friday, March 17, 2017 3:39 PM To: Utkarsh Ayachit Cc: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) ; Ken Martin ; ParaView Developers Subject: Re: [Paraview-developers] [Non-DoD Source] Re: What is the minimum nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Since you're running it under SRD, I don't think you're actually getting a connection to the GPU. I suspect it's likely an issue with VirtualGL and VNC and how it's forwarding things on to the underlying GPU. Not that I have any idea how to fix it right now but that's probably a good place to start looking. - Chuck On Thu, Mar 16, 2017 at 4:01 PM, Utkarsh Ayachit > wrote: Hmm okay. In which case it may indeed be the issue with offscreen buffer creation. I'll follow up with Ken and let you know when those fixes are merged in so we can try again. On Thu, Mar 16, 2017 at 3:56 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > wrote: > Utkarsh, > > I tried it with forcing remoting rendering ie.. from Edit | Settings | Render > View, ensure Remote Render Threshold is set to 0 > and with the value set to 20 (the default) and it does not seem to affect the > operation. I have tried it under SRD in client mode > and in client server mode and it still works fine as long as that variable is > set. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Voice: 410-278-3619 < tel:410-278-3619 > > Fax: 410-278-8799 < tel:410-278-8799 > > Email: joseph.g.hennessey2.ctr at mail.mil < Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > > > -----Original Message----- > From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com < Caution-mailto:utkarsh.ayachit at kitware.com > ] > Sent: Thursday, March 16, 2017 2:22 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > > Cc: ParaView Developers >; Su, Simon M CIV > USARMY RDECOM ARL (US) > > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the minimum > nvidia driver level that works with ParaView 5.3.0 (UNCLASSIFIED) > > Another thing to confirm (that I forgot to mention), you're forcing remoting > rendering ie.. from Edit | Settings | Render View, ensure Remote Render > Threshold is set to 0. > > On Thu, Mar 16, 2017 at 2:15 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) > wrote: >> Utkarsh, >> >> I have tested on Excalibur and close all views, split views and/or >> create new views all work as long as the environment variable >> >> PV_DEBUG_SKIP_OPENGL_VERSION_CHECK is set to 1 >> >> On another system the ARL utility server, it has the same behavior, >> segfaulting unless the environment variable is set to 1. >> Again, it works fine with close all views, split views and/or create >> new views as long as the environment variable is set. >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> Aberdeen Proving Ground, MD 21005 >> Voice: 410-278-3619 < tel:410-278-3619 > >> Fax: 410-278-8799 < tel:410-278-8799 > >> Email: joseph.g.hennessey2.ctr at mail.mil < Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > >> >> >> -----Original Message----- >> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com < Caution-mailto:utkarsh.ayachit at kitware.com > ] >> Sent: Wednesday, March 15, 2017 11:14 AM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> > >> Cc: ParaView Developers > >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >> minimum nvidia driver level that works with ParaView 5.3.0 >> (UNCLASSIFIED) >> >> Joe, >> >> Can you see if you close all views, split views and/or create new >> views if it still works? I wonder if you're running to some GL/GLX >> issue with creating multiple OpenGL contexts. >> >> There's also some known issue with creation of the offscreen context, >> or so I am told, that encounters some issues on certain linuxes..you >> may be running into that. >> >> Utkarsh >> >> On Fri, Mar 10, 2017 at 12:29 PM, Hennessey, Joseph G CTR USARMY >> RDECOM ARL >> (US) > wrote: >>> CLASSIFICATION: UNCLASSIFIED >>> >>> Utkarsh, >>> >>> You are correct, I had set the variable but not exported it. >>> When I correctly exported the variable then ParaView 5.3.0-RC3 >>> correctly launched without segfaulting. >>> >>> So, now I have a workaround at least. >>> Is there anything else I should check for you? >>> >>> Thanks, >>> >>> Joe >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Joseph G. Hennessey Ph.D., SAIC >>> Team SAIC >>> Army Research Lab >>> DOD Supercomputing Resource Center >>> Aberdeen Proving Ground, MD 21005 >>> Voice: 410-278-3619 < tel:410-278-3619 > >>> Fax: 410-278-8799 < tel:410-278-8799 > >>> Email: joseph.g.hennessey2.ctr at mail.mil < Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > >>> >>> >>> -----Original Message----- >>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com < Caution-mailto:utkarsh.ayachit at kitware.com > ] >>> Sent: Friday, March 10, 2017 12:10 PM >>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>> > >>> Cc: ParaView Developers > >>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>> minimum nvidia driver level that works with ParaView 5.3.0 >>> (UNCLASSIFIED) >>> >>> All active links contained in this email were disabled. Please >>> verify the identity of the sender, and confirm the authenticity of >>> all links contained within the message prior to copying and pasting >>> the address to a Web browser. >>> >>> >>> >>> >>> ---- >>> >>> Joe, >>> >>> Something's not correct. If you look at the code in >>> vtkPVDisplayInformation [1], it should not even get to line #108 if >>> the environment variable was set correctly. >>> >>> Utkarsh >>> >>> [1] >>> Caution-Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/Para < Caution-https://gitlab.kitware.com/paraview/paraview/blob/master/Para > >>> V >>> iewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx#L86-90 >>> >>> On Fri, Mar 10, 2017 at 12:02 PM, Hennessey, Joseph G CTR USARMY >>> RDECOM ARL >>> (US) > wrote: >>>> CLASSIFICATION: UNCLASSIFIED >>>> >>>> Utkarsh, >>>> >>>> It fails at the same point with the variable set. >>>> Here is the backtrace. (It is I think the same) >>>> >>>> Thanks, >>>> >>>> Joe >>>> >>>> Program received signal SIGSEGV, Segmentation fault. >>>> 0x00002aaad5d2e2af in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> (gdb) backtrace >>>> #0 0x00002aaad5d2e2af in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> #1 0x00002aaad5d2e69f in ?? () from >>>> /usr/lib64/libnvidia-glcore.so.352.68 >>>> #2 0x00002aaab8d9b8f7 in ?? () from /usr/lib64/libGL.so.1 >>>> #3 0x00002aaaaad01dc6 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #4 0x00002aaaaad04f84 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #5 0x00002aaaaad06559 in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #6 0x00002aaaaad0726e in ?? () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #7 0x00002aaaaacf5e80 in glXMakeCurrent () from >>>> /app/SRD/VirtualGL/2.3.3/fakelib64/librrfaker.so >>>> #8 0x00002aaab1d46735 in vtkXOpenGLRenderWindow::DestroyWindow >>>> (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:741 >>>> #9 0x00002aaab1cabd72 in >>>> vtkOpenGLRenderWindow::DestroyHardwareOffScreenWindow (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2177 >>>> #10 0x00002aaab1d46a52 in >>>> vtkXOpenGLRenderWindow::DestroyOffScreenWindow >>>> (this=0x1daf950) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:849 >>>> #11 0x00002aaab1d499f4 in >>>> vtkXOpenGLRenderWindow::SetOffScreenRendering >>>> (this=0x1daf950, i=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:1757 >>>> #12 0x00002aaab1d46c30 in vtkXOpenGLRenderWindow::Finalize >>>> (this=0x1daf950) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:930 >>>> #13 0x00002aaab1d44b9c in >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>>> (this=0x1daf950, __in_chrg=) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:357 >>>> #14 0x00002aaab1d44c7a in >>>> vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow >>>> (this=0x1daf950, __in_chrg=) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkXOpenGLRenderWindow.cxx:368 >>>> #15 0x00002aaab71b149d in vtkObjectBase::UnRegisterInternal >>>> (this=0x1daf950, >>>> check=0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:240 >>>> #16 0x00002aaab71b3a66 in vtkObject::UnRegisterInternal >>>> (this=0x1daf950, o=0x0, check=0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:900 >>>> #17 0x00002aaab71b1366 in vtkObjectBase::UnRegister (this=0x1daf950, >>>> o=0x0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:197 >>>> #18 0x00002aaab3fa0781 in vtkRenderWindow::UnRegister >>>> (this=0x1daf950, >>>> o=0x0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> Core/vtkRenderWindow.cxx:1420 >>>> #19 0x00002aaab71b10da in vtkObjectBase::Delete (this=0x1daf950) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObjectBase.cxx:142 >>>> #20 0x00002aaab1cac4c2 in vtkOpenGLRenderWindow::SupportsOpenGL >>>> (this=0x1dae810) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Renderin >>>> g >>>> / >>>> OpenGL2/vtkOpenGLRenderWindow.cxx:2338 >>>> #21 0x00002aaaba3b4b53 in vtkPVDisplayInformation::SupportsOpenGLLocally >>>> () >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 >>>> #22 0x00002aaaba3b4bd7 in vtkPVDisplayInformation::CopyFromObject >>>> (this=0xd36d30) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 >>>> #23 0x00002aaaaefdb966 in >>>> vtkPVSessionCore::GatherInformationInternal >>>> (this=0x8c6d70, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionCore.cxx:783 >>>> #24 0x00002aaaaefdbc21 in vtkPVSessionCore::GatherInformation >>>> (this=0x8c6d70, location=4, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionCore.cxx:821 >>>> #25 0x00002aaaaefd77ea in vtkPVSessionBase::GatherInformation >>>> (this=0xb27240, location=4, information=0xd36d30, globalid=0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverImplementation/Core/vtkPVSessionBase.cxx:243 >>>> #26 0x00002aaaaafbaea9 in pqDefaultViewBehavior::onServerCreation >>>> (this=0xb25e60, server=0xe552b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqDefaultViewBehavior.cxx:119 >>>> #27 0x00002aaaab04f4c2 in pqDefaultViewBehavior::qt_static_metacall >>>> (_o=0xb25e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffff6e80) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Applica >>>> t >>>> i >>>> onComponents/moc_pqDefaultViewBehavior.cxx:54 >>>> #28 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #29 0x00002aaaacbcf41f in pqServerManagerModel::serverAdded >>>> (this=0x8acd90, >>>> _t1=0xe552b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerModel.cxx:218 >>>> #30 0x00002aaaacb9b67f in pqServerManagerModel::onConnectionCreated >>>> (this=0x8acd90, id=1) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>>> r >>>> v >>>> erManagerModel.cxx:503 >>>> #31 0x00002aaaacbcf231 in pqServerManagerModel::qt_static_metacall >>>> (_o=0x8acd90, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffff7080) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerModel.cxx:160 >>>> #32 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #33 0x00002aaaacbd05ab in pqServerManagerObserver::connectionCreated >>>> (this=0x8c8a80, _t1=1) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerObserver.cxx:170 >>>> #34 0x00002aaaacb9f186 in pqServerManagerObserver::connectionCreated >>>> (this=0x8c8a80, callData=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqSe >>>> r >>>> v >>>> erManagerObserver.cxx:110 >>>> #35 0x00002aaaacbd01d2 in >>>> pqServerManagerObserver::qt_static_metacall >>>> (_o=0x8c8a80, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffff7290) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Qt/Core/mo >>>> c >>>> _ >>>> pqServerManagerObserver.cxx:90 >>>> #36 0x00002aaab06076ea in QMetaObject::activate(QObject*, >>>> QMetaObject const*, int, void**) () from >>>> /p/app/DAAC/paraview/5.3.0/lib/paraview-5.3/libQtCore.so.4 >>>> #37 0x00002aaaaff48373 in vtkQtConnection::EmitExecute >>>> (this=0x84c030, _t1=0x912420, _t2=67, _t3=0x0, _t4=0x912460, _t5=0x88b020) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/VTK/GUISup >>>> p >>>> o >>>> rt/Qt/moc_vtkQtConnection.cxx:103 >>>> #38 0x00002aaaaff36d36 in vtkQtConnection::Execute (this=0x84c030, >>>> caller=0x912420, e=67, call_data=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>>> r >>>> t >>>> /Qt/vtkQtConnection.cxx:72 >>>> #39 0x00002aaaaff36cd6 in vtkQtConnection::DoCallback >>>> (vtk_obj=0x912420, event=67, client_data=0x84c030, call_data=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/GUISuppo >>>> r >>>> t >>>> /Qt/vtkQtConnection.cxx:62 >>>> #40 0x00002aaab70a89b9 in vtkCallbackCommand::Execute >>>> (this=0x88b020, caller=0x912420, event=67, callData=0x912460) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkCallbackCommand.cxx:42 >>>> #41 0x00002aaab71b2d3e in vtkSubjectHelper::InvokeEvent >>>> (this=0x84bec0, event=67, callData=0x912460, self=0x912420) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:616 >>>> #42 0x00002aaab71b3245 in vtkObject::InvokeEvent (this=0x912420, >>>> event=67, >>>> callData=0x912460) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/VTK/Common/C >>>> o >>>> r >>>> e/vtkObject.cxx:785 >>>> #43 0x00002aaaafa05828 in vtkProcessModule::RegisterSession >>>> (this=0x912420, >>>> session=0xb27240) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> C >>>> lientServerCore/Core/vtkProcessModule.cxx:378 >>>> #44 0x00002aaaaec18373 in vtkSMSession::ConnectToSelf () at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/ParaViewCore >>>> / >>>> S >>>> erverManager/Core/vtkSMSession.cxx:308 >>>> #45 0x00002aaaacb5e0ca in pqObjectBuilder::createServer >>>> (this=0x8acc70, >>>> resource=...) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Core/pqOb >>>> j >>>> e >>>> ctBuilder.cxx:656 >>>> #46 0x00002aaaaaf7aa56 in pqAlwaysConnectedBehavior::serverCheck >>>> (this=0xb24d00) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqAlwaysConnectedBehavior.cxx:81 >>>> #47 0x00002aaaaaf7a8d6 in >>>> pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior >>>> (this=0xb24d00, parentObject=0xb19b40) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqAlwaysConnectedBehavior.cxx:52 >>>> #48 0x00002aaaaafec564 in pqParaViewBehaviors::pqParaViewBehaviors >>>> (this=0xb19b40, mainWindow=0x8ff0b0, parentObject=0x8ff0b0) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Qt/Applicati >>>> o >>>> n >>>> Components/pqParaViewBehaviors.cxx:157 >>>> #49 0x000000000040cb7e in ParaViewMainWindow::ParaViewMainWindow >>>> (this=0x8ff0b0) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/src/Applications >>>> / >>>> P >>>> araView/ParaViewMainWindow.cxx:249 >>>> #50 0x000000000040accb in pqparaviewInitializer::Initialize >>>> (this=0x7fffffff7bb0, argc=1, argv=0x7fffffff7d18) >>>> at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>>> n >>>> s >>>> /ParaView/pqparaviewInitializer.cxx:122 >>>> #51 0x000000000040a7a1 in main (argc=1, argv=0x7fffffff7d18) at >>>> /p/home/joeh/PV/Build_5.3.0_gl2/superbuild/paraview/build/Applicatio >>>> n >>>> s >>>> /ParaView/paraview_main.cxx:117 >>>> >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> Joseph G. Hennessey Ph.D., SAIC >>>> Team SAIC >>>> Army Research Lab >>>> DOD Supercomputing Resource Center >>>> >>>> >>>> -----Original Message----- >>>> From: Utkarsh Ayachit [Caution-Caution-mailto:utkarsh.ayachit at kitware.com < Caution-mailto:utkarsh.ayachit at kitware.com > ] >>>> Sent: Friday, March 10, 2017 11:47 AM >>>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>>> > >>>> Cc: ParaView Developers > >>>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] What is the >>>> minimum nvidia driver level that works with ParaView 5.3.0 >>>> (UNCLASSIFIED) >>>> >>>> Joe, >>>> >>>> Next, can you try setting PV_DEBUG_SKIP_OPENGL_VERSION_CHECK=1 in >>>> the environment and see if it goes further? >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> >>>> CLASSIFICATION: UNCLASSIFIED >>> >>> >>> CLASSIFICATION: UNCLASSIFIED _______________________________________________ Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > Search the list archives at: Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From mzhao at cea-igp.ac.cn Sun Mar 19 04:44:42 2017 From: mzhao at cea-igp.ac.cn (=?gbk?B?1dTD9w==?=) Date: Sun, 19 Mar 2017 16:44:42 +0800 Subject: [Paraview-developers] link error in FortranPoissonSolver of ParaViewCatalystExample Message-ID: <8481c07d2c699dc1b2611349e1cca4f3@cea-igp.ac.cn> Hi everyone, I'm trying to complie "FortranPoissonSolver" in "ParaviewCatalystExample" in Windows 10,the environment is visual studio 2015,intel visual fortran,everything is fine except in the last step, I always get this link error information: error code: LNK2019 unresolved external symbol _main referenced in function "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ) D:\build_example_catalyst_codes\FortranPoissonSolver\MSVCRT.lib(exe_main.obj) does anyone encounter such problem?It is really annoying. By the way,it seems in Linux there is no such problem. Any advice will be appreciated! CheersMing -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Mon Mar 20 04:58:25 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 20 Mar 2017 09:58:25 +0100 Subject: [Paraview-developers] Unload a loaded plugin In-Reply-To: References: Message-ID: Sorry, it is not yet possible to unload a plugin in ParaView. You need to restart ParaView. Mathieu Westphal On Fri, Mar 17, 2017 at 8:50 PM, Maxim Torgonskiy wrote: > Hello, > > I'm currently working on a custom paraview version and now I'm trying > to dynamicallyreplace xml python plugins by their newer versions but I > didn't find any remove / unload function in the interface of plugin > managers (pqPluginManager, vtkSMPluginManager) except > pqPluginManager::hidePlugin which doesn't do what I want. There's only > a function vtkPVPluginLoader::PluginLibraryUnloaded which's called in > the destructor of every plugin via a macro in pqParaViewPlugin.cxx.in > . Can I use it in my case? If not, is there any other solution? > > Thanks, > Maxim > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Mar 20 11:23:09 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 20 Mar 2017 11:23:09 -0400 Subject: [Paraview-developers] link error in FortranPoissonSolver of ParaViewCatalystExample In-Reply-To: <8481c07d2c699dc1b2611349e1cca4f3@cea-igp.ac.cn> References: <8481c07d2c699dc1b2611349e1cca4f3@cea-igp.ac.cn> Message-ID: Hi, ParaView Catalyst has really focused on Linux platforms so we don't test the Catalyst examples with Windows. So far there has not been a project to support this use case either so I do not have a timeline for when this may be fixed. Best, Andy On Sun, Mar 19, 2017 at 4:44 AM, ?? wrote: > Hi everyone, > > I'm trying to complie "FortranPoissonSolver" in "ParaviewCatalystExample" > in Windows 10,the environment is visual studio 2015,intel visual > fortran,everything is fine except in the last step, I always get this link > error information: > > *error code: LNK2019* unresolved external symbol *_main* referenced in > function "*int __cdecl __scrt_common_main_seh(void)*" > (?__scrt_common_main_seh@@YAHXZ) D:\build_example_catalyst_ > codes\FortranPoissonSolver\MSVCRT.lib(exe_main.obj) > does anyone encounter such problem?It is really annoying. > > By the way,it seems in Linux there is no such problem. > > Any advice will be appreciated! > > Cheers > Ming > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 20 13:04:28 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 20 Mar 2017 17:04:28 +0000 Subject: [Paraview-developers] Ogg files Message-ID: <8528d98126b1475d8fb492b5a985f140@ES01AMSNLNT.srn.sandia.gov> We have had the ogg movie writer in ParaView forever. I have never used it or seen it used. Should we delete it? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Mar 20 13:06:40 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 20 Mar 2017 13:06:40 -0400 Subject: [Paraview-developers] Ogg files In-Reply-To: <8528d98126b1475d8fb492b5a985f140@ES01AMSNLNT.srn.sandia.gov> References: <8528d98126b1475d8fb492b5a985f140@ES01AMSNLNT.srn.sandia.gov> Message-ID: I use it all the time on Linux desktop. I don't think we should delete it. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 20, 2017 at 1:04 PM, Scott, W Alan wrote: > We have had the ogg movie writer in ParaView forever. I have never used > it or seen it used. Should we delete it? > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 20 13:09:41 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 20 Mar 2017 17:09:41 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Ogg files In-Reply-To: References: <8528d98126b1475d8fb492b5a985f140@ES01AMSNLNT.srn.sandia.gov> Message-ID: <4134d93ab8ec448796dd0f4261e19bf3@ES01AMSNLNT.srn.sandia.gov> Ah ? a user! Great. I withdraw my question. How do you play it? vlc player? You may want to replicate and write up the bog on the list. ?Paraview save video on high resolution?, from Sunday. Alan From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Monday, March 20, 2017 11:07 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Ogg files I use it all the time on Linux desktop. I don't think we should delete it. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 20, 2017 at 1:04 PM, Scott, W Alan > wrote: We have had the ogg movie writer in ParaView forever. I have never used it or seen it used. Should we delete it? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Mar 20 16:51:13 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 20 Mar 2017 16:51:13 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Ogg files In-Reply-To: <4134d93ab8ec448796dd0f4261e19bf3@ES01AMSNLNT.srn.sandia.gov> References: <8528d98126b1475d8fb492b5a985f140@ES01AMSNLNT.srn.sandia.gov> <4134d93ab8ec448796dd0f4261e19bf3@ES01AMSNLNT.srn.sandia.gov> Message-ID: David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 20, 2017 at 1:09 PM, Scott, W Alan wrote: > Ah ? a user! Great. I withdraw my question. > > > > How do you play it? vlc player? > ubuntu's standard video player seems fine. vlc should do well anywhere. > > > You may want to replicate and write up the bog on the list. ?Paraview > save video on high resolution?, from Sunday. > > if can find time > Alan > > > > *From:* David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Monday, March 20, 2017 11:07 AM > *To:* Scott, W Alan > *Cc:* paraview-developers at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Ogg files > > > > I use it all the time on Linux desktop. I don't think we should delete it. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > > > On Mon, Mar 20, 2017 at 1:04 PM, Scott, W Alan wrote: > > We have had the ogg movie writer in ParaView forever. I have never used > it or seen it used. Should we delete it? > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Mar 21 03:46:48 2017 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 21 Mar 2017 07:46:48 +0000 Subject: [Paraview-developers] failed to compile H5detect.c Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68438352F8@MBX211.d.ethz.ch> I have run into a hurdle compiling 5.3 on a Linux box with gcc version 5.3.0 (cmake 3.4.1) the error is: /dev/shm/jfavre/ParaView/ParaView-v5.3.0/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:87:19: error: unknown type name ?sigjmp_buf? #define H5JMP_BUF sigjmp_buf ^ /dev/shm/jfavre/ParaView/ParaView-v5.3.0/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:163:8: note: in expansion of macro ?H5JMP_BUF? static H5JMP_BUF jbuf_g; the error is caused by using the compilation flag -std=c99. Replacing it with -std=gnu99, then the compilation succeeds. Consequently, I patched the file VTK/ThirdParty/hdf5/vtkhdf5/CMakeLists.txt - set (CMAKE_C_FLAGS "${CMAKE_ANSI_CFLAGS} ${CMAKE_C_FLAGS} -std=c99 -fomit-frame-pointer -finline-functions -fno-common") + set (CMAKE_C_FLAGS "${CMAKE_ANSI_CFLAGS} ${CMAKE_C_FLAGS} -std=gnu99 -fomit-frame-pointer -finline-functions -fno-common") I am not sure if this is applicable to other systems. This posting is for documentation. It may be useful to someone else. ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 21 14:25:28 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 21 Mar 2017 18:25:28 +0000 Subject: [Paraview-developers] FW: ParaView 5.3.0 release In-Reply-To: <1490112747288.38578@sandia.gov> References: <1490112747288.38578@sandia.gov> Message-ID: <89fd090cd773451781b052a400e34751@ES01AMSNLNT.srn.sandia.gov> Congratulations from a user. Good job team. Alan From: Manktelow, Kevin Lee Sent: Tuesday, March 21, 2017 10:12 AM To: Scott, W Alan Subject: Re: ParaView 5.3.0 release Thanks for getting this rolled out to us Alan. I've been using 5.3.0 and once I resolved my white font issue it's been a real pleasure to use. It feels a lot more polished -- even some of the defaults lighting and rendering settings seem a bit "prettier" (I'm sure the color map gurus loathe that). Definitely a lot of noticeable and useful improvements here. Please feel free to pass the message onto the rest of the team. -Kevin ________________________________ From: Scott, W Alan Sent: Monday, March 20, 2017 12:11 PM To: <> Subject: ParaView 5.3.0 release ParaView 5.3.0 has been released by Kitware and is now installed and the default here at Sandia on the SRN and SCN LANs. ParaView is a scientific visualization application installed at Sandia. Standalone installs for, Windows, OS X and Linux are being worked on, and will be available for download within a week at computing.sandia.gov (https://computing.sandia.gov/paraview/getting_paraview). ParaView 5.3.0 is medium level upgrade, with the following enhancements that stand out to me. The CGNS reader now works correctly for single input files. This includes CGNS datasets with missing or incorrect ZoneIterativeData_t. Future work will make the CGNS reader work correctly in parallel. OSPRay, a built in ray tracer, is now available in ParaView from the Properties tab. This feature is a work in progress, and I would say the featureset is alpha quality. Anti-aliasing for lines has been implemented and turned on by default. Settings are Edit/ Settings/ Render View / Use FXAA. This works local and remote server. Enhancements from the 5.2.0 release (that I did not release here at Sandia). Sources/ Ruler has been enhanced, allowing users to measure distances between points or cells. Try turning on Auto Apply, and the ruler will automatically update. Also, hitting the number 1 sets the beginning placement for the ruler, 2 sets the ending point for the ruler. There are also many improvements still to come with this tool. A generic Edit/ Reload Files menu option has been added. This works on all readers. Hidden line removal has been enhanced and is now available. Find this at the bottom of the Properties tab - Hidden Line Removal. Test with Sources/ Wavelet, then render with Wireframe. This fails on large data, remote server, which is why it is turned off by default. Kitware's release notes for 5.2.0 are located here: https://blog.kitware.com/paraview-5-2-0-release-notes/, and the release notes for 5.3.0 are located here: https://blog.kitware.com/paraview-5-3-0-release-notes/, as well as through the ParaView help menu. If you have any questions or issues, please send an e-mail to paraview-help at sandia.gov. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Wed Mar 22 00:36:34 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Wed, 22 Mar 2017 00:36:34 -0400 Subject: [Paraview-developers] failed to compile H5detect.c In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F68438352F8@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F68438352F8@MBX211.d.ethz.ch> Message-ID: Hi Jean, I've encountered this before and while I don't know the exact cause of it, it's somehow related to building out of /dev/shm. I know it doesn't make any sense but I spend a few days on this error when I finally got a successful build by accident when I happend to use a build directory on an actual filesystem. So, as wierd as it sounds, try the build out of an actual disk backed filesystem and it will probably work. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Tue, Mar 21, 2017 at 3:46 AM, Favre Jean wrote: > > I have run into a hurdle compiling 5.3 on a Linux box with gcc version > 5.3.0 (cmake 3.4.1) > > the error is: > > /dev/shm/jfavre/ParaView/ParaView-v5.3.0/VTK/ThirdParty/ > hdf5/vtkhdf5/src/H5detect.c:87:19: error: unknown type name ?sigjmp_buf? > #define H5JMP_BUF sigjmp_buf > ^ > /dev/shm/jfavre/ParaView/ParaView-v5.3.0/VTK/ThirdParty/ > hdf5/vtkhdf5/src/H5detect.c:163:8: note: in expansion of macro ?H5JMP_BUF? > static H5JMP_BUF jbuf_g; > > the error is caused by using the compilation flag -std=c99. Replacing it > with -std=gnu99, then the compilation succeeds. Consequently, I patched the > file VTK/ThirdParty/hdf5/vtkhdf5/CMakeLists.txt > > - set (CMAKE_C_FLAGS "${CMAKE_ANSI_CFLAGS} ${CMAKE_C_FLAGS} -std=c99 > -fomit-frame-pointer -finline-functions -fno-common") > + set (CMAKE_C_FLAGS "${CMAKE_ANSI_CFLAGS} ${CMAKE_C_FLAGS} > -std=gnu99 -fomit-frame-pointer -finline-functions -fno-common") > > I am not sure if this is applicable to other systems. This posting is for > documentation. It may be useful to someone else. > > ----------------- > Jean/CSCS > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Wed Mar 22 04:28:18 2017 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 22 Mar 2017 08:28:18 +0000 Subject: [Paraview-developers] failed to compile H5detect.c In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F68438352F8@MBX211.d.ethz.ch>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68438377BD@MBX211.d.ethz.ch> Chuck, thanks for the tip. I am in a catch-22 situation. If I compile out of a regular filesystem (like my $HOME) cmake fails early with the error /apps/common/cmake/3.7.2/share/cmake-3.7/Modules/TestBigEndian.cmake(41): message(FATAL_ERROR no suitable type found ) Called from: [2] /apps/common/cmake/3.7.2/share/cmake-3.7/Modules/TestBigEndian.cmake [1] /users/jfavre/foo/ParaView-v5.3.0/VTK/CMakeLists.txt CMake Error at /apps/common/cmake/3.7.2/share/cmake-3.7/Modules/TestBigEndian.cmake:41 (message): no suitable type found Call Stack (most recent call first): VTK/CMakeLists.txt:337 (TEST_BIG_ENDIAN) If I compile from /dev/shm, I must patch the compile flags to use -std=gnu99, otherwise compilation of H5detect.c fails. ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From mzhao at cea-igp.ac.cn Wed Mar 22 04:31:44 2017 From: mzhao at cea-igp.ac.cn (=?gbk?B?1dTD9w==?=) Date: Wed, 22 Mar 2017 16:31:44 +0800 Subject: [Paraview-developers] =?gbk?q?/usr/lib64/libGL=2Eso=2E1=A3=BAunde?= =?gbk?q?fined_reference_to_=27=5Fglapi=5Ftls=5FDispatch=27_when_bu?= =?gbk?q?ild_Paraview_5=2E3_with_cmake?= Message-ID: Hi everyone, I got this error when build Paraview 5.3 in Centos with cmake 3.7: /usr/lib64/libGL.so.1?undefined reference to '_glapi_tls_Dispatch' Strangle thing is,when I use ldd,everything seems OK: [zm at centos7 ~]$ ldd /usr/lib64/libGL.so.1 | grep libglapi libglapi.so.0 => /lib64/libglapi.so.0 (0x00007f3aae953000) [zm at centos7 ~]$ ldd /usr/lib64/libglapi.so.0 linux-vdso.so.1 => (0x00007ffd195f3000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8d996a0000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f8d99478000) libc.so.6 => /lib64/libc.so.6 (0x00007f8d990b7000) /lib64/ld-linux-x86-64.so.2 (0x00007f8d99b03000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f8d98e56000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f8d98c51000) [zm at centos7 ~]$ grep -r "_glapi_tls_Dispatch" /usr/lib64 ???????? /usr/lib64/dri/i915_dri.so ???????? /usr/lib64/dri/i965_dri.so ???????? /usr/lib64/dri/kms_swrast_dri.so ???????? /usr/lib64/dri/nouveau_dri.so ???????? /usr/lib64/dri/r300_dri.so ???????? /usr/lib64/dri/r600_dri.so ???????? /usr/lib64/dri/radeonsi_dri.so ???????? /usr/lib64/dri/swrast_dri.so ???????? /usr/lib64/dri/virtio_gpu_dri.so ???????? /usr/lib64/dri/vmwgfx_dri.so ???????? /usr/lib64/libglapi.so.0.0.0 grep: /usr/lib64/dbus-1/dbus-daemon-launch-helper: ???? ???????? /usr/lib64/libGL.so.1.2.0 grep: /usr/lib64/vte-2.91/gnome-pty-helper: ???? this is really strangle,isn't it? Best Ming -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 22 10:34:43 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 22 Mar 2017 10:34:43 -0400 Subject: [Paraview-developers] FW: ParaView 5.3.0 release In-Reply-To: <89fd090cd773451781b052a400e34751@ES01AMSNLNT.srn.sandia.gov> References: <1490112747288.38578@sandia.gov> <89fd090cd773451781b052a400e34751@ES01AMSNLNT.srn.sandia.gov> Message-ID: Thanks for sharing, Alan. Always nice to hear :). On Tue, Mar 21, 2017 at 2:25 PM, Scott, W Alan wrote: > Congratulations from a user. Good job team. > > > > Alan > > > > From: Manktelow, Kevin Lee > Sent: Tuesday, March 21, 2017 10:12 AM > To: Scott, W Alan > Subject: Re: ParaView 5.3.0 release > > > > Thanks for getting this rolled out to us Alan. I've been using 5.3.0 and > once I resolved my white font issue it's been a real pleasure to use. It > feels a lot more polished -- even some of the defaults lighting and > rendering settings seem a bit "prettier" (I'm sure the color map gurus > loathe that). > > > > Definitely a lot of noticeable and useful improvements here. > > > Please feel free to pass the message onto the rest of the team. > > -Kevin > > ________________________________ > > From: Scott, W Alan > Sent: Monday, March 20, 2017 12:11 PM > To: <> > > Subject: ParaView 5.3.0 release > > > > ParaView 5.3.0 has been released by Kitware and is now installed and the > default here at Sandia on the SRN and SCN LANs. ParaView is a scientific > visualization application installed at Sandia. > > > > Standalone installs for, Windows, OS X and Linux are being worked on, and > will be available for download within a week at computing.sandia.gov > (https://computing.sandia.gov/paraview/getting_paraview). > > > > > > ParaView 5.3.0 is medium level upgrade, with the following enhancements that > stand out to me. > > > > The CGNS reader now works correctly for single input files. This includes > CGNS datasets with missing or incorrect ZoneIterativeData_t. Future work > will make the CGNS reader work correctly in parallel. > > > > OSPRay, a built in ray tracer, is now available in ParaView from the > Properties tab. This feature is a work in progress, and I would say the > featureset is alpha quality. > > > > Anti-aliasing for lines has been implemented and turned on by default. > Settings are Edit/ Settings/ Render View / Use FXAA. This works local and > remote server. > > > > > > Enhancements from the 5.2.0 release (that I did not release here at Sandia). > > > > Sources/ Ruler has been enhanced, allowing users to measure distances > between points or cells. Try turning on Auto Apply, and the ruler will > automatically update. Also, hitting the number 1 sets the beginning > placement for the ruler, 2 sets the ending point for the ruler. There are > also many improvements still to come with this tool. > > > > A generic Edit/ Reload Files menu option has been added. This works on all > readers. > > > > Hidden line removal has been enhanced and is now available. Find this at > the bottom of the Properties tab ? Hidden Line Removal. Test with Sources/ > Wavelet, then render with Wireframe. This fails on large data, remote > server, which is why it is turned off by default. > > > > Kitware?s release notes for 5.2.0 are located here: > https://blog.kitware.com/paraview-5-2-0-release-notes/, and the release > notes for 5.3.0 are located here: > https://blog.kitware.com/paraview-5-3-0-release-notes/, as well as through > the ParaView help menu. > > > > If you have any questions or issues, please send an e-mail to > paraview-help at sandia.gov. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From ben.boeckel at kitware.com Wed Mar 22 11:26:58 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 22 Mar 2017 11:26:58 -0400 Subject: [Paraview-developers] [kwrobot] New `Do: reformat` command Message-ID: <20170322152658.GB13165@megas.kitware.com> Hi, The kwrobot can now automatically fix the `clang-format` errors detected for your MRs. Developers can run it on any MR and the submitter of an MR can run it on their own MRs as well. Note that this will push right back to your source branch, so you will need to fetch from your fork to sync up with the reformatted branch. This may be done by using the new command: Do: reformat The topology of your MR is untouched, so merges and the like are preserved. If non-merge commits are found to be empty after a reformat (and not empty before reformatting), they are removed from the history since it is assumed they were "make the formatting checks pass" commits (dropped commits will be mentioned if it happens since it really is just a heuristic). --Ben From cory.quammen at kitware.com Wed Mar 22 11:34:15 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 22 Mar 2017 11:34:15 -0400 Subject: [Paraview-developers] [kwrobot] New `Do: reformat` command In-Reply-To: <20170322152658.GB13165@megas.kitware.com> References: <20170322152658.GB13165@megas.kitware.com> Message-ID: Nice! On Wed, Mar 22, 2017 at 11:26 AM, Ben Boeckel wrote: > Hi, > > The kwrobot can now automatically fix the `clang-format` errors detected > for your MRs. Developers can run it on any MR and the submitter of an MR > can run it on their own MRs as well. Note that this will push right back > to your source branch, so you will need to fetch from your fork to sync > up with the reformatted branch. > > This may be done by using the new command: > > Do: reformat > > The topology of your MR is untouched, so merges and the like are > preserved. If non-merge commits are found to be empty after a reformat > (and not empty before reformatting), they are removed from the history > since it is assumed they were "make the formatting checks pass" commits > (dropped commits will be mentioned if it happens since it really is just > a heuristic). > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers -- Cory Quammen Staff R&D Engineer Kitware, Inc. From michalwozniak at live.ca Wed Mar 22 12:27:06 2017 From: michalwozniak at live.ca (michal wozniak) Date: Wed, 22 Mar 2017 16:27:06 +0000 Subject: [Paraview-developers] superbuild paraview pythonpath windows Message-ID: Hi, I am currently building a custom application based on ParaView. I have one small problem with the PYTHONPATH set by the super build. After using CPack to create the installer, I installed my packaged ParaView on a different windows system. The installed application is missing the path to the site-package, therefore my python shell will display this error "ImportError: No module named ParaView.simple". I used the cmd "import sys" "sys.path" to print all the path set in PYTHONPATH and I am missing this path: "bin\Lib\site-packages". I saw this macro "superbuild_add_project_python" in common-superbuild. When is supposed to be replaced by the install path? Is there another macro that is supposed to set the PYTHONPATH? I am currently building the super build on window 10 using ninja + vs 2015. I have enabled the following super build options: * ENABLE_paraview * ENABLE_python * ENABLE_qt5 * USE_SYSTEM_qt5 thanks Michal -------------- next part -------------- An HTML attachment was scrubbed... URL: From daanvanvugt at gmail.com Wed Mar 22 12:34:28 2017 From: daanvanvugt at gmail.com (Daan van Vugt) Date: Wed, 22 Mar 2017 17:34:28 +0100 Subject: [Paraview-developers] H5py in paraview python Message-ID: Hi, Just a quick question: Would it be possible to include h5py in the ParaView distribution? It would make the development of file readers based on the python programmable filter much easier. Thanks, Daan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 22 13:05:51 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 22 Mar 2017 13:05:51 -0400 Subject: [Paraview-developers] H5py in paraview python In-Reply-To: References: Message-ID: It's indeed a great suggestion -- something I've been thinking of doing, but never got around to it. Ben, how hard would it be? On Wed, Mar 22, 2017 at 12:34 PM, Daan van Vugt wrote: > Hi, > > Just a quick question: Would it be possible to include h5py in the ParaView > distribution? > It would make the development of file readers based on the python > programmable filter much easier. > > Thanks, > Daan > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From cornelis.bockemuehl at gmail.com Thu Mar 23 03:32:06 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Thu, 23 Mar 2017 08:32:06 +0100 Subject: [Paraview-developers] Buildbots migrated to Qt5 In-Reply-To: <20170201195354.GA4822@megas.kitware.com> References: <20170131203811.GA18716@megas.kitware.com> <20170201161641.GC27687@megas.kitware.com> <20170201195354.GA4822@megas.kitware.com> Message-ID: Good morning, I just finished to move my entire ParaView related development to latest versions, i.e. I migrated: - from VS 2010 to 2015 - from Qt 4.8.4 to 5.8 - from ParaView 5.2 (some pre-release) to 5.3 ("official release") After the normal little struggles I managed to get this built - with the exception of 5 targets: - LagrangianParticleTracker - SierraPlotTools - SLACTools - StreamLinesRepresentation - NonOrthogonalSource For all of them the final error comes from MOC and it is: "Undefined interface" Now I don't care so much about these 5 items, but I am developing some own plugins, the latest effort being to have some customized property widget - and it turns out: I am running into the same "Undefined interface" issue! Thanks to your findings already I understand that this is a Qt 5.8 problem - and that there are some fixes around that are supposed to go into Qt 5.8.1 - but this is not out yet, and I also do not see any preliminary fixes. My options are now: - just sit and wait for Qt 5.8.1, hope that it will fix the problem, and continue programming other things in the meantime - no idea about how long this will take! - downgrade to some earlier version of Qt - with the side effect of having to downgrade also the VS version again - tedous and maybe not required! - OR - ideally! - somebody can give me access to some fixed version of MOC (and whatever else may be required) so I can get around this "Undefined interface" stuff. Another option would of course be to find a workaround, i.e. writing a custom property widget without running into this problem, but I already tried this and did not find a solution either... Many thanks for helpful hints! Regards, Cornelis 2017-02-01 20:53 GMT+01:00 Ben Boeckel : > On Wed, Feb 01, 2017 at 11:16:41 -0500, Ben Boeckel wrote: > > This looks to be a 5.8 thing on Windows; 5.7.0 doesn't have this issue. > > I'll try and get to look at this more today. > > Indeed, it's a 5.8 issue. It's patched locally on the machines; trying > to get it upstream now for 5.8.1. > > > Enabling Qt5 required lz4 on this build; I installed the package and > > restarted the failed build I saw; if there are others, let me know. > > All required packages have been installed on `vall`. > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Thu Mar 23 04:15:27 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 23 Mar 2017 09:15:27 +0100 Subject: [Paraview-developers] [kwrobot] New `Do: reformat` command In-Reply-To: References: <20170322152658.GB13165@megas.kitware.com> Message-ID: That's just awesome ! Mathieu Westphal On Wed, Mar 22, 2017 at 4:34 PM, Cory Quammen wrote: > Nice! > > On Wed, Mar 22, 2017 at 11:26 AM, Ben Boeckel > wrote: > > Hi, > > > > The kwrobot can now automatically fix the `clang-format` errors detected > > for your MRs. Developers can run it on any MR and the submitter of an MR > > can run it on their own MRs as well. Note that this will push right back > > to your source branch, so you will need to fetch from your fork to sync > > up with the reformatted branch. > > > > This may be done by using the new command: > > > > Do: reformat > > > > The topology of your MR is untouched, so merges and the like are > > preserved. If non-merge commits are found to be empty after a reformat > > (and not empty before reformatting), they are removed from the history > > since it is assumed they were "make the formatting checks pass" commits > > (dropped commits will be mentioned if it happens since it really is just > > a heuristic). > > > > --Ben > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Mar 23 08:24:49 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 23 Mar 2017 08:24:49 -0400 Subject: [Paraview-developers] Buildbots migrated to Qt5 In-Reply-To: References: <20170131203811.GA18716@megas.kitware.com> <20170201161641.GC27687@megas.kitware.com> <20170201195354.GA4822@megas.kitware.com> Message-ID: <20170323122449.GA27088@megas.kitware.com> On Thu, Mar 23, 2017 at 08:32:06 +0100, Cornelis Bockem?hl wrote: > Thanks to your findings already I understand that this is a Qt 5.8 problem > - and that there are some fixes around that are supposed to go into Qt > 5.8.1 - but this is not out yet, and I also do not see any preliminary > fixes. Sorry, I thought I had linked it in this thread. This is the patch you need: https://codereview.qt-project.org/#/c/184321/ --Ben From mzhao at cea-igp.ac.cn Thu Mar 23 09:20:59 2017 From: mzhao at cea-igp.ac.cn (=?utf-8?B?6LW15piO?=) Date: Thu, 23 Mar 2017 21:20:59 +0800 Subject: [Paraview-developers] link error in FortranPoissonSolver of ParaViewCatalystExample In-Reply-To: References: <8481c07d2c699dc1b2611349e1cca4f3@cea-igp.ac.cn>, Message-ID: Hi Bauer, Thank you very much for your reply.Now follow your instruction,I compiled Paraview 5.3 in CentOS 7.However,when I run the command (for example pvpython) in the bin directory,it reports "segmentation fault(core dumped)",when use dmesg it gives: [zm at centos7 bin]$ dmesg | grep segfault [ 734.025588] pvpython[5381]: segfault at 0 ip 00007f2ff7227e29 sp 00007fff75d182a8 error 4 in libLLVM-3.9.so[7f2ff6e04000+1953000] [ 765.893732] pvserver[5401]: segfault at 0 ip 00007f490a12ae29 sp 00007ffd944dda18 error 4 in libLLVM-3.9.so[7f4909d07000+1953000] [ 1027.562577] pvpython[15124]: segfault at 0 ip 00007f22d4c2ee29 sp 00007ffc89605368 error 4 in libLLVM-3.9.so[7f22d480b000+1953000] [10541.371157] pvpython[17494]: segfault at 0 ip 00007fe7d244bc89 sp 00007ffd67c8b6b0 error 4 in libLLVM-3.9.so[7fe7d2027000+1953000] [16015.006928] pvpython[18631]: segfault at 0 ip 00007ff0ae2d2e29 sp 00007ffefbbb0278 error 4 in libLLVM-3.9.so[7ff0adeaf000+1953000] It seems libLLVM-3.9.so cause this problem,so does that mean:paraview 5.3 is not compatible with LLVM-3.9,if so,which version will be good? Anyone has any ideas?Looking forward for your reply! Best regards Ming --------- Original Message --------- From: "Andy Bauer" To: "??" Cc: "paraview-developers at paraview.org" Subject: Re: [Paraview-developers] link error in FortranPoissonSolver of ParaViewCatalystExample Date: 03/20/2017 23:23:09 (Mon) Hi, ParaView Catalyst has really focused on Linux platforms so we don't test the Catalyst examples with Windows. So far there has not been a project to support this use case either so I do not have a timeline for when this may be fixed. Best, Andy On Sun, Mar 19, 2017 at 4:44 AM, ?? wrote: Hi everyone, I'm trying to complie "FortranPoissonSolver" in "ParaviewCatalystExample" in Windows 10,the environment is visual studio 2015,intel visual fortran,everything is fine except in the last step, I always get this link error information: error code: LNK2019 unresolved external symbol _main referenced in function "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ) D:\build_example_catalyst_codes\FortranPoissonSolver\MSVCRT.lib(exe_main.obj) does anyone encounter such problem?It is really annoying. By the way,it seems in Linux there is no such problem. Any advice will be appreciated! CheersMing _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Mar 23 09:31:32 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 23 Mar 2017 09:31:32 -0400 Subject: [Paraview-developers] link error in FortranPoissonSolver of ParaViewCatalystExample In-Reply-To: References: <8481c07d2c699dc1b2611349e1cca4f3@cea-igp.ac.cn> Message-ID: The ParaView superbuild uses LLVM version 3.8.1. It is at https://gitlab.kitware.com/paraview/paraview-superbuild in case you want to try that. On Thu, Mar 23, 2017 at 9:20 AM, ?? wrote: > Hi Bauer, > Thank you very much for your reply.Now follow your instruction,I compiled > Paraview 5.3 in CentOS 7.However,when I run the command (for example > pvpython) in the bin directory,it reports "segmentation fault(core > dumped)",when use dmesg it gives: > > [zm at centos7 bin]$ dmesg | grep segfault > [ 734.025588] pvpython[5381]: segfault at 0 ip 00007f2ff7227e29 sp > 00007fff75d182a8 error 4 in libLLVM-3.9.so[7f2ff6e04000+1953000] > [ 765.893732] pvserver[5401]: segfault at 0 ip 00007f490a12ae29 sp > 00007ffd944dda18 error 4 in libLLVM-3.9.so[7f4909d07000+1953000] > [ 1027.562577] pvpython[15124]: segfault at 0 ip 00007f22d4c2ee29 sp > 00007ffc89605368 error 4 in libLLVM-3.9.so[7f22d480b000+1953000] > [10541.371157] pvpython[17494]: segfault at 0 ip 00007fe7d244bc89 sp > 00007ffd67c8b6b0 error 4 in libLLVM-3.9.so[7fe7d2027000+1953000] > [16015.006928] pvpython[18631]: segfault at 0 ip 00007ff0ae2d2e29 sp > 00007ffefbbb0278 error 4 in libLLVM-3.9.so[7ff0adeaf000+1953000] > > It seems libLLVM-3.9.so cause this problem,so does that mean:paraview 5.3 > is not compatible with LLVM-3.9,if so,which version will be good? > > Anyone has any ideas?Looking forward for your reply! > > Best regards > Ming > > --------- Original Message --------- > *From:* "Andy Bauer" > *To:* "??" > *Cc:* "paraview-developers at paraview.org" > > *Subject:* Re: [Paraview-developers] link error in FortranPoissonSolver > of ParaViewCatalystExample > *Date:* 03/20/2017 23:23:09 (Mon) > > Hi, > > ParaView Catalyst has really focused on Linux platforms so we don't test > the Catalyst examples with Windows. So far there has not been a project to > support this use case either so I do not have a timeline for when this may > be fixed. > > Best, > Andy > > > On Sun, Mar 19, 2017 at 4:44 AM, ?? wrote: > >> Hi everyone, >> >> I'm trying to complie "FortranPoissonSolver" in "ParaviewCatalystExample" >> in Windows 10,the environment is visual studio 2015,intel visual >> fortran,everything is fine except in the last step, I always get this link >> error information: >> >> *error code: LNK2019* unresolved external symbol *_main* referenced in >> function "*int __cdecl __scrt_common_main_seh(void)*" >> (?__scrt_common_main_seh@@YAHXZ) D:\build_example_catalyst_code >> s\FortranPoissonSolver\MSVCRT.lib(exe_main.obj) >> does anyone encounter such problem?It is really annoying. >> >> By the way,it seems in Linux there is no such problem. >> >> Any advice will be appreciated! >> >> Cheers >> Ming >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 23 10:29:16 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 23 Mar 2017 10:29:16 -0400 Subject: [Paraview-developers] [kwrobot] New `Do: reformat` command In-Reply-To: References: <20170322152658.GB13165@megas.kitware.com> Message-ID: Now we just need "Do: code" and we're all set ;) On Thu, Mar 23, 2017 at 4:15 AM, Mathieu Westphal wrote: > That's just awesome ! > > Mathieu Westphal > > On Wed, Mar 22, 2017 at 4:34 PM, Cory Quammen > wrote: >> >> Nice! >> >> On Wed, Mar 22, 2017 at 11:26 AM, Ben Boeckel >> wrote: >> > Hi, >> > >> > The kwrobot can now automatically fix the `clang-format` errors detected >> > for your MRs. Developers can run it on any MR and the submitter of an MR >> > can run it on their own MRs as well. Note that this will push right back >> > to your source branch, so you will need to fetch from your fork to sync >> > up with the reformatted branch. >> > >> > This may be done by using the new command: >> > >> > Do: reformat >> > >> > The topology of your MR is untouched, so merges and the like are >> > preserved. If non-merge commits are found to be empty after a reformat >> > (and not empty before reformatting), they are removed from the history >> > since it is assumed they were "make the formatting checks pass" commits >> > (dropped commits will be mentioned if it happens since it really is just >> > a heuristic). >> > >> > --Ben >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From joachim.pouderoux at kitware.com Thu Mar 23 16:43:12 2017 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Thu, 23 Mar 2017 16:43:12 -0400 Subject: [Paraview-developers] [kwrobot] New `Do: reformat` command In-Reply-To: References: <20170322152658.GB13165@megas.kitware.com> Message-ID: Agree with Utkarsh. I would also appreciate a Do: fix bugs :D *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2017-03-23 10:29 GMT-04:00 Utkarsh Ayachit : > Now we just need "Do: code" and we're all set ;) > > > > On Thu, Mar 23, 2017 at 4:15 AM, Mathieu Westphal > wrote: > > That's just awesome ! > > > > Mathieu Westphal > > > > On Wed, Mar 22, 2017 at 4:34 PM, Cory Quammen > > wrote: > >> > >> Nice! > >> > >> On Wed, Mar 22, 2017 at 11:26 AM, Ben Boeckel > >> wrote: > >> > Hi, > >> > > >> > The kwrobot can now automatically fix the `clang-format` errors > detected > >> > for your MRs. Developers can run it on any MR and the submitter of an > MR > >> > can run it on their own MRs as well. Note that this will push right > back > >> > to your source branch, so you will need to fetch from your fork to > sync > >> > up with the reformatted branch. > >> > > >> > This may be done by using the new command: > >> > > >> > Do: reformat > >> > > >> > The topology of your MR is untouched, so merges and the like are > >> > preserved. If non-merge commits are found to be empty after a reformat > >> > (and not empty before reformatting), they are removed from the history > >> > since it is assumed they were "make the formatting checks pass" > commits > >> > (dropped commits will be mentioned if it happens since it really is > just > >> > a heuristic). > >> > > >> > --Ben > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Thu Mar 23 17:41:47 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Thu, 23 Mar 2017 22:41:47 +0100 Subject: [Paraview-developers] Buildbots migrated to Qt5 In-Reply-To: <20170323122449.GA27088@megas.kitware.com> References: <20170131203811.GA18716@megas.kitware.com> <20170201161641.GC27687@megas.kitware.com> <20170201195354.GA4822@megas.kitware.com> <20170323122449.GA27088@megas.kitware.com> Message-ID: That's great: Everything compiles now! Thanks a lot! Cornelis 2017-03-23 13:24 GMT+01:00 Ben Boeckel : > On Thu, Mar 23, 2017 at 08:32:06 +0100, Cornelis Bockem?hl wrote: > > Thanks to your findings already I understand that this is a Qt 5.8 > problem > > - and that there are some fixes around that are supposed to go into Qt > > 5.8.1 - but this is not out yet, and I also do not see any preliminary > > fixes. > > Sorry, I thought I had linked it in this thread. This is the patch you > need: > > https://codereview.qt-project.org/#/c/184321/ > > --Ben > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Thu Mar 23 17:49:30 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Thu, 23 Mar 2017 17:49:30 -0400 Subject: [Paraview-developers] vtkSMSourceProxy (vtkSMProxy) comparison Message-ID: Hello, I'm trying to create a widget for interactive point picking on a vtkPolyData surface. I use vtkSMRenderViewProxy::ConvertDisplayToPointOnSurface which originally picks a point on the closest surface. I successfully customized this code such that it works only with one input surfafce (vtkSMSourceProxy) and its representation (vtkSMPVRepresentationProxy). In order to provide the input I need be able to compare two vtkSMSourceProxy (whether or not they point to the same pipeline source) OR be able to extract vtkSMPVRepresentationProxy from vtkSMSourceProxy and vtkSMRenderViewProxy. What is the best way to do that? Thanks, Maxim From felipebordeu at gmail.com Tue Mar 28 05:11:10 2017 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Tue, 28 Mar 2017 11:11:10 +0200 Subject: [Paraview-developers] Negative Volume after Tetrahedralize/Tessellate Message-ID: Hi, I'm having trouble working with clip feature in ParaView ("vtkPVMetaClipDataset"), but I think is a VTK bug. My mesh if 100% tetrahedron mesh, then I clip the mesh, the resulting mesh has tets and wedge. Then I apply a tetrahedralize to convert the resulting mesh back to only tets but the connectivity (numbering) of the element is not correct. If I apply mesh quality I get negative volume for some elements. I have the same "wrong" result with the Tessellate Filter (with zero level of subdivisions). Can anyone confirm this bug. Attached a single wedge to demonstrate the bug. Using Paraview 5.2 in linux (home build) and Windows (binary from web) Thanks to all Felipe -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wedge.vtk Type: application/octet-stream Size: 599 bytes Desc: not available URL: From joachim.pouderoux at kitware.com Tue Mar 28 15:38:12 2017 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 28 Mar 2017 15:38:12 -0400 Subject: [Paraview-developers] Fwd: [vtkusers] Negative Volume after Tetrahedralize/Tessellate In-Reply-To: References: Message-ID: Hi Felipe, See documentation of vtkTetra class: * vtkTetra [...] The tetrahedron is defined by the four points * (0-3); where (0,1,2) is the base of the tetrahedron which, using the * right hand rule, forms a triangle whose normal points in the direction * of the fourth point. Which seems to mean that face formed with points 0, 1 and 2 describes the base face considering points are listed in clockwise order when seen from the exterior of the cell. In this case vtkTetra::ComputeVolume() returns a positive volume. Rule is the same with vtkWedge but it looks like the wedge you provide have point listed in incorrect order (CCW when seen from exterior). If you reverse them, tets are correct. If I am wrong with point ordering, then I guess there is a problem when constructing wedges in the Clip filter. Dou you agree? Best, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2017-03-28 5:11 GMT-04:00 Felipe Bordeu : > Hi, > > > I'm having trouble working with clip feature in ParaView > ("vtkPVMetaClipDataset"), but I think is a VTK bug. My mesh if 100% > tetrahedron mesh, then I clip the mesh, the resulting mesh has tets and > wedge. Then I apply a tetrahedralize to convert the resulting mesh back to > only tets but the connectivity (numbering) of the element is not correct. > If I apply mesh quality I get negative volume for some elements. > I have the same "wrong" result with the Tessellate Filter (with zero level > of subdivisions). > > Can anyone confirm this bug. > > Attached a single wedge to demonstrate the bug. > > Using Paraview 5.2 in linux (home build) and Windows (binary from web) > > Thanks to all > Felipe > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Please keep messages on-topic and check the VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Mar 29 16:57:28 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 29 Mar 2017 20:57:28 +0000 Subject: [Paraview-developers] Superbuild failure with vtkm Message-ID: Hi Y'All, I am seeing an error with the superbuild and vtkm. This is a master pull from a few hours ago (i.e., noon, 3/29/17). 58%] Built target tbb [ 60%] Performing download step (git clone) for 'vtkm' Cloning into 'src'... fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed connect to gitlab.kitware.com:443; Operation now in progress Cloning into 'src'... fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed connect to gitlab.kitware.com:443; Operation now in progress Cloning into 'src'... fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed connect to gitlab.kitware.com:443; Operation now in progress -- Had to git clone more than once: 3 times. CMake Error at tmp/vtkm-gitclone.cmake:40 (message): Failed to clone repository: 'https://gitlab.kitware.com/vtk/vtk-m.git' Help and thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Mar 29 22:11:53 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 29 Mar 2017 22:11:53 -0400 Subject: [Paraview-developers] Superbuild failure with vtkm In-Reply-To: References: Message-ID: Alan, It may have been a temporary network hiccup. Do you mind trying it again? I was able to clone VTK-m just now. - Cory On Wed, Mar 29, 2017 at 4:57 PM, Scott, W Alan wrote: > Hi Y?All, > > I am seeing an error with the superbuild and vtkm. This is a master pull > from a few hours ago (i.e., noon, 3/29/17). > > > > 58%] Built target tbb > > [ 60%] Performing download step (git clone) for 'vtkm' > > Cloning into 'src'... > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed > connect to gitlab.kitware.com:443; Operation now in progress > > Cloning into 'src'... > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed > connect to gitlab.kitware.com:443; Operation now in progress > > Cloning into 'src'... > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed > connect to gitlab.kitware.com:443; Operation now in progress > > -- Had to git clone more than once: > > 3 times. > > CMake Error at tmp/vtkm-gitclone.cmake:40 (message): > > Failed to clone repository: 'https://gitlab.kitware.com/vtk/vtk-m.git' > > > > Help and thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Wed Mar 29 22:20:32 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 30 Mar 2017 02:20:32 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild failure with vtkm In-Reply-To: References: Message-ID: Sounds good. I do have a manual build working both client and server, with CGNS turned on. (obviously pre Utkarsh changes) . Alan > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Wednesday, March 29, 2017 8:12 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Superbuild failure with vtkm > > Alan, > > It may have been a temporary network hiccup. Do you mind trying it again? I > was able to clone VTK-m just now. > > - Cory > > On Wed, Mar 29, 2017 at 4:57 PM, Scott, W Alan > wrote: > > Hi Y?All, > > > > I am seeing an error with the superbuild and vtkm. This is a master > > pull from a few hours ago (i.e., noon, 3/29/17). > > > > > > > > 58%] Built target tbb > > > > [ 60%] Performing download step (git clone) for 'vtkm' > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > -- Had to git clone more than once: > > > > 3 times. > > > > CMake Error at tmp/vtkm-gitclone.cmake:40 (message): > > > > Failed to clone repository: 'https://gitlab.kitware.com/vtk/vtk-m.git' > > > > > > > > Help and thanks, > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From wascott at sandia.gov Wed Mar 29 22:25:11 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 30 Mar 2017 02:25:11 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild failure with vtkm In-Reply-To: References: Message-ID: <1e31ef694ffc4d8d965e04183be3ce1a@ES01AMSNLNT.srn.sandia.gov> Both ParaView and Superbuild were up to date. Heading home, I will beat on it tomorrow. Thanks and have a wonderful night, Alan > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Wednesday, March 29, 2017 8:12 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Superbuild failure with vtkm > > Alan, > > It may have been a temporary network hiccup. Do you mind trying it again? I > was able to clone VTK-m just now. > > - Cory > > On Wed, Mar 29, 2017 at 4:57 PM, Scott, W Alan > wrote: > > Hi Y?All, > > > > I am seeing an error with the superbuild and vtkm. This is a master > > pull from a few hours ago (i.e., noon, 3/29/17). > > > > > > > > 58%] Built target tbb > > > > [ 60%] Performing download step (git clone) for 'vtkm' > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > Cloning into 'src'... > > > > fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': > > Failed connect to gitlab.kitware.com:443; Operation now in progress > > > > -- Had to git clone more than once: > > > > 3 times. > > > > CMake Error at tmp/vtkm-gitclone.cmake:40 (message): > > > > Failed to clone repository: 'https://gitlab.kitware.com/vtk/vtk-m.git' > > > > > > > > Help and thanks, > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. From jfavre at cscs.ch Thu Mar 30 08:08:55 2017 From: jfavre at cscs.ch (Favre Jean) Date: Thu, 30 Mar 2017 12:08:55 +0000 Subject: [Paraview-developers] failed to compile Cosmo Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch> Developers I'd like to compile the CosmoHaloFinder, with parallel support. compilation fails with the error: ThirdParty/CosmoHaloFinder/FOFDistribute.cxx:59:32: fatal error: GenericIOMPIReader.h: No such file or directory I have looked for that file, have browsed the ANL site (http://trac.alcf.anl.gov/projects/genericio) but cannot find it anywhere. ParaView web page [1] lists at least a couple of Halo finder options, but it is not clear to me how to build them. [1] http://www.paraview.org/astro-physics/ ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipebordeu at gmail.com Thu Mar 30 10:07:05 2017 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Thu, 30 Mar 2017 16:07:05 +0200 Subject: [Paraview-developers] [vtkusers] Negative Volume after Tetrahedralize/Tessellate In-Reply-To: References: Message-ID: I can confirm that the problem is in the tetrahedralize and not in the clip. To reproduce the bug. Generate a Wavelet source | Clip the data (the mesh has, hexas, tetras, and wedges, pyramids) the index of the Wedges are correct | | tetrahedralize | |- mesh quality with volume for tetras (negarive volume) | |Extract only one cell ( a wedge ) |tetrahedralize |mesh quality (negative volume for some tetras also you can filter the data from the clip filter by element type and apply tetrahedralize and mesh quality. I'm doing some investigation to try to understand the problem. Felipe 2017-03-28 21:38 GMT+02:00 Joachim Pouderoux : > Hi Felipe, > > See documentation of vtkTetra class: > > * vtkTetra [...] The tetrahedron is defined by the four points > * (0-3); where (0,1,2) is the base of the tetrahedron which, using the > * right hand rule, forms a triangle whose normal points in the direction > * of the fourth point. > > Which seems to mean that face formed with points 0, 1 and 2 describes the > base face considering points are listed > in clockwise order when seen from the exterior of the cell. > In this case vtkTetra::ComputeVolume() returns a positive volume. > > Rule is the same with vtkWedge but it looks like the wedge you provide > have point listed in incorrect order (CCW when seen from exterior). > If you reverse them, tets are correct. > > If I am wrong with point ordering, then I guess there is a problem when > constructing wedges in the Clip filter. > > Dou you agree? > > Best, > > Joachim > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2017-03-28 5:11 GMT-04:00 Felipe Bordeu : > >> Hi, >> >> >> I'm having trouble working with clip feature in ParaView >> ("vtkPVMetaClipDataset"), but I think is a VTK bug. My mesh if 100% >> tetrahedron mesh, then I clip the mesh, the resulting mesh has tets and >> wedge. Then I apply a tetrahedralize to convert the resulting mesh back to >> only tets but the connectivity (numbering) of the element is not correct. >> If I apply mesh quality I get negative volume for some elements. >> I have the same "wrong" result with the Tessellate Filter (with zero >> level of subdivisions). >> >> Can anyone confirm this bug. >> >> Attached a single wedge to demonstrate the bug. >> >> Using Paraview 5.2 in linux (home build) and Windows (binary from web) >> >> Thanks to all >> Felipe >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the VTK FAQ at: >> http://www.vtk.org/Wiki/VTK_FAQ >> >> Search the list archives at: http://markmail.org/search/?q=vtkusers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtkusers >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mzhao at cea-igp.ac.cn Thu Mar 30 23:34:25 2017 From: mzhao at cea-igp.ac.cn (=?gbk?B?1dTD9w==?=) Date: Fri, 31 Mar 2017 11:34:25 +0800 Subject: [Paraview-developers] what is paraview-config? Message-ID: <92517c81d86952fca383ed97be2d1a5a@cea-igp.ac.cn> Hi all, Can anyone told me what is paraview-config used for? Usage: /usr/local/lib/paraview-4.3/paraview-config [--libs [--python] |--include|--list|--python-lib] Thanks! Ming -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Mar 31 10:16:29 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 31 Mar 2017 10:16:29 -0400 Subject: [Paraview-developers] what is paraview-config? In-Reply-To: <92517c81d86952fca383ed97be2d1a5a@cea-igp.ac.cn> References: <92517c81d86952fca383ed97be2d1a5a@cea-igp.ac.cn> Message-ID: <20170331141629.GB13038@megas.kitware.com> On Fri, Mar 31, 2017 at 11:34:25 +0800, ?? wrote: > Can anyone told me what is paraview-config used for? > Usage: /usr/local/lib/paraview-4.3/paraview-config [--libs [--python] |--include|--list|--python-lib] It's meant to be used to figure out what libraries need to be linked to when using ParaView from a non-CMake build system (mainly Makefiles using a compiler which understands `-L` and `-l` flags). --Ben From mzhao at cea-igp.ac.cn Fri Mar 31 11:21:45 2017 From: mzhao at cea-igp.ac.cn (mzhao at cea-igp.ac.cn) Date: Fri, 31 Mar 2017 23:21:45 +0800 Subject: [Paraview-developers] what is paraview-config? References: <92517c81d86952fca383ed97be2d1a5a@cea-igp.ac.cn>, <20170331141629.GB13038@megas.kitware.com> Message-ID: <201703312321450494306@cea-igp.ac.cn> Thank you,ben.So,that means I can complie those catalyst examples without using cmake?Nice. However, the usage is too simple and therefore it is still confusing how to use it. So far there are nearly no detailed instructions on the internet for this command. Anyway,thanks again for your explain. Ming mzhao at cea-igp.ac.cn From: Ben Boeckel Date: 2017-03-31 22:16 To: ?? CC: paraview-developers Subject: Re: [Paraview-developers] what is paraview-config? On Fri, Mar 31, 2017 at 11:34:25 +0800, ?? wrote: > Can anyone told me what is paraview-config used for? > Usage: /usr/local/lib/paraview-4.3/paraview-config [--libs [--python] |--include|--list|--python-lib] It's meant to be used to figure out what libraries need to be linked to when using ParaView from a non-CMake build system (mainly Makefiles using a compiler which understands `-L` and `-l` flags). --Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: