From archaerolog at mail.ru Wed Mar 1 03:23:11 2017 From: archaerolog at mail.ru (Gena Bug) Date: Wed, 1 Mar 2017 11:23:11 +0300 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <35ae3bd7af38410f9d614c71971478ab@ES01AMSNLNT.srn.sandia.gov> References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> <35ae3bd7af38410f9d614c71971478ab@ES01AMSNLNT.srn.sandia.gov> Message-ID: <3a4ee2f8-48f7-9ed7-d24d-82cb9ef42f22@mail.ru> Scott, Is fix available in the last nightly build? On 02/28/17 21:41, Scott, W Alan wrote: > Gena, > I just tried saving animations, Linux, local server, using master from yesterday. This includes a fix for https://gitlab.kitware.com/paraview/paraview/issues/17222 that is not in RC2. I was able to successfully create an .avi file with can.exo in one view and plot over line (line chart view) in a second view. If master is still showing save animation bugs, please let Kitware know. > > Thanks, > > Alan > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit > Sent: Tuesday, February 28, 2017 7:57 AM > To: Gena Bug ; Mathieu Westphal > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download > > Mathieu, > > Do you want to take this one on? I suspect the patch needs some more tweaking. > > Utkarsh > > On Tue, Feb 28, 2017 at 7:53 AM, Gena Bug > wrote: > Hi, Utkarsh > > I've tried your patch and now it's possible to set real numbers for axis range (Line Chart View). Also, Set Range dialog is now working (both Rescale buttons are work). However, in Calculator filter dot and comma are treated differently for real numbers in scientific notation: exponent is ignored when using dot. > > Also, I noticed another issue -- saving animation with two views (one, for example, with 2D/3D distribution and one with 1D) is not working anymore! In final movie I see two views but both with the same distribution. > > > On 26.02.2017 20:07, Utkarsh Ayachit wrote: > Gena, > > Can you please try if the attached patch fixes the issue? > > Thanks > Utkarsh > > On Fri, Feb 24, 2017 at 5:27 AM, Gena Bug > wrote: > Hi, Utkarsh > > I've just tried RC2 and saw that plots looks much better, thanks! > > I also noticed another issues: > dot and comma: https://gitlab.kitware.com/paraview/paraview/issues/17225 > rescale: https://gitlab.kitware.com/paraview/paraview/issues/17226 > > However, they both concern my regional settings (ru). After switching to C > they are gone. > > > Debian testing amd64, kf5, plasma5 > > > On 20.02.2017 23:48, Utkarsh Ayachit wrote: > > Gena, > > I can certainly reproduce this issue. Let me see what's going on. I've > reported the issue here: > https://gitlab.kitware.com/paraview/paraview/issues/17202 > > On Sat, Feb 18, 2017 at 10:02 AM, Gena Bug via ParaView > > wrote: > > Hi, > > I noticed a difference in the plot rendering (Line Chart View) -- in the > 5.3RC1 lines aren't smooth as it were in 5.2. > > Another difference is that in 5.3RC1 you can't set real numbers in the > axis > custom range fields using . (dot), only with , (comma). > > Debian testing amd64, nvidia, fxaa disabled. > > > On 13.02.2017 19:49, Cory Quammen wrote: > > > Folks, > > Binaries and source code zip files and tar balls for ParaView 5.3.0 > Release Candidate 1 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. > > Sincerely, > Cory > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > From wascott at sandia.gov Wed Mar 1 12:25:28 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 1 Mar 2017 17:25:28 +0000 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <3a4ee2f8-48f7-9ed7-d24d-82cb9ef42f22@mail.ru> References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> <35ae3bd7af38410f9d614c71971478ab@ES01AMSNLNT.srn.sandia.gov> <3a4ee2f8-48f7-9ed7-d24d-82cb9ef42f22@mail.ru> Message-ID: Yes. Alan > -----Original Message----- > From: Gena Bug [mailto:archaerolog at mail.ru] > Sent: Wednesday, March 1, 2017 1:23 AM > To: Scott, W Alan ; Utkarsh Ayachit > ; Mathieu Westphal > > Cc: ParaView > Subject: Re: [EXTERNAL] Re: [Paraview] ParaView 5.3.0 Release Candidate 1 > binaries are available for download > > Scott, > > Is fix available in the last nightly build? > > On 02/28/17 21:41, Scott, W Alan wrote: > > Gena, > > I just tried saving animations, Linux, local server, using master from > yesterday. This includes a fix for > https://gitlab.kitware.com/paraview/paraview/issues/17222 that is not in > RC2. I was able to successfully create an .avi file with can.exo in one view and > plot over line (line chart view) in a second view. If master is still showing save > animation bugs, please let Kitware know. > > > > Thanks, > > > > Alan > > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > > Utkarsh Ayachit > > Sent: Tuesday, February 28, 2017 7:57 AM > > To: Gena Bug ; Mathieu Westphal > > > > Cc: ParaView > > Subject: [EXTERNAL] Re: [Paraview] ParaView 5.3.0 Release Candidate 1 > > binaries are available for download > > > > Mathieu, > > > > Do you want to take this one on? I suspect the patch needs some more > tweaking. > > > > Utkarsh > > > > On Tue, Feb 28, 2017 at 7:53 AM, Gena Bug > > wrote: > > Hi, Utkarsh > > > > I've tried your patch and now it's possible to set real numbers for axis range > (Line Chart View). Also, Set Range dialog is now working (both Rescale > buttons are work). However, in Calculator filter dot and comma are treated > differently for real numbers in scientific notation: exponent is ignored when > using dot. > > > > Also, I noticed another issue -- saving animation with two views (one, for > example, with 2D/3D distribution and one with 1D) is not working anymore! > In final movie I see two views but both with the same distribution. > > > > > > On 26.02.2017 20:07, Utkarsh Ayachit wrote: > > Gena, > > > > Can you please try if the attached patch fixes the issue? > > > > Thanks > > Utkarsh > > > > On Fri, Feb 24, 2017 at 5:27 AM, Gena Bug > > wrote: > > Hi, Utkarsh > > > > I've just tried RC2 and saw that plots looks much better, thanks! > > > > I also noticed another issues: > > dot and comma: > > https://gitlab.kitware.com/paraview/paraview/issues/17225 > > rescale: https://gitlab.kitware.com/paraview/paraview/issues/17226 > > > > However, they both concern my regional settings (ru). After switching > > to C they are gone. > > > > > > Debian testing amd64, kf5, plasma5 > > > > > > On 20.02.2017 23:48, Utkarsh Ayachit wrote: > > > > Gena, > > > > I can certainly reproduce this issue. Let me see what's going on. I've > > reported the issue here: > > https://gitlab.kitware.com/paraview/paraview/issues/17202 > > > > On Sat, Feb 18, 2017 at 10:02 AM, Gena Bug via ParaView > > > wrote: > > > > Hi, > > > > I noticed a difference in the plot rendering (Line Chart View) -- in > > the > > 5.3RC1 lines aren't smooth as it were in 5.2. > > > > Another difference is that in 5.3RC1 you can't set real numbers in the > > axis custom range fields using . (dot), only with , (comma). > > > > Debian testing amd64, nvidia, fxaa disabled. > > > > > > On 13.02.2017 19:49, Cory Quammen wrote: > > > > > > Folks, > > > > Binaries and source code zip files and tar balls for ParaView 5.3.0 > > Release Candidate 1 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. > > > > Sincerely, > > Cory > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > From kschau at gatech.edu Wed Mar 1 12:35:38 2017 From: kschau at gatech.edu (Schau, Kyle A) Date: Wed, 1 Mar 2017 17:35:38 +0000 Subject: [Paraview] Maintain triangulation of slive from vtk to numpy Message-ID: Hello All Does anyone know if the capability exists to extract slice data through the python interface of paraview that contains the triangulation data of the slice? This would allow one to pull flattened VTK data in the form of numpy arrays, but still plot non-convex slice geometries easily with mayplotlib.tricont() Thanks for your help. Kyle A. Schau Graduate Research Assistant Computational Combustion Lab Georgia Institute of Technology Atlanta, GA (269)-986-4579 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fontana.mauro at gmail.com Wed Mar 1 15:38:46 2017 From: fontana.mauro at gmail.com (Mauro Fontana) Date: Wed, 01 Mar 2017 20:38:46 +0000 Subject: [Paraview] pvpython pass string to Script (Programmable Source) Message-ID: Hello Sorry to bother, but I can't seem to find a way (in the mailing list or the documentation) to pass a string as some kind of argument to Programmable Source (using pvpython interpreter). The python "program" needs to load a custom binary format using numpy.fromfile. What I've thought is to write a wrapper function. The function should receive a string as argument and then instantiate a programmable filter and execute myscript.replace(random_var_name, myfilename) MyProgrammableSource.Script = myscript return MyProgrammableSource Where random_var_name is the argument of my numpy.fromfile call. But that doesn't seem very "pythonic". Is there a way to pass a string to the Script without the .replace hack? Sorry if this is documented, I couldn't find it. Cheers, Mauro -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Wed Mar 1 16:03:27 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Wed, 1 Mar 2017 16:03:27 -0500 Subject: [Paraview] CSV to PVTU Message-ID: Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Wed Mar 1 16:15:13 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 1 Mar 2017 21:15:13 +0000 Subject: [Paraview] CSV to PVTU Message-ID: You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Wed Mar 1 16:17:39 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 1 Mar 2017 21:17:39 +0000 Subject: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) Message-ID: CLASSIFICATION: UNCLASSIFIED Hello, >> What I want to do - load this huge file in a CAVE like environment, and use >> 8 parallel processors. if you don't mind, can you elaborate a little on the process you are using to do that (running in the CAVE like environment)? thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth Sent: Wednesday, March 01, 2017 4:15 PM To: Faiz Abidi ; ParaView Subject: [Non-DoD Source] Re: [Paraview] CSV to PVTU 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. ________________________________ You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [Caution-mailto:paraview-bounces at paraview.org]On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | Caution-www.faizabidi.com < Caution-http://www.faizabidi.com > | +1-540-998-6636 CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From kmorel at sandia.gov Wed Mar 1 16:29:55 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 1 Mar 2017 21:29:55 +0000 Subject: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) Message-ID: <16b9707f36d845269fd231ff6d50e2c3@ES08AMSNLNT.srn.sandia.gov> My description just involves using ParaView to convert a CSV file to a PVTU file using its GUI. I don't know what if any idiosyncrasies are involved if using a CAVE. I've never used one with ParaView. I'll let someone else answer that part. -Ken -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Su, Simon M CIV USARMY RDECOM ARL (US) Sent: Wednesday, March 1, 2017 2:18 PM To: Faiz Abidi ; ParaView Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED Hello, >> What I want to do - load this huge file in a CAVE like environment, >> and use >> 8 parallel processors. if you don't mind, can you elaborate a little on the process you are using to do that (running in the CAVE like environment)? thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth Sent: Wednesday, March 01, 2017 4:15 PM To: Faiz Abidi ; ParaView Subject: [Non-DoD Source] Re: [Paraview] CSV to PVTU 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. ________________________________ You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [Caution-mailto:paraview-bounces at paraview.org]On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | Caution-www.faizabidi.com < Caution-http://www.faizabidi.com > | +1-540-998-6636 CLASSIFICATION: UNCLASSIFIED From simon.m.su.civ at mail.mil Wed Mar 1 16:35:45 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 1 Mar 2017 21:35:45 +0000 Subject: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) In-Reply-To: <16b9707f36d845269fd231ff6d50e2c3@ES08AMSNLNT.srn.sandia.gov> References: <16b9707f36d845269fd231ff6d50e2c3@ES08AMSNLNT.srn.sandia.gov> Message-ID: CLASSIFICATION: UNCLASSIFIED Hi Ken, I have seen Bill Sherman ran it at the CAVE at IUPUI, I am just curious to see if VT has a different way of running PV on a CAVE like display. We run PV on zSpace here. thanks -simon -----Original Message----- From: Moreland, Kenneth [mailto:kmorel at sandia.gov] Sent: Wednesday, March 01, 2017 4:30 PM To: Su, Simon M CIV USARMY RDECOM ARL (US) ; Faiz Abidi ; ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) My description just involves using ParaView to convert a CSV file to a PVTU file using its GUI. I don't know what if any idiosyncrasies are involved if using a CAVE. I've never used one with ParaView. I'll let someone else answer that part. -Ken -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Su, Simon M CIV USARMY RDECOM ARL (US) Sent: Wednesday, March 1, 2017 2:18 PM To: Faiz Abidi ; ParaView Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] Re: CSV to PVTU (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED Hello, >> What I want to do - load this huge file in a CAVE like environment, >> and use >> 8 parallel processors. if you don't mind, can you elaborate a little on the process you are using to do that (running in the CAVE like environment)? thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth Sent: Wednesday, March 01, 2017 4:15 PM To: Faiz Abidi ; ParaView Subject: [Non-DoD Source] Re: [Paraview] CSV to PVTU 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. ________________________________ You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [Caution-mailto:paraview-bounces at paraview.org]On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | Caution-www.faizabidi.com < Caution-http://www.faizabidi.com > | +1-540-998-6636 CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From ahasan94 at gmail.com Thu Mar 2 00:00:38 2017 From: ahasan94 at gmail.com (Mahmud Hasan) Date: Wed, 1 Mar 2017 23:00:38 -0600 Subject: [Paraview] Paraveiw.exe has stopped working Message-ID: Dear Sir/Madam, Good day. I have downloaded Paraview, however it is not opening. Every time it is giving error message "paraveiw.exe has stopped working". I am attaching the screenshot for your information. Would you please let me know what to do. [image: Inline image 1] Thank you. Have a nice day. Regards-- Hasan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From archaerolog at mail.ru Thu Mar 2 04:34:14 2017 From: archaerolog at mail.ru (Gena Bug) Date: Thu, 2 Mar 2017 12:34:14 +0300 Subject: [Paraview] [EXTERNAL] Re: ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> <35ae3bd7af38410f9d614c71971478ab@ES01AMSNLNT.srn.sandia.gov> <3a4ee2f8-48f7-9ed7-d24d-82cb9ef42f22@mail.ru> Message-ID: <280090b4-3e30-1d28-21fd-0690b62a8217@mail.ru> I tried 37-ge566e81 and with it saving animations (and screenshots of LineChartView) works. Thanks! On 03/01/17 20:25, Scott, W Alan wrote: > Yes. > > Alan > >> -----Original Message----- >> From: Gena Bug [mailto:archaerolog at mail.ru] >> Sent: Wednesday, March 1, 2017 1:23 AM >> To: Scott, W Alan ; Utkarsh Ayachit >> ; Mathieu Westphal >> >> Cc: ParaView >> Subject: Re: [EXTERNAL] Re: [Paraview] ParaView 5.3.0 Release Candidate 1 >> binaries are available for download >> >> Scott, >> >> Is fix available in the last nightly build? >> >> On 02/28/17 21:41, Scott, W Alan wrote: >>> Gena, >>> I just tried saving animations, Linux, local server, using master from >> yesterday. This includes a fix for >> https://gitlab.kitware.com/paraview/paraview/issues/17222 that is not in >> RC2. I was able to successfully create an .avi file with can.exo in one view and >> plot over line (line chart view) in a second view. If master is still showing save >> animation bugs, please let Kitware know. >>> >>> Thanks, >>> >>> Alan >>> >>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of >>> Utkarsh Ayachit >>> Sent: Tuesday, February 28, 2017 7:57 AM >>> To: Gena Bug ; Mathieu Westphal >>> >>> Cc: ParaView >>> Subject: [EXTERNAL] Re: [Paraview] ParaView 5.3.0 Release Candidate 1 >>> binaries are available for download >>> >>> Mathieu, >>> >>> Do you want to take this one on? I suspect the patch needs some more >> tweaking. >>> >>> Utkarsh >>> >>> On Tue, Feb 28, 2017 at 7:53 AM, Gena Bug >> > wrote: >>> Hi, Utkarsh >>> >>> I've tried your patch and now it's possible to set real numbers for axis range >> (Line Chart View). Also, Set Range dialog is now working (both Rescale >> buttons are work). However, in Calculator filter dot and comma are treated >> differently for real numbers in scientific notation: exponent is ignored when >> using dot. >>> >>> Also, I noticed another issue -- saving animation with two views (one, for >> example, with 2D/3D distribution and one with 1D) is not working anymore! >> In final movie I see two views but both with the same distribution. >>> >>> >>> On 26.02.2017 20:07, Utkarsh Ayachit wrote: >>> Gena, >>> >>> Can you please try if the attached patch fixes the issue? >>> >>> Thanks >>> Utkarsh >>> >>> On Fri, Feb 24, 2017 at 5:27 AM, Gena Bug >> > wrote: >>> Hi, Utkarsh >>> >>> I've just tried RC2 and saw that plots looks much better, thanks! >>> >>> I also noticed another issues: >>> dot and comma: >>> https://gitlab.kitware.com/paraview/paraview/issues/17225 >>> rescale: https://gitlab.kitware.com/paraview/paraview/issues/17226 >>> >>> However, they both concern my regional settings (ru). After switching >>> to C they are gone. >>> >>> >>> Debian testing amd64, kf5, plasma5 >>> >>> >>> On 20.02.2017 23:48, Utkarsh Ayachit wrote: >>> >>> Gena, >>> >>> I can certainly reproduce this issue. Let me see what's going on. I've >>> reported the issue here: >>> https://gitlab.kitware.com/paraview/paraview/issues/17202 >>> >>> On Sat, Feb 18, 2017 at 10:02 AM, Gena Bug via ParaView >>> > wrote: >>> >>> Hi, >>> >>> I noticed a difference in the plot rendering (Line Chart View) -- in >>> the >>> 5.3RC1 lines aren't smooth as it were in 5.2. >>> >>> Another difference is that in 5.3RC1 you can't set real numbers in the >>> axis custom range fields using . (dot), only with , (comma). >>> >>> Debian testing amd64, nvidia, fxaa disabled. >>> >>> >>> On 13.02.2017 19:49, Cory Quammen wrote: >>> >>> >>> Folks, >>> >>> Binaries and source code zip files and tar balls for ParaView 5.3.0 >>> Release Candidate 1 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. >>> >>> Sincerely, >>> Cory >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> From utkarsh.ayachit at kitware.com Thu Mar 2 08:06:51 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Mar 2017 08:06:51 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: Can you share details about your system? What's the GPU? Are the drivers up-to-date? Utkarsh On Thu, Mar 2, 2017 at 12:00 AM, Mahmud Hasan wrote: > Dear Sir/Madam, > Good day. I have downloaded Paraview, however it is not opening. Every > time it is giving error message "paraveiw.exe has stopped working". I am > attaching the screenshot for your information. Would you please let me know > what to do. > > > > > [image: Inline image 1] > > > > > > Thank you. Have a nice day. > > Regards-- > Hasan > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 2 08:07:28 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Mar 2017 08:07:28 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: Also, what version of ParaView are you using? On Thu, Mar 2, 2017 at 8:06 AM, Utkarsh Ayachit wrote: > Can you share details about your system? What's the GPU? Are the drivers > up-to-date? > > Utkarsh > > On Thu, Mar 2, 2017 at 12:00 AM, Mahmud Hasan wrote: > >> Dear Sir/Madam, >> Good day. I have downloaded Paraview, however it is not opening. >> Every time it is giving error message "paraveiw.exe has stopped working". I >> am attaching the screenshot for your information. Would you please let me >> know what to do. >> >> >> >> >> [image: Inline image 1] >> >> >> >> >> >> Thank you. Have a nice day. >> >> Regards-- >> Hasan >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From ahasan94 at gmail.com Thu Mar 2 08:15:32 2017 From: ahasan94 at gmail.com (Mahmud Hasan) Date: Thu, 2 Mar 2017 07:15:32 -0600 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: Utkarsh, Thank you for your email and contact. I am trying to download two versions (version 5.3.0-R2 which is available in the Paraview website as well as version 5.1.2 from BlueCFD-Core), however none is opening. I am sending screen shot of my computer configurations below. Please let me know if you have any more question. [image: Inline image 1] Thank you. Have a nice day. Regards-- Hasan On Thu, Mar 2, 2017 at 7:07 AM, Utkarsh Ayachit wrote: > Also, what version of ParaView are you using? > > On Thu, Mar 2, 2017 at 8:06 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Can you share details about your system? What's the GPU? Are the drivers >> up-to-date? >> >> Utkarsh >> >> On Thu, Mar 2, 2017 at 12:00 AM, Mahmud Hasan wrote: >> >>> Dear Sir/Madam, >>> Good day. I have downloaded Paraview, however it is not opening. >>> Every time it is giving error message "paraveiw.exe has stopped working". I >>> am attaching the screenshot for your information. Would you please let me >>> know what to do. >>> >>> >>> >>> >>> [image: Inline image 1] >>> >>> >>> >>> >>> >>> Thank you. Have a nice day. >>> >>> Regards-- >>> Hasan >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67283 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 2 09:45:52 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Mar 2017 09:45:52 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: Any way you can figure out your GPU & drivers/version etc? On Thu, Mar 2, 2017 at 8:15 AM, Mahmud Hasan wrote: > Utkarsh, > Thank you for your email and contact. I am trying to download two > versions (version 5.3.0-R2 which is available in the Paraview website as > well as version 5.1.2 from BlueCFD-Core), however none is opening. I am > sending screen shot of my computer configurations below. Please let me know > if you have any more question. > > > > > [image: Inline image 1] > > > > Thank you. Have a nice day. > > Regards-- > Hasan > > > > > > On Thu, Mar 2, 2017 at 7:07 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Also, what version of ParaView are you using? >> >> On Thu, Mar 2, 2017 at 8:06 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Can you share details about your system? What's the GPU? Are the drivers >>> up-to-date? >>> >>> Utkarsh >>> >>> On Thu, Mar 2, 2017 at 12:00 AM, Mahmud Hasan >>> wrote: >>> >>>> Dear Sir/Madam, >>>> Good day. I have downloaded Paraview, however it is not opening. >>>> Every time it is giving error message "paraveiw.exe has stopped working". I >>>> am attaching the screenshot for your information. Would you please let me >>>> know what to do. >>>> >>>> >>>> >>>> >>>> [image: Inline image 1] >>>> >>>> >>>> >>>> >>>> >>>> Thank you. Have a nice day. >>>> >>>> Regards-- >>>> Hasan >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67283 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From dave.demarle at kitware.com Thu Mar 2 11:05:38 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 2 Mar 2017 11:05:38 -0500 Subject: [Paraview] pvpython pass string to Script (Programmable Source) In-Reply-To: References: Message-ID: Use the hidden property called Parameters on the Python Filter/Source to pass in information. >>> prosrc = ProgrammableSource() >>> prosrc.Script = (""" ... try: ... instring ... except NameError: ... instring = "GOODBYE" ... print instring ... """) >>> prop = prosrc.GetProperty("Parameters") >>> prop.SetElement(0, "instring") 1 >>> prop.SetElement(1, "'HELLO'") 1 >>> prosrc.UpdateProperty("Parameters") True >>> prosrc.UpdatePipeline() HELLO David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 1, 2017 at 3:38 PM, Mauro Fontana wrote: > Hello > > Sorry to bother, but I can't seem to find a way (in the mailing list or > the documentation) to pass a string as some kind of argument to > Programmable Source (using pvpython interpreter). The python "program" > needs to load a custom binary format using numpy.fromfile. > > What I've thought is to write a wrapper function. The function should > receive a string as argument and then instantiate a programmable filter and > execute > myscript.replace(random_var_name, myfilename) > MyProgrammableSource.Script = myscript > return MyProgrammableSource > > Where random_var_name is the argument of my numpy.fromfile call. But that > doesn't seem very "pythonic". Is there a way to pass a string to the Script > without the .replace hack? > > Sorry if this is documented, I couldn't find it. > > Cheers, > Mauro > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fontana.mauro at gmail.com Thu Mar 2 11:25:41 2017 From: fontana.mauro at gmail.com (Mauro Fontana) Date: Thu, 02 Mar 2017 16:25:41 +0000 Subject: [Paraview] pvpython pass string to Script (Programmable Source) In-Reply-To: References: Message-ID: Now that sounds (reads) much better and cleaner. Thanks for your time and your response David. Cheers On Thu, Mar 2, 2017 at 1:06 PM David E DeMarle wrote: > Use the hidden property called Parameters on the Python Filter/Source to > pass in information. > > >>> prosrc = ProgrammableSource() > > >>> prosrc.Script = (""" > > ... try: > > ... instring > > ... except NameError: > > ... instring = "GOODBYE" > > ... print instring > > ... """) > > >>> prop = prosrc.GetProperty("Parameters") > > >>> prop.SetElement(0, "instring") > > 1 > > >>> prop.SetElement(1, "'HELLO'") > > 1 > > >>> prosrc.UpdateProperty("Parameters") > > True > > >>> prosrc.UpdatePipeline() > > HELLO > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Wed, Mar 1, 2017 at 3:38 PM, Mauro Fontana > wrote: > > Hello > > Sorry to bother, but I can't seem to find a way (in the mailing list or > the documentation) to pass a string as some kind of argument to > Programmable Source (using pvpython interpreter). The python "program" > needs to load a custom binary format using numpy.fromfile. > > What I've thought is to write a wrapper function. The function should > receive a string as argument and then instantiate a programmable filter and > execute > myscript.replace(random_var_name, myfilename) > MyProgrammableSource.Script = myscript > return MyProgrammableSource > > Where random_var_name is the argument of my numpy.fromfile call. But that > doesn't seem very "pythonic". Is there a way to pass a string to the Script > without the .replace hack? > > Sorry if this is documented, I couldn't find it. > > Cheers, > Mauro > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Thu Mar 2 15:38:25 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Thu, 2 Mar 2017 15:38:25 -0500 Subject: [Paraview] CSV to PVTU In-Reply-To: References: Message-ID: Hi Moreland, Thanks for your reply. I thought same except maybe not use the GUI since my data is big and takes forever to load up in Paraview. Quick question/observation - using the GUI and 8 processes, and applying the Tables to Points filter + D3 and then trying to save files doesn't create 8 vtu files and 1 pvtu file as expected. Instead, what happens is that I get only 1 pvtu file along with 1 vtu file instead. Clearly something wrong. This was done using v5.2.0. I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 vtu files and 1 pvtu file as expected. Do you think this is a bug with 5.2.0? Or do I need to do something different with 5.2.0? Any pointers appreciated! On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth wrote: > You can use ParaView itself to read in the csv file, convert it to an > unstructured grid (Table to Points filter), redistributed on your 8 > parallel processors (D3 filter) and then write out a pvtu file. > > > > Offhand I cannot think of an easier way. > > > > -Ken > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Faiz > Abidi > *Sent:* Wednesday, March 1, 2017 2:03 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] CSV to PVTU > > > > Hi again community! > > > > Looking for suggestions - what would be a decently fast way to convert a > huge CSV file into PVTU files? > > > > What I want to do - load this huge file in a CAVE like environment, and > use 8 parallel processors. > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Mar 2 15:59:16 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 2 Mar 2017 20:59:16 +0000 Subject: [Paraview] [EXTERNAL] Re: CSV to PVTU In-Reply-To: References: Message-ID: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> Faiz, I was able to replicate your problem. It looks like it is not an issue with D3 but a change with how Table to Points creates data (or perhaps how data are written). It looks like Table to Points is creating one ?cell? with a lot of points. This saves a little memory but ends up preventing D3 from dividing the points up. The best solution is to add a ?2D Glyph? filter after the Table to Points but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the D3 filter to the output of the 2D Glyph filter. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Thursday, March 2, 2017 1:38 PM To: Moreland, Kenneth Cc: ParaView ; Rajamohan, Srijith ; Nicholas Polys ; Ayat Mohammed Subject: [EXTERNAL] Re: [Paraview] CSV to PVTU Hi Moreland, Thanks for your reply. I thought same except maybe not use the GUI since my data is big and takes forever to load up in Paraview. Quick question/observation - using the GUI and 8 processes, and applying the Tables to Points filter + D3 and then trying to save files doesn't create 8 vtu files and 1 pvtu file as expected. Instead, what happens is that I get only 1 pvtu file along with 1 vtu file instead. Clearly something wrong. This was done using v5.2.0. I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 vtu files and 1 pvtu file as expected. Do you think this is a bug with 5.2.0? Or do I need to do something different with 5.2.0? Any pointers appreciated! On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView > Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Thu Mar 2 16:44:02 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Thu, 2 Mar 2017 16:44:02 -0500 Subject: [Paraview] [EXTERNAL] Re: CSV to PVTU In-Reply-To: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> References: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> Message-ID: Ohk, that makes more sense. I could get it to work as well but also had to check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. Thanks Moreland! On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth wrote: > Faiz, > > > > I was able to replicate your problem. It looks like it is not an issue > with D3 but a change with how Table to Points creates data (or perhaps how > data are written). It looks like Table to Points is creating one ?cell? > with a lot of points. This saves a little memory but ends up preventing D3 > from dividing the points up. > > > > The best solution is to add a ?2D Glyph? filter after the Table to Points > but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the > D3 filter to the output of the 2D Glyph filter. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Thursday, March 2, 2017 1:38 PM > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Hi Moreland, > > > > Thanks for your reply. > > > > I thought same except maybe not use the GUI since my data is big and takes > forever to load up in Paraview. > > > > Quick question/observation - using the GUI and 8 processes, and applying > the Tables to Points filter + D3 and then trying to save files doesn't > create 8 vtu files and 1 pvtu file as expected. Instead, what happens is > that I get only 1 pvtu file along with 1 vtu file instead. Clearly > something wrong. This was done using v5.2.0. > > > > I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 > vtu files and 1 pvtu file as expected. > > > > Do you think this is a bug with 5.2.0? Or do I need to do something > different with 5.2.0? Any pointers appreciated! > > > > On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: > > You can use ParaView itself to read in the csv file, convert it to an > unstructured grid (Table to Points filter), redistributed on your 8 > parallel processors (D3 filter) and then write out a pvtu file. > > > > Offhand I cannot think of an easier way. > > > > -Ken > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Faiz > Abidi > *Sent:* Wednesday, March 1, 2017 2:03 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] CSV to PVTU > > > > Hi again community! > > > > Looking for suggestions - what would be a decently fast way to convert a > huge CSV file into PVTU files? > > > > What I want to do - load this huge file in a CAVE like environment, and > use 8 parallel processors. > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Mar 2 18:42:27 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 2 Mar 2017 23:42:27 +0000 Subject: [Paraview] [EXTERNAL] Re: CSV to PVTU In-Reply-To: References: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> Message-ID: I?m pretty sure if you select Duplicate Cells it will just copy all the points to all processes, so that is not a good option. The divide cells is also giving poor results on this front. I think you are better off using the 2D Glyph filter to break up the cell first. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Thursday, March 2, 2017 2:44 PM To: Moreland, Kenneth Cc: ParaView ; Rajamohan, Srijith ; Nicholas Polys ; Ayat Mohammed Subject: Re: [EXTERNAL] Re: [Paraview] CSV to PVTU Ohk, that makes more sense. I could get it to work as well but also had to check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. Thanks Moreland! On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth > wrote: Faiz, I was able to replicate your problem. It looks like it is not an issue with D3 but a change with how Table to Points creates data (or perhaps how data are written). It looks like Table to Points is creating one ?cell? with a lot of points. This saves a little memory but ends up preventing D3 from dividing the points up. The best solution is to add a ?2D Glyph? filter after the Table to Points but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the D3 filter to the output of the 2D Glyph filter. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Thursday, March 2, 2017 1:38 PM To: Moreland, Kenneth > Cc: ParaView >; Rajamohan, Srijith >; Nicholas Polys >; Ayat Mohammed > Subject: [EXTERNAL] Re: [Paraview] CSV to PVTU Hi Moreland, Thanks for your reply. I thought same except maybe not use the GUI since my data is big and takes forever to load up in Paraview. Quick question/observation - using the GUI and 8 processes, and applying the Tables to Points filter + D3 and then trying to save files doesn't create 8 vtu files and 1 pvtu file as expected. Instead, what happens is that I get only 1 pvtu file along with 1 vtu file instead. Clearly something wrong. This was done using v5.2.0. I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 vtu files and 1 pvtu file as expected. Do you think this is a bug with 5.2.0? Or do I need to do something different with 5.2.0? Any pointers appreciated! On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView > Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Fri Mar 3 14:14:27 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Fri, 3 Mar 2017 14:14:27 -0500 Subject: [Paraview] [EXTERNAL] Re: CSV to PVTU In-Reply-To: References: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> Message-ID: I see. I did that because when I choose "Assign Cells Uniquely" as the "Boundary Mode" in the D3 filter, I was getting a warning like below: Warning: In /home/faiz89/git/ParaView/VTK/Common/DataModel/vtkKdTree.cxx, line 1887 vtkKdTree (0x2db5950): vtkKdTree::BuildMapForDuplicatePoints - invalid tolerance But in spite of the warning, 8 vtu files get generated along with 1 pvtu file. So, maybe that warning can be ignored. On Thu, Mar 2, 2017 at 6:42 PM, Moreland, Kenneth wrote: > I?m pretty sure if you select Duplicate Cells it will just copy all the > points to all processes, so that is not a good option. The divide cells is > also giving poor results on this front. I think you are better off using > the 2D Glyph filter to break up the cell first. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Thursday, March 2, 2017 2:44 PM > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* Re: [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Ohk, that makes more sense. I could get it to work as well but also had to > check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. > > > > Thanks Moreland! > > > > On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth > wrote: > > Faiz, > > > > I was able to replicate your problem. It looks like it is not an issue > with D3 but a change with how Table to Points creates data (or perhaps how > data are written). It looks like Table to Points is creating one ?cell? > with a lot of points. This saves a little memory but ends up preventing D3 > from dividing the points up. > > > > The best solution is to add a ?2D Glyph? filter after the Table to Points > but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the > D3 filter to the output of the 2D Glyph filter. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Thursday, March 2, 2017 1:38 PM > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Hi Moreland, > > > > Thanks for your reply. > > > > I thought same except maybe not use the GUI since my data is big and takes > forever to load up in Paraview. > > > > Quick question/observation - using the GUI and 8 processes, and applying > the Tables to Points filter + D3 and then trying to save files doesn't > create 8 vtu files and 1 pvtu file as expected. Instead, what happens is > that I get only 1 pvtu file along with 1 vtu file instead. Clearly > something wrong. This was done using v5.2.0. > > > > I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 > vtu files and 1 pvtu file as expected. > > > > Do you think this is a bug with 5.2.0? Or do I need to do something > different with 5.2.0? Any pointers appreciated! > > > > On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: > > You can use ParaView itself to read in the csv file, convert it to an > unstructured grid (Table to Points filter), redistributed on your 8 > parallel processors (D3 filter) and then write out a pvtu file. > > > > Offhand I cannot think of an easier way. > > > > -Ken > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Faiz > Abidi > *Sent:* Wednesday, March 1, 2017 2:03 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] CSV to PVTU > > > > Hi again community! > > > > Looking for suggestions - what would be a decently fast way to convert a > huge CSV file into PVTU files? > > > > What I want to do - load this huge file in a CAVE like environment, and > use 8 parallel processors. > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saideep.Pavuluri at pet.hw.ac.uk Sat Mar 4 11:36:38 2017 From: Saideep.Pavuluri at pet.hw.ac.uk (Saideep Pavuluri) Date: Sat, 4 Mar 2017 16:36:38 +0000 Subject: [Paraview] Finding volume enclosed by a contour. Message-ID: Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Bubble vol.jpg Type: image/jpeg Size: 28487 bytes Desc: Bubble vol.jpg URL: From tim.gallagher at gatech.edu Sat Mar 4 12:09:13 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Sat, 4 Mar 2017 17:09:13 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: Message-ID: Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView on behalf of Saideep Pavuluri Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saideep.Pavuluri at pet.hw.ac.uk Sat Mar 4 12:30:54 2017 From: Saideep.Pavuluri at pet.hw.ac.uk (Saideep Pavuluri) Date: Sat, 4 Mar 2017 17:30:54 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: Message-ID: Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc.... How do I integrate the the region in space to find the enclosed volume? Sorry, if it's a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fig2.png Type: image/png Size: 8300 bytes Desc: fig2.png URL: From tim.gallagher at gatech.edu Sat Mar 4 12:36:05 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Sat, 4 Mar 2017 17:36:05 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , Message-ID: The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc?. How do I integrate the the region in space to find the enclosed volume? Sorry, if it?s a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saideep.Pavuluri at pet.hw.ac.uk Sat Mar 4 13:00:52 2017 From: Saideep.Pavuluri at pet.hw.ac.uk (Saideep Pavuluri) Date: Sat, 4 Mar 2017 18:00:52 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , Message-ID: Tim, I did try to vary from pointData to cellData but I see the same fields present. That is, I see no additional field being added. Attached is a screenshot (all the data from U are the variables being computed from my solver). I tried it over 4.x and 5.x versions of paraview so, I guess I am doing something wrong. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:36 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc.... How do I integrate the the region in space to find the enclosed volume? Sorry, if it's a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fig1.png Type: image/png Size: 203062 bytes Desc: fig1.png URL: From tim.gallagher at gatech.edu Sat Mar 4 13:07:27 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Sat, 4 Mar 2017 18:07:27 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , , Message-ID: Hmmm, interesting. It must be a function of the type of data from the OpenFOAM reader and I am unfamiliar with that reader. All of my datasets are structured and behave the way I mentioned earlier. I'm not sure how to get the volume from the dataset you have. Somebody else will have to chime in on this one. Just out of curiosity, if you IntegrateVariables again, does it condense the data into a single set of values? (That's a totally random guess -- maybe the first IntegrateVariables is coming up with the cell-averaged values from an unstructured dataset, and the second would do the integral of all the cell-averages). Sorry, I tried! Tim ________________________________ From: Saideep Pavuluri Sent: Saturday, March 4, 2017 1:00 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Tim, I did try to vary from pointData to cellData but I see the same fields present. That is, I see no additional field being added. Attached is a screenshot (all the data from U are the variables being computed from my solver). I tried it over 4.x and 5.x versions of paraview so, I guess I am doing something wrong. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:36 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc?. How do I integrate the the region in space to find the enclosed volume? Sorry, if it?s a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saideep.Pavuluri at pet.hw.ac.uk Sat Mar 4 13:44:32 2017 From: Saideep.Pavuluri at pet.hw.ac.uk (Saideep Pavuluri) Date: Sat, 4 Mar 2017 18:44:32 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , , Message-ID: Hi Tim; Yes I do think so it is somehow related to the OpenFOAM reader. I just tried a tutorial case from the CFD package and I still have the same data set with no additional data related to the volume/ area/ length. I am not sure if I understood your idea right, do you mean apply integrateVariables twice on the same threshold data set? "Sorry, I tried!" No worries this has been a long standing problem for my work. I am really happy that you shared your ideas with me. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 18:07 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Hmmm, interesting. It must be a function of the type of data from the OpenFOAM reader and I am unfamiliar with that reader. All of my datasets are structured and behave the way I mentioned earlier. I'm not sure how to get the volume from the dataset you have. Somebody else will have to chime in on this one. Just out of curiosity, if you IntegrateVariables again, does it condense the data into a single set of values? (That's a totally random guess -- maybe the first IntegrateVariables is coming up with the cell-averaged values from an unstructured dataset, and the second would do the integral of all the cell-averages). Sorry, I tried! Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 1:00 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Tim, I did try to vary from pointData to cellData but I see the same fields present. That is, I see no additional field being added. Attached is a screenshot (all the data from U are the variables being computed from my solver). I tried it over 4.x and 5.x versions of paraview so, I guess I am doing something wrong. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:36 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc.... How do I integrate the the region in space to find the enclosed volume? Sorry, if it's a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Sat Mar 4 13:46:40 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Sat, 4 Mar 2017 18:46:40 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , , , Message-ID: I was suggesting trying a pipeline like: OpenFOAM Reader -> Threshold -> IntegrateVariables -> IntegrateVariables So your second IV filter is applied to the first IV filter. Again, no idea if that will help. Hopefully somebody else can come along and give you a solution. Tim ________________________________ From: Saideep Pavuluri Sent: Saturday, March 4, 2017 1:44 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Hi Tim; Yes I do think so it is somehow related to the OpenFOAM reader. I just tried a tutorial case from the CFD package and I still have the same data set with no additional data related to the volume/ area/ length. I am not sure if I understood your idea right, do you mean apply integrateVariables twice on the same threshold data set? ?Sorry, I tried!? No worries this has been a long standing problem for my work. I am really happy that you shared your ideas with me. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 18:07 To: Saideep Pavuluri ; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Hmmm, interesting. It must be a function of the type of data from the OpenFOAM reader and I am unfamiliar with that reader. All of my datasets are structured and behave the way I mentioned earlier. I'm not sure how to get the volume from the dataset you have. Somebody else will have to chime in on this one. Just out of curiosity, if you IntegrateVariables again, does it condense the data into a single set of values? (That's a totally random guess -- maybe the first IntegrateVariables is coming up with the cell-averaged values from an unstructured dataset, and the second would do the integral of all the cell-averages). Sorry, I tried! Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 1:00 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Tim, I did try to vary from pointData to cellData but I see the same fields present. That is, I see no additional field being added. Attached is a screenshot (all the data from U are the variables being computed from my solver). I tried it over 4.x and 5.x versions of paraview so, I guess I am doing something wrong. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:36 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc?. How do I integrate the the region in space to find the enclosed volume? Sorry, if it?s a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD -------------- next part -------------- An HTML attachment was scrubbed... URL: From yzhzhang at ipe.ac.cn Sat Mar 4 21:29:21 2017 From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=) Date: Sun, 5 Mar 2017 10:29:21 +0800 (GMT+08:00) Subject: [Paraview] Is there any documentation that introduces new features of ParaView 5.3.0? Message-ID: <492c43.1daa7.15a9c4cc47a.Coremail.yzhzhang@ipe.ac.cn> Hello, ParaView 5.3.0 has been released for some time, I want to know if there is any documentation that introduces new features of it. I noticed that in ParaView 5.3.0, vtkm has replaced PISTON as an accelerator, but is it still just an accelerator for some filters? I am particularly concerned that if my data is generated by the code running on GPUs, can I write something like an adapter to visualize the data in situ in GPU memory ? My data is just point data and doesn't need any filter. Thanks! -Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdutta at vt.edu Sat Mar 4 22:19:54 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Sat, 4 Mar 2017 22:19:54 -0500 Subject: [Paraview] Query on EGL libs for Paraview 5.0.1 Message-ID: Hi All, I am trying to compile Paraview 5.0.1 with EGL support as I want to use NVIDIA Tesla K20c for rendering in Ubuntu 14.04. This is without any windowing system as K20c is designed for server based rendering (without any VGA port and OpenGL support (I think!)) I went through https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/ and as I understand, for this I need to set the below Paraview flags before compilation: VTK_EGL_DEVICE_INDEX=set to graphics driver index VTK_USE_OFFSCREEN_EGL =on EGL_INCLUDE_DIR EGL_LIBRARY /usr/lib/x86_64-linux-gnu/libEGL.so EGL_gldispatch_LIBRARY /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 EGL_opengl_LIBRARY /usr/lib/x86_64-linux-gnu/libOpenGL.so My query is on gettting the correct libs i.e. libEGL.so, libGLdispatch.so.0 and libOpenGL.so. When I installed "NVIDIA-Linux-x86_64-375.26.run" these libs were not installed. Which is the right place to get them. I can see several links on internet search: https://github.com/NVIDIA/libglvnd/blob/master/README.md https://www.mesa3d.org/egl.html Which is the correct one Thanks in advance for help. BR, Bishwajit Virginia Tech -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipebordeu at gmail.com Sun Mar 5 04:27:26 2017 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Sun, 5 Mar 2017 10:27:26 +0100 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: Message-ID: The volume is nothing more that the integral of one (1). So make a calculator with a new variable named "rho" and with the value 1 then apply the int?grate variable filter to compute the volume. Be careful no to have bars in your mesh, they will also contribute to the volume calculation. In general you must filter your mesh by dimensionality (only 3D cell or only 2D...) Hope it helps Felipe Le 4 mars 2017 7:46 PM, "Gallagher, Timothy P" a ?crit : > I was suggesting trying a pipeline like: > > > OpenFOAM Reader -> Threshold -> IntegrateVariables -> IntegrateVariables > > > So your second IV filter is applied to the first IV filter. > > > Again, no idea if that will help. Hopefully somebody else can come along > and give you a solution. > > > Tim > > > ------------------------------ > *From:* Saideep Pavuluri > *Sent:* Saturday, March 4, 2017 1:44 PM > *To:* Gallagher, Timothy P; paraview at paraview.org > *Subject:* RE: Finding volume enclosed by a contour. > > > Hi Tim; > > > > Yes I do think so it is somehow related to the OpenFOAM reader. I just > tried a tutorial case from the CFD package and I still have the same data > set with no additional data related to the volume/ area/ length. > > > > I am not sure if I understood your idea right, do you mean apply > integrateVariables twice on the same threshold data set? > > > > ?Sorry, I tried!? > > No worries this has been a long standing problem for my work. I am really > happy that you shared your ideas with me. > > > > Saideep > > > > *From:* Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] > *Sent:* 04 March 2017 18:07 > *To:* Saideep Pavuluri ; > paraview at paraview.org > *Subject:* Re: Finding volume enclosed by a contour. > > > > Hmmm, interesting. It must be a function of the type of data from the > OpenFOAM reader and I am unfamiliar with that reader. > > > > All of my datasets are structured and behave the way I mentioned earlier. > I'm not sure how to get the volume from the dataset you have. > > > > Somebody else will have to chime in on this one. Just out of curiosity, if > you IntegrateVariables again, does it condense the data into a single set > of values? (That's a totally random guess -- maybe the first > IntegrateVariables is coming up with the cell-averaged values from an > unstructured dataset, and the second would do the integral of all the > cell-averages). > > > > Sorry, I tried! > > > > Tim > > > ------------------------------ > > *From:* Saideep Pavuluri > *Sent:* Saturday, March 4, 2017 1:00 PM > *To:* Gallagher, Timothy P; paraview at paraview.org > *Subject:* RE: Finding volume enclosed by a contour. > > > > Tim, > > > > I did try to vary from pointData to cellData but I see the same fields > present. That is, I see no additional field being added. > > > > Attached is a screenshot (all the data from U are the variables being > computed from my solver). I tried it over 4.x and 5.x versions of paraview > so, I guess I am doing something wrong. > > > > Saideep > > > > *From:* Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu > ] > *Sent:* 04 March 2017 17:36 > *To:* Saideep Pavuluri ; > paraview at paraview.org > *Subject:* Re: Finding volume enclosed by a contour. > > > > The IntegrateVariables filter creates a spreadsheet of PointData (or > CellData, depending on where your data is stored in the filter just before > IntegrateVariables) with the integral of your data over the > volume/area/length depending on if it is 3D/2D/1D data respectively. > > > > It also adds a field to the CellData array that will be Volume/Area/Length > respectively. > > > > My guess is if you aren't seeing it immediately it is because you are > looking at the PointData array and not the CellData array. In the > SpreadSheetView that opens up, change the Attribute dropdown from Point > Data to Cell Data. > > > > Also, as a note -- the values for your variables (pressure, velocity, > whatever) are multiplied by the length scale, so if you want the average > value in the domain, you need to divide it by the length scale. > > > > Tim > > > ------------------------------ > > *From:* Saideep Pavuluri > *Sent:* Saturday, March 4, 2017 12:30 PM > *To:* Gallagher, Timothy P; paraview at paraview.org > *Subject:* RE: Finding volume enclosed by a contour. > > > > Thanks Tim; > > > > I could precisely extract the bubble using the threshold filter as you > said (attached picture). > > > > Coming to the 2nd step: I applied the integrate variables filter on the > threshold data but I get the general data set values within individual > cells like the computed velocity, pressure, etc?. > > > > How do I integrate the the region in space to find the enclosed volume? > > > > Sorry, if it?s a basic question. > > > > Saideep > > > > *From:* Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu > ] > *Sent:* 04 March 2017 17:09 > *To:* Saideep Pavuluri ; > paraview at paraview.org > *Subject:* Re: Finding volume enclosed by a contour. > > > > Your best bet would be to use the Threshold filter to extract the region > where the scalar is greater (or less than) 0.5 and then use the > IntegrateVariables filter on the Threshold. > > > > It's not entirely clear your exact pipeline, but it sounds like you are > using the IntegrateVariables filter on the Contour, which would give you > the surface area of the region instead. > > > > Tim > > > ------------------------------ > > *From:* ParaView on behalf of Saideep > Pavuluri > *Sent:* Saturday, March 4, 2017 11:36 AM > *To:* paraview at paraview.org > *Subject:* [Paraview] Finding volume enclosed by a contour. > > > > Hi guys; > > > > I am using a numerical method (Volume of fluid, just for information) to > look at the breaking of a bubble in a micro-channel. Attached picture. > > > > As mostly, the bubbles are of uniform size, I would like to know the > volume of any one bubble formed. > > > > The bubble is represented by a scalar data set represented by 1 and > bounded by the same data set with values 0. > > > > I think to clip the region enclosing one bubble and draw a contour where > the scalar value is 0.5. Now, I tried the integrate variables filter but I > did not find a data representing the volume. Any idea how can I get the > volume enclosed by this contour? > > > > Any help appreciated. > > > > Thanks; > > SaiD > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daviddoria at gmail.com Sun Mar 5 11:31:06 2017 From: daviddoria at gmail.com (David Doria) Date: Sun, 5 Mar 2017 10:31:06 -0600 Subject: [Paraview] CellCenters filter produces non-deterministic result Message-ID: With this file , when I apply a Cell Centers filter sometimes it works (see attached works.jpg) and sometimes it produces garbage output (note the Y-range) (see attached broken.jpg) Can anyone explain why this is? Thanks, David (See the same question here for inline images: http://stackoverflow.com/questions/42543496/cellcenters-filter-non-deterministic-result ) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: works.jpg Type: image/jpeg Size: 38697 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: broken.jpg Type: image/jpeg Size: 38467 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Sun Mar 5 11:52:39 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 5 Mar 2017 11:52:39 -0500 Subject: [Paraview] 2d image tiling problem In-Reply-To: References: Message-ID: Alan, There are couple of options that could be work exploring. Let me know which you see is most appropriate and I can get you in touch with the appropriate folks. 1. GeoJS -- a web-based solution. Docs: https://github.com/OpenGeoscience/geojs Example: http://opengeoscience.github.io/geojs/examples/deepzoom/ Other examples: http://opengeoscience.github.io/geojs/examples/index.html 2. vtkMap -- a VTK-based solution which is currently being developed which also includes ParaView integration. Code: https://github.com/OpenGeoscience/vtkMap Utkarsh On Tue, Feb 28, 2017 at 2:57 PM, Scott, W Alan wrote: > Hi guys, > > I have a user that wants to visualize very large images (i.e., terrabyte > size images). These images are composed of tiles or subimages, which are > offset in the main image according to a metafile. Does Kitware have any > tools for visualizing and manipulating large images? > > > > Thanks, > > > > Alan > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ronald.fowler at stfc.ac.uk Sun Mar 5 13:52:40 2017 From: ronald.fowler at stfc.ac.uk (ronald.fowler at stfc.ac.uk) Date: Sun, 5 Mar 2017 18:52:40 +0000 Subject: [Paraview] Finding volume enclosed by a contour. In-Reply-To: References: , Message-ID: <398242C76E3D3740BA94E23089B34E2C012C75BA69@exchmbx03> I was trying IntegrateVaraiables with OpenFoam data last week and it seemed to give the areas OK, though the data had been converted to EnSight format- might be worth a try? Ron fowler ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Felipe Bordeu [felipebordeu at gmail.com] Sent: 05 March 2017 09:27 Cc: paraview Subject: Re: [Paraview] Finding volume enclosed by a contour. The volume is nothing more that the integral of one (1). So make a calculator with a new variable named "rho" and with the value 1 then apply the int?grate variable filter to compute the volume. Be careful no to have bars in your mesh, they will also contribute to the volume calculation. In general you must filter your mesh by dimensionality (only 3D cell or only 2D...) Hope it helps Felipe Le 4 mars 2017 7:46 PM, "Gallagher, Timothy P" > a ?crit : I was suggesting trying a pipeline like: OpenFOAM Reader -> Threshold -> IntegrateVariables -> IntegrateVariables So your second IV filter is applied to the first IV filter. Again, no idea if that will help. Hopefully somebody else can come along and give you a solution. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 1:44 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Hi Tim; Yes I do think so it is somehow related to the OpenFOAM reader. I just tried a tutorial case from the CFD package and I still have the same data set with no additional data related to the volume/ area/ length. I am not sure if I understood your idea right, do you mean apply integrateVariables twice on the same threshold data set? ?Sorry, I tried!? No worries this has been a long standing problem for my work. I am really happy that you shared your ideas with me. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 18:07 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Hmmm, interesting. It must be a function of the type of data from the OpenFOAM reader and I am unfamiliar with that reader. All of my datasets are structured and behave the way I mentioned earlier. I'm not sure how to get the volume from the dataset you have. Somebody else will have to chime in on this one. Just out of curiosity, if you IntegrateVariables again, does it condense the data into a single set of values? (That's a totally random guess -- maybe the first IntegrateVariables is coming up with the cell-averaged values from an unstructured dataset, and the second would do the integral of all the cell-averages). Sorry, I tried! Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 1:00 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Tim, I did try to vary from pointData to cellData but I see the same fields present. That is, I see no additional field being added. Attached is a screenshot (all the data from U are the variables being computed from my solver). I tried it over 4.x and 5.x versions of paraview so, I guess I am doing something wrong. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:36 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. The IntegrateVariables filter creates a spreadsheet of PointData (or CellData, depending on where your data is stored in the filter just before IntegrateVariables) with the integral of your data over the volume/area/length depending on if it is 3D/2D/1D data respectively. It also adds a field to the CellData array that will be Volume/Area/Length respectively. My guess is if you aren't seeing it immediately it is because you are looking at the PointData array and not the CellData array. In the SpreadSheetView that opens up, change the Attribute dropdown from Point Data to Cell Data. Also, as a note -- the values for your variables (pressure, velocity, whatever) are multiplied by the length scale, so if you want the average value in the domain, you need to divide it by the length scale. Tim ________________________________ From: Saideep Pavuluri > Sent: Saturday, March 4, 2017 12:30 PM To: Gallagher, Timothy P; paraview at paraview.org Subject: RE: Finding volume enclosed by a contour. Thanks Tim; I could precisely extract the bubble using the threshold filter as you said (attached picture). Coming to the 2nd step: I applied the integrate variables filter on the threshold data but I get the general data set values within individual cells like the computed velocity, pressure, etc?. How do I integrate the the region in space to find the enclosed volume? Sorry, if it?s a basic question. Saideep From: Gallagher, Timothy P [mailto:tim.gallagher at gatech.edu] Sent: 04 March 2017 17:09 To: Saideep Pavuluri >; paraview at paraview.org Subject: Re: Finding volume enclosed by a contour. Your best bet would be to use the Threshold filter to extract the region where the scalar is greater (or less than) 0.5 and then use the IntegrateVariables filter on the Threshold. It's not entirely clear your exact pipeline, but it sounds like you are using the IntegrateVariables filter on the Contour, which would give you the surface area of the region instead. Tim ________________________________ From: ParaView > on behalf of Saideep Pavuluri > Sent: Saturday, March 4, 2017 11:36 AM To: paraview at paraview.org Subject: [Paraview] Finding volume enclosed by a contour. Hi guys; I am using a numerical method (Volume of fluid, just for information) to look at the breaking of a bubble in a micro-channel. Attached picture. As mostly, the bubbles are of uniform size, I would like to know the volume of any one bubble formed. The bubble is represented by a scalar data set represented by 1 and bounded by the same data set with values 0. I think to clip the region enclosing one bubble and draw a contour where the scalar value is 0.5. Now, I tried the integrate variables filter but I did not find a data representing the volume. Any idea how can I get the volume enclosed by this contour? Any help appreciated. Thanks; SaiD _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From fabidi89 at vt.edu Sun Mar 5 18:08:42 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Sun, 5 Mar 2017 18:08:42 -0500 Subject: [Paraview] [EXTERNAL] Re: CSV to PVTU In-Reply-To: References: <78e52cf10f9c4102a8a433ecf3d5ac88@ES08AMSNLNT.srn.sandia.gov> Message-ID: Btw, I am a bit confused that why after applying a "2D Glyph" filter and "Glyph Type" as "Vertex", the number of points decreases. For example, if after applying "TableToPoints" filter I have 1 cell and 100k points, I get 502 cells and 502 points after applying a "2D Glyph" filter. I was expecting the number of cells to increase but total number of points should have remained 100k, no? I am not really sure if applying a 2D Glyph is the best solution in my case. I may go back to using 4.0.1 to convert this csv data into pvtu and then use the latest version to load it up. On Fri, Mar 3, 2017 at 2:14 PM, Faiz Abidi wrote: > I see. > > I did that because when I choose "Assign Cells Uniquely" as the "Boundary > Mode" in the D3 filter, I was getting a warning like below: > > Warning: In /home/faiz89/git/ParaView/VTK/Common/DataModel/vtkKdTree.cxx, > line 1887 > vtkKdTree (0x2db5950): vtkKdTree::BuildMapForDuplicatePoints - invalid > tolerance > > But in spite of the warning, 8 vtu files get generated along with 1 pvtu > file. So, maybe that warning can be ignored. > > > On Thu, Mar 2, 2017 at 6:42 PM, Moreland, Kenneth > wrote: > >> I?m pretty sure if you select Duplicate Cells it will just copy all the >> points to all processes, so that is not a good option. The divide cells is >> also giving poor results on this front. I think you are better off using >> the 2D Glyph filter to break up the cell first. >> >> >> >> -Ken >> >> >> >> *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] >> *Sent:* Thursday, March 2, 2017 2:44 PM >> *To:* Moreland, Kenneth >> *Cc:* ParaView ; Rajamohan, Srijith < >> srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < >> maaayat at vt.edu> >> *Subject:* Re: [EXTERNAL] Re: [Paraview] CSV to PVTU >> >> >> >> Ohk, that makes more sense. I could get it to work as well but also had >> to check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. >> >> >> >> Thanks Moreland! >> >> >> >> On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth >> wrote: >> >> Faiz, >> >> >> >> I was able to replicate your problem. It looks like it is not an issue >> with D3 but a change with how Table to Points creates data (or perhaps how >> data are written). It looks like Table to Points is creating one ?cell? >> with a lot of points. This saves a little memory but ends up preventing D3 >> from dividing the points up. >> >> >> >> The best solution is to add a ?2D Glyph? filter after the Table to Points >> but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the >> D3 filter to the output of the 2D Glyph filter. >> >> >> >> -Ken >> >> >> >> *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] >> *Sent:* Thursday, March 2, 2017 1:38 PM >> *To:* Moreland, Kenneth >> *Cc:* ParaView ; Rajamohan, Srijith < >> srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < >> maaayat at vt.edu> >> *Subject:* [EXTERNAL] Re: [Paraview] CSV to PVTU >> >> >> >> Hi Moreland, >> >> >> >> Thanks for your reply. >> >> >> >> I thought same except maybe not use the GUI since my data is big and >> takes forever to load up in Paraview. >> >> >> >> Quick question/observation - using the GUI and 8 processes, and applying >> the Tables to Points filter + D3 and then trying to save files doesn't >> create 8 vtu files and 1 pvtu file as expected. Instead, what happens is >> that I get only 1 pvtu file along with 1 vtu file instead. Clearly >> something wrong. This was done using v5.2.0. >> >> >> >> I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 >> vtu files and 1 pvtu file as expected. >> >> >> >> Do you think this is a bug with 5.2.0? Or do I need to do something >> different with 5.2.0? Any pointers appreciated! >> >> >> >> On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth >> wrote: >> >> You can use ParaView itself to read in the csv file, convert it to an >> unstructured grid (Table to Points filter), redistributed on your 8 >> parallel processors (D3 filter) and then write out a pvtu file. >> >> >> >> Offhand I cannot think of an easier way. >> >> >> >> -Ken >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Faiz >> Abidi >> *Sent:* Wednesday, March 1, 2017 2:03 PM >> *To:* ParaView >> *Subject:* [EXTERNAL] [Paraview] CSV to PVTU >> >> >> >> Hi again community! >> >> >> >> Looking for suggestions - what would be a decently fast way to convert a >> huge CSV file into PVTU files? >> >> >> >> What I want to do - load this huge file in a CAVE like environment, and >> use 8 parallel processors. >> -- >> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | >> +1-540-998-6636 <(540)%20998-6636> >> >> >> >> >> >> -- >> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | >> +1-540-998-6636 <(540)%20998-6636> >> >> >> >> >> >> -- >> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | >> +1-540-998-6636 <(540)%20998-6636> >> > > > > -- > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sun Mar 5 19:09:28 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 5 Mar 2017 19:09:28 -0500 Subject: [Paraview] Query on EGL libs for Paraview 5.0.1 In-Reply-To: References: Message-ID: Hi, Maybe look in: /usr/lib/nvidia- for the drivers -- that's where it is for my r367 NVIDIA drivers on Ubuntu 16.04. Otherwise you may need to check with NVIDIA on where it gets installed for your set of drivers and system. On Sat, Mar 4, 2017 at 10:19 PM, Bishwajit Dutta wrote: > Hi All, > > I am trying to compile Paraview 5.0.1 with EGL support as I want to use > NVIDIA Tesla K20c > for rendering in Ubuntu 14.04. This is without any windowing system as > K20c is designed for > server based rendering (without any VGA port and OpenGL support (I think!)) > > I went through > > https://blog.kitware.com/off-screen-rendering-through-the- > native-platform-interface-egl/ > > and as I understand, for this I need to set the below Paraview flags > before compilation: > > VTK_EGL_DEVICE_INDEX=set to graphics driver index > VTK_USE_OFFSCREEN_EGL =on > EGL_INCLUDE_DIR > EGL_LIBRARY /usr/lib/x86_64-linux-gnu/libEGL.so > EGL_gldispatch_LIBRARY /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 > EGL_opengl_LIBRARY /usr/lib/x86_64-linux-gnu/libOpenGL.so > > My query is on gettting the correct libs i.e. libEGL.so, > libGLdispatch.so.0 and libOpenGL.so. > > When I installed "NVIDIA-Linux-x86_64-375.26.run" these libs were not > installed. > > Which is the right place to get them. I can see several links on internet > search: > > https://github.com/NVIDIA/libglvnd/blob/master/README.md > > https://www.mesa3d.org/egl.html > > Which is the correct one > > Thanks in advance for help. > > BR, > Bishwajit > Virginia Tech > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sun Mar 5 20:05:14 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 5 Mar 2017 20:05:14 -0500 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: Hi David, This looks like it has to do with blanking (i.e. in PV 5.2 if I don't load the vtkGhostType array it has the proper bounds). Would you mind putting in a bug report on Gitlab (https://gitlab.kitware.com/paraview/paraview)? Thanks, Andy On Sun, Mar 5, 2017 at 11:31 AM, David Doria wrote: > With this file > , when I > apply a Cell Centers filter sometimes it works (see attached works.jpg) and > sometimes it produces garbage output (note the Y-range) (see attached > broken.jpg) > > Can anyone explain why this is? > > Thanks, > > David > > (See the same question here for inline images: http://stackoverflow.com/ > questions/42543496/cellcenters-filter-non-deterministic-result) > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From David.Benn at csiro.au Sun Mar 5 21:57:13 2017 From: David.Benn at csiro.au (David.Benn at csiro.au) Date: Mon, 6 Mar 2017 02:57:13 +0000 Subject: [Paraview] Paraview 5.3 release notes Message-ID: <6f8f867821764367a8a14dd85833bc45@exch4-cdc.nexus.csiro.au> Apologies if there has already been a post about this, but after searching the list archive I didn't see it. I downloaded a Windows 64 bit installer for Paraview 5.3.0 RC2 and tried to look at the release notes via the Help menu but the URL opened in the browser points to a page that does not exist: https://blog.kitware.com/paraview-5-3-0-release-notes/ I tried a few variants of the URL but can't see release notes. I'm keen to see whether this was included: https://gitlab.kitware.com/paraview/paraview/issues/17135 David -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Mar 5 22:05:31 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 5 Mar 2017 22:05:31 -0500 Subject: [Paraview] Paraview 5.3 release notes In-Reply-To: <6f8f867821764367a8a14dd85833bc45@exch4-cdc.nexus.csiro.au> References: <6f8f867821764367a8a14dd85833bc45@exch4-cdc.nexus.csiro.au> Message-ID: Hi David, > > I tried a few variants of the URL but can?t see release notes. We typically don't post the release notes until the final binaries are released as new items may be added during the release candidate phase as issues are identified. > I?m keen to see whether this was included: > > https://gitlab.kitware.com/paraview/paraview/issues/17135 > Yes, this will be in 5.3.0. Thanks again for the patch. Cory > > David > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Sun Mar 5 22:07:39 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 5 Mar 2017 22:07:39 -0500 Subject: [Paraview] Is there any documentation that introduces new features of ParaView 5.3.0? In-Reply-To: <492c43.1daa7.15a9c4cc47a.Coremail.yzhzhang@ipe.ac.cn> References: <492c43.1daa7.15a9c4cc47a.Coremail.yzhzhang@ipe.ac.cn> Message-ID: Hi Zhang, > ParaView 5.3.0 has been released for some time, We are actually still in the release candidate phase. The final release of 5.3.0 should be coming out next week. > I want to know if there is > any documentation that introduces new features of it. Yes, there will be. > I noticed that in > ParaView 5.3.0, vtkm has replaced PISTON as an accelerator, but is it still > just an accelerator for some filters? I am particularly concerned that if my > data is generated by the code running on GPUs, can I write something like an > adapter to visualize the data in situ in GPU memory ? My data is just point > data and doesn't need any filter. I have to defer to the VTKm and in situ experts on the list to answer this question. Best, Cory > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From David.Benn at csiro.au Sun Mar 5 22:18:58 2017 From: David.Benn at csiro.au (David.Benn at csiro.au) Date: Mon, 6 Mar 2017 03:18:58 +0000 Subject: [Paraview] Paraview 5.3 release notes In-Reply-To: References: <6f8f867821764367a8a14dd85833bc45@exch4-cdc.nexus.csiro.au> Message-ID: <0ea32f9025ab419cbec3b624b5515119@exch4-cdc.nexus.csiro.au> Thanks Cory. David -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Monday, 6 March 2017 1:36 PM To: Benn, David (IM&T, Waite Campus) Cc: ParaView Subject: Re: [Paraview] Paraview 5.3 release notes Hi David, > > I tried a few variants of the URL but can?t see release notes. We typically don't post the release notes until the final binaries are released as new items may be added during the release candidate phase as issues are identified. > I?m keen to see whether this was included: > > https://gitlab.kitware.com/paraview/paraview/issues/17135 > Yes, this will be in 5.3.0. Thanks again for the patch. Cory > > David > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From daviddoria at gmail.com Mon Mar 6 08:45:56 2017 From: daviddoria at gmail.com (David Doria) Date: Mon, 6 Mar 2017 07:45:56 -0600 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer wrote: > Hi David, > > This looks like it has to do with blanking (i.e. in PV 5.2 if I don't load > the vtkGhostType array it has the proper bounds). Would you mind putting in > a bug report on Gitlab (https://gitlab.kitware.com/paraview/paraview)? > > Thanks, > Andy > Done: https://gitlab.kitware.com/paraview/paraview/issues/17244 Here is another presumed bug that seems to also have to do with blanking: http://stackoverflow.com/questions/42543340/cell-labels-in-selection-display-inspector-dont-work-when-any-cells-are-ghosted - not trying to pollute this thread but do you think that behavior could be helpful to understand the Cell Centers issue? Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.held at uibk.ac.at Mon Mar 6 10:25:16 2017 From: markus.held at uibk.ac.at (markus) Date: Mon, 06 Mar 2017 16:25:16 +0100 Subject: [Paraview] 3d contour interpolation problem Message-ID: <58BD7F5C.1060705@uibk.ac.at> Dear all, i currently experience a 3d contour issue in paraview. If i try to visualise my scalar data on a cylindrical R,Z,\varphi grid by contours, the interpolation of the contours prefers the \varphi direction even if the real data or contour prefers the direction along another vectorfield. You can find an exemplary picture at https://github.com/feltor-dev/feltor. Here, the bubbles along \varphi are not interpolated correctly. Is there any workaround to do it correctly? best regards markus held From markus.held at uibk.ac.at Mon Mar 6 10:17:43 2017 From: markus.held at uibk.ac.at (markus) Date: Mon, 06 Mar 2017 16:17:43 +0100 Subject: [Paraview] 3d contour interpolation problem Message-ID: <58BD7D97.5090401@uibk.ac.at> Dear all, i currently experience a 3d contour issue in paraview. If i try to visualise my scalar data on a cylindrical R,Z,\varphi grid by contours, the interpolation of the contours prefers the \varphi direction even if the real data or contour prefers the direction along another vectorfield. You can find an exemplary picture at https://github.com/feltor-dev/feltor. Here, the bubbles along \varphi are not interpolated correctly. best regards markus held From markus.held at uibk.ac.at Mon Mar 6 10:18:40 2017 From: markus.held at uibk.ac.at (markus) Date: Mon, 06 Mar 2017 16:18:40 +0100 Subject: [Paraview] 3d contour interpolation problem Message-ID: <58BD7DD0.3060704@uibk.ac.at> Dear all, i currently experience a 3d contour issue in paraview. If i try to visualise my scalar data on a cylindrical R,Z,\varphi grid by contours, the interpolation of the contours prefers the \varphi direction even if the real data or contour prefers the direction along another vectorfield. You can find an exemplary picture at https://github.com/feltor-dev/feltor. Here, the bubbles along \varphi are not interpolated correctly. Is there any workaround to do it correctly? best regards markus held From utkarsh.ayachit at kitware.com Mon Mar 6 11:12:05 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Mar 2017 11:12:05 -0500 Subject: [Paraview] How to save a high-resolution image that contains a selected region of the viewport? In-Reply-To: <15c95ef.1675.15a70146209.Coremail.yzhzhang@ipe.ac.cn> References: <15c95ef.1675.15a70146209.Coremail.yzhzhang@ipe.ac.cn> Message-ID: Zhang, Since you're most likely changing the aspect ratio quite dramatically, I'd suggest the following: 1. explicitly setting the current view size to have an aspect ratio comparable to the target, but keep the resolution smaller than what's available on your display. You can use "Tools | Lock View Size To Custom". 2. then, adjust the scene as appropriate to view the data optimally. 3. now try saving the screenshot of the resolution of interest. Utkarsh On Fri, Feb 24, 2017 at 7:24 AM, ??? wrote: > > Hello, > > I'm using paraview 5.2.0 to render a relatively large dataset. In the > simulated region, the Z direction is much larger than that of X and Y. I > want to save a high-resolution image that contains the whole simulation > region, but no other regions. However, by only specifying a relatively high > resolution, like 2,000*50,000, in the Save Screenshot Options dialog, I got > an image that mainly contains the background, not the simulation region. I > wonder if I can select the region that I want to save and specify a high > resolution to get the details in the region and then save it as an image? > > Thanks! > -Zhang > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From andy.bauer at kitware.com Mon Mar 6 12:14:56 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 6 Mar 2017 12:14:56 -0500 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: Thanks for the bug report! I think the stackoverflow issue is probably also related to blanking. I added to your bug report with two other (likely) related issues. As a side note, I think if blanking was used instead of ghost cells this may work properly. Thanks, Andy On Mon, Mar 6, 2017 at 8:45 AM, David Doria wrote: > On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer wrote: > >> Hi David, >> >> This looks like it has to do with blanking (i.e. in PV 5.2 if I don't >> load the vtkGhostType array it has the proper bounds). Would you mind >> putting in a bug report on Gitlab (https://gitlab.kitware.com/pa >> raview/paraview)? >> >> Thanks, >> Andy >> > > Done: > https://gitlab.kitware.com/paraview/paraview/issues/17244 > > Here is another presumed bug that seems to also have to do with blanking: > http://stackoverflow.com/questions/42543340/cell-labels-in- > selection-display-inspector-dont-work-when-any-cells-are-ghosted - not > trying to pollute this thread but do you think that behavior could be > helpful to understand the Cell Centers issue? > > Thanks, > > David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Mar 6 13:18:40 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 6 Mar 2017 18:18:40 +0000 Subject: [Paraview] CSV to PVTU Message-ID: Sorry, I might have mislead you a little bit before. What you actually need is the Glyph filter with Glyph Type set to 2D Glyph and then the secondary Glyph Type set to Vertex. By default the glyph filter subsamples the data (to prevent occlusion when creating glyphs with size). Under Masking change the Glyph Mode to All Points, and you should get what you want. Also, check the vtu files being generated by ParaView 4.0.1 carefully. I suspect one of them is very large and all the others are very small. I think the old version of ParaView is writing a bunch of vtu files with no points whereas new versions of ParaView are not writing out pointless empty vtu files. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Sunday, March 5, 2017 4:09 PM To: Moreland, Kenneth Cc: ParaView ; Rajamohan, Srijith ; Nicholas Polys ; Ayat Mohammed Subject: Re: [EXTERNAL] Re: [Paraview] CSV to PVTU Btw, I am a bit confused that why after applying a "2D Glyph" filter and "Glyph Type" as "Vertex", the number of points decreases. For example, if after applying "TableToPoints" filter I have 1 cell and 100k points, I get 502 cells and 502 points after applying a "2D Glyph" filter. I was expecting the number of cells to increase but total number of points should have remained 100k, no? I am not really sure if applying a 2D Glyph is the best solution in my case. I may go back to using 4.0.1 to convert this csv data into pvtu and then use the latest version to load it up. On Fri, Mar 3, 2017 at 2:14 PM, Faiz Abidi > wrote: I see. I did that because when I choose "Assign Cells Uniquely" as the "Boundary Mode" in the D3 filter, I was getting a warning like below: Warning: In /home/faiz89/git/ParaView/VTK/Common/DataModel/vtkKdTree.cxx, line 1887 vtkKdTree (0x2db5950): vtkKdTree::BuildMapForDuplicatePoints - invalid tolerance But in spite of the warning, 8 vtu files get generated along with 1 pvtu file. So, maybe that warning can be ignored. On Thu, Mar 2, 2017 at 6:42 PM, Moreland, Kenneth > wrote: I?m pretty sure if you select Duplicate Cells it will just copy all the points to all processes, so that is not a good option. The divide cells is also giving poor results on this front. I think you are better off using the 2D Glyph filter to break up the cell first. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Thursday, March 2, 2017 2:44 PM To: Moreland, Kenneth > Cc: ParaView >; Rajamohan, Srijith >; Nicholas Polys >; Ayat Mohammed > Subject: Re: [EXTERNAL] Re: [Paraview] CSV to PVTU Ohk, that makes more sense. I could get it to work as well but also had to check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. Thanks Moreland! On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth > wrote: Faiz, I was able to replicate your problem. It looks like it is not an issue with D3 but a change with how Table to Points creates data (or perhaps how data are written). It looks like Table to Points is creating one ?cell? with a lot of points. This saves a little memory but ends up preventing D3 from dividing the points up. The best solution is to add a ?2D Glyph? filter after the Table to Points but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the D3 filter to the output of the 2D Glyph filter. -Ken From: Faiz Abidi [mailto:fabidi89 at vt.edu] Sent: Thursday, March 2, 2017 1:38 PM To: Moreland, Kenneth > Cc: ParaView >; Rajamohan, Srijith >; Nicholas Polys >; Ayat Mohammed > Subject: [EXTERNAL] Re: [Paraview] CSV to PVTU Hi Moreland, Thanks for your reply. I thought same except maybe not use the GUI since my data is big and takes forever to load up in Paraview. Quick question/observation - using the GUI and 8 processes, and applying the Tables to Points filter + D3 and then trying to save files doesn't create 8 vtu files and 1 pvtu file as expected. Instead, what happens is that I get only 1 pvtu file along with 1 vtu file instead. Clearly something wrong. This was done using v5.2.0. I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 vtu files and 1 pvtu file as expected. Do you think this is a bug with 5.2.0? Or do I need to do something different with 5.2.0? Any pointers appreciated! On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: You can use ParaView itself to read in the csv file, convert it to an unstructured grid (Table to Points filter), redistributed on your 8 parallel processors (D3 filter) and then write out a pvtu file. Offhand I cannot think of an easier way. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Faiz Abidi Sent: Wednesday, March 1, 2017 2:03 PM To: ParaView > Subject: [EXTERNAL] [Paraview] CSV to PVTU Hi again community! Looking for suggestions - what would be a decently fast way to convert a huge CSV file into PVTU files? What I want to do - load this huge file in a CAVE like environment, and use 8 parallel processors. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.maynard at kitware.com Mon Mar 6 13:32:35 2017 From: robert.maynard at kitware.com (Robert Maynard) Date: Mon, 6 Mar 2017 13:32:35 -0500 Subject: [Paraview] Is there any documentation that introduces new features of ParaView 5.3.0? In-Reply-To: <492c43.1daa7.15a9c4cc47a.Coremail.yzhzhang@ipe.ac.cn> References: <492c43.1daa7.15a9c4cc47a.Coremail.yzhzhang@ipe.ac.cn> Message-ID: > I am particularly concerned that if my > data is generated by the code running on GPUs, can I write something like an > adapter to visualize the data in situ in GPU memory ? My data is just point > data and doesn't need any filter. Yes you can use VTK-m for this exact use case, but it will require you to write a new VTK-m / ParaView component. VTK-m offers a collection of OpenGL functions that help marshall data between CUDA and the OpenGL runtime. if you are curious on what this would entail I recommend starting with the VTK-m users guide (still a work in progress) : http://m.vtk.org/images/c/c8/VTKmUsersGuide.pdf On Sat, Mar 4, 2017 at 9:29 PM, ??? wrote: > > > Hello, > > ParaView 5.3.0 has been released for some time, I want to know if there is > any documentation that introduces new features of it. I noticed that in > ParaView 5.3.0, vtkm has replaced PISTON as an accelerator, but is it still > just an accelerator for some filters? I am particularly concerned that if my > data is generated by the code running on GPUs, can I write something like an > adapter to visualize the data in situ in GPU memory ? My data is just point > data and doesn't need any filter. > > Thanks! > > -Zhang > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From l.rabbit.88 at gmail.com Mon Mar 6 16:11:20 2017 From: l.rabbit.88 at gmail.com (John) Date: Mon, 6 Mar 2017 16:11:20 -0500 Subject: [Paraview] pvpython, get data over time Message-ID: Hello all, I'm trying to collect data over time. Using as a #### import the simple module from the paraview from paraview.simple import * # create a new 'ExodusIIReader' reader = ExodusIIReader(FileName=['C:\\Users\\John\\Desktop\\download\\V_171_V_d_2_um_phi_4.50_eV_tOn_0.5_ns.e']) reader.GenerateObjectIdCellArray = 1 reader.GenerateGlobalElementIdArray = 1 reader.ElementVariables = reader.ElementVariables.Available reader.PointVariables = reader.PointVariables.Available reader.ElementBlocks = reader.ElementBlocks.Available reader.ApplyDisplacements = 1 reader.DisplacementMagnitude = 1.0 # get animation scene animationScene1 = GetAnimationScene() # update animation scene based on data timesteps animationScene1.UpdateAnimationUsingDataTimeSteps() # create a new 'Integrate Variables' integrateVariables1 = IntegrateVariables(Input=reader) Then, in the trace, the next important line output is plotSelectionOverTime1 = PlotSelectionOverTime(Input=integrateVariables1, Selection=None) But whereas in the GUI, it integrates over space for all time steps, this doesn't create any data. I'm assuming the problem is related to "Selection=None" but I cannot figure out how to select the data or a different function I could use. Any advice? John -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 6 17:10:28 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Mar 2017 17:10:28 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: BTW, do you have Dell Backup and Recovery tools installed? There's a known issue with Qt 5 and DBaR. You may want to update the DBaR tools to the latest version, if possible. On Thu, Mar 2, 2017 at 9:45 AM, Utkarsh Ayachit wrote: > Any way you can figure out your GPU & drivers/version etc? > > On Thu, Mar 2, 2017 at 8:15 AM, Mahmud Hasan wrote: > >> Utkarsh, >> Thank you for your email and contact. I am trying to download two >> versions (version 5.3.0-R2 which is available in the Paraview website as >> well as version 5.1.2 from BlueCFD-Core), however none is opening. I am >> sending screen shot of my computer configurations below. Please let me know >> if you have any more question. >> >> >> >> >> [image: Inline image 1] >> >> >> >> Thank you. Have a nice day. >> >> Regards-- >> Hasan >> >> >> >> >> >> On Thu, Mar 2, 2017 at 7:07 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Also, what version of ParaView are you using? >>> >>> On Thu, Mar 2, 2017 at 8:06 AM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> Can you share details about your system? What's the GPU? Are the >>>> drivers up-to-date? >>>> >>>> Utkarsh >>>> >>>> On Thu, Mar 2, 2017 at 12:00 AM, Mahmud Hasan >>>> wrote: >>>> >>>>> Dear Sir/Madam, >>>>> Good day. I have downloaded Paraview, however it is not opening. >>>>> Every time it is giving error message "paraveiw.exe has stopped working". I >>>>> am attaching the screenshot for your information. Would you please let me >>>>> know what to do. >>>>> >>>>> >>>>> >>>>> >>>>> [image: Inline image 1] >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Thank you. Have a nice day. >>>>> >>>>> Regards-- >>>>> Hasan >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67283 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 116082 bytes Desc: not available URL: From alex.razoumov at westgrid.ca Mon Mar 6 19:14:57 2017 From: alex.razoumov at westgrid.ca (alex razoumov) Date: Mon, 6 Mar 2017 16:14:57 -0800 Subject: [Paraview] ParaViewWeb in 5.2 Message-ID: Hello, I am compiling ParaView-5.2.0 for offscreen rendering and ParaViewWeb on an Ubuntu 16.04.2 VM with: -DPARAVIEW_ENABLE_PYTHON=ON \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DVTK_OPENGL_HAS_OSMESA=ON \ -DVTK_USE_OFFSCREEN=ON \ -DVTK_USE_X=OFF \ -DPARAVIEW_ENABLE_WEB=ON \ but the resulting build does not include ParaViewWeb: $ ls paraview/share/ cmake and there is no pvw-visualizer.py anywhere. Am I missing something? Thank you, -- Alex Razoumov -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Mon Mar 6 19:28:32 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 6 Mar 2017 17:28:32 -0700 Subject: [Paraview] ParaViewWeb in 5.2 In-Reply-To: References: Message-ID: What you are seeing is expected. The Web (JS+HTML) part of ParaView has been externalized inside its own repo. But based on what you've done, you've properly build ParaView and the Python side of it that is required for the Web component to work. ParaView super build for instance will download visualizer from ( https://github.com/Kitware/visualizer) and bundle it in our distribution. So what you are missing is the "dist" directory from the repo above (which correspond to the www directory) and the "server" directory that contains the python script that should be run inside pvpython. Let me know if you need more guidance. Seb On Mon, Mar 6, 2017 at 5:14 PM, alex razoumov wrote: > Hello, > > I am compiling ParaView-5.2.0 for offscreen rendering and ParaViewWeb on > an Ubuntu 16.04.2 VM with: > > -DPARAVIEW_ENABLE_PYTHON=ON \ > -DPARAVIEW_BUILD_QT_GUI=OFF \ > -DVTK_OPENGL_HAS_OSMESA=ON \ > -DVTK_USE_OFFSCREEN=ON \ > -DVTK_USE_X=OFF \ > -DPARAVIEW_ENABLE_WEB=ON \ > > but the resulting build does not include ParaViewWeb: > > $ ls paraview/share/ > cmake > > and there is no pvw-visualizer.py anywhere. Am I missing something? > > Thank you, > > -- > > Alex Razoumov > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 6 21:36:50 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Mar 2017 21:36:50 -0500 Subject: [Paraview] How to save a high-resolution image that contains a selected region of the viewport? In-Reply-To: <1aace45.2524.15aa63f40fc.Coremail.yzhzhang@ipe.ac.cn> References: <15c95ef.1675.15a70146209.Coremail.yzhzhang@ipe.ac.cn> <1aace45.2524.15aa63f40fc.Coremail.yzhzhang@ipe.ac.cn> Message-ID: Great! Glad that worked. On Mon, Mar 6, 2017 at 7:50 PM, ??? wrote: > > Hi Utkarsh? > > Thank you! I've gotten the ideal images in the way you said. > > Sincerely > -Zhang >> -----????----- >> ???: "Utkarsh Ayachit" >> ????: 2017?3?7? ??? >> ???: "???" >> ??: ParaView >> ??: Re: [Paraview] How to save a high-resolution image that contains a >> selected region of the viewport? > >> >> Zhang, >> >> Since you're most likely changing the aspect ratio quite dramatically, >> I'd suggest the following: >> 1. explicitly setting the current view size to have an aspect ratio >> comparable to the target, but keep the resolution smaller than what's >> available on your display. You can use "Tools | Lock View Size To >> Custom". >> 2. then, adjust the scene as appropriate to view the data optimally. >> 3. now try saving the screenshot of the resolution of interest. >> >> Utkarsh >> >> On Fri, Feb 24, 2017 at 7:24 AM, ??? wrote: >> > >> > Hello, >> > >> > I'm using paraview 5.2.0 to render a relatively large dataset. In the >> > simulated region, the Z direction is much larger than that of X and Y. I >> > want to save a high-resolution image that contains the whole simulation >> > region, but no other regions. However, by only specifying a relatively >> > high >> > resolution, like 2,000*50,000, in the Save Screenshot Options dialog, I >> > got >> > an image that mainly contains the background, not the simulation region. >> > I >> > wonder if I can select the region that I want to save and specify a high >> > resolution to get the details in the region and then save it as an >> > image? >> > >> > Thanks! >> > -Zhang >> > >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > > From l.rabbit.88 at gmail.com Mon Mar 6 21:40:53 2017 From: l.rabbit.88 at gmail.com (John) Date: Mon, 6 Mar 2017 21:40:53 -0500 Subject: [Paraview] pvpython, get data over time In-Reply-To: References: Message-ID: Hi All, I found an older post that used the SelectPoints/SelectCells methods. However, even with "OnlyReportSelectionStatistics = 0" I still am getting min, q1, med, q3, max, avg, std. My script is attached. On Mon, Mar 6, 2017 at 4:11 PM, John wrote: > Hello all, > > I'm trying to collect data over time. Using as a > > #### import the simple module from the paraview > from paraview.simple import * > > # create a new 'ExodusIIReader' > reader = ExodusIIReader(FileName=['C:\\Users\\John\\Desktop\\ > download\\V_171_V_d_2_um_phi_4.50_eV_tOn_0.5_ns.e']) > reader.GenerateObjectIdCellArray = 1 > reader.GenerateGlobalElementIdArray = 1 > reader.ElementVariables = reader.ElementVariables.Available > reader.PointVariables = reader.PointVariables.Available > reader.ElementBlocks = reader.ElementBlocks.Available > reader.ApplyDisplacements = 1 > reader.DisplacementMagnitude = 1.0 > > # get animation scene > animationScene1 = GetAnimationScene() > > # update animation scene based on data timesteps > animationScene1.UpdateAnimationUsingDataTimeSteps() > > # create a new 'Integrate Variables' > integrateVariables1 = IntegrateVariables(Input=reader) > > Then, in the trace, the next important line output is > > plotSelectionOverTime1 = PlotSelectionOverTime(Input=integrateVariables1, > Selection=None) > > > But whereas in the GUI, it integrates over space for all time steps, this > doesn't create any data. I'm assuming the problem is related to > "Selection=None" but I cannot figure out how to select the data or a > different function I could use. > > Any advice? > > John > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: script.py Type: application/octet-stream Size: 2265 bytes Desc: not available URL: From fabidi89 at vt.edu Tue Mar 7 00:42:13 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 7 Mar 2017 00:42:13 -0500 Subject: [Paraview] CSV to PVTU In-Reply-To: References: Message-ID: You are right about v4.0.1. Though it creates 8 vtu files, only the first one contains all the points while the other seven are empty. And yes, changing the Masking to All Points worked. Thanks again for your help! P.S. I was reading THIS paper and realized you were one of the authors. Nice read. On Mon, Mar 6, 2017 at 1:18 PM, Moreland, Kenneth wrote: > Sorry, I might have mislead you a little bit before. What you actually > need is the Glyph filter with Glyph Type set to 2D Glyph and then the > secondary Glyph Type set to Vertex. > > > > By default the glyph filter subsamples the data (to prevent occlusion when > creating glyphs with size). Under Masking change the Glyph Mode to All > Points, and you should get what you want. > > > > Also, check the vtu files being generated by ParaView 4.0.1 carefully. I > suspect one of them is very large and all the others are very small. I > think the old version of ParaView is writing a bunch of vtu files with no > points whereas new versions of ParaView are not writing out pointless empty > vtu files. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Sunday, March 5, 2017 4:09 PM > > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* Re: [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Btw, I am a bit confused that why after applying a "2D Glyph" filter and > "Glyph Type" as "Vertex", the number of points decreases. For example, if > after applying "TableToPoints" filter I have 1 cell and 100k points, I get > 502 cells and 502 points after applying a "2D Glyph" filter. I was > expecting the number of cells to increase but total number of points should > have remained 100k, no? > > > > I am not really sure if applying a 2D Glyph is the best solution in my > case. I may go back to using 4.0.1 to convert this csv data into pvtu and > then use the latest version to load it up. > > > > On Fri, Mar 3, 2017 at 2:14 PM, Faiz Abidi wrote: > > I see. > > > I did that because when I choose "Assign Cells Uniquely" as the "Boundary > Mode" in the D3 filter, I was getting a warning like below: > > Warning: In /home/faiz89/git/ParaView/VTK/Common/DataModel/vtkKdTree.cxx, > line 1887 > vtkKdTree (0x2db5950): vtkKdTree::BuildMapForDuplicatePoints - invalid > tolerance > > > > But in spite of the warning, 8 vtu files get generated along with 1 pvtu > file. So, maybe that warning can be ignored. > > > > On Thu, Mar 2, 2017 at 6:42 PM, Moreland, Kenneth > wrote: > > I?m pretty sure if you select Duplicate Cells it will just copy all the > points to all processes, so that is not a good option. The divide cells is > also giving poor results on this front. I think you are better off using > the 2D Glyph filter to break up the cell first. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Thursday, March 2, 2017 2:44 PM > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* Re: [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Ohk, that makes more sense. I could get it to work as well but also had to > check "Boundary Mode" as "Duplicate Cells" while applying the D3 filter. > > > > Thanks Moreland! > > > > On Thu, Mar 2, 2017 at 3:59 PM, Moreland, Kenneth > wrote: > > Faiz, > > > > I was able to replicate your problem. It looks like it is not an issue > with D3 but a change with how Table to Points creates data (or perhaps how > data are written). It looks like Table to Points is creating one ?cell? > with a lot of points. This saves a little memory but ends up preventing D3 > from dividing the points up. > > > > The best solution is to add a ?2D Glyph? filter after the Table to Points > but before the D3 filter. Set the ?Glyph Type? to ?Vertex?. Then apply the > D3 filter to the output of the 2D Glyph filter. > > > > -Ken > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Thursday, March 2, 2017 1:38 PM > *To:* Moreland, Kenneth > *Cc:* ParaView ; Rajamohan, Srijith < > srijithr at vt.edu>; Nicholas Polys ; Ayat Mohammed < > maaayat at vt.edu> > *Subject:* [EXTERNAL] Re: [Paraview] CSV to PVTU > > > > Hi Moreland, > > > > Thanks for your reply. > > > > I thought same except maybe not use the GUI since my data is big and takes > forever to load up in Paraview. > > > > Quick question/observation - using the GUI and 8 processes, and applying > the Tables to Points filter + D3 and then trying to save files doesn't > create 8 vtu files and 1 pvtu file as expected. Instead, what happens is > that I get only 1 pvtu file along with 1 vtu file instead. Clearly > something wrong. This was done using v5.2.0. > > > > I tried the same thing using v4.0.1 (yes, old but it works!) and I got 8 > vtu files and 1 pvtu file as expected. > > > > Do you think this is a bug with 5.2.0? Or do I need to do something > different with 5.2.0? Any pointers appreciated! > > > > On Wed, Mar 1, 2017 at 4:15 PM, Moreland, Kenneth > wrote: > > You can use ParaView itself to read in the csv file, convert it to an > unstructured grid (Table to Points filter), redistributed on your 8 > parallel processors (D3 filter) and then write out a pvtu file. > > > > Offhand I cannot think of an easier way. > > > > -Ken > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Faiz > Abidi > *Sent:* Wednesday, March 1, 2017 2:03 PM > *To:* ParaView > *Subject:* [EXTERNAL] [Paraview] CSV to PVTU > > > > Hi again community! > > > > Looking for suggestions - what would be a decently fast way to convert a > huge CSV file into PVTU files? > > > > What I want to do - load this huge file in a CAVE like environment, and > use 8 parallel processors. > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > > > > > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Tue Mar 7 09:17:32 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 7 Mar 2017 14:17:32 +0000 Subject: [Paraview] Maintain triangulation of slive from vtk to numpy In-Reply-To: References: Message-ID: Kyle, Once you get a slice, you can extract the underlying vtkUnstructuredGrid and use that to extract the connectivity. For example: uns_grid = servermanager.Fetch(slice) npts = uns_grid.GetNumberOfCells() for n in xrange(npts): ptids = vtk.vtkIdList() uns_grid.GetCellPoints(0, ptids) print [ptids.GetId(i) for i in xrange(ptids.GetNumberOfIds())] And you can interchange the words Point and Cell to get the inverse information (all of the cells using a given point). I tried playing around with something along the lines of: uns_grid.BuildLinks() links = uns_grid.GetCellLinks() npts = uns_grid.GetNumberOfPoints() for i in xrange(npts) print links.GetCells(i) but GetCells returns a vtkIdType pointer, which in Python shows up as a string containing an address in memory. I couldn't figure out how to translate that back into something meaningful. Tim ________________________________ From: ParaView on behalf of Schau, Kyle A Sent: Wednesday, March 1, 2017 12:35 PM To: paraview at paraview.org Subject: [Paraview] Maintain triangulation of slive from vtk to numpy Hello All Does anyone know if the capability exists to extract slice data through the python interface of paraview that contains the triangulation data of the slice? This would allow one to pull flattened VTK data in the form of numpy arrays, but still plot non-convex slice geometries easily with mayplotlib.tricont() Thanks for your help. Kyle A. Schau Graduate Research Assistant Computational Combustion Lab Georgia Institute of Technology Atlanta, GA (269)-986-4579 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Tue Mar 7 10:15:28 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Tue, 7 Mar 2017 18:15:28 +0300 Subject: [Paraview] Axes Grid Message-ID: Hello, Under certain angles axes grid behaves like this(or just disappears):[image: ?????????? ??????????? 2] Is it a bug? Best Regards, Rustem Khabetdinov. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 65237 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Mar 7 10:17:16 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Mar 2017 10:17:16 -0500 Subject: [Paraview] Axes Grid In-Reply-To: References: Message-ID: Yup, it's indeed a bug. Please report it with steps to reproduce (or state file) on the bug tracker: https://gitlab.kitware.com/paraview/paraview/issues Thanks Utkarsh On Tue, Mar 7, 2017 at 10:15 AM, Rustem Khabetdinov < rustem.khabetdinov at gmail.com> wrote: > Hello, > Under certain angles axes grid behaves like this(or just disappears):[image: > ?????????? ??????????? 2] > Is it a bug? > > Best Regards, > Rustem Khabetdinov. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 65237 bytes Desc: not available URL: From daviddoria at gmail.com Tue Mar 7 10:22:37 2017 From: daviddoria at gmail.com (David Doria) Date: Tue, 7 Mar 2017 09:22:37 -0600 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: On Mon, Mar 6, 2017 at 11:14 AM, Andy Bauer wrote: > Thanks for the bug report! > > I think the stackoverflow issue is probably also related to blanking. I > added to your bug report with two other (likely) related issues. > > As a side note, I think if blanking was used instead of ghost cells this > may work properly. > > Thanks, > Andy > > On Mon, Mar 6, 2017 at 8:45 AM, David Doria wrote: > >> On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer >> wrote: >> >>> Hi David, >>> >>> This looks like it has to do with blanking (i.e. in PV 5.2 if I don't >>> load the vtkGhostType array it has the proper bounds). Would you mind >>> putting in a bug report on Gitlab (https://gitlab.kitware.com/pa >>> raview/paraview)? >>> >>> Thanks, >>> Andy >>> >> >> Done: >> https://gitlab.kitware.com/paraview/paraview/issues/17244 >> >> Here is another presumed bug that seems to also have to do with blanking: >> http://stackoverflow.com/questions/42543340/cell- >> labels-in-selection-display-inspector-dont-work-when-any- >> cells-are-ghosted - not trying to pollute this thread but do you think >> that behavior could be helpful to understand the Cell Centers issue? >> >> Thanks, >> >> David >> > > Hi Andy, The file was created with something like this: https://gist.github.com/daviddoria/8bf981aa593b7cefcd9114588e4766db Does calling structuredGrid->BlankPoint(0); not count as "using blanking"? Can you point me to the "right way" to do this if this is not the current best practice? Thanks! David -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 7 10:29:17 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Mar 2017 10:29:17 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: On Mon, Mar 6, 2017 at 11:28 PM, Mahmud Hasan wrote: > Mr. Utkarsh, > ...Yes, I have Dell laptop. > > Mahmud, if you have "Dell Backup and Recovery" tools installed, you'll need to either remove them or update them to the latest version due a known issue. See this for details: http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253 Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: From yves.rogez at univ-grenoble-alpes.fr Tue Mar 7 10:29:34 2017 From: yves.rogez at univ-grenoble-alpes.fr (Yves Rogez) Date: Tue, 7 Mar 2017 16:29:34 +0100 Subject: [Paraview] Making a package for Nix system In-Reply-To: References: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> <3f314df6-9623-6396-7be3-b3929f8d2164@univ-grenoble-alpes.fr> Message-ID: <1646caac-7ccb-4110-a6fc-97c87356dc9e@univ-grenoble-alpes.fr> Hi Mathieu, for info, here is the backtrace for the PV5.2 bug with seg fault when disconnecting (sorry it was stuck in my draft e-mails since a while :-). I did not find the time to rebuild with the last version. I will try to do so soon... I think I have to rebuild it from source as the basic goal is to package it on nix system (which uses internal nix package dependencies). I currently use 5.3 RC2 for my developments and it works completely fine on any system (not including nix :-). Bye, Yves Le 10/02/2017 ? 15:14, Mathieu Westphal a ?crit : > Hi Yves > > In order to test with the last version, you do not need to compile, > you can download a nightly build on the ParaView download page. > (Highest number means newer). > Let me know how it goes. > > I will defer to others regarding the packaging question. > > > Mathieu Westphal > > On Fri, Feb 10, 2017 at 9:44 AM, Yves Rogez > > wrote: > > Hi Mathieu :-) > > yes it's for the case of multi-server (actually single client) > option. I will get the source from the git repository master a > give it another try. > > OK for the debug, I can compile it again in debug but it takes a > long time on my little test laptop so I was wondering maybe some > other tricky test on the release version ;-) I will let the debug > build run this week-end and send a quick report. > > By the way, do you plan to support nix packages build in the > future for Paraview ? The problem I will encounter now is that > Paraview depends on video card driver OpenGL libs so that to get > good performances, I will break the nix packages philosophy of > being independent from the operating system specific kernel... > > Thanks for the answer! > > Yves > > > Le 10/02/2017 ? 03:48, Mathieu Westphal a ?crit : >> Hi Yves ! >> >> Do you happen to use the multi-clients/multi-server option ? we >> recently corrected a bug that sound like yours, will be fixed in >> ParaView 5.3. >> In any case, you may want to try with the last version of >> paraview master. >> >> In order to debug, the first step would be to build ParaView in >> Debug, and then run it with a debuger, in order to get a >> backtrace of the segfault. >> >> Best Regards, >> >> Mathieu Westphal >> >> On Thu, Feb 9, 2017 at 6:09 PM, Yves Rogez >> > > wrote: >> >> Dear Paraview team, >> >> we are currently studying the opportunity of migrating our >> computing grid environment from "module" system to "nix" >> packaging system (https://nixos.org/). In that purpose, I'm >> trying to compile and pack Paraview 5.2.0 with its >> dependencies with nix packages >> (https://nixos.org/nixos/packages.html >> ). >> >> To do so, I first installed nixos on a local laptop and give >> it a try. The main issue I encountered was to update my nixos >> kernel with native videocard drivers but OK, that's done. >> Then using the attached nix package script (a slight >> evolution on paraview 4.0.1 existing one), I could have >> packetized 5.2.0 succesfully and it runs very well. >> >> However, I still get an error when I'm trying to use MPI >> functionality. The MPI itself with parallelism works, as I >> can run a auto-MPI session without problem. The issue occurs >> when *servermanager.Disconnect() function is called => Seg >> fault* with no more info... The bad thing is that the >> Disconnect function is called every time I would like to >> connect to a server (to disconnect the built-in one). This is >> also the case when passing the pvserver in command-line argument. >> >> Do you have an idea of the cause of this seg fault ? Maybe >> could you help me find any useful test to debug this ? >> >> Thanks in advance for your support, >> >> Best regards, >> >> Yves >> >> >> -- >> Yves Rogez >> >> *IPAG* >> /Institut de Plan?tologie et d'Astrophysique de Grenoble / >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > > -- > Yves Rogez > > *IPAG* > /Institut de Plan?tologie et d'Astrophysique de Grenoble / > Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE > > tel : +33 (0)4 76 63 52 80 > lab : +33 (0)4 76 63 57 60 > > -- Yves Rogez *IPAG* /Institut de Plan?tologie et d'Astrophysique de Grenoble / Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE tel : +33 (0)4 76 63 52 80 lab : +33 (0)4 76 63 57 60 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- #0 0x00007fffeb7de320 in classify_object_over_fdes () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #1 0x00007fffeb7de829 in search_object () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #2 0x00007fffeb7df0c2 in _Unwind_Find_FDE () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #3 0x00007fffeb7dbb16 in uw_frame_state_for () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #4 0x00007fffeb7dcd60 in uw_init_context_1 () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #5 0x00007fffeb7dd22e in _Unwind_RaiseException () from /nix/store/kk71vkqipf30qc165718jmp0s8cggn2y-glibc-2.24/lib64/libgcc_s.so.1 #6 0x00007fffebd72f5b in __cxa_throw () from /nix/store/jar52969wyf10sh2wj62ipfjiw7xaq2j-gcc-5.4.0-lib/lib/libstdc++.so.6 #7 0x00007ffff65e863e in pqFindDataSelectionDisplayFrame::setView(pqView*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqComponents-pv5.2.so.1 #8 0x00007ffff264d2f0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #9 0x00007ffff672f5a2 in pqActiveObjects::viewChanged(pqView*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqComponents-pv5.2.so.1 #10 0x00007ffff6558eee in pqActiveObjects::triggerSignals() () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqComponents-pv5.2.so.1 #11 0x00007ffff264d2f0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #12 0x00007ffff5fea402 in pqServerManagerModel::preItemRemoved(pqServerManagerModelItem*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #13 0x00007ffff5fb3a51 in pqServerManagerModel::onProxyUnRegistered(QString const&, QString const&, vtkSMProxy*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #14 0x00007ffff264d2f0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #15 0x00007ffff5feb53c in pqServerManagerObserver::proxyUnRegistered(QString const&, QString const&, vtkSMProxy*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #16 0x00007ffff5fb7845 in pqServerManagerObserver::proxyUnRegistered(vtkObject*, unsigned long, void*, void*, vtkCommand*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #17 0x00007ffff5feb94b in pqServerManagerObserver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #18 0x00007ffff264d2f0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #19 0x00007ffff2d37925 in vtkQtConnection::EmitExecute(vtkObject*, unsigned long, void*, void*, vtkCommand*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkGUISupportQt-pv5.2.so.1 #20 0x00007ffff2d14a33 in vtkQtConnection::Execute(vtkObject*, unsigned long, void*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkGUISupportQt-pv5.2.so.1 #21 0x00007fffec574ab9 in vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkCommonCore-pv5.2.so.1 #22 0x00007fffec606439 in vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkCommonCore-pv5.2.so.1 #23 0x00007ffff3da39a3 in vtkSMSessionProxyManager::UnRegisterProxy(char const*, char const*, vtkSMProxy*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkPVServerManagerCore-pv5.2.so.1 #24 0x00007ffff3da4006 in vtkSMSessionProxyManager::UnRegisterProxies() () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkPVServerManagerCore-pv5.2.so.1 #25 0x00007ffff3d96589 in vtkSMSession::Disconnect(vtkSMSession*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkPVServerManagerCore-pv5.2.so.1 #26 0x00007ffff3d96762 in vtkSMSession::Disconnect(long long) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkPVServerManagerCore-pv5.2.so.1 #27 0x00007ffff5f6f0a2 in pqObjectBuilder::removeServer(pqServer*) () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqCore-pv5.2.so.1 #28 0x00007ffff7ae137a in pqServerDisconnectReaction::disconnectFromServerWithWarning() () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqApplicationComponents-pv5.2.so.1 #29 0x00007ffff7ae1584 in pqServerDisconnectReaction::onTriggered() () from /nix/store/vjyv0zvh3jglspi9n9xw4pd6359bnm6s-paraview-5.2.0/lib/paraview-5.2/libvtkpqApplicationComponents-pv5.2.so.1 #30 0x00007ffff264d2f0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #31 0x00007ffff6e95de2 in QAction::triggered(bool) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #32 0x00007ffff6e97153 in QAction::activate(QAction::ActionEvent) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #33 0x00007ffff72514f3 in ?? () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #34 0x00007ffff7251644 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #35 0x00007ffff73174ba in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #36 0x00007ffff6ef22a0 in QWidget::event(QEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #37 0x00007ffff6e9bdbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #38 0x00007ffff6ea2dd6 in QApplication::notify(QObject*, QEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #39 0x00007ffff263932d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #40 0x00007ffff6ea23dd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #41 0x00007ffff6f1c422 in ?? () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #42 0x00007ffff6f1adfd in QApplication::x11ProcessEvent(_XEvent*) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #43 0x00007ffff6f43e92 in ?? () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #44 0x00007fffdf3d2d47 in g_main_context_dispatch () from /nix/store/sn1qh8arj193gpxxl6s3gw6hvh4277ks-glib-2.50.2/lib/libglib-2.0.so.0 #45 0x00007fffdf3d2fa0 in g_main_context_iterate.isra () from /nix/store/sn1qh8arj193gpxxl6s3gw6hvh4277ks-glib-2.50.2/lib/libglib-2.0.so.0 #46 0x00007fffdf3d304c in g_main_context_iteration () from /nix/store/sn1qh8arj193gpxxl6s3gw6hvh4277ks-glib-2.50.2/lib/libglib-2.0.so.0 #47 0x00007ffff26694c4 in QEventDispatcherGlib::processEvents(QFlags) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #48 0x00007ffff6f43f66 in ?? () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtGui.so.4 #49 0x00007ffff2637ba1 in QEventLoop::processEvents(QFlags) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #50 0x00007ffff2637f15 in QEventLoop::exec(QFlags) () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #51 0x00007ffff263d899 in QCoreApplication::exec() () from /nix/store/hw18dgxdq6c2bls5n3ffbmwxzn0m0c80-qt-4.8.7/lib/libQtCore.so.4 #52 0x0000000000407d01 in main () From mathieu.westphal at kitware.com Tue Mar 7 11:08:17 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 7 Mar 2017 17:08:17 +0100 Subject: [Paraview] Making a package for Nix system In-Reply-To: <1646caac-7ccb-4110-a6fc-97c87356dc9e@univ-grenoble-alpes.fr> References: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> <3f314df6-9623-6396-7be3-b3929f8d2164@univ-grenoble-alpes.fr> <1646caac-7ccb-4110-a6fc-97c87356dc9e@univ-grenoble-alpes.fr> Message-ID: Hi Without debug symbols, we can't really use the backtrace. Regarding 5.3 version, are you saying that it does not have the segfault ? Mathieu Westphal On Tue, Mar 7, 2017 at 4:29 PM, Yves Rogez < yves.rogez at univ-grenoble-alpes.fr> wrote: > Hi Mathieu, > > for info, here is the backtrace for the PV5.2 bug with seg fault when > disconnecting (sorry it was stuck in my draft e-mails since a while :-). > > I did not find the time to rebuild with the last version. I will try to do > so soon... I think I have to rebuild it from source as the basic goal is to > package it on nix system (which uses internal nix package dependencies). I > currently use 5.3 RC2 for my developments and it works completely fine on > any system (not including nix :-). > > Bye, > > Yves > > Le 10/02/2017 ? 15:14, Mathieu Westphal a ?crit : > > Hi Yves > > In order to test with the last version, you do not need to compile, you > can download a nightly build on the ParaView download page. > (Highest number means newer). > Let me know how it goes. > > I will defer to others regarding the packaging question. > > > Mathieu Westphal > > On Fri, Feb 10, 2017 at 9:44 AM, Yves Rogez alpes.fr> wrote: > >> Hi Mathieu :-) >> >> yes it's for the case of multi-server (actually single client) option. I >> will get the source from the git repository master a give it another try. >> >> OK for the debug, I can compile it again in debug but it takes a long >> time on my little test laptop so I was wondering maybe some other tricky >> test on the release version ;-) I will let the debug build run this >> week-end and send a quick report. >> >> By the way, do you plan to support nix packages build in the future for >> Paraview ? The problem I will encounter now is that Paraview depends on >> video card driver OpenGL libs so that to get good performances, I will >> break the nix packages philosophy of being independent from the operating >> system specific kernel... >> >> Thanks for the answer! >> >> Yves >> >> Le 10/02/2017 ? 03:48, Mathieu Westphal a ?crit : >> >> Hi Yves ! >> >> Do you happen to use the multi-clients/multi-server option ? we recently >> corrected a bug that sound like yours, will be fixed in ParaView 5.3. >> In any case, you may want to try with the last version of paraview master. >> >> In order to debug, the first step would be to build ParaView in Debug, >> and then run it with a debuger, in order to get a backtrace of the segfault. >> >> Best Regards, >> >> Mathieu Westphal >> >> On Thu, Feb 9, 2017 at 6:09 PM, Yves Rogez > s.fr> wrote: >> >>> Dear Paraview team, >>> >>> we are currently studying the opportunity of migrating our computing >>> grid environment from "module" system to "nix" packaging system ( >>> https://nixos.org/). In that purpose, I'm trying to compile and pack >>> Paraview 5.2.0 with its dependencies with nix packages ( >>> https://nixos.org/nixos/packages.html). >>> >>> To do so, I first installed nixos on a local laptop and give it a try. >>> The main issue I encountered was to update my nixos kernel with native >>> videocard drivers but OK, that's done. Then using the attached nix package >>> script (a slight evolution on paraview 4.0.1 existing one), I could have >>> packetized 5.2.0 succesfully and it runs very well. >>> >>> However, I still get an error when I'm trying to use MPI functionality. >>> The MPI itself with parallelism works, as I can run a auto-MPI session >>> without problem. The issue occurs when *servermanager.Disconnect() >>> function is called => Seg fault* with no more info... The bad thing is >>> that the Disconnect function is called every time I would like to connect >>> to a server (to disconnect the built-in one). This is also the case when >>> passing the pvserver in command-line argument. >>> >>> Do you have an idea of the cause of this seg fault ? Maybe could you >>> help me find any useful test to debug this ? >>> >>> Thanks in advance for your support, >>> >>> Best regards, >>> >>> Yves >>> >>> -- >>> Yves Rogez >>> >>> *IPAG* >>> *Institut de Plan?tologie et d'Astrophysique de Grenoble * >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> -- >> Yves Rogez >> >> *IPAG* >> *Institut de Plan?tologie et d'Astrophysique de Grenoble * >> Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE >> >> tel : +33 (0)4 76 63 52 80 <+33%204%2076%2063%2052%2080> >> lab : +33 (0)4 76 63 57 60 <+33%204%2076%2063%2057%2060> >> > > > -- > Yves Rogez > > *IPAG* > *Institut de Plan?tologie et d'Astrophysique de Grenoble * > Bat D de Physique - BP. 53 - 38041 Grenoble - FRANCE > > tel : +33 (0)4 76 63 52 80 <+33%204%2076%2063%2052%2080> > lab : +33 (0)4 76 63 57 60 <+33%204%2076%2063%2057%2060> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Tue Mar 7 11:36:41 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Tue, 7 Mar 2017 19:36:41 +0300 Subject: [Paraview] Programmable Filter/Source 5.3 RC2 Message-ID: Hello, When I try to type any non-latin symbols inside Script field I get this error: QTextCursor::setPosition: Position '1' out of range (:0, ) Previous versions did not have that issue. Best Regards, Rustem Khabetdinov. -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.rabbit.88 at gmail.com Tue Mar 7 13:43:12 2017 From: l.rabbit.88 at gmail.com (John) Date: Tue, 7 Mar 2017 13:43:12 -0500 Subject: [Paraview] OnlyReportSelectionStatistics not turning off statistics Message-ID: Hello Paraviewers, I'm trying to save a table to csv (similar to http://markmail.org/search/?q=ParaView+order%3Adate-backward+plotselectionovertime#query:ParaView%20order%3Adate-backward%20plotselectionovertime+page:3+mid:7k7wbaoz23uxhpgf+state:results ) However, even though I have "OnlyReportSelectionStatistics = 0", I am still getting statistics rather than values. Is this a bug or am I doing sometime wrong? I've attached a simple version of my script. Thank you, John -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: simplified.py Type: application/octet-stream Size: 1336 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Mar 7 14:57:30 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Mar 2017 14:57:30 -0500 Subject: [Paraview] OnlyReportSelectionStatistics not turning off statistics In-Reply-To: References: Message-ID: Currently, "PlotSelectionOverTime" can only generate summaries (aka OnlyReportSelectionStatistics=1) when the selection is query-based selection. The `simple.SelectCells` only creates query-based selection. Currently here's no clean way to create an id-based selection. Attached script directly create an ID-based selection source. Now, OnlyReportSelectionStatistics=0 works as expected. On Tue, Mar 7, 2017 at 1:43 PM, John wrote: > Hello Paraviewers, > > I'm trying to save a table to csv (similar to > http://markmail.org/search/?q=ParaView+order%3Adate-backward+plotselectionovertime#query:ParaView%20order%3Adate-backward%20plotselectionovertime+page:3+mid:7k7wbaoz23uxhpgf+state:results > ) > > However, even though I have "OnlyReportSelectionStatistics = 0", I am still > getting statistics rather than values. > > Is this a bug or am I doing sometime wrong? > > I've attached a simple version of my script. > > Thank you, > > John > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.py Type: text/x-python Size: 1092 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Mar 7 15:14:28 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Mar 2017 15:14:28 -0500 Subject: [Paraview] Paraveiw.exe has stopped working In-Reply-To: References: Message-ID: Mahmud, Please cc-ing the mailing list so that everyone can benefit from this discussion. Like I said in my previous emails, ParaView now uses Qt 5 and there's a known issues with Dell Backup & Recovery Tools and Qt 5 ( http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253). If you cannot upgrade on uninstall Dell Backup & Recovery software, then you may have to stick with using previous version of ParaView. If you do not have Dell Backup and Recovery Tools installed, then I am still at loss at what could be going on, since I can't reproduce this issue. So any more insight you can provide at that point, may help. Utkarsh On Tue, Mar 7, 2017 at 3:05 PM, Mahmud Hasan wrote: > Mr. Utkarsh, > I am using my office computer which is HP computer. I have installed > Paraview software (version 5.3.0-RC2) from the website to this computer. > This also shows error message. I am attaching those for your information. I > am wondering either Paraview has changed anything recently that is causing > so much of problems. I have downloaded Paraview 5.2 in another of my office > computer 3 months ago, that installed well and I was able to use the > software in that computer. I left that job, so I no longer use that > computer. I think something going wrong recently with Paraview software. > > > > > [image: Inline image 1] > > > [image: Inline image 2] > > > [image: Inline image 3] > > > > > > > > Thank you. Have a nice day. > > Regards-- > Hasan > > > > > On Tue, Mar 7, 2017 at 9:29 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> >> On Mon, Mar 6, 2017 at 11:28 PM, Mahmud Hasan wrote: >> >>> Mr. Utkarsh, >>> ...Yes, I have Dell laptop. >>> >>> >> Mahmud, if you have "Dell Backup and Recovery" tools installed, you'll >> need to either remove them or update them to the latest version due a known >> issue. >> See this for details: http://en.community.dell.com/s >> upport-forums/software-os/f/3526/t/19634253 >> >> Utkarsh >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 30840 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 34394 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 36990 bytes Desc: not available URL: From l.rabbit.88 at gmail.com Tue Mar 7 16:37:12 2017 From: l.rabbit.88 at gmail.com (John) Date: Tue, 7 Mar 2017 16:37:12 -0500 Subject: [Paraview] OnlyReportSelectionStatistics not turning off statistics In-Reply-To: References: Message-ID: Thank you. Is there a way to do something similar for points? Because I tried to just change "CELL" to "POINT" and it did not work. Regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Tue Mar 7 16:44:14 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Tue, 7 Mar 2017 16:44:14 -0500 Subject: [Paraview] Query on EGL libs for Paraview 5.0.1 In-Reply-To: References: Message-ID: Hi Bishwajit, I hate to be the bearer of bad news, but the K20c was a specific model of Tesla that is restricted to compute functionality only and is not capable of performing OpenGL functions via EGL. As such, it won't be usable by ParaView for rendering. Almost all other Teslas, including the other K20 models (K20m and K20x), can be switched into either compute-only, graphics-only, or both modes, but the K20c only has compute mode available. So even though you may get it building with the libraries in the folder Andy is pointing to, I don't believe you'll actually get a working EGL device. If you do, then fantastic, but don't get your hopes up :-/ - Chuck On Sun, Mar 5, 2017 at 7:09 PM, Andy Bauer wrote: > Hi, > > Maybe look in: > /usr/lib/nvidia- > > for the drivers -- that's where it is for my r367 NVIDIA drivers on > Ubuntu 16.04. Otherwise you may need to check with NVIDIA on where it gets > installed for your set of drivers and system. > > On Sat, Mar 4, 2017 at 10:19 PM, Bishwajit Dutta wrote: > >> Hi All, >> >> I am trying to compile Paraview 5.0.1 with EGL support as I want to use >> NVIDIA Tesla K20c >> for rendering in Ubuntu 14.04. This is without any windowing system as >> K20c is designed for >> server based rendering (without any VGA port and OpenGL support (I >> think!)) >> >> I went through >> >> https://blog.kitware.com/off-screen-rendering-through-the-na >> tive-platform-interface-egl/ >> >> and as I understand, for this I need to set the below Paraview flags >> before compilation: >> >> VTK_EGL_DEVICE_INDEX=set to graphics driver index >> VTK_USE_OFFSCREEN_EGL =on >> EGL_INCLUDE_DIR >> EGL_LIBRARY /usr/lib/x86_64-linux-gnu/libEGL.so >> EGL_gldispatch_LIBRARY /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 >> EGL_opengl_LIBRARY /usr/lib/x86_64-linux-gnu/libOpenGL.so >> >> My query is on gettting the correct libs i.e. libEGL.so, >> libGLdispatch.so.0 and libOpenGL.so. >> >> When I installed "NVIDIA-Linux-x86_64-375.26.run" these libs were not >> installed. >> >> Which is the right place to get them. I can see several links on internet >> search: >> >> https://github.com/NVIDIA/libglvnd/blob/master/README.md >> >> https://www.mesa3d.org/egl.html >> >> Which is the correct one >> >> Thanks in advance for help. >> >> BR, >> Bishwajit >> Virginia Tech >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 7 19:20:00 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 8 Mar 2017 00:20:00 +0000 Subject: [Paraview] [EXTERNAL] Re: 2d image tiling problem In-Reply-To: References: Message-ID: Thanks, this is exactly what I wanted. Will let you know what my user wants. Alan From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Sunday, March 5, 2017 9:53 AM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] 2d image tiling problem Alan, There are couple of options that could be work exploring. Let me know which you see is most appropriate and I can get you in touch with the appropriate folks. 1. GeoJS -- a web-based solution. Docs: https://github.com/OpenGeoscience/geojs Example: http://opengeoscience.github.io/geojs/examples/deepzoom/ Other examples: http://opengeoscience.github.io/geojs/examples/index.html 2. vtkMap -- a VTK-based solution which is currently being developed which also includes ParaView integration. Code: https://github.com/OpenGeoscience/vtkMap Utkarsh On Tue, Feb 28, 2017 at 2:57 PM, Scott, W Alan > wrote: Hi guys, I have a user that wants to visualize very large images (i.e., terrabyte size images). These images are composed of tiles or subimages, which are offset in the main image according to a metafile. Does Kitware have any tools for visualizing and manipulating large images? Thanks, Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From hero.jairaj at gmail.com Tue Mar 7 19:59:13 2017 From: hero.jairaj at gmail.com (JAIRAJ MATHUR) Date: Tue, 7 Mar 2017 18:59:13 -0600 Subject: [Paraview] Regarding creating high quality small size animations Message-ID: Dear all I am trying to export my animation, but want to keep the size small, and quality of the simulation good. How can I go about it? I tried to directly save in the avi format, but the quality is bad and size is too large. -- Jairaj Mathur, Mechanical Engineering Washington University in St Louis -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 7 20:15:38 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 8 Mar 2017 01:15:38 +0000 Subject: [Paraview] [EXTERNAL] Regarding creating high quality small size animations In-Reply-To: References: Message-ID: Save as a flipbook of .png?s. Then, post process this into any type of move files (.avi etc). Use a third party movie creating program, such as ffmpeg. I think vlc may also do it, but have never done so. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of JAIRAJ MATHUR Sent: Tuesday, March 7, 2017 5:59 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Regarding creating high quality small size animations Dear all I am trying to export my animation, but want to keep the size small, and quality of the simulation good. How can I go about it? I tried to directly save in the avi format, but the quality is bad and size is too large. -- Jairaj Mathur, Mechanical Engineering Washington University in St Louis -------------- next part -------------- An HTML attachment was scrubbed... URL: From hero.jairaj at gmail.com Tue Mar 7 20:20:39 2017 From: hero.jairaj at gmail.com (JAIRAJ MATHUR) Date: Tue, 7 Mar 2017 19:20:39 -0600 Subject: [Paraview] [EXTERNAL] Regarding creating high quality small size animations In-Reply-To: References: Message-ID: Hi Scott Thanks for your reply. Will PNG ensure the final movie size is small? Or is there something else that will determine the final size? Jairaj Mathur Mechanical Engineering Washington University in St Louis On Mar 7, 2017 7:16 PM, "Scott, W Alan" wrote: > Save as a flipbook of .png?s. Then, post process this into any type of > move files (.avi etc). Use a third party movie creating program, such as > ffmpeg. I think vlc may also do it, but have never done so. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *JAIRAJ > MATHUR > *Sent:* Tuesday, March 7, 2017 5:59 PM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Regarding creating high quality small > size animations > > > > Dear all > > > > I am trying to export my animation, but want to keep the size small, and > quality of the simulation good. How can I go about it? > > > > I tried to directly save in the avi format, but the quality is bad and > size is too large. > > > > -- > > Jairaj Mathur, > Mechanical Engineering > > Washington University in St Louis > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 7 21:03:39 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 8 Mar 2017 02:03:39 +0000 Subject: [Paraview] [EXTERNAL] Regarding creating high quality small size animations In-Reply-To: References: Message-ID: <8eb171cdfce441438286fc60a264f228@ES01AMSNLNT.srn.sandia.gov> As with most things in life, you have a balance. Generally speaking, for better quality, you will need larger movies. For smaller movies, you will have higher compression and poorer quality. And of course, the smaller the screen size, the smaller the resultant movie. So, you get to choose. .png is an intermediate file format or storage that you will use. I believe that when you make movies, the final file format (and movie size) is what will determine the movie size. Regarding .png?s, they are lossless compression. .jpg?s are lossy compression. Png?s lose no quality, jpg?s lose quality. From: JAIRAJ MATHUR [mailto:hero.jairaj at gmail.com] Sent: Tuesday, March 7, 2017 6:21 PM To: Scott, W Alan Cc: paraview at paraview.org Subject: RE: [EXTERNAL] [Paraview] Regarding creating high quality small size animations Hi Scott Thanks for your reply. Will PNG ensure the final movie size is small? Or is there something else that will determine the final size? Jairaj Mathur Mechanical Engineering Washington University in St Louis On Mar 7, 2017 7:16 PM, "Scott, W Alan" > wrote: Save as a flipbook of .png?s. Then, post process this into any type of move files (.avi etc). Use a third party movie creating program, such as ffmpeg. I think vlc may also do it, but have never done so. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of JAIRAJ MATHUR Sent: Tuesday, March 7, 2017 5:59 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Regarding creating high quality small size animations Dear all I am trying to export my animation, but want to keep the size small, and quality of the simulation good. How can I go about it? I tried to directly save in the avi format, but the quality is bad and size is too large. -- Jairaj Mathur, Mechanical Engineering Washington University in St Louis -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 7 21:10:48 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Mar 2017 21:10:48 -0500 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: Hi David, I'm not sure how it works with structured grids but with vtkUniformGrids (i.e. vtkImageData with blanking) the VTK readers and writers really just produce vtkImageData and the blanking is ignored. It may be the same with the XML structured grid files. My suggestion would be to look at the vtkImageDataToUniformGrid class in VTK and try doing a similar thing in ParaView using the Python Programmable filter. Cheers, Andy On Tue, Mar 7, 2017 at 10:22 AM, David Doria wrote: > On Mon, Mar 6, 2017 at 11:14 AM, Andy Bauer > wrote: > >> Thanks for the bug report! >> >> I think the stackoverflow issue is probably also related to blanking. I >> added to your bug report with two other (likely) related issues. >> >> As a side note, I think if blanking was used instead of ghost cells this >> may work properly. >> >> Thanks, >> Andy >> >> On Mon, Mar 6, 2017 at 8:45 AM, David Doria wrote: >> >>> On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer >>> wrote: >>> >>>> Hi David, >>>> >>>> This looks like it has to do with blanking (i.e. in PV 5.2 if I don't >>>> load the vtkGhostType array it has the proper bounds). Would you mind >>>> putting in a bug report on Gitlab (https://gitlab.kitware.com/pa >>>> raview/paraview)? >>>> >>>> Thanks, >>>> Andy >>>> >>> >>> Done: >>> https://gitlab.kitware.com/paraview/paraview/issues/17244 >>> >>> Here is another presumed bug that seems to also have to do with >>> blanking: http://stackoverflow.com/questions/42543340/cell-l >>> abels-in-selection-display-inspector-dont-work-when-any-cell >>> s-are-ghosted - not trying to pollute this thread but do you think that >>> behavior could be helpful to understand the Cell Centers issue? >>> >>> Thanks, >>> >>> David >>> >> >> > Hi Andy, > > The file was created with something like this: > > https://gist.github.com/daviddoria/8bf981aa593b7cefcd9114588e4766db > > Does calling > > structuredGrid->BlankPoint(0); > > not count as "using blanking"? Can you point me to the "right way" to do > this if this is not the current best practice? > > Thanks! > > David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipebordeu at gmail.com Wed Mar 8 02:08:04 2017 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Wed, 8 Mar 2017 08:08:04 +0100 Subject: [Paraview] [EXTERNAL] Regarding creating high quality small size animations In-Reply-To: <8eb171cdfce441438286fc60a264f228@ES01AMSNLNT.srn.sandia.gov> References: <8eb171cdfce441438286fc60a264f228@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi, I always have problems choosing the settings when doing videos (bitrate, framerate, resolution...). Now I make my videos in full resolution/no compression. And use my Google(YouTube) account to upload my video to my private space. YouTube will automatically recompress the video. And because the video belongs to me, I can download it. Et voil?. A video with a very good quality/size balance. Felipe Le 8 mars 2017 3:04 AM, "Scott, W Alan" a ?crit : > As with most things in life, you have a balance. Generally speaking, for > better quality, you will need larger movies. For smaller movies, you will > have higher compression and poorer quality. And of course, the smaller the > screen size, the smaller the resultant movie. So, you get to choose. > > > > .png is an intermediate file format or storage that you will use. I > believe that when you make movies, the final file format (and movie size) > is what will determine the movie size. > > > > Regarding .png?s, they are lossless compression. .jpg?s are lossy > compression. Png?s lose no quality, jpg?s lose quality. > > > > > > > > > > *From:* JAIRAJ MATHUR [mailto:hero.jairaj at gmail.com] > *Sent:* Tuesday, March 7, 2017 6:21 PM > *To:* Scott, W Alan > *Cc:* paraview at paraview.org > *Subject:* RE: [EXTERNAL] [Paraview] Regarding creating high quality > small size animations > > > > Hi Scott > > > > Thanks for your reply. Will PNG ensure the final movie size is small? Or > is there something else that will determine the final size? > > Jairaj Mathur > Mechanical Engineering > Washington University in St Louis > > > > On Mar 7, 2017 7:16 PM, "Scott, W Alan" wrote: > > Save as a flipbook of .png?s. Then, post process this into any type of > move files (.avi etc). Use a third party movie creating program, such as > ffmpeg. I think vlc may also do it, but have never done so. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *JAIRAJ > MATHUR > *Sent:* Tuesday, March 7, 2017 5:59 PM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Regarding creating high quality small > size animations > > > > Dear all > > > > I am trying to export my animation, but want to keep the size small, and > quality of the simulation good. How can I go about it? > > > > I tried to directly save in the avi format, but the quality is bad and > size is too large. > > > > -- > > Jairaj Mathur, > Mechanical Engineering > > Washington University in St Louis > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hero.jairaj at gmail.com Wed Mar 8 07:31:50 2017 From: hero.jairaj at gmail.com (JAIRAJ MATHUR) Date: Wed, 8 Mar 2017 06:31:50 -0600 Subject: [Paraview] [EXTERNAL] Regarding creating high quality small size animations In-Reply-To: References: <8eb171cdfce441438286fc60a264f228@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Felipe That is genius! Thanks for this! Does YouTube allow you to download in as low as 144p? Jairaj Mathur Mechanical Engineering Washington University in St Louis On Mar 8, 2017 1:08 AM, "Felipe Bordeu" wrote: Hi, I always have problems choosing the settings when doing videos (bitrate, framerate, resolution...). Now I make my videos in full resolution/no compression. And use my Google(YouTube) account to upload my video to my private space. YouTube will automatically recompress the video. And because the video belongs to me, I can download it. Et voil?. A video with a very good quality/size balance. Felipe Le 8 mars 2017 3:04 AM, "Scott, W Alan" a ?crit : > As with most things in life, you have a balance. Generally speaking, for > better quality, you will need larger movies. For smaller movies, you will > have higher compression and poorer quality. And of course, the smaller the > screen size, the smaller the resultant movie. So, you get to choose. > > > > .png is an intermediate file format or storage that you will use. I > believe that when you make movies, the final file format (and movie size) > is what will determine the movie size. > > > > Regarding .png?s, they are lossless compression. .jpg?s are lossy > compression. Png?s lose no quality, jpg?s lose quality. > > > > > > > > > > *From:* JAIRAJ MATHUR [mailto:hero.jairaj at gmail.com] > *Sent:* Tuesday, March 7, 2017 6:21 PM > *To:* Scott, W Alan > *Cc:* paraview at paraview.org > *Subject:* RE: [EXTERNAL] [Paraview] Regarding creating high quality > small size animations > > > > Hi Scott > > > > Thanks for your reply. Will PNG ensure the final movie size is small? Or > is there something else that will determine the final size? > > Jairaj Mathur > Mechanical Engineering > Washington University in St Louis > > > > On Mar 7, 2017 7:16 PM, "Scott, W Alan" wrote: > > Save as a flipbook of .png?s. Then, post process this into any type of > move files (.avi etc). Use a third party movie creating program, such as > ffmpeg. I think vlc may also do it, but have never done so. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *JAIRAJ > MATHUR > *Sent:* Tuesday, March 7, 2017 5:59 PM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Regarding creating high quality small > size animations > > > > Dear all > > > > I am trying to export my animation, but want to keep the size small, and > quality of the simulation good. How can I go about it? > > > > I tried to directly save in the avi format, but the quality is bad and > size is too large. > > > > -- > > Jairaj Mathur, > Mechanical Engineering > > Washington University in St Louis > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/ opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Wed Mar 8 08:28:59 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Wed, 8 Mar 2017 15:28:59 +0200 (EET) Subject: [Paraview] vector plot with multiblock dataset. possible bug or dataset issue? Message-ID: <64626.160.75.142.243.1488979739.squirrel@webmail.be.itu.edu.tr> Hi All, I have some weird observation with 5.3RC2 when i try to create visualisation of vector field that is coming from multiblock dataset (has 4x4 decomposition). The problem is that in the simple visualization pipeline such as Calculator -> Glyph, i could barely see or pick the boundaries of the individual blocks which is not good. Then i tried to add MergeBlocks filter just after Calculator and try to visualize data with Glyph. In this case, it fixes the boundary problem (at least it seems like that). But, when i play with the Glyph Mode property and change it such as Every Nth Point and set as 3 then i could again see the boundaries with flat vectors. I just wonder that is it a bug or related with the dataset itself? It was also exist in earlier versions of the PV such as 5.2. Anyway,a simple dataset and also the state to reproduce the problem can be retrieved from following link, https://www.dropbox.com/s/1chvdmehqzuslmj/vector_issue.tar.gz?dl=0 If anyone has any other multiblock dataset (with vector field) that could test the same pipeline, then it could be easy to find the source of the problem (PV or dataset itself). Thanks, Regards, --ufuk From daviddoria at gmail.com Wed Mar 8 09:20:57 2017 From: daviddoria at gmail.com (David Doria) Date: Wed, 8 Mar 2017 08:20:57 -0600 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: On Tue, Mar 7, 2017 at 8:10 PM, Andy Bauer wrote: > Hi David, > > I'm not sure how it works with structured grids but with vtkUniformGrids > (i.e. vtkImageData with blanking) the VTK readers and writers really just > produce vtkImageData and the blanking is ignored. It may be the same with > the XML structured grid files. My suggestion would be to look at the > vtkImageDataToUniformGrid class in VTK and try doing a similar thing in > ParaView using the Python Programmable filter. > > Cheers, > Andy > > On Tue, Mar 7, 2017 at 10:22 AM, David Doria wrote: > >> On Mon, Mar 6, 2017 at 11:14 AM, Andy Bauer >> wrote: >> >>> Thanks for the bug report! >>> >>> I think the stackoverflow issue is probably also related to blanking. I >>> added to your bug report with two other (likely) related issues. >>> >>> As a side note, I think if blanking was used instead of ghost cells this >>> may work properly. >>> >>> Thanks, >>> Andy >>> >>> On Mon, Mar 6, 2017 at 8:45 AM, David Doria >>> wrote: >>> >>>> On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer >>>> wrote: >>>> >>>>> Hi David, >>>>> >>>>> This looks like it has to do with blanking (i.e. in PV 5.2 if I don't >>>>> load the vtkGhostType array it has the proper bounds). Would you mind >>>>> putting in a bug report on Gitlab (https://gitlab.kitware.com/pa >>>>> raview/paraview)? >>>>> >>>>> Thanks, >>>>> Andy >>>>> >>>> >>>> Done: >>>> https://gitlab.kitware.com/paraview/paraview/issues/17244 >>>> >>>> Here is another presumed bug that seems to also have to do with >>>> blanking: http://stackoverflow.com/questions/42543340/cell-l >>>> abels-in-selection-display-inspector-dont-work-when-any-cell >>>> s-are-ghosted - not trying to pollute this thread but do you think >>>> that behavior could be helpful to understand the Cell Centers issue? >>>> >>>> Thanks, >>>> >>>> David >>>> >>> >>> >> Hi Andy, >> >> The file was created with something like this: >> >> https://gist.github.com/daviddoria/8bf981aa593b7cefcd9114588e4766db >> >> Does calling >> >> structuredGrid->BlankPoint(0); >> >> not count as "using blanking"? Can you point me to the "right way" to do >> this if this is not the current best practice? >> >> Thanks! >> >> David >> > > I created a uniform grid: https://gist.github.com/daviddoria/99fa99c52aa07ee78b7e7412e74d592f https://drive.google.com/open?id=0B8yIfGqnlfSoNTNKWWtua1pEUTA Using the vtkXMLImageDataWriter seemed to write the same type of vtkGhostType array (shown in the cell data in Paraview), but Paraview doesn't seem to respect the blanking - all 8 voxels are drawn. Any other ideas? David -------------- next part -------------- An HTML attachment was scrubbed... URL: 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] 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 mathieu.westphal at kitware.com Wed Mar 8 12:27:49 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 8 Mar 2017 18:27:49 +0100 Subject: [Paraview] Programmable Filter/Source 5.3 RC2 In-Reply-To: References: Message-ID: Hello This is indeed an issue , please add an issue in https://gitlab.kitware.com/paraview/paraview/issues Thanks Mathieu Westphal On Tue, Mar 7, 2017 at 5:36 PM, Rustem Khabetdinov < rustem.khabetdinov at gmail.com> wrote: > Hello, > > When I try to type any non-latin symbols inside Script field I get this > error: QTextCursor::setPosition: Position '1' out of range (:0, ) > Previous versions did not have that issue. > > Best Regards, > Rustem Khabetdinov. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.rabbit.88 at gmail.com Wed Mar 8 12:50:11 2017 From: l.rabbit.88 at gmail.com (John) Date: Wed, 8 Mar 2017 12:50:11 -0500 Subject: [Paraview] OnlyReportSelectionStatistics not turning off statistics In-Reply-To: References: Message-ID: Hi Paraviewers, I want to export tables as CSV for points. However, even with "OnlyReportSelectionStatistics = 0", I am still getting statistics rather than values. Utkarsh's fix for cells worked but, changing the FieldType from "CELL" to "POINT" throws an error. Is there a different method I can use? On Tue, Mar 7, 2017 at 4:37 PM, John wrote: > Thank you. Is there a way to do something similar for points? Because I > tried to just change "CELL" to "POINT" and it did not work. > > Regards, > > John > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: simplified2.py Type: application/octet-stream Size: 1555 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Mar 8 13:57:08 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 8 Mar 2017 13:57:08 -0500 Subject: [Paraview] OnlyReportSelectionStatistics not turning off statistics In-Reply-To: References: Message-ID: > Utkarsh's fix for cells worked but, changing the FieldType from "CELL" to > "POINT" throws an error. Is there a different method I can use? I am not sure what error you're getting `source.FieldType = "POINT"` worked just fine for me. From joseph.g.hennessey2.ctr at mail.mil Wed Mar 8 14:51:27 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Wed, 8 Mar 2017 19:51:27 +0000 Subject: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Hello, I am finding that the volume rendering is not working with OSPRay Renderer not working with ParaView 5.3.0-RC3. The volume render sample that I am testing looks fine when rendered with the default renderer, but when I switch to the OSPRay volume renderer, then nothing is shown. Has anyone managed to volume render data, using the OSPRay renderer with ParaView 5.3.0-RC3? 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 dave.demarle at kitware.com Wed Mar 8 15:02:14 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Mar 2017 15:02:14 -0500 Subject: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> Message-ID: Wavelet->Volume Works for me on Linux, builtin mode. Can you provide more details? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > I am finding that the volume rendering is not working with > > OSPRay Renderer not working with ParaView 5.3.0-RC3. > > The volume render sample that I am testing looks fine > > when rendered with the default renderer, but when I switch to the > > OSPRay volume renderer, then nothing is shown. > > Has anyone managed to volume render data, using > > the OSPRay renderer with ParaView 5.3.0-RC3? > > 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 > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From agsmith424 at gmail.com Wed Mar 8 15:02:58 2017 From: agsmith424 at gmail.com (Andy Smith) Date: Wed, 8 Mar 2017 15:02:58 -0500 Subject: [Paraview] XDMF Multiblock limit on number of blocks shown in Hierarchy Message-ID: We use XDMF to output multiple unstructured blocks from our CFD code within a Spatial Collection. If 998 or fewer blocks are output in the collection all of the individual blocks are displayed in the Blocks and Hierarchy tabs in the main Properties tab when loading the grid. This allows the user the select only the blocks of interest. If 999 or more blocks are output in the collection, only the containing collection grid is shown in the Blocks and Hierarchy tabs. In this case the user cannot select the individual blocks of interest. I've attached two simple XDMF grids for reference. The same limitations on block selection occur when using Python to read the grid. Is this a limitation for all multiblock readers in ParaView or XDMF specific? Is there anyway to extend this limit to a higher value? A typical use case is to define a spatial region of interest in a Python script, read the XDMF file directly to determine the datasets that contain the grids (in HDF5 format) then loop over these datasets and query each block's bounds using h5py to see if they lie within the region of interest. If they do, then we load them in Paraview by setting the GridStatus to the appropriate list of grids. As mentioned above, this fails when the main grid collection has more than 998 blocks in it. A workaround could be to write out a temporary XDMF file based on the list of grids required, but hopefully there is a simpler solution. As a final note, for all of these cases we use the XDMF2 reader. With the XDMF3 reader neither of the supplied grids display the block hierarchy that we require. Thanks, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grid_with_00998_blocks.xmf Type: application/octet-stream Size: 51163 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grid_with_00999_blocks.xmf Type: application/octet-stream Size: 51214 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Mar 8 15:08:10 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Mar 2017 15:08:10 -0500 Subject: [Paraview] XDMF Multiblock limit on number of blocks shown in Hierarchy In-Reply-To: References: Message-ID: It is a max constant in defined in the XDMF readers. from Xdmf3SILBuilder.cxx for example: // As soon as num-grids (sub-grids and all) grows beyond this number, we assume // that the grids are too numerous for the user to select individually and // hence only the top-level grids are made accessible. #define MAX_COLLECTABLE_NUMBER_OF_GRIDS 1000 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 3:02 PM, Andy Smith wrote: > We use XDMF to output multiple unstructured blocks from our CFD code > within a Spatial Collection. > > If 998 or fewer blocks are output in the collection all of the individual > blocks are displayed in the Blocks and Hierarchy tabs in the main > Properties tab when loading the grid. This allows the user the select only > the blocks of interest. > > If 999 or more blocks are output in the collection, only the containing > collection grid is shown in the Blocks and Hierarchy tabs. In this case > the user cannot select the individual blocks of interest. > > I've attached two simple XDMF grids for reference. > > The same limitations on block selection occur when using Python to read > the grid. > > Is this a limitation for all multiblock readers in ParaView or XDMF > specific? Is there anyway to extend this limit to a higher value? > > A typical use case is to define a spatial region of interest in a Python > script, read the XDMF file directly to determine the datasets that contain > the grids (in HDF5 format) then loop over these datasets and query each > block's bounds using h5py to see if they lie within the region of > interest. If they do, then we load them in Paraview by setting the > GridStatus to the appropriate list of grids. As mentioned above, this > fails when the main grid collection has more than 998 blocks in it. > A workaround could be to write out a temporary XDMF file based on the list > of grids required, but hopefully there is a simpler solution. > > As a final note, for all of these cases we use the XDMF2 reader. With the > XDMF3 reader neither of the supplied grids display the block hierarchy that > we require. > > Thanks, > Andy > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.j.burns35.ctr at mail.mil Wed Mar 8 15:10:21 2017 From: andrew.j.burns35.ctr at mail.mil (Burns, Andrew J CTR USARMY RDECOM ARL (US)) Date: Wed, 8 Mar 2017 20:10:21 +0000 Subject: [Paraview] [Non-DoD Source] XDMF Multiblock limit on number of blocks shown in Hierarchy In-Reply-To: References: Message-ID: For the Xdmf3 reader, does it simply not display anything or does it not display correctly? From the files you attached, I see the grid/subgrid structure, but there is no data inside each item. I would guess that the Xdmf3 reader sees the empty grid and simply doesn't load it. Andrew Burns Software Engineer | Parsons Phone: 410-306-0409 ARL DSRC andrew.j.burns35.ctr at mail.mil -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Andy Smith Sent: Wednesday, March 08, 2017 3:03 PM To: Benson Muite via ParaView Subject: [Non-DoD Source] [Paraview] XDMF Multiblock limit on number of blocks shown in Hierarchy We use XDMF to output multiple unstructured blocks from our CFD code within a Spatial Collection. If 998 or fewer blocks are output in the collection all of the individual blocks are displayed in the Blocks and Hierarchy tabs in the main Properties tab when loading the grid. This allows the user the select only the blocks of interest. If 999 or more blocks are output in the collection, only the containing collection grid is shown in the Blocks and Hierarchy tabs. In this case the user cannot select the individual blocks of interest. I've attached two simple XDMF grids for reference. The same limitations on block selection occur when using Python to read the grid. Is this a limitation for all multiblock readers in ParaView or XDMF specific? Is there anyway to extend this limit to a higher value? A typical use case is to define a spatial region of interest in a Python script, read the XDMF file directly to determine the datasets that contain the grids (in HDF5 format) then loop over these datasets and query each block's bounds using h5py to see if they lie within the region of interest. If they do, then we load them in Paraview by setting the GridStatus to the appropriate list of grids. As mentioned above, this fails when the main grid collection has more than 998 blocks in it. A workaround could be to write out a temporary XDMF file based on the list of grids required, but hopefully there is a simpler solution. As a final note, for all of these cases we use the XDMF2 reader. With the XDMF3 reader neither of the supplied grids display the block hierarchy that we require. Thanks, Andy From dave.demarle at kitware.com Wed Mar 8 15:11:32 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Mar 2017 15:11:32 -0500 Subject: [Paraview] XDMF Multiblock limit on number of blocks shown in Hierarchy In-Reply-To: References: Message-ID: It is a max constant in defined in the XDMF readers. from Xdmf3SILBuilder.cxx for example: // As soon as num-grids (sub-grids and all) grows beyond this number, we assume // that the grids are too numerous for the user to select individually and // hence only the top-level grids are made accessible. #define MAX_COLLECTABLE_NUMBER_OF_GRIDS 1000 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 3:02 PM, Andy Smith wrote: > We use XDMF to output multiple unstructured blocks from our CFD code > within a Spatial Collection. > > If 998 or fewer blocks are output in the collection all of the individual > blocks are displayed in the Blocks and Hierarchy tabs in the main > Properties tab when loading the grid. This allows the user the select only > the blocks of interest. > > If 999 or more blocks are output in the collection, only the containing > collection grid is shown in the Blocks and Hierarchy tabs. In this case > the user cannot select the individual blocks of interest. > > I've attached two simple XDMF grids for reference. > > The same limitations on block selection occur when using Python to read > the grid. > > Is this a limitation for all multiblock readers in ParaView or XDMF > specific? Is there anyway to extend this limit to a higher value? > > A typical use case is to define a spatial region of interest in a Python > script, read the XDMF file directly to determine the datasets that contain > the grids (in HDF5 format) then loop over these datasets and query each > block's bounds using h5py to see if they lie within the region of > interest. If they do, then we load them in Paraview by setting the > GridStatus to the appropriate list of grids. As mentioned above, this > fails when the main grid collection has more than 998 blocks in it. > A workaround could be to write out a temporary XDMF file based on the list > of grids required, but hopefully there is a simpler solution. > > As a final note, for all of these cases we use the XDMF2 reader. With the > XDMF3 reader neither of the supplied grids display the block hierarchy that > we require. > > Thanks, > Andy > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joseph.g.hennessey2.ctr at mail.mil Wed Mar 8 17:13:42 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Wed, 8 Mar 2017 22:13:42 +0000 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED David, I can not send my data set, But I am experiencing similar problems With one of visit's sample data sets. curv3d.silo (A multi-block containing a structured curvilinear grid) I clip it and then render it with the default volume renderer and it works, but then when I turn on OSPRay it fails. (crashes) Strangely enough it also fails (does not renderer visibly) in the default renderer when I do not first clip it. My data which is failing is instead a large unstructured grid with cell/Point arrays They visualize ok with the default Volume renderer but are invisible with the OSPRay volume renderer. I have not yet found a sample I can share with you that has the same behavior. I will see if I can get you one though. Do you know of any similar publicly available samples? I have also tried the vtk analyze sample data S01_epi_r01_001.img S01_epi_r01_001.hdr Which are image (uniform rectangular grids) S01_epi_r01_001 renderers correctly with both the default volume renderer and the OSPRay one. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, March 08, 2017 3:02 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: paraview at paraview.org Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (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. ________________________________ Wavelet->Volume Works for me on Linux, builtin mode. Can you provide more details? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED Hello, I am finding that the volume rendering is not working with OSPRay Renderer not working with ParaView 5.3.0-RC3. The volume render sample that I am testing looks fine when rendered with the default renderer, but when I switch to the OSPRay volume renderer, then nothing is shown. Has anyone managed to volume render data, using the OSPRay renderer with ParaView 5.3.0-RC3? 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 < 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 > Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView > Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview > 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 dave.demarle at kitware.com Wed Mar 8 17:21:45 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Mar 2017 17:21:45 -0500 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: Thanks Joe. I'll take a look at the silo data tomorrow and see what I can find. For the large ugrid data, if you can tell me the size and number/type of arrays, that would help diagnose and/or allow me to make something to replicate the behavior. Another thing that will help isolate is if you can try with 5.1 and or 5.2 and tell me if the behavior changed. If so I should be able to pinpoint what change broke it. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 5:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > David, > > I can not send my data set, > But I am experiencing similar problems > With one of visit's sample data sets. > > curv3d.silo (A multi-block containing a structured curvilinear grid) > > I clip it and then render it with the default volume renderer > > and it works, but then when I turn on OSPRay it fails. (crashes) > > Strangely enough it also fails (does not renderer visibly) in the default > renderer when I do not first clip it. > > > My data which is failing is instead a large unstructured grid with > cell/Point > arrays > > They visualize ok with the default Volume renderer but are invisible with > the > > OSPRay volume renderer. I have not yet found a sample I can share with you > that has the same > > behavior. I will see if I can get you one though. Do you know of any > similar > publicly available samples? > > > I have also tried the vtk analyze sample data > > S01_epi_r01_001.img > S01_epi_r01_001.hdr > > Which are image (uniform rectangular grids) > > S01_epi_r01_001 renderers correctly with both the default volume renderer > > and the OSPRay one. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > -----Original Message----- > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Wednesday, March 08, 2017 3:02 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: paraview at paraview.org > Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay > Renderer > not working with ParaView 5.3.0-RC3 (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. > > > ________________________________ > > > > Wavelet->Volume Works for me on Linux, builtin mode. > > > Can you provide more details? > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) > Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote: > > > CLASSIFICATION: UNCLASSIFIED > > Hello, > > I am finding that the volume rendering is not working with > > OSPRay Renderer not working with ParaView 5.3.0-RC3. > > The volume render sample that I am testing looks fine > > when rendered with the default renderer, but when I switch to the > > OSPRay volume renderer, then nothing is shown. > > Has anyone managed to volume render data, using > > the OSPRay renderer with ParaView 5.3.0-RC3? > > 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 < 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 > > > Please keep messages on-topic and check the ParaView Wiki at: > Caution-http://paraview.org/Wiki/ParaView < > Caution-http://paraview.org/Wiki/ParaView > > > Search the list archives at: Caution-http://markmail.org/ > search/?q=ParaView < > Caution-http://markmail.org/search/?q=ParaView > > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview < > Caution-http://public.kitware.com/mailman/listinfo/paraview > > > > > > > CLASSIFICATION: UNCLASSIFIED > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taylorbrennen731 at gmail.com Thu Mar 9 01:54:47 2017 From: taylorbrennen731 at gmail.com (Brennen Taylor) Date: Thu, 9 Mar 2017 12:24:47 +0530 Subject: [Paraview] Unable to open .dat file in paraview Message-ID: Dear All , I was trying to open fluent case and data file in paraview but I am getting this error "Warning: In /build/buildd/paraview-4.0.1/VTK/IO/Geometry/vtkFLUENTReader.cxx, line 423 vtkFLUENTReader (0x3627890): Unable to open dat file." Please help me to resolve this issue. Regards, Brennen -------------- next part -------------- An HTML attachment was scrubbed... URL: From rccm.kyoshimi at gmail.com Thu Mar 9 04:56:25 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Thu, 9 Mar 2017 18:56:25 +0900 Subject: [Paraview] Unable to open .dat file in paraview In-Reply-To: References: Message-ID: Hi Brennen, This is not the error message but the warning. If dat file does not exist in the same directory as the cas, the reader is working correctly. Otherwise dat file name may be different from the cas file because vtkFLUENTReader uses the exactly the same name for both cas and dat files. Thanks, yoshimi 2017-03-09 15:54 GMT+09:00 Brennen Taylor : > Dear All , > > I was trying to open fluent case and data file in paraview but I am getting > this error "Warning: In > /build/buildd/paraview-4.0.1/VTK/IO/Geometry/vtkFLUENTReader.cxx, line 423 > > vtkFLUENTReader (0x3627890): Unable to open dat file." > > > > > Please help me to resolve this issue. > > > > > Regards, > > > Brennen > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From dave.demarle at kitware.com Thu Mar 9 12:06:41 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 9 Mar 2017 12:06:41 -0500 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: Just remembering now that OSPRay (currently) only has volume rendering implemented for image data. Please try the resample to image filter and that should look OK in OSPRay. Also - please file an issue on gitlab to remind me to make the UI warn whenever ParaView hands OSPRay something incompatible rather than just rendering nothing. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 5:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > David, > > I can not send my data set, > But I am experiencing similar problems > With one of visit's sample data sets. > > curv3d.silo (A multi-block containing a structured curvilinear grid) > > I clip it and then render it with the default volume renderer > > and it works, but then when I turn on OSPRay it fails. (crashes) > > Strangely enough it also fails (does not renderer visibly) in the default > renderer when I do not first clip it. > > > My data which is failing is instead a large unstructured grid with > cell/Point > arrays > > They visualize ok with the default Volume renderer but are invisible with > the > > OSPRay volume renderer. I have not yet found a sample I can share with you > that has the same > > behavior. I will see if I can get you one though. Do you know of any > similar > publicly available samples? > > > I have also tried the vtk analyze sample data > > S01_epi_r01_001.img > S01_epi_r01_001.hdr > > Which are image (uniform rectangular grids) > > S01_epi_r01_001 renderers correctly with both the default volume renderer > > and the OSPRay one. > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > -----Original Message----- > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Wednesday, March 08, 2017 3:02 PM > To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > Cc: paraview at paraview.org > Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay > Renderer > not working with ParaView 5.3.0-RC3 (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. > > > ________________________________ > > > > Wavelet->Volume Works for me on Linux, builtin mode. > > > Can you provide more details? > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) > Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote: > > > CLASSIFICATION: UNCLASSIFIED > > Hello, > > I am finding that the volume rendering is not working with > > OSPRay Renderer not working with ParaView 5.3.0-RC3. > > The volume render sample that I am testing looks fine > > when rendered with the default renderer, but when I switch to the > > OSPRay volume renderer, then nothing is shown. > > Has anyone managed to volume render data, using > > the OSPRay renderer with ParaView 5.3.0-RC3? > > 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 < 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 > > > Please keep messages on-topic and check the ParaView Wiki at: > Caution-http://paraview.org/Wiki/ParaView < > Caution-http://paraview.org/Wiki/ParaView > > > Search the list archives at: Caution-http://markmail.org/ > search/?q=ParaView < > Caution-http://markmail.org/search/?q=ParaView > > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview < > Caution-http://public.kitware.com/mailman/listinfo/paraview > > > > > > > CLASSIFICATION: UNCLASSIFIED > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Mar 9 12:29:16 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 9 Mar 2017 12:29:16 -0500 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: nvm on the issue request: https://gitlab.kitware.com/paraview/paraview/issues/17258 looking into the crash with curve3d.silo... David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Mar 9, 2017 at 12:06 PM, David E DeMarle wrote: > Just remembering now that OSPRay (currently) only has volume rendering > implemented for image data. > > Please try the resample to image filter and that should look OK in OSPRay. > > Also - please file an issue on gitlab to remind me to make the UI warn > whenever ParaView hands OSPRay something incompatible rather than just > rendering nothing. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Wed, Mar 8, 2017 at 5:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL > (US) wrote: > >> CLASSIFICATION: UNCLASSIFIED >> >> David, >> >> I can not send my data set, >> But I am experiencing similar problems >> With one of visit's sample data sets. >> >> curv3d.silo (A multi-block containing a structured curvilinear grid) >> >> I clip it and then render it with the default volume renderer >> >> and it works, but then when I turn on OSPRay it fails. (crashes) >> >> Strangely enough it also fails (does not renderer visibly) in the default >> renderer when I do not first clip it. >> >> >> My data which is failing is instead a large unstructured grid with >> cell/Point >> arrays >> >> They visualize ok with the default Volume renderer but are invisible with >> the >> >> OSPRay volume renderer. I have not yet found a sample I can share with you >> that has the same >> >> behavior. I will see if I can get you one though. Do you know of any >> similar >> publicly available samples? >> >> >> I have also tried the vtk analyze sample data >> >> S01_epi_r01_001.img >> S01_epi_r01_001.hdr >> >> Which are image (uniform rectangular grids) >> >> S01_epi_r01_001 renderers correctly with both the default volume renderer >> >> and the OSPRay one. >> >> Thanks, >> >> Joe >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Joseph G. Hennessey Ph.D., SAIC >> Team SAIC >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -----Original Message----- >> From: David E DeMarle [mailto:dave.demarle at kitware.com] >> Sent: Wednesday, March 08, 2017 3:02 PM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >> >> Cc: paraview at paraview.org >> Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay >> Renderer >> not working with ParaView 5.3.0-RC3 (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. >> >> >> ________________________________ >> >> >> >> Wavelet->Volume Works for me on Linux, builtin mode. >> >> >> Can you provide more details? >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL >> (US) >> > Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote: >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> Hello, >> >> I am finding that the volume rendering is not working with >> >> OSPRay Renderer not working with ParaView 5.3.0-RC3. >> >> The volume render sample that I am testing looks fine >> >> when rendered with the default renderer, but when I switch to the >> >> OSPRay volume renderer, then nothing is shown. >> >> Has anyone managed to volume render data, using >> >> the OSPRay renderer with ParaView 5.3.0-RC3? >> >> 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 < 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 > >> >> Please keep messages on-topic and check the ParaView Wiki at: >> Caution-http://paraview.org/Wiki/ParaView < >> Caution-http://paraview.org/Wiki/ParaView > >> >> Search the list archives at: Caution-http://markmail.org/se >> arch/?q=ParaView < >> Caution-http://markmail.org/search/?q=ParaView > >> >> Follow this link to subscribe/unsubscribe: >> Caution-http://public.kitware.com/mailman/listinfo/paraview < >> Caution-http://public.kitware.com/mailman/listinfo/paraview > >> >> >> >> >> >> CLASSIFICATION: UNCLASSIFIED >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ganplankr at hotmail.com Thu Mar 9 13:09:15 2017 From: ganplankr at hotmail.com (=?gb2312?B?tq0gyua1zw==?=) Date: Thu, 9 Mar 2017 18:09:15 +0000 Subject: [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Message-ID: Dear all, I am currently use ParaView version 4.1, to analyse vtk data. I want to export a group of data file from vtk into csv. However, there are about 900 data file in that group, and I don't think I could export them one by one. Do you know is there any way I could select them all and export them together at one time? I cannot find relevant information in guidebook of version 4.1, and I am wondering is this due to the limitation of the old version? Many Thanks, Stan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rca19_geek at outlook.com Thu Mar 9 13:51:55 2017 From: rca19_geek at outlook.com (Rick Angelini) Date: Thu, 9 Mar 2017 18:51:55 +0000 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> , <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe I seem to recall that I could get PV 5.2 to crash with one of the 3 demo datasets that pop up with the splash screen when I turned on OSPRay. You might check those datasets. 8-) Get Outlook for iOS ________________________________ From: ParaView on behalf of Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Sent: Wednesday, March 8, 2017 6:13:42 PM To: David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED David, I can not send my data set, But I am experiencing similar problems With one of visit's sample data sets. curv3d.silo (A multi-block containing a structured curvilinear grid) I clip it and then render it with the default volume renderer and it works, but then when I turn on OSPRay it fails. (crashes) Strangely enough it also fails (does not renderer visibly) in the default renderer when I do not first clip it. My data which is failing is instead a large unstructured grid with cell/Point arrays They visualize ok with the default Volume renderer but are invisible with the OSPRay volume renderer. I have not yet found a sample I can share with you that has the same behavior. I will see if I can get you one though. Do you know of any similar publicly available samples? I have also tried the vtk analyze sample data S01_epi_r01_001.img S01_epi_r01_001.hdr Which are image (uniform rectangular grids) S01_epi_r01_001 renderers correctly with both the default volume renderer and the OSPRay one. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, March 08, 2017 3:02 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: paraview at paraview.org Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (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. ________________________________ Wavelet->Volume Works for me on Linux, builtin mode. Can you provide more details? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED Hello, I am finding that the volume rendering is not working with OSPRay Renderer not working with ParaView 5.3.0-RC3. The volume render sample that I am testing looks fine when rendered with the default renderer, but when I switch to the OSPRay volume renderer, then nothing is shown. Has anyone managed to volume render data, using the OSPRay renderer with ParaView 5.3.0-RC3? 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 < 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 > Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView > Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview > CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Mar 9 14:17:40 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 9 Mar 2017 14:17:40 -0500 Subject: [Paraview] CellCenters filter produces non-deterministic result In-Reply-To: References: Message-ID: You can try doing the following in the GUI's Python shell (starting out with the reader as the active source): ii = ImageDataToUniformGrid() ii.SelectInputScalars = ['CELLS', 'vtkGhostType'] Show() Render() This still shows the ghost cells but if you do operations like slice or cut it will not include these cells. Note that the ImageDataToUniformGrid filter has an option to Reverse whether zero/non-zero is to be interpreted as a blanked cell. On Wed, Mar 8, 2017 at 9:20 AM, David Doria wrote: > On Tue, Mar 7, 2017 at 8:10 PM, Andy Bauer wrote: > >> Hi David, >> >> I'm not sure how it works with structured grids but with vtkUniformGrids >> (i.e. vtkImageData with blanking) the VTK readers and writers really just >> produce vtkImageData and the blanking is ignored. It may be the same with >> the XML structured grid files. My suggestion would be to look at the >> vtkImageDataToUniformGrid class in VTK and try doing a similar thing in >> ParaView using the Python Programmable filter. >> >> Cheers, >> Andy >> >> On Tue, Mar 7, 2017 at 10:22 AM, David Doria >> wrote: >> >>> On Mon, Mar 6, 2017 at 11:14 AM, Andy Bauer >>> wrote: >>> >>>> Thanks for the bug report! >>>> >>>> I think the stackoverflow issue is probably also related to blanking. I >>>> added to your bug report with two other (likely) related issues. >>>> >>>> As a side note, I think if blanking was used instead of ghost cells >>>> this may work properly. >>>> >>>> Thanks, >>>> Andy >>>> >>>> On Mon, Mar 6, 2017 at 8:45 AM, David Doria >>>> wrote: >>>> >>>>> On Sun, Mar 5, 2017 at 7:05 PM, Andy Bauer >>>>> wrote: >>>>> >>>>>> Hi David, >>>>>> >>>>>> This looks like it has to do with blanking (i.e. in PV 5.2 if I don't >>>>>> load the vtkGhostType array it has the proper bounds). Would you mind >>>>>> putting in a bug report on Gitlab (https://gitlab.kitware.com/pa >>>>>> raview/paraview)? >>>>>> >>>>>> Thanks, >>>>>> Andy >>>>>> >>>>> >>>>> Done: >>>>> https://gitlab.kitware.com/paraview/paraview/issues/17244 >>>>> >>>>> Here is another presumed bug that seems to also have to do with >>>>> blanking: http://stackoverflow.com/questions/42543340/cell-l >>>>> abels-in-selection-display-inspector-dont-work-when-any-cell >>>>> s-are-ghosted - not trying to pollute this thread but do you think >>>>> that behavior could be helpful to understand the Cell Centers issue? >>>>> >>>>> Thanks, >>>>> >>>>> David >>>>> >>>> >>>> >>> Hi Andy, >>> >>> The file was created with something like this: >>> >>> https://gist.github.com/daviddoria/8bf981aa593b7cefcd9114588e4766db >>> >>> Does calling >>> >>> structuredGrid->BlankPoint(0); >>> >>> not count as "using blanking"? Can you point me to the "right way" to do >>> this if this is not the current best practice? >>> >>> Thanks! >>> >>> David >>> >> >> > I created a uniform grid: > > https://gist.github.com/daviddoria/99fa99c52aa07ee78b7e7412e74d592f > https://drive.google.com/open?id=0B8yIfGqnlfSoNTNKWWtua1pEUTA > > Using the vtkXMLImageDataWriter seemed to write the same type of > vtkGhostType array (shown in the cell data in Paraview), but Paraview > doesn't seem to respect the blanking - all 8 voxels are drawn. > > Any other ideas? > > David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 9 14:24:31 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 9 Mar 2017 19:24:31 +0000 Subject: [Paraview] [EXTERNAL] Re: [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> , <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: <4535b77b20264d2197d1cfbe0fc87a07@ES01AMSNLNT.srn.sandia.gov> https://gitlab.kitware.com/paraview/paraview/issues/17258 Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Rick Angelini Sent: Thursday, March 9, 2017 11:52 AM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) ; David E DeMarle Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) Joe I seem to recall that I could get PV 5.2 to crash with one of the 3 demo datasets that pop up with the splash screen when I turned on OSPRay. You might check those datasets. 8-) Get Outlook for iOS ________________________________ From: ParaView > on behalf of Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > Sent: Wednesday, March 8, 2017 6:13:42 PM To: David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED David, I can not send my data set, But I am experiencing similar problems With one of visit's sample data sets. curv3d.silo (A multi-block containing a structured curvilinear grid) I clip it and then render it with the default volume renderer and it works, but then when I turn on OSPRay it fails. (crashes) Strangely enough it also fails (does not renderer visibly) in the default renderer when I do not first clip it. My data which is failing is instead a large unstructured grid with cell/Point arrays They visualize ok with the default Volume renderer but are invisible with the OSPRay volume renderer. I have not yet found a sample I can share with you that has the same behavior. I will see if I can get you one though. Do you know of any similar publicly available samples? I have also tried the vtk analyze sample data S01_epi_r01_001.img S01_epi_r01_001.hdr Which are image (uniform rectangular grids) S01_epi_r01_001 renderers correctly with both the default volume renderer and the OSPRay one. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, March 08, 2017 3:02 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > Cc: paraview at paraview.org Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (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. ________________________________ Wavelet->Volume Works for me on Linux, builtin mode. Can you provide more details? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > > wrote: CLASSIFICATION: UNCLASSIFIED Hello, I am finding that the volume rendering is not working with OSPRay Renderer not working with ParaView 5.3.0-RC3. The volume render sample that I am testing looks fine when rendered with the default renderer, but when I switch to the OSPRay volume renderer, then nothing is shown. Has anyone managed to volume render data, using the OSPRay renderer with ParaView 5.3.0-RC3? 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 < 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 > Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView > Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview > CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Thu Mar 9 14:38:32 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Thu, 9 Mar 2017 19:38:32 +0000 Subject: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91E4021A@UCOLHPUD.easf.csd.disa.mil> , <10A03274360DCF47A6EE78C9952A31CA91E402EA@UCOLHPUD.easf.csd.disa.mil> Message-ID: CLASSIFICATION: UNCLASSIFIED that would be a much smaller dataset... nice. We will give a shot..... thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Rick Angelini Sent: Thursday, March 09, 2017 1:52 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) ; David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (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 seem to recall that I could get PV 5.2 to crash with one of the 3 demo datasets that pop up with the splash screen when I turned on OSPRay. You might check those datasets. 8-) Get Outlook for iOS < Caution-https://aka.ms/o0ukef > ________________________________ From: ParaView on behalf of Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Sent: Wednesday, March 8, 2017 6:13:42 PM To: David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] [Non-DoD Source] Re: Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED David, I can not send my data set, But I am experiencing similar problems With one of visit's sample data sets. curv3d.silo (A multi-block containing a structured curvilinear grid) I clip it and then render it with the default volume renderer and it works, but then when I turn on OSPRay it fails. (crashes) Strangely enough it also fails (does not renderer visibly) in the default renderer when I do not first clip it. My data which is failing is instead a large unstructured grid with cell/Point arrays They visualize ok with the default Volume renderer but are invisible with the OSPRay volume renderer. I have not yet found a sample I can share with you that has the same behavior. I will see if I can get you one though. Do you know of any similar publicly available samples? I have also tried the vtk analyze sample data S01_epi_r01_001.img S01_epi_r01_001.hdr Which are image (uniform rectangular grids) S01_epi_r01_001 renderers correctly with both the default volume renderer and the OSPRay one. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com < Caution-mailto:dave.demarle at kitware.com > ] Sent: Wednesday, March 08, 2017 3:02 PM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: paraview at paraview.org Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay Renderer not working with ParaView 5.3.0-RC3 (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. ________________________________ Wavelet->Volume Works for me on Linux, builtin mode. Can you provide more details? David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Mar 8, 2017 at 2:51 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED Hello, I am finding that the volume rendering is not working with OSPRay Renderer not working with ParaView 5.3.0-RC3. The volume render sample that I am testing looks fine when rendered with the default renderer, but when I switch to the OSPRay volume renderer, then nothing is shown. Has anyone managed to volume render data, using the OSPRay renderer with ParaView 5.3.0-RC3? Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center CLASSIFICATION: UNCLASSIFIED _______________________________________________ Powered by Caution-Caution-www.kitware.com < Caution-Caution-http://www.kitware.com > Visit other Kitware open-source projects at Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-Caution-http://www.kitware.com/opensource/opensource.html > Please keep messages on-topic and check the ParaView Wiki at: Caution-Caution-http://paraview.org/Wiki/ParaView < Caution-Caution-http://paraview.org/Wiki/ParaView > Search the list archives at: Caution-Caution-http://markmail.org/search/?q=ParaView < Caution-Caution-http://markmail.org/search/?q=ParaView > Follow this link to subscribe/unsubscribe: Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview > CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From kmorel at sandia.gov Thu Mar 9 15:08:11 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 9 Mar 2017 20:08:11 +0000 Subject: [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Message-ID: <15C22232-552C-4C2B-9A27-43C35F2C095F@sandia.gov> Stan, I don?t know if this functionality goes all the way back to version 4.1 (I only tried back to 4.3), but if you load your vtk data as a time series then you can similarly write them out as a time series of csv files. Assuming that your vtk files are written as a numeric series (e.g. file001.vtk, file002.vtk, file003.vtk, ?), ParaView will interpret that as a file series. When you click on the file series in the browser to open it, ParaView only actually reads in the first file. If you hit the play button, ParaView will load your files one by one as an animation over time. If you have data in a time series like that, you can write out a series of csv files as a time series. Simply click on Save Data, specify a csv file name in the file browser, and then in the next dialog box check the box for ?Write All Time Steps?. ParaView will then write out a series of numbered csv file, one per time step, which corresponds to each of your input files. -Ken From: ParaView on behalf of ? ?? Date: Thursday, March 9, 2017 at 1:09 PM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Dear all, I am currently use ParaView version 4.1, to analyse vtk data. I want to export a group of data file from vtk into csv. However, there are about 900 data file in that group, and I don't think I could export them one by one. Do you know is there any way I could select them all and export them together at one time? I cannot find relevant information in guidebook of version 4.1, and I am wondering is this due to the limitation of the old version? Many Thanks, Stan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Mar 9 15:58:01 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 9 Mar 2017 20:58:01 +0000 Subject: [Paraview] =?utf-8?b?562U5aSNOiAgSGVscDogSG93IHRvIGNvbnZlcnQgYSBn?= =?utf-8?q?roup_of_vtk_data_files_at_one_time_though_ParaView?= Message-ID: <5DAABFD4-4DCA-4747-803D-AC0E3DF0C09B@sandia.gov> (Responding back to the list.) As I said, click on the ?Save Data? toolbar button (or select File -> Save Data). This will give you an option to save the data from the vtk file as a csv file. -Ken From: ? ?? Date: Thursday, March 9, 2017 at 3:51 PM To: "Moreland, Kenneth" Subject: [EXTERNAL] ??: [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Hello Ken, Really thank you for your reply. Yes, my data files are written as a numeric series, and I notice that ParaView will load all of them when I press play button. However, I have a confusion. I am not sure about the meaning of "write out", do you mean export? I obtained those files from my colleague with another simulation software, this is why I want to convert (or export) those series data file with ParaView. I will try your method, and thank you for your kind reply. Best regards, Stan ________________________________ ???: Moreland, Kenneth ????: 2017?3?9? 20:08 ???: ? ??; paraview at paraview.org ??: Re: [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Stan, I don?t know if this functionality goes all the way back to version 4.1 (I only tried back to 4.3), but if you load your vtk data as a time series then you can similarly write them out as a time series of csv files. Assuming that your vtk files are written as a numeric series (e.g. file001.vtk, file002.vtk, file003.vtk, ?), ParaView will interpret that as a file series. When you click on the file series in the browser to open it, ParaView only actually reads in the first file. If you hit the play button, ParaView will load your files one by one as an animation over time. If you have data in a time series like that, you can write out a series of csv files as a time series. Simply click on Save Data, specify a csv file name in the file browser, and then in the next dialog box check the box for ?Write All Time Steps?. ParaView will then write out a series of numbered csv file, one per time step, which corresponds to each of your input files. -Ken From: ParaView on behalf of ? ?? Date: Thursday, March 9, 2017 at 1:09 PM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Help: How to convert a group of vtk data files at one time though ParaView Dear all, I am currently use ParaView version 4.1, to analyse vtk data. I want to export a group of data file from vtk into csv. However, there are about 900 data file in that group, and I don't think I could export them one by one. Do you know is there any way I could select them all and export them together at one time? I cannot find relevant information in guidebook of version 4.1, and I am wondering is this due to the limitation of the old version? Many Thanks, Stan -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Thu Mar 9 16:51:23 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Thu, 9 Mar 2017 23:51:23 +0200 (EET) Subject: [Paraview] Cannot generate Python state when tracing is active ... Message-ID: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> Hi All, I am getting following error when i try to export visualization pipeline using co-processing plugin. I just wonder the source of the error because i could not generate python script? Traceback (most recent call last): File "", line 10, in File "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpexport.py", line 97, in DumpCoProcessingScript export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection) File "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpstate.py", line 351, in DumpPipeline state = smstate.get_state(filter=filter, raw=True) File "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/smstate.py", line 109, in get_state raise RuntimeError ("Cannot generate Python state when tracing is active.") Regards, --ufuk From utkarsh.ayachit at kitware.com Thu Mar 9 16:58:53 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 9 Mar 2017 16:58:53 -0500 Subject: [Paraview] Cannot generate Python state when tracing is active ... In-Reply-To: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> References: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> Message-ID: As the error states, currently you cannot save Python state or export Catalyst state files when trace is active. On Thu, Mar 9, 2017 at 4:51 PM, wrote: > Hi All, > > I am getting following error when i try to export visualization pipeline > using co-processing plugin. I just wonder the source of the error because > i could not generate python script? > > Traceback (most recent call last): > File "", line 10, in > File > "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpexport.py", > line 97, in DumpCoProcessingScript > export_rendering, simulation_input_map, screenshot_info, > cinema_tracks, array_selection) > File > "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpstate.py", > line 351, in DumpPipeline > state = smstate.get_state(filter=filter, raw=True) > File > "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/smstate.py", > line 109, in get_state > raise RuntimeError ("Cannot generate Python state when tracing is > active.") > > Regards, > > --ufuk > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From u.utku.turuncoglu at be.itu.edu.tr Thu Mar 9 23:52:33 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 10 Mar 2017 06:52:33 +0200 (EET) Subject: [Paraview] Cannot generate Python state when tracing is active ... In-Reply-To: References: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> Message-ID: <61701.95.7.173.201.1489121553.squirrel@webmail.be.itu.edu.tr> Yes. My first reaction was same and i checked the tracing but it was not active. So, the error must be related with something else. By the way, is any particular filter could trigger this error. Is there any restriction out there when we are trying to use co-processing? Thanks, --ufuk > As the error states, currently you cannot save Python state or export > Catalyst state files when trace is active. > > On Thu, Mar 9, 2017 at 4:51 PM, wrote: >> Hi All, >> >> I am getting following error when i try to export visualization pipeline >> using co-processing plugin. I just wonder the source of the error >> because >> i could not generate python script? >> >> Traceback (most recent call last): >> File "", line 10, in >> File >> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpexport.py", >> line 97, in DumpCoProcessingScript >> export_rendering, simulation_input_map, screenshot_info, >> cinema_tracks, array_selection) >> File >> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpstate.py", >> line 351, in DumpPipeline >> state = smstate.get_state(filter=filter, raw=True) >> File >> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/smstate.py", >> line 109, in get_state >> raise RuntimeError ("Cannot generate Python state when tracing is >> active.") >> >> Regards, >> >> --ufuk >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Mar 10 10:15:57 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 10:15:57 -0500 Subject: [Paraview] Cannot generate Python state when tracing is active ... In-Reply-To: <61701.95.7.173.201.1489121553.squirrel@webmail.be.itu.edu.tr> References: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> <61701.95.7.173.201.1489121553.squirrel@webmail.be.itu.edu.tr> Message-ID: That's odd, that sounds like a bug. What does you pipeline look like? To you can steps that I can use to reproduce this issue? If so, it would be great if you report an issue on the issue tracker here: https://gitlab.kitware.com/paraview/paraview/issues Utkarsh On Thu, Mar 9, 2017 at 11:52 PM, wrote: > Yes. My first reaction was same and i checked the tracing but it was not > active. So, the error must be related with something else. By the way, is > any particular filter could trigger this error. Is there any restriction > out there when we are trying to use co-processing? > > Thanks, > --ufuk > >> As the error states, currently you cannot save Python state or export >> Catalyst state files when trace is active. >> >> On Thu, Mar 9, 2017 at 4:51 PM, wrote: >>> Hi All, >>> >>> I am getting following error when i try to export visualization pipeline >>> using co-processing plugin. I just wonder the source of the error >>> because >>> i could not generate python script? >>> >>> Traceback (most recent call last): >>> File "", line 10, in >>> File >>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpexport.py", >>> line 97, in DumpCoProcessingScript >>> export_rendering, simulation_input_map, screenshot_info, >>> cinema_tracks, array_selection) >>> File >>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpstate.py", >>> line 351, in DumpPipeline >>> state = smstate.get_state(filter=filter, raw=True) >>> File >>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/smstate.py", >>> line 109, in get_state >>> raise RuntimeError ("Cannot generate Python state when tracing is >>> active.") >>> >>> Regards, >>> >>> --ufuk >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From rustem.khabetdinov at gmail.com Fri Mar 10 11:43:09 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Fri, 10 Mar 2017 19:43:09 +0300 Subject: [Paraview] Python 3 Message-ID: Hello, Is there any exact date when python 3 will be supported? It seems like it's been almost 3 months since there was last update: https://gitlab.kitware.com/paraview/paraview/issues/16818 Best Regards, Rustem -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 10 11:45:35 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 11:45:35 -0500 Subject: [Paraview] Python 3 In-Reply-To: References: Message-ID: Python 3 is supported with 5.3 (except for ParaViewWeb components). We have dashboards testing it too. There still may be some leftovers, so please report if you catch anything that we missed. Utkarsh On Fri, Mar 10, 2017 at 11:43 AM, Rustem Khabetdinov wrote: > Hello, > Is there any exact date when python 3 will be supported? It seems like it's > been almost 3 months since there was last update: > https://gitlab.kitware.com/paraview/paraview/issues/16818 > > Best Regards, > Rustem > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From rustem.khabetdinov at gmail.com Fri Mar 10 12:03:28 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Fri, 10 Mar 2017 20:03:28 +0300 Subject: [Paraview] Python 3 In-Reply-To: References: Message-ID: Thank you. On 10 Mar 2017 19:45, "Utkarsh Ayachit" wrote: Python 3 is supported with 5.3 (except for ParaViewWeb components). We have dashboards testing it too. There still may be some leftovers, so please report if you catch anything that we missed. Utkarsh On Fri, Mar 10, 2017 at 11:43 AM, Rustem Khabetdinov wrote: > Hello, > Is there any exact date when python 3 will be supported? It seems like it's > been almost 3 months since there was last update: > https://gitlab.kitware.com/paraview/paraview/issues/16818 > > Best Regards, > Rustem > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Mar 10 13:13:30 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 10 Mar 2017 20:13:30 +0200 (EET) Subject: [Paraview] Cannot generate Python state when tracing is active ... In-Reply-To: References: <39988.95.7.173.201.1489096283.squirrel@webmail.be.itu.edu.tr> <61701.95.7.173.201.1489121553.squirrel@webmail.be.itu.edu.tr> Message-ID: <64890.95.7.173.201.1489169610.squirrel@webmail.be.itu.edu.tr> Hi, Thanks for your help. I opened issue about that https://gitlab.kitware.com/paraview/paraview/issues/17270 I think that the tracing error is triggered by another one. Please see issue for detailed information. Regards, --ufuk > That's odd, that sounds like a bug. What does you pipeline look like? > To you can steps that I can use to reproduce this issue? If so, it > would be great if you report an issue on the issue tracker here: > https://gitlab.kitware.com/paraview/paraview/issues > > Utkarsh > > On Thu, Mar 9, 2017 at 11:52 PM, wrote: >> Yes. My first reaction was same and i checked the tracing but it was not >> active. So, the error must be related with something else. By the way, >> is >> any particular filter could trigger this error. Is there any restriction >> out there when we are trying to use co-processing? >> >> Thanks, >> --ufuk >> >>> As the error states, currently you cannot save Python state or export >>> Catalyst state files when trace is active. >>> >>> On Thu, Mar 9, 2017 at 4:51 PM, >>> wrote: >>>> Hi All, >>>> >>>> I am getting following error when i try to export visualization >>>> pipeline >>>> using co-processing plugin. I just wonder the source of the error >>>> because >>>> i could not generate python script? >>>> >>>> Traceback (most recent call last): >>>> File "", line 10, in >>>> File >>>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpexport.py", >>>> line 97, in DumpCoProcessingScript >>>> export_rendering, simulation_input_map, screenshot_info, >>>> cinema_tracks, array_selection) >>>> File >>>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/cpstate.py", >>>> line 351, in DumpPipeline >>>> state = smstate.get_state(filter=filter, raw=True) >>>> File >>>> "/opt/progs/paraview-5.3.0rc2/lib/site-packages/paraview/smstate.py", >>>> line 109, in get_state >>>> raise RuntimeError ("Cannot generate Python state when tracing is >>>> active.") >>>> >>>> Regards, >>>> >>>> --ufuk >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> > From wascott at sandia.gov Fri Mar 10 13:16:42 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 10 Mar 2017 18:16:42 +0000 Subject: [Paraview] Field value question from a user Message-ID: Greetings, Is there a way with the calculator or something similar in paraview to grab the field value at a particular time step, so that I could then subtract it off of the time varying field? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Mar 10 13:44:02 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 10 Mar 2017 18:44:02 +0000 Subject: [Paraview] Field value question from a user Message-ID: <83BC7593-448F-45B4-908A-B4630CA4269C@sandia.gov> This is complex but can be done with the time support in VTK?s pipeline. However, it requires the filter to hold state from one call of RequestData to the next. This is simple enough in C++, but I?m not sure how you do it in the Python interpreter (used by the programmable filter). You could declare a global variable, but are you guaranteed to get the same interpreter instance each call? That?s a question for Utkarsh. -Ken From: ParaView on behalf of Walter Scott Date: Friday, March 10, 2017 at 1:16 PM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Field value question from a user Greetings, Is there a way with the calculator or something similar in paraview to grab the field value at a particular time step, so that I could then subtract it off of the time varying field? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Mar 10 14:15:46 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 14:15:46 -0500 Subject: [Paraview] Field value question from a user In-Reply-To: <83BC7593-448F-45B4-908A-B4630CA4269C@sandia.gov> References: <83BC7593-448F-45B4-908A-B4630CA4269C@sandia.gov> Message-ID: > You could declare > a global variable, but are you guaranteed to get the same interpreter > instance each call? That?s a question for Utkarsh. Yes, you are. From rodneicouto at gmail.com Fri Mar 10 14:37:44 2017 From: rodneicouto at gmail.com (Rodnei Couto) Date: Fri, 10 Mar 2017 16:37:44 -0300 Subject: [Paraview] ParaView Web - module twisted.internet error Message-ID: I set up my environment as indicated in http://kitware.github.io/ paraviewweb/docs/ubuntu_14_04.html My operational system is Ubuntu 64 14_04 LTS. When I try to run my start.sh, I get an error: pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in from twisted.internet import reactor, defer ImportError: No module named twisted.internet i think the twisted is properly installed in my environment, as can be seen below: pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " My start.sh code is: #!/bin/bash export DISPLAY=:0.0 /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & Can anybody help me? I do not know what else I can do Cheers, ? Rodnei Couto | (55 21) 98749-9885 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Mar 10 14:55:27 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 10 Mar 2017 12:55:27 -0700 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Did you try to set up your own version of twisted in your system python? When you illustrated how twisted was properly set up, you did it with "python", but your start script runs pvpython. I wonder if maybe your system python twisted is conflicting (or overriding) with the one provided by pvpython? That's just a guess based on a quick read. Hope this helps, Scott On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto wrote: > I set up my environment as indicated in http://kitware.github.io/pa > raviewweb/docs/ubuntu_14_04.html > > My operational system is Ubuntu 64 14_04 LTS. > > When I try to run my start.sh, I get an error: > > pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): > File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in > from twisted.internet import reactor, defer > ImportError: No module named twisted.internet > > i think the twisted is properly installed in my environment, as can be > seen below: > > pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " > > > > > My start.sh code is: > > #!/bin/bash > export DISPLAY=:0.0 > /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & > > > Can anybody help me? I do not know what else I can do > > Cheers, > > ? > > Rodnei Couto | (55 21) 98749-9885 > ? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rodneicouto at gmail.com Fri Mar 10 16:31:10 2017 From: rodneicouto at gmail.com (Rodnei Couto) Date: Fri, 10 Mar 2017 18:31:10 -0300 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Hi, Thanks for the answer. I completely removed the twisted from my machine and the error continue. In fact the error occurred before his installation. I installed twitted to try to solve it Any other ideas? Cheers, -- Rodnei Couto | (55 21) 98749-9885 On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > Did you try to set up your own version of twisted in your system python? > When you illustrated how twisted was properly set up, you did it with > "python", but your start script runs pvpython. I wonder if maybe your > system python twisted is conflicting (or overriding) with the one provided > by pvpython? That's just a guess based on a quick read. > > Hope this helps, > Scott > > On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto > wrote: > >> I set up my environment as indicated in http://kitware.github.io/pa >> raviewweb/docs/ubuntu_14_04.html >> >> My operational system is Ubuntu 64 14_04 LTS. >> >> When I try to run my start.sh, I get an error: >> >> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >> from twisted.internet import reactor, defer >> ImportError: No module named twisted.internet >> >> i think the twisted is properly installed in my environment, as can be >> seen below: >> >> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >> >> >> >> >> My start.sh code is: >> >> #!/bin/bash >> export DISPLAY=:0.0 >> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >> >> >> Can anybody help me? I do not know what else I can do >> >> Cheers, >> >> ? >> >> Rodnei Couto | (55 21) 98749-9885 >> ? >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Mar 10 16:36:17 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 10 Mar 2017 14:36:17 -0700 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: What version of ParaView are you using? One you built yourself (if so, how old), or a release binary? On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto wrote: > Hi, > > Thanks for the answer. > > I completely removed the twisted from my machine and the error continue. > In fact the error occurred before his installation. I installed twitted to > try to solve it > > Any other ideas? > > Cheers, > > > -- > Rodnei Couto | (55 21) 98749-9885 > > On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> Did you try to set up your own version of twisted in your system python? >> When you illustrated how twisted was properly set up, you did it with >> "python", but your start script runs pvpython. I wonder if maybe your >> system python twisted is conflicting (or overriding) with the one provided >> by pvpython? That's just a guess based on a quick read. >> >> Hope this helps, >> Scott >> >> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto >> wrote: >> >>> I set up my environment as indicated in http://kitware.github.io/pa >>> raviewweb/docs/ubuntu_14_04.html >>> >>> My operational system is Ubuntu 64 14_04 LTS. >>> >>> When I try to run my start.sh, I get an error: >>> >>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>> from twisted.internet import reactor, defer >>> ImportError: No module named twisted.internet >>> >>> i think the twisted is properly installed in my environment, as can be >>> seen below: >>> >>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>> >>> >>> >>> >>> My start.sh code is: >>> >>> #!/bin/bash >>> export DISPLAY=:0.0 >>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>> >>> >>> Can anybody help me? I do not know what else I can do >>> >>> Cheers, >>> >>> ? >>> >>> Rodnei Couto | (55 21) 98749-9885 >>> ? >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rskowch at gmail.com Fri Mar 10 17:32:49 2017 From: rskowch at gmail.com (Roman Kowch) Date: Fri, 10 Mar 2017 17:32:49 -0500 Subject: [Paraview] Crash occurs after clicking "File" then "Open" Message-ID: Hi, I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the GUI. The application however crashes on one of my computers when I simply click "File" then "Open." It seems that the crash happens when it needs to bring up the dialog for selecting a file. It also happens if I do these menu clicks: 1. "File", "Load Window Layout" 2. "File", "Load State" 3. "File", "Save State" As you can see, the crash appears to happen whenever a directory dialog is expected to appear. Should I send a crash report to diagnose this problem? I should also mention that on another computer, this problem does NOT appear for the same build of Paraview. The problem seems unique to a particular computer I'm using. Regards, Roman -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvan.fournier at free.fr Fri Mar 10 18:36:00 2017 From: yvan.fournier at free.fr (Yvan Fournier) Date: Sat, 11 Mar 2017 00:36:00 +0100 Subject: [Paraview] Issues with OpenGL2 support for off-screen Mesa In-Reply-To: <1610574620.163154086.1487957114108.JavaMail.root@zimbra10-e2> References: <1610574620.163154086.1487957114108.JavaMail.root@zimbra10-e2> Message-ID: <1489188960.14532.1.camel@free.fr> Hello, I made some progress using OpenGL2 for offs-screen Mesa on a Debian 8-based system: I don't need to compile my code or ParaView in static: compiling everything with dyanmic libraries works, as long as I link everything together instead of loading a plugin (consisting of some Code_Saturne libraries, ParaView Libraries, and OSMesa/Gallium). So it seems some things re not initialized correctly when I load ParaView and OSMesa as a plugin, so I'm not took sure the problem comes from ParaView, OSMesa, or LLVM. I tried OSMesa 13.0.3 and 17.0.1, and LLVM 3.5 (packaged with Debian 8) and 3.9 (local build), with identical results. I also tried using RTLD_NOW and even RTLD_NOW | RTLD_GLOBAL instead of the usual RTLD_LAZY when using dlopen, with no difference in behavior (I have not tried RTLD_DEEPBIND). Has anyone encountered similar issues or does anyone have an idea what could be missing in the initialization stage using dlopen for a plugin linked with Catalyst ? I do not encounter this issue on an Arch-Linux-based system, but encounter it on a Debian 8 ("Jessie") system ? Using a plugin is not an absolute must, but it would be preferable if I managed to get it working again with that build option. Best regards, Yvan Friday Feb 24 f?vrier 2017 at 18:25 +0100, yvan.fournier at free.fr wrote: > Hi Chuck, > > here is what I have in /home/D43345/opt/Mesa-13.0/arch/calibre9/lib: > > -rwxr-xr-x 1 D43345 rdusers?????1098 Feb 22 15:24 libOSMesa.la > lrwxrwxrwx 1 D43345 rdusers???????18 Feb 22 15:24 libOSMesa.so -> > libOSMesa.so.8.0.0 > lrwxrwxrwx 1 D43345 rdusers???????18 Feb 22 15:24 libOSMesa.so.8 -> > libOSMesa.so.8.0.0 > -rwxr-xr-x 1 D43345 rdusers 47309888 Feb 22 15:24 libOSMesa.so.8.0.0 > -rwxr-xr-x 1 D43345 rdusers??????962 Feb 22 15:24 libglapi.la > lrwxrwxrwx 1 D43345 rdusers???????17 Feb 22 15:24 libglapi.so -> > libglapi.so.0.0.0 > lrwxrwxrwx 1 D43345 rdusers???????17 Feb 22 15:24 libglapi.so.0 -> > libglapi.so.0.0.0 > -rwxr-xr-x 1 D43345 rdusers??1400520 Feb 22 15:24 libglapi.so.0.0.0 > -rwxr-xr-x 1 D43345 rdusers?????1018 Feb 22 15:24 libswrAVX.la > lrwxrwxrwx 1 D43345 rdusers???????18 Feb 22 15:24 libswrAVX.so -> > libswrAVX.so.0.0.0 > lrwxrwxrwx 1 D43345 rdusers???????18 Feb 22 15:24 libswrAVX.so.0 -> > libswrAVX.so.0.0.0 > -rwxr-xr-x 1 D43345 rdusers 97879312 Feb 22 15:24 libswrAVX.so.0.0.0 > -rwxr-xr-x 1 D43345 rdusers?????1024 Feb 22 15:24 libswrAVX2.la > lrwxrwxrwx 1 D43345 rdusers???????19 Feb 22 15:24 libswrAVX2.so -> > libswrAVX2.so.0.0.0 > lrwxrwxrwx 1 D43345 rdusers???????19 Feb 22 15:24 libswrAVX2.so.0 -> > libswrAVX2.so.0.0.0 > -rwxr-xr-x 1 D43345 rdusers 96655416 Feb 22 15:24 libswrAVX2.so.0.0.0 > drwxr-xr-x 2 D43345 rdusers?????4096 Feb 22 15:24 pkgconfig > > > And here is the summary after configuration of Mesa: > > ????????prefix:??????????/home/D43345/opt/Mesa-13.0/arch/calibre9 > ????????exec_prefix:?????${prefix} > ????????libdir:??????????${exec_prefix}/lib > ????????includedir:??????${prefix}/include > > ????????OpenGL:??????????yes (ES1: no ES2: no) > > ????????OSMesa:??????????libOSMesa (Gallium) > > ????????GLX:?????????????no > > ????????EGL:?????????????no > > ????????Vulkan drivers:??no > > ????????llvm:????????????yes > ????????llvm-config:?????/home/D43345/opt/llvm-3.9/arch/calibre9/bin/llvm- > config > ????????llvm-version:????3.9.1 > > ????????Gallium drivers: swrast swr > ????????Gallium st:??????mesa > > ????????HUD extra stats: no > ????????HUD lmsensors:???no > > ????????Shader cache:????yes > ????????With SHA1 from:??libcrypto > > ????????Shared libs:?????yes > ????????Static libs:?????no > ????????Shared-glapi:????yes > > ????????CFLAGS:??????????-g -O2 -Wall -std=c99 -Werror=implicit-function- > declaration -Werror=missing-prototypes -fno-math-errno -fno-trapping-math > ????????CXXFLAGS:????????-g -O2 -Wall -fno-math-errno -fno-trapping-math > ????????Macros:??????????-D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS > -D_GNU_SOURCE -DUSE_SSE41 -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG -DUSE_X86_64_ASM > -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP > -DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_SHA1 -DMESA_EGL_NO_X11_HEADERS > -DHAVE_LLVM=0x0309 -DMESA_LLVM_VERSION_PATCH=1 > > ????????LLVM_CFLAGS:?????-I/home/D43345/opt/llvm-3.9/arch/calibre9/include??- > D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS > ????????LLVM_CXXFLAGS:???-I/home/D43345/opt/llvm- > 3.9/arch/calibre9/include????-W -Wno-unused-parameter -Wwrite-strings??-Wno- > missing-field-initializers??-Wno-long-long -Wno-maybe-uninitialized -Wdelete- > non-virtual-dtor -Wno-comment -Werror=date-time -std=c++11???????- > D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS > ????????LLVM_CPPFLAGS:???-I/home/D43345/opt/llvm-3.9/arch/calibre9/include??- > D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS > ????????LLVM_LDFLAGS:????-L/home/D43345/opt/llvm-3.9/arch/calibre9/lib? > > ????????PYTHON2:?????????python2.7 > > ????????Run 'make' to build Mesa > > > Best regards, > > ? Yvan > > ----- Mail original ----- > De: "Chuck Atkins" > ?: "yvan fournier" > Cc: "ParaView Mailing List" > Envoy?: Jeudi 23 F?vrier 2017 19:14:03 > Objet: Re: [Paraview] Issues with OpenGL2 support for off-screen Mesa > > > > Hi Yvan,? > What are the resulting libraries in /home/D43345/opt/Mesa- > 13.0/arch/calibre9/lib after the Mesa install? It looks like something has > gone a bit awry with the Mesa build. Also, what does the summary look like > that's printed out at the end of ./configure for Mesa?? > > > > > > > > > > ----------? > Chuck Atkins? > Staff R&D Engineer, Scientific Computing? > Kitware, Inc.? > > > > On Wed, Feb 22, 2017 at 7:00 PM, < yvan.fournier at free.fr > wrote:? > > > Hello,? > > I recently encountered issues related to the OpenGL2 support for off-screen > Mesa. Up to at least ParaView V5.1.2, I could use ParaView/Catalyst built with > OSMesa with no specific issues (I mostly used OSMesa compiled without LLVM, as > rendering did not represent a huge portion of my compute time.? > > I'm using Catalyst in the context of the Code_Saturne CFD code. By default, > the code includes a plugin, linked to both ParaView or a Catalys edition > (based on the info from the cmake entry in ParaView installs when > -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON is used). On Linux systems, the plugin > is loaded with dlopen(, RTLD_LAZY).? > We use Catalyst Python scripts, so the plugin goes through ParaView's Python > layer also to render images.? > > On my personal PC, running Arch Linux I have not encountered any specific > issue with recent ParaView changes and the move to OpenGL2 (actually, for on- > screen redering, the Intel graphics driver/QT5 rendering issue leading to > spurious transparencies that I had before seem to have disappeared, so things > are actually better.? > > On company machines (workstations and clusters using EDF's Debian 8 flavor, > with gcc version (Debian 4.9.2-10) 4.9.2, things are not working so well, as I > get an error message related to missing OpenGL features starting with ParaView > 5.2 (and up to today's master).? > I switched to Mesa 13.0.1, then 13.0.4, following the new instructions on the > ParaView Wiki, but I still always get the following error:? > > """? > ERROR: In > /home/D43345/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 733? > vtkOSOpenGLRenderWindow (0x808db80): GL version 2.1 with the gpu_shader4 > extension is not supported by your graphics driver but is required for the new > OpenGL rendering backend. Please update your OpenGL driver. If you are using > Mesa please make sure you have version 10.6.5 or later and make sure your > driver in Mesa supports OpenGL 3.2.? > GL_Version: 3.3 (Core Profile) Mesa 13.0.4.? > """? > > My mesa build used the following options (from the ParaView wiki) :? > > ./configure --prefix=$HOME/opt/Mesa-13.0/arch/calibre9 --enable-opengl -- > disable-gles1 --disable-gles2 --disable-va --disable-xvmc --disable-vdpau -- > enable-shared-glapi --disable-texture-float --enable-gallium-llvm --enable- > llvm-shared-libs --with-gallium-drivers=swrast,swr --disable-dri --with-dri- > drivers= --disable-egl --with-egl-platforms= --disable-gbm --disable-glx -- > disable-osmesa --enable-gallium-osmesa --with-llvm-prefix=$HOME/opt/llvm- > 3.9/arch/calibre9? > > I tried both using the local llvm install (v3.5, which worked in part and > could not compile OpenSwr), and a local build of LLVM 3.9.1 (shown above). I > also added --enable-debug for my latest tests.? > > Things work slightly better with LLVM 3.9 than with 3.5, but I still get the > above error mentioning the gpu_shader4 extension, whether exporting > GALLIUM_DRIVER=llvmpipe or softpipe. With GALLIUM_DRIVER=swr, I have another > error:? > > """? > Using OpenSWR :? > > SWR detected AVX2? > SWR library load failure: /home/D43345/opt/Mesa- > 13.0/arch/calibre9/lib/libswrAVX2.so: undefined symbol: _glapi_Context? > """? > > During my testing, I also built a static version of my code, with a static > build of ParaView (and the plugin replaced by a static link), but keeping the > same dynamic library for OSMesa. And surprise, that version worked normally, > producing the expected images (at least with the LLVM 3.9 build; with LLVM > 3.5, I had the color map labels, but no colored slice...).? > > So the issue seems to be on the ParaView side more than on the OSMesa side. I > have a debug build of the Code_Saturne/ParaView/OSMesa stack, but although I > can explore where the final error occurs (in vtkOpenGLRenderWindow.cxx), and > some GLES querying before that, I don't realy know where to look .? > > As the error occurs with a dynamic but not static build, is seems to be > related to initialization issues, but I don't know VTK well enough to provide > more precise info.? > > Has anybody encounted this issue ? Does anybody have suggestions ? I'm > planning on trying other options than RTLD_LAZY on my plugin's side, but if > that does not work, I'll be out of ideas.? > > Best regards,? > > Yvan? > > PS: in case they are useful as a reference, the build options for Mesa used by > Arch Linux (recently switched from 13 to 17), on the system on which I had > zero issue, are the following:? > > ./configure --prefix=/usr \? > --sysconfdir=/etc \? > --with-dri-driverdir=/usr/lib/xorg/modules/dri \? > --with-gallium-drivers=r300,r600,radeonsi,nouveau,svga,swrast,virgl \? > --with-dri-drivers=i915,i965,r200,radeon,nouveau,swrast \? > --with-egl-platforms=x11,drm,wayland \? > --with-vulkan-drivers=intel,radeon \? > --disable-xvmc \? > --enable-gallium-llvm \? > --enable-llvm-shared-libs \? > --enable-shared-glapi \? > --enable-libglvnd \? > --enable-egl \? > --enable-glx \? > --enable-glx-tls \? > --enable-gles1 \? > --enable-gles2 \? > --enable-gbm \? > --enable-dri \? > --enable-osmesa \? > --enable-texture-float \? > --enable-xa \? > --enable-vdpau \? > --enable-omx \? > --enable-nine \? > --enable-opencl \? > --enable-opencl-icd \? > --with-clang-libdir=/usr/lib? > > There is also a patch related to glapi linkage which I might try in case it > solved my glapi missing symbol issue with OpenSWR...? > _______________________________________________? > Powered by www.kitware.com? > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/ > opensource.html? > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview. > org/Wiki/ParaView? > > Search the list archives at: http://markmail.org/search/?q=ParaView? > > Follow this link to subscribe/unsubscribe:? > http://public.kitware.com/mailman/listinfo/paraview? > From kmorel at sandia.gov Fri Mar 10 20:02:52 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Sat, 11 Mar 2017 01:02:52 +0000 Subject: [Paraview] Field value question from a user In-Reply-To: References: <83BC7593-448F-45B4-908A-B4630CA4269C@sandia.gov>, Message-ID: <9D5D216B-F7EA-43AF-B820-62C18F79410B@sandia.gov> Alan, So in summary, yes it is possible to do this with the programmable filter. What you do is check the time to see if it equals the target time step. If so, save the array from the desired field in a global variable. Then on other time steps do the difference. You may have noticed I'm not giving you code. This is because I am too lazy to spend the hour or so getting it to work. -Ken Sent from my iPad so blame autocorrect. On Mar 10, 2017, at 12:15 PM, Utkarsh Ayachit wrote: >> You could declare >> a global variable, but are you guaranteed to get the same interpreter >> instance each call? That?s a question for Utkarsh. > > Yes, you are. From utkarsh.ayachit at kitware.com Fri Mar 10 20:30:30 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 10 Mar 2017 20:30:30 -0500 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Do you have Dell Backup and Recovery (DBaR) tools installed on your system? If so, the crash may be related to an issue with DBaR at Qt 5. You may need to update DBaR to the latest version. See [1] for details. [1] http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253 On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: > Hi, > > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the GUI. The > application however crashes on one of my computers when I simply click > "File" then "Open." It seems that the crash happens when it needs to bring > up the dialog for selecting a file. It also happens if I do these menu > clicks: > > 1. "File", "Load Window Layout" > 2. "File", "Load State" > 3. "File", "Save State" > > As you can see, the crash appears to happen whenever a directory dialog is > expected to appear. Should I send a crash report to diagnose this problem? > > I should also mention that on another computer, this problem does NOT appear > for the same build of Paraview. The problem seems unique to a particular > computer I'm using. > > Regards, > Roman > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From rodneicouto at gmail.com Fri Mar 10 20:34:35 2017 From: rodneicouto at gmail.com (Rodnei Couto) Date: Fri, 10 Mar 2017 22:34:35 -0300 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: My version was downloaded from the official site ParaView-5.3.0-RC3-Qt5-OpenGL2-MPI-Linux-64bit Cheers, -- Rodnei Couto | (55 21) 98749-9885 On Fri, Mar 10, 2017 at 6:36 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > What version of ParaView are you using? One you built yourself (if so, > how old), or a release binary? > > > On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto > wrote: > >> Hi, >> >> Thanks for the answer. >> >> I completely removed the twisted from my machine and the error continue. >> In fact the error occurred before his installation. I installed twitted to >> try to solve it >> >> Any other ideas? >> >> Cheers, >> >> >> -- >> Rodnei Couto | (55 21) 98749-9885 >> >> On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> Did you try to set up your own version of twisted in your system >>> python? When you illustrated how twisted was properly set up, you did it >>> with "python", but your start script runs pvpython. I wonder if maybe your >>> system python twisted is conflicting (or overriding) with the one provided >>> by pvpython? That's just a guess based on a quick read. >>> >>> Hope this helps, >>> Scott >>> >>> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto >>> wrote: >>> >>>> I set up my environment as indicated in http://kitware.github.io/pa >>>> raviewweb/docs/ubuntu_14_04.html >>>> >>>> My operational system is Ubuntu 64 14_04 LTS. >>>> >>>> When I try to run my start.sh, I get an error: >>>> >>>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>>> from twisted.internet import reactor, defer >>>> ImportError: No module named twisted.internet >>>> >>>> i think the twisted is properly installed in my environment, as can be >>>> seen below: >>>> >>>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>>> >>>> >>>> >>>> >>>> My start.sh code is: >>>> >>>> #!/bin/bash >>>> export DISPLAY=:0.0 >>>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>>> >>>> >>>> Can anybody help me? I do not know what else I can do >>>> >>>> Cheers, >>>> >>>> ? >>>> >>>> Rodnei Couto | (55 21) 98749-9885 >>>> ? >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Mar 10 20:45:45 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 11 Mar 2017 01:45:45 +0000 Subject: [Paraview] Field value question from a user In-Reply-To: <9D5D216B-F7EA-43AF-B820-62C18F79410B@sandia.gov> References: <83BC7593-448F-45B4-908A-B4630CA4269C@sandia.gov> <9D5D216B-F7EA-43AF-B820-62C18F79410B@sandia.gov> Message-ID: Thanks. I passed this on to my user. If necessary, I will poke either Jeff or Kitware. Alan On 3/10/17, 6:02 PM, "Moreland, Kenneth" wrote: Alan, So in summary, yes it is possible to do this with the programmable filter. What you do is check the time to see if it equals the target time step. If so, save the array from the desired field in a global variable. Then on other time steps do the difference. You may have noticed I'm not giving you code. This is because I am too lazy to spend the hour or so getting it to work. -Ken Sent from my iPad so blame autocorrect. On Mar 10, 2017, at 12:15 PM, Utkarsh Ayachit wrote: >> You could declare >> a global variable, but are you guaranteed to get the same interpreter >> instance each call? That?s a question for Utkarsh. > > Yes, you are. From hero.jairaj at gmail.com Fri Mar 10 23:29:38 2017 From: hero.jairaj at gmail.com (JAIRAJ MATHUR) Date: Fri, 10 Mar 2017 22:29:38 -0600 Subject: [Paraview] Issue following data when scaled Message-ID: Dear all The camera can perfectly follow data when I add it, but when I scale the axis by 10 times in x and y directions(by using the transforming options in display), the camera is unable to follow data. It seems that it still thinks the data is where it was originally. Am I missing a step after scaling? Thanking you -- Jairaj Mathur, Mechanical Engineering Washington University in St Louis -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sat Mar 11 12:45:20 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 11 Mar 2017 12:45:20 -0500 Subject: [Paraview] Issue following data when scaled In-Reply-To: References: Message-ID: Try using the "Transform" filter instead. The transformation properties on t he "Display" only affect the rendering, not the data. The "Follow Data" functionality currently uses the data bounds, rather than the transformed bounds -- which should be fixed; so please feel free to report a bug on the issue tracker [1]. The Transform filter transform the data itself, as a result, the current "Follow Data" implementation should be able to follow it better. [1] https://gitlab.kitware.com/paraview/paraview/issues On Fri, Mar 10, 2017 at 11:29 PM, JAIRAJ MATHUR wrote: > Dear all > > The camera can perfectly follow data when I add it, but when I scale the > axis by 10 times in x and y directions(by using the transforming options in > display), the camera is unable to follow data. It seems that it still thinks > the data is where it was originally. Am I missing a step after scaling? > > Thanking you > > -- > Jairaj Mathur, > Mechanical Engineering > Washington University in St Louis > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From frank0734 at gmail.com Sat Mar 11 12:49:24 2017 From: frank0734 at gmail.com (Liang Wang) Date: Sat, 11 Mar 2017 12:49:24 -0500 Subject: [Paraview] Python API to set color palette? Message-ID: I don't find a dedicated Python function to set color palette. It does not appear to be an option to the simple.SaveScreenshot function either. Or, can I directly set each color available in the Edit -> Settings -> Color Palette? Best, Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sat Mar 11 13:33:51 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 11 Mar 2017 13:33:51 -0500 Subject: [Paraview] Python API to set color palette? In-Reply-To: References: Message-ID: There isn't one currently. I am actively working on a fix for the same, however. It should be available in the ParaView release scheduled for May/June 2017. On Sat, Mar 11, 2017 at 12:49 PM, Liang Wang wrote: > I don't find a dedicated Python function to set color palette. > It does not appear to be an option to the simple.SaveScreenshot function > either. > > Or, can I directly set each color available in the Edit -> Settings -> Color > Palette? > > Best, > Liang > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From rskowch at gmail.com Sat Mar 11 18:49:36 2017 From: rskowch at gmail.com (Roman Kowch) Date: Sat, 11 Mar 2017 18:49:36 -0500 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Sorry, I should have mentioned that I'm running ParaView on a Mac Pro computer, with OS X 10.11.6. The computer does not have DBaR. Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the same crash I'm seeing on this particular computer. Again, I could send a crash report if that would help. On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Do you have Dell Backup and Recovery (DBaR) tools installed on your > system? If so, the crash may be related to an issue with DBaR at Qt 5. > You may need to update DBaR to the latest version. See [1] for > details. > > [1] http://en.community.dell.com/support-forums/software-os/f/ > 3526/t/19634253 > > > > On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: > > Hi, > > > > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the GUI. > The > > application however crashes on one of my computers when I simply click > > "File" then "Open." It seems that the crash happens when it needs to > bring > > up the dialog for selecting a file. It also happens if I do these menu > > clicks: > > > > 1. "File", "Load Window Layout" > > 2. "File", "Load State" > > 3. "File", "Save State" > > > > As you can see, the crash appears to happen whenever a directory dialog > is > > expected to appear. Should I send a crash report to diagnose this > problem? > > > > I should also mention that on another computer, this problem does NOT > appear > > for the same build of Paraview. The problem seems unique to a particular > > computer I'm using. > > > > Regards, > > Roman > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Mar 12 12:22:11 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 12 Mar 2017 12:22:11 -0400 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Roman, A crash report would be helpful. Thank you, Cory On Sat, Mar 11, 2017 at 6:49 PM, Roman Kowch wrote: > Sorry, I should have mentioned that I'm running ParaView on a Mac Pro > computer, with OS X 10.11.6. The computer does not have DBaR. > > Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the same > crash I'm seeing on this particular computer. Again, I could send a crash > report if that would help. > > > On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit > wrote: >> >> Do you have Dell Backup and Recovery (DBaR) tools installed on your >> system? If so, the crash may be related to an issue with DBaR at Qt 5. >> You may need to update DBaR to the latest version. See [1] for >> details. >> >> [1] >> http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253 >> >> >> >> On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: >> > Hi, >> > >> > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the GUI. >> > The >> > application however crashes on one of my computers when I simply click >> > "File" then "Open." It seems that the crash happens when it needs to >> > bring >> > up the dialog for selecting a file. It also happens if I do these menu >> > clicks: >> > >> > 1. "File", "Load Window Layout" >> > 2. "File", "Load State" >> > 3. "File", "Save State" >> > >> > As you can see, the crash appears to happen whenever a directory dialog >> > is >> > expected to appear. Should I send a crash report to diagnose this >> > problem? >> > >> > I should also mention that on another computer, this problem does NOT >> > appear >> > for the same build of Paraview. The problem seems unique to a particular >> > computer I'm using. >> > >> > Regards, >> > Roman >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From sebastien.jourdain at kitware.com Sun Mar 12 14:12:31 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Sun, 12 Mar 2017 12:12:31 -0600 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Are you sure, there is no twisted library in your system python? On Fri, Mar 10, 2017 at 6:34 PM, Rodnei Couto wrote: > My version was downloaded from the official site > > ParaView-5.3.0-RC3-Qt5-OpenGL2-MPI-Linux-64bit > > Cheers, > > -- > Rodnei Couto | (55 21) 98749-9885 > > On Fri, Mar 10, 2017 at 6:36 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> What version of ParaView are you using? One you built yourself (if so, >> how old), or a release binary? >> >> >> On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto >> wrote: >> >>> Hi, >>> >>> Thanks for the answer. >>> >>> I completely removed the twisted from my machine and the error continue. >>> In fact the error occurred before his installation. I installed twitted to >>> try to solve it >>> >>> Any other ideas? >>> >>> Cheers, >>> >>> >>> -- >>> Rodnei Couto | (55 21) 98749-9885 >>> >>> On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < >>> scott.wittenburg at kitware.com> wrote: >>> >>>> Did you try to set up your own version of twisted in your system >>>> python? When you illustrated how twisted was properly set up, you did it >>>> with "python", but your start script runs pvpython. I wonder if maybe your >>>> system python twisted is conflicting (or overriding) with the one provided >>>> by pvpython? That's just a guess based on a quick read. >>>> >>>> Hope this helps, >>>> Scott >>>> >>>> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto >>>> wrote: >>>> >>>>> I set up my environment as indicated in http://kitware.github.io/pa >>>>> raviewweb/docs/ubuntu_14_04.html >>>>> >>>>> My operational system is Ubuntu 64 14_04 LTS. >>>>> >>>>> When I try to run my start.sh, I get an error: >>>>> >>>>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>>>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>>>> from twisted.internet import reactor, defer >>>>> ImportError: No module named twisted.internet >>>>> >>>>> i think the twisted is properly installed in my environment, as can be >>>>> seen below: >>>>> >>>>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>>>> >>>>> >>>>> >>>>> >>>>> My start.sh code is: >>>>> >>>>> #!/bin/bash >>>>> export DISPLAY=:0.0 >>>>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>>>> >>>>> >>>>> Can anybody help me? I do not know what else I can do >>>>> >>>>> Cheers, >>>>> >>>>> ? >>>>> >>>>> Rodnei Couto | (55 21) 98749-9885 >>>>> ? >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Mar 13 04:43:50 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 13 Mar 2017 10:43:50 +0200 (EET) Subject: [Paraview] place of colormap ... In-Reply-To: <51841.78.190.99.135.1487320975.squirrel@webmail.be.itu.edu.tr> References: <51841.78.190.99.135.1487320975.squirrel@webmail.be.itu.edu.tr> Message-ID: <50912.78.182.90.145.1489394630.squirrel@webmail.be.itu.edu.tr> Hi, I just want to add additional color map to ParaView but I don't have access to GUI (it is installed to a cluster with NVIDIA EGL support). So, I just wonder that which file must be edited to include colormap manually. Is it lib/site-packages/paraview/ColorMaps.xml? If so I could not see my new colormap in that file when I look at my laptop installation. It must be somewhere else but where? Thanks, --ufuk From markus.held at uibk.ac.at Mon Mar 13 06:43:55 2017 From: markus.held at uibk.ac.at (markus) Date: Mon, 13 Mar 2017 11:43:55 +0100 Subject: [Paraview] 3d Contour plot on cylindrical grid - inaccurate contours with prefered direction in toroidal angle Message-ID: <58C677EB.4080306@uibk.ac.at> Dear all, i'm for a long time experiencing a contour plot problem in 3d. Our scalar data is on a cylindrical (R,Z,\varphi) grid. A 3d contour of the data produces correct "2d contours" in the RZ plane, but the contours are elongated in the \varphi direction, even if the data prefers another direction. Image here: ftp://ftp.uibk.ac.at/private/c7441143_20170403_7512b21ed0886d37bdf38b41d4056946 The prefered direction is aligned to a given vector field. Is there a way to improve the 3d contours with a filter in paraview or maybe with the help of the given vector field? best regards markus From dennis_conklin at goodyear.com Mon Mar 13 08:12:51 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Mon, 13 Mar 2017 12:12:51 +0000 Subject: [Paraview] Field value question from a user Message-ID: Alan, Wouldn't it be possible to use ForceTime filter on the dataset at your desired timepoint, then make it and the original dataset as 2 inputs to a programmable filter. You should then be able to subtract the variable from the two inputs and get what you want. Am I missing somehow that this wouldn't work? Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Mon Mar 13 08:18:28 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 13 Mar 2017 13:18:28 +0100 Subject: [Paraview] Field value question from a user In-Reply-To: References: Message-ID: That's exactly how the force time filter is expected to be used. It could be more easy to use a PythonCalculator instead of a Programmable Filter. to obtain the same resultats. Regards, Mathieu Westphal On Mon, Mar 13, 2017 at 1:12 PM, Dennis Conklin wrote: > Alan, > > > > Wouldn?t it be possible to use ForceTime filter on the dataset at your > desired timepoint, then make it and the original dataset as 2 inputs to a > programmable filter. You should then be able to subtract the variable > from the two inputs and get what you want. > > > > Am I missing somehow that this wouldn?t work? > > Dennis > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rskowch at gmail.com Mon Mar 13 10:45:56 2017 From: rskowch at gmail.com (Roman Kowch) Date: Mon, 13 Mar 2017 10:45:56 -0400 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: I attached a crash report here. On Sun, Mar 12, 2017 at 12:22 PM, Cory Quammen wrote: > Roman, > > A crash report would be helpful. > > Thank you, > Cory > > On Sat, Mar 11, 2017 at 6:49 PM, Roman Kowch wrote: > > Sorry, I should have mentioned that I'm running ParaView on a Mac Pro > > computer, with OS X 10.11.6. The computer does not have DBaR. > > > > Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the same > > crash I'm seeing on this particular computer. Again, I could send a crash > > report if that would help. > > > > > > On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit > > wrote: > >> > >> Do you have Dell Backup and Recovery (DBaR) tools installed on your > >> system? If so, the crash may be related to an issue with DBaR at Qt 5. > >> You may need to update DBaR to the latest version. See [1] for > >> details. > >> > >> [1] > >> http://en.community.dell.com/support-forums/software-os/f/ > 3526/t/19634253 > >> > >> > >> > >> On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: > >> > Hi, > >> > > >> > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the > GUI. > >> > The > >> > application however crashes on one of my computers when I simply click > >> > "File" then "Open." It seems that the crash happens when it needs to > >> > bring > >> > up the dialog for selecting a file. It also happens if I do these menu > >> > clicks: > >> > > >> > 1. "File", "Load Window Layout" > >> > 2. "File", "Load State" > >> > 3. "File", "Save State" > >> > > >> > As you can see, the crash appears to happen whenever a directory > dialog > >> > is > >> > expected to appear. Should I send a crash report to diagnose this > >> > problem? > >> > > >> > I should also mention that on another computer, this problem does NOT > >> > appear > >> > for the same build of Paraview. The problem seems unique to a > particular > >> > computer I'm using. > >> > > >> > Regards, > >> > Roman > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Search the list archives at: http://markmail.org/search/?q=ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Process: paraview [22669] Path: /Applications/paraview.app/Contents/MacOS/paraview Identifier: org.paraview.ParaView Version: 5.3.0 (???) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: paraview [22669] User ID: 947211430 Date/Time: 2017-03-13 10:36:24.649 -0400 OS Version: Mac OS X 10.11.6 (15G1217) Report Version: 11 Anonymous UUID: 6F539D48-A119-4184-44C0-DDBA358D3FA2 Time Awake Since Boot: 1100000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0: --> __TEXT 000000010f9b0000-000000010fa59000 [ 676K] r-x/rwx SM=COW /Applications/paraview.app/Contents/MacOS/paraview Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x00007fff88a7a132 strlen + 18 1 libvtkPVClientServerCoreDefault-pv5.3.1.dylib 0x00000001194e8da9 vtkPVMacFileInformationHelper::GetMountedVolumes() + 585 2 libvtkPVClientServerCoreDefault-pv5.3.1.dylib 0x00000001194e327e vtkPVFileInformation::GetSpecialDirectories() + 1198 3 libvtkPVServerImplementationCore-pv5.3.1.dylib 0x000000011113becc vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) + 220 4 libvtkPVServerImplementationCore-pv5.3.1.dylib 0x000000011113c037 vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 39 5 libvtkPVServerManagerCore-pv5.3.1.dylib 0x0000000111022f6b vtkSMProxy::GatherInformation(vtkPVInformation*) + 107 6 libvtkpqCore-pv5.3.1.dylib 0x00000001100fe5ee pqFileDialogFavoriteModel::pqImplementation::pqImplementation(pqServer*) + 174 7 libvtkpqCore-pv5.3.1.dylib 0x00000001100fe02e pqFileDialogFavoriteModel::pqFileDialogFavoriteModel(pqServer*, QObject*) + 62 8 libvtkpqCore-pv5.3.1.dylib 0x00000001100fa646 pqFileDialog::pqImplementation::pqImplementation(pqFileDialog*, pqServer*) + 102 9 libvtkpqCore-pv5.3.1.dylib 0x00000001100ef0c8 pqFileDialog::pqFileDialog(pqServer*, QWidget*, QString const&, QString const&, QString const&) + 104 10 libvtkpqApplicationComponents-pv5.3.1.dylib 0x000000010fae4c56 pqLoadDataReaction::loadData() + 374 11 libvtkpqApplicationComponents-pv5.3.1.dylib 0x000000010fb59c4c pqLoadDataReaction::onTriggered() + 44 12 org.qt-project.QtCore 0x00000001139190cc QMetaObject::activate(QObject*, int, int, void**) + 3020 13 org.qt-project.QtWidgets 0x0000000112c433d7 QAction::activate(QAction::ActionEvent) + 263 14 org.qt-project.QtWidgets 0x0000000112d3ad59 0x112c3a000 + 1051993 15 org.qt-project.QtWidgets 0x0000000112d3be00 QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 272 16 org.qt-project.QtWidgets 0x0000000112e161cf QToolButton::mouseReleaseEvent(QMouseEvent*) + 15 17 org.qt-project.QtWidgets 0x0000000112c8e5d3 QWidget::event(QEvent*) + 1571 18 org.qt-project.QtWidgets 0x0000000112d3bb50 QAbstractButton::event(QEvent*) + 160 19 org.qt-project.QtWidgets 0x0000000112e167f5 QToolButton::event(QEvent*) + 325 20 org.qt-project.QtWidgets 0x0000000112c4ca76 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 294 21 org.qt-project.QtWidgets 0x0000000112c4fe73 QApplication::notify(QObject*, QEvent*) + 8339 22 org.qt-project.QtCore 0x00000001138e3264 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 23 org.qt-project.QtWidgets 0x0000000112c4d42a QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) + 970 24 org.qt-project.QtWidgets 0x0000000112cb0852 0x112c3a000 + 485458 25 org.qt-project.QtWidgets 0x0000000112caf82e 0x112c3a000 + 481326 26 org.qt-project.QtWidgets 0x0000000112c4ca76 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 294 27 org.qt-project.QtWidgets 0x0000000112c4dfd8 QApplication::notify(QObject*, QEvent*) + 504 28 org.qt-project.QtCore 0x00000001138e3264 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 29 org.qt-project.QtGui 0x0000000113235f2d QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 2877 30 org.qt-project.QtGui 0x000000011321e03b QWindowSystemInterface::sendWindowSystemEvents(QFlags) + 203 31 libqcocoa.dylib 0x0000000123538f21 0x123513000 + 155425 32 com.apple.CoreFoundation 0x00007fff872327e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 33 com.apple.CoreFoundation 0x00007fff87211f1c __CFRunLoopDoSources0 + 556 34 com.apple.CoreFoundation 0x00007fff8721143f __CFRunLoopRun + 927 35 com.apple.CoreFoundation 0x00007fff87210e38 CFRunLoopRunSpecific + 296 36 com.apple.HIToolbox 0x00007fff8eb6c935 RunCurrentEventLoopInMode + 235 37 com.apple.HIToolbox 0x00007fff8eb6c677 ReceiveNextEventCommon + 184 38 com.apple.HIToolbox 0x00007fff8eb6c5af _BlockUntilNextEventMatchingListInModeWithFilter + 71 39 com.apple.AppKit 0x00007fff8d2f8df6 _DPSNextEvent + 1067 40 com.apple.AppKit 0x00007fff8d2f8226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 41 com.apple.AppKit 0x00007fff8d2ecd80 -[NSApplication run] + 682 42 libqcocoa.dylib 0x0000000123537e2f 0x123513000 + 151087 43 org.qt-project.QtCore 0x00000001138df421 QEventLoop::exec(QFlags) + 417 44 org.qt-project.QtCore 0x00000001138e38d5 QCoreApplication::exec() + 341 45 org.paraview.ParaView 0x000000010f9bf5bc main + 460 46 libdyld.dylib 0x00007fff8c3265ad start + 1 Thread 1:: Dispatch queue: com.apple.root.default-qos 0 libsystem_kernel.dylib 0x00007fff8f0b6fae semaphore_wait_trap + 10 1 libsystem_platform.dylib 0x00007fff87caece8 _os_semaphore_wait + 16 2 libdispatch.dylib 0x00007fff9ab4b994 _dispatch_barrier_sync_f_slow + 594 3 com.apple.AppKit 0x00007fff8d4442ee NSCGSDisableUpdates + 213 4 com.apple.AppKit 0x00007fff8d444124 NSCGSTransactionRunPreCommitActionsForOrder_ + 156 5 com.apple.AppKit 0x00007fff8d44406b NSCGSTransactionRunPreCommitActions_ + 21 6 com.apple.AppKit 0x00007fff8d44404a __39+[_NSCGSTransaction currentTransaction]_block_invoke + 34 7 com.apple.QuartzCore 0x00007fff9ab9af71 CA::Transaction::run_commit_handlers(CATransactionPhase) + 85 8 com.apple.QuartzCore 0x00007fff9ab9a7ce CA::Context::commit_transaction(CA::Transaction*) + 1090 9 com.apple.QuartzCore 0x00007fff9ab9a0ec CA::Transaction::commit() + 508 10 com.apple.AppKit 0x00007fff8d4df5ae -[NSAnimation(NSInternal) _advanceTimeWithDisplayLink:] + 429 11 com.apple.AppKit 0x00007fff8d4df2ea -[NSScreenDisplayLink _fire] + 439 12 com.apple.CoreFoundation 0x00007fff8721aaf4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 13 com.apple.CoreFoundation 0x00007fff8721a783 __CFRunLoopDoTimer + 1075 14 com.apple.CoreFoundation 0x00007fff8721a2da __CFRunLoopDoTimers + 298 15 com.apple.CoreFoundation 0x00007fff872117d1 __CFRunLoopRun + 1841 16 com.apple.CoreFoundation 0x00007fff87210e38 CFRunLoopRunSpecific + 296 17 com.apple.Foundation 0x00007fff97df0ed9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270 18 com.apple.AppKit 0x00007fff8d442d72 -[NSAnimation(NSInternal) _runBlocking] + 398 19 com.apple.AppKit 0x00007fff8d442bcb -[NSAnimation(NSInternal) _animationThread] + 66 20 libdispatch.dylib 0x00007fff9ab4893d _dispatch_call_block_and_release + 12 21 libdispatch.dylib 0x00007fff9ab3d40b _dispatch_client_callout + 8 22 libdispatch.dylib 0x00007fff9ab4129b _dispatch_root_queue_drain + 1890 23 libdispatch.dylib 0x00007fff9ab40b00 _dispatch_worker_thread3 + 91 24 libsystem_pthread.dylib 0x00007fff98a324de _pthread_wqthread + 1129 25 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 2:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff8f0bdefa kevent_qos + 10 1 libdispatch.dylib 0x00007fff9ab43165 _dispatch_mgr_invoke + 216 2 libdispatch.dylib 0x00007fff9ab42dcd _dispatch_mgr_thread + 52 Thread 3: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 5:: Dispatch queue: NSCGSDisableUpdates 0 libsystem_kernel.dylib 0x00007fff8f0b6f72 mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff8f0b63b3 mach_msg + 55 2 com.apple.CoreGraphics 0x00007fff901639c1 _CGSReenableUpdateForConnection + 92 3 com.apple.CoreGraphics 0x00007fff90163691 CGSReenableUpdateToken + 469 4 libdispatch.dylib 0x00007fff9ab4893d _dispatch_call_block_and_release + 12 5 libdispatch.dylib 0x00007fff9ab3d40b _dispatch_client_callout + 8 6 libdispatch.dylib 0x00007fff9ab4203b _dispatch_queue_drain + 754 7 libdispatch.dylib 0x00007fff9ab48707 _dispatch_queue_invoke + 549 8 libdispatch.dylib 0x00007fff9ab3d40b _dispatch_client_callout + 8 9 libdispatch.dylib 0x00007fff9ab4129b _dispatch_root_queue_drain + 1890 10 libdispatch.dylib 0x00007fff9ab40b00 _dispatch_worker_thread3 + 91 11 libsystem_pthread.dylib 0x00007fff98a324de _pthread_wqthread + 1129 12 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 7: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 8: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 9: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 10: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 11: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 12: 0 libsystem_kernel.dylib 0x00007fff8f0bd5e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff98a32578 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff98a30341 start_wqthread + 13 Thread 13:: com.apple.NSEventThread 0 libsystem_kernel.dylib 0x00007fff8f0b6f72 mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff8f0b63b3 mach_msg + 55 2 com.apple.CoreFoundation 0x00007fff87212124 __CFRunLoopServiceMachPort + 212 3 com.apple.CoreFoundation 0x00007fff872115ec __CFRunLoopRun + 1356 4 com.apple.CoreFoundation 0x00007fff87210e38 CFRunLoopRunSpecific + 296 5 com.apple.AppKit 0x00007fff8d44ed95 _NSEventThread + 149 6 libsystem_pthread.dylib 0x00007fff98a3299d _pthread_body + 131 7 libsystem_pthread.dylib 0x00007fff98a3291a _pthread_start + 168 8 libsystem_pthread.dylib 0x00007fff98a30351 thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x00007fff875e8e00 rbp: 0x00007fff5024ca80 rsp: 0x00007fff5024ca80 r8: 0x0000000000000006 r9: 0x0000000000000002 r10: 0x00000000b1ccaed9 r11: 0x00007fe657000000 r12: 0x00007fff5024ccb0 r13: 0x00007fff5024caf8 r14: 0x00007fff5024cb10 r15: 0x00007fff5024cb10 rip: 0x00007fff88a7a132 rfl: 0x0000000000010246 cr2: 0x0000000000000000 Logical CPU: 2 Error Code: 0x00000004 Trap Number: 14 Binary Images: 0x10f9b0000 - 0x10fa58ff3 +org.paraview.ParaView (5.3.0 - ???) <6F803F0A-71F8-301A-A39F-E2CFC15F114B> /Applications/paraview.app/Contents/MacOS/paraview 0x10fa65000 - 0x10fbcdff3 +libvtkpqApplicationComponents-pv5.3.1.dylib (0) <3768E0AE-BD21-38D3-8A0C-53062D65AFFC> /Applications/paraview.app/Contents/Libraries/libvtkpqApplicationComponents-pv5.3.1.dylib 0x10fc89000 - 0x10fc8bfff +libvtkUtilitiesPythonInitializer-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkUtilitiesPythonInitializer-pv5.3.1.dylib 0x10fc8d000 - 0x10ff54ffb +libvtkpqComponents-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkpqComponents-pv5.3.1.dylib 0x110074000 - 0x110099ffb +libvtkpqPython-pv5.3.1.dylib (0) <4324B76E-EFC8-3131-9C0D-0E682F47B500> /Applications/paraview.app/Contents/Libraries/libvtkpqPython-pv5.3.1.dylib 0x1100b2000 - 0x1101b3ffb +libvtkpqCore-pv5.3.1.dylib (0) <1B6C8EB0-3170-335C-9164-9EA2DB942A43> /Applications/paraview.app/Contents/Libraries/libvtkpqCore-pv5.3.1.dylib 0x11024a000 - 0x110b81ffb +libvtkPVServerManagerApplication-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerApplication-pv5.3.1.dylib 0x110e9f000 - 0x110ef2ffb +libvtkpqWidgets-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkpqWidgets-pv5.3.1.dylib 0x110f42000 - 0x110f86fff +libQtTesting.dylib (0) <504E7839-5618-3EEF-B8BA-4FE0FDE459D3> /Applications/paraview.app/Contents/Libraries/libQtTesting.dylib 0x110fbf000 - 0x1110a2ff3 +libvtkPVServerManagerCore-pv5.3.1.dylib (0) <48D86CAA-1916-3E0E-B634-AF0681DDA96E> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerCore-pv5.3.1.dylib 0x11112a000 - 0x111186ff7 +libvtkPVServerImplementationCore-pv5.3.1.dylib (0) <6A261DCB-176F-36F4-A130-051F8B8C5821> /Applications/paraview.app/Contents/Libraries/libvtkPVServerImplementationCore-pv5.3.1.dylib 0x1111d8000 - 0x111258ff7 +libprotobuf.dylib (0) <65DB4145-B589-38C6-B782-1E41E5A6B5D2> /Applications/paraview.app/Contents/Libraries/libprotobuf.dylib 0x1112aa000 - 0x1112aafe7 +cl_kernels (???) cl_kernels 0x1112ac000 - 0x11132eff7 +libvtkPVClientServerCoreCore-pv5.3.1.dylib (0) <85E9890A-E7E7-3015-AFCA-E038DE48FA9E> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreCore-pv5.3.1.dylib 0x11137c000 - 0x111382ff7 +libvtkFiltersProgrammable-pv5.3.1.dylib (0) <722D44B2-7A35-3E57-A588-2E4AC7FCE3E7> /Applications/paraview.app/Contents/Libraries/libvtkFiltersProgrammable-pv5.3.1.dylib 0x11138d000 - 0x1113afff3 +libvtkGUISupportQt-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkGUISupportQt-pv5.3.1.dylib 0x1113dc000 - 0x11140fff7 +libvtkPVVTKExtensionsCore-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsCore-pv5.3.1.dylib 0x111444000 - 0x111457fff +libvtkPVCommon-pv5.3.1.dylib (0) <2FAA9764-5971-3B16-BF25-F2501B6A21C2> /Applications/paraview.app/Contents/Libraries/libvtkPVCommon-pv5.3.1.dylib 0x111472000 - 0x11148fffb +libvtkClientServer-pv5.3.1.dylib (0) <84DF1B4D-63AB-33DC-AA12-D6A0807B58A6> /Applications/paraview.app/Contents/Libraries/libvtkClientServer-pv5.3.1.dylib 0x1114a9000 - 0x1114b4ff7 +libvtkParallelMPI-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkParallelMPI-pv5.3.1.dylib 0x1114c1000 - 0x1114c6ff3 +libvtkPythonInterpreter-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPythonInterpreter-pv5.3.1.dylib 0x1114d4000 - 0x111608ff7 +org.python.python (2.7.13, [c] 2001-2016 Python Software Foundation. - 2.7.13) /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Python 0x1116f0000 - 0x111749ff7 +libvtkFiltersParallel-pv5.3.1.dylib (0) <90A90A90-2CD6-388E-9EC0-06E6B0FF8123> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallel-pv5.3.1.dylib 0x111793000 - 0x1118a4ff7 +libvtkRenderingOpenGL2-pv5.3.1.dylib (0) <42571086-FEF3-3699-855B-40F47C78D594> /Applications/paraview.app/Contents/Libraries/libvtkRenderingOpenGL2-pv5.3.1.dylib 0x111929000 - 0x11196cff3 +libvtkParallelCore-pv5.3.1.dylib (0) <7948FC3D-113D-3DE0-8E6B-1A36C11AA70B> /Applications/paraview.app/Contents/Libraries/libvtkParallelCore-pv5.3.1.dylib 0x111985000 - 0x1119d9fff +libvtkIOLegacy-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOLegacy-pv5.3.1.dylib 0x111a09000 - 0x111a4bfff +libvtkFiltersModeling-pv5.3.1.dylib (0) <3CC4DD6C-7DB3-31CF-9C1E-980650C1B8F4> /Applications/paraview.app/Contents/Libraries/libvtkFiltersModeling-pv5.3.1.dylib 0x111a78000 - 0x111b1cffb +libvtkFiltersExtraction-pv5.3.1.dylib (0) <1A6A1291-1C0B-3803-A9B8-0D216A71CF7D> /Applications/paraview.app/Contents/Libraries/libvtkFiltersExtraction-pv5.3.1.dylib 0x111b4e000 - 0x111b5eff7 +libvtkIOXMLParser-pv5.3.1.dylib (0) <85502308-25BE-3293-92CA-6332C8ECB359> /Applications/paraview.app/Contents/Libraries/libvtkIOXMLParser-pv5.3.1.dylib 0x111b72000 - 0x111bb3ff3 +libvtkIOCore-pv5.3.1.dylib (0) <365E82EC-F173-3A9C-B300-2E8AE9866C01> /Applications/paraview.app/Contents/Libraries/libvtkIOCore-pv5.3.1.dylib 0x111be1000 - 0x111d18ff3 +libvtkIOImage-pv5.3.1.dylib (0) <47E7E005-177E-344E-A199-C5AFE75F725B> /Applications/paraview.app/Contents/Libraries/libvtkIOImage-pv5.3.1.dylib 0x111d64000 - 0x111e5afff +libvtkRenderingCore-pv5.3.1.dylib (0) <3C9046CA-9208-3AFF-8BA2-8264AFD2A106> /Applications/paraview.app/Contents/Libraries/libvtkRenderingCore-pv5.3.1.dylib 0x111ef3000 - 0x111f3bfff +libvtkFiltersGeometry-pv5.3.1.dylib (0) <420E16DF-E499-3608-9E22-A1E716380691> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeometry-pv5.3.1.dylib 0x111f62000 - 0x111fa9fff +libvtkFiltersSources-pv5.3.1.dylib (0) <3193DACE-6CCA-372E-9AA3-283E657EE1A6> /Applications/paraview.app/Contents/Libraries/libvtkFiltersSources-pv5.3.1.dylib 0x111fdd000 - 0x11221aff3 +libvtkFiltersGeneral-pv5.3.1.dylib (0) <9FA99CA2-D378-3B7C-A66B-EC7047293E58> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeneral-pv5.3.1.dylib 0x1122b7000 - 0x1126aaffb +libvtkFiltersCore-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkFiltersCore-pv5.3.1.dylib 0x1127af000 - 0x1127fcff7 +libvtkCommonExecutionModel-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkCommonExecutionModel-pv5.3.1.dylib 0x112857000 - 0x112ab8fff +libvtkCommonDataModel-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkCommonDataModel-pv5.3.1.dylib 0x112ba9000 - 0x112bbaffb +libvtkCommonMisc-pv5.3.1.dylib (0) <86EADAFF-92A7-31AA-8C51-15C77B694133> /Applications/paraview.app/Contents/Libraries/libvtkCommonMisc-pv5.3.1.dylib 0x112bc6000 - 0x112bd2ff3 +libvtkCommonSystem-pv5.3.1.dylib (0) <77F9B844-4F09-31D2-8E92-BDA7C146C417> /Applications/paraview.app/Contents/Libraries/libvtkCommonSystem-pv5.3.1.dylib 0x112be5000 - 0x112bfdff3 +libvtkCommonTransforms-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkCommonTransforms-pv5.3.1.dylib 0x112c16000 - 0x112c2eff7 +libvtkCommonMath-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkCommonMath-pv5.3.1.dylib 0x112c3a000 - 0x1130b4fff +org.qt-project.QtWidgets (5.6 - 5.6.2) <1E6630D7-05AF-3636-AB09-53F6A3F4B9C6> /opt/local/libexec/*/QtWidgets.framework/Versions/5/QtWidgets 0x11320c000 - 0x113603fe3 +org.qt-project.QtGui (5.6 - 5.6.2) <894C790B-D657-3315-A5A0-58DA2C92A57D> /opt/local/libexec/*/QtGui.framework/Versions/5/QtGui 0x1136ee000 - 0x113ae7fff +org.qt-project.QtCore (5.6 - 5.6.2) <0787C21D-984A-35DB-B5C8-086DF8B2CE45> /opt/local/libexec/*/QtCore.framework/Versions/5/QtCore 0x113b97000 - 0x113bbcff7 +libvtkWrappingPython27Core-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkWrappingPython27Core-pv5.3.1.dylib 0x113bd6000 - 0x113f04ff7 +libvtkCommonCore-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkCommonCore-pv5.3.1.dylib 0x114047000 - 0x114075ff7 +libvtksys-pv5.3.1.dylib (0) <064F3C44-3ED2-3744-A049-5496DDBB6F25> /Applications/paraview.app/Contents/Libraries/libvtksys-pv5.3.1.dylib 0x114094000 - 0x1140aefff +libtbb.dylib (0) <8C10F751-8A33-3331-8629-7203F64C5DE2> /opt/local/lib/libtbb.dylib 0x1140d7000 - 0x114108ff7 +libvtkPVCinemaReader-pv5.3.1.dylib (0) <94B9EFEC-8101-3595-91AD-6174642DC360> /Applications/paraview.app/Contents/Libraries/libvtkPVCinemaReader-pv5.3.1.dylib 0x11411f000 - 0x11419aff7 +org.qt-project.QtHelp (5.6 - 5.6.2) <2D7E59AD-8A46-3984-9B77-6C136BEDD6FB> /opt/local/libexec/*/QtHelp.framework/Versions/5/QtHelp 0x1141be000 - 0x1141f9ffb +libvtkPVAnimation-pv5.3.1.dylib (0) <70DAD889-92B9-341C-B0A4-62DCE85E05DB> /Applications/paraview.app/Contents/Libraries/libvtkPVAnimation-pv5.3.1.dylib 0x114227000 - 0x11425dffb +libvtkPVServerManagerDefault-pv5.3.1.dylib (0) <23382738-3560-39AC-92F9-97BE49CB4907> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerDefault-pv5.3.1.dylib 0x114283000 - 0x114349fff +libvtkPVServerManagerRendering-pv5.3.1.dylib (0) <8D3B9B96-27C2-33E3-9749-E75B18E3C82B> /Applications/paraview.app/Contents/Libraries/libvtkPVServerManagerRendering-pv5.3.1.dylib 0x114395000 - 0x1143b4ffb +libvtkPVServerImplementationRendering-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPVServerImplementationRendering-pv5.3.1.dylib 0x1143bd000 - 0x114469fff +libvtkPVClientServerCoreRendering-pv5.3.1.dylib (0) <832D3270-7370-33FC-8884-59A972913536> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreRendering-pv5.3.1.dylib 0x114515000 - 0x1146ceffb +libvtkPVVTKExtensionsDefault-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsDefault-pv5.3.1.dylib 0x114790000 - 0x1147afff7 +libvtkFiltersParallelFlowPaths-pv5.3.1.dylib (0) <5755E806-0FF5-3446-B180-A1F4E041C407> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelFlowPaths-pv5.3.1.dylib 0x1147ca000 - 0x114816ffb +libvtkFiltersFlowPaths-pv5.3.1.dylib (0) <7E2DAD32-1D62-392B-8D56-724A23738FD4> /Applications/paraview.app/Contents/Libraries/libvtkFiltersFlowPaths-pv5.3.1.dylib 0x114847000 - 0x11485cff3 +libvtkFiltersParallelStatistics-pv5.3.1.dylib (0) <7886E06F-EC2B-3C62-9B58-1D210689081E> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelStatistics-pv5.3.1.dylib 0x114876000 - 0x1148d6ff7 +libvtkIOEnSight-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOEnSight-pv5.3.1.dylib 0x1148ef000 - 0x11491eff7 +libvtkIOImport-pv5.3.1.dylib (0) <0714EF8B-A08F-3447-9326-46DC8F5D0681> /Applications/paraview.app/Contents/Libraries/libvtkIOImport-pv5.3.1.dylib 0x114931000 - 0x11493fffb +libvtkIOMPIImage-pv5.3.1.dylib (0) <962583FE-9E8F-3A12-9CF0-B09BC443ECF0> /Applications/paraview.app/Contents/Libraries/libvtkIOMPIImage-pv5.3.1.dylib 0x11494b000 - 0x114997ff7 +libvtkIOParallel-pv5.3.1.dylib (0) <4A58D40A-E3E8-3429-B18E-FC888714D785> /Applications/paraview.app/Contents/Libraries/libvtkIOParallel-pv5.3.1.dylib 0x1149bc000 - 0x1149e4ff7 +libvtkjsoncpp-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkjsoncpp-pv5.3.1.dylib 0x1149fd000 - 0x114b29ff3 +libvtkIOGeometry-pv5.3.1.dylib (0) <4E9CBF6A-9A29-34E8-A651-84AE0BED240C> /Applications/paraview.app/Contents/Libraries/libvtkIOGeometry-pv5.3.1.dylib 0x114b69000 - 0x114bb3ff7 +libvtkIONetCDF-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIONetCDF-pv5.3.1.dylib 0x114bd5000 - 0x114beaff7 +libvtkIOParallelExodus-pv5.3.1.dylib (0) <388EF0D6-5663-3D42-95AF-C0495A238DB6> /Applications/paraview.app/Contents/Libraries/libvtkIOParallelExodus-pv5.3.1.dylib 0x114bfe000 - 0x114c6eff3 +libvtkIOExodus-pv5.3.1.dylib (0) <0886FE57-FF85-33A4-9862-55F8069C2F1E> /Applications/paraview.app/Contents/Libraries/libvtkIOExodus-pv5.3.1.dylib 0x114ca1000 - 0x114ce0ffb +libvtkexoIIc-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkexoIIc-pv5.3.1.dylib 0x114ceb000 - 0x114cf8fff +libnetcdf_c++.4.dylib (0) <73E94D3D-7731-36E3-ADE2-FB8832AF2440> /opt/local/lib/libnetcdf_c++.4.dylib 0x114d08000 - 0x114d9cfff +libnetcdf.11.dylib (0) <0B7A9C01-7EBB-3657-B290-479F660F6472> /opt/local/lib/libnetcdf.11.dylib 0x117e1b000 - 0x117e28fff +libvtkIOParallelXML-pv5.3.1.dylib (0) <5B15AB43-2F50-3E1E-9385-E547CE20BBE0> /Applications/paraview.app/Contents/Libraries/libvtkIOParallelXML-pv5.3.1.dylib 0x117e3f000 - 0x117f08ff3 +libvtkPVVTKExtensionsRendering-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsRendering-pv5.3.1.dylib 0x117f7e000 - 0x118066ff3 +libvtkChartsCore-pv5.3.1.dylib (0) <43464D21-DA1D-345C-B8A4-ACD0866DC7C8> /Applications/paraview.app/Contents/Libraries/libvtkChartsCore-pv5.3.1.dylib 0x1180ae000 - 0x1180c5ff7 +libvtkFiltersGeneric-pv5.3.1.dylib (0) <4755E8D5-F5CF-3A1D-902C-87A280BC7F44> /Applications/paraview.app/Contents/Libraries/libvtkFiltersGeneric-pv5.3.1.dylib 0x1180df000 - 0x1180fdfff +libvtkFiltersHyperTree-pv5.3.1.dylib (0) <18863FFF-A439-3F37-88F9-087DAB097221> /Applications/paraview.app/Contents/Libraries/libvtkFiltersHyperTree-pv5.3.1.dylib 0x118117000 - 0x118134ff7 +libvtkFiltersParallelMPI-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelMPI-pv5.3.1.dylib 0x118151000 - 0x11815afff +libvtkIOExportOpenGL2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOExportOpenGL2-pv5.3.1.dylib 0x118169000 - 0x11819bff3 +libvtkIOExport-pv5.3.1.dylib (0) <83020BF9-16AA-3A4B-A5D3-B589D05F018C> /Applications/paraview.app/Contents/Libraries/libvtkIOExport-pv5.3.1.dylib 0x1181b7000 - 0x1181c5fff +libvtkRenderingGL2PSOpenGL2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingGL2PSOpenGL2-pv5.3.1.dylib 0x1181d4000 - 0x1181e0ff7 +libvtkRenderingMatplotlib-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingMatplotlib-pv5.3.1.dylib 0x1181ef000 - 0x11820fff7 +libvtkRenderingParallel-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingParallel-pv5.3.1.dylib 0x11822c000 - 0x118235ff7 +libvtkRenderingVolumeAMR-pv5.3.1.dylib (0) <49781D24-25B2-3512-98D3-A6508D221809> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolumeAMR-pv5.3.1.dylib 0x11823f000 - 0x118254ff3 +libvtkFiltersAMR-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkFiltersAMR-pv5.3.1.dylib 0x11826a000 - 0x11826cfff +libIceTMPI.dylib (0) <22354530-0E7E-3C3B-8B9A-2FDA08183F8E> /Applications/paraview.app/Contents/Libraries/libIceTMPI.dylib 0x118273000 - 0x118316ff7 +libmpi.12.dylib (0) /opt/local/lib/*/libmpi.12.dylib 0x118372000 - 0x118374ff3 +libIceTGL.dylib (0) <833C79CE-E528-383D-8777-6E0C78215B7B> /Applications/paraview.app/Contents/Libraries/libIceTGL.dylib 0x11837c000 - 0x11839bfff +libIceTCore.dylib (0) <5308C2C7-B55D-31D8-BDFE-535668CBD1EE> /Applications/paraview.app/Contents/Libraries/libIceTCore.dylib 0x1183a3000 - 0x1183daff7 +libvtkDomainsChemistry-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkDomainsChemistry-pv5.3.1.dylib 0x1183ff000 - 0x118462ff3 +libvtkRenderingLabel-pv5.3.1.dylib (0) <863F1EBD-9DF0-3346-8ACE-B3A78D95ECB9> /Applications/paraview.app/Contents/Libraries/libvtkRenderingLabel-pv5.3.1.dylib 0x118485000 - 0x1184c6fff +libvtkRenderingVolumeOpenGL2-pv5.3.1.dylib (0) <6ED83EEF-F275-3421-95CB-847E9FADCA55> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolumeOpenGL2-pv5.3.1.dylib 0x1184e9000 - 0x11851cff3 +libvtkImagingMath-pv5.3.1.dylib (0) <63743A62-7B3B-3E5A-8373-610EBF636574> /Applications/paraview.app/Contents/Libraries/libvtkImagingMath-pv5.3.1.dylib 0x118537000 - 0x1185b2ffb +libvtkglew-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkglew-pv5.3.1.dylib 0x1185f0000 - 0x1185f7ff7 +libvtkViewsContext2D-pv5.3.1.dylib (0) <155FEF11-23C7-34FA-B869-9B8E15871B9F> /Applications/paraview.app/Contents/Libraries/libvtkViewsContext2D-pv5.3.1.dylib 0x118603000 - 0x118619fff +libvtkRenderingContext2D-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingContext2D-pv5.3.1.dylib 0x118638000 - 0x118648ff3 +libvtkViewsCore-pv5.3.1.dylib (0) <68245166-D03A-304E-9837-8D8F3DDAF08A> /Applications/paraview.app/Contents/Libraries/libvtkViewsCore-pv5.3.1.dylib 0x118660000 - 0x118762ff3 +libvtkInteractionWidgets-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkInteractionWidgets-pv5.3.1.dylib 0x118819000 - 0x118835ff7 +libvtkInteractionStyle-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkInteractionStyle-pv5.3.1.dylib 0x118857000 - 0x1188a8fff +libvtkFiltersStatistics-pv5.3.1.dylib (0) <5A36BD43-7504-3145-9FBF-C4D05DD49ABC> /Applications/paraview.app/Contents/Libraries/libvtkFiltersStatistics-pv5.3.1.dylib 0x1188d6000 - 0x1188edfff +libvtkImagingFourier-pv5.3.1.dylib (0) <5B70AE6E-DF18-3133-91A9-0EBBAC98F5F2> /Applications/paraview.app/Contents/Libraries/libvtkImagingFourier-pv5.3.1.dylib 0x1188fd000 - 0x118923fff +libvtkalglib-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkalglib-pv5.3.1.dylib 0x11892e000 - 0x1189b3ff3 +libvtkRenderingAnnotation-pv5.3.1.dylib (0) <3B9B2E18-E12B-3743-9FB1-1260B50B89BC> /Applications/paraview.app/Contents/Libraries/libvtkRenderingAnnotation-pv5.3.1.dylib 0x118a00000 - 0x118a28ff3 +libvtkRenderingFreeType-pv5.3.1.dylib (0) <6A059F27-01F5-30B0-BEF6-EA82E0FA9AC6> /Applications/paraview.app/Contents/Libraries/libvtkRenderingFreeType-pv5.3.1.dylib 0x118aad000 - 0x118b24ff3 +libvtkfreetype-pv5.3.1.dylib (0) <435A9322-4039-3FBF-A920-C9F32D735DB3> /Applications/paraview.app/Contents/Libraries/libvtkfreetype-pv5.3.1.dylib 0x118b39000 - 0x118dd0fff +libvtkRenderingVolume-pv5.3.1.dylib (0) <21BF1481-00CC-3833-8CD0-0538999B5DD4> /Applications/paraview.app/Contents/Libraries/libvtkRenderingVolume-pv5.3.1.dylib 0x118ff6000 - 0x119059fff +libvtkIOXML-pv5.3.1.dylib (0) <445DBBD1-66A9-3008-BE0F-6B1F0DF16A03> /Applications/paraview.app/Contents/Libraries/libvtkIOXML-pv5.3.1.dylib 0x1190a7000 - 0x1190b9ffb +libvtkCommonComputationalGeometry-pv5.3.1.dylib (0) <7557092C-0F19-3701-AB14-FB14A46143DF> /Applications/paraview.app/Contents/Libraries/libvtkCommonComputationalGeometry-pv5.3.1.dylib 0x1190d1000 - 0x119103fff +libvtkImagingSources-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkImagingSources-pv5.3.1.dylib 0x11911b000 - 0x1192feff3 +libvtkImagingCore-pv5.3.1.dylib (0) <774AD6E5-C649-3776-AE12-FC1A235400B5> /Applications/paraview.app/Contents/Libraries/libvtkImagingCore-pv5.3.1.dylib 0x119354000 - 0x119368ff3 +libvtkzlib-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkzlib-pv5.3.1.dylib 0x11936d000 - 0x119458ff7 +org.qt-project.QtNetwork (5.6 - 5.6.2) /opt/local/libexec/*/QtNetwork.framework/Versions/5/QtNetwork 0x1194a0000 - 0x1194aefff +libvtkTestingRendering-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkTestingRendering-pv5.3.1.dylib 0x1194c2000 - 0x1194f1ff7 +libvtkPVClientServerCoreDefault-pv5.3.1.dylib (0) <2D92E86E-DE87-3368-A13F-6702CD0FA466> /Applications/paraview.app/Contents/Libraries/libvtkPVClientServerCoreDefault-pv5.3.1.dylib 0x11950c000 - 0x119538ffb +org.qt-project.QtPrintSupport (5.6 - 5.6.2) <35E76AC2-8F2A-3A79-8D77-1B70B2312E6C> /opt/local/libexec/*/QtPrintSupport.framework/Versions/5/QtPrintSupport 0x11955d000 - 0x11956cfff +libvtkCommonColor-pv5.3.1.dylib (0) <04A54F01-80E8-39A8-B84A-7756DE3F0BBB> /Applications/paraview.app/Contents/Libraries/libvtkCommonColor-pv5.3.1.dylib 0x11957a000 - 0x11958cfff +libvtkDICOMParser-pv5.3.1.dylib (0) <79467DBE-B0C0-3BF8-8B28-1D7865E69116> /Applications/paraview.app/Contents/Libraries/libvtkDICOMParser-pv5.3.1.dylib 0x119599000 - 0x119613ff3 +libvtkmetaio-pv5.3.1.dylib (0) <14000A35-EC2A-3A63-BEFB-0CF369EAF586> /Applications/paraview.app/Contents/Libraries/libvtkmetaio-pv5.3.1.dylib 0x11963a000 - 0x11965aff7 +libvtkpng-pv5.3.1.dylib (0) <46D4C6D2-D088-312B-AB0A-2849D7521D1D> /Applications/paraview.app/Contents/Libraries/libvtkpng-pv5.3.1.dylib 0x119668000 - 0x1196c3ff7 +libvtktiff-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtktiff-pv5.3.1.dylib 0x1196d4000 - 0x1196f4fff +libvtkjpeg-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkjpeg-pv5.3.1.dylib 0x119701000 - 0x119711ff7 +libz.1.dylib (0) /opt/local/lib/libz.1.dylib 0x119715000 - 0x119719fff com.apple.agl (3.3.1 - AGL-3.3.1) <11FD7720-F5AC-3719-9CE7-FF8EBDF52B42> /System/Library/Frameworks/AGL.framework/Versions/A/AGL 0x119726000 - 0x11979affb +libharfbuzz.0.dylib (0) <51CE1B60-DC19-3E24-9101-6A531279762D> /opt/local/lib/libharfbuzz.0.dylib 0x1197af000 - 0x1197d2ff3 +libpng16.16.dylib (0) <08992A25-7FC6-3CA4-870A-EE3E36A6F2D8> /opt/local/lib/libpng16.16.dylib 0x1197e0000 - 0x11992cfff +libicui18n.55.dylib (0) <054B43C2-3393-3605-A3F9-273CC00548F2> /opt/local/lib/libicui18n.55.dylib 0x119a00000 - 0x119af4fff +libicuuc.55.dylib (0) <64E390EA-13D5-3A95-9443-90300A7FB2D7> /opt/local/lib/libicuuc.55.dylib 0x119b5d000 - 0x11b412fff +libicudata.55.dylib (0) /opt/local/lib/libicudata.55.dylib 0x11b417000 - 0x11b476ffb +libpcre16.0.dylib (0) <799080ED-BDC6-3FC3-BBBE-091C3A8E0459> /opt/local/lib/libpcre16.0.dylib 0x11b47c000 - 0x11b47efff +libgthread-2.0.0.dylib (0) <0E2F7512-607D-3819-9660-E282FA284B3F> /opt/local/lib/libgthread-2.0.0.dylib 0x11b481000 - 0x11b54bff3 +libglib-2.0.0.dylib (0) /opt/local/lib/libglib-2.0.0.dylib 0x11b572000 - 0x11b57bfff +libintl.8.dylib (0) <6C3DC2F0-96B8-37D8-81EF-D85A680D5245> /opt/local/lib/libintl.8.dylib 0x11b585000 - 0x11b67aff7 +libiconv.2.dylib (0) /opt/local/lib/libiconv.2.dylib 0x11b68e000 - 0x11b6f7fff +libpcre.1.dylib (0) /opt/local/lib/libpcre.1.dylib 0x11b6ff000 - 0x11b77aff3 +libfreetype.6.dylib (0) /opt/local/lib/libfreetype.6.dylib 0x11b794000 - 0x11b7b0ff3 +libgraphite2.3.dylib (0) <23FAE77A-BA4F-3C84-B687-03B7C64B3928> /opt/local/lib/libgraphite2.3.dylib 0x11b7bc000 - 0x11b7cbff7 +libbz2.1.0.dylib (0) /opt/local/lib/libbz2.1.0.dylib 0x11b7d2000 - 0x11b7f5ff3 +libvtkpugixml-pv5.3.1.dylib (0) <9F9B51A6-7E91-33FB-9F5A-E3D9716AB075> /Applications/paraview.app/Contents/Libraries/libvtkpugixml-pv5.3.1.dylib 0x11b808000 - 0x11b810ffb +libmpi_cxx.1.dylib (0) <4AD6C6E0-DE1A-3BC5-A272-27E29590C78A> /opt/local/lib/*/libmpi_cxx.1.dylib 0x11b81f000 - 0x11b82fffb +libvtklz4-pv5.3.1.dylib (0) <0B9457D1-43DF-3857-94E9-2BEFE96F5C4C> /Applications/paraview.app/Contents/Libraries/libvtklz4-pv5.3.1.dylib 0x11b834000 - 0x11b851fff +libvtkexpat-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkexpat-pv5.3.1.dylib 0x11b859000 - 0x11b8b4ff3 +libopen-rte.12.dylib (0) <18BF88AC-64A2-31D4-A684-E2D62D129EBE> /opt/local/lib/*/libopen-rte.12.dylib 0x11b8d7000 - 0x11b93efff +libopen-pal.13.dylib (0) <3887FBD0-A674-3FC1-B540-EC2D142E86F7> /opt/local/lib/*/libopen-pal.13.dylib 0x11b96e000 - 0x11b98cfff +libhwloc.5.dylib (0) <7AADDD05-A58F-364C-8E0D-7382B66D24BA> /opt/local/lib/libhwloc.5.dylib 0x11b996000 - 0x11b9daff7 +libssl.1.0.0.dylib (0) <4C9B2B06-526E-3D2C-815C-906A67984274> /opt/local/lib/libssl.1.0.0.dylib 0x11b9f9000 - 0x11bb7d7ef +libcrypto.1.0.0.dylib (0) <67CBE89C-5A49-3D33-AB6C-3F86D009D60D> /opt/local/lib/libcrypto.1.0.0.dylib 0x11bbf4000 - 0x11bca4ffb +org.qt-project.QtCLucene (5.6 - 5.6.2) <212F1667-808A-3079-A2E5-67EF705CA30A> /opt/local/libexec/*/QtCLucene.framework/Versions/5/QtCLucene 0x11bccc000 - 0x11bcf0ff3 +org.qt-project.QtSql (5.6 - 5.6.2) /opt/local/libexec/*/QtSql.framework/Versions/5/QtSql 0x11bd03000 - 0x11bd0bff7 +libvtkIOFFMPEG-pv5.3.1.dylib (0) <078EFDB8-EF3D-37D7-A5E2-F60418D0EAC2> /Applications/paraview.app/Contents/Libraries/libvtkIOFFMPEG-pv5.3.1.dylib 0x11bd19000 - 0x11bd20ff7 +libvtkIOMovie-pv5.3.1.dylib (0) <45FDF392-A99A-34AD-9586-6C0B7DF1396B> /Applications/paraview.app/Contents/Libraries/libvtkIOMovie-pv5.3.1.dylib 0x11bd2a000 - 0x11bd5fff7 +libvtkoggtheora-pv5.3.1.dylib (0) <174AEC7C-59FF-3640-B598-6C2BBE57B787> /Applications/paraview.app/Contents/Libraries/libvtkoggtheora-pv5.3.1.dylib 0x11bd66000 - 0x11bda2ff3 +libvtkIOInfovis-pv5.3.1.dylib (0) <237DD95A-E495-3C98-97A1-6D9973A00972> /Applications/paraview.app/Contents/Libraries/libvtkIOInfovis-pv5.3.1.dylib 0x11bdca000 - 0x11bdd8ff7 +libvtkIOPLY-pv5.3.1.dylib (0) <001F01DB-2BF0-3FA1-9715-50DC1BF2CD15> /Applications/paraview.app/Contents/Libraries/libvtkIOPLY-pv5.3.1.dylib 0x11bde9000 - 0x11bdfeffb +libhdf5_hl.10.dylib (0) /opt/local/lib/*/libhdf5_hl.10.dylib 0x11be0e000 - 0x11c019fff +libhdf5.10.dylib (0) <3CF979A0-AD0E-38B4-A291-6043DD728AE5> /opt/local/lib/*/libhdf5.10.dylib 0x11c053000 - 0x11c0a2ffb +libcurl.4.dylib (0) /opt/local/lib/libcurl.4.dylib 0x11c0b8000 - 0x11c132ff7 +libvtkInfovisCore-pv5.3.1.dylib (0) <52CF430A-0DCA-381E-90D8-CE487769B20F> /Applications/paraview.app/Contents/Libraries/libvtkInfovisCore-pv5.3.1.dylib 0x11c179000 - 0x11c18fffb +libvtkgl2ps-pv5.3.1.dylib (0) <3E51BC61-8E2F-3307-9650-F3101D16B197> /Applications/paraview.app/Contents/Libraries/libvtkgl2ps-pv5.3.1.dylib 0x11c193000 - 0x11c22effb +libvtkFiltersHybrid-pv5.3.1.dylib (0) <4333104A-3904-3350-A09B-B252BF9081E7> /Applications/paraview.app/Contents/Libraries/libvtkFiltersHybrid-pv5.3.1.dylib 0x11c262000 - 0x11c302fff +libvtkImagingGeneral-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkImagingGeneral-pv5.3.1.dylib 0x11c333000 - 0x11c3a8ffb +libvtkImagingHybrid-pv5.3.1.dylib (0) <9D8297BA-3604-35EC-8229-45EA84C6AA1F> /Applications/paraview.app/Contents/Libraries/libvtkImagingHybrid-pv5.3.1.dylib 0x11c3eb000 - 0x11c424ffb +libvtkImagingColor-pv5.3.1.dylib (0) <7F59DF31-95D8-3C63-ACAA-11065D9DF8F0> /Applications/paraview.app/Contents/Libraries/libvtkImagingColor-pv5.3.1.dylib 0x11c43a000 - 0x11c575fff +libvtklibxml2-pv5.3.1.dylib (0) <9ADEBDE8-2731-3368-A1D7-B1BCF4F0202A> /Applications/paraview.app/Contents/Libraries/libvtklibxml2-pv5.3.1.dylib 0x11c5a8000 - 0x11c749fff +libavformat.57.dylib (0) <4BEEB699-0F96-3ACA-AACD-EB984BAA8A0D> /opt/local/lib/libavformat.57.dylib 0x11c78d000 - 0x11d546f27 +libavcodec.57.dylib (0) <26D59431-7DF6-3E18-8CA4-95DA784B5AF4> /opt/local/lib/libavcodec.57.dylib 0x11dd84000 - 0x11ddd3fff +libavutil.55.dylib (0) <75A9A6B6-B0AA-366B-BDFD-30EA5BA7B48F> /opt/local/lib/libavutil.55.dylib 0x11de05000 - 0x11deb0fff +libswscale.4.dylib (0) /opt/local/lib/libswscale.4.dylib 0x11dec0000 - 0x11dee7fff +libswresample.2.dylib (0) <3BCB6DF6-BE2A-3F37-A6CE-DE9C19640D4C> /opt/local/lib/libswresample.2.dylib 0x11def0000 - 0x11def1fff com.apple.VideoDecodeAcceleration (1.1 - 10) <8B971772-F623-3211-8FC8-EAB8F16ECE4A> /System/Library/Frameworks/VideoDecodeAcceleration.framework/Versions/A/VideoDecodeAcceleration 0x11def7000 - 0x11df09ff7 +libxcb.1.dylib (0) <899C025C-134E-3B40-AF28-A4F0321137DB> /opt/local/lib/libxcb.1.dylib 0x11df1d000 - 0x11df1efff +libxcb-shm.0.dylib (0) /opt/local/lib/libxcb-shm.0.dylib 0x11df25000 - 0x11df28fff +libxcb-xfixes.0.dylib (0) /opt/local/lib/libxcb-xfixes.0.dylib 0x11df32000 - 0x11df33fff +libxcb-shape.0.dylib (0) /opt/local/lib/libxcb-shape.0.dylib 0x11df3d000 - 0x11e02fff3 +libX11.6.dylib (0) <358B6A86-1BAD-3978-910D-4F4BCC56BFE2> /opt/local/lib/libX11.6.dylib 0x11e05a000 - 0x11e11affb +libSDL2-2.0.0.dylib (0) <77EC2568-897C-3AB0-BE08-0DC2E8DB56F3> /opt/local/lib/libSDL2-2.0.0.dylib 0x11e159000 - 0x11e449fff +libx265.110.dylib (0) <40772C2E-F081-3828-850E-7ACDE775AC82> /opt/local/lib/libx265.110.dylib 0x11e4ed000 - 0x11e5eaff7 +libx264.148.dylib (0) <6B68CDCD-0B99-3DCF-8696-15272847611C> /opt/local/lib/libx264.148.dylib 0x11e68c000 - 0x11e703fff +libvorbisenc.2.dylib (0) /opt/local/lib/libvorbisenc.2.dylib 0x11e751000 - 0x11e775fff +libvorbis.0.dylib (0) /opt/local/lib/libvorbis.0.dylib 0x11e780000 - 0x11e783fff +libogg.0.dylib (0) /opt/local/lib/libogg.0.dylib 0x11e789000 - 0x11e7aefff +libtheoraenc.1.dylib (0) <0FCAC911-9564-37D9-9310-101836AB81D1> /opt/local/lib/libtheoraenc.1.dylib 0x11e7ba000 - 0x11e7c5fff +libtheoradec.1.dylib (0) /opt/local/lib/libtheoradec.1.dylib 0x11e7cd000 - 0x11e7deffb +libspeex.1.dylib (0) /opt/local/lib/libspeex.1.dylib 0x11e7e6000 - 0x11e808ffb +libsoxr.0.dylib (0) <7C73D8B5-0C05-31B2-ACF4-3BB48E0A55D9> /opt/local/lib/libsoxr.0.dylib 0x11e845000 - 0x11e8cdfff +libschroedinger-1.0.0.dylib (0) <965D0517-B6FD-33A8-8CD8-8C6CC98DF93C> /opt/local/lib/libschroedinger-1.0.0.dylib 0x11e8ea000 - 0x11e92affb +libopus.0.dylib (0) <4CA69B04-7907-3805-82BD-024738CA234E> /opt/local/lib/libopus.0.dylib 0x11e934000 - 0x11e959ffb +libopenjp2.7.dylib (0) /opt/local/lib/libopenjp2.7.dylib 0x11e968000 - 0x11e99dff7 +libmp3lame.0.dylib (0) <2A68B0EE-B281-37D0-9662-E107C00E0250> /opt/local/lib/libmp3lame.0.dylib 0x11e9dd000 - 0x11ea17ff7 +libmodplug.1.dylib (0) /opt/local/lib/libmodplug.1.dylib 0x11ead2000 - 0x11eae7fff +libfribidi.0.dylib (0) <604F9F8C-F13B-3FF7-A67B-FECF92B6D894> /opt/local/lib/libfribidi.0.dylib 0x11eaef000 - 0x11eb1cff7 +libfontconfig.1.dylib (0) /opt/local/lib/libfontconfig.1.dylib 0x11eb32000 - 0x11eb63ff7 +libbluray.1.dylib (0) <96509175-3B78-3BE0-B2EE-8FAC362B042D> /opt/local/lib/libbluray.1.dylib 0x11eb6e000 - 0x11eb94ff7 +libass.9.dylib (0) /opt/local/lib/libass.9.dylib 0x11eba3000 - 0x11eca9fd7 +libgnutls.30.dylib (0) <317C702B-26EE-35A0-820E-49752F385F81> /opt/local/lib/libgnutls.30.dylib 0x11ece7000 - 0x11ed03ffb +liblzma.5.dylib (0) /opt/local/lib/liblzma.5.dylib 0x11ed09000 - 0x11ed0afff +libXau.6.dylib (0) <52738584-55BC-3BB7-A64C-5D5E2F5BF75C> /opt/local/lib/libXau.6.dylib 0x11ed0f000 - 0x11ed12ff7 +libXdmcp.6.dylib (0) /opt/local/lib/libXdmcp.6.dylib 0x11ed1b000 - 0x11ed25ff7 +libXext.6.dylib (0) <98ED824E-EA93-319C-BB2B-609704693CB8> /opt/local/lib/libXext.6.dylib 0x11ed2d000 - 0x11ed33fff +libXcursor.1.dylib (0) /opt/local/lib/libXcursor.1.dylib 0x11ed3d000 - 0x11ed3efff +libXinerama.1.dylib (0) /opt/local/lib/libXinerama.1.dylib 0x11ed48000 - 0x11ed52ffb +libXi.6.dylib (0) <57DFFDC4-88B2-3B9B-BA84-1E1A463E07C0> /opt/local/lib/libXi.6.dylib 0x11ed57000 - 0x11ed5dfff +libXrandr.2.dylib (0) /opt/local/lib/libXrandr.2.dylib 0x11ed66000 - 0x11ed68fff +libXss.1.dylib (0) <6D410ED1-CEBF-3288-B5CC-FA9DC14A51C4> /opt/local/lib/libXss.1.dylib 0x11ed6f000 - 0x11ed72fff +libXxf86vm.1.dylib (0) <6F650171-C637-3330-A4EE-45AB0DF51A0C> /opt/local/lib/libXxf86vm.1.dylib 0x11ed79000 - 0x11ed7bfff com.apple.ForceFeedback (1.0.6 - 1.0.6) <2CCA0B39-2B72-3B89-B698-42A57FE59E27> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback 0x11ed87000 - 0x11ed8dffb +libXrender.1.dylib (0) <2B4FF496-35D6-3B3F-8F53-F09ED8702BCF> /opt/local/lib/libXrender.1.dylib 0x11ed95000 - 0x11ed98fff +libXfixes.3.dylib (0) <83D95B4E-EBE3-36DC-8328-EACB6261A9BA> /opt/local/lib/libXfixes.3.dylib 0x11eda0000 - 0x11edfafff +liborc-0.4.0.dylib (0) <1879D2E6-A8A5-3CE1-9485-5EA1AF8A9D26> /opt/local/lib/liborc-0.4.0.dylib 0x11ee15000 - 0x11ee2eff3 +libexpat.1.dylib (0) <63805D6E-987D-3052-8FA9-89F7771139C0> /opt/local/lib/libexpat.1.dylib 0x11ee3b000 - 0x11ef2dfff +libxml2.2.dylib (0) /opt/local/lib/libxml2.2.dylib 0x11ef5f000 - 0x11ef97ffb +libp11-kit.0.dylib (0) <5611700B-F468-35C7-8760-149429612C34> /opt/local/lib/libp11-kit.0.dylib 0x11efc4000 - 0x11eff2ffb +libidn.11.dylib (0) <5E70EC18-5955-33E1-916A-87C0E1A4FBC5> /opt/local/lib/libidn.11.dylib 0x11effd000 - 0x11f14eff3 +libunistring.2.dylib (0) <08F46D34-26BA-3BA1-B7C3-C2C75CD32700> /opt/local/lib/libunistring.2.dylib 0x11f168000 - 0x11f174fff +libtasn1.6.dylib (0) /opt/local/lib/libtasn1.6.dylib 0x11f17e000 - 0x11f1a4fff +libnettle.6.dylib (0) <619F3194-40FC-3164-9D2B-D21F8A171BCF> /opt/local/lib/libnettle.6.dylib 0x11f1c6000 - 0x11f1edff7 +libhogweed.4.dylib (0) /opt/local/lib/libhogweed.4.dylib 0x11f203000 - 0x11f27dfff +libgmp.10.dylib (0) /opt/local/lib/libgmp.10.dylib 0x11f28b000 - 0x11f290fff +libffi.6.dylib (0) /opt/local/lib/libffi.6.dylib 0x11f297000 - 0x11f29effb +libvtkDomainsChemistryOpenGL2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkDomainsChemistryOpenGL2-pv5.3.1.dylib 0x11f2aa000 - 0x11f2dfffb +libvtkFiltersParallelDIY2-pv5.3.1.dylib (0) <5C880FCA-8256-33F4-B741-20303A76EE8F> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelDIY2-pv5.3.1.dylib 0x11f2f6000 - 0x11f31bfff +libvtkFiltersParallelGeometry-pv5.3.1.dylib (0) <96A8C1F3-59E1-32D2-94D3-57371003A127> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelGeometry-pv5.3.1.dylib 0x11f33a000 - 0x11f346ff7 +libvtkFiltersParallelImaging-pv5.3.1.dylib (0) <27E29917-0092-366F-90D5-6D7518762037> /Applications/paraview.app/Contents/Libraries/libvtkFiltersParallelImaging-pv5.3.1.dylib 0x11f357000 - 0x11f35cffb +libvtkFiltersPython-pv5.3.1.dylib (0) <36745B67-8389-312D-B672-7580EBEB8984> /Applications/paraview.app/Contents/Libraries/libvtkFiltersPython-pv5.3.1.dylib 0x11f368000 - 0x11f375ff3 +libvtkFiltersVerdict-pv5.3.1.dylib (0) <0B13ABDC-6C77-3654-950B-8721EA86B84A> /Applications/paraview.app/Contents/Libraries/libvtkFiltersVerdict-pv5.3.1.dylib 0x11f385000 - 0x11f3a8ffb +libvtkverdict-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkverdict-pv5.3.1.dylib 0x11f3b9000 - 0x11f3d9fff +libvtkIOAMR-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOAMR-pv5.3.1.dylib 0x11f3f5000 - 0x11f40cff3 +libvtkIOMPIParallel-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOMPIParallel-pv5.3.1.dylib 0x11f421000 - 0x11f427fff +libvtkIOParallelLSDyna-pv5.3.1.dylib (0) <1C9DAC03-4FD7-3291-A191-0E019E83AAF7> /Applications/paraview.app/Contents/Libraries/libvtkIOParallelLSDyna-pv5.3.1.dylib 0x11f437000 - 0x11f484ffb +libvtkIOLSDyna-pv5.3.1.dylib (0) <8AE26549-B5BB-3745-BDAA-4F97ABE6418E> /Applications/paraview.app/Contents/Libraries/libvtkIOLSDyna-pv5.3.1.dylib 0x11f49d000 - 0x11f4a6ff3 +libvtkIOParallelNetCDF-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOParallelNetCDF-pv5.3.1.dylib 0x11f4af000 - 0x11f4bbff7 +libvtkIOTRUCHAS-pv5.3.1.dylib (0) <0DF0ADB3-B165-3174-A69E-7AFC6715E19B> /Applications/paraview.app/Contents/Libraries/libvtkIOTRUCHAS-pv5.3.1.dylib 0x11f4cd000 - 0x11f4d6fff +libvtkIOTecplotTable-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOTecplotTable-pv5.3.1.dylib 0x11f511000 - 0x11f519fff +libvtkIOVPIC-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOVPIC-pv5.3.1.dylib 0x11f522000 - 0x11f537fff +libvtkVPIC-pv5.3.1.dylib (0) <3EDB2438-EBD8-3DAA-9FFD-64E27E3A0A64> /Applications/paraview.app/Contents/Libraries/libvtkVPIC-pv5.3.1.dylib 0x11f541000 - 0x11f56bff3 +libvtkIOXdmf2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkIOXdmf2-pv5.3.1.dylib 0x11f585000 - 0x11f5e6ff3 +libvtkImagingMorphological-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkImagingMorphological-pv5.3.1.dylib 0x11f600000 - 0x11f60cff7 +libvtkInteractionImage-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkInteractionImage-pv5.3.1.dylib 0x11f617000 - 0x11f61dff3 +libvtkPVVTKExtensionsPoints-pv5.3.1.dylib (0) <279C2D84-1BFF-3EAB-BD40-07E404974C6C> /Applications/paraview.app/Contents/Libraries/libvtkPVVTKExtensionsPoints-pv5.3.1.dylib 0x11f626000 - 0x11f76eff7 +libvtkFiltersPoints-pv5.3.1.dylib (0) <372431E7-C8B7-3499-A2FC-A7467D8F7470> /Applications/paraview.app/Contents/Libraries/libvtkFiltersPoints-pv5.3.1.dylib 0x11f82a000 - 0x11f82eff7 +libvtkParallelMPI4Py-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkParallelMPI4Py-pv5.3.1.dylib 0x11f833000 - 0x11f83bff7 +libvtkRenderingLOD-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingLOD-pv5.3.1.dylib 0x11f843000 - 0x11f8bffff +libvtkRenderingParallelLIC-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingParallelLIC-pv5.3.1.dylib 0x11f8df000 - 0x11f92efff +libvtkRenderingLICOpenGL2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingLICOpenGL2-pv5.3.1.dylib 0x11f94d000 - 0x11f976fff +libvtkIOSQL-pv5.3.1.dylib (0) <50148C83-9910-3D71-ABDF-A306DF15612E> /Applications/paraview.app/Contents/Libraries/libvtkIOSQL-pv5.3.1.dylib 0x11f98d000 - 0x11f9a1ff3 +libvtkImagingStatistics-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkImagingStatistics-pv5.3.1.dylib 0x11f9b1000 - 0x11f9c9fff +libvtkImagingStencil-pv5.3.1.dylib (0) <4EC333D1-773E-3AC3-AC85-80843B4320C3> /Applications/paraview.app/Contents/Libraries/libvtkImagingStencil-pv5.3.1.dylib 0x11f9db000 - 0x11f9fdff7 +libvtkParaViewWebCore-pv5.3.1.dylib (0) <1563225D-9FE8-3CDB-A5AD-363BD2FF6BEC> /Applications/paraview.app/Contents/Libraries/libvtkParaViewWebCore-pv5.3.1.dylib 0x11fa05000 - 0x11fa17ffb +libvtkWebCore-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkWebCore-pv5.3.1.dylib 0x11fa24000 - 0x11fa4eff3 +libvtkWebGLExporter-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkWebGLExporter-pv5.3.1.dylib 0x11fa5d000 - 0x11fa7cfff +libvtkRenderingContextOpenGL2-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingContextOpenGL2-pv5.3.1.dylib 0x11fa91000 - 0x11fabcff3 +libvtkRenderingImage-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkRenderingImage-pv5.3.1.dylib 0x11fadb000 - 0x11faedffb +libvtkRenderingQt-pv5.3.1.dylib (0) <71D8926A-4AA2-3243-A117-BFA6B7F9A41F> /Applications/paraview.app/Contents/Libraries/libvtkRenderingQt-pv5.3.1.dylib 0x11fafc000 - 0x11fb08ff7 +libvtkFiltersTexture-pv5.3.1.dylib (0) <57BBF83A-F028-3B6B-BDBF-B3F972809FBA> /Applications/paraview.app/Contents/Libraries/libvtkFiltersTexture-pv5.3.1.dylib 0x11fb15000 - 0x11fb1dffb +libvtkViewsGeovis-pv5.3.1.dylib (0) <4B812A5D-E7AE-3AAD-8FC6-97E7E4468E74> /Applications/paraview.app/Contents/Libraries/libvtkViewsGeovis-pv5.3.1.dylib 0x11fb24000 - 0x11fb5bff7 +libvtkGeovisCore-pv5.3.1.dylib (0) <0BF1000E-A7DE-3C11-BF6C-2D936F73E72B> /Applications/paraview.app/Contents/Libraries/libvtkGeovisCore-pv5.3.1.dylib 0x11fb87000 - 0x11fbc6ffb +libvtkproj4-pv5.3.1.dylib (0) <04D14321-9049-304B-B515-48F62EEC8332> /Applications/paraview.app/Contents/Libraries/libvtkproj4-pv5.3.1.dylib 0x11fbd4000 - 0x11fc31ff7 +libvtkViewsInfovis-pv5.3.1.dylib (0) <923268EC-C21A-3F09-B2C8-6A6BCBAF74A9> /Applications/paraview.app/Contents/Libraries/libvtkViewsInfovis-pv5.3.1.dylib 0x11fc7a000 - 0x11fc88fff +libvtkFiltersImaging-pv5.3.1.dylib (0) <9755ECFB-AE49-3F8E-BCA9-37EF3513B742> /Applications/paraview.app/Contents/Libraries/libvtkFiltersImaging-pv5.3.1.dylib 0x11fc94000 - 0x11fcd7ffb +libvtkInfovisLayout-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkInfovisLayout-pv5.3.1.dylib 0x11fd03000 - 0x11fd1bfff +libvtkhdf5_hl-pv5.3.1.dylib (0) /Applications/paraview.app/Contents/Libraries/libvtkhdf5_hl-pv5.3.1.dylib 0x11fd34000 - 0x11ff96ff3 +libvtkhdf5-pv5.3.1.dylib (0) <30B56949-2759-33F5-8FAF-989E6986ADAC> /Applications/paraview.app/Contents/Libraries/libvtkhdf5-pv5.3.1.dylib 0x11ffd1000 - 0x120026ffb +libvtkxdmf2-pv5.3.1.dylib (0) <29D7548F-B0CC-3933-9C3B-0A7D2DF38382> /Applications/paraview.app/Contents/Libraries/libvtkxdmf2-pv5.3.1.dylib 0x120040000 - 0x120130ffb +libvtksqlite-pv5.3.1.dylib (0) <6EFA261D-E89B-36BB-91D5-C815636BC515> /Applications/paraview.app/Contents/Libraries/libvtksqlite-pv5.3.1.dylib 0x123513000 - 0x1235b2fff +libqcocoa.dylib (0) /opt/local/libexec/*/libqcocoa.dylib 0x12602b000 - 0x126035ff7 +libqdds.dylib (0) <88A07AC8-4F2A-3D46-AF0E-0DA3BEF9AFF2> /opt/local/libexec/*/libqdds.dylib 0x12603a000 - 0x126040fff +libqgif.dylib (0) <93779B77-7822-34A5-9836-AE41D820B9B3> /opt/local/libexec/*/libqgif.dylib 0x126044000 - 0x12604bffb +libqicns.dylib (0) /opt/local/libexec/*/libqicns.dylib 0x126050000 - 0x126055ff7 +libqico.dylib (0) /opt/local/libexec/*/libqico.dylib 0x12605a000 - 0x126060ffb +libqjp2.dylib (0) <5CAB1469-FF7A-3F94-9E75-FCE5FD1DDC8E> /opt/local/libexec/*/libqjp2.dylib 0x126065000 - 0x12609dff7 +libjasper.4.dylib (0) <502A21FE-C7D1-38B8-A567-5A6DC65D7B6A> /opt/local/lib/libjasper.4.dylib 0x1260b1000 - 0x1260ddff3 +libjpeg.9.dylib (0) <665B49BB-77FB-3393-8E9F-84AC4A5DC511> /opt/local/lib/libjpeg.9.dylib 0x1260e4000 - 0x1260ecff3 +libqjpeg.dylib (0) /opt/local/libexec/*/libqjpeg.dylib 0x1260f2000 - 0x1260f7ffb +libqmng.dylib (0) <8E78077D-AC65-3BF4-B1A9-BCEF29C0E3F5> /opt/local/libexec/*/libqmng.dylib 0x1260fc000 - 0x12613dff7 +libmng.2.dylib (0) <2BCC3C14-8677-3444-BCB2-A2D85A2F83A9> /opt/local/lib/libmng.2.dylib 0x126157000 - 0x12618effb +liblcms2.2.dylib (0) /opt/local/lib/liblcms2.2.dylib 0x1261a1000 - 0x1261a6ff7 +libqsvg.dylib (0) <3EC909F6-2480-39E0-85EA-321A140E3569> /opt/local/libexec/*/libqsvg.dylib 0x1261ab000 - 0x1261e1fff +org.qt-project.QtSvg (5.6 - 5.6.2) /opt/local/libexec/*/QtSvg.framework/Versions/5/QtSvg 0x1261fc000 - 0x126200fff +libqtga.dylib (0) <1B90CAD6-A143-300C-A975-54273162B7E6> /opt/local/libexec/*/libqtga.dylib 0x126204000 - 0x12620aff7 +libqtiff.dylib (0) /opt/local/libexec/*/libqtiff.dylib 0x12620f000 - 0x12625dfff +libtiff.5.dylib (0) /opt/local/lib/libtiff.5.dylib 0x12626b000 - 0x12626ffff +libqwbmp.dylib (0) <99FCC374-EDB1-3FC9-9DEA-0FD7C0534DAA> /opt/local/libexec/*/libqwbmp.dylib 0x126273000 - 0x126277ff3 +libqwebp.dylib (0) /opt/local/libexec/*/libqwebp.dylib 0x12627b000 - 0x1262ccfff +libwebp.7.dylib (0) /opt/local/lib/libwebp.7.dylib 0x127e48000 - 0x127efcff7 com.apple.AMDRadeonX4000GLDriver (1.42.15 - 1.4.2) <578CDCA4-1CE6-3E56-8D65-6319C49901FE> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver 0x127f14000 - 0x1283effff ATIRadeonX4000SCLib.dylib (1.42.15) <66B1764C-35D8-343B-8350-8B9EEBC7DFBB> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib 0x129dea000 - 0x129eecff7 com.apple.AMDMTLBronzeDriver (1.42.15 - 1.4.2) <88937E6A-81B0-3079-9BD7-12EED4FC9ABA> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver 0x7fff62181000 - 0x7fff621b8a47 dyld (360.22) <884763FC-CC0F-31CC-ACC4-75A805CE401D> /usr/lib/dyld 0x7fff87135000 - 0x7fff8716fff7 com.apple.DebugSymbols (132 - 132) <23A42C53-B941-3871-9EE2-4C87A46005B5> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x7fff87188000 - 0x7fff875feff7 com.apple.CoreFoundation (6.9 - 1259) <51D1F34F-9FEC-3EF2-8382-2D13D75F845A> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff8769a000 - 0x7fff87796ff7 libFontParser.dylib (158.6) <267A9AE4-4138-3112-8D73-BDFDC96568FF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x7fff877d1000 - 0x7fff87bfffff com.apple.vision.FaceCore (3.3.1 - 3.3.1) /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0x7fff87c07000 - 0x7fff87c4cff3 libFontRegistry.dylib (155.2) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x7fff87cad000 - 0x7fff87cb5fef libsystem_platform.dylib (74.40.2) <29A905EF-6777-3C33-82B0-6C3A88C4BA15> /usr/lib/system/libsystem_platform.dylib 0x7fff87cbb000 - 0x7fff87d2afff com.apple.datadetectorscore (7.0 - 460) /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x7fff880d3000 - 0x7fff880dbfff com.apple.NetFS (6.0 - 4.0) <842A5346-24C3-3F22-9ECF-E586A10EA1F2> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff88139000 - 0x7fff8813cff7 com.apple.help (1.3.3 - 46) <35DA4D48-0BC2-35A1-8D7C-40905CDF4F64> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x7fff8813d000 - 0x7fff88141fff libpam.2.dylib (20) /usr/lib/libpam.2.dylib 0x7fff88599000 - 0x7fff88833ff3 com.apple.security (7.0 - 57337.60.2) /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff88895000 - 0x7fff888b9fff com.apple.MultitouchSupport.framework (304.12 - 304.12) <25FA270C-361D-3732-ABF5-A291240AD6A4> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x7fff888ba000 - 0x7fff88929fff com.apple.SearchKit (1.4.0 - 1.4.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff88966000 - 0x7fff88968fff libCVMSPluginSupport.dylib (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x7fff88969000 - 0x7fff88985ff7 libsystem_malloc.dylib (67.40.1) <5748E8B2-F81C-34C6-8B13-456213127678> /usr/lib/system/libsystem_malloc.dylib 0x7fff88986000 - 0x7fff88a78ff7 libiconv.2.dylib (44) /usr/lib/libiconv.2.dylib 0x7fff88a79000 - 0x7fff88b06fef libsystem_c.dylib (1082.60.1) <28733D22-553E-3CBC-8D2C-EDCEB46E46AF> /usr/lib/system/libsystem_c.dylib 0x7fff88dcd000 - 0x7fff88f12fff com.apple.QTKit (7.7.3 - 2943.13) <3E3DB3DD-8D7E-3478-B020-F975CCAAE522> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit 0x7fff88f13000 - 0x7fff88f62ff7 com.apple.opencl (2.7.0 - 2.7.0) <07FB8F36-A00C-3BFD-BC38-9E4EC484907E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x7fff88f7b000 - 0x7fff88f94fff com.apple.CFOpenDirectory (10.11 - 194) <11F95672-55E0-3F9D-9171-5E8C56AEE948> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x7fff88f95000 - 0x7fff88fc6fff com.apple.GSS (4.0 - 2.0) /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x7fff88ffb000 - 0x7fff89017ff7 libextension.dylib (78) /usr/lib/libextension.dylib 0x7fff89018000 - 0x7fff8905aff7 com.apple.Metal (56.6 - 56.6) <30518711-8D00-3759-AA19-800D3C88E693> /System/Library/Frameworks/Metal.framework/Versions/A/Metal 0x7fff8905b000 - 0x7fff8905bfff com.apple.ApplicationServices (48 - 48) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff8905c000 - 0x7fff892f2fff libmecabra.dylib (696.5) /usr/lib/libmecabra.dylib 0x7fff894d5000 - 0x7fff894d8fff com.apple.IOSurface (108.2.3 - 108.2.3) <52E51D16-42E9-3DDB-A16C-48225EF262C4> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x7fff894d9000 - 0x7fff894e2fff com.apple.icloud.FindMyDevice (1.0 - 1) /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice 0x7fff895be000 - 0x7fff895c9fff libkxld.dylib (3248.60.11.2.1) <9DFD804D-B16C-379C-8986-2D8781DFAEAE> /usr/lib/system/libkxld.dylib 0x7fff895ca000 - 0x7fff89671fff com.apple.LanguageModeling (1.0 - 1) <58C18A47-BDE7-3CBE-81C0-797029D170A1> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0x7fff89672000 - 0x7fff89bb0ff7 com.apple.MediaToolbox (1.0 - 1731.15.207) <63AD3FB7-BAD3-3040-8A99-843033F24CF6> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox 0x7fff89c68000 - 0x7fff89caeff7 libauto.dylib (186) <999E610F-41FC-32A3-ADCA-5EC049B65DFB> /usr/lib/libauto.dylib 0x7fff89d4d000 - 0x7fff89d99fff com.apple.print.framework.PrintCore (11.2 - 472.2) <5AE8AA6B-CE09-397D-B0D4-0F9CCBF1F77D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x7fff89dd6000 - 0x7fff89e7afff com.apple.Bluetooth (4.4.6 - 4.4.6f1) <4072EA3E-F2DD-32C1-9B19-9339C7087051> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x7fff8a578000 - 0x7fff8a5a7ffb libsystem_m.dylib (3105) <08E1A4B2-6448-3DFE-A58C-ACC7335BE7E4> /usr/lib/system/libsystem_m.dylib 0x7fff8a5a8000 - 0x7fff8a5bafff libsasl2.2.dylib (209) <11C7D200-0CA5-30F4-A19A-178CA81D48FE> /usr/lib/libsasl2.2.dylib 0x7fff8a5bb000 - 0x7fff8a5bbff7 liblaunch.dylib (765.50.8) <834ED605-5114-3641-AA4D-ECF31B801C50> /usr/lib/system/liblaunch.dylib 0x7fff8a5bc000 - 0x7fff8a6e3fff com.apple.LaunchServices (728.13 - 728.13) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff8a6f3000 - 0x7fff8a706fff com.apple.CoreBluetooth (1.0 - 1) /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x7fff8a75a000 - 0x7fff8a7abfff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x7fff8a7ac000 - 0x7fff8a7daff7 libsandbox.1.dylib (460.60.2) <99132331-202E-35CC-A94D-48CD16B6F588> /usr/lib/libsandbox.1.dylib 0x7fff8a7db000 - 0x7fff8a7e3fff libcopyfile.dylib (127) /usr/lib/system/libcopyfile.dylib 0x7fff8a7e4000 - 0x7fff8a7fafff com.apple.CoreMediaAuthoring (2.2 - 953) /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring 0x7fff8a86e000 - 0x7fff8a885fff libmarisa.dylib (4) /usr/lib/libmarisa.dylib 0x7fff8a977000 - 0x7fff8a98eff7 libsystem_coretls.dylib (83.40.5) /usr/lib/system/libsystem_coretls.dylib 0x7fff8aa58000 - 0x7fff8aa60ffb libsystem_dnssd.dylib (625.60.4) <80189998-32B0-316C-B5C5-53857486713D> /usr/lib/system/libsystem_dnssd.dylib 0x7fff8aca1000 - 0x7fff8aca3ffb libutil.dylib (43) <4C9BFE8B-563B-3EEA-A323-8F4F14E0A46C> /usr/lib/libutil.dylib 0x7fff8aca4000 - 0x7fff8acadff7 com.apple.CommonAuth (4.0 - 2.0) <4B8673E1-3697-3FE2-8D30-AC7AC5D4F8BF> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x7fff8acae000 - 0x7fff8acc8fff com.apple.Kerberos (3.0 - 1) <1B4744BF-E5AE-38E2-AA56-E22D3270F2E8> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x7fff8acc9000 - 0x7fff8aed4fff libFosl_dynamic.dylib (16.24) <5F9DB82D-FD4B-3952-8531-CE020F93ED49> /usr/lib/libFosl_dynamic.dylib 0x7fff8bde0000 - 0x7fff8bdecfff com.apple.speech.synthesis.framework (5.4.12 - 5.4.12) <71DA00B8-5EA2-326B-8814-59DB25512F65> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fff8bded000 - 0x7fff8bfb6ff7 com.apple.ImageIO.framework (3.3.0 - 1460) /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x7fff8bfb7000 - 0x7fff8c322657 libobjc.A.dylib (680) /usr/lib/libobjc.A.dylib 0x7fff8c323000 - 0x7fff8c326ffb libdyld.dylib (360.22) /usr/lib/system/libdyld.dylib 0x7fff8c76a000 - 0x7fff8c775fff libcsfde.dylib (517.50.1) <52F0DB6A-13B8-355E-ADFD-72834D3CA183> /usr/lib/libcsfde.dylib 0x7fff8ca76000 - 0x7fff8ca7bfff com.apple.MediaAccessibility (1.0 - 79) /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility 0x7fff8ca7c000 - 0x7fff8caa7ffb libarchive.2.dylib (33.20.2) <6C370A21-63FD-3A68-B4B3-5333F24B770B> /usr/lib/libarchive.2.dylib 0x7fff8cad0000 - 0x7fff8cb07ff7 com.apple.LDAPFramework (2.4.28 - 194.5) <9AE33BF2-FB17-342D-8F1E-5F83C6E6EB69> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x7fff8cb22000 - 0x7fff8cb6dff7 com.apple.CoreMediaIO (703.0 - 4791) <57D92CFE-E717-38FE-AEE8-0A4D9769679F> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO 0x7fff8cb6e000 - 0x7fff8cba1ff7 com.apple.MediaKit (16 - 809) /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit 0x7fff8cbaa000 - 0x7fff8cbacff7 libRadiance.dylib (1460) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x7fff8cbad000 - 0x7fff8cbccff7 com.apple.framework.Apple80211 (11.0 - 1121.34.2) <90477FAE-B835-3931-80FB-FDFF02B21D9D> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff8cbcf000 - 0x7fff8ccbeff7 libxml2.2.dylib (29.11) /usr/lib/libxml2.2.dylib 0x7fff8ccf5000 - 0x7fff8ccf5fff com.apple.Accelerate (1.10 - Accelerate 1.10) <5831771A-C1C3-3625-9FE9-2CCB6B2E7EE1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff8ccf6000 - 0x7fff8cd6bfff com.apple.framework.IOKit (2.0.2 - 1179.50.2) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff8cd6c000 - 0x7fff8cdf4fff com.apple.CoreSymbolication (3.1 - 58048.1) <1A6BF14E-55F3-324E-81DB-BB22B9C288AE> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x7fff8ce91000 - 0x7fff8ce99fff libGFXShared.dylib (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x7fff8d258000 - 0x7fff8d28cff7 com.apple.CoreVideo (1.8 - 191.3) <1AA24A1B-CB84-3F6B-B6DE-11494542649C> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x7fff8d28d000 - 0x7fff8d29bfff com.apple.opengl (12.1.0 - 12.1.0) <62997B59-BCD2-3A71-BD16-DE75DBAFA7C2> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x7fff8d2b0000 - 0x7fff8ded9ff7 com.apple.AppKit (6.9 - 1404.47) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x7fff8deea000 - 0x7fff8df73ff7 com.apple.PerformanceAnalysis (1.0 - 1) <07DC8D32-56AF-3AD3-83D8-9DC413BA8C2F> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x7fff8df84000 - 0x7fff8dfadff7 libxpc.dylib (765.50.8) <54D1328E-054E-3DAA-89E2-375722F9D18F> /usr/lib/system/libxpc.dylib 0x7fff8e395000 - 0x7fff8e61cfff com.apple.CFNetwork (760.6.3 - 760.6.3) <8CB9CB2E-D0FB-31D4-A1AE-2A5FE028AD6B> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff8e61d000 - 0x7fff8e670ff7 libc++.1.dylib (120.1) <8FC3D139-8055-3498-9AC5-6467CB7F4D14> /usr/lib/libc++.1.dylib 0x7fff8e679000 - 0x7fff8e6b3fff com.apple.QD (3.12 - 302) <0FE53180-2895-3D14-A1E7-F82DE1D106E1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x7fff8e6b4000 - 0x7fff8e6b7fff libsystem_sandbox.dylib (460.60.2) <2A68B39C-B786-3A05-87A2-56E688469FB8> /usr/lib/system/libsystem_sandbox.dylib 0x7fff8e6e2000 - 0x7fff8eabafef com.apple.CoreAUC (214.0.0 - 214.0.0) /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC 0x7fff8eabb000 - 0x7fff8eac3fff libMatch.1.dylib (27) <3AC0BFB8-7E69-3DBE-A175-7F3946FC4554> /usr/lib/libMatch.1.dylib 0x7fff8eac4000 - 0x7fff8eb22fff com.apple.SystemConfiguration (1.14 - 1.14) <8886E043-B668-3A49-BCA5-F89FB0ECB6EC> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff8eb23000 - 0x7fff8eb2eff7 libcommonCrypto.dylib (60075.50.1) <93732261-34B4-3914-B7A2-90A81A182DBA> /usr/lib/system/libcommonCrypto.dylib 0x7fff8eb2f000 - 0x7fff8eb2ffff com.apple.CoreServices (728.13 - 728.13) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff8eb30000 - 0x7fff8eb34fff com.apple.CommonPanels (1.2.6 - 96) <4AE7E5AE-55B3-37FA-9BDE-B23147ADA2E9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x7fff8eb3c000 - 0x7fff8ee31fff com.apple.HIToolbox (2.1.1 - 807.2) <36413C45-36AF-34EF-9C0E-F18B31D1E565> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x7fff8ef32000 - 0x7fff8ef33fff libsystem_secinit.dylib (20) <32B1A8C6-DC84-3F4F-B8CE-9A52B47C3E6B> /usr/lib/system/libsystem_secinit.dylib 0x7fff8efb4000 - 0x7fff8efdeff7 libc++abi.dylib (307.2) <922EFB36-0E9E-315B-8270-E81AC43472C0> /usr/lib/libc++abi.dylib 0x7fff8effb000 - 0x7fff8f061ff7 libsystem_network.dylib (583.50.1) /usr/lib/system/libsystem_network.dylib 0x7fff8f0a6000 - 0x7fff8f0c4ff7 libsystem_kernel.dylib (3248.60.11.2.1) <19B06617-EDC1-3925-8A09-BC775F3D6A08> /usr/lib/system/libsystem_kernel.dylib 0x7fff8f2be000 - 0x7fff8f2c8fff com.apple.NetAuth (6.0 - 6.0) /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x7fff8f2c9000 - 0x7fff8f2e2fe7 libcompression.dylib (28) /usr/lib/libcompression.dylib 0x7fff8f2e3000 - 0x7fff8f2ebfef libcldcpuengine.dylib (2.7.3) <6A6B8893-5A77-3014-9780-D3681DC0A08B> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib 0x7fff8f2f2000 - 0x7fff8f2fafff libsystem_networkextension.dylib (385.40.36) <66095DC7-6539-38F2-95EE-458F15F6D014> /usr/lib/system/libsystem_networkextension.dylib 0x7fff8f2fb000 - 0x7fff8f31dfff com.apple.IconServices (68.1 - 68.1) /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0x7fff8f31e000 - 0x7fff8f31eff7 libkeymgr.dylib (28) <8371CE54-5FDD-3CE9-B3DF-E98C761B6FE0> /usr/lib/system/libkeymgr.dylib 0x7fff8f397000 - 0x7fff8f477ff7 unorm8_rgba.dylib (2.7.3) <9EB6C346-CFF6-32D7-B4A1-2409DFBCB216> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_rgba.dylib 0x7fff8f503000 - 0x7fff8f553ff7 com.apple.Symbolication (1.4 - 58044) /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication 0x7fff8f5f7000 - 0x7fff8f6e9ff7 libJP2.dylib (1460) <7FD6231B-EDB9-377F-87F0-ED1C6EDC6F21> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x7fff8fdbd000 - 0x7fff8fe02ff7 com.apple.coreservices.SharedFileList (24.4 - 24.5) <1D2AD77B-778F-3253-A295-3D0A32A8121C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList 0x7fff90096000 - 0x7fff90099fff com.apple.Mangrove (1.0 - 1) <2D86B3AD-64C3-3BB4-BC66-1CFD0C90E844> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove 0x7fff9009a000 - 0x7fff900fdfff libAVFAudio.dylib (161.2) <1A98DBF3-490B-37FB-928A-AB1E36E6E5DD> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Resources/libAVFAudio.dylib 0x7fff900fe000 - 0x7fff90101fff libCoreVMClient.dylib (119.5) <560D70FB-709F-3030-96C9-F249FCB7DA6D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x7fff90102000 - 0x7fff91368ff3 com.apple.CoreGraphics (1.600.0 - 960.7) <61850A83-03A8-33D0-8A9B-3DC57177DFB3> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff91427000 - 0x7fff9148efff com.apple.framework.CoreWiFi (11.0 - 1101.20) <993592F1-B3F1-3FAD-87BD-EA83C361BCCF> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x7fff91c72000 - 0x7fff91c7dfff com.apple.CrashReporterSupport (10.11 - 718) <05892B57-F2CD-3C84-B984-0417F6B361DB> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x7fff91cb6000 - 0x7fff91cbbfff com.apple.ImageCapture (9.0 - 9.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x7fff91cee000 - 0x7fff91ceefff libOpenScriptingUtil.dylib (169.1) /usr/lib/libOpenScriptingUtil.dylib 0x7fff91d7f000 - 0x7fff91d81fff com.apple.EFILogin (2.0 - 2) <38150198-DD7F-3C73-BCAA-C74BB376393A> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin 0x7fff91d82000 - 0x7fff91d82fff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <848125D3-AF14-3526-8745-FFCDB200CD76> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x7fff91db9000 - 0x7fff91df1ff7 com.apple.RemoteViewServices (2.0 - 101) /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x7fff91df2000 - 0x7fff91df2ff7 libunc.dylib (29) /usr/lib/system/libunc.dylib 0x7fff91df3000 - 0x7fff91df3fff libenergytrace.dylib (10.40.1) <0A491CA7-3451-3FD5-999A-58AB4362682B> /usr/lib/libenergytrace.dylib 0x7fff91e66000 - 0x7fff91e69ff7 libCoreFSCache.dylib (119.5) <2389D7DA-B8EF-3EB4-AAAF-FBEDE01CDECA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib 0x7fff91e6a000 - 0x7fff91e76fff com.apple.SpeechRecognitionCore (2.2.7 - 2.2.7) <6BA06290-D4A3-351C-87F9-B61EF61FF055> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0x7fff91e98000 - 0x7fff91ea6fff libxar.1.dylib (302) <03207F66-2C4A-3DBD-8D81-70F4C85903C4> /usr/lib/libxar.1.dylib 0x7fff92176000 - 0x7fff9219fffb libRIP.A.dylib (960.7) <6C9E6C2C-62FD-32E6-AEB8-564A3510B17A> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x7fff924d4000 - 0x7fff924d6ff7 com.apple.xpc.ServiceManagement (1.0 - 1) /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x7fff926a8000 - 0x7fff926f6fff libcurl.4.dylib (90) <12E01E4B-24C9-394C-9D2C-85CF85D5F459> /usr/lib/libcurl.4.dylib 0x7fff927c8000 - 0x7fff927f8ff3 com.apple.CoreAVCHD (5.8.0 - 5800.4.2) <4AAFB1C4-3708-30F9-ACFA-90564347204C> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD 0x7fff9280d000 - 0x7fff928f3ff7 libcrypto.0.9.8.dylib (59.60.1) /usr/lib/libcrypto.0.9.8.dylib 0x7fff928f4000 - 0x7fff928fffff com.apple.AppSandbox (4.0 - 261.40.2) <52766210-B6EB-3B73-AB1B-42E0A9AD2EE8> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox 0x7fff92900000 - 0x7fff92906fff com.apple.XPCService (2.0 - 1) <5E2122D6-FFA2-3552-BF16-9FD3F36B40DB> /System/Library/PrivateFrameworks/XPCService.framework/Versions/A/XPCService 0x7fff92908000 - 0x7fff92973ff7 com.apple.framework.CoreWLAN (11.0 - 1101.20) <3B35C543-7FCE-333F-80C1-432FA41DDCDE> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x7fff92974000 - 0x7fff92998ff7 libJPEG.dylib (1460) <82AF76D7-B3E6-39AA-947E-C34A280FD1CF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x7fff929c7000 - 0x7fff929ccff7 libmacho.dylib (875.1) <318264FA-58F1-39D8-8285-1F6254EE410E> /usr/lib/system/libmacho.dylib 0x7fff929f8000 - 0x7fff929fbfff libspindump.dylib (197.1) <0977578F-0FA1-3F44-B16E-37DFD2C52CC8> /usr/lib/libspindump.dylib 0x7fff92dac000 - 0x7fff92e3bff7 libCoreStorage.dylib (517.50.1) /usr/lib/libCoreStorage.dylib 0x7fff92e40000 - 0x7fff92e81ff7 libGLU.dylib (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x7fff92e82000 - 0x7fff92ee0fff com.apple.CoreServices.OSServices (728.13 - 728.13) <27C12B92-7845-38DD-B82D-DC5B678352D6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff92ee1000 - 0x7fff92ef2fff libcmph.dylib (6) /usr/lib/libcmph.dylib 0x7fff92efa000 - 0x7fff92f21fff com.apple.ChunkingLibrary (167 - 167) /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x7fff933c6000 - 0x7fff935d3fff libicucore.A.dylib (551.51.4) <3899B146-3840-3D4A-8C4A-FE391D5D25C7> /usr/lib/libicucore.A.dylib 0x7fff935f7000 - 0x7fff93611ff3 liblzma.5.dylib (10) /usr/lib/liblzma.5.dylib 0x7fff93768000 - 0x7fff93783ff7 libCRFSuite.dylib (34) <078B4CD8-6A8C-3067-B2BA-0C2A0BAB8AC3> /usr/lib/libCRFSuite.dylib 0x7fff93784000 - 0x7fff93786fff com.apple.SecCodeWrapper (4.0 - 261.40.2) <1F832591-59A8-3B3F-943F-D6D827463782> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper 0x7fff93787000 - 0x7fff93788fff liblangid.dylib (122) <9CC4F0D1-5C51-3B69-BC8F-EE3A51FD0822> /usr/lib/liblangid.dylib 0x7fff937ad000 - 0x7fff937adfff com.apple.Cocoa (6.11 - 22) <807787AB-D231-3F51-A99B-A9314623C571> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x7fff937ae000 - 0x7fff937befff libSparseBLAS.dylib (1162.2) <6F591A0F-80D0-384D-8304-B035C4ED1BBD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib 0x7fff937cd000 - 0x7fff9386dfff com.apple.Metadata (10.7.0 - 972.34) <5F407CB0-3244-3A15-8000-82DDB0420244> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff93acb000 - 0x7fff93acbfff com.apple.audio.units.AudioUnit (1.13 - 1.13) <378B5292-F216-32AB-B628-8C33A72D7052> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x7fff93acc000 - 0x7fff93ad5fff com.apple.IOAccelMemoryInfo (1.0 - 1) <5938394C-EAF4-37C7-A335-62D9A5DEC196> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo 0x7fff93ad6000 - 0x7fff93c62ff7 libGLProgrammability.dylib (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x7fff93c63000 - 0x7fff93c6cff3 libsystem_notify.dylib (150.40.1) /usr/lib/system/libsystem_notify.dylib 0x7fff93c6d000 - 0x7fff93c73fff com.apple.IOAccelerator (205.11 - 205.11) /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator 0x7fff93d07000 - 0x7fff93e19fef libvDSP.dylib (563.5) <5702650E-DF08-3D58-B16F-9EF0A28702B3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x7fff93ec9000 - 0x7fff93f5efff com.apple.ink.framework (10.9 - 214) <1F76CF36-3F79-36B8-BC37-C540AF34B338> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x7fff93f5f000 - 0x7fff93f67fff com.apple.AppleSRP (5.0 - 1) <840A5C20-6452-36BB-ACF7-29BA6CBF7C48> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP 0x7fff94040000 - 0x7fff9405cfff com.apple.GenerationalStorage (2.0 - 239.1) <8C821448-4294-3736-9CEF-467C93785CB9> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x7fff9405d000 - 0x7fff94061fff libcache.dylib (75) <9548AAE9-2AB7-3525-9ECE-A2A7C4688447> /usr/lib/system/libcache.dylib 0x7fff94161000 - 0x7fff941cfff7 com.apple.ApplicationServices.ATS (377 - 394.4) <9779E916-0788-3CAC-B1EC-F68BCB12A2B6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x7fff941d0000 - 0x7fff941feff7 com.apple.CoreServicesInternal (248.2 - 248.2) <6E111F0A-D7F1-3738-ADE7-CF983BD4EC8B> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x7fff941ff000 - 0x7fff94295fff com.apple.ColorSync (4.9.0 - 4.9.0) <8FC37E20-6579-3CB2-9D49-BC39FC38DF87> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x7fff94296000 - 0x7fff9429dff7 libcompiler_rt.dylib (62) /usr/lib/system/libcompiler_rt.dylib 0x7fff9429e000 - 0x7fff9429fffb libSystem.B.dylib (1226.10.1) <012548CD-614D-3AF0-B3B1-676F427D2CD6> /usr/lib/libSystem.B.dylib 0x7fff942a0000 - 0x7fff9475efcf com.apple.vImage (8.0 - 8.0) <85FB412E-EB30-3433-A79B-B3970FC83580> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff947d0000 - 0x7fff947deff7 libbz2.1.0.dylib (38) <28E54258-C0FE-38D4-AB76-1734CACCB344> /usr/lib/libbz2.1.0.dylib 0x7fff947df000 - 0x7fff947e5ff7 com.apple.speech.recognition.framework (5.1.1 - 5.1.1) <9E5A980A-F455-32D5-BBEE-3BD6018CC45E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x7fff94bf7000 - 0x7fff94ff9fff libLAPACK.dylib (1162.2) <42238ED4-6B7A-39D0-BFF2-304A0C287213> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff94ffa000 - 0x7fff95005fff libGPUSupportMercury.dylib (12.1) <28957CBD-2E85-3D1E-9750-757F2A893FCA> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib 0x7fff95006000 - 0x7fff95184fff com.apple.UIFoundation (1.0 - 436.1) /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0x7fff95185000 - 0x7fff95330ffb GLEngine (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine 0x7fff95331000 - 0x7fff95342ff7 libz.1.dylib (61.20.1) /usr/lib/libz.1.dylib 0x7fff9539a000 - 0x7fff953bcff7 com.apple.Sharing (442.13.6 - 442.13.6) /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0x7fff953dd000 - 0x7fff953e1fff libGIF.dylib (1460) /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x7fff953e2000 - 0x7fff954bbfff com.apple.CoreMedia (1.0 - 1731.15.207) <70CAD4A7-3F8B-3767-A420-98BE1062C230> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia 0x7fff954c1000 - 0x7fff954dafff com.apple.openscripting (1.7.1 - 169.1) <36EBF6A7-334A-3197-838F-E8C7B27FCDBB> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x7fff954db000 - 0x7fff95681ff7 com.apple.audio.toolbox.AudioToolbox (1.13 - 1.13) <370E95BC-956C-3962-86CC-0A14CF6A0389> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x7fff957bd000 - 0x7fff957c0ffb libScreenReader.dylib (426.42) <16FC79D1-4573-3E90-945F-CBA22D5185FD> /usr/lib/libScreenReader.dylib 0x7fff957c4000 - 0x7fff959e5ff7 com.apple.CoreImage (11.4.0 - 366.4.20) <7721BA55-A10E-3425-8392-C5D7C510EAAB> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x7fff95bf5000 - 0x7fff95c82dd7 com.apple.AppleJPEG (1.0 - 1) /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x7fff95cfd000 - 0x7fff95e47ff7 com.apple.coreui (2.1 - 366.1) <8138636F-A0A7-31C7-896C-5F5747FA1B2A> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x7fff95e48000 - 0x7fff95e86ff7 libGLImage.dylib (12.1) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x7fff95ffc000 - 0x7fff9604dff7 libcups.2.dylib (435.2) <91584A40-214D-33E8-A613-CE22289037C8> /usr/lib/libcups.2.dylib 0x7fff96075000 - 0x7fff96080fff libGL.dylib (12.1) <70D51643-04AC-3400-8F11-A6FC25985289> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x7fff96081000 - 0x7fff960aafff com.apple.ProtectedCloudStorage (1.0 - 1) <7436B2B3-943A-3500-B099-80F133B3E002> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage 0x7fff960b1000 - 0x7fff960b6fff com.apple.TCC (1.0 - 1) /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x7fff960d1000 - 0x7fff960d9fff com.apple.CoreServices.FSEvents (1223.10.1 - 1223.10.1) <7F5B7A23-BC1D-3FA9-A9B8-D534F1E1979A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x7fff96107000 - 0x7fff96123ff3 libresolv.9.dylib (60) /usr/lib/libresolv.9.dylib 0x7fff96e1d000 - 0x7fff96e25fff com.apple.frameworks.CoreDaemon (1.3 - 1.3) /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon 0x7fff96e58000 - 0x7fff96e6dff3 libCGInterfaces.dylib (317.9) <473434E1-5269-3077-A047-D05E024AE631> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib 0x7fff96e6e000 - 0x7fff96f8bfff libsqlite3.dylib (216.4) /usr/lib/libsqlite3.dylib 0x7fff96fb8000 - 0x7fff96fc9ff7 libsystem_trace.dylib (201.10.3) /usr/lib/system/libsystem_trace.dylib 0x7fff97004000 - 0x7fff97005ffb libremovefile.dylib (41) <552EF39E-14D7-363E-9059-4565AC2F894E> /usr/lib/system/libremovefile.dylib 0x7fff97006000 - 0x7fff97023ff7 com.apple.AppleVPAFramework (2.1.2 - 2.1.2) <7B26B7D9-AEB3-3DEC-B4AD-B49BC0FD1082> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA 0x7fff970b9000 - 0x7fff970beff3 libunwind.dylib (35.3) /usr/lib/system/libunwind.dylib 0x7fff970ed000 - 0x7fff97103ff7 libLinearAlgebra.dylib (1162.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x7fff97104000 - 0x7fff971bdff7 libvMisc.dylib (563.5) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x7fff971be000 - 0x7fff97219ff7 libTIFF.dylib (1460) <37D499DA-A4A6-3CC8-8F60-F374F992C304> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x7fff9728a000 - 0x7fff9728afff libmetal_timestamp.dylib (600.0.44.2) /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib 0x7fff972aa000 - 0x7fff972abfff libDiagnosticMessagesClient.dylib (100) <4243B6B4-21E9-355B-9C5A-95A216233B96> /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff97462000 - 0x7fff97491ff7 com.apple.DictionaryServices (1.2 - 250.3) <30250542-CBAA-39C1-91AA-B57A5DE17594> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff97492000 - 0x7fff974e7fff com.apple.AE (701 - 701) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x7fff974e8000 - 0x7fff974eaff7 libsystem_configuration.dylib (802.40.13) <3DEB7DF9-6804-37E1-BC83-0166882FF0FF> /usr/lib/system/libsystem_configuration.dylib 0x7fff97cf5000 - 0x7fff97dcbffb com.apple.DiskImagesFramework (10.11.4 - 417.4) /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 0x7fff97dcc000 - 0x7fff98120fff com.apple.Foundation (6.9 - 1259) <71A9D3A0-0B1F-3E3A-86F3-1486365A6EF2> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff98136000 - 0x7fff98146fff libbsm.0.dylib (34) <7E14504C-A8B0-3574-B6EB-5D5FABC72926> /usr/lib/libbsm.0.dylib 0x7fff98147000 - 0x7fff98148fff libsystem_blocks.dylib (65) <1244D9D5-F6AA-35BB-B307-86851C24B8E5> /usr/lib/system/libsystem_blocks.dylib 0x7fff98149000 - 0x7fff98158ffb com.apple.LangAnalysis (1.7.0 - 1.7.0) <18D21123-A3E7-3851-974A-08E5D4540475> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x7fff98200000 - 0x7fff98277feb libcorecrypto.dylib (335.50.1) /usr/lib/system/libcorecrypto.dylib 0x7fff9839b000 - 0x7fff983c4fff libsystem_info.dylib (477.50.4) /usr/lib/system/libsystem_info.dylib 0x7fff987e3000 - 0x7fff987e5ff7 com.apple.securityhi (9.0 - 55006) <1E7BE52B-97EA-371A-AECA-1EE2AD246D8A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x7fff987e6000 - 0x7fff989a6ffb libBLAS.dylib (1162.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff98a2f000 - 0x7fff98a38ff7 libsystem_pthread.dylib (138.10.4) <3DD1EF4C-1D1B-3ABF-8CC6-B3B1CEEE9559> /usr/lib/system/libsystem_pthread.dylib 0x7fff98a39000 - 0x7fff98a3bfff libsystem_coreservices.dylib (19.2) <1B3F5AFC-FFCD-3ECB-8B9A-5538366FB20D> /usr/lib/system/libsystem_coreservices.dylib 0x7fff98a7f000 - 0x7fff98c2bff7 com.apple.avfoundation (2.0 - 1046.9.12) <41BDD03F-5545-3B9F-8DD7-7106485BAE8B> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation 0x7fff98c94000 - 0x7fff98dc1ff3 com.apple.CoreText (352.0 - 494.12) /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x7fff98e3f000 - 0x7fff98e64ff7 libPng.dylib (1460) <2A9174D0-445A-3AD9-8141-D602E9A1D735> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x7fff99865000 - 0x7fff99915fff com.apple.backup.framework (1.7.4 - 1.7.4) /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x7fff99944000 - 0x7fff999b8ff7 com.apple.Heimdal (4.0 - 2.0) <5D365381-8B5E-3259-8867-FC4A7D307BDE> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x7fff999ba000 - 0x7fff99a74fff com.apple.DiscRecording (9.0.1 - 9010.4.3) <540853B2-B123-3560-8023-C92EE229051A> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 0x7fff99a75000 - 0x7fff99df3ff3 com.apple.VideoToolbox (1.0 - 1731.15.207) <6C7C261F-CB65-3AF1-92E7-16ACAD371EF4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox 0x7fff9a273000 - 0x7fff9a381ff3 com.apple.desktopservices (1.10.3 - 1.10.3) <3A6906D4-C0B8-30D1-B589-0466E5E42B69> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x7fff9a382000 - 0x7fff9a3f6ff3 com.apple.securityfoundation (6.0 - 55126) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x7fff9a6bb000 - 0x7fff9a961ff7 com.apple.CoreData (120 - 641.3) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x7fff9a962000 - 0x7fff9a9b4fff com.apple.AppleVAFramework (5.0.32 - 5.0.32) /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA 0x7fff9a9b8000 - 0x7fff9a9b9ff3 com.apple.print.framework.Print (10.0 - 266) <3E85F70C-D7D4-34E1-B88A-C1F503F99CDA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x7fff9ab3b000 - 0x7fff9ab68fff libdispatch.dylib (501.40.12) /usr/lib/system/libdispatch.dylib 0x7fff9ab69000 - 0x7fff9ab6bfff com.apple.loginsupport (1.0 - 1) <9B2F5F9B-ED38-313F-B798-D2B667BCD6B5> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0x7fff9ab8a000 - 0x7fff9ad58ff3 com.apple.QuartzCore (1.11 - 410.14) <3CEA7616-63A9-3B69-B6A8-476BF6D3F58B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x7fff9aeea000 - 0x7fff9af01ff7 libsystem_asl.dylib (323.50.1) <41F8E11F-1BD0-3F1D-BA3A-AA1577ED98A9> /usr/lib/system/libsystem_asl.dylib 0x7fff9af02000 - 0x7fff9af04ff7 libquarantine.dylib (80) <0F4169F0-0C84-3A25-B3AE-E47B3586D908> /usr/lib/system/libquarantine.dylib 0x7fff9bff2000 - 0x7fff9c01cff7 GLRendererFloat (12.1) <15894300-8350-343F-942D-6D168BFFDB13> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat 0x7fff9c886000 - 0x7fff9c8d2ffb com.apple.HIServices (1.22 - 550) <6B76B41C-CF5A-34C4-89F4-EFD7CA3D1C9D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x7fff9c8da000 - 0x7fff9c9c0fef unorm8_bgra.dylib (2.7.3) /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib 0x7fff9c9c1000 - 0x7fff9c9eaff7 libxslt.1.dylib (14.4) <72CD1CA4-1FBD-3672-ADCE-A89AB741689A> /usr/lib/libxslt.1.dylib 0x7fff9d11e000 - 0x7fff9d11ffff com.apple.TrustEvaluationAgent (2.0 - 25) <0239494E-FEFE-39BC-9FC7-E251BA5128F1> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x7fff9d120000 - 0x7fff9d125fff com.apple.DiskArbitration (2.7 - 2.7) /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff9d126000 - 0x7fff9d40bffb com.apple.CoreServices.CarbonCore (1136.2 - 1136.2) <2DBAFC9A-6CD6-351D-B1F4-87D81AA6D640> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff9d92f000 - 0x7fff9d934ff7 libheimdal-asn1.dylib (453.40.10) <981DE40B-FA16-36F7-BE92-8C8A115D6CD9> /usr/lib/libheimdal-asn1.dylib 0x7fff9d935000 - 0x7fff9d935fff com.apple.Carbon (154 - 157) <8F6ED602-5943-3E29-A793-BC331E2C183D> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x7fff9d936000 - 0x7fff9d942ff7 com.apple.OpenDirectory (10.11 - 194) <31A67AD5-5CC2-350A-96D7-821DF4BC4196> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x7fff9d98e000 - 0x7fff9d9a3fff com.apple.AppContainer (4.0 - 261.40.2) /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer 0x7fff9da90000 - 0x7fff9da9bff7 libChineseTokenizer.dylib (16) <79B8C67A-3061-3C78-92CD-4650719E68D4> /usr/lib/libChineseTokenizer.dylib 0x7fff9daa9000 - 0x7fff9daabfff libCGXType.A.dylib (960.7) /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 5 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 903749 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=443.2M resident=0K(0%) swapped_out_or_unallocated=443.2M(100%) Writable regions: Total=314.7M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=314.7M(100%) VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= Accelerate.framework 128K 2 Activity Tracing 2048K 2 CG backing stores 9648K 7 CG image 44K 9 CG shared images 464K 11 CoreAnimation 124K 18 CoreUI image data 1860K 10 CoreUI image file 192K 4 Dispatch continuations 24.0M 2 Kernel Alloc Once 8K 3 MALLOC 184.6M 47 MALLOC guard page 32K 7 Memory Tag 242 12K 2 OpenCL 8K 2 OpenGL GLSL 256K 4 Process Corpse Info 2048K 2 STACK GUARD 56.1M 15 Stack 14.2M 17 VM_ALLOCATE 544K 20 __DATA 86.5M 559 __GLSLBUILTINS 2588K 2 __IMAGE 528K 2 __LINKEDIT 127.2M 289 __TEXT 316.0M 519 __UNICODE 552K 2 mapped file 45.8M 12 shared memory 16.3M 10 =========== ======= ======= TOTAL 891.2M 1552 Model: MacPro6,1, BootROM MP61.0116.B21, 6 processors, 6-Core Intel Xeon E5, 3.5 GHz, 64 GB, SMC 2.20f18 Graphics: AMD FirePro D500, AMD FirePro D500, PCIe, 3072 MB Graphics: AMD FirePro D500, AMD FirePro D500, PCIe, 3072 MB Memory Module: DIMM1, 16 GB, DDR3 ECC, 1866 MHz, 0x80CE, 0x4D33393342324737305148302D434D412020 Memory Module: DIMM2, 16 GB, DDR3 ECC, 1866 MHz, 0x80CE, 0x4D33393342324737305148302D434D412020 Memory Module: DIMM3, 16 GB, DDR3 ECC, 1866 MHz, 0x80CE, 0x4D33393342324737305148302D434D412020 Memory Module: DIMM4, 16 GB, DDR3 ECC, 1866 MHz, 0x80CE, 0x4D33393342324737305148302D434D412020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.21.95.175.1a6) Bluetooth: Version 4.4.6f1 17910, 3 services, 27 devices, 1 incoming serial ports Network Service: Ethernet 1, Ethernet, en0 PCI Card: AMD FirePro D500, Display Controller, Slot-1 PCI Card: AMD FirePro D500, Display Controller, Slot-2 PCI Card: Apple 57761-B0, Ethernet Controller, Thunderbolt at 236,0,0 PCI Card: pci11c1,5901, IEEE 1394 Open HCI, Thunderbolt at 235,0,0 PCI Card: Apple 57761-B0, Ethernet Controller, Thunderbolt at 186,0,0 PCI Card: pci11c1,5901, IEEE 1394 Open HCI, Thunderbolt at 185,0,0 PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt at 241,0,0 PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt at 241,0,1 PCI Card: pci12d8,400f, USB Enhanced Host Controller, Thunderbolt at 241,0,2 PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt at 184,0,0 PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt at 184,0,1 PCI Card: pci12d8,400f, USB Enhanced Host Controller, Thunderbolt at 184,0,2 Serial ATA Device: APPLE SSD SM1024F, 1 TB USB Device: USB 2.0 Bus USB Device: Hub USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: USB 2.0 Bus USB Device: Hub USB Device: FaceTime HD Camera (Display) USB Device: Apple Thunderbolt Display USB Device: Display Audio USB Device: USB 2.0 Bus USB Device: Hub USB Device: FaceTime HD Camera (Display) USB Device: Apple Thunderbolt Display USB Device: Display Audio USB Device: USB 3.0 Bus USB Device: Keyboard Hub USB Device: Apple Keyboard USB Device: SCRx31 USB Smart Card Reader USB Device: iPhone USB Device: Macally ECOMouse Thunderbolt Bus: Mac Pro, Apple Inc., 19.2 Thunderbolt Bus: Mac Pro, Apple Inc., 19.2 Thunderbolt Bus: Mac Pro, Apple Inc., 19.2 Thunderbolt Device: Thunderbolt Display, Apple Inc., 1, 26.2 Thunderbolt Device: Thunderbolt Display, Apple Inc., 3, 26.2 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] 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 rodneicouto at gmail.com Mon Mar 13 13:42:11 2017 From: rodneicouto at gmail.com (Rodnei Couto) Date: Mon, 13 Mar 2017 14:42:11 -0300 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Yes, I'm sure there is no twisted library in my system python. I rollback to version 5.2.0 and everything works fine. Can be a bug? -- Rodnei Couto | (55 21) 98749-9885 On Sun, Mar 12, 2017 at 3:12 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Are you sure, there is no twisted library in your system python? > > > On Fri, Mar 10, 2017 at 6:34 PM, Rodnei Couto > wrote: > >> My version was downloaded from the official site >> >> ParaView-5.3.0-RC3-Qt5-OpenGL2-MPI-Linux-64bit >> >> Cheers, >> >> -- >> Rodnei Couto | (55 21) 98749-9885 >> >> On Fri, Mar 10, 2017 at 6:36 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> What version of ParaView are you using? One you built yourself (if so, >>> how old), or a release binary? >>> >>> >>> On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto >>> wrote: >>> >>>> Hi, >>>> >>>> Thanks for the answer. >>>> >>>> I completely removed the twisted from my machine and the error >>>> continue. In fact the error occurred before his installation. I installed >>>> twitted to try to solve it >>>> >>>> Any other ideas? >>>> >>>> Cheers, >>>> >>>> >>>> -- >>>> Rodnei Couto | (55 21) 98749-9885 >>>> >>>> On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < >>>> scott.wittenburg at kitware.com> wrote: >>>> >>>>> Did you try to set up your own version of twisted in your system >>>>> python? When you illustrated how twisted was properly set up, you did it >>>>> with "python", but your start script runs pvpython. I wonder if maybe your >>>>> system python twisted is conflicting (or overriding) with the one provided >>>>> by pvpython? That's just a guess based on a quick read. >>>>> >>>>> Hope this helps, >>>>> Scott >>>>> >>>>> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto >>>>> wrote: >>>>> >>>>>> I set up my environment as indicated in http://kitware.github.io/pa >>>>>> raviewweb/docs/ubuntu_14_04.html >>>>>> >>>>>> My operational system is Ubuntu 64 14_04 LTS. >>>>>> >>>>>> When I try to run my start.sh, I get an error: >>>>>> >>>>>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>>>>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>>>>> from twisted.internet import reactor, defer >>>>>> ImportError: No module named twisted.internet >>>>>> >>>>>> i think the twisted is properly installed in my environment, as can >>>>>> be seen below: >>>>>> >>>>>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> My start.sh code is: >>>>>> >>>>>> #!/bin/bash >>>>>> export DISPLAY=:0.0 >>>>>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>>>>> >>>>>> >>>>>> Can anybody help me? I do not know what else I can do >>>>>> >>>>>> Cheers, >>>>>> >>>>>> ? >>>>>> >>>>>> Rodnei Couto | (55 21) 98749-9885 >>>>>> ? >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 13 14:11:16 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 13 Mar 2017 14:11:16 -0400 Subject: [Paraview] place of colormap ... In-Reply-To: <50912.78.182.90.145.1489394630.squirrel@webmail.be.itu.edu.tr> References: <51841.78.190.99.135.1487320975.squirrel@webmail.be.itu.edu.tr> <50912.78.182.90.145.1489394630.squirrel@webmail.be.itu.edu.tr> Message-ID: If your intention is to make the colormaps available to the client connecting to a pvserver running on your cluster, then alas, there's no way currently. You'll have to provide your color maps to the users so that can import them on their desktops. If your intention is to use the color map is python scripts, then you can do the following: from paraview.simple import * ImportPresets(filename='/tmp/MyCustom.json') # To use the color map, get color transfer function/color map for an array e.g. 'RTData' rTDataLUT = GetColorTransferFunction('RTData') # Apply a preset using its name. Note this may not work as expected when presets have duplicate names. rTDataLUT.ApplyPreset('MyCustomColorMap', True) Utkarsh On Mon, Mar 13, 2017 at 4:43 AM, wrote: > Hi, > > I just want to add additional color map to ParaView but I don't have > access to GUI (it is installed to a cluster with NVIDIA EGL support). So, > I just wonder that which file must be edited to include colormap manually. > Is it lib/site-packages/paraview/ColorMaps.xml? If so I could not see my > new colormap in that file when I look at my laptop installation. It must > be somewhere else but where? > > Thanks, > > --ufuk > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Mon Mar 13 14:19:56 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 13 Mar 2017 12:19:56 -0600 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Hum, that is weird. It could be a bug. Do you mind doing a diff between the 2 python modules between 5.2 and 5.3. Twisted should be the same. Then on the ParaView side, I'm not expecting much difference. Thanks for tracking that down... Seb On Mon, Mar 13, 2017 at 11:42 AM, Rodnei Couto wrote: > Yes, I'm sure there is no twisted library in my system python. > > I rollback to version 5.2.0 and everything works fine. > > Can be a bug? > > -- > Rodnei Couto | (55 21) 98749-9885 > > On Sun, Mar 12, 2017 at 3:12 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Are you sure, there is no twisted library in your system python? >> >> >> On Fri, Mar 10, 2017 at 6:34 PM, Rodnei Couto >> wrote: >> >>> My version was downloaded from the official site >>> >>> ParaView-5.3.0-RC3-Qt5-OpenGL2-MPI-Linux-64bit >>> >>> Cheers, >>> >>> -- >>> Rodnei Couto | (55 21) 98749-9885 >>> >>> On Fri, Mar 10, 2017 at 6:36 PM, Scott Wittenburg < >>> scott.wittenburg at kitware.com> wrote: >>> >>>> What version of ParaView are you using? One you built yourself (if so, >>>> how old), or a release binary? >>>> >>>> >>>> On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> Thanks for the answer. >>>>> >>>>> I completely removed the twisted from my machine and the error >>>>> continue. In fact the error occurred before his installation. I installed >>>>> twitted to try to solve it >>>>> >>>>> Any other ideas? >>>>> >>>>> Cheers, >>>>> >>>>> >>>>> -- >>>>> Rodnei Couto | (55 21) 98749-9885 >>>>> >>>>> On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < >>>>> scott.wittenburg at kitware.com> wrote: >>>>> >>>>>> Did you try to set up your own version of twisted in your system >>>>>> python? When you illustrated how twisted was properly set up, you did it >>>>>> with "python", but your start script runs pvpython. I wonder if maybe your >>>>>> system python twisted is conflicting (or overriding) with the one provided >>>>>> by pvpython? That's just a guess based on a quick read. >>>>>> >>>>>> Hope this helps, >>>>>> Scott >>>>>> >>>>>> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto >>>>> > wrote: >>>>>> >>>>>>> I set up my environment as indicated in http://kitware.github.io/pa >>>>>>> raviewweb/docs/ubuntu_14_04.html >>>>>>> >>>>>>> My operational system is Ubuntu 64 14_04 LTS. >>>>>>> >>>>>>> When I try to run my start.sh, I get an error: >>>>>>> >>>>>>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>>>>>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>>>>>> from twisted.internet import reactor, defer >>>>>>> ImportError: No module named twisted.internet >>>>>>> >>>>>>> i think the twisted is properly installed in my environment, as can >>>>>>> be seen below: >>>>>>> >>>>>>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> My start.sh code is: >>>>>>> >>>>>>> #!/bin/bash >>>>>>> export DISPLAY=:0.0 >>>>>>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>>>>>> >>>>>>> >>>>>>> Can anybody help me? I do not know what else I can do >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> ? >>>>>>> >>>>>>> Rodnei Couto | (55 21) 98749-9885 >>>>>>> ? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Mon Mar 13 15:10:47 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Mon, 13 Mar 2017 15:10:47 -0400 Subject: [Paraview] Potential Memory Error in CAVE mode Message-ID: Hi again community! I have been testing Paraview 5.2.0 in a CAVE mode with pretty big data (1+ billion points) while remotely connected to some HPC servers. PROBLEM: In CAVE mode, I get the below error when I try to change mode from "Outline" to "Points". Same issue while doing other things as well like applying a Glyph (Sphere), etc. ERROR: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc The same issue doesn't occur if I don't use the CAVE mode in that I simple connect a Paraview client with the HPC servers and don't pass any pvx file. I read some similar online discussions pointing towards memory issues but it's hard for me to believe that given a) I have hundreds of gigs of memory and most of it remains empty even with my big data loaded, b) the issue doesn't occur when not in a CAVE mode. Anyone experienced any such similar issues? Thanks for all the help! -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Markus.Held at uibk.ac.at Mon Mar 13 16:08:37 2017 From: Markus.Held at uibk.ac.at (Held, Markus) Date: Mon, 13 Mar 2017 20:08:37 +0000 Subject: [Paraview] WG: AW: Re: 3d Contour plot on cylindrical grid - inaccurate contours with prefered direction in toroidal angle In-Reply-To: <000f4253.0146c7e64c3816a0@uibk.ac.at> References: <58C677EB.4080306@uibk.ac.at>, <2952a84b-0aa3-6db0-d9bc-e71a11b95714@bresnan.net>, <000f4253.0146c7e64c3816a0@uibk.ac.at> Message-ID: <000f424a.0e75aa9d227c99b6@uibk.ac.at>> ------ Originalnachricht------ Von: Held, Markus Datum: Mo., 13.03.2017 21:05 An: samuelkey at bresnan.net; Betreff:AW: Re: [Paraview] 3d Contour plot on cylindrical grid - inaccurate contours with prefered direction in toroidal angle Dear sam key, thank you for the fast reply. Actually we transform the R,Z,\varphi coordinates to cartesian x,y,z coordinates via filters in paraview. This is also shown in the picturre. However, we see the same problem in cylindrical coordinates. Here, the isosurface still prefers the /varphi direction. 2d contours in the R,Z plane are accurate. Best regards markus ------ Originalnachricht------ Von: Samuel Key Datum: Mo., 13.03.2017 20:13 An: Held, Markus; Betreff:Re: [Paraview] 3d Contour plot on cylindrical grid - inaccurate contours with prefered direction in toroidal angle Markus, Unless I am mistaken, PV works with rectangular Cartesian coordinates (x,y,z) If you supplied PV with cylindrical coordinates (r,z,\varphi) , and used a slice plane that contained the r=0.0 axis, then the two cylindrical coordinates r and z would form a 2-D planar rectangular Cartesian coordinate system. In this case, one would get an "accurate" 2-D contour of the data contained in the r,z-plane. To get true 3-D contours (also known as, isosurfaces) from the (r,z,\varphi) coordinates, as you write out the simulation results from your software to the datum set for PV, use a transformation to convert (r,z,\varphi) into (x,y,z). Hope this helps Sam Key On 3/13/2017 4:43 AM, markus wrote: > Dear all, > > i'm for a long time experiencing a contour plot problem in 3d. Our > scalar data is on a cylindrical (R,Z,\varphi) grid. A 3d contour of > the data produces correct "2d contours" in the RZ plane, but the > contours are elongated in the \varphi direction, even if the data > prefers another direction. > > Image here: > ftp://ftp.uibk.ac.at/private/c7441143_20170403_7512b21ed0886d37bdf38b41d4056946 > > > The prefered direction is aligned to a given vector field. > > Is there a way to improve the 3d contours with a filter in paraview or > maybe with the help of the given vector field? > > best regards > markus > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at snumerics.com Mon Mar 13 16:26:50 2017 From: chrisneal at snumerics.com (Christopher Neal) Date: Mon, 13 Mar 2017 16:26:50 -0400 Subject: [Paraview] Paraview with osMesa compile Message-ID: Hi All, I'm working to compile the paraview superbuild(5.2.0) on OpenSuse13.2 with osMesa enabled(for HPC related CPU in-situ computing). I'm seeing a compile error: [ 44%] Performing build step for 'pythonsetuptools' Traceback (most recent call last): File "setup.py", line 6, in import io File "/usr/lib64/python2.7/io.py", line 51, in import _io ImportError: /home/neal/software/paraview_testbuild/paraview-superbuild-install/install/lib64/python2.7/lib-dynload/_io.so: undefined symbol: PyUnicodeUCS2_Replace CMake Error at /home/neal/software/paraview_testbuild/paraview-superbuild-install/superbuild/sb-pythonsetuptools-build.cmake:43 (message): Failed with exit code 1 I thought that I requested the superbuild to not use my system python, but it appears that it is searching /usr/lib64/python2.7 for something that it fails to read. My current compile script(bolded section pertains to python): cmake \ -DCMAKE_INSTALL_PREFIX:PATH=/home/neal/software/paraview_testbuild/paraview-superbuild-install \ -Dparaview_GIT_TAG='5.2.0' \ -DCMAKE_BUILD_TYPE=Release \ -DENABLE_hdf5=ON \ -DENABLE_osmesa=ON \ -DENABLE_mesa=OFF \ -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \ -DENABLE_mpi=ON \ -DUSE_SYSTEM_mpi=OFF \ -DENABLE_paraview=ON \ *-DENABLE_python=ON \ -DUSE_SYSTEM_python=OFF \ -DENABLE_numpy=ON \ -DENABLE_matplotlib=ON \* -DENABLE_qt=OFF \ -Dqt_DISABLE_WEBKIT=ON \ -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \ /home/neal/software/paraview_testbuild/paraview-superbuild make Thank you, -- Christopher Neal Research Engineer Streamline Numerics, Inc. https://www.snumerics.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Mar 13 16:45:58 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Mar 2017 16:45:58 -0400 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Roman, Thanks for the error report, it provides some useful clues. It looks like ParaView is crashing when collecting information about the mounted volumes on your system. Do you have an external drive or network file system mounted on the Mac Pro that is crashing? If so, could you try to unmount it and see if ParaView runs as expected? Barring that, are there any non-Latin characters in the names of the volumes mounted on the Mac in question? Thanks, Cory On Sat, Mar 11, 2017 at 6:49 PM, Roman Kowch wrote: > Sorry, I should have mentioned that I'm running ParaView on a Mac Pro > computer, with OS X 10.11.6. The computer does not have DBaR. > > Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the same > crash I'm seeing on this particular computer. Again, I could send a crash > report if that would help. > > > On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit > wrote: >> >> Do you have Dell Backup and Recovery (DBaR) tools installed on your >> system? If so, the crash may be related to an issue with DBaR at Qt 5. >> You may need to update DBaR to the latest version. See [1] for >> details. >> >> [1] >> http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253 >> >> >> >> On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: >> > Hi, >> > >> > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the GUI. >> > The >> > application however crashes on one of my computers when I simply click >> > "File" then "Open." It seems that the crash happens when it needs to >> > bring >> > up the dialog for selecting a file. It also happens if I do these menu >> > clicks: >> > >> > 1. "File", "Load Window Layout" >> > 2. "File", "Load State" >> > 3. "File", "Save State" >> > >> > As you can see, the crash appears to happen whenever a directory dialog >> > is >> > expected to appear. Should I send a crash report to diagnose this >> > problem? >> > >> > I should also mention that on another computer, this problem does NOT >> > appear >> > for the same build of Paraview. The problem seems unique to a particular >> > computer I'm using. >> > >> > Regards, >> > Roman >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From leonardopessanha74 at gmail.com Mon Mar 13 18:55:08 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Mon, 13 Mar 2017 19:55:08 -0300 Subject: [Paraview] Remote rendering to multiple displays Message-ID: Hi! What would be the best approach in order to achieve this configurations: 1) Remote rendering in a cluster and one client with 6 viewports(Cubemap) 2) Remote rendering in a cluster and X clients with X viewports Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Tue Mar 14 01:55:41 2017 From: antech777 at gmail.com (Andrew) Date: Tue, 14 Mar 2017 08:55:41 +0300 Subject: [Paraview] Unable to open .dat file in paraview In-Reply-To: References: Message-ID: Hello. Anyway, ParaView has not full support for Fluent files (cas + dat). It doesn't see all the variables (at least in versions up to 5.0.1 RC2 that I use, although I know that I should update to 5.2 or 5.3). Instead of reading Fluent format, I convert to EnSight (in Fluent) and then read in ParaView. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Tue Mar 14 04:31:21 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 14 Mar 2017 09:31:21 +0100 Subject: [Paraview] Remote rendering to multiple displays In-Reply-To: References: Message-ID: 1) ParaView in client server mode with remote rendering enabled, connected to a pvserver on your cluster. Multiple viewports are not a problem. 2) X ParaView in client server mode with remote rendering enabled, connected to a pvserver in multi-client mode on your cluster. Multiple viewports are not a problem. Mathieu Westphal On Mon, Mar 13, 2017 at 11:55 PM, L?o Pessanha wrote: > Hi! > > What would be the best approach in order to achieve this configurations: > > 1) Remote rendering in a cluster and one client with 6 viewports(Cubemap) > > 2) Remote rendering in a cluster and X clients with X viewports > > Thanks in advance. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rodneicouto at gmail.com Tue Mar 14 11:01:32 2017 From: rodneicouto at gmail.com (Rodnei Couto) Date: Tue, 14 Mar 2017 12:01:32 -0300 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: Python modules are different from 5.2 to 5.3 For example, inside* lib/python2.7/site-packages, *the version 5.2 has the modules *autobahn, zope and twisted*, and the version 5.3 does not. I tried to copy the twisted and zope modules from version 5.2 to version 5.3, but a got others errors. By now, I reverted to release 5.2 in production environment. Cheers, -- Rodnei Couto | (55 21) 98749-9885 On Mon, Mar 13, 2017 at 3:19 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hum, that is weird. > > It could be a bug. > > Do you mind doing a diff between the 2 python modules between 5.2 and 5.3. > > Twisted should be the same. Then on the ParaView side, I'm not expecting > much difference. > > Thanks for tracking that down... > > Seb > > On Mon, Mar 13, 2017 at 11:42 AM, Rodnei Couto > wrote: > >> Yes, I'm sure there is no twisted library in my system python. >> >> I rollback to version 5.2.0 and everything works fine. >> >> Can be a bug? >> >> -- >> Rodnei Couto | (55 21) 98749-9885 >> >> On Sun, Mar 12, 2017 at 3:12 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> Are you sure, there is no twisted library in your system python? >>> >>> >>> On Fri, Mar 10, 2017 at 6:34 PM, Rodnei Couto >>> wrote: >>> >>>> My version was downloaded from the official site >>>> >>>> ParaView-5.3.0-RC3-Qt5-OpenGL2-MPI-Linux-64bit >>>> >>>> Cheers, >>>> >>>> -- >>>> Rodnei Couto | (55 21) 98749-9885 >>>> >>>> On Fri, Mar 10, 2017 at 6:36 PM, Scott Wittenburg < >>>> scott.wittenburg at kitware.com> wrote: >>>> >>>>> What version of ParaView are you using? One you built yourself (if >>>>> so, how old), or a release binary? >>>>> >>>>> >>>>> On Fri, Mar 10, 2017 at 2:31 PM, Rodnei Couto >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks for the answer. >>>>>> >>>>>> I completely removed the twisted from my machine and the error >>>>>> continue. In fact the error occurred before his installation. I installed >>>>>> twitted to try to solve it >>>>>> >>>>>> Any other ideas? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> >>>>>> -- >>>>>> Rodnei Couto | (55 21) 98749-9885 >>>>>> >>>>>> On Fri, Mar 10, 2017 at 4:55 PM, Scott Wittenburg < >>>>>> scott.wittenburg at kitware.com> wrote: >>>>>> >>>>>>> Did you try to set up your own version of twisted in your system >>>>>>> python? When you illustrated how twisted was properly set up, you did it >>>>>>> with "python", but your start script runs pvpython. I wonder if maybe your >>>>>>> system python twisted is conflicting (or overriding) with the one provided >>>>>>> by pvpython? That's just a guess based on a quick read. >>>>>>> >>>>>>> Hope this helps, >>>>>>> Scott >>>>>>> >>>>>>> On Fri, Mar 10, 2017 at 12:37 PM, Rodnei Couto < >>>>>>> rodneicouto at gmail.com> wrote: >>>>>>> >>>>>>>> I set up my environment as indicated in http://kitware.github.io/pa >>>>>>>> raviewweb/docs/ubuntu_14_04.html >>>>>>>> >>>>>>>> My operational system is Ubuntu 64 14_04 LTS. >>>>>>>> >>>>>>>> When I try to run my start.sh, I get an error: >>>>>>>> >>>>>>>> pvw-user at cole:/local/pvw-user$ Traceback (most recent call last): >>>>>>>> File "/local/pvw-user/data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py", line 14, in >>>>>>>> from twisted.internet import reactor, defer >>>>>>>> ImportError: No module named twisted.internet >>>>>>>> >>>>>>>> i think the twisted is properly installed in my environment, as can >>>>>>>> be seen below: >>>>>>>> >>>>>>>> pvw-user at cole:/local/pvw-user$ python -c "from twisted.internet import reactor, defer; print( defer ); print ( reactor ) " >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> My start.sh code is: >>>>>>>> >>>>>>>> #!/bin/bash >>>>>>>> export DISPLAY=:0.0 >>>>>>>> /data/pv/pv-current/bin/pvpython /data/pv/pv-current/lib/python2.7/site-packages/vtk/web/launcher.py /data/pvw/conf/launcher.json & >>>>>>>> >>>>>>>> >>>>>>>> Can anybody help me? I do not know what else I can do >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> ? >>>>>>>> >>>>>>>> Rodnei Couto | (55 21) 98749-9885 >>>>>>>> ? >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Mar 14 11:39:00 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 14 Mar 2017 11:39:00 -0400 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: References: Message-ID: <20170314153900.GA28423@rotor> On Tue, Mar 14, 2017 at 12:01:32 -0300, Rodnei Couto wrote: > Python modules are different from 5.2 to 5.3 > > For example, inside* lib/python2.7/site-packages, *the version 5.2 has the > modules *autobahn, zope and twisted*, and the version 5.3 does not. > > I tried to copy the twisted and zope modules from version 5.2 to version > 5.3, but a got others errors. > > By now, I reverted to release 5.2 in production environment. Looking at the superbuild, it appears that when ParaViewWeb got moved from ParaView into its own repository, the flags that turned on pvweb got removed and now there's nothing enabling those modules in ParaView's build anymore. Do those packages need to be shipped with ParaView at all now? If so, we'll need to add them to the superbuild specifically. If not, some flag will need to be used to turn them on. --Ben From sebastien.jourdain at kitware.com Tue Mar 14 11:50:10 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 14 Mar 2017 09:50:10 -0600 Subject: [Paraview] ParaView Web - module twisted.internet error In-Reply-To: <20170314153900.GA28423@rotor> References: <20170314153900.GA28423@rotor> Message-ID: Hi Ben, Those modules are needed and should be shipped with ParaView. I believe the issue might be in the ParaView project itself not in its superbuild. I'm guessing, I messed up a dependency when I split the python code between python 2+3 and python 2 only. The python 2 one should depend on those libraries but not the python 2+3 code. Let me know how I can help to fix that, Thanks, Seb On Tue, Mar 14, 2017 at 9:39 AM, Ben Boeckel wrote: > On Tue, Mar 14, 2017 at 12:01:32 -0300, Rodnei Couto wrote: > > Python modules are different from 5.2 to 5.3 > > > > For example, inside* lib/python2.7/site-packages, *the version 5.2 has > the > > modules *autobahn, zope and twisted*, and the version 5.3 does not. > > > > I tried to copy the twisted and zope modules from version 5.2 to version > > 5.3, but a got others errors. > > > > By now, I reverted to release 5.2 in production environment. > > Looking at the superbuild, it appears that when ParaViewWeb got moved > from ParaView into its own repository, the flags that turned on pvweb > got removed and now there's nothing enabling those modules in ParaView's > build anymore. Do those packages need to be shipped with ParaView at all > now? If so, we'll need to add them to the superbuild specifically. If > not, some flag will need to be used to turn them on. > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkulesza at umich.edu Tue Mar 14 12:29:25 2017 From: jkulesza at umich.edu (Joel Kulesza) Date: Tue, 14 Mar 2017 10:29:25 -0600 Subject: [Paraview] Gridline Visibility Reduction Inquiry (v.5.3.0) Message-ID: Colleagues: After installing 5.3.0-RC2 and now 5.3.0 (both after using 5.2.0), the Plot gridlines have become almost invisible (see attached screenshot). There also appears to be a radial gradient about the center. I run a 3840x2160 display on OS X 10.11.6. Is this expected behavior? Please contact me with any comments, questions, or concerns. Thank you, Joel Joel A. Kulesza, P.E.Ph.D. Candidate / Graduate Student Researcher University of Michigan, College of EngineeringNuclear Engineering & Radiological Sciences Dept.2355 Bonisteel Boulevard Ann Arbor, MI 48109-2104, USAMobile: +1 (734) 223-7312Email: jkulesza at umich.eduHome Page: http://www.engin.umich.edu/ners/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-14 at 10.00.17.png Type: image/png Size: 409875 bytes Desc: not available URL: From wascott at sandia.gov Tue Mar 14 13:59:26 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 14 Mar 2017 17:59:26 +0000 Subject: [Paraview] [EXTERNAL] Gridline Visibility Reduction Inquiry (v.5.3.0) In-Reply-To: References: Message-ID: Joel, Gridlines really are too light. I will add a bug. Thanks for reporting. They can be changed trivially. Make a 2d plot. Properties tab. Advanced. Click Left Axis Grid Color. Make it darker. Repeat for Bottom Axis.. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Joel Kulesza Sent: Tuesday, March 14, 2017 10:29 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Gridline Visibility Reduction Inquiry (v.5.3.0) Colleagues: After installing 5.3.0-RC2 and now 5.3.0 (both after using 5.2.0), the Plot gridlines have become almost invisible (see attached screenshot). There also appears to be a radial gradient about the center. I run a 3840x2160 display on OS X 10.11.6. Is this expected behavior? Please contact me with any comments, questions, or concerns. Thank you, Joel Joel A. Kulesza, P.E. Ph.D. Candidate / Graduate Student Researcher University of Michigan, College of Engineering Nuclear Engineering & Radiological Sciences Dept. 2355 Bonisteel Boulevard Ann Arbor, MI 48109-2104, USA Mobile: +1 (734) 223-7312 Email: jkulesza at umich.edu Home Page: http://www.engin.umich.edu/ners/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank0734 at gmail.com Tue Mar 14 14:24:34 2017 From: frank0734 at gmail.com (Liang Wang) Date: Tue, 14 Mar 2017 14:24:34 -0400 Subject: [Paraview] StreamTracer: Combined ReasonForTermination or select individual polylines? Message-ID: If the IntegrationDirection is set to BOTH, the two segments of the streamlines from the seed might terminate for different reasons. For example, one end might end due to STAGNATION, the other due to OUT_OF_DOMAIN. When coloring by ReasonForTermination, then the two segments are colored differently. My question is: Can a user create more cases of ReasonForTermination so that we can tell examples like above? Or, how can I select individual streamlines by its SeedIds (I tried IdsSelection, but that appears to work for cell/point data only, not for polydata?) My current solution is to use threshold filter to select lines in the different regions and apply different solid colors. But it would be nice if I can handle a few different cases more directly, even if that involves some coding in C++ or Python. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkulesza at umich.edu Tue Mar 14 14:30:02 2017 From: jkulesza at umich.edu (Joel Kulesza) Date: Tue, 14 Mar 2017 12:30:02 -0600 Subject: [Paraview] [EXTERNAL] Gridline Visibility Reduction Inquiry (v.5.3.0) In-Reply-To: References: Message-ID: Alan, Thanks for the quick response. Having changed the colors to black (#000000), I see the attached. There still appears to be some regional washout (on this end). If you see it in the screenshot, I suspect it's *not* a hardware issue. Thanks again, Joel On Tue, Mar 14, 2017 at 11:59 AM, Scott, W Alan wrote: > Joel, > > Gridlines really are too light. I will add a bug. Thanks for reporting. > > > > They can be changed trivially. Make a 2d plot. Properties tab. > Advanced. Click Left Axis Grid Color. Make it darker. Repeat for Bottom > Axis.. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Joel > Kulesza > *Sent:* Tuesday, March 14, 2017 10:29 AM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Gridline Visibility Reduction Inquiry > (v.5.3.0) > > > > Colleagues: > > After installing 5.3.0-RC2 and now 5.3.0 (both after using 5.2.0), the > Plot gridlines have become almost invisible (see attached screenshot). > There also appears to be a radial gradient about the center. > > > > I run a 3840x2160 display on OS X 10.11.6. > > > > Is this expected behavior? > > > > Please contact me with any comments, questions, or concerns. > > > > Thank you, > > Joel > > > > Joel A. Kulesza, P.E. > > Ph.D. Candidate / Graduate Student Researcher > > > > University of Michigan, College of Engineering > > Nuclear Engineering & Radiological Sciences Dept. > > 2355 Bonisteel Boulevard > > Ann Arbor, MI 48109-2104, USA > > Mobile: +1 (734) 223-7312 <(734)%20223-7312> > > Email: jkulesza at umich.edu > > Home Page: http://www.engin.umich.edu/ners/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-14 at 12.20.17.png Type: image/png Size: 433096 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Mar 14 14:32:51 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 14 Mar 2017 14:32:51 -0400 Subject: [Paraview] [EXTERNAL] Gridline Visibility Reduction Inquiry (v.5.3.0) In-Reply-To: References: Message-ID: Issue reported here: https://gitlab.kitware.com/paraview/paraview/issues/17296 On Tue, Mar 14, 2017 at 1:59 PM, Scott, W Alan wrote: > Joel, > > Gridlines really are too light. I will add a bug. Thanks for reporting. > > > > They can be changed trivially. Make a 2d plot. Properties tab. > Advanced. Click Left Axis Grid Color. Make it darker. Repeat for Bottom > Axis.. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Joel > Kulesza > *Sent:* Tuesday, March 14, 2017 10:29 AM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Gridline Visibility Reduction Inquiry > (v.5.3.0) > > > > Colleagues: > > After installing 5.3.0-RC2 and now 5.3.0 (both after using 5.2.0), the > Plot gridlines have become almost invisible (see attached screenshot). > There also appears to be a radial gradient about the center. > > > > I run a 3840x2160 display on OS X 10.11.6. > > > > Is this expected behavior? > > > > Please contact me with any comments, questions, or concerns. > > > > Thank you, > > Joel > > > > Joel A. Kulesza, P.E. > > Ph.D. Candidate / Graduate Student Researcher > > > > University of Michigan, College of Engineering > > Nuclear Engineering & Radiological Sciences Dept. > > 2355 Bonisteel Boulevard > > Ann Arbor, MI 48109-2104, USA > > Mobile: +1 (734) 223-7312 <(734)%20223-7312> > > Email: jkulesza at umich.edu > > Home Page: http://www.engin.umich.edu/ners/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 14 15:17:25 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 14 Mar 2017 15:17:25 -0400 Subject: [Paraview] StreamTracer: Combined ReasonForTermination or select individual polylines? In-Reply-To: References: Message-ID: Hi, What version of ParaView are you using? >From my testing it looks like each direction for the stream tracer seeds has a separate reason for termination in PV 5.3 -- see the attached image. The domain is a box with length 20 on each side, the velocity is [1, 0, 0], the seeds are a line source going from min to max of the bounding box ([-10, -10, -10] to [10,10,10]). The red is for when the maximum streamline length has exceeded my specified max length of 5 and the blue is for when the streamline exited the domain. Is there a case where the same reason for termination value is being used for multiple termination criteria? You can use the SeedIds cell data array in the Threshold filter or use the Edit->Find Data option to select a given streamline from the seed id. Cheers, Andy On Tue, Mar 14, 2017 at 2:24 PM, Liang Wang wrote: > If the IntegrationDirection is set to BOTH, the two segments of the > streamlines from the seed might terminate for different reasons. For > example, one end might end due to STAGNATION, the other due > to OUT_OF_DOMAIN. When coloring by ReasonForTermination, then the two > segments are colored differently. > > My question is: Can a user create more cases of ReasonForTermination so > that we can tell examples like above? Or, how can I select individual > streamlines by its SeedIds (I tried IdsSelection, but that appears to work > for cell/point data only, not for polydata?) > > My current solution is to use threshold filter to select lines in the > different regions and apply different solid colors. But it would be nice if > I can handle a few different cases more directly, even if that involves > some coding in C++ or Python. > > Thanks. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: reasonfortermination.png Type: image/png Size: 62706 bytes Desc: not available URL: From leonardopessanha74 at gmail.com Tue Mar 14 15:30:09 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 14 Mar 2017 16:30:09 -0300 Subject: [Paraview] Remote rendering to multiple displays In-Reply-To: References: Message-ID: I believe I was not clear. The 6 viewports I want to achieve cannot be in the GUI. They have to be separate like when using a .pvx file in the server. The problem is when using a .pvx the viewports are open in the remote machine, I want them to be open in the client machine. Best regards, Leonardo Pessanha 2017-03-14 5:31 GMT-03:00 Mathieu Westphal : > 1) ParaView in client server mode with remote rendering enabled, connected > to a pvserver on your cluster. Multiple viewports are not a problem. > 2) X ParaView in client server mode with remote rendering enabled, > connected to a pvserver in multi-client mode on your cluster. Multiple > viewports are not a problem. > > Mathieu Westphal > > On Mon, Mar 13, 2017 at 11:55 PM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> Hi! >> >> What would be the best approach in order to achieve this configurations: >> >> 1) Remote rendering in a cluster and one client with 6 viewports(Cubemap) >> >> >> 2) Remote rendering in a cluster and X clients with X viewports >> >> Thanks in advance. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank0734 at gmail.com Tue Mar 14 15:47:45 2017 From: frank0734 at gmail.com (Liang Wang) Date: Tue, 14 Mar 2017 15:47:45 -0400 Subject: [Paraview] StreamTracer: Combined ReasonForTermination or select individual polylines? In-Reply-To: References: Message-ID: Thank you, Andy. I): I'm using 5.3 and your example is what I would get. But what I want is a way to tell if the two streamlines from the same seed point are terminated for different reasons. It might be more clear from the image I attached. I would like to tell 1) closed field lines that have both ends terminated on the sphere surface (the red tubes) 2) semi-open field lines that have on the ends terminated on the sphere surface, the other goes out-of-domain (the red and blue tubes) 3) open field lines that have both ends out-of-bound (not shown in the image, would be blue tubes) (Or, ideal, I would be happier to be able to tell if the open end of the semi-open field lines goes out of the southern or northern bound) Indeed, I saw people doing this in Mayavi-based python (see https://github.com/KristoforMaynard/Viscid/blob/dev/viscid/cython/streamline.pyx and http://kristoformaynard.github.io/Viscid/docs/master/examples/mayavi.html). One obstacle I can see is that ParaView (or vtk?) probably treats the two streamlines from the same seed point independently, thus it won't be easy to tag them together. II): I realize that I am demanding too much. I tried your way of `Find Data`, and now I am able to manually choose individual streamlines, which is already helpful. On Tue, Mar 14, 2017 at 3:17 PM, Andy Bauer wrote: > Hi, > > What version of ParaView are you using? > > From my testing it looks like each direction for the stream tracer seeds > has a separate reason for termination in PV 5.3 -- see the attached image. > The domain is a box with length 20 on each side, the velocity is [1, 0, 0], > the seeds are a line source going from min to max of the bounding box > ([-10, -10, -10] to [10,10,10]). The red is for when the maximum > streamline length has exceeded my specified max length of 5 and the blue is > for when the streamline exited the domain. > > Is there a case where the same reason for termination value is being used > for multiple termination criteria? > > You can use the SeedIds cell data array in the Threshold filter or use the > Edit->Find Data option to select a given streamline from the seed id. > > Cheers, > Andy > > > > On Tue, Mar 14, 2017 at 2:24 PM, Liang Wang wrote: > >> If the IntegrationDirection is set to BOTH, the two segments of the >> streamlines from the seed might terminate for different reasons. For >> example, one end might end due to STAGNATION, the other due >> to OUT_OF_DOMAIN. When coloring by ReasonForTermination, then the two >> segments are colored differently. >> >> My question is: Can a user create more cases of ReasonForTermination so >> that we can tell examples like above? Or, how can I select individual >> streamlines by its SeedIds (I tried IdsSelection, but that appears to work >> for cell/point data only, not for polydata?) >> >> My current solution is to use threshold filter to select lines in the >> different regions and apply different solid colors. But it would be nice if >> I can handle a few different cases more directly, even if that involves >> some coding in C++ or Python. >> >> Thanks. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: example-magnetic-field-lines-closed-and-semi-open.png Type: image/png Size: 131227 bytes Desc: not available URL: From frank0734 at gmail.com Tue Mar 14 16:31:59 2017 From: frank0734 at gmail.com (Liang Wang) Date: Tue, 14 Mar 2017 16:31:59 -0400 Subject: [Paraview] StreamTracer: Combined ReasonForTermination or select individual polylines? In-Reply-To: References: Message-ID: A follow-up question: How to perform the `Find Data` by `criteria` in Python? I tried to record a macro but only got extractSelection1 = ExtractSelection(Input=tube1, Selection=None) On Tue, Mar 14, 2017 at 3:47 PM, Liang Wang wrote: > Thank you, Andy. > > > I): > > I'm using 5.3 and your example is what I would get. But what I want is a > way to tell if the two streamlines from the same seed point are terminated > for different reasons. It might be more clear from the image I attached. I > would like to tell > > 1) closed field lines that have both ends terminated on the sphere surface > (the red tubes) > 2) semi-open field lines that have on the ends terminated on the sphere > surface, the other goes out-of-domain (the red and blue tubes) > 3) open field lines that have both ends out-of-bound (not shown in the > image, would be blue tubes) > > (Or, ideal, I would be happier to be able to tell if the open end of the > semi-open field lines goes out of the southern or northern bound) > > Indeed, I saw people doing this in Mayavi-based python (see > https://github.com/KristoforMaynard/Viscid/blob/ > dev/viscid/cython/streamline.pyx and http://kristoformaynard. > github.io/Viscid/docs/master/examples/mayavi.html). One obstacle I can > see is that ParaView (or vtk?) probably treats the two streamlines from the > same seed point independently, thus it won't be easy to tag them together. > > II): > > I realize that I am demanding too much. I tried your way of `Find Data`, > and now I am able to manually choose individual streamlines, which is > already helpful. > > > > On Tue, Mar 14, 2017 at 3:17 PM, Andy Bauer > wrote: > >> Hi, >> >> What version of ParaView are you using? >> >> From my testing it looks like each direction for the stream tracer seeds >> has a separate reason for termination in PV 5.3 -- see the attached image. >> The domain is a box with length 20 on each side, the velocity is [1, 0, 0], >> the seeds are a line source going from min to max of the bounding box >> ([-10, -10, -10] to [10,10,10]). The red is for when the maximum >> streamline length has exceeded my specified max length of 5 and the blue is >> for when the streamline exited the domain. >> >> Is there a case where the same reason for termination value is being used >> for multiple termination criteria? >> >> You can use the SeedIds cell data array in the Threshold filter or use >> the Edit->Find Data option to select a given streamline from the seed id. >> >> Cheers, >> Andy >> >> >> >> On Tue, Mar 14, 2017 at 2:24 PM, Liang Wang wrote: >> >>> If the IntegrationDirection is set to BOTH, the two segments of the >>> streamlines from the seed might terminate for different reasons. For >>> example, one end might end due to STAGNATION, the other due >>> to OUT_OF_DOMAIN. When coloring by ReasonForTermination, then the two >>> segments are colored differently. >>> >>> My question is: Can a user create more cases of ReasonForTermination so >>> that we can tell examples like above? Or, how can I select individual >>> streamlines by its SeedIds (I tried IdsSelection, but that appears to work >>> for cell/point data only, not for polydata?) >>> >>> My current solution is to use threshold filter to select lines in the >>> different regions and apply different solid colors. But it would be nice if >>> I can handle a few different cases more directly, even if that involves >>> some coding in C++ or Python. >>> >>> Thanks. >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Tue Mar 14 17:52:53 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Tue, 14 Mar 2017 22:52:53 +0100 Subject: [Paraview] ParaView 5.3.0 released In-Reply-To: References: Message-ID: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> > 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/ Please add the tag to the superbuild. BTW: My whole office is grateful for the reload (F5) and autoscaled warping of PV 5.2 (at least compared to PV 5.0)!! :) Thanks to the folks at kitware for the really cool software! Fabian Dr. Fabian Wein ZISC - Zentralinstitut f?r wissenschaftliches Rechnen Universit?t Erlangen-N?rnberg D-91052 Erlangen, Germany fabian.wein at fau.de From cory.quammen at kitware.com Tue Mar 14 17:58:18 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 14 Mar 2017 17:58:18 -0400 Subject: [Paraview] ParaView 5.3.0 released In-Reply-To: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> References: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> Message-ID: Fabian, The superbuild was tagged with v5.3.0 this morning. Best regards, Cory On Tue, Mar 14, 2017 at 5:52 PM, Fabian Wein wrote: >> 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/ > > Please add the tag to the superbuild. > > BTW: My whole office is grateful for the reload (F5) and autoscaled warping of PV 5.2 (at least compared to PV 5.0)!! :) > > Thanks to the folks at kitware for the really cool software! > > Fabian > > > > > Dr. Fabian Wein > ZISC - Zentralinstitut f?r wissenschaftliches Rechnen > Universit?t Erlangen-N?rnberg > D-91052 Erlangen, Germany > fabian.wein at fau.de > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Tue Mar 14 21:01:57 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 14 Mar 2017 21:01:57 -0400 Subject: [Paraview] StreamTracer: Combined ReasonForTermination or select individual polylines? In-Reply-To: References: Message-ID: In Python you can do something like create a Threshold filter to # create a new 'Threshold' threshold1 = Threshold(Input=streamTracer1) threshold1.Scalars = ['CELLS', 'SeedIds'] threshold1.ThresholdRange = [1.0, 2.0] threshold1.CellData['ReasonForTermination'].GetRange() This will give you the range of values in the threshold output for the ReasonForTermination array. You can query the number of seeds for the high resolution line source with .SeedType.Resolution On Tue, Mar 14, 2017 at 4:31 PM, Liang Wang wrote: > A follow-up question: How to perform the `Find Data` by `criteria` in > Python? I tried to record a macro but only got > > extractSelection1 = ExtractSelection(Input=tube1, > Selection=None) > > On Tue, Mar 14, 2017 at 3:47 PM, Liang Wang wrote: > >> Thank you, Andy. >> >> >> I): >> >> I'm using 5.3 and your example is what I would get. But what I want is a >> way to tell if the two streamlines from the same seed point are terminated >> for different reasons. It might be more clear from the image I attached. I >> would like to tell >> >> 1) closed field lines that have both ends terminated on the sphere >> surface (the red tubes) >> 2) semi-open field lines that have on the ends terminated on the sphere >> surface, the other goes out-of-domain (the red and blue tubes) >> 3) open field lines that have both ends out-of-bound (not shown in the >> image, would be blue tubes) >> >> (Or, ideal, I would be happier to be able to tell if the open end of the >> semi-open field lines goes out of the southern or northern bound) >> >> Indeed, I saw people doing this in Mayavi-based python (see >> https://github.com/KristoforMaynard/Viscid/blob/dev/viscid/ >> cython/streamline.pyx and http://kristoformaynard.github >> .io/Viscid/docs/master/examples/mayavi.html). One obstacle I can see is >> that ParaView (or vtk?) probably treats the two streamlines from the same >> seed point independently, thus it won't be easy to tag them together. >> >> II): >> >> I realize that I am demanding too much. I tried your way of `Find Data`, >> and now I am able to manually choose individual streamlines, which is >> already helpful. >> >> >> >> On Tue, Mar 14, 2017 at 3:17 PM, Andy Bauer >> wrote: >> >>> Hi, >>> >>> What version of ParaView are you using? >>> >>> From my testing it looks like each direction for the stream tracer seeds >>> has a separate reason for termination in PV 5.3 -- see the attached image. >>> The domain is a box with length 20 on each side, the velocity is [1, 0, 0], >>> the seeds are a line source going from min to max of the bounding box >>> ([-10, -10, -10] to [10,10,10]). The red is for when the maximum >>> streamline length has exceeded my specified max length of 5 and the blue is >>> for when the streamline exited the domain. >>> >>> Is there a case where the same reason for termination value is being >>> used for multiple termination criteria? >>> >>> You can use the SeedIds cell data array in the Threshold filter or use >>> the Edit->Find Data option to select a given streamline from the seed id. >>> >>> Cheers, >>> Andy >>> >>> >>> >>> On Tue, Mar 14, 2017 at 2:24 PM, Liang Wang wrote: >>> >>>> If the IntegrationDirection is set to BOTH, the two segments of the >>>> streamlines from the seed might terminate for different reasons. For >>>> example, one end might end due to STAGNATION, the other due >>>> to OUT_OF_DOMAIN. When coloring by ReasonForTermination, then the two >>>> segments are colored differently. >>>> >>>> My question is: Can a user create more cases of ReasonForTermination so >>>> that we can tell examples like above? Or, how can I select individual >>>> streamlines by its SeedIds (I tried IdsSelection, but that appears to work >>>> for cell/point data only, not for polydata?) >>>> >>>> My current solution is to use threshold filter to select lines in the >>>> different regions and apply different solid colors. But it would be nice if >>>> I can handle a few different cases more directly, even if that involves >>>> some coding in C++ or Python. >>>> >>>> Thanks. >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Wed Mar 15 03:36:30 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Wed, 15 Mar 2017 08:36:30 +0100 Subject: [Paraview] ParaView 5.3.0 released In-Reply-To: References: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> <70BFC17A-414F-41AB-B3EC-0076FA809E2B@fau.de> Message-ID: <041a46a8-d0d4-2455-9735-4b611fa79b4d@fau.de> Sorry, this doesn't work for me: I start with a clean directory mkdir pv53 cd pv53 git clone --recursive https://gitlab.kitware.com/paraview/paraview-superbuild.git cd paraview-superbuild git fetch --tags origin git checkout v5.3.0 -> error: pathspec 'v5.3.0' did not match any file(s) known to git. Fabian On 03/15/17 02:21, Cory Quammen wrote: > git fetch --tags origin > git checkout v5.3.0 > > On Tue, Mar 14, 2017 at 6:06 PM, Fabian Wein wrote: >>> The superbuild was tagged with v5.3.0 this morning. >>> >> >> I just did >> >> git clone ?recursive https://gitlab.kitware.com/paraview/paraview-superbuild.git >> cd paraview-superbuild >> git fetch origin >> git checkout v5.3.0 >> >> and got >> error: pathspec 'v5.3.0' did not match any file(s) known to git. >> >> Do I miss something? >> >> Thanks, >> >> Fabian >> >>> Best regards, >>> Cory >>> >>> On Tue, Mar 14, 2017 at 5:52 PM, Fabian Wein wrote: >>>>> 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/ >>>> >>>> Please add the tag to the superbuild. >>>> >>>> BTW: My whole office is grateful for the reload (F5) and autoscaled warping of PV 5.2 (at least compared to PV 5.0)!! :) >>>> >>>> Thanks to the folks at kitware for the really cool software! >>>> >>>> Fabian From mathieu.westphal at kitware.com Wed Mar 15 03:46:08 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 15 Mar 2017 08:46:08 +0100 Subject: [Paraview] Remote rendering to multiple displays In-Reply-To: References: Message-ID: In this case you will need to have a render server running on your client, and a data server running on your cluster. http://www.paraview.org/Wiki/ParaView:Server_Configuration#Case_Three:_Simple_connection_to_a_data-server.2Frender-server This should work, but will definitelly not be ideal since whole dataset will be transferred from the data server to the render server. Regards, Mathieu Westphal On Tue, Mar 14, 2017 at 8:30 PM, L?o Pessanha wrote: > I believe I was not clear. > > The 6 viewports I want to achieve cannot be in the GUI. They have to be > separate like when using a .pvx file in the server. > > The problem is when using a .pvx the viewports are open in the remote > machine, I want them to be open in the client machine. > > Best regards, > Leonardo Pessanha > > 2017-03-14 5:31 GMT-03:00 Mathieu Westphal : > >> 1) ParaView in client server mode with remote rendering enabled, >> connected to a pvserver on your cluster. Multiple viewports are not a >> problem. >> 2) X ParaView in client server mode with remote rendering enabled, >> connected to a pvserver in multi-client mode on your cluster. Multiple >> viewports are not a problem. >> >> Mathieu Westphal >> >> On Mon, Mar 13, 2017 at 11:55 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Hi! >>> >>> What would be the best approach in order to achieve this configurations: >>> >>> 1) Remote rendering in a cluster and one client with 6 >>> viewports(Cubemap) >>> >>> 2) Remote rendering in a cluster and X clients with X viewports >>> >>> Thanks in advance. >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Mar 15 08:53:07 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 15 Mar 2017 08:53:07 -0400 Subject: [Paraview] ParaView 5.3.0 released In-Reply-To: References: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> Message-ID: <20170315125307.GA24161@megas.kitware.com> On Tue, Mar 14, 2017 at 17:58:18 -0400, Cory Quammen wrote: > The superbuild was tagged with v5.3.0 this morning. That may be, but it seems you missed pushing it to the main repository :) . --Ben From cory.quammen at kitware.com Wed Mar 15 09:42:40 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 15 Mar 2017 09:42:40 -0400 Subject: [Paraview] ParaView 5.3.0 released In-Reply-To: <20170315125307.GA24161@megas.kitware.com> References: <6E5B2C1E-846C-4F97-AA2C-FDB3E5A148C9@fau.de> <20170315125307.GA24161@megas.kitware.com> Message-ID: My mistake, my push URL was incorrect when I pushed the tag. Should be fixed now. https://gitlab.kitware.com/paraview/paraview-superbuild/tags Sorry for the trouble. Cory On Wed, Mar 15, 2017 at 8:53 AM, Ben Boeckel wrote: > On Tue, Mar 14, 2017 at 17:58:18 -0400, Cory Quammen wrote: >> The superbuild was tagged with v5.3.0 this morning. > > That may be, but it seems you missed pushing it to the main repository > :) . > > --Ben -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Wed Mar 15 09:56:59 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 09:56:59 -0400 Subject: [Paraview] vector plot with multiblock dataset. possible bug or dataset issue? In-Reply-To: <64626.160.75.142.243.1488979739.squirrel@webmail.be.itu.edu.tr> References: <64626.160.75.142.243.1488979739.squirrel@webmail.be.itu.edu.tr> Message-ID: Ufuk, > I have some weird observation with 5.3RC2 when i try to create > visualisation of vector field that is coming from multiblock dataset (has > 4x4 decomposition). The problem is that in the simple visualization > pipeline such as Calculator -> Glyph, i could barely see or pick the > boundaries of the individual blocks which is not good. I do not follow. Are you expecting to see the border between blocks highlighted for some reason? There's no reason to expect that, unless that was a characteristic of your data. > Then i tried to add > MergeBlocks filter just after Calculator and try to visualize data with > Glyph. In this case, it fixes the boundary problem (at least it seems like > that). I don't think I see anything particularly different if I use merge blocks or not. Note, if your "Glyph Mode" is not "All Points" there may be minor differences between which points get selected for glyphing, but that's just coincidental, and any patterns you notice in that case are likely to be aliasing artifacts due to subsampling. > But, when i play with the Glyph Mode property and change it such as > Every Nth Point and set as 3 then i could again see the boundaries with > flat vectors. I just wonder that is it a bug or related with the dataset > itself? If you're referring to the band in the attached image, then this is just an aliasing artifact. Otherwise, here too I am not sure which flat vectors are you referring to. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-15 at 9.56.02 AM.png Type: image/png Size: 581047 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Mar 15 10:47:46 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 10:47:46 -0400 Subject: [Paraview] Potential Memory Error in CAVE mode In-Reply-To: References: Message-ID: You may indeed be running into a limitation of current implementation. To support fast rendering requirements for CAVE, ParaView duplicates geometry between all rendering ranks. Seems like you're running out of memory during that process. On Mon, Mar 13, 2017 at 3:10 PM, Faiz Abidi wrote: > Hi again community! > > I have been testing Paraview 5.2.0 in a CAVE mode with pretty big data (1+ > billion points) while remotely connected to some HPC servers. > > PROBLEM: In CAVE mode, I get the below error when I try to change mode from > "Outline" to "Points". Same issue while doing other things as well like > applying a Glyph (Sphere), etc. > > ERROR: terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > The same issue doesn't occur if I don't use the CAVE mode in that I simple > connect a Paraview client with the HPC servers and don't pass any pvx file. > > I read some similar online discussions pointing towards memory issues but > it's hard for me to believe that given a) I have hundreds of gigs of memory > and most of it remains empty even with my big data loaded, b) the issue > doesn't occur when not in a CAVE mode. > > Anyone experienced any such similar issues? > > Thanks for all the help! > -- > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From aashish.chaudhary at kitware.com Wed Mar 15 11:06:31 2017 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 15 Mar 2017 15:06:31 +0000 Subject: [Paraview] Potential Memory Error in CAVE mode In-Reply-To: References: Message-ID: Faiz, Can you remind us about your setup again so that we can see if something can be done to reduce per rank memory requirements? Also, I am assuming the current setup works if the data is small? On Wed, Mar 15, 2017 at 10:47 AM Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > You may indeed be running into a limitation of current implementation. > To support fast rendering requirements for CAVE, ParaView duplicates > geometry between all rendering ranks. Seems like you're running out of > memory during that process. > > On Mon, Mar 13, 2017 at 3:10 PM, Faiz Abidi wrote: > > Hi again community! > > > > I have been testing Paraview 5.2.0 in a CAVE mode with pretty big data > (1+ > > billion points) while remotely connected to some HPC servers. > > > > PROBLEM: In CAVE mode, I get the below error when I try to change mode > from > > "Outline" to "Points". Same issue while doing other things as well like > > applying a Glyph (Sphere), etc. > > > > ERROR: terminate called after throwing an instance of 'std::bad_alloc' > > what(): std::bad_alloc > > > > The same issue doesn't occur if I don't use the CAVE mode in that I > simple > > connect a Paraview client with the HPC servers and don't pass any pvx > file. > > > > I read some similar online discussions pointing towards memory issues but > > it's hard for me to believe that given a) I have hundreds of gigs of > memory > > and most of it remains empty even with my big data loaded, b) the issue > > doesn't occur when not in a CAVE mode. > > > > Anyone experienced any such similar issues? > > > > Thanks for all the help! > > -- > > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > > +1-540-998-6636 <(540)%20998-6636> > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 15 13:05:09 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 13:05:09 -0400 Subject: [Paraview] XML tag for naming tensor components In-Reply-To: References: Message-ID: Ruben, (apologies for the delayed reply) In the VTU XML, you can add component names as follows: for each of the components. Utkarsh On Tue, Feb 7, 2017 at 8:22 AM, Reuben Kraft wrote: > Hello, > > > > I am writing a VTU xml formatted file for a finite element program. I?m > trying to find the option to specify the component names in my DataArray xml > tag. For example, in paraview instead of listing the tensor values 0-5, I > would like them to say s_xx, s_yy, s_xx, etc. > > > > Does anyone know that tag to do this? I did not see it in the VTK manual. > > > > Thanks, > > Reuben > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Mar 15 13:25:39 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 13:25:39 -0400 Subject: [Paraview] vector plot with multiblock dataset. possible bug or dataset issue? In-Reply-To: <60750.78.182.90.145.1489598235.squirrel@webmail.be.itu.edu.tr> References: <64626.160.75.142.243.1488979739.squirrel@webmail.be.itu.edu.tr> <60750.78.182.90.145.1489598235.squirrel@webmail.be.itu.edu.tr> Message-ID: I am not sure how you can avoid the aliasing effect, expect maybe glyphing all points or using the "Uniform Spatial Distribution" mode and playing the seed and maximum number of points. Alternatively, you can try different modes. e.g. attached is a SurfaceLIC result along with SurfaceLIC + sparser Glyph result. On Wed, Mar 15, 2017 at 1:17 PM, wrote: > Thanks for your help Utkarsh. No, just opposite, I don't want to see the > borders among blocks. And yes, actually I was talking about those bands > that you showed in your mail. In my opinion, it is still weird to have > those bands that exactly appears in the areas that blocks change. Anyway, > I'll look into deeply to the data (generated by Catalyst) to find any > problem. BTW, is it possible to remove aliasing artifacts. As I know 5.3.0 > has some improvements about that but in this case I was using 5.3.0RC2 and > maybe those mods are not default in that particular version. Thanks again, > > Regards, > > --ufuk > >> Ufuk, >> >>> I have some weird observation with 5.3RC2 when i try to create >>> visualisation of vector field that is coming from multiblock dataset >>> (has >>> 4x4 decomposition). The problem is that in the simple visualization >>> pipeline such as Calculator -> Glyph, i could barely see or pick the >>> boundaries of the individual blocks which is not good. >> >> I do not follow. Are you expecting to see the border between blocks >> highlighted for some reason? There's no reason to expect that, unless >> that was a characteristic of your data. >> >>> Then i tried to add >>> MergeBlocks filter just after Calculator and try to visualize data with >>> Glyph. In this case, it fixes the boundary problem (at least it seems >>> like >>> that). >> >> I don't think I see anything particularly different if I use merge >> blocks or not. Note, if your "Glyph Mode" is not "All Points" there >> may be minor differences between which points get selected for >> glyphing, but that's just coincidental, and any patterns you notice in >> that case are likely to be aliasing artifacts due to subsampling. >> >>> But, when i play with the Glyph Mode property and change it such as >>> Every Nth Point and set as 3 then i could again see the boundaries with >>> flat vectors. I just wonder that is it a bug or related with the dataset >>> itself? >> >> If you're referring to the band in the attached image, then this is >> just an aliasing artifact. Otherwise, here too I am not sure which >> flat vectors are you referring to. >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-15 at 1.21.28 PM.png Type: image/png Size: 777192 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-15 at 1.25.20 PM.png Type: image/png Size: 1335254 bytes Desc: not available URL: From marco.cisternino at optimad.it Wed Mar 15 14:08:52 2017 From: marco.cisternino at optimad.it (Marco Cisternino) Date: Wed, 15 Mar 2017 18:08:52 +0000 Subject: [Paraview] rendering window position on screen Message-ID: Good morning, I wrote a python script in order to process my data and to render the result at the end. To do this last step I call Render(myRenderView) Interact() and the rendering window is open at the top left corner of my screen. How can I change the position of the rendering window? Thanks a lot for any hint. Best regards, Marco Cisternino, PhD marco.cisternino at optimad.it _______________________________ OPTIMAD Engineering srl Via Giacinto Collegno 18, Torino, Italia. +3901119719782 www.optimad.it From utkarsh.ayachit at kitware.com Wed Mar 15 14:16:59 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 14:16:59 -0400 Subject: [Paraview] rendering window position on screen In-Reply-To: References: Message-ID: It not really well supported, but something like the following may work on linux/windows: window = view.GetRenderWindow() window.SetPosition(450, 0) Utkarsh On Wed, Mar 15, 2017 at 2:08 PM, Marco Cisternino wrote: > Good morning, > I wrote a python script in order to process my data and to render the result at the end. > To do this last step I call > > Render(myRenderView) > Interact() > > and the rendering window is open at the top left corner of my screen. > How can I change the position of the rendering window? > Thanks a lot for any hint. > Best regards, > > > Marco Cisternino, PhD > marco.cisternino at optimad.it > _______________________________ > OPTIMAD Engineering srl > Via Giacinto Collegno 18, Torino, Italia. > +3901119719782 > www.optimad.it > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From cellinger at lanl.gov Wed Mar 15 13:47:48 2017 From: cellinger at lanl.gov (Ellinger, Carola) Date: Wed, 15 Mar 2017 17:47:48 +0000 Subject: [Paraview] Help on SPHVolumeInterpolator Message-ID: Hello, I have astrophysical SPH (smoothed particle hydrodynamics) data that I want to interpolate for visualization in ParaView. I've found the SPHVolumeInterpolator filter to do that, but can this filter handle non-constant smoothing lengths of SPH particles for the interpolation? If so, how is this set? Due to the nature of the object I'm trying to visualize (a star), the smoothing lengths varies over a few orders of magnitude. Thank you for any help, Carola -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Wed Mar 15 16:21:31 2017 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 15 Mar 2017 20:21:31 +0000 Subject: [Paraview] Help on SPHVolumeInterpolator In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68437EC998@MBX111.d.ethz.ch> Carola the answer is "soon". ParaView's GUI already enables the setting of the so-called Cuttoff Array. In the GUI (I am assuming you use version 5.3), there should be a setting for the Density and the Mass arrays. And just below it, is the 3rd setting for the "smooting length" array. Unfortunately, we are waiting on a patch to the underlying VTK class vtkSPHInterpolator.cxx which currently has a small error preventing the correct setting. By the way, I strongly suggest that you use a version of ParaView compiled with OpenMP, or TBB. You will see great speed-ups on a multi-core node, since the Point Interpolators (Line, Plane, Volume) are all parallelized on-the-node. Until the patch is merged into VTK, and ParaView picks up the change, you will be limited to setting the Density and Mass arrays. (Unless you compile your own ParaView, and I can tell you how to edit the source code to enable the smoothing array.) ----------------- Jean/CSCS ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Ellinger, Carola [cellinger at lanl.gov] Sent: Wednesday, March 15, 2017 6:47 PM To: paraview at paraview.org Subject: [Paraview] Help on SPHVolumeInterpolator Hello, I have astrophysical SPH (smoothed particle hydrodynamics) data that I want to interpolate for visualization in ParaView. I've found the SPHVolumeInterpolator filter to do that, but can this filter handle non-constant smoothing lengths of SPH particles for the interpolation? If so, how is this set? Due to the nature of the object I'm trying to visualize (a star), the smoothing lengths varies over a few orders of magnitude. Thank you for any help, Carola -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank0734 at gmail.com Wed Mar 15 17:40:54 2017 From: frank0734 at gmail.com (Liang Wang) Date: Wed, 15 Mar 2017 17:40:54 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly Message-ID: By using the arrow glyph filter on the lines/tubes, the arrows are often slightly dislocated (and thus slightly misaligned) from the tubes themselves (see the attached image). In comparison, I am trying to get images like http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or https://i.stack.imgur.com/z8nkm.png Logically, the arrows could have been an attribute of the streamlines/stream tubes? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: arrows-on-tubes.png Type: image/png Size: 578472 bytes Desc: not available URL: From andy.bauer at kitware.com Wed Mar 15 17:50:33 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 15 Mar 2017 17:50:33 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: Hi, How does it look if you Glyph the streamlines themselves instead of the tubes? On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang wrote: > By using the arrow glyph filter on the lines/tubes, the arrows are often > slightly dislocated (and thus slightly misaligned) from the tubes > themselves (see the attached image). > > In comparison, I am trying to get images like http://www.tecplot.com/wp- > content/uploads/2016/01/fstream.jpg or https://i.stack.imgur.com/z8nkm.png > > Logically, the arrows could have been an attribute of the > streamlines/stream tubes? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank0734 at gmail.com Wed Mar 15 17:59:07 2017 From: frank0734 at gmail.com (Liang Wang) Date: Wed, 15 Mar 2017 17:59:07 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: Hi Andy, The results are similar if I apply glyph on streamlines directly (see the attached image). I guess the difficulty part is that arrow heads are not easily centered on lines/tubes? On Wed, Mar 15, 2017 at 5:50 PM, Andy Bauer wrote: > Hi, > > How does it look if you Glyph the streamlines themselves instead of the > tubes? > > On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang wrote: > >> By using the arrow glyph filter on the lines/tubes, the arrows are often >> slightly dislocated (and thus slightly misaligned) from the tubes >> themselves (see the attached image). >> >> In comparison, I am trying to get images like >> http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or >> https://i.stack.imgur.com/z8nkm.png >> >> Logically, the arrows could have been an attribute of the >> streamlines/stream tubes? >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: arrows-on-lines.png Type: image/png Size: 326803 bytes Desc: not available URL: From andy.bauer at kitware.com Wed Mar 15 18:16:06 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 15 Mar 2017 18:16:06 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: I think it is because you have set the Shaft radius to 0. The start of the arrow doesn't appear because of this and I'm suspecting that the start of the arrow is centered along the streamline. Maybe try using using either a non-zero value for the Shaft radius that is bigger than the Tube radius or use the Cone glyph type instead. On Wed, Mar 15, 2017 at 5:59 PM, Liang Wang wrote: > Hi Andy, > > The results are similar if I apply glyph on streamlines directly (see the > attached image). > > I guess the difficulty part is that arrow heads are not easily centered on > lines/tubes? > > On Wed, Mar 15, 2017 at 5:50 PM, Andy Bauer > wrote: > >> Hi, >> >> How does it look if you Glyph the streamlines themselves instead of the >> tubes? >> >> On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang wrote: >> >>> By using the arrow glyph filter on the lines/tubes, the arrows are often >>> slightly dislocated (and thus slightly misaligned) from the tubes >>> themselves (see the attached image). >>> >>> In comparison, I am trying to get images like >>> http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or >>> https://i.stack.imgur.com/z8nkm.png >>> >>> Logically, the arrows could have been an attribute of the >>> streamlines/stream tubes? >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrealphus at gmail.com Wed Mar 15 19:24:14 2017 From: andrealphus at gmail.com (andrealphus) Date: Wed, 15 Mar 2017 16:24:14 -0700 Subject: [Paraview] Paraview 5.2.0 compilation with support for HMD and Python In-Reply-To: References: Message-ID: Just to slightly thread jack for a second, will there be continued development for both Oculus and Vive? I'm leaning towards a Vive and it looks like that was the one originally recommended. Maybe more importantly, and thoughts on whether we're going to see this working on Linux any time soon. It seems like vrserver is working on linux but there is no full VRsteam support. Anyone had success using a Vive on a *nix machine with a windows VM (I mean usable success, with minimum latency). Thanks Ken! -ashton On Tue, Jan 10, 2017 at 6:36 AM, Ken Martin wrote: > > Hi Guillaume, > > I hope to get some time to clean up some issues with the code and to merge > it into PV master. It will probably be a bit though as right now I am > taking another pass at the OpenVR VTK code which it is based on to add a > medical (volume rendering) example and a few options such as a floor etc. > Once that is done, I'll try to get to another pass on the PV code and get > it merged. For now the code can be found at > > https://gitlab.kitware.com/ken-martin/paraview/commits/add_vr_2 > > but I believe that is old and not rebased to 5.2.0. Best bet would be to > rebase that to 5.2.0 and then update VTK to master to get the latest OpenVR > SDK fixes and then hope the two work/compile together. > > > > > > > > On Tue, Jan 10, 2017 at 9:23 AM, Cory Quammen > wrote: > >> Hi Guillaume, >> >> Ken Martin is responsible for this cool version of ParaView. I'm not >> sure that the code is ready for release just yet - Ken can tell you >> more. >> >> Thanks, >> Cory >> >> On Tue, Jan 10, 2017 at 5:55 AM, Guillaume Jacquenot >> wrote: >> > I have seen that Kitware developers have proposed a ParaView version >> with >> > support for Oculus Rift and HTC Vive HMD. >> > And it looks awesome, and opens a wide range of opportunities. >> > >> > https://blog.kitware.com/taking-paraview-into-virtual-reality/ >> > >> > However, the proposed version does not embed Python scripting >> possibilities. >> > >> > I would like to benefit from these functionnalities. >> > >> > Can anyone give me some advice on: >> > - where to find the source code with the support for HMD >> > - how to compile to the code with Python support >> > >> > The best would be a link to an installation file, but I am ready to >> compile >> > it! >> > >> > Thanks >> > >> > Guillaume Jacquenot >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 <(518)%20371-3971> > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 15 20:12:01 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 20:12:01 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: Try changing the "Glyph Type" to Cone. See attached image. On Wed, Mar 15, 2017 at 6:16 PM, Andy Bauer wrote: > I think it is because you have set the Shaft radius to 0. The start of the > arrow doesn't appear because of this and I'm suspecting that the start of > the arrow is centered along the streamline. Maybe try using using either a > non-zero value for the Shaft radius that is bigger than the Tube radius or > use the Cone glyph type instead. > > On Wed, Mar 15, 2017 at 5:59 PM, Liang Wang wrote: >> >> Hi Andy, >> >> The results are similar if I apply glyph on streamlines directly (see the >> attached image). >> >> I guess the difficulty part is that arrow heads are not easily centered on >> lines/tubes? >> >> On Wed, Mar 15, 2017 at 5:50 PM, Andy Bauer >> wrote: >>> >>> Hi, >>> >>> How does it look if you Glyph the streamlines themselves instead of the >>> tubes? >>> >>> On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang wrote: >>>> >>>> By using the arrow glyph filter on the lines/tubes, the arrows are often >>>> slightly dislocated (and thus slightly misaligned) from the tubes themselves >>>> (see the attached image). >>>> >>>> In comparison, I am trying to get images like >>>> http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or >>>> https://i.stack.imgur.com/z8nkm.png >>>> >>>> Logically, the arrows could have been an attribute of the >>>> streamlines/stream tubes? >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-15 at 8.11.45 PM.png Type: image/png Size: 194638 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Mar 15 20:14:20 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Mar 2017 20:14:20 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: To control spacing of the glyphs, on the Glyph's properties panel you can change the Glyph Mode to "Every Nth Point" and then tweak the "Stride". On Wed, Mar 15, 2017 at 8:12 PM, Utkarsh Ayachit wrote: > Try changing the "Glyph Type" to Cone. See attached image. > > On Wed, Mar 15, 2017 at 6:16 PM, Andy Bauer wrote: >> I think it is because you have set the Shaft radius to 0. The start of the >> arrow doesn't appear because of this and I'm suspecting that the start of >> the arrow is centered along the streamline. Maybe try using using either a >> non-zero value for the Shaft radius that is bigger than the Tube radius or >> use the Cone glyph type instead. >> >> On Wed, Mar 15, 2017 at 5:59 PM, Liang Wang wrote: >>> >>> Hi Andy, >>> >>> The results are similar if I apply glyph on streamlines directly (see the >>> attached image). >>> >>> I guess the difficulty part is that arrow heads are not easily centered on >>> lines/tubes? >>> >>> On Wed, Mar 15, 2017 at 5:50 PM, Andy Bauer >>> wrote: >>>> >>>> Hi, >>>> >>>> How does it look if you Glyph the streamlines themselves instead of the >>>> tubes? >>>> >>>> On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang wrote: >>>>> >>>>> By using the arrow glyph filter on the lines/tubes, the arrows are often >>>>> slightly dislocated (and thus slightly misaligned) from the tubes themselves >>>>> (see the attached image). >>>>> >>>>> In comparison, I am trying to get images like >>>>> http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or >>>>> https://i.stack.imgur.com/z8nkm.png >>>>> >>>>> Logically, the arrows could have been an attribute of the >>>>> streamlines/stream tubes? >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-15 at 8.14.07 PM.png Type: image/png Size: 212174 bytes Desc: not available URL: From fabidi89 at vt.edu Wed Mar 15 20:26:37 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Wed, 15 Mar 2017 20:26:37 -0400 Subject: [Paraview] Potential Memory Error in CAVE mode In-Reply-To: References: Message-ID: Thanks Utkarsh and Ashish for your replies. CC'ing some more people since it may be of interest to them too. Writing pointwise for clarity. 1. Our pipeline involves TurboVNC, VirtualGL, and ParaView 5.2.0. We have a 4 walled CAVE-like system where each wall is driven by two projectors. We are doing mono and not stereo. The Paraview client connects to the remote HPC servers which have 512 GB of memory and GPUs. The data we have is in PVTU format. 2. I have ruled out TurboVNC and VirtualGL as the issue since it all works along with them in the pipeline when I don't use the CAVE mode. But can't be 100% certain about that either. 3. This setup works for small data sets (I have tested for a few million points) but I don't know what's the limit above which this error occurs. I can do some more testing to find out though. 3. Question: if this is a memory issue, I am assuming memory per CPU issue? Because system wide I have 512 GB and at no point while the data is trying to load I see more than 200 GB consumed. I mean, it could be a spike in memory and ParaView crashes so quickly that I can't see it in /proc/meminfo but I am not sure. 4. Question: If it is indeed a memory per CPU issue, do you think using more processes can help divide the workload? And on that note, my second question is that is it even possible to use more processes than displays defined in the PVX file? I have read about tiled displays and using tdx and tdy flags but that won't work in a CAVE mode I assume? Currently, I only use 8 processes, each driving one projector. But if there is a way to bump up my processes while providing only 8 displays in the PVX file, please do let me know. 5. Question: With regards to #4, I was actually trying to do tiled rendering in the sense that for each display in my PVX file (attached), I was defining two geometries (basically half of each). I did load up small data successfully like this and was able to use 16 processes, but ParaView still crashed with memory issues with the big data. 6. Question: On a related note, when I check the memory inspector while ParaView is connected in a CAVE mode, I see the attached picture (pvserver.png). This seems off since though I request 16 processes in this case, I see every process id twice in the memory inspector and apparently, only the first 8 processors work and the rest 8 don't do anything? 7. I just tested using my updated pvx file in which I tried tiling the walls and loaded a 100million points PVTU file, and I got different warnings and errors as attached (errors.png). I don't get any errors with a 10 million data points file and everything else same. I think these errors maybe due to how MPI implements and handles memory? Not sure again. Sorry if it is too much information in one email but just trying to figure out if this is indeed a limitation in the current implementation of ParaView in a CAVE mode. And if so, I would have to significantly cut down on my data size to get any results. Appreciate all the help! On Wed, Mar 15, 2017 at 11:06 AM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Faiz, > > Can you remind us about your setup again so that we can see if something > can be done to reduce per rank memory requirements? Also, I am assuming the > current setup works if the data is small? > > > > On Wed, Mar 15, 2017 at 10:47 AM Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> You may indeed be running into a limitation of current implementation. >> To support fast rendering requirements for CAVE, ParaView duplicates >> geometry between all rendering ranks. Seems like you're running out of >> memory during that process. >> >> On Mon, Mar 13, 2017 at 3:10 PM, Faiz Abidi wrote: >> > Hi again community! >> > >> > I have been testing Paraview 5.2.0 in a CAVE mode with pretty big data >> (1+ >> > billion points) while remotely connected to some HPC servers. >> > >> > PROBLEM: In CAVE mode, I get the below error when I try to change mode >> from >> > "Outline" to "Points". Same issue while doing other things as well like >> > applying a Glyph (Sphere), etc. >> > >> > ERROR: terminate called after throwing an instance of 'std::bad_alloc' >> > what(): std::bad_alloc >> > >> > The same issue doesn't occur if I don't use the CAVE mode in that I >> simple >> > connect a Paraview client with the HPC servers and don't pass any pvx >> file. >> > >> > I read some similar online discussions pointing towards memory issues >> but >> > it's hard for me to believe that given a) I have hundreds of gigs of >> memory >> > and most of it remains empty even with my big data loaded, b) the issue >> > doesn't occur when not in a CAVE mode. >> > >> > Anyone experienced any such similar issues? >> > >> > Thanks for all the help! >> > -- >> > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | >> > +1-540-998-6636 <(540)%20998-6636> >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/ >> opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pvserver.png Type: image/png Size: 118335 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cave-mono-2tiles.pvx Type: application/octet-stream Size: 4037 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: errors.png Type: image/png Size: 191105 bytes Desc: not available URL: From frank0734 at gmail.com Wed Mar 15 22:20:09 2017 From: frank0734 at gmail.com (Liang Wang) Date: Wed, 15 Mar 2017 22:20:09 -0400 Subject: [Paraview] Attach arrows onto streamlines/stream tubes more smoothly In-Reply-To: References: Message-ID: Indeed, using Cone glyph gives much better results, and tweaking by "Stride" is very helpful! Thank you, Andy and Utkarsh. On Wed, Mar 15, 2017 at 8:14 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > To control spacing of the glyphs, on the Glyph's properties panel you > can change the Glyph Mode to "Every Nth Point" and then tweak the > "Stride". > > On Wed, Mar 15, 2017 at 8:12 PM, Utkarsh Ayachit > wrote: > > Try changing the "Glyph Type" to Cone. See attached image. > > > > On Wed, Mar 15, 2017 at 6:16 PM, Andy Bauer > wrote: > >> I think it is because you have set the Shaft radius to 0. The start of > the > >> arrow doesn't appear because of this and I'm suspecting that the start > of > >> the arrow is centered along the streamline. Maybe try using using > either a > >> non-zero value for the Shaft radius that is bigger than the Tube radius > or > >> use the Cone glyph type instead. > >> > >> On Wed, Mar 15, 2017 at 5:59 PM, Liang Wang > wrote: > >>> > >>> Hi Andy, > >>> > >>> The results are similar if I apply glyph on streamlines directly (see > the > >>> attached image). > >>> > >>> I guess the difficulty part is that arrow heads are not easily > centered on > >>> lines/tubes? > >>> > >>> On Wed, Mar 15, 2017 at 5:50 PM, Andy Bauer > >>> wrote: > >>>> > >>>> Hi, > >>>> > >>>> How does it look if you Glyph the streamlines themselves instead of > the > >>>> tubes? > >>>> > >>>> On Wed, Mar 15, 2017 at 5:40 PM, Liang Wang > wrote: > >>>>> > >>>>> By using the arrow glyph filter on the lines/tubes, the arrows are > often > >>>>> slightly dislocated (and thus slightly misaligned) from the tubes > themselves > >>>>> (see the attached image). > >>>>> > >>>>> In comparison, I am trying to get images like > >>>>> http://www.tecplot.com/wp-content/uploads/2016/01/fstream.jpg or > >>>>> https://i.stack.imgur.com/z8nkm.png > >>>>> > >>>>> Logically, the arrows could have been an attribute of the > >>>>> streamlines/stream tubes? > >>>>> > >>>>> _______________________________________________ > >>>>> Powered by www.kitware.com > >>>>> > >>>>> Visit other Kitware open-source projects at > >>>>> http://www.kitware.com/opensource/opensource.html > >>>>> > >>>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>>> http://paraview.org/Wiki/ParaView > >>>>> > >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView > >>>>> > >>>>> Follow this link to subscribe/unsubscribe: > >>>>> http://public.kitware.com/mailman/listinfo/paraview > >>>>> > >>>> > >>> > >> > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.fahner at gmail.com Thu Mar 16 04:39:49 2017 From: tom.fahner at gmail.com (Tom Fahner) Date: Thu, 16 Mar 2017 09:39:49 +0100 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. Message-ID: Dear all, Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1). The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are all rendered nicely, but it looks like some cells are missing in the domain/volume. Is there some setting that I need to apply? Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues. ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all. Best regards, Tom -- T.C. Fahner e: tom.fahner at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Domain.png Type: image/png Size: 287447 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Slice.png Type: image/png Size: 109080 bytes Desc: not available URL: From Mark.Olesen at esi-group.com Thu Mar 16 06:44:38 2017 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Thu, 16 Mar 2017 10:44:38 +0000 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. In-Reply-To: References: Message-ID: Hi Tom, Sorry, no answers - only questions/ideas: Is decompose polyhedral on or off? How do things look using the other setting? If the number of cells corresponds to checkMesh - then you either have no polyhedra, or decompose polyhedral is off. If you use foamToVTK (with and without -poly) and then read the VTK file back in, how does that compare? Using foamToEnsight could be yet another check, but without the option to decompose polyhedra. In most paraview versions I've had issues with slicing through polyhedron (eg, from the motorBike tutorial). The symptoms are either holes in the visual (like you have) or crashing the program. I haven't checked if this is better/worse in 5.3.0. Cheers, /mark ________________________________________ From: ParaView on behalf of Tom Fahner Sent: Thursday, March 16, 2017 9:39:49 AM To: ParaView Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. Dear all, Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1). The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are all rendered nicely, but it looks like some cells are missing in the domain/volume. Is there some setting that I need to apply? Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues. ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all. Best regards, Tom -- T.C. Fahner e: tom.fahner at gmail.com From tom.fahner at gmail.com Thu Mar 16 07:47:05 2017 From: tom.fahner at gmail.com (Tom Fahner) Date: Thu, 16 Mar 2017 12:47:05 +0100 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. In-Reply-To: References: Message-ID: Hi Mark, I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess changing "decompose polyhedral on/off" does not make sense. In fact the smaller mesh that I tested with before did show the correct visualization and that mesh had polyhedral/hexagonal cells. It did not matter whether I used decompose polyhedral on/off. I also have experienced the slicing issues from time to time with various paraview versions with polyhedral meshes, but the effect was typically much less severe than in the current situation. Using foamToVTK (with and without the -poly option) does indeed work and provides the correct visualization. So yes this can be a workaround for now, but I than rather go back to 5.1.2. Regards, Tom 2017-03-16 11:44 GMT+01:00 Mark Olesen : > Hi Tom, > > Sorry, no answers - only questions/ideas: > > Is decompose polyhedral on or off? How do things look using the other > setting? > If the number of cells corresponds to checkMesh - then you either have no > polyhedra, or decompose polyhedral is off. > If you use foamToVTK (with and without -poly) and then read the VTK file > back in, how does that compare? > Using foamToEnsight could be yet another check, but without the option to > decompose polyhedra. > > In most paraview versions I've had issues with slicing through polyhedron > (eg, from the motorBike tutorial). > The symptoms are either holes in the visual (like you have) or crashing > the program. I haven't checked if this is better/worse in 5.3.0. > > Cheers, > /mark > ________________________________________ > From: ParaView on behalf of Tom Fahner < > tom.fahner at gmail.com> > Sent: Thursday, March 16, 2017 9:39:49 AM > To: ParaView > Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some > weird visualization issues. > > Dear all, > > Please find attached two images that show my OpenFOAM model in ParaView > 5.3.0. It was the standard Binary Installers package downloaded from the > website for 64 bit linux (OpenSUSE Leap 42.1). > > The correct number of cells is reported in the information tab (when > compared to OpenFOAM's checkMesh result). The patches are > all rendered nicely, but it looks like some cells are missing in the > domain/volume. > > Is there some setting that I need to apply? > > Please note that the mesh has about 25.8 million cells, for smaller meshes > this was not a problem. A colleague had similar issues. > ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not > able to open the OpenFOAM files at all. > > Best regards, > Tom > > -- > T.C. Fahner > e: tom.fahner at gmail.com > > -- T.C. Fahner e: tom.fahner at gmail.com t: +31-6-52642814 a: Groene Woud 48 4834 BC Delft Netherlands -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark.Olesen at esi-group.com Thu Mar 16 08:08:50 2017 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Thu, 16 Mar 2017 12:08:50 +0000 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. In-Reply-To: References: , Message-ID: Hi Tom, So if foamToVTK works, it sounds like a reader bug. Maybe somewhere where the prism order is getting swapped - or something else where the reader's cell modeller is getting into trouble. It may not work, but if you try to export from paraview to VTK format (ie, use the OpenFOAM reader for reading). Then with some effort it might be able to identify which cells are different. Presumably the cell ordering will be preserved in both cases, but still not 100% trivial. Either way, we need to figure out which cell types are causing the issue, or an off-by-one of whatever. /mark ________________________________________ From: Tom Fahner Sent: Thursday, March 16, 2017 12:47:05 PM To: Mark Olesen Cc: ParaView Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. Hi Mark, I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess changing "decompose polyhedral on/off" does not make sense. In fact the smaller mesh that I tested with before did show the correct visualization and that mesh had polyhedral/hexagonal cells. It did not matter whether I used decompose polyhedral on/off. I also have experienced the slicing issues from time to time with various paraview versions with polyhedral meshes, but the effect was typically much less severe than in the current situation. Using foamToVTK (with and without the -poly option) does indeed work and provides the correct visualization. So yes this can be a workaround for now, but I than rather go back to 5.1.2. Regards, Tom 2017-03-16 11:44 GMT+01:00 Mark Olesen >: Hi Tom, Sorry, no answers - only questions/ideas: Is decompose polyhedral on or off? How do things look using the other setting? If the number of cells corresponds to checkMesh - then you either have no polyhedra, or decompose polyhedral is off. If you use foamToVTK (with and without -poly) and then read the VTK file back in, how does that compare? Using foamToEnsight could be yet another check, but without the option to decompose polyhedra. In most paraview versions I've had issues with slicing through polyhedron (eg, from the motorBike tutorial). The symptoms are either holes in the visual (like you have) or crashing the program. I haven't checked if this is better/worse in 5.3.0. Cheers, /mark ________________________________________ From: ParaView > on behalf of Tom Fahner > Sent: Thursday, March 16, 2017 9:39:49 AM To: ParaView Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. Dear all, Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1). The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are all rendered nicely, but it looks like some cells are missing in the domain/volume. Is there some setting that I need to apply? Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues. ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all. Best regards, Tom -- T.C. Fahner e: tom.fahner at gmail.com> -- T.C. Fahner e: tom.fahner at gmail.com t: +31-6-52642814 a: Groene Woud 48 4834 BC Delft Netherlands From utkarsh.ayachit at kitware.com Thu Mar 16 08:12:48 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Mar 2017 08:12:48 -0400 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. In-Reply-To: References: Message-ID: Tom, Do you have a dataset to reproduce this issue? There were changes in the reader in this past release, so it's conceivable that it introduced a bug. Utkarsh On Thu, Mar 16, 2017 at 8:08 AM, Mark Olesen wrote: > Hi Tom, > > So if foamToVTK works, it sounds like a reader bug. Maybe somewhere where the prism order is getting swapped - or something else where the reader's cell modeller is getting into trouble. > It may not work, but if you try to export from paraview to VTK format (ie, use the OpenFOAM reader for reading). Then with some effort it might be able to identify which cells are different. Presumably the cell ordering will be preserved in both cases, but still not 100% trivial. Either way, we need to figure out which cell types are causing the issue, or an off-by-one of whatever. > > /mark > ________________________________________ > From: Tom Fahner > Sent: Thursday, March 16, 2017 12:47:05 PM > To: Mark Olesen > Cc: ParaView > Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. > > Hi Mark, > > I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess changing "decompose polyhedral on/off" does not make sense. In fact the smaller mesh that I tested with before did show the correct visualization and that mesh had polyhedral/hexagonal cells. It did not matter whether I used decompose polyhedral on/off. I also have experienced the slicing issues from time to time with various paraview versions with polyhedral meshes, but the effect was typically much less severe than in the current situation. > > Using foamToVTK (with and without the -poly option) does indeed work and provides the correct visualization. So yes this can be a workaround for now, but I than rather go back to 5.1.2. > > Regards, > Tom > > 2017-03-16 11:44 GMT+01:00 Mark Olesen >: > Hi Tom, > > Sorry, no answers - only questions/ideas: > > Is decompose polyhedral on or off? How do things look using the other setting? > If the number of cells corresponds to checkMesh - then you either have no polyhedra, or decompose polyhedral is off. > If you use foamToVTK (with and without -poly) and then read the VTK file back in, how does that compare? > Using foamToEnsight could be yet another check, but without the option to decompose polyhedra. > > In most paraview versions I've had issues with slicing through polyhedron (eg, from the motorBike tutorial). > The symptoms are either holes in the visual (like you have) or crashing the program. I haven't checked if this is better/worse in 5.3.0. > > Cheers, > /mark > ________________________________________ > From: ParaView > on behalf of Tom Fahner > > Sent: Thursday, March 16, 2017 9:39:49 AM > To: ParaView > Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. > > Dear all, > > Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1). > > The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are > all rendered nicely, but it looks like some cells are missing in the domain/volume. > > Is there some setting that I need to apply? > > Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues. > ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all. > > Best regards, > Tom > > -- > T.C. Fahner > e: tom.fahner at gmail.com> > > > > > -- > T.C. Fahner > e: tom.fahner at gmail.com > t: +31-6-52642814 > a: Groene Woud 48 > 4834 BC Delft > Netherlands > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From tom.fahner at gmail.com Thu Mar 16 08:25:28 2017 From: tom.fahner at gmail.com (Tom Fahner) Date: Thu, 16 Mar 2017 13:25:28 +0100 Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues. In-Reply-To: References: Message-ID: Hi, Let me check if that is possible, I do not think I can share this particular one. I will come back to you. Tom 2017-03-16 13:12 GMT+01:00 Utkarsh Ayachit : > Tom, > > Do you have a dataset to reproduce this issue? There were changes in > the reader in this past release, so it's conceivable that it > introduced a bug. > > Utkarsh > > On Thu, Mar 16, 2017 at 8:08 AM, Mark Olesen > wrote: > > Hi Tom, > > > > So if foamToVTK works, it sounds like a reader bug. Maybe somewhere > where the prism order is getting swapped - or something else where the > reader's cell modeller is getting into trouble. > > It may not work, but if you try to export from paraview to VTK format > (ie, use the OpenFOAM reader for reading). Then with some effort it might > be able to identify which cells are different. Presumably the cell ordering > will be preserved in both cases, but still not 100% trivial. Either way, we > need to figure out which cell types are causing the issue, or an off-by-one > of whatever. > > > > /mark > > ________________________________________ > > From: Tom Fahner > > Sent: Thursday, March 16, 2017 12:47:05 PM > > To: Mark Olesen > > Cc: ParaView > > Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has > some weird visualization issues. > > > > Hi Mark, > > > > I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess > changing "decompose polyhedral on/off" does not make sense. In fact the > smaller mesh that I tested with before did show the correct visualization > and that mesh had polyhedral/hexagonal cells. It did not matter whether I > used decompose polyhedral on/off. I also have experienced the slicing > issues from time to time with various paraview versions with polyhedral > meshes, but the effect was typically much less severe than in the current > situation. > > > > Using foamToVTK (with and without the -poly option) does indeed work and > provides the correct visualization. So yes this can be a workaround for > now, but I than rather go back to 5.1.2. > > > > Regards, > > Tom > > > > 2017-03-16 11:44 GMT+01:00 Mark Olesen mailto:Mark.Olesen at esi-group.com>>: > > Hi Tom, > > > > Sorry, no answers - only questions/ideas: > > > > Is decompose polyhedral on or off? How do things look using the other > setting? > > If the number of cells corresponds to checkMesh - then you either have > no polyhedra, or decompose polyhedral is off. > > If you use foamToVTK (with and without -poly) and then read the VTK file > back in, how does that compare? > > Using foamToEnsight could be yet another check, but without the option > to decompose polyhedra. > > > > In most paraview versions I've had issues with slicing through > polyhedron (eg, from the motorBike tutorial). > > The symptoms are either holes in the visual (like you have) or crashing > the program. I haven't checked if this is better/worse in 5.3.0. > > > > Cheers, > > /mark > > ________________________________________ > > From: ParaView paraview.org>> on behalf of Tom Fahner om.fahner at gmail.com>> > > Sent: Thursday, March 16, 2017 9:39:49 AM > > To: ParaView > > Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some > weird visualization issues. > > > > Dear all, > > > > Please find attached two images that show my OpenFOAM model in ParaView > 5.3.0. It was the standard Binary Installers package downloaded from the > website for 64 bit linux (OpenSUSE Leap 42.1). > > > > The correct number of cells is reported in the information tab (when > compared to OpenFOAM's checkMesh result). The patches are > > all rendered nicely, but it looks like some cells are missing in the > domain/volume. > > > > Is there some setting that I need to apply? > > > > Please note that the mesh has about 25.8 million cells, for smaller > meshes this was not a problem. A colleague had similar issues. > > ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not > able to open the OpenFOAM files at all. > > > > Best regards, > > Tom > > > > -- > > T.C. Fahner > > e: tom.fahner at gmail.com .fahner at gmail.com> > > > > > > > > > > -- > > T.C. Fahner > > e: tom.fahner at gmail.com > > t: +31-6-52642814 > > a: Groene Woud 48 > > 4834 BC Delft > > Netherlands > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > -- T.C. Fahner e: tom.fahner at gmail.com t: +31-6-52642814 a: Groene Woud 48 4834 BC Delft Netherlands -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Thu Mar 16 08:37:59 2017 From: will.schroeder at kitware.com (Will Schroeder) Date: Thu, 16 Mar 2017 08:37:59 -0400 Subject: [Paraview] Help on SPHVolumeInterpolator In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F68437EC998@MBX111.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F68437EC998@MBX111.d.ethz.ch> Message-ID: Carola- What Jean said :-) The patch is waiting on me and I am waiting on deadlines which will be clearing up shortly. If you haven't seen these yet, it's worth reviewing these articles: https://blog.kitware.com/point-and-smoothed-particle-hydrodynamics-sph-interpolation-in-vtk/ https://blog.kitware.com/point-and-smoothed-particle-hydrodynamics-sph-interpolation-in-paraview/ Best, W On Wed, Mar 15, 2017 at 4:21 PM, Favre Jean wrote: > Carola > > the answer is "soon". ParaView's GUI already enables the setting of the > so-called Cuttoff Array. In the GUI (I am assuming you use version 5.3), > there should be a setting for the Density and the Mass arrays. And just > below it, is the 3rd setting for the "smooting length" array. > Unfortunately, we are waiting on a patch to the underlying VTK class > vtkSPHInterpolator.cxx which currently has a small error preventing the > correct setting. > > By the way, I strongly suggest that you use a version of ParaView compiled > with OpenMP, or TBB. You will see great speed-ups on a multi-core node, > since the Point Interpolators (Line, Plane, Volume) are all parallelized > on-the-node. > > Until the patch is merged into VTK, and ParaView picks up the change, you > will be limited to setting the Density and Mass arrays. (Unless you compile > your own ParaView, and I can tell you how to edit the source code to enable > the smoothing array.) > > ----------------- > Jean/CSCS > ------------------------------ > *From:* ParaView [paraview-bounces at paraview.org] on behalf of Ellinger, > Carola [cellinger at lanl.gov] > *Sent:* Wednesday, March 15, 2017 6:47 PM > *To:* paraview at paraview.org > *Subject:* [Paraview] Help on SPHVolumeInterpolator > > Hello, > > I have astrophysical SPH (smoothed particle hydrodynamics) data that I > want to interpolate for visualization in ParaView. I've found the > SPHVolumeInterpolator filter to do that, but can this filter handle > non-constant smoothing lengths of SPH particles for the interpolation? If > so, how is this set? Due to the nature of the object I'm trying to > visualize (a star), the smoothing lengths varies over a few orders of > magnitude. > > Thank you for any help, > > Carola > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- William J. Schroeder, PhD Kitware, Inc. - Building the World's Technical Computing Software 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Thu Mar 16 11:57:43 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Thu, 16 Mar 2017 18:57:43 +0300 Subject: [Paraview] Multiple volumes Message-ID: Hello, I create two wavelets then change their representation to volume and translating(20,0,0) one of the wavelets. Then after I turn around camera I get this:[image: ?????????? ??????????? 1][image: ?????????? ??????????? 2] It seems like the wavelet that was created first is not transparent at all. Shouldn't it be the same picture when I turn camera around? I managed to get the correct result when I appended two datasets but I don't think that it is the right solution. Best Regards, Rustem -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 190064 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 227297 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 16 11:59:58 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Mar 2017 11:59:58 -0400 Subject: [Paraview] Multiple volumes In-Reply-To: References: Message-ID: Multiple volume renderings are currently not supported in ParaView. There's work ongoing that may make this possible in the future. On Thu, Mar 16, 2017 at 11:57 AM, Rustem Khabetdinov < rustem.khabetdinov at gmail.com> wrote: > Hello, > I create two wavelets then change their representation to volume and > translating(20,0,0) one of the wavelets. Then after I turn around camera I > get this:[image: ?????????? ??????????? 1][image: ?????????? ??????????? > 2] > It seems like the wavelet that was created first is not transparent at > all. Shouldn't it be the same picture when I turn camera around? > I managed to get the correct result when I appended two datasets but I > don't think that it is the right solution. > > Best Regards, > Rustem > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 227297 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 190064 bytes Desc: not available URL: From rustem.khabetdinov at gmail.com Thu Mar 16 12:17:29 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Thu, 16 Mar 2017 19:17:29 +0300 Subject: [Paraview] Multiple volumes In-Reply-To: References: Message-ID: Thank you, Rustem On 16 Mar 2017 18:59, "Utkarsh Ayachit" wrote: > Multiple volume renderings are currently not supported in ParaView. > There's work ongoing that may make this possible in the future. > > On Thu, Mar 16, 2017 at 11:57 AM, Rustem Khabetdinov < > rustem.khabetdinov at gmail.com> wrote: > >> Hello, >> I create two wavelets then change their representation to volume and >> translating(20,0,0) one of the wavelets. Then after I turn around camera I >> get this:[image: ?????????? ??????????? 1][image: ?????????? ??????????? >> 2] >> It seems like the wavelet that was created first is not transparent at >> all. Shouldn't it be the same picture when I turn camera around? >> I managed to get the correct result when I appended two datasets but I >> don't think that it is the right solution. >> >> Best Regards, >> Rustem >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 227297 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 190064 bytes Desc: not available URL: From cellinger at lanl.gov Thu Mar 16 12:21:39 2017 From: cellinger at lanl.gov (Ellinger, Carola) Date: Thu, 16 Mar 2017 16:21:39 +0000 Subject: [Paraview] Help on SPHVolumeInterpolator In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F68437EC998@MBX111.d.ethz.ch> Message-ID: Hi Jean, and Will, Thanks for the help! I think I might just wait until that patch is released. It sounds like that is not too far into the future, so that's the easiest way for me to go. :) Cheers, Carola From: Will Schroeder > Date: Thursday, March 16, 2017 at 05:37 To: Favre Jean > Cc: Carola Ellinger >, "paraview at paraview.org" > Subject: Re: [Paraview] Help on SPHVolumeInterpolator Carola- What Jean said :-) The patch is waiting on me and I am waiting on deadlines which will be clearing up shortly. If you haven't seen these yet, it's worth reviewing these articles: https://blog.kitware.com/point-and-smoothed-particle-hydrodynamics-sph-interpolation-in-vtk/ https://blog.kitware.com/point-and-smoothed-particle-hydrodynamics-sph-interpolation-in-paraview/ Best, W On Wed, Mar 15, 2017 at 4:21 PM, Favre Jean > wrote: Carola the answer is "soon". ParaView's GUI already enables the setting of the so-called Cuttoff Array. In the GUI (I am assuming you use version 5.3), there should be a setting for the Density and the Mass arrays. And just below it, is the 3rd setting for the "smooting length" array. Unfortunately, we are waiting on a patch to the underlying VTK class vtkSPHInterpolator.cxx which currently has a small error preventing the correct setting. By the way, I strongly suggest that you use a version of ParaView compiled with OpenMP, or TBB. You will see great speed-ups on a multi-core node, since the Point Interpolators (Line, Plane, Volume) are all parallelized on-the-node. Until the patch is merged into VTK, and ParaView picks up the change, you will be limited to setting the Density and Mass arrays. (Unless you compile your own ParaView, and I can tell you how to edit the source code to enable the smoothing array.) ----------------- Jean/CSCS ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Ellinger, Carola [cellinger at lanl.gov] Sent: Wednesday, March 15, 2017 6:47 PM To: paraview at paraview.org Subject: [Paraview] Help on SPHVolumeInterpolator Hello, I have astrophysical SPH (smoothed particle hydrodynamics) data that I want to interpolate for visualization in ParaView. I've found the SPHVolumeInterpolator filter to do that, but can this filter handle non-constant smoothing lengths of SPH particles for the interpolation? If so, how is this set? Due to the nature of the object I'm trying to visualize (a star), the smoothing lengths varies over a few orders of magnitude. Thank you for any help, Carola _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- William J. Schroeder, PhD Kitware, Inc. - Building the World's Technical Computing Software 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at snumerics.com Thu Mar 16 14:59:29 2017 From: chrisneal at snumerics.com (Christopher Neal) Date: Thu, 16 Mar 2017 14:59:29 -0400 Subject: [Paraview] Labeling axes for non-spatial data Message-ID: Hi all, I want to write out a data set that doesn't have any spatial variables (in the physical sense of X,Y,Z. My three axes are independent variables that we can call Z, S, C. They have no relation to any physical coordinates whatsoever. Is there a way to encode the information that the axes should be labeled as Z,S,C in the dataset? That way users who load the file would know immediately what they are looking at instead of trying to work backwards to figure out which variable maps to X,Y,Z. The dataset is a simple set of regularly spaced points, and I was considering the STRUCTURED_GRID format. Thank you, -- Christopher Neal Research Engineer Streamline Numerics, Inc. https://www.snumerics.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Thu Mar 16 19:50:05 2017 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 16 Mar 2017 16:50:05 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. Message-ID: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> I tried out ParaView 5.3.0 today, and I encountered the above crash. steps to reproduce: load data (sphere source will work), set color by var, open color map dialog, change to categorical, open choose presets dialog, scroll down, when you get near the bottom you will get the crash. Program received signal SIGFPE, Arithmetic exception. 0x00007ffff660a833 in pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, stc=0x647f460, size=...) at /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 273 Nh = wmp / (ss + PQ_SWATCH_PAD); (gdb) p ss $5 = -2 of course PQ_SWATCH_PAD == 2 From bloring at lbl.gov Thu Mar 16 20:10:15 2017 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 16 Mar 2017 17:10:15 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> Message-ID: <4e707b77-1974-90b6-0467-2f756eaaffe0@lbl.gov> not sure if it matters, but I had been trying to load a color map that was saved from ParaView 5.1.0. attached. On 03/16/2017 04:50 PM, Burlen Loring wrote: > I tried out ParaView 5.3.0 today, and I encountered the above crash. > > steps to reproduce: load data (sphere source will work), set color by > var, open color map dialog, change to categorical, open choose presets > dialog, scroll down, when you get near the bottom you will get the crash. > > Program received signal SIGFPE, Arithmetic exception. > 0x00007ffff660a833 in > pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, > stc=0x647f460, size=...) at > /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 > 273 Nh = wmp / (ss + PQ_SWATCH_PAD); > (gdb) p ss > $5 = -2 > > of course PQ_SWATCH_PAD == 2 -------------- next part -------------- A non-text attachment was scrubbed... Name: red_cmap.json Type: application/json Size: 780 bytes Desc: not available URL: From dennis.dunn at ecp.fr Thu Mar 16 20:37:25 2017 From: dennis.dunn at ecp.fr (Dennis Dunn) Date: Fri, 17 Mar 2017 01:37:25 +0100 Subject: [Paraview] Spatial Collection Boundary Interpolation Message-ID: <33c1ae9d-b66c-ff40-5681-b5694cd23bfa@ecp.fr> Hello, I have a question about loading spatial collections with XDMF. I have a collection of scalar fields (each saved as h5 files) and need to display them together as a single field. For example, a 2D global structured uniform grid is 64x64 cells, split into four 32x32 grids. The scalar data is simple cell-centered values, but I can't use the Attribute Center="Cell" mode because that seems to require more details like face/edge values and possibly the vertices. The Center="Node" method is simple and works since it requires only 1 scalar value per cell. Below is the first portion of the xmf file I used to generate the attached image: See the attached image for the result. The *.h5 supplied data points lie at the intersections of the visible grid lines. All the data is present, but ParaView 5.3.0 isn't interpolating between the different fields in the spatial collection, leaving very apparent gaps of width "?x". How can I resolve this? I have also tried the JOIN function, but it's quite tricky for merging 2D/3D spatial collections. Any help you could provide would be greatly appreciated. If there is no easy solution, I'll probably try parallel HDF5 to avoid the whole issue of xdmf spatial collections entirely. Best regards, -Dennis -------------- next part -------------- A non-text attachment was scrubbed... Name: Node Centers.png Type: image/png Size: 281261 bytes Desc: not available URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Mar 17 03:15:00 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 17 Mar 2017 09:15:00 +0200 (EET) Subject: [Paraview] installation of PV 5.3.0 with Intel compiler ... Message-ID: <48892.78.182.90.145.1489734900.squirrel@webmail.be.itu.edu.tr> Hi All, Again, i am stuck into following error, CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known features for CXX compiler "Intel" version 17.0.2.20170213. Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) In this case, i am trying to install 5.3.0 with Intel compiler. Earlier (with 5.3.0RC2), i fix the issue by upgrading cmake to 3.7.2 but now it is not working. I also tried to use cmake-3.8.0-rc2 but still same error. I found a similar issue in the following thread but i could not solve the problem, http://public.kitware.com/pipermail/paraview-developers/2016-July/004490.html Thanks, Regards, --ufuk From u.utku.turuncoglu at be.itu.edu.tr Fri Mar 17 03:18:21 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 17 Mar 2017 09:18:21 +0200 (EET) Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> Message-ID: <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> Hi Burlen, Your issue could be related with following, https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 I opened a bug report in Intel form and they found a bug in that particular source file (pqPresetToPixmap.cxx). So, if you apply the fix you might solve the problem but i am not sure. I hope it helps, Regards, --ufuk > I tried out ParaView 5.3.0 today, and I encountered the above crash. > > steps to reproduce: load data (sphere source will work), set color by > var, open color map dialog, change to categorical, open choose presets > dialog, scroll down, when you get near the bottom you will get the crash. > > Program received signal SIGFPE, Arithmetic exception. > 0x00007ffff660a833 in > pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, > stc=0x647f460, size=...) at > /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 > 273 Nh = wmp / (ss + PQ_SWATCH_PAD); > (gdb) p ss > $5 = -2 > > of course PQ_SWATCH_PAD == 2 > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From u.utku.turuncoglu at be.itu.edu.tr Fri Mar 17 09:37:33 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 17 Mar 2017 15:37:33 +0200 (EET) Subject: [Paraview] installation of PV 5.3.0 with Intel compiler ... In-Reply-To: <48892.78.182.90.145.1489734900.squirrel@webmail.be.itu.edu.tr> References: <48892.78.182.90.145.1489734900.squirrel@webmail.be.itu.edu.tr> Message-ID: <38038.78.182.90.145.1489757853.squirrel@webmail.be.itu.edu.tr> This is my fault. Sorry! After upgrading to cmake-3.8.0-rc2, it installs without any problem. --ufuk > Hi All, > > Again, i am stuck into following error, > > CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 > (target_compile_features): > target_compile_features no known features for CXX compiler > > "Intel" > > version 17.0.2.20170213. > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) > VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) > > In this case, i am trying to install 5.3.0 with Intel compiler. Earlier > (with 5.3.0RC2), i fix the issue by upgrading cmake to 3.7.2 but now it is > not working. I also tried to use cmake-3.8.0-rc2 but still same error. I > found a similar issue in the following thread but i could not solve the > problem, > > http://public.kitware.com/pipermail/paraview-developers/2016-July/004490.html > > Thanks, > Regards, > > --ufuk > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Fri Mar 17 10:09:48 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 17 Mar 2017 10:09:48 -0400 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> Message-ID: Burlen, I've created an issue for your report. It sure looks like a bug. https://gitlab.kitware.com/paraview/paraview/issues/17305 Ufuk, That fix turns out to already be in v5.3.0: commit 90e710d5792116e640d25caa8ff455ae4e65d718 Author: Sergey Sindeev Date: Sun Dec 18 13:21:27 2016 +0100 fix a compilation crash when using the latest ICC compiler diff --git a/Qt/Components/pqPresetToPixmap.cxx b/Qt/Components/pqPresetToPixmap.cxx index 13f6b2e..b80fb80 100644 --- a/Qt/Components/pqPresetToPixmap.cxx +++ b/Qt/Components/pqPresetToPixmap.cxx @@ -254,15 +254,12 @@ QPixmap pqPresetToPixmap::renderIndexedColorTransferFunction( // Now determine best value for Nh in [Nh/2,Nh-1] double bestQ = vtkMath::Inf(); int best = -1; - for (int i = Nh / 2; i < Nh; ++i) + double ar = Nv * wmp / static_cast(hmp * Nh); + double q = (ar >= 1.0) ? ar : 1. / ar; + if (q < bestQ) { - double ar = Nv * wmp / static_cast(hmp * Nh); - double q = (ar >= 1.0) ? ar : 1. / ar; - if (q < bestQ) - { - bestQ = q; - best = i; - } + bestQ = q; + best = Nh-1; } Nh = best; } Thanks to you and Sergey for pursuing this Intel compiler issue and ParaView issue! - Cory On Fri, Mar 17, 2017 at 3:18 AM, wrote: > Hi Burlen, > > Your issue could be related with following, > > https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 > > I opened a bug report in Intel form and they found a bug in that > particular source file (pqPresetToPixmap.cxx). So, if you apply the fix > you might solve the problem but i am not sure. > > I hope it helps, > Regards, > > --ufuk > > >> I tried out ParaView 5.3.0 today, and I encountered the above crash. >> >> steps to reproduce: load data (sphere source will work), set color by >> var, open color map dialog, change to categorical, open choose presets >> dialog, scroll down, when you get near the bottom you will get the crash. >> >> Program received signal SIGFPE, Arithmetic exception. >> 0x00007ffff660a833 in >> pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, >> stc=0x647f460, size=...) at >> /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 >> 273 Nh = wmp / (ss + PQ_SWATCH_PAD); >> (gdb) p ss >> $5 = -2 >> >> of course PQ_SWATCH_PAD == 2 >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. From rustem.khabetdinov at gmail.com Fri Mar 17 11:30:41 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Fri, 17 Mar 2017 18:30:41 +0300 Subject: [Paraview] Cmake flags Message-ID: Hello, Is there any detailed description for cmake flags? The most interesting are: VTK_Group_Imaging VTK_Group_MPI VTK_Group_Rendering Module_vtkImagingOpenGL2 On VTK_Group_Views VTK_Group_ParaViewQt VTK_Group_ParaViewRendering VTK_Group_Qt VTK_NO_PYTHON_THREADS Best Regards, Rustem -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Fri Mar 17 13:22:00 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Fri, 17 Mar 2017 20:22:00 +0300 Subject: [Paraview] Labels in Custom Filters Message-ID: Hello, In custom filters we can set some field labels and names. Why when we set labels they become accessors instead of field names? Is it a bug or there is some meaning behind this? It may be a problem when non-English users create filters and set some labels using their native language. Of course they can use SetPropertyWithName('name',value) but I do not think that it is what they need. Best Regards, Rustem -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Fri Mar 17 15:11:25 2017 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 17 Mar 2017 12:11:25 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> Message-ID: <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> Thank you guys. I poked around this morning and found the following: The "BlueObeliskElements" is the only cmap in the default presets that triggers the issue. It has more values than can be displayed on a single line, and this is what triggers the FPE in the logic. Enforcing a minimum swatch size(terminology from the code) prevents the FPE and seems to produce the desired result of displaying all of the cmap values in one line, although they are quite small. a moment ago I pushed a patch onto gitlab demonstrating. Perhaps it or something like it could be back ported to the 5.3.0 branch? On 03/17/2017 07:09 AM, Cory Quammen wrote: > Burlen, > > I've created an issue for your report. It sure looks like a bug. > > https://gitlab.kitware.com/paraview/paraview/issues/17305 > > Ufuk, > > That fix turns out to already be in v5.3.0: > > commit 90e710d5792116e640d25caa8ff455ae4e65d718 > Author: Sergey Sindeev > Date: Sun Dec 18 13:21:27 2016 +0100 > > fix a compilation crash when using the latest ICC compiler > > diff --git a/Qt/Components/pqPresetToPixmap.cxx > b/Qt/Components/pqPresetToPixmap.cxx > index 13f6b2e..b80fb80 100644 > --- a/Qt/Components/pqPresetToPixmap.cxx > +++ b/Qt/Components/pqPresetToPixmap.cxx > @@ -254,15 +254,12 @@ QPixmap > pqPresetToPixmap::renderIndexedColorTransferFunction( > // Now determine best value for Nh in [Nh/2,Nh-1] > double bestQ = vtkMath::Inf(); > int best = -1; > - for (int i = Nh / 2; i < Nh; ++i) > + double ar = Nv * wmp / static_cast(hmp * Nh); > + double q = (ar >= 1.0) ? ar : 1. / ar; > + if (q < bestQ) > { > - double ar = Nv * wmp / static_cast(hmp * Nh); > - double q = (ar >= 1.0) ? ar : 1. / ar; > - if (q < bestQ) > - { > - bestQ = q; > - best = i; > - } > + bestQ = q; > + best = Nh-1; > } > Nh = best; > } > > Thanks to you and Sergey for pursuing this Intel compiler issue and > ParaView issue! > > - Cory > > On Fri, Mar 17, 2017 at 3:18 AM, wrote: >> Hi Burlen, >> >> Your issue could be related with following, >> >> https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 >> >> I opened a bug report in Intel form and they found a bug in that >> particular source file (pqPresetToPixmap.cxx). So, if you apply the fix >> you might solve the problem but i am not sure. >> >> I hope it helps, >> Regards, >> >> --ufuk >> >> >>> I tried out ParaView 5.3.0 today, and I encountered the above crash. >>> >>> steps to reproduce: load data (sphere source will work), set color by >>> var, open color map dialog, change to categorical, open choose presets >>> dialog, scroll down, when you get near the bottom you will get the crash. >>> >>> Program received signal SIGFPE, Arithmetic exception. >>> 0x00007ffff660a833 in >>> pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, >>> stc=0x647f460, size=...) at >>> /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 >>> 273 Nh = wmp / (ss + PQ_SWATCH_PAD); >>> (gdb) p ss >>> $5 = -2 >>> >>> of course PQ_SWATCH_PAD == 2 >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > From chuck.atkins at kitware.com Fri Mar 17 15:33:24 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Fri, 17 Mar 2017 15:33:24 -0400 Subject: [Paraview] installation of PV 5.3.0 with Intel compiler ... In-Reply-To: <38038.78.182.90.145.1489757853.squirrel@webmail.be.itu.edu.tr> References: <48892.78.182.90.145.1489734900.squirrel@webmail.be.itu.edu.tr> <38038.78.182.90.145.1489757853.squirrel@webmail.be.itu.edu.tr> Message-ID: ParaView now requires C++11 support and uses some newer CMake features to detect this properly. While this worked for gcc and clang for some time with CMake, the Intel compiler did not have language feature support with CMake until at least 3.6. ---------- - Chuck On Fri, Mar 17, 2017 at 9:37 AM, wrote: > This is my fault. Sorry! After upgrading to cmake-3.8.0-rc2, it installs > without any problem. > > --ufuk > > > Hi All, > > > > Again, i am stuck into following error, > > > > CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 > > (target_compile_features): > > target_compile_features no known features for CXX compiler > > > > "Intel" > > > > version 17.0.2.20170213. > > Call Stack (most recent call first): > > VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) > > VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) > > > > In this case, i am trying to install 5.3.0 with Intel compiler. Earlier > > (with 5.3.0RC2), i fix the issue by upgrading cmake to 3.7.2 but now it > is > > not working. I also tried to use cmake-3.8.0-rc2 but still same error. I > > found a similar issue in the following thread but i could not solve the > > problem, > > > > http://public.kitware.com/pipermail/paraview-developers/ > 2016-July/004490.html > > > > Thanks, > > Regards, > > > > --ufuk > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Fri Mar 17 15:36:10 2017 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 17 Mar 2017 12:36:10 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> Message-ID: fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476 it complains about clang-format, but it seems that the source file was not formatted in that way to begin with. On 03/17/2017 12:11 PM, Burlen Loring wrote: > Thank you guys. I poked around this morning and found the following: > > The "BlueObeliskElements" is the only cmap in the default presets that > triggers the issue. It has more values than can be displayed on a > single line, and this is what triggers the FPE in the logic. > > Enforcing a minimum swatch size(terminology from the code) prevents > the FPE and seems to produce the desired result of displaying all of > the cmap values in one line, although they are quite small. > > a moment ago I pushed a patch onto gitlab demonstrating. Perhaps it or > something like it could be back ported to the 5.3.0 branch? > > On 03/17/2017 07:09 AM, Cory Quammen wrote: >> Burlen, >> >> I've created an issue for your report. It sure looks like a bug. >> >> https://gitlab.kitware.com/paraview/paraview/issues/17305 >> >> Ufuk, >> >> That fix turns out to already be in v5.3.0: >> >> commit 90e710d5792116e640d25caa8ff455ae4e65d718 >> Author: Sergey Sindeev >> Date: Sun Dec 18 13:21:27 2016 +0100 >> >> fix a compilation crash when using the latest ICC compiler >> >> diff --git a/Qt/Components/pqPresetToPixmap.cxx >> b/Qt/Components/pqPresetToPixmap.cxx >> index 13f6b2e..b80fb80 100644 >> --- a/Qt/Components/pqPresetToPixmap.cxx >> +++ b/Qt/Components/pqPresetToPixmap.cxx >> @@ -254,15 +254,12 @@ QPixmap >> pqPresetToPixmap::renderIndexedColorTransferFunction( >> // Now determine best value for Nh in [Nh/2,Nh-1] >> double bestQ = vtkMath::Inf(); >> int best = -1; >> - for (int i = Nh / 2; i < Nh; ++i) >> + double ar = Nv * wmp / static_cast(hmp * Nh); >> + double q = (ar >= 1.0) ? ar : 1. / ar; >> + if (q < bestQ) >> { >> - double ar = Nv * wmp / static_cast(hmp * Nh); >> - double q = (ar >= 1.0) ? ar : 1. / ar; >> - if (q < bestQ) >> - { >> - bestQ = q; >> - best = i; >> - } >> + bestQ = q; >> + best = Nh-1; >> } >> Nh = best; >> } >> >> Thanks to you and Sergey for pursuing this Intel compiler issue and >> ParaView issue! >> >> - Cory >> >> On Fri, Mar 17, 2017 at 3:18 AM, >> wrote: >>> Hi Burlen, >>> >>> Your issue could be related with following, >>> >>> https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 >>> >>> I opened a bug report in Intel form and they found a bug in that >>> particular source file (pqPresetToPixmap.cxx). So, if you apply the fix >>> you might solve the problem but i am not sure. >>> >>> I hope it helps, >>> Regards, >>> >>> --ufuk >>> >>> >>>> I tried out ParaView 5.3.0 today, and I encountered the above crash. >>>> >>>> steps to reproduce: load data (sphere source will work), set color by >>>> var, open color map dialog, change to categorical, open choose presets >>>> dialog, scroll down, when you get near the bottom you will get the >>>> crash. >>>> >>>> Program received signal SIGFPE, Arithmetic exception. >>>> 0x00007ffff660a833 in >>>> pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, >>>> stc=0x647f460, size=...) at >>>> /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 >>>> 273 Nh = wmp / (ss + PQ_SWATCH_PAD); >>>> (gdb) p ss >>>> $5 = -2 >>>> >>>> of course PQ_SWATCH_PAD == 2 >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> > From cory.quammen at kitware.com Fri Mar 17 15:50:37 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 17 Mar 2017 15:50:37 -0400 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> Message-ID: Burlen, Thanks for the patch. With regards to clang-format, we recently enabled automatic style enforcement checks. This way to fix is to install clang-format, run `git clang-format` in your ParaView source directory, amend your commit, then force push it with `git gitlab-push -f`. - Cory On Fri, Mar 17, 2017 at 3:36 PM, Burlen Loring wrote: > fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476 > > it complains about clang-format, but it seems that the source file was not > formatted in that way to begin with. > > > On 03/17/2017 12:11 PM, Burlen Loring wrote: >> >> Thank you guys. I poked around this morning and found the following: >> >> The "BlueObeliskElements" is the only cmap in the default presets that >> triggers the issue. It has more values than can be displayed on a single >> line, and this is what triggers the FPE in the logic. >> >> Enforcing a minimum swatch size(terminology from the code) prevents the >> FPE and seems to produce the desired result of displaying all of the cmap >> values in one line, although they are quite small. >> >> a moment ago I pushed a patch onto gitlab demonstrating. Perhaps it or >> something like it could be back ported to the 5.3.0 branch? >> >> On 03/17/2017 07:09 AM, Cory Quammen wrote: >>> >>> Burlen, >>> >>> I've created an issue for your report. It sure looks like a bug. >>> >>> https://gitlab.kitware.com/paraview/paraview/issues/17305 >>> >>> Ufuk, >>> >>> That fix turns out to already be in v5.3.0: >>> >>> commit 90e710d5792116e640d25caa8ff455ae4e65d718 >>> Author: Sergey Sindeev >>> Date: Sun Dec 18 13:21:27 2016 +0100 >>> >>> fix a compilation crash when using the latest ICC compiler >>> >>> diff --git a/Qt/Components/pqPresetToPixmap.cxx >>> b/Qt/Components/pqPresetToPixmap.cxx >>> index 13f6b2e..b80fb80 100644 >>> --- a/Qt/Components/pqPresetToPixmap.cxx >>> +++ b/Qt/Components/pqPresetToPixmap.cxx >>> @@ -254,15 +254,12 @@ QPixmap >>> pqPresetToPixmap::renderIndexedColorTransferFunction( >>> // Now determine best value for Nh in [Nh/2,Nh-1] >>> double bestQ = vtkMath::Inf(); >>> int best = -1; >>> - for (int i = Nh / 2; i < Nh; ++i) >>> + double ar = Nv * wmp / static_cast(hmp * Nh); >>> + double q = (ar >= 1.0) ? ar : 1. / ar; >>> + if (q < bestQ) >>> { >>> - double ar = Nv * wmp / static_cast(hmp * Nh); >>> - double q = (ar >= 1.0) ? ar : 1. / ar; >>> - if (q < bestQ) >>> - { >>> - bestQ = q; >>> - best = i; >>> - } >>> + bestQ = q; >>> + best = Nh-1; >>> } >>> Nh = best; >>> } >>> >>> Thanks to you and Sergey for pursuing this Intel compiler issue and >>> ParaView issue! >>> >>> - Cory >>> >>> On Fri, Mar 17, 2017 at 3:18 AM, wrote: >>>> >>>> Hi Burlen, >>>> >>>> Your issue could be related with following, >>>> >>>> https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 >>>> >>>> I opened a bug report in Intel form and they found a bug in that >>>> particular source file (pqPresetToPixmap.cxx). So, if you apply the fix >>>> you might solve the problem but i am not sure. >>>> >>>> I hope it helps, >>>> Regards, >>>> >>>> --ufuk >>>> >>>> >>>>> I tried out ParaView 5.3.0 today, and I encountered the above crash. >>>>> >>>>> steps to reproduce: load data (sphere source will work), set color by >>>>> var, open color map dialog, change to categorical, open choose presets >>>>> dialog, scroll down, when you get near the bottom you will get the >>>>> crash. >>>>> >>>>> Program received signal SIGFPE, Arithmetic exception. >>>>> 0x00007ffff660a833 in >>>>> pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, >>>>> stc=0x647f460, size=...) at >>>>> /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 >>>>> 273 Nh = wmp / (ss + PQ_SWATCH_PAD); >>>>> (gdb) p ss >>>>> $5 = -2 >>>>> >>>>> of course PQ_SWATCH_PAD == 2 >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >> > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From yzhzhang at ipe.ac.cn Sat Mar 18 03:51:16 2017 From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=) Date: Sat, 18 Mar 2017 15:51:16 +0800 (GMT+08:00) Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? Message-ID: Hello, I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 GPUs. The K80 GPUs have no interface for monitor, so I have to use off screen rendering. It's said that EGL is a pretty good choice for this situation, but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to "ON" and then make, I get these errors: Built target vtkIOImage [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/CMakeFiles/vtkglew.dir/src/glew.c.o In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No such file or directory In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLint? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLContext? /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? ...... Maybe it is clear that there is something wrong with the EGL header file, but I don't know how to fix it. The operation system is CentOS 6.6. There is an integrated graphics and 6 K80 GPUs. I connect to the machine using ssh and have set headless X server using one of the K80 GPUs. I can run the glxgears test in the off screen mode, but I don'n know how to make sure that EGL is correctly setted. I want to know how to use EGL for off screen rendering. Any help would be highly appreciated! -Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From asmprog32 at hotmail.com Sun Mar 19 18:11:09 2017 From: asmprog32 at hotmail.com (Pietro Incardona) Date: Sun, 19 Mar 2017 22:11:09 +0000 Subject: [Paraview] Paraview save video on high resolution Message-ID: Hi All I tried to save a video in Paraview with "save animation" in ogv. The tool work perfectly wit the exception when I choose a resolution higher than the screen resolution. In this case the video can be played but the video image is completely corrupted. I tried with the latest Paraview 5.3 binary on Linux and OSX with the same results. Did someone else had the same problem ? Regards Pietro -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Mar 20 09:46:31 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 20 Mar 2017 09:46:31 -0400 Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? In-Reply-To: References: Message-ID: It seems you are missing KHR/khrplatform.h You can download it from the EGL website: https://www.khronos.org/registry/EGL/ On Sat, Mar 18, 2017 at 3:51 AM, ??? wrote: > > > Hello, > > I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 GPUs. > The K80 GPUs have no interface for monitor, so I have to use off screen > rendering. It's said that EGL is a pretty good choice for this situation, > but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to "ON" and > then make, I get these errors: > > Built target vtkIOImage > [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/ > CMakeFiles/vtkglew.dir/src/glew.c.o > In file included from /pan20/yzzhang/EGL/egl.h:39, > from /pan20/yzzhang/ParaView-v5.2. > 0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: > /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No such > file or directory > In file included from /pan20/yzzhang/EGL/egl.h:39, > from /pan20/yzzhang/ParaView-v5.2. > 0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: > /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, > ?asm? or ?__attribute__? before ?EGLint? > In file included from /pan20/yzzhang/ParaView-v5.2. > 0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: > /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or > ?__attribute__? before ?EGLBoolean? > In file included from /pan20/yzzhang/ParaView-v5.2. > 0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: > /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or > ?__attribute__? before ?EGLBoolean? > /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or > ?__attribute__? before ?EGLContext? > /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or > ?__attribute__? before ?EGLSurface? > /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or > ?__attribute__? before ?EGLSurface? > ...... > > Maybe it is clear that there is something wrong with the EGL header file, > but I don't know how to fix it. The operation system is CentOS 6.6. There > is an integrated graphics and 6 K80 GPUs. I connect to the machine using > ssh and have set headless X server using one of the K80 GPUs. I can run the > glxgears test in the off screen mode, but I don'n know how to make sure > that EGL is correctly setted. I want to know how to use EGL for off screen > rendering. > > Any help would be highly appreciated! > > -Zhang > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Mar 20 10:21:44 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 20 Mar 2017 10:21:44 -0400 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> Message-ID: <20170320142144.GA6579@megas.kitware.com> On Fri, Mar 17, 2017 at 12:36:10 -0700, Burlen Loring wrote: > fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476 > > it complains about clang-format, but it seems that the source file was > not formatted in that way to begin with. When I enabled clang-format checking, I did a sweep of the repo with clang-format. I think the problem is that your headers aren't sorted: #include #include --Ben From yzhzhang at ipe.ac.cn Mon Mar 20 10:22:47 2017 From: yzhzhang at ipe.ac.cn (=?UTF-8?B?5byg6amt5rSy?=) Date: Mon, 20 Mar 2017 22:22:47 +0800 (GMT+08:00) Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? In-Reply-To: References: Message-ID: Thanks for your reply! But I don't know where the KHR/khrplatform.h is used. When I configure paraview using ccmake, the options about EGL are EGL_INCLUDE_DIR, EGL_LIBRARY, EGL_gldispatch_LIBRARY, EGL_opengl_LIBRARY, VTK_EGL_DEVICE_INDEX and VTK_USE_OFFSCREEN_EGL. In the path that I assigned to the EGL_INCLUDE_DIR, there is khrplatform.h file. What's more, I have built ParaView 5.2.0 with EGL used on another machine. That machine use NVIDIA GT 730 GPU, and in the EGL_INCLUDE_DIR path, there is not a khrplatform.h file, but the paraview can be built successfully and works. The khrplatform.h is required by the current EGL (1.5), but my EGL version is 1.4. Maybe it doesn't need that file? Thank you again! -Zhang -----????----- ???: "Dan Lipsa" ????: 2017?3?20? ??? ???: "???" ??: paraview ??: Re: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? It seems you are missing KHR/khrplatform.h You can download it from the EGL website: https://www.khronos.org/registry/EGL/ On Sat, Mar 18, 2017 at 3:51 AM, ??? wrote: Hello, I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 GPUs. The K80 GPUs have no interface for monitor, so I have to use off screen rendering. It's said that EGL is a pretty good choice for this situation, but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to "ON" and then make, I get these errors: Built target vtkIOImage [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/CMakeFiles/vtkglew.dir/src/glew.c.o In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No such file or directory In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLint? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLContext? /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? ...... Maybe it is clear that there is something wrong with the EGL header file, but I don't know how to fix it. The operation system is CentOS 6.6. There is an integrated graphics and 6 K80 GPUs. I connect to the machine using ssh and have set headless X server using one of the K80 GPUs. I can run the glxgears test in the off screen mode, but I don'n know how to make sure that EGL is correctly setted. I want to know how to use EGL for off screen rendering. Any help would be highly appreciated! -Zhang _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Mar 20 10:28:43 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 20 Mar 2017 10:28:43 -0400 Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? In-Reply-To: References: Message-ID: Looking at the errors you are getting looks like /pan20/yzzhang/EGL/eglplatform.h needs KHR/khrplatform.h Maybe your configuration uses different EGL header files than what you expect. DAn On Mon, Mar 20, 2017 at 10:22 AM, ??? wrote: > > > Thanks for your reply! But I don't know where the KHR/khrplatform.h is > used. When I configure paraview using ccmake, the options about EGL are > EGL_INCLUDE_DIR, > EGL_LIBRARY, EGL_gldispatch_LIBRARY, EGL_opengl_LIBRARY, > VTK_EGL_DEVICE_INDEX and VTK_USE_OFFSCREEN_EGL. In the path that I assigned > to the EGL_INCLUDE_DIR, there is khrplatform.h file. What's more, I have > built ParaView 5.2.0 with EGL used on another machine. That machine use > NVIDIA GT 730 GPU, and in the EGL_INCLUDE_DIR path, there is not a > khrplatform.h file, but the paraview can be built successfully and works. > The khrplatform.h is required by the current EGL (1.5), but my EGL version > is 1.4. Maybe it doesn't need that file? > > Thank you again! > > -Zhang > > -----????----- > *???:* "Dan Lipsa" > *????:* 2017?3?20? ??? > *???:* "???" > *??:* paraview > *??:* Re: [Paraview] How to configure ParaView 5.2.0 to use off screen > rendering? > > > It seems you are missing KHR/khrplatform.h > You can download it from the EGL website: > https://www.khronos.org/registry/EGL/ > > On Sat, Mar 18, 2017 at 3:51 AM, ??? wrote: > >> >> >> Hello, >> >> I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 GPUs. >> The K80 GPUs have no interface for monitor, so I have to use off screen >> rendering. It's said that EGL is a pretty good choice for this situation, >> but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to "ON" and >> then make, I get these errors: >> >> Built target vtkIOImage >> [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/CM >> akeFiles/vtkglew.dir/src/glew.c.o >> In file included from /pan20/yzzhang/EGL/egl.h:39, >> from /pan20/yzzhang/ParaView-v5.2.0 >> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >> /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No >> such file or directory >> In file included from /pan20/yzzhang/EGL/egl.h:39, >> from /pan20/yzzhang/ParaView-v5.2.0 >> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >> /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, >> ?asm? or ?__attribute__? before ?EGLint? >> In file included from /pan20/yzzhang/ParaView-v5.2.0 >> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >> /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or >> ?__attribute__? before ?EGLBoolean? >> In file included from /pan20/yzzhang/ParaView-v5.2.0 >> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >> /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or >> ?__attribute__? before ?EGLBoolean? >> /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or >> ?__attribute__? before ?EGLContext? >> /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or >> ?__attribute__? before ?EGLSurface? >> /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or >> ?__attribute__? before ?EGLSurface? >> ...... >> >> Maybe it is clear that there is something wrong with the EGL header file, >> but I don't know how to fix it. The operation system is CentOS 6.6. There >> is an integrated graphics and 6 K80 GPUs. I connect to the machine using >> ssh and have set headless X server using one of the K80 GPUs. I can run the >> glxgears test in the off screen mode, but I don'n know how to make sure >> that EGL is correctly setted. I want to know how to use EGL for off screen >> rendering. >> >> Any help would be highly appreciated! >> >> -Zhang >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgreen at lanl.gov Mon Mar 20 12:21:39 2017 From: jgreen at lanl.gov (Green, Jennifer Kathleen) Date: Mon, 20 Mar 2017 16:21:39 +0000 Subject: [Paraview] Potential bug (feature request) Export Scene PV/5.3.0 Message-ID: <1490026899387.72285@lanl.gov> We have a customer inquiring about whether there's a capability to export scene save min as well as max, indicates that the max is only exportable. Can you please advise whether this is available in 5.3.0 or if it's on the roadmap for future releases? Thanks! This is an actual PV bug as reported by Alan Scott: Export Scene for 2d plots misses columns I believe we are missing columns of information when Export Scene is run for 2d plots. Here is how to replicate: * 5.3.0, Linux, local server. * can.exo, all vars on, apply. * Select Points On. Select maybe 10 points somewhere on the can. * Plot Selection. Apply. Turn on only ACCL Magnitude. * Export Scene. Now, open the file. You will find columns for time, average, median, min/max (I believe it is max), and q1/q3 (I believe it is the third quartile. What I want is time, average, median, min, max, q1 and then q3. Thanks! Jennifer Green Jennifer Green, Team Leader Programming & Runtime Environments Team High Performance Computing Environments Los Alamos National Laboratory PO Box 1663 MS T080 Los Alamos NM 87545 office: 505-665-8421 cell: 505-695-6437 pager: 505-664-1504 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Mar 20 12:43:58 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 20 Mar 2017 16:43:58 +0000 Subject: [Paraview] [EXTERNAL] Potential bug (feature request) Export Scene PV/5.3.0 In-Reply-To: <1490026899387.72285@lanl.gov> References: <1490026899387.72285@lanl.gov> Message-ID: Jennifer, The bug you list was written for and found on PV 5.3. It is scheduled to be fixed by next fall, PV 5.5, for Supercomputing. The user can output the data in question by using Save Data. This will save all of the data from the plot selections filter, giving many more columns than the user wanted. But, that is his/her fallback for now. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Green, Jennifer Kathleen Sent: Monday, March 20, 2017 10:22 AM To: ParaView Subject: [EXTERNAL] [Paraview] Potential bug (feature request) Export Scene PV/5.3.0 We have a customer inquiring about whether there's a capability to export scene save min as well as max, indicates that the max is only exportable. Can you please advise whether this is available in 5.3.0 or if it's on the roadmap for future releases? Thanks! This is an actual PV bug as reported by Alan Scott: Export Scene for 2d plots misses columns I believe we are missing columns of information when Export Scene is run for 2d plots. Here is how to replicate: * 5.3.0, Linux, local server. * can.exo, all vars on, apply. * Select Points On. Select maybe 10 points somewhere on the can. * Plot Selection. Apply. Turn on only ACCL Magnitude. * Export Scene. Now, open the file. You will find columns for time, average, median, min/max (I believe it is max), and q1/q3 (I believe it is the third quartile. What I want is time, average, median, min, max, q1 and then q3. Thanks! Jennifer Green Jennifer Green, Team Leader Programming & Runtime Environments Team High Performance Computing Environments Los Alamos National Laboratory PO Box 1663 MS T080 Los Alamos NM 87545 > office: 505-665-8421 cell: 505-695-6437 pager: 505-664-1504 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Mar 20 12:45:39 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 20 Mar 2017 12:45:39 -0400 Subject: [Paraview] Potential bug (feature request) Export Scene PV/5.3.0 In-Reply-To: <1490026899387.72285@lanl.gov> References: <1490026899387.72285@lanl.gov> Message-ID: This is indeed a bug. Alan has marked it as "nice-to-have" for SC 2017. On Mon, Mar 20, 2017 at 12:21 PM, Green, Jennifer Kathleen wrote: > We have a customer inquiring about whether there's a capability to export > scene save min as well as max, indicates that the max is only exportable. > Can you please advise whether this is available in 5.3.0 or if it's on the > roadmap for future releases? > > > Thanks! > > > This is an actual PV bug as reported by Alan Scott: > > > Export Scene for 2d plots misses columns > > I believe we are missing columns of information when Export Scene is run for > 2d plots. Here is how to replicate: > > 5.3.0, Linux, local server. > can.exo, all vars on, apply. > Select Points On. Select maybe 10 points somewhere on the can. > Plot Selection. Apply. Turn on only ACCL Magnitude. > Export Scene. > > Now, open the file. You will find columns for time, average, median, min/max > (I believe it is max), and q1/q3 (I believe it is the third quartile. > > What I want is time, average, median, min, max, q1 and then q3. > > > Thanks! > > > Jennifer Green > > > Jennifer Green, Team Leader > Programming & Runtime Environments Team > High Performance Computing Environments > Los Alamos National Laboratory > PO Box 1663 MS T080 > Los Alamos NM 87545 > > office: 505-665-8421 > cell: 505-695-6437 > pager: 505-664-1504 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Mon Mar 20 12:51:44 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 20 Mar 2017 16:51:44 +0000 Subject: [Paraview] [EXTERNAL] Re: Potential bug (feature request) Export Scene PV/5.3.0 In-Reply-To: References: <1490026899387.72285@lanl.gov> Message-ID: Just changed to "important". > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Utkarsh Ayachit > Sent: Monday, March 20, 2017 10:46 AM > To: Green, Jennifer Kathleen (LANL) > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] Potential bug (feature request) Export > Scene PV/5.3.0 > > This is indeed a bug. Alan has marked it as "nice-to-have" for SC 2017. > > > > On Mon, Mar 20, 2017 at 12:21 PM, Green, Jennifer Kathleen > wrote: > > We have a customer inquiring about whether there's a capability to > > export scene save min as well as max, indicates that the max is only > exportable. > > Can you please advise whether this is available in 5.3.0 or if it's on > > the roadmap for future releases? > > > > > > Thanks! > > > > > > This is an actual PV bug as reported by Alan Scott: > > > > > > Export Scene for 2d plots misses columns > > > > I believe we are missing columns of information when Export Scene is > > run for 2d plots. Here is how to replicate: > > > > 5.3.0, Linux, local server. > > can.exo, all vars on, apply. > > Select Points On. Select maybe 10 points somewhere on the can. > > Plot Selection. Apply. Turn on only ACCL Magnitude. > > Export Scene. > > > > Now, open the file. You will find columns for time, average, median, > > min/max (I believe it is max), and q1/q3 (I believe it is the third quartile. > > > > What I want is time, average, median, min, max, q1 and then q3. > > > > > > Thanks! > > > > > > Jennifer Green > > > > > > Jennifer Green, Team Leader > > Programming & Runtime Environments Team High Performance Computing > > Environments Los Alamos National Laboratory PO Box 1663 MS T080 Los > > Alamos NM 87545 > > office: 505-665-8421 > > cell: 505-695-6437 > > pager: 505-664-1504 > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From jgreen at lanl.gov Mon Mar 20 13:16:37 2017 From: jgreen at lanl.gov (Green, Jennifer Kathleen) Date: Mon, 20 Mar 2017 17:16:37 +0000 Subject: [Paraview] [EXTERNAL] Re: Potential bug (feature request) Export Scene PV/5.3.0 In-Reply-To: References: <1490026899387.72285@lanl.gov> , Message-ID: <1490030197550.21185@lanl.gov> Thanks, I'll let our customer know! Jen Jennifer Green, Team Leader Programming & Runtime Environments Team High Performance Computing Environments Los Alamos National Laboratory PO Box 1663 MS T080 Los Alamos NM 87545 office: 505-665-8421 cell: 505-695-6437 pager: 505-664-1504 ________________________________ From: Scott, W Alan Sent: Monday, March 20, 2017 10:51 AM To: Ayachit, Utkarsh (External Contacts); Green, Jennifer Kathleen Cc: ParaView Subject: RE: [EXTERNAL] Re: [Paraview] Potential bug (feature request) Export Scene PV/5.3.0 Just changed to "important". > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Utkarsh Ayachit > Sent: Monday, March 20, 2017 10:46 AM > To: Green, Jennifer Kathleen (LANL) > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] Potential bug (feature request) Export > Scene PV/5.3.0 > > This is indeed a bug. Alan has marked it as "nice-to-have" for SC 2017. > > > > On Mon, Mar 20, 2017 at 12:21 PM, Green, Jennifer Kathleen > wrote: > > We have a customer inquiring about whether there's a capability to > > export scene save min as well as max, indicates that the max is only > exportable. > > Can you please advise whether this is available in 5.3.0 or if it's on > > the roadmap for future releases? > > > > > > Thanks! > > > > > > This is an actual PV bug as reported by Alan Scott: > > > > > > Export Scene for 2d plots misses columns > > > > I believe we are missing columns of information when Export Scene is > > run for 2d plots. Here is how to replicate: > > > > 5.3.0, Linux, local server. > > can.exo, all vars on, apply. > > Select Points On. Select maybe 10 points somewhere on the can. > > Plot Selection. Apply. Turn on only ACCL Magnitude. > > Export Scene. > > > > Now, open the file. You will find columns for time, average, median, > > min/max (I believe it is max), and q1/q3 (I believe it is the third quartile. > > > > What I want is time, average, median, min, max, q1 and then q3. > > > > > > Thanks! > > > > > > Jennifer Green > > > > > > Jennifer Green, Team Leader > > Programming & Runtime Environments Team High Performance Computing > > Environments Los Alamos National Laboratory PO Box 1663 MS T080 Los > > Alamos NM 87545 > > office: 505-665-8421 > > cell: 505-695-6437 > > pager: 505-664-1504 > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From demaio.a at gmail.com Mon Mar 20 14:16:22 2017 From: demaio.a at gmail.com (Alessandro De Maio) Date: Mon, 20 Mar 2017 19:16:22 +0100 Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? In-Reply-To: References: Message-ID: Hi, I've just compiled the Paraview-5.3.0 superbuild with EGL. I created an EGL dir in /usr/include with egl.h, eglext.h and eglplatform.h (taken from www.khronos.org/registry/egl/) and I created a KHR dir in /usr/include with khrplatform.h (taken from the same site). ccmake already recognized the /usr/include/EGL include path for EGL and everything was ok. Alessandro On Mon, Mar 20, 2017 at 3:28 PM, Dan Lipsa wrote: > Looking at the errors you are getting looks like > /pan20/yzzhang/EGL/eglplatform.h > needs KHR/khrplatform.h > > Maybe your configuration uses different EGL header files than what you > expect. > > DAn > > > On Mon, Mar 20, 2017 at 10:22 AM, ??? wrote: > >> >> >> Thanks for your reply! But I don't know where the KHR/khrplatform.h is >> used. When I configure paraview using ccmake, the options about EGL are >> EGL_INCLUDE_DIR, >> EGL_LIBRARY, EGL_gldispatch_LIBRARY, EGL_opengl_LIBRARY, >> VTK_EGL_DEVICE_INDEX and VTK_USE_OFFSCREEN_EGL. In the path that I assigned >> to the EGL_INCLUDE_DIR, there is khrplatform.h file. What's more, I have >> built ParaView 5.2.0 with EGL used on another machine. That machine use >> NVIDIA GT 730 GPU, and in the EGL_INCLUDE_DIR path, there is not a >> khrplatform.h file, but the paraview can be built successfully and works. >> The khrplatform.h is required by the current EGL (1.5), but my EGL version >> is 1.4. Maybe it doesn't need that file? >> >> Thank you again! >> >> -Zhang >> >> -----????----- >> *???:* "Dan Lipsa" >> *????:* 2017?3?20? ??? >> *???:* "???" >> *??:* paraview >> *??:* Re: [Paraview] How to configure ParaView 5.2.0 to use off screen >> rendering? >> >> >> It seems you are missing KHR/khrplatform.h >> You can download it from the EGL website: >> https://www.khronos.org/registry/EGL/ >> >> On Sat, Mar 18, 2017 at 3:51 AM, ??? wrote: >> >>> >>> >>> Hello, >>> >>> I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 >>> GPUs. The K80 GPUs have no interface for monitor, so I have to use off >>> screen rendering. It's said that EGL is a pretty good choice for this >>> situation, but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to >>> "ON" and then make, I get these errors: >>> >>> Built target vtkIOImage >>> [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/CM >>> akeFiles/vtkglew.dir/src/glew.c.o >>> In file included from /pan20/yzzhang/EGL/egl.h:39, >>> from /pan20/yzzhang/ParaView-v5.2.0 >>> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >>> /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No >>> such file or directory >>> In file included from /pan20/yzzhang/EGL/egl.h:39, >>> from /pan20/yzzhang/ParaView-v5.2.0 >>> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >>> /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, >>> ?asm? or ?__attribute__? before ?EGLint? >>> In file included from /pan20/yzzhang/ParaView-v5.2.0 >>> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >>> /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or >>> ?__attribute__? before ?EGLBoolean? >>> In file included from /pan20/yzzhang/ParaView-v5.2.0 >>> /VTK/ThirdParty/glew/vtkglew/src/glew.c:38: >>> /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or >>> ?__attribute__? before ?EGLBoolean? >>> /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or >>> ?__attribute__? before ?EGLContext? >>> /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or >>> ?__attribute__? before ?EGLSurface? >>> /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or >>> ?__attribute__? before ?EGLSurface? >>> ...... >>> >>> Maybe it is clear that there is something wrong with the EGL header >>> file, but I don't know how to fix it. The operation system is CentOS 6.6. >>> There is an integrated graphics and 6 K80 GPUs. I connect to the machine >>> using ssh and have set headless X server using one of the K80 GPUs. I can >>> run the glxgears test in the off screen mode, but I don'n know how to make >>> sure that EGL is correctly setted. I want to know how to use EGL for off >>> screen rendering. >>> >>> Any help would be highly appreciated! >>> >>> -Zhang >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Mon Mar 20 14:31:28 2017 From: burlen.loring at gmail.com (Burlen Loring) Date: Mon, 20 Mar 2017 11:31:28 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> Message-ID: <09cf70c9-06ed-4803-711f-f7f332c211d0@gmail.com> Hi Cory, I had to apply to clang-format manually. it's up there now. changes were minimal so I squashed them into the patch. System has yet to acknowledge and re check. I assume it will eventually. Try as I may the clang-format script you guys are using doesn't work for me. here are the errors: Fedora 24: smic:~/work/ParaView$Utilities/Scripts/clang-format.bash --amend YAML:4:24: error: invalid boolean AlignAfterOpenBracket: DontAlign ^~~~~~~~~ Error reading /home/bloring/work/ParaView/.clang-format: Invalid argument Maybe this is due to clang-format --version == 3.7? not sure but I won't have time to re-install clang on this system, so I also tried on a newer system. OSX Sierra: pipin:~/ParaView/ParaView$./Utilities/Scripts/clang-format.bash --amend sed: 1: "/: format\.clang-format ...": bad flag in substitute command: '}' xargs: illegal option -- d usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements]] [-J replstr] [-L number] [-n number [-x]] [-P maxprocs] [-s size] [utility [argument ...]] clang-format --version==4.0. what ended up working on the OSX system was clang-format -style="{BasedOnStyle: Mozilla, AlignAfterOpenBracket: DontAlign, AlignOperands: false, AlwaysBreakAfterReturnType: None, AlwaysBreakAfterDefinitionReturnType: None, BreakBeforeBraces: Allman, ColumnLimit: 100, Standard: Cpp03}" -i Qt/Components/pqPresetToPixmap.cxx where style arguments were extracted from .clang-format in top level ParaView dir. Burlen On 03/17/2017 12:50 PM, Cory Quammen wrote: > Burlen, > > Thanks for the patch. > > With regards to clang-format, we recently enabled automatic style > enforcement checks. This way to fix is to install clang-format, run > `git clang-format` in your ParaView source directory, amend your > commit, then force push it with `git gitlab-push -f`. > > - Cory > > On Fri, Mar 17, 2017 at 3:36 PM, Burlen Loring wrote: >> fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476 >> >> it complains about clang-format, but it seems that the source file was not >> formatted in that way to begin with. >> >> >> On 03/17/2017 12:11 PM, Burlen Loring wrote: >>> Thank you guys. I poked around this morning and found the following: >>> >>> The "BlueObeliskElements" is the only cmap in the default presets that >>> triggers the issue. It has more values than can be displayed on a single >>> line, and this is what triggers the FPE in the logic. >>> >>> Enforcing a minimum swatch size(terminology from the code) prevents the >>> FPE and seems to produce the desired result of displaying all of the cmap >>> values in one line, although they are quite small. >>> >>> a moment ago I pushed a patch onto gitlab demonstrating. Perhaps it or >>> something like it could be back ported to the 5.3.0 branch? >>> >>> On 03/17/2017 07:09 AM, Cory Quammen wrote: >>>> Burlen, >>>> >>>> I've created an issue for your report. It sure looks like a bug. >>>> >>>> https://gitlab.kitware.com/paraview/paraview/issues/17305 >>>> >>>> Ufuk, >>>> >>>> That fix turns out to already be in v5.3.0: >>>> >>>> commit 90e710d5792116e640d25caa8ff455ae4e65d718 >>>> Author: Sergey Sindeev >>>> Date: Sun Dec 18 13:21:27 2016 +0100 >>>> >>>> fix a compilation crash when using the latest ICC compiler >>>> >>>> diff --git a/Qt/Components/pqPresetToPixmap.cxx >>>> b/Qt/Components/pqPresetToPixmap.cxx >>>> index 13f6b2e..b80fb80 100644 >>>> --- a/Qt/Components/pqPresetToPixmap.cxx >>>> +++ b/Qt/Components/pqPresetToPixmap.cxx >>>> @@ -254,15 +254,12 @@ QPixmap >>>> pqPresetToPixmap::renderIndexedColorTransferFunction( >>>> // Now determine best value for Nh in [Nh/2,Nh-1] >>>> double bestQ = vtkMath::Inf(); >>>> int best = -1; >>>> - for (int i = Nh / 2; i < Nh; ++i) >>>> + double ar = Nv * wmp / static_cast(hmp * Nh); >>>> + double q = (ar >= 1.0) ? ar : 1. / ar; >>>> + if (q < bestQ) >>>> { >>>> - double ar = Nv * wmp / static_cast(hmp * Nh); >>>> - double q = (ar >= 1.0) ? ar : 1. / ar; >>>> - if (q < bestQ) >>>> - { >>>> - bestQ = q; >>>> - best = i; >>>> - } >>>> + bestQ = q; >>>> + best = Nh-1; >>>> } >>>> Nh = best; >>>> } >>>> >>>> Thanks to you and Sergey for pursuing this Intel compiler issue and >>>> ParaView issue! >>>> >>>> - Cory >>>> >>>> On Fri, Mar 17, 2017 at 3:18 AM, wrote: >>>>> Hi Burlen, >>>>> >>>>> Your issue could be related with following, >>>>> >>>>> https://software.intel.com/en-us/forums/intel-c-compiler/topic/702934 >>>>> >>>>> I opened a bug report in Intel form and they found a bug in that >>>>> particular source file (pqPresetToPixmap.cxx). So, if you apply the fix >>>>> you might solve the problem but i am not sure. >>>>> >>>>> I hope it helps, >>>>> Regards, >>>>> >>>>> --ufuk >>>>> >>>>> >>>>>> I tried out ParaView 5.3.0 today, and I encountered the above crash. >>>>>> >>>>>> steps to reproduce: load data (sphere source will work), set color by >>>>>> var, open color map dialog, change to categorical, open choose presets >>>>>> dialog, scroll down, when you get near the bottom you will get the >>>>>> crash. >>>>>> >>>>>> Program received signal SIGFPE, Arithmetic exception. >>>>>> 0x00007ffff660a833 in >>>>>> pqPresetToPixmap::renderIndexedColorTransferFunction (this=0x5e22560, >>>>>> stc=0x647f460, size=...) at >>>>>> /home/bloring/work/ParaView/Qt/Components/pqPresetToPixmap.cxx:273 >>>>>> 273 Nh = wmp / (ss + PQ_SWATCH_PAD); >>>>>> (gdb) p ss >>>>>> $5 = -2 >>>>>> >>>>>> of course PQ_SWATCH_PAD == 2 >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Mar 20 15:16:58 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 20 Mar 2017 15:16:58 -0400 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <09cf70c9-06ed-4803-711f-f7f332c211d0@gmail.com> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> <09cf70c9-06ed-4803-711f-f7f332c211d0@gmail.com> Message-ID: <20170320191658.GA11734@megas.kitware.com> On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote: > I had to apply to clang-format manually. it's up there now. changes were > minimal so I squashed them into the patch. The fixes would have had to had been squashed in anyways; the robot checks each commit individually. > System has yet to acknowledge and re check. I assume it will > eventually. The new robot is silent on successful checks, so if it's silent, you're (likely) good. > Try as I may the clang-format script you guys are using doesn't work for > me. here are the errors: > Fedora 24: > > smic:~/work/ParaView$Utilities/Scripts/clang-format.bash --amend > YAML:4:24: error: invalid boolean > AlignAfterOpenBracket: DontAlign > ^~~~~~~~~ > Error reading /home/bloring/work/ParaView/.clang-format: Invalid > argument > > Maybe this is due to clang-format --version == 3.7? not sure but I won't > have time to re-install clang on this system, so I also tried on a newer > system. Yeah, I think it requires 3.8. There is a new `Do: reformat` command coming soon (this week ideally) to do the reformatting of your branch for you since not everyone has a suitable clang-format just laying around. --Ben From samuelkey at bresnan.net Mon Mar 20 17:18:23 2017 From: samuelkey at bresnan.net (Samuel Key) Date: Mon, 20 Mar 2017 15:18:23 -0600 Subject: [Paraview] SWKey: How to Clean-up an STL datum set? Message-ID: Hello All, I am working with a less than perfect STL surface. I was able to use PV's Clip filter spheres to remove a number of spatially isolated undesirable triangle clusters. (With a new application of the Extract Surface Filter, I was able to use Save Data to get an updated/revised STL file.) I am now working on removing triangles that have a point or an edge attached like a fish fin to the desired STL surface. I have successfully selected the undesirable fin-like triangles. Now, I want to delete (or Clip) these triangles to remove them from the datum set. Right-click delete does not appear to be an option? Is there some way to delete these selected STL triangles from the Datum set? Regards, Sam Key FMA Development From wascott at sandia.gov Mon Mar 20 21:54:45 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 21 Mar 2017 01:54:45 +0000 Subject: [Paraview] White (or other strange text) on Linux - Solved Message-ID: <4f1a405e6e164749888b253d671f27f2@ES01AMSNLNT.srn.sandia.gov> I wanted to mention a strange bug a user had In ParaView 5.3.0, Linux. All of his text in the ParaView GUI went white. He reset the appearance/display schemes and all of the text now appears normal. Keep calm and carry on. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From yzhzhang at ipe.ac.cn Mon Mar 20 22:33:16 2017 From: yzhzhang at ipe.ac.cn (=?UTF-8?B?5byg6amt5rSy?=) Date: Tue, 21 Mar 2017 10:33:16 +0800 (GMT+08:00) Subject: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? In-Reply-To: References: Message-ID: <1684530.2d330.15aeeb619f0.Coremail.yzhzhang@ipe.ac.cn> Hello, Thanks a lot for you two! I've found my mistakes based on your tips. It is true that I missed the khrplatform.h file. I put it in the same directory of other EGL header files with the name of "EGL", so it can not be found by the program. Creating a KHR dir and putting khrplatform.h into it solved my problem. Now my paraview can work with EGL. Thank you very much! Sincerely -Zhang -----????----- ???: "Alessandro De Maio" ????: 2017?3?21? ??? ???: "Dan Lipsa" ??: "???" , paraview ??: Re: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? Hi, I've just compiled the Paraview-5.3.0 superbuild with EGL. I created an EGL dir in /usr/include with egl.h, eglext.h and eglplatform.h (taken from www.khronos.org/registry/egl/) and I created a KHR dir in /usr/include with khrplatform.h (taken from the same site). ccmake already recognized the /usr/include/EGL include path for EGL and everything was ok. Alessandro On Mon, Mar 20, 2017 at 3:28 PM, Dan Lipsa wrote: Looking at the errors you are getting looks like /pan20/yzzhang/EGL/eglplatform.h needs KHR/khrplatform.h Maybe your configuration uses different EGL header files than what you expect. DAn On Mon, Mar 20, 2017 at 10:22 AM, ??? wrote: Thanks for your reply! But I don't know where the KHR/khrplatform.h is used. When I configure paraview using ccmake, the options about EGL are EGL_INCLUDE_DIR, EGL_LIBRARY, EGL_gldispatch_LIBRARY, EGL_opengl_LIBRARY, VTK_EGL_DEVICE_INDEX and VTK_USE_OFFSCREEN_EGL. In the path that I assigned to the EGL_INCLUDE_DIR, there is khrplatform.h file. What's more, I have built ParaView 5.2.0 with EGL used on another machine. That machine use NVIDIA GT 730 GPU, and in the EGL_INCLUDE_DIR path, there is not a khrplatform.h file, but the paraview can be built successfully and works. The khrplatform.h is required by the current EGL (1.5), but my EGL version is 1.4. Maybe it doesn't need that file? Thank you again! -Zhang -----????----- ???: "Dan Lipsa" ????: 2017?3?20? ??? ???: "???" ??: paraview ??: Re: [Paraview] How to configure ParaView 5.2.0 to use off screen rendering? It seems you are missing KHR/khrplatform.h You can download it from the EGL website: https://www.khronos.org/registry/EGL/ On Sat, Mar 18, 2017 at 3:51 AM, ??? wrote: Hello, I'm building ParaView 5.2.0 on a machine that uses NVIDIA Tesla K80 GPUs. The K80 GPUs have no interface for monitor, so I have to use off screen rendering. It's said that EGL is a pretty good choice for this situation, but as I switch VTK_USE_OFFSCREEN and VTK_USE_OFFSCREEN_EGL to "ON" and then make, I get these errors: Built target vtkIOImage [ 16%] Building C object VTK/ThirdParty/glew/vtkglew/CMakeFiles/vtkglew.dir/src/glew.c.o In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:37:29: error: KHR/khrplatform.h: No such file or directory In file included from /pan20/yzzhang/EGL/egl.h:39, from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/eglplatform.h:151: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLint? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:121: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? In file included from /pan20/yzzhang/ParaView-v5.2.0/VTK/ThirdParty/glew/vtkglew/src/glew.c:38: /pan20/yzzhang/EGL/egl.h:122: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLBoolean? /pan20/yzzhang/EGL/egl.h:123: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLContext? /pan20/yzzhang/EGL/egl.h:124: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? /pan20/yzzhang/EGL/egl.h:125: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?EGLSurface? ...... Maybe it is clear that there is something wrong with the EGL header file, but I don't know how to fix it. The operation system is CentOS 6.6. There is an integrated graphics and 6 K80 GPUs. I connect to the machine using ssh and have set headless X server using one of the K80 GPUs. I can run the glxgears test in the off screen mode, but I don'n know how to make sure that EGL is correctly setted. I want to know how to use EGL for off screen rendering. Any help would be highly appreciated! -Zhang _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Mar 21 08:40:06 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 21 Mar 2017 08:40:06 -0400 Subject: [Paraview] White (or other strange text) on Linux - Solved In-Reply-To: <4f1a405e6e164749888b253d671f27f2@ES01AMSNLNT.srn.sandia.gov> References: <4f1a405e6e164749888b253d671f27f2@ES01AMSNLNT.srn.sandia.gov> Message-ID: Good to hear! Thanks, Alan. On Mon, Mar 20, 2017 at 9:54 PM, Scott, W Alan wrote: > I wanted to mention a strange bug a user had In ParaView 5.3.0, Linux. All > of his text in the ParaView GUI went white. He reset the appearance/display > schemes and all of the text now appears normal. > > > > Keep calm and carry on. > > > > Alan > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Tue Mar 21 08:45:33 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 21 Mar 2017 08:45:33 -0400 Subject: [Paraview] SWKey: How to Clean-up an STL datum set? In-Reply-To: References: Message-ID: You can use the *Extract Selection* filter. Before you create the filter, make sure you invert the selection so that you are removing the selected selected. To do that, once you've made your selection, go to *Edit | Find Data* and then check the *Invert Selection *check box. Now, from the dialog itself, you can click the *Extract Selection* button to create a new *Extract Selection* filter. The output of this filter is *Unstructured Grid * and STL only supports *Polydata, *hence apply the *Extract Surface* filter again and then you shall be able to save out the result as a new STL file. Hope that helps. Utkarsh On Mon, Mar 20, 2017 at 5:18 PM, Samuel Key wrote: > Hello All, > > I am working with a less than perfect STL surface. I was able to use PV's > Clip filter spheres to remove a number of spatially isolated undesirable > triangle clusters. (With a new application of the Extract Surface Filter, > I was able to use Save Data to get an updated/revised STL file.) > > I am now working on removing triangles that have a point or an edge > attached like a fish fin to the desired STL surface. I have successfully > selected the undesirable fin-like triangles. Now, I want to delete (or > Clip) these triangles to remove them from the datum set. Right-click > delete does not appear to be an option? > > Is there some way to delete these selected STL triangles from the Datum > set? > > Regards, > > Sam Key > FMA Development > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Tue Mar 21 13:00:02 2017 From: burlen.loring at gmail.com (Burlen Loring) Date: Tue, 21 Mar 2017 10:00:02 -0700 Subject: [Paraview] Program received signal SIGFPE, Arithmetic exception. In-Reply-To: <20170320191658.GA11734@megas.kitware.com> References: <152bf64a-65b3-5bd6-48fa-89d44f791db2@lbl.gov> <49150.78.182.90.145.1489735101.squirrel@webmail.be.itu.edu.tr> <6b4f488a-3b12-4d3c-5928-f3fefec5db9c@gmail.com> <09cf70c9-06ed-4803-711f-f7f332c211d0@gmail.com> <20170320191658.GA11734@megas.kitware.com> Message-ID: OK, good to know. would any one be willing to give a quick review? https://gitlab.kitware.com/paraview/paraview/merge_requests/1476 On 03/20/2017 12:16 PM, Ben Boeckel wrote: > On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote: >> I had to apply to clang-format manually. it's up there now. changes were >> minimal so I squashed them into the patch. > The fixes would have had to had been squashed in anyways; the robot > checks each commit individually. > >> System has yet to acknowledge and re check. I assume it will >> eventually. > The new robot is silent on successful checks, so if it's silent, you're > (likely) good. > >> Try as I may the clang-format script you guys are using doesn't work for >> me. here are the errors: >> Fedora 24: >> >> smic:~/work/ParaView$Utilities/Scripts/clang-format.bash --amend >> YAML:4:24: error: invalid boolean >> AlignAfterOpenBracket: DontAlign >> ^~~~~~~~~ >> Error reading /home/bloring/work/ParaView/.clang-format: Invalid >> argument >> >> Maybe this is due to clang-format --version == 3.7? not sure but I won't >> have time to re-install clang on this system, so I also tried on a newer >> system. > Yeah, I think it requires 3.8. There is a new `Do: reformat` command > coming soon (this week ideally) to do the reformatting of your branch > for you since not everyone has a suitable clang-format just laying > around. > > --Ben From zdavis at pointwise.com Tue Mar 21 13:22:54 2017 From: zdavis at pointwise.com (Zach Davis) Date: Tue, 21 Mar 2017 17:22:54 +0000 Subject: [Paraview] ParaView 5 Crashes on macOS (Sierra) Message-ID: Tuesday, 21 March 2017 All, I?ve been having issues with ParaView version 5 builds since their release. I?ve tried each new release as its announced, but run into the same issue. The application can be opened, but anytime I attempt to open a file the application crashes before even displaying the Open/Save dialog window. The termination signal is a Segmentation fault of type 11. I?ve attached the crash report for anyone more knowledgeable about what the issue is. Has anyone else experienced this issue? Is there a workaround? Best Regards, Zach Davis Pointwise?, Inc. Sr. Engineer, Sales & Marketing 213 South Jennings Avenue Fort Worth, TX 76104-1107 E: zach.davis at pointwise.com P: (817) 377-2807 x1202 F: (817) 377-2799 enc -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ParaView 5.3.0 Crash Report.rtf Type: text/rtf Size: 99407 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP URL: From cory.quammen at kitware.com Tue Mar 21 13:30:35 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 21 Mar 2017 13:30:35 -0400 Subject: [Paraview] ParaView 5 Crashes on macOS (Sierra) In-Reply-To: References: Message-ID: Hi Zach, Someone else on this mailing list recently reported a similar crash. Do you have any unusual file systems mounted on the Mac in question? That will help debug the problem. Thanks, Cory On Tue, Mar 21, 2017 at 1:22 PM, Zach Davis wrote: > Tuesday, 21 March 2017 > > > > All, > > I?ve been having issues with ParaView version 5 builds since their > release. I?ve tried each new release as its announced, but run into the > same issue. The application can be opened, but anytime I attempt to open a > file the application crashes before even displaying the Open/Save dialog > window. The termination signal is a Segmentation fault of type 11. I?ve > attached the crash report for anyone more knowledgeable about what the > issue is. Has anyone else experienced this issue? Is there a workaround? > > Best Regards, > > > > [image: Pointwise, Inc.] > Zach Davis > Pointwise?, Inc. > Sr. Engineer, Sales & Marketing > 213 South Jennings Avenue > Fort Worth, TX 76104-1107 > > *E*: zach.davis at pointwise.com > *P*: (817) 377-2807 x1202 <(817)%20377-2807> > *F*: (817) 377-2799 > > > > enc > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zdavis at pointwise.com Tue Mar 21 13:36:03 2017 From: zdavis at pointwise.com (Zach Davis) Date: Tue, 21 Mar 2017 17:36:03 +0000 Subject: [Paraview] ParaView 5 Crashes on macOS (Sierra) In-Reply-To: References: Message-ID: <377360A2-FDC6-4612-A3A6-D1C247083BF8@pointwise.com> Hi Cory, I have three SMB volumes and one NFS volume mounted at /Users/zdavis/Shares using Autofs. As an aside, I have been able to revert to using ParaView 4.4.0, but obviously don?t want to be stuck on this version forever if it can be avoided. Best Regards, Zach Davis Pointwise?, Inc. Sr. Engineer, Sales & Marketing 213 South Jennings Avenue Fort Worth, TX 76104-1107 E: zach.davis at pointwise.com P: (817) 377-2807 x1202 F: (817) 377-2799 > On Mar 21, 2017, at 12:30 PM, Cory Quammen wrote: > > Hi Zach, > > Someone else on this mailing list recently reported a similar crash. Do you have any unusual file systems mounted on the Mac in question? That will help debug the problem. > > Thanks, > Cory > > On Tue, Mar 21, 2017 at 1:22 PM, Zach Davis > wrote: > Tuesday, 21 March 2017 > > > > All, > > I?ve been having issues with ParaView version 5 builds since their release. I?ve tried each new release as its announced, but run into the same issue. The application can be opened, but anytime I attempt to open a file the application crashes before even displaying the Open/Save dialog window. The termination signal is a Segmentation fault of type 11. I?ve attached the crash report for anyone more knowledgeable about what the issue is. Has anyone else experienced this issue? Is there a workaround? > > Best Regards, > > > > > Zach Davis > Pointwise?, Inc. > Sr. Engineer, Sales & Marketing > 213 South Jennings Avenue > Fort Worth, TX 76104-1107 > > E: zach.davis at pointwise.com > P: (817) 377-2807 x1202 > F: (817) 377-2799 > > > enc > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP URL: From d.r.tunuguntla at utwente.nl Tue Mar 21 13:55:41 2017 From: d.r.tunuguntla at utwente.nl (d.r.tunuguntla at utwente.nl) Date: Tue, 21 Mar 2017 17:55:41 +0000 Subject: [Paraview] Unable to build Command Line Executables in Paraview 5.3 using CMake Message-ID: <1490118941838.3876@utwente.nl> Dear Paraview Team, Currently, I am building paraview 5.3 from its source files alongwith Qt 5.8. I am doing this to add superquadric custom glyphs in paraview. After a whole day of figuring out and installing the required libraries, the build process now reaches 100% however it fails when trying to build command line executables. Below is the is what i see on my terminal when i use make -d.. [100%] Linking CXX executable ../bin/pvpython Reaping winning child 0x6e9990 PID 28851 Live child 0x6e9990 (bin/pvpython) PID 28853 //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QDateTime::toSecsSinceEpoch() const at Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `qrand()@Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QByteArray::mid(int, int) const at Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QAbstractItemModel::layoutAboutToBeChanged(QList const&, QAbstractItemModel::LayoutChangeHint)@Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QMetaType::unregisterConverterFunction(int, int)@Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `typeinfo for QAbstractItemModelPrivate at Qt_5_PRIVATE_API' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QMetaType::typeName(int)@Qt_5' //home/scordee/Qt5.8.0/5.8/gcc_64/lib/libQt5Gui.so.5: undefined reference to `QChar::toUpper(unsigned int)@Qt_5' ... ... ... ... Reaping losing child 0x6e9990 PID 28853 CommandLineExecutables/CMakeFiles/pvpython.dir/build.make:127: recipe for target 'bin/pvpython' failed make[2]: *** [bin/pvpython] Error 1 Removing child 0x6e9990 PID 28853 from chain. Reaping losing child 0x2106100 PID 28850 CMakeFiles/Makefile2:51541: recipe for target 'CommandLineExecutables/CMakeFiles/pvpython.dir/all' failed make[1]: *** [CommandLineExecutables/CMakeFiles/pvpython.dir/all] Error 2 Removing child 0x2106100 PID 28850 from chain. Reaping losing child 0x1877c60 PID 25089 Makefile:138: recipe for target 'all' failed make: *** [all] Error 2 Removing child 0x1877c60 PID 25089 from chain. ========================================= So as a temporary solution, I commented out the add_subdirectory(CommandLineExecutables) in the CMakeLists.txt. #if (PARAVIEW_ENABLE_COMMANDLINE_TOOLS) # add_subdirectory(CommandLineExecutables) #endif() Then the build succeeds. But sadly, I am still unable to start paraview because then I get some "libprotobuf" error which states that I need to update my libprotobuf library. ============== libprotobuf FATAL /home/scordee/Paraview/Source/ThirdParty/protobuf/vtkprotobuf/src/google/protobuf/stubs/common.cc:62] This program requires version 2.6.0 of the Protocol Buffer runtime library, but the installed version is 2.3.0. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/build/mir-pkdHET/mir-0.21.0+16.04.20160330/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc".) Aborted (core dumped) ============= Could you please help me with the above issue? I am building paraview on Ubuntu Xenial 16 LTS. Thank you in advance Deepak Dr. Deepak Tunuguntla Post-Doctoral Researcher Multi-Scale Mechanics Group Dept. of Thermal and Fluid Engineering University of Twente, The Netherlands -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 21 14:09:02 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 21 Mar 2017 14:09:02 -0400 Subject: [Paraview] ParaView 5 Crashes on macOS (Sierra) In-Reply-To: <377360A2-FDC6-4612-A3A6-D1C247083BF8@pointwise.com> References: <377360A2-FDC6-4612-A3A6-D1C247083BF8@pointwise.com> Message-ID: Zach, Thanks for the information. I mounted an SMB volume on my machine and did not get a crash when opening a file in ParaView 5.3.0. That leaves NFS as causing some unhandled condition in the code pointed out by your error report. I'll file a bug report and investigate for 5.4.0. https://gitlab.kitware.com/paraview/paraview/issues/17310 Thanks, Cory On Tue, Mar 21, 2017 at 1:36 PM, Zach Davis wrote: > Hi Cory, > > I have three SMB volumes and one NFS volume mounted at > /Users/zdavis/Shares using Autofs. As an aside, I have been able to revert > to using ParaView 4.4.0, but obviously don?t want to be stuck on this > version forever if it can be avoided. > > Best Regards, > > > [image: Pointwise, Inc.] > Zach Davis > Pointwise?, Inc. > Sr. Engineer, Sales & Marketing > 213 South Jennings Avenue > Fort Worth, TX 76104-1107 > > *E*: zach.davis at pointwise.com > *P*: (817) 377-2807 x1202 <(817)%20377-2807> > *F*: (817) 377-2799 > > > > On Mar 21, 2017, at 12:30 PM, Cory Quammen > wrote: > > Hi Zach, > > Someone else on this mailing list recently reported a similar crash. Do > you have any unusual file systems mounted on the Mac in question? That will > help debug the problem. > > Thanks, > Cory > > On Tue, Mar 21, 2017 at 1:22 PM, Zach Davis wrote: > >> Tuesday, 21 March 2017 >> >> >> >> All, >> >> I?ve been having issues with ParaView version 5 builds since their >> release. I?ve tried each new release as its announced, but run into the >> same issue. The application can be opened, but anytime I attempt to open a >> file the application crashes before even displaying the Open/Save dialog >> window. The termination signal is a Segmentation fault of type 11. I?ve >> attached the crash report for anyone more knowledgeable about what the >> issue is. Has anyone else experienced this issue? Is there a workaround? >> >> Best Regards, >> >> >> >> [image: Pointwise, Inc.] >> Zach Davis >> Pointwise?, Inc. >> Sr. Engineer, Sales & Marketing >> 213 South Jennings Avenue >> Fort Worth, TX 76104-1107 >> >> *E*: zach.davis at pointwise.com >> *P*: (817) 377-2807 x1202 <(817)%20377-2807> >> *F*: (817) 377-2799 >> >> >> >> >> enc >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/open >> source/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Tue Mar 21 16:07:48 2017 From: samuelkey at bresnan.net (Samuel Key) Date: Tue, 21 Mar 2017 14:07:48 -0600 Subject: [Paraview] SWKey: How to Clean-up an STL datum set? In-Reply-To: References: Message-ID: <98ea8c6b-f23d-73a0-8224-c38f8c4917e7@bresnan.net> Greetings Utkarsh! Your advice is exceptional; the remaining "unwanted" STL triangles attached to the desired STL surface have been removed. A couple of lessons: (1) At first the instruction sequence seemed to me a little awkward. However, after repeated use it became rhythmic. I did find it better to reset/uncheck *Invert Selection* of the*Edit | Find Data* panel before going to the next location. (2) It took a couple of tries for me to discover that the unwanted fin-like attachments were actually zero-thickness regions with matching back-to-back STL-triangles -- one for each side, and hence, it required a second removal go around. (The original 30+ layered tetrahedral mesh as our Japanese colleagues would say, "was not so good.") (3) A triangular hole required a hand-crafted STL-triangle with a borrowed normal-vector from a neighbor triangle. After writing out the datum set, hand editing the STL-file to add in the missing triangle and renaming a copy of the datum-set, a read and write with PV showed that PV 'corrected' the normal vector. Whoever wrote that section of code deserves a pat on the back. (4) The PV window with the row of miniature icons in upper-left corner took me a couple of tries to figure out that add & subtract were clues to use ctrl & shift keys when making selections. IMHO, well done. (5) Message to myself: "The more you use ParaView, the smarter it gets." Thanks for really great tool! Sam Key On 3/21/2017 6:45 AM, Utkarsh Ayachit wrote: > You can use the *Extract Selection* filter. Before you create the > filter, make sure you invert the selection so that you are removing > the selected selected. To do that, once you've made your selection, go > to *Edit | Find Data* and then check the *Invert Selection *check box. > Now, from the dialog itself, you can click the *Extract > Selection* button to create a new *Extract Selection* filter. The > output of this filter is *Unstructured Grid * and STL only supports > *Polydata, *hence apply the *Extract Surface* filter again and then > you shall be able to save out the result as a new STL file. > > Hope that helps. > Utkarsh > > On Mon, Mar 20, 2017 at 5:18 PM, Samuel Key > wrote: > > Hello All, > > I am working with a less than perfect STL surface. I was able to > use PV's Clip filter spheres to remove a number of spatially > isolated undesirable triangle clusters. (With a new application > of the Extract Surface Filter, I was able to use Save Data to get > an updated/revised STL file.) > > I am now working on removing triangles that have a point or an > edge attached like a fish fin to the desired STL surface. I have > successfully selected the undesirable fin-like triangles. Now, I > want to delete (or Clip) these triangles to remove them from the > datum set. Right-click delete does not appear to be an option? > > Is there some way to delete these selected STL triangles from the > Datum set? > > Regards, > > Sam Key > FMA Development > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsivakumar at cdac.in Wed Mar 22 00:12:14 2017 From: vsivakumar at cdac.in (Dr. Sivakumar) Date: Wed, 22 Mar 2017 09:42:14 +0530 (IST) Subject: [Paraview] HELP Message-ID: <1746184554.933.1490155934905.JavaMail.open-xchange@webmail.cdac.in> Dear All, I would like to know about Paraview 3D visuvalization option, whether present version 5.3 of Paraview support the displaying global bathymetry data (.img, geotif) with projection information without customization? and how do I display the geocoded ocean parameters like ocean salinity data and ocean temperature data (geocoded points and geocoded raster image) over bathymetry image. These information can be seen in 3D view with overlaying geocoded/projected multiple image. Kindly let me know. With Regards, Sivakumar ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Wed Mar 22 06:50:38 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Wed, 22 Mar 2017 13:50:38 +0300 Subject: [Paraview] Custom filters Message-ID: Hello, Is it possible to change drop down list values from information script? For example, we can take values from input arrays but instead we create field self.names and take values from it. Best Regards, Rustem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 22 10:09:06 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 22 Mar 2017 10:09:06 -0400 Subject: [Paraview] Custom filters In-Reply-To: References: Message-ID: If I understanding you correctly, unfortunately no, it's not possible using custom filters. On Wed, Mar 22, 2017 at 6:50 AM, Rustem Khabetdinov wrote: > Hello, > > Is it possible to change drop down list values from information script? For > example, we can take values from input arrays but instead we create field > self.names and take values from it. > > Best Regards, > Rustem. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Wed Mar 22 12:55:32 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 22 Mar 2017 16:55:32 +0000 Subject: [Paraview] [EXTERNAL] HELP In-Reply-To: <1746184554.933.1490155934905.JavaMail.open-xchange@webmail.cdac.in> References: <1746184554.933.1490155934905.JavaMail.open-xchange@webmail.cdac.in> Message-ID: Sivakumar, I don?t know the answer to your question, but the easy way would be to download ParaView from paraview.org (it?s free!) and find out. With regards to how to use ParaView, there is a 2 page getting started guide that appears at startup. There are two good links to training materials found on the Help menu within ParaView. Last, the ParaView Guide (book) comes with ParaView as a .pdf for free. This is also available from the Help menu. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dr. Sivakumar Sent: Tuesday, March 21, 2017 10:12 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] HELP Dear All, I would like to know about Paraview 3D visuvalization option, whether present version 5.3 of Paraview support the displaying global bathymetry data (.img, geotif) with projection information without customization? and how do I display the geocoded ocean parameters like ocean salinity data and ocean temperature data (geocoded points and geocoded raster image) over bathymetry image. These information can be seen in 3D view with overlaying geocoded/projected multiple image. Kindly let me know. With Regards, Sivakumar ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Wed Mar 22 18:35:58 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Wed, 22 Mar 2017 23:35:58 +0100 Subject: [Paraview] Unable to build Command Line Executables in Paraview 5.3 using CMake In-Reply-To: <1490118941838.3876@utwente.nl> References: <1490118941838.3876@utwente.nl> Message-ID: > Currently, I am building paraview 5.3 from its source files alongwith Qt 5.8. I am doing this to add superquadric custom glyphs in paraview. > > After a whole day of figuring out and installing the required libraries, the build process now reaches 100% however it fails when trying to build command line executables. Below is the is what i see on my terminal when i use make -d.. Is there any reason you don?t use the superbuild? https://gitlab.kitware.com/paraview/paraview-superbuild Regards, Fabian From d.r.tunuguntla at utwente.nl Wed Mar 22 19:00:49 2017 From: d.r.tunuguntla at utwente.nl (d.r.tunuguntla at utwente.nl) Date: Wed, 22 Mar 2017 23:00:49 +0000 Subject: [Paraview] Unable to build Command Line Executables in Paraview 5.3 using CMake In-Reply-To: References: <1490118941838.3876@utwente.nl>, Message-ID: <1490223649265.50020@utwente.nl> Ahh.. didn't really know about that. Will try installing vis superbuild option. I hope I can also add the superquadric glyphs (which is why I am building the source files) to the plugin directory. Thank you for your reply. I will update you with the outcome very soon. Fingers crossed ;) Deepak ________________________________________ From: Fabian Wein Sent: Wednesday, March 22, 2017 11:35 PM To: Tunuguntla, D.R. (ET) Cc: paraview at paraview.org Subject: Re: [Paraview] Unable to build Command Line Executables in Paraview 5.3 using CMake > Currently, I am building paraview 5.3 from its source files alongwith Qt 5.8. I am doing this to add superquadric custom glyphs in paraview. > > After a whole day of figuring out and installing the required libraries, the build process now reaches 100% however it fails when trying to build command line executables. Below is the is what i see on my terminal when i use make -d.. Is there any reason you don?t use the superbuild? https://gitlab.kitware.com/paraview/paraview-superbuild Regards, Fabian From chandisasmal at engineering.ucsb.edu Wed Mar 22 20:32:54 2017 From: chandisasmal at engineering.ucsb.edu (chandisasmal) Date: Wed, 22 Mar 2017 17:32:54 -0700 Subject: [Paraview] how to visualize a derived quantity in Paraview Message-ID: Hi Community, I am using Paraview for the visualization of my OpenFoam data. I would like to visualize a derived quantity which is (dUx / dx)^2 + (dUx / dy)^2 + (dUy / dx)^2 + (dUy / dy)^2 Can someone please help me how to do that in Paraview ? Thanks in advance ! Cheers Chandi From cory.quammen at kitware.com Wed Mar 22 21:21:08 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 22 Mar 2017 21:21:08 -0400 Subject: [Paraview] how to visualize a derived quantity in Paraview In-Reply-To: References: Message-ID: Chandi, See the Calculator filter for computing expressions from data arrays. If you need to do differentiation, see the Gradient filter for first derivatives. HTH, Cory On Wed, Mar 22, 2017 at 8:32 PM, chandisasmal wrote: > Hi Community, > > I am using Paraview for the visualization of my OpenFoam data. I would like > to visualize a derived quantity which is > > (dUx / dx)^2 + (dUx / dy)^2 + (dUy / dx)^2 + (dUy / dy)^2 > > Can someone please help me how to do that in Paraview ? > > Thanks in advance ! > > Cheers > Chandi > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. From d.r.tunuguntla at utwente.nl Thu Mar 23 12:39:40 2017 From: d.r.tunuguntla at utwente.nl (d.r.tunuguntla at utwente.nl) Date: Thu, 23 Mar 2017 16:39:40 +0000 Subject: [Paraview] Unable to launch paraview Message-ID: <1490287180348.30524@utwente.nl> Dear Paraview team and users, Today i built paraview on Ubuntu 16.04 LTS, using the paraview-superbuild option. On launching paraview via the terminal, I first had an issue with libprotobuf .. as the version of libprotobuf on my machine was 2.6.1 when compared to the one supplied by ParaView-superbuild source. Their version was 2.3. After going through the protobuf source files .. as a solution I removed the libprotobuf package from my Desktop and this solved the libprotobuf version issue. However, when I rebuilt and relaunched paraview via the terminal I get into another problem which is shown below QFontDatabase: Cannot find font directory /home/scordee/Paraview/ParaviewSuperbuild/Build/install/lib/fonts. Segmentation fault (core dumped) How do I solve this problem now? Any help would be appreciated. Regards Deepak -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Thu Mar 23 15:02:56 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 23 Mar 2017 15:02:56 -0400 Subject: [Paraview] Difference between two Exodus II files Message-ID: Hello Paraviewers, I want to get the difference of all the cell data, similar to what was done here http://paraview.markmail.org/search/?q=difference#query:difference+page:1+mid:lc6a4ss2j5hi37ps+state:results However, how do I make a writer that can accept the appended data? I tried to create the writer writer = CreateWriter(path+'Difference.e', reader[0]) writer.CellData.append( reader[0].CellData['x'] - reader[1].CellData['x'] , 'x') and got the error Traceback (most recent call last): File "", line 1, in File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", line 1595, in __getattr__ array = self.GetArray(name) File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", line 1531, in GetArray if not self.GetFieldData().GetArrayInformation(idx): File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", line 1520, in GetFieldData return getattr(self.Proxy.GetDataInformation(self.OutputPort), "Get%sInformation" % self.FieldData)() AttributeError: 'NoneType' object has no attribute 'GetCellDataInformation' Then, I also tried to just copy the reader writer = reader[0] writer.CellData.append( reader[0].CellData['x'] - reader[1].CellData['x'] , 'x') and got the error Traceback (most recent call last): File "", line 1, in File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", line 1597, in __getattr__ raise AttributeError("class has no attribute %s" % name) AttributeError: class has no attribute append Any advice? Regards, John R. Haase jhaase1 at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Mar 23 16:41:44 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 23 Mar 2017 20:41:44 +0000 Subject: [Paraview] Scale time Message-ID: Is it possible to scale time, and then display this on the screen with the Annotate Time source? For instance, assuming can.exo's time is in seconds, I would like to present time on screen in milliseconds. Can.exo's first timestep is at 0.0001 seconds. I want to display it as 0.1 milliseconds. 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 wascott at sandia.gov Thu Mar 23 17:06:27 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 23 Mar 2017 21:06:27 +0000 Subject: [Paraview] How do you "see" FieldData Message-ID: <42c095f23ac64b92aec99ee5c0a4e7ca@ES01AMSNLNT.srn.sandia.gov> >From a user: How do you "see" FieldData variables created in the ProgrammableFilter in the PlotGlobalVariablesOverTime filter? I'm creating a FieldData variable in the ProgrammableFilter. Now I'd like to plot it over time. It isn't available as an option for me to plot, though. I see other global variables, just not this one. disp_y = inputs[0].PointData["displ_"][:,1] mean_disp = mean(disp_y) output.FieldData.append(mean_disp, "MEAN_DISP") Am I doing something wrong here? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Mar 23 17:09:26 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 23 Mar 2017 21:09:26 +0000 Subject: [Paraview] Scale time Message-ID: You can add the Temporal Shift Scale filter and set the Scale, in your case, to 1000. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 2:42 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Scale time Is it possible to scale time, and then display this on the screen with the Annotate Time source? For instance, assuming can.exo's time is in seconds, I would like to present time on screen in milliseconds. Can.exo's first timestep is at 0.0001 seconds. I want to display it as 0.1 milliseconds. 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 wascott at sandia.gov Thu Mar 23 17:29:15 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 23 Mar 2017 21:29:15 +0000 Subject: [Paraview] Scale time In-Reply-To: References: Message-ID: <22e936d811cd47e282e5fa5d334a889c@ES01AMSNLNT.srn.sandia.gov> That works! I thought I tried it, and it failed. I suspect it was me that failed. Thanks, Alan From: Moreland, Kenneth Sent: Thursday, March 23, 2017 3:09 PM To: Scott, W Alan ; paraview at paraview.org Subject: RE: [Paraview] Scale time You can add the Temporal Shift Scale filter and set the Scale, in your case, to 1000. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 2:42 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Scale time Is it possible to scale time, and then display this on the screen with the Annotate Time source? For instance, assuming can.exo's time is in seconds, I would like to present time on screen in milliseconds. Can.exo's first timestep is at 0.0001 seconds. I want to display it as 0.1 milliseconds. 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 kmorel at sandia.gov Thu Mar 23 17:59:34 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 23 Mar 2017 21:59:34 +0000 Subject: [Paraview] How do you "see" FieldData Message-ID: <86376fae02604d629b512aec342e6d10@ES08AMSNLNT.srn.sandia.gov> I don't think Plot Global Variables Over Time works the way you think it does. This filter assumes that the global arrays contain a static array the same size as the number of time steps and then plots that with the time array on the x axis and the entries in this array in the y axis. If the size of the global variable does not equal the number of time steps, the view will show nothing. I think you really want to use Plot Selection Over Time. That you can give a value and it will iterate the pipeline over time and compute the value for each time step. Unfortunately, it looks like the filter is broken for selections on field data. It works, however, on table data, so you can write the result as that. I got what I think you want using the can data set. Here are the steps I used: 1. Load can.ex2. All variables. Apply. 2. Add the Programmable Filter. Set the output type to vtkTable (!) and use the following script: disp_y = inputs[0].PointData["DISPL"][:,1] mean_disp = mean(disp_y) output.RowData.append(mean_disp, "MEAN_DISP") 3. Select the single row shown in the spreadsheet that pops up. 4. Add Plot Selection Over Time filter. Apply. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 3:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] How do you "see" FieldData >From a user: How do you "see" FieldData variables created in the ProgrammableFilter in the PlotGlobalVariablesOverTime filter? I'm creating a FieldData variable in the ProgrammableFilter. Now I'd like to plot it over time. It isn't available as an option for me to plot, though. I see other global variables, just not this one. disp_y = inputs[0].PointData["displ_"][:,1] mean_disp = mean(disp_y) output.FieldData.append(mean_disp, "MEAN_DISP") Am I doing something wrong here? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.r.tunuguntla at utwente.nl Thu Mar 23 18:06:12 2017 From: d.r.tunuguntla at utwente.nl (d.r.tunuguntla at utwente.nl) Date: Thu, 23 Mar 2017 22:06:12 +0000 Subject: [Paraview] Superquadric tensor glyph Message-ID: <1490306777569.30849@utwente.nl> Dear Paraview users, I would like to visualise non-spherical particles in paraview (super ellipsoids to be precise). Thereby, I am currently trying to add customised plugins named tensor glyphs and superquadric tensor glyphs, which are available on the paraview wiki. However, since the past 4 days I have not been able to build paraview from its source files. I hav even tried the superbuild option but there is always some or the other library missing. The farthest I have reached so far is a black screen with a XError. Morover, different issues pop up on different desktops (with Ubuntu) I have tried to install paraview on. It is really very annoying at the moment. Is there any other way to add superquadric glyphs option to paraview? It would be great if this is possible. Regards Deepak Dr. Deepak Tunuguntla Post-Doctoral Researcher Multi-Scale Mechanics Group Dept. of Thermal and Fluid Engineering University of Twente, The Netherlands -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Fri Mar 24 05:17:18 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 24 Mar 2017 10:17:18 +0100 Subject: [Paraview] Superquadric tensor glyph In-Reply-To: <1490306777569.30849@utwente.nl> References: <1490306777569.30849@utwente.nl> Message-ID: Hi There is already something called Tensor Glyph in ParaView, you may want to check it out. Regards, Mathieu Westphal On Thu, Mar 23, 2017 at 11:06 PM, wrote: > Dear Paraview users, > > > I would like to visualise non-spherical particles in paraview (super > ellipsoids to be precise). Thereby, I am currently trying to add customised > plugins named tensor glyphs and superquadric tensor glyphs, which are > available on the paraview wiki. > > > However, since the past 4 days I have not been able to build paraview from > its source files. I hav even tried the superbuild option but there is > always some or the other library missing. The farthest I have reached so > far is a black screen with a XError. Morover, different issues pop up on > different desktops (with Ubuntu) I have tried to install paraview on. It is > really very annoying at the moment. > > > Is there any other way to add superquadric glyphs option to paraview? It > would be great if this is possible. > > > Regards > > Deepak > > > Dr. Deepak Tunuguntla > Post-Doctoral Researcher > Multi-Scale Mechanics Group > Dept. of Thermal and Fluid Engineering > University of Twente, The Netherlands > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rccm.kyoshimi at gmail.com Fri Mar 24 06:46:32 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Fri, 24 Mar 2017 19:46:32 +0900 Subject: [Paraview] Difference between two Exodus II files In-Reply-To: References: Message-ID: Hi, One solution is to call programmable filter from your python program. I haven't tried Exodus II format, but the below is working: readers = [] readers.append(OpenDataFile(PATH + 'aaa.vtp')) readers.append(OpenDataFile(PATH + 'bbb.vtp')) programmable = ProgrammableFilter(Input=readers) programmable.Script="\nelev0 = inputs[0].PointData['Elevation'] \nelev1 = inputs[1].PointData['Elevation']\noutput.PointData.append(elev1 - elev0, 'difference')" programmable.UpdatePipeline() writer = CreateWriter(PATH + 'ccc.vtp', programmable) writer.UpdatePipeline() Regards, yoshimi 2017-03-24 4:02 GMT+09:00 John Haase : > Hello Paraviewers, > > I want to get the difference of all the cell data, similar to what was done > here > > http://paraview.markmail.org/search/?q=difference#query:difference+page:1+mid:lc6a4ss2j5hi37ps+state:results > > However, how do I make a writer that can accept the appended data? I tried > to create the writer > > writer = CreateWriter(path+'Difference.e', reader[0]) > writer.CellData.append( reader[0].CellData['x'] - reader[1].CellData['x'] , > 'x') > > > and got the error > > Traceback (most recent call last): > File "", line 1, in > File "C:\Program Files\ParaView > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > line 1595, in __getattr__ > array = self.GetArray(name) > File "C:\Program Files\ParaView > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > line 1531, in GetArray > if not self.GetFieldData().GetArrayInformation(idx): > File "C:\Program Files\ParaView > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > line 1520, in GetFieldData > return getattr(self.Proxy.GetDataInformation(self.OutputPort), > "Get%sInformation" % self.FieldData)() > AttributeError: 'NoneType' object has no attribute 'GetCellDataInformation' > > > Then, I also tried to just copy the reader > > writer = reader[0] > writer.CellData.append( reader[0].CellData['x'] - reader[1].CellData['x'] , > 'x') > > > and got the error > > Traceback (most recent call last): > File "", line 1, in > File "C:\Program Files\ParaView > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > line 1597, in __getattr__ > raise AttributeError("class has no attribute %s" % name) > AttributeError: class has no attribute append > > > Any advice? > > Regards, > > John R. Haase > jhaase1 at nd.edu > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Fri Mar 24 14:16:45 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 24 Mar 2017 18:16:45 +0000 Subject: [Paraview] How do you "see" FieldData In-Reply-To: <86376fae02604d629b512aec342e6d10@ES08AMSNLNT.srn.sandia.gov> References: <86376fae02604d629b512aec342e6d10@ES08AMSNLNT.srn.sandia.gov> Message-ID: <8c10e15c07dc480ea826948070b0ff4c@ES01AMSNLNT.srn.sandia.gov> OK, looking at your reply, I think I have a fundamental misunderstanding, and have been mixing up terms. What is a "global data" and "field data"? What's the difference? I think you are saying that if we have 43 timesteps (can.exo), any global arrays will have 43 entries (such as time or atmospheric pressure). However, field data will have a single entry (such as Title)? Below, you are setting - and resetting - the field data over and over again? Alan From: Moreland, Kenneth Sent: Thursday, March 23, 2017 4:00 PM To: Scott, W Alan ; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData I don't think Plot Global Variables Over Time works the way you think it does. This filter assumes that the global arrays contain a static array the same size as the number of time steps and then plots that with the time array on the x axis and the entries in this array in the y axis. If the size of the global variable does not equal the number of time steps, the view will show nothing. I think you really want to use Plot Selection Over Time. That you can give a value and it will iterate the pipeline over time and compute the value for each time step. Unfortunately, it looks like the filter is broken for selections on field data. It works, however, on table data, so you can write the result as that. I got what I think you want using the can data set. Here are the steps I used: 1. Load can.ex2. All variables. Apply. 2. Add the Programmable Filter. Set the output type to vtkTable (!) and use the following script: disp_y = inputs[0].PointData["DISPL"][:,1] mean_disp = mean(disp_y) output.RowData.append(mean_disp, "MEAN_DISP") 3. Select the single row shown in the spreadsheet that pops up. 4. Add Plot Selection Over Time filter. Apply. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 3:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] How do you "see" FieldData >From a user: How do you "see" FieldData variables created in the ProgrammableFilter in the PlotGlobalVariablesOverTime filter? I'm creating a FieldData variable in the ProgrammableFilter. Now I'd like to plot it over time. It isn't available as an option for me to plot, though. I see other global variables, just not this one. disp_y = inputs[0].PointData["displ_"][:,1] mean_disp = mean(disp_y) output.FieldData.append(mean_disp, "MEAN_DISP") Am I doing something wrong here? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Mar 24 14:35:07 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 24 Mar 2017 18:35:07 +0000 Subject: [Paraview] How do you "see" FieldData In-Reply-To: <8c10e15c07dc480ea826948070b0ff4c@ES01AMSNLNT.srn.sandia.gov> References: <86376fae02604d629b512aec342e6d10@ES08AMSNLNT.srn.sandia.gov> <8c10e15c07dc480ea826948070b0ff4c@ES01AMSNLNT.srn.sandia.gov> Message-ID: <68c46c635ec04690a31860fabf52da55@ES08AMSNLNT.srn.sandia.gov> The Exodus II file format has the concept of "global data." When this is read into ParaView/VTK, it gets placed into what vtkDataSet calls the "field data." Because of this, I tend to use the two interchangeably (and likewise so does the ParaView GUI). Personally, I prefer the term "global data" as it is more descriptive. Arrays in global/field data can be whatever you want and whatever size you want. For example, someone might want to record the total volume of the data set. That could reasonably be stored in the global/field data. Another example might be that someone wants to record the time at which a particular event occurs. This could be stored in the global/field data as an array of marked time indices. As you can see, global/field data can mean pretty much whatever you want it to mean, so you can't do much with it unless you understand the semantics. Consequently, global/field data is mostly ignored by ParaView. One thing that we have encountered with simulations at Sandia is that the simulation might track some global information, such as the mean of a field, and append that value to an array in the global data every time a timestep is written out. Thus, you end up with a global/field data array of length equal to the number of timesteps. The Plot Global Data Over Time filter addresses this use case and only this use case. If you want to compute a value and then plot how that value changes over time, your best approach is to write that value out to a table and then use Plot Selection Over Time to plot the value. -Ken From: Scott, W Alan Sent: Friday, March 24, 2017 12:17 PM To: Moreland, Kenneth ; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData OK, looking at your reply, I think I have a fundamental misunderstanding, and have been mixing up terms. What is a "global data" and "field data"? What's the difference? I think you are saying that if we have 43 timesteps (can.exo), any global arrays will have 43 entries (such as time or atmospheric pressure). However, field data will have a single entry (such as Title)? Below, you are setting - and resetting - the field data over and over again? Alan From: Moreland, Kenneth Sent: Thursday, March 23, 2017 4:00 PM To: Scott, W Alan >; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData I don't think Plot Global Variables Over Time works the way you think it does. This filter assumes that the global arrays contain a static array the same size as the number of time steps and then plots that with the time array on the x axis and the entries in this array in the y axis. If the size of the global variable does not equal the number of time steps, the view will show nothing. I think you really want to use Plot Selection Over Time. That you can give a value and it will iterate the pipeline over time and compute the value for each time step. Unfortunately, it looks like the filter is broken for selections on field data. It works, however, on table data, so you can write the result as that. I got what I think you want using the can data set. Here are the steps I used: 1. Load can.ex2. All variables. Apply. 2. Add the Programmable Filter. Set the output type to vtkTable (!) and use the following script: disp_y = inputs[0].PointData["DISPL"][:,1] mean_disp = mean(disp_y) output.RowData.append(mean_disp, "MEAN_DISP") 3. Select the single row shown in the spreadsheet that pops up. 4. Add Plot Selection Over Time filter. Apply. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 3:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] How do you "see" FieldData >From a user: How do you "see" FieldData variables created in the ProgrammableFilter in the PlotGlobalVariablesOverTime filter? I'm creating a FieldData variable in the ProgrammableFilter. Now I'd like to plot it over time. It isn't available as an option for me to plot, though. I see other global variables, just not this one. disp_y = inputs[0].PointData["displ_"][:,1] mean_disp = mean(disp_y) output.FieldData.append(mean_disp, "MEAN_DISP") Am I doing something wrong here? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Fri Mar 24 16:11:22 2017 From: jhaase1 at nd.edu (John Haase) Date: Fri, 24 Mar 2017 16:11:22 -0400 Subject: [Paraview] Difference in dataset for multiple variables Message-ID: Hello Paraviewers, I want to make sure my multivariable cyclic simulation has reached "steady state" so I am trying to match the corresponding timesteps and get the R^2 error. To take the difference between the two datasets, I was thinking of following the method laid out here http://paraview.markmail.org/search/?q=difference#query:difference+page:1+mid:lc6a4ss2j5hi37ps+state:results and using the ProgrammableFilter to take the difference. That works great for a single variable. However, is there a way to take the difference of all the variables in the data set? Or do I just have to have a ProgrammableFilter for each variable? Thank you for the advice Regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Mar 24 16:27:26 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 24 Mar 2017 20:27:26 +0000 Subject: [Paraview] Difference in dataset for multiple variables Message-ID: The programmable filter just runs the Python script you give it. Use Python to iterate over all the fields in your dataset. Augmenting the example in the email you reference, use something like this to iterate over all the fields: for field in inputs[0].PointData.keys(): data0 = inputs[0].PointData[field] data1 = inputs[1].PointData[field] output.PointData.append(data0-data1, field + '-diff') -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of John Haase Sent: Friday, March 24, 2017 2:11 PM To: ParaView Subject: [EXTERNAL] [Paraview] Difference in dataset for multiple variables Hello Paraviewers, I want to make sure my multivariable cyclic simulation has reached "steady state" so I am trying to match the corresponding timesteps and get the R^2 error. To take the difference between the two datasets, I was thinking of following the method laid out here http://paraview.markmail.org/search/?q=difference#query:difference+page:1+mid:lc6a4ss2j5hi37ps+state:results and using the ProgrammableFilter to take the difference. That works great for a single variable. However, is there a way to take the difference of all the variables in the data set? Or do I just have to have a ProgrammableFilter for each variable? Thank you for the advice Regards, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsivakumar at cdac.in Mon Mar 27 01:31:56 2017 From: vsivakumar at cdac.in (Dr. Sivakumar) Date: Mon, 27 Mar 2017 11:01:56 +0530 (IST) Subject: [Paraview] Map projection types in Paraview Message-ID: <766926527.11.1490592716268.JavaMail.open-xchange@webmail.cdac.in> Dear All, What are map projection system Paraview software supports? with regards Sivakumar ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexander.Stief at hs-aalen.de Tue Mar 28 11:31:28 2017 From: Alexander.Stief at hs-aalen.de (Stief, Alexander) Date: Tue, 28 Mar 2017 15:31:28 +0000 Subject: [Paraview] Switching time steps when running parallel Message-ID: <11BC40335FCF354D99B30918B180F5296B4B0028@MAIL-1.htw-aalen.de> I am using the ensight gold file format for transient results. When running Paraview in parallel mode (Auto MPI), I am unable to load any time step except the first one. Trying to load a different time step results in the error message: ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/VTKExtensions/Default/vtkPEnSightReader.cxx, line 343 vtkPEnSightGoldBinaryReader (0x30d9510): error reading geometry file ../ModelEnsight/LB_results.geo 0 ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784 vtkCompositeDataPipeline (0x30d8f40): Algorithm vtkPEnSightGoldBinaryReader(0x30d9510) returned failure for request: vtkInformation (0x31fc9a0) Debug: Off Modified Time: 96520 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 FROM_OUTPUT_PORT: 0 When I try the same without Auto MPI enabled it works perfectly. It is just that I would like to use Auto MPI because it speeds up the filters a lot. I tried with versions 5.2.0 and 5.3.0. Regards Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 28 12:02:44 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 28 Mar 2017 12:02:44 -0400 Subject: [Paraview] Switching time steps when running parallel In-Reply-To: <11BC40335FCF354D99B30918B180F5296B4B0028@MAIL-1.htw-aalen.de> References: <11BC40335FCF354D99B30918B180F5296B4B0028@MAIL-1.htw-aalen.de> Message-ID: Hi, Any chance you could share the data set? I cannot determine the problem from the error message and am not sure I can reproduce it otherwise. Thanks, Andy On Tue, Mar 28, 2017 at 11:31 AM, Stief, Alexander < Alexander.Stief at hs-aalen.de> wrote: > I am using the ensight gold file format for transient results. > > When running Paraview in parallel mode (Auto MPI), I am unable to load any > time step except the first one. > > Trying to load a different time step results in the error message: > > > > > > ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash- > linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ > VTKExtensions/Default/vtkPEnSightReader.cxx, line 343 > > vtkPEnSightGoldBinaryReader (0x30d9510): error reading geometry file > ../ModelEnsight/LB_results.geo 0 > > > > ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash- > linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/ > ExecutionModel/vtkExecutive.cxx, line 784 > > vtkCompositeDataPipeline (0x30d8f40): Algorithm > vtkPEnSightGoldBinaryReader(0x30d9510) returned failure for request: > vtkInformation (0x31fc9a0) > > Debug: Off > > Modified Time: 96520 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_DATA > > ALGORITHM_AFTER_FORWARD: 1 > > FORWARD_DIRECTION: 0 > > FROM_OUTPUT_PORT: 0 > > > > > > When I try the same without Auto MPI enabled it works perfectly. It is > just that I would like to use Auto MPI because it speeds up the filters a > lot. > > I tried with versions 5.2.0 and 5.3.0. > > > > Regards > > Alex > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Mar 28 14:37:07 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 28 Mar 2017 14:37:07 -0400 Subject: [Paraview] Switching time steps when running parallel In-Reply-To: References: <11BC40335FCF354D99B30918B180F5296B4B0028@MAIL-1.htw-aalen.de> Message-ID: Hi, I was able to reproduce this issue with a data set that Alex shared privately with me (but is ok to share publicly). I've created a bug report ( https://gitlab.kitware.com/paraview/paraview/issues/17333). Cheers, Andy ps. Alex: I've cc'ed the list so that others can follow the issue. On Tue, Mar 28, 2017 at 12:02 PM, Andy Bauer wrote: > Hi, > > Any chance you could share the data set? I cannot determine the problem > from the error message and am not sure I can reproduce it otherwise. > > Thanks, > Andy > > On Tue, Mar 28, 2017 at 11:31 AM, Stief, Alexander < > Alexander.Stief at hs-aalen.de> wrote: > >> I am using the ensight gold file format for transient results. >> >> When running Paraview in parallel mode (Auto MPI), I am unable to load >> any time step except the first one. >> >> Trying to load a different time step results in the error message: >> >> >> >> >> >> ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-lin >> ux-shared-release_opengl2_qt4_superbuild/source-paraview/ >> ParaViewCore/VTKExtensions/Default/vtkPEnSightReader.cxx, line 343 >> >> vtkPEnSightGoldBinaryReader (0x30d9510): error reading geometry file >> ../ModelEnsight/LB_results.geo 0 >> >> >> >> ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-lin >> ux-shared-release_opengl2_qt4_superbuild/source-paraview/ >> VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784 >> >> vtkCompositeDataPipeline (0x30d8f40): Algorithm >> vtkPEnSightGoldBinaryReader(0x30d9510) returned failure for request: >> vtkInformation (0x31fc9a0) >> >> Debug: Off >> >> Modified Time: 96520 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Request: REQUEST_DATA >> >> ALGORITHM_AFTER_FORWARD: 1 >> >> FORWARD_DIRECTION: 0 >> >> FROM_OUTPUT_PORT: 0 >> >> >> >> >> >> When I try the same without Auto MPI enabled it works perfectly. It is >> just that I would like to use Auto MPI because it speeds up the filters a >> lot. >> >> I tried with versions 5.2.0 and 5.3.0. >> >> >> >> Regards >> >> Alex >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Mar 28 16:24:08 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 28 Mar 2017 20:24:08 +0000 Subject: [Paraview] How do you "see" FieldData In-Reply-To: <68c46c635ec04690a31860fabf52da55@ES08AMSNLNT.srn.sandia.gov> References: <86376fae02604d629b512aec342e6d10@ES08AMSNLNT.srn.sandia.gov> <8c10e15c07dc480ea826948070b0ff4c@ES01AMSNLNT.srn.sandia.gov> <68c46c635ec04690a31860fabf52da55@ES08AMSNLNT.srn.sandia.gov> Message-ID: Thanks Ken - really good explanation. I have never understood global data, I think I do now. Alan From: Moreland, Kenneth Sent: Friday, March 24, 2017 12:35 PM To: Scott, W Alan ; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData The Exodus II file format has the concept of "global data." When this is read into ParaView/VTK, it gets placed into what vtkDataSet calls the "field data." Because of this, I tend to use the two interchangeably (and likewise so does the ParaView GUI). Personally, I prefer the term "global data" as it is more descriptive. Arrays in global/field data can be whatever you want and whatever size you want. For example, someone might want to record the total volume of the data set. That could reasonably be stored in the global/field data. Another example might be that someone wants to record the time at which a particular event occurs. This could be stored in the global/field data as an array of marked time indices. As you can see, global/field data can mean pretty much whatever you want it to mean, so you can't do much with it unless you understand the semantics. Consequently, global/field data is mostly ignored by ParaView. One thing that we have encountered with simulations at Sandia is that the simulation might track some global information, such as the mean of a field, and append that value to an array in the global data every time a timestep is written out. Thus, you end up with a global/field data array of length equal to the number of timesteps. The Plot Global Data Over Time filter addresses this use case and only this use case. If you want to compute a value and then plot how that value changes over time, your best approach is to write that value out to a table and then use Plot Selection Over Time to plot the value. -Ken From: Scott, W Alan Sent: Friday, March 24, 2017 12:17 PM To: Moreland, Kenneth >; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData OK, looking at your reply, I think I have a fundamental misunderstanding, and have been mixing up terms. What is a "global data" and "field data"? What's the difference? I think you are saying that if we have 43 timesteps (can.exo), any global arrays will have 43 entries (such as time or atmospheric pressure). However, field data will have a single entry (such as Title)? Below, you are setting - and resetting - the field data over and over again? Alan From: Moreland, Kenneth Sent: Thursday, March 23, 2017 4:00 PM To: Scott, W Alan >; paraview at paraview.org Subject: RE: [Paraview] How do you "see" FieldData I don't think Plot Global Variables Over Time works the way you think it does. This filter assumes that the global arrays contain a static array the same size as the number of time steps and then plots that with the time array on the x axis and the entries in this array in the y axis. If the size of the global variable does not equal the number of time steps, the view will show nothing. I think you really want to use Plot Selection Over Time. That you can give a value and it will iterate the pipeline over time and compute the value for each time step. Unfortunately, it looks like the filter is broken for selections on field data. It works, however, on table data, so you can write the result as that. I got what I think you want using the can data set. Here are the steps I used: 1. Load can.ex2. All variables. Apply. 2. Add the Programmable Filter. Set the output type to vtkTable (!) and use the following script: disp_y = inputs[0].PointData["DISPL"][:,1] mean_disp = mean(disp_y) output.RowData.append(mean_disp, "MEAN_DISP") 3. Select the single row shown in the spreadsheet that pops up. 4. Add Plot Selection Over Time filter. Apply. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, March 23, 2017 3:06 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] How do you "see" FieldData >From a user: How do you "see" FieldData variables created in the ProgrammableFilter in the PlotGlobalVariablesOverTime filter? I'm creating a FieldData variable in the ProgrammableFilter. Now I'd like to plot it over time. It isn't available as an option for me to plot, though. I see other global variables, just not this one. disp_y = inputs[0].PointData["displ_"][:,1] mean_disp = mean(disp_y) output.FieldData.append(mean_disp, "MEAN_DISP") Am I doing something wrong here? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rskowch at gmail.com Tue Mar 28 19:29:23 2017 From: rskowch at gmail.com (Roman Kowch) Date: Tue, 28 Mar 2017 19:29:23 -0400 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Hi Cory, Thanks for your solution! I found that ParaView crashed when I had a volume mounted that belonged to another user on the Mac workstation, and that volume denied me access. For example, if I tried: ls -l /Volumes the error stream shows "ls: volume_name: Permission denied" for each volume denying me access. After unmounting those volumes, ParaView was able to open files normally. Thanks, Roman On Mon, Mar 13, 2017 at 4:45 PM, Cory Quammen wrote: > Roman, > > Thanks for the error report, it provides some useful clues. It looks > like ParaView is crashing when collecting information about the > mounted volumes on your system. Do you have an external drive or > network file system mounted on the Mac Pro that is crashing? If so, > could you try to unmount it and see if ParaView runs as expected? > > Barring that, are there any non-Latin characters in the names of the > volumes mounted on the Mac in question? > > Thanks, > Cory > > On Sat, Mar 11, 2017 at 6:49 PM, Roman Kowch wrote: > > Sorry, I should have mentioned that I'm running ParaView on a Mac Pro > > computer, with OS X 10.11.6. The computer does not have DBaR. > > > > Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the same > > crash I'm seeing on this particular computer. Again, I could send a crash > > report if that would help. > > > > > > On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit > > wrote: > >> > >> Do you have Dell Backup and Recovery (DBaR) tools installed on your > >> system? If so, the crash may be related to an issue with DBaR at Qt 5. > >> You may need to update DBaR to the latest version. See [1] for > >> details. > >> > >> [1] > >> http://en.community.dell.com/support-forums/software-os/f/ > 3526/t/19634253 > >> > >> > >> > >> On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: > >> > Hi, > >> > > >> > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the > GUI. > >> > The > >> > application however crashes on one of my computers when I simply click > >> > "File" then "Open." It seems that the crash happens when it needs to > >> > bring > >> > up the dialog for selecting a file. It also happens if I do these menu > >> > clicks: > >> > > >> > 1. "File", "Load Window Layout" > >> > 2. "File", "Load State" > >> > 3. "File", "Save State" > >> > > >> > As you can see, the crash appears to happen whenever a directory > dialog > >> > is > >> > expected to appear. Should I send a crash report to diagnose this > >> > problem? > >> > > >> > I should also mention that on another computer, this problem does NOT > >> > appear > >> > for the same build of Paraview. The problem seems unique to a > particular > >> > computer I'm using. > >> > > >> > Regards, > >> > Roman > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Search the list archives at: http://markmail.org/search/?q=ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Mar 28 19:58:01 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 28 Mar 2017 19:58:01 -0400 Subject: [Paraview] Crash occurs after clicking "File" then "Open" In-Reply-To: References: Message-ID: Roman, Thanks for reporting back. It looks like I need to handle some errors conditions in ParaView better. I have reported this issue at https://gitlab.kitware.com/paraview/paraview/issues/17310 - Cory On Tue, Mar 28, 2017 at 7:29 PM, Roman Kowch wrote: > Hi Cory, > > Thanks for your solution! I found that ParaView crashed when I had a volume > mounted that belonged to another user on the Mac workstation, and that > volume denied me access. For example, if I tried: > > ls -l /Volumes > > the error stream shows "ls: volume_name: Permission denied" for each volume > denying me access. After unmounting those volumes, ParaView was able to open > files normally. > > Thanks, > Roman > > On Mon, Mar 13, 2017 at 4:45 PM, Cory Quammen > wrote: >> >> Roman, >> >> Thanks for the error report, it provides some useful clues. It looks >> like ParaView is crashing when collecting information about the >> mounted volumes on your system. Do you have an external drive or >> network file system mounted on the Mac Pro that is crashing? If so, >> could you try to unmount it and see if ParaView runs as expected? >> >> Barring that, are there any non-Latin characters in the names of the >> volumes mounted on the Mac in question? >> >> Thanks, >> Cory >> >> On Sat, Mar 11, 2017 at 6:49 PM, Roman Kowch wrote: >> > Sorry, I should have mentioned that I'm running ParaView on a Mac Pro >> > computer, with OS X 10.11.6. The computer does not have DBaR. >> > >> > Another Mac Pro I've used, with OS X 10.11.6, does not reproduce the >> > same >> > crash I'm seeing on this particular computer. Again, I could send a >> > crash >> > report if that would help. >> > >> > >> > On Fri, Mar 10, 2017 at 8:30 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> Do you have Dell Backup and Recovery (DBaR) tools installed on your >> >> system? If so, the crash may be related to an issue with DBaR at Qt 5. >> >> You may need to update DBaR to the latest version. See [1] for >> >> details. >> >> >> >> [1] >> >> >> >> http://en.community.dell.com/support-forums/software-os/f/3526/t/19634253 >> >> >> >> >> >> >> >> On Fri, Mar 10, 2017 at 5:32 PM, Roman Kowch wrote: >> >> > Hi, >> >> > >> >> > I've compiled Paraview from source, v. 5.3.0 RC3 using Qt5 for the >> >> > GUI. >> >> > The >> >> > application however crashes on one of my computers when I simply >> >> > click >> >> > "File" then "Open." It seems that the crash happens when it needs to >> >> > bring >> >> > up the dialog for selecting a file. It also happens if I do these >> >> > menu >> >> > clicks: >> >> > >> >> > 1. "File", "Load Window Layout" >> >> > 2. "File", "Load State" >> >> > 3. "File", "Save State" >> >> > >> >> > As you can see, the crash appears to happen whenever a directory >> >> > dialog >> >> > is >> >> > expected to appear. Should I send a crash report to diagnose this >> >> > problem? >> >> > >> >> > I should also mention that on another computer, this problem does NOT >> >> > appear >> >> > for the same build of Paraview. The problem seems unique to a >> >> > particular >> >> > computer I'm using. >> >> > >> >> > Regards, >> >> > Roman >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From fabian.wein at fau.de Wed Mar 29 11:00:34 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Wed, 29 Mar 2017 17:00:34 +0200 Subject: [Paraview] changing color of coordinate system arrows Message-ID: Is it possible to change the colors of the coordinate system arrows? The yellow one is not that clear visible on a white background. Thanks, Fabian From utkarsh.ayachit at kitware.com Wed Mar 29 11:12:05 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Mar 2017 11:12:05 -0400 Subject: [Paraview] changing color of coordinate system arrows In-Reply-To: References: Message-ID: Not currently, I am afraid. They are not exposed to be user settable. Feel free to report a issue on the issue tracker, however. It should be fairly straight forward to support. Utkarsh On Wed, Mar 29, 2017 at 11:00 AM, Fabian Wein wrote: > Is it possible to change the colors of the coordinate system arrows? The > yellow one is not that clear visible on a white background. > > Thanks, > > Fabian > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christinebeaulieu1990 at gmail.com Wed Mar 29 11:14:37 2017 From: christinebeaulieu1990 at gmail.com (Christine Beaulieu) Date: Wed, 29 Mar 2017 11:14:37 -0400 Subject: [Paraview] Error in rendering Point Sprite - vtkShader Message-ID: Hello, my name is Christine Beaulieu. I am doing a PhD at ?cole Polytechnique Montr?al. I am using Paraview to visualize results of my simulations in granular materials. I have a problem when I try to use the ?Point Spite? mode with non constant radius. When I use ?Constant Radius? for my particles, I have no problem. However, as soon as I change it for ?Radius?, I get the following error : [image: Images int?gr?es 1] I tried to install different versions (5.1, 4.1 and 4.4...) but I always get some errors (but not the same error) when I try to do this operation. With the version 5.1, Paraview simply freezes when I try to use ?Gaussian Points?. With the version 4.1, I have this error : [image: Images int?gr?es 2] I also tried to look on forums, but I didn't find any satisfactory and comprehensible answer... My operating system is Windows 10, 64-bits. Do you think you can help me? It would be very useful for my research if I could visualize properly my results... Thank you very much in advance. Have a nice day -- *Christine Beaulieu* Candidate au doctorat / PhD Candidate ?cole Polytechnique Montr?al *pearl.polymtl.ca * *www.urpei.polymtl.ca * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 69233 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 387346 bytes Desc: not available URL: From cory.quammen at kitware.com Wed Mar 29 11:22:51 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 29 Mar 2017 11:22:51 -0400 Subject: [Paraview] Error in rendering Point Sprite - vtkShader In-Reply-To: References: Message-ID: Hi Christine, It looks like you are loading the Point Sprite plugin in ParaView and are trying to use that? As of ParaView 5.1 (and maybe 5.0), you can use the Point Gaussian representation that comes built in to ParaView. Try that and see if you get similar errors. Thanks, Cory On Wed, Mar 29, 2017 at 11:14 AM, Christine Beaulieu < christinebeaulieu1990 at gmail.com> wrote: > Hello, > > my name is Christine Beaulieu. I am doing a PhD at ?cole Polytechnique > Montr?al. I am using Paraview to visualize results of my simulations in > granular materials. > > I have a problem when I try to use the ?Point Spite? mode with non > constant radius. When I use ?Constant Radius? for my particles, I have no > problem. However, as soon as I change it for ?Radius?, I get the following > error : > > [image: Images int?gr?es 1] > > I tried to install different versions (5.1, 4.1 and 4.4...) but I always > get some errors (but not the same error) when I try to do this operation. > With the version 5.1, Paraview simply freezes when I try to use ?Gaussian > Points?. With the version 4.1, I have this error : > > [image: Images int?gr?es 2] > > I also tried to look on forums, but I didn't find any satisfactory and > comprehensible answer... > > My operating system is Windows 10, 64-bits. > > Do you think you can help me? It would be very useful for my research if I > could visualize properly my results... > > Thank you very much in advance. > Have a nice day > > -- > *Christine Beaulieu* > Candidate au doctorat / PhD Candidate > ?cole Polytechnique Montr?al > > *pearl.polymtl.ca * > *www.urpei.polymtl.ca * > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 69233 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 387346 bytes Desc: not available URL: From jhaase1 at nd.edu Wed Mar 29 12:01:15 2017 From: jhaase1 at nd.edu (John Haase) Date: Wed, 29 Mar 2017 12:01:15 -0400 Subject: [Paraview] (no subject) Message-ID: Hello Paraviewers, I'm trying to integrate variables over time. I found this thread where it had been brought up previously. http://paraview.markmail.org/search/?q=integral+over+time#query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results However, when I try and open the state file, paraview crashes. So what commands do I use to do the integral over time? I'm trying to integrate a PlotSelectionOverTime filter (with row data). I'm doing this programmatically, so attached is the python script. I have so far. Regards, John R. Haase jhaase1 at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GetR2Error.py Type: application/octet-stream Size: 1614 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Mar 29 12:06:52 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Mar 2017 12:06:52 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: John, Can you send me the datafiles too (feel free to do it off the mailing list) so I can figure out what could be going wrong. Thanks Utkarsh On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: > Hello Paraviewers, > > I'm trying to integrate variables over time. I found this thread where it > had been brought up previously. > > http://paraview.markmail.org/search/?q=integral+over+time# > query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results > > However, when I try and open the state file, paraview crashes. So what > commands do I use to do the integral over time? I'm trying to integrate a > PlotSelectionOverTime filter (with row data). > > I'm doing this programmatically, so attached is the python script. I have > so far. > > Regards, > > John R. Haase > jhaase1 at nd.edu > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Wed Mar 29 12:30:43 2017 From: jhaase1 at nd.edu (John Haase) Date: Wed, 29 Mar 2017 12:30:43 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: They are very large. I believe you should be able to access them through this link https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s Regards, John R. Haase jhaase1 at nd.edu On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > John, > > Can you send me the datafiles too (feel free to do it off the mailing > list) so I can figure out what could be going wrong. > > Thanks > Utkarsh > > On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: > >> Hello Paraviewers, >> >> I'm trying to integrate variables over time. I found this thread where it >> had been brought up previously. >> >> http://paraview.markmail.org/search/?q=integral+over+time#qu >> ery:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >> >> However, when I try and open the state file, paraview crashes. So what >> commands do I use to do the integral over time? I'm trying to integrate a >> PlotSelectionOverTime filter (with row data). >> >> I'm doing this programmatically, so attached is the python script. I have >> so far. >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Mar 29 13:05:46 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Mar 2017 13:05:46 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Your script worked for me for the most part with ParaView 5.3. All I did was added a plot view to show the results (attached). If that what you were looking for? On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: > They are very large. I believe you should be able to access them through > this link > > https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> John, >> >> Can you send me the datafiles too (feel free to do it off the mailing >> list) so I can figure out what could be going wrong. >> >> Thanks >> Utkarsh >> >> On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: >> >>> Hello Paraviewers, >>> >>> I'm trying to integrate variables over time. I found this thread where >>> it had been brought up previously. >>> >>> http://paraview.markmail.org/search/?q=integral+over+time#qu >>> ery:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >>> >>> However, when I try and open the state file, paraview crashes. So what >>> commands do I use to do the integral over time? I'm trying to integrate a >>> PlotSelectionOverTime filter (with row data). >>> >>> I'm doing this programmatically, so attached is the python script. I >>> have so far. >>> >>> Regards, >>> >>> John R. Haase >>> jhaase1 at nd.edu >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GetR2Error.py Type: text/x-python Size: 1549 bytes Desc: not available URL: From jhaase1 at nd.edu Wed Mar 29 13:15:38 2017 From: jhaase1 at nd.edu (John Haase) Date: Wed, 29 Mar 2017 13:15:38 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Sorry, that's not what I wanted. I want to integrate the variable "integrateSqrVarOverSpace", over time as well. Regards, John R. Haase jhaase1 at nd.edu On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Your script worked for me for the most part with ParaView 5.3. All I did > was added a plot view to show the results (attached). If that what you were > looking for? > > On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: > >> They are very large. I believe you should be able to access them through >> this link >> >> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> John, >>> >>> Can you send me the datafiles too (feel free to do it off the mailing >>> list) so I can figure out what could be going wrong. >>> >>> Thanks >>> Utkarsh >>> >>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: >>> >>>> Hello Paraviewers, >>>> >>>> I'm trying to integrate variables over time. I found this thread where >>>> it had been brought up previously. >>>> >>>> http://paraview.markmail.org/search/?q=integral+over+time#qu >>>> ery:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >>>> >>>> However, when I try and open the state file, paraview crashes. So what >>>> commands do I use to do the integral over time? I'm trying to integrate a >>>> PlotSelectionOverTime filter (with row data). >>>> >>>> I'm doing this programmatically, so attached is the python script. I >>>> have so far. >>>> >>>> Regards, >>>> >>>> John R. Haase >>>> jhaase1 at nd.edu >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Wed Mar 29 16:30:02 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Wed, 29 Mar 2017 22:30:02 +0200 Subject: [Paraview] changing color of coordinate system arrows In-Reply-To: References: Message-ID: <994B7BF4-342E-47F0-A9D7-048607E51E33@fau.de> I opened https://gitlab.kitware.com/paraview/paraview/issues/17340 I did not see the option for ?minor enhancement?. Thanks :) Fabian > Not currently, I am afraid. They are not exposed to be user settable. Feel free to report a issue on the issue tracker, however. It should be fairly straight forward to support. > > Utkarsh > > On Wed, Mar 29, 2017 at 11:00 AM, Fabian Wein wrote: > Is it possible to change the colors of the coordinate system arrows? The yellow one is not that clear visible on a white background. > > Thanks, > > Fabian > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From jlopezfisica at ciencias.unam.mx Wed Mar 29 16:31:18 2017 From: jlopezfisica at ciencias.unam.mx (=?UTF-8?B?Sm9zw6kgTHVpcyBMw7NwZXogTMOzcGV6?=) Date: Wed, 29 Mar 2017 22:31:18 +0200 Subject: [Paraview] Problems with writing VTK in MPI Message-ID: Hi! Paraviewers, We are having problems with the output VTK files when running a Lattice Boltzmann simulation in parallel with MPI. I am not sure what could be the problem. The thing is that when executing the program in the front end there is no problem, however when sending sbatch with 64 processors the files most of the time do not write correctly. I am attaching a file and maybe you can guide me to solve the issue, warmly, Jose The files have square part that should not be there, ? rho1_t.50.vtk ?? rho1_t.0.vtk ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Wed Mar 29 16:37:04 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Wed, 29 Mar 2017 16:37:04 -0400 Subject: [Paraview] CAVE and Paraview Message-ID: Hi there! Wondering how many people have used Paraview in a CAVE mode? And if so, can you share how big of a dataset you were able to visualize with good enough frame rate? I am curious because I am struggling here to even visualize smaller datasets (like 100k points file PVTU format) with interactive frame rates in our 4 walled CAVE. I am getting poor performance. -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Mar 29 23:19:31 2017 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Thu, 30 Mar 2017 03:19:31 +0000 Subject: [Paraview] CAVE and Paraview In-Reply-To: References: Message-ID: Faiz, As per your last email, I think the problem could be related to VirtualGL and TurboVNC. Can you try running your app outside cave (either setup as two X displays or use two computer systems) without VirtualGL or TurboVNC as that would surely give you a clear indication on what is the bottleneck. I believe you are using nearly current paraview which uses OpenGL2 then my other guess would be that your LOD is not triggering, but even without that you should be able to render 100K points without much trouble on a decent graphics card. Let us know what you think of the above before we dig into it further. Thanks, On Wed, Mar 29, 2017 at 4:37 PM Faiz Abidi wrote: > Hi there! > > Wondering how many people have used Paraview in a CAVE mode? And if so, > can you share how big of a dataset you were able to visualize with good > enough frame rate? > > I am curious because I am struggling here to even visualize smaller > datasets (like 100k points file PVTU format) with interactive frame rates > in our 4 walled CAVE. I am getting poor performance. > -- > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | > +1-540-998-6636 <(540)%20998-6636> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdutta at vt.edu Thu Mar 30 08:25:39 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Thu, 30 Mar 2017 08:25:39 -0400 Subject: [Paraview] pvpython script fails on Paraview 5.0.1 Message-ID: Hi All, I have compiled Paraview 5.0.1 on ubuntu with mesa libs to run it on CPU. Also I generated a simple pvpython script from Paraview 5.0.1 GUI on my windows machine (attached) and the script runs fine there. However this script fails with my mesa compiled pvpython. =============error logs=============== Traceback (most recent call last): File "cone_clip.py", line 19, in cone1Display.SetScaleArray = [None, ''] File "/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/lib/site-packages/paraview/servermanager.py", line 307, in __setattr__ "to add this attribute.") AttributeError: Attribute SetScaleArray does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute. ============================= ? I have built the Paraview with the following options (CMakeCache.txt attached): cmake ../ -DBUILD_TESTING=OFF -DCMAKE_BUILD_TYPE=Release -DPARAVIEW_ENABLE_CATALYST=ON -DPARAVIEW_ENABLE_PYTHON=ON -DPYTHON_LIBRARY=$PYTHON_LIBRARY -DPYTHON_INCLUDE_DIR=$PYTHON_INCLUDE_DIR -DPARAVIEW_USE_MPI=ON -DMPI_HEADER_PATH=$MPI_HEADER_PATH -DCMAKE_INSTALL_PREFIX=$BD_INSTALL_PATH -DPARAVIEW_BUILD_QT_GUI=OFF -DVTK_USE_X=OFF -DOPENGL_INCLUDE_DIR=$BD_INSTALL_PATH/include -DOPENGL_gl_LIBRARY=$BD_INSTALL_PATH/lib/libOSMesa.so -DOPENGL_glu_LIBRARY=$BD_INSTALL_PATH/lib/libGLU.so -DVTK_OPENGL_HAS_OSMESA=ON -DOSMESA_INCLUDE_DIR=$BD_INSTALL_PATH/include -DOSMESA_LIBRARY=$BD_INSTALL_PATH/lib/libOSMesa.so Do I need to pass some extra parameters while building and if so what are they? All my GUI generated scripts seem to fail with similar errors. ??Thanks in advance for guidance. ? BR, Bishwajit (Bish) Dutta CpE - Grad Student Virginia Tech -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa # It was generated by CMake: /home/bd/.local/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Dependencies for the target AcceleratedAlgorithms_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Dependencies for the target AnalyzeNIfTIIO_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkzlib; //Dependencies for the target ArrowGlyph_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Build the VTK documentation BUILD_DOCUMENTATION:BOOL=OFF BUILD_EXAMPLES:BOOL=OFF //Build IceT with shared libraries. BUILD_SHARED_LIBS:BOOL=ON //Build the testing tree. BUILD_TESTING:BOOL=OFF //Build With User Defined Values BUILD_USER_DEFINED_LIBS:BOOL=OFF //Dependencies for the target CDIReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkNetCDF;general;vtkNetCDF_cxx; //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //For backwards compatibility, what version of CMake commands and // syntax should this version of CMake try to support. CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4 //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel. CMAKE_BUILD_TYPE:STRING=Release //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Fortran compiler CMAKE_Fortran_COMPILER:FILEPATH=NOTFOUND //Fortran flags CMAKE_Fortran_FLAGS:STRING= //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/home/bd/.local //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy //Path to a program. CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=ParaView //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //Thread library used. CMAKE_THREAD_LIBS:STRING=-lpthread //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Enable to build Debian packages CPACK_BINARY_DEB:BOOL=OFF //Enable to build IFW packages CPACK_BINARY_IFW:BOOL=OFF //Enable to build NSIS packages CPACK_BINARY_NSIS:BOOL=OFF //Enable to build RPM packages CPACK_BINARY_RPM:BOOL=OFF //Enable to build STGZ packages CPACK_BINARY_STGZ:BOOL=ON //Enable to build TBZ2 packages CPACK_BINARY_TBZ2:BOOL=OFF //Enable to build TGZ packages CPACK_BINARY_TGZ:BOOL=ON //Enable to build TXZ packages CPACK_BINARY_TXZ:BOOL=OFF //Enable to build TZ packages CPACK_BINARY_TZ:BOOL=ON //Enable to build RPM source packages CPACK_SOURCE_RPM:BOOL=OFF //Enable to build TBZ2 source packages CPACK_SOURCE_TBZ2:BOOL=ON //Enable to build TGZ source packages CPACK_SOURCE_TGZ:BOOL=ON //Enable to build TXZ source packages CPACK_SOURCE_TXZ:BOOL=ON //Enable to build TZ source packages CPACK_SOURCE_TZ:BOOL=ON //Enable to build ZIP source packages CPACK_SOURCE_ZIP:BOOL=OFF //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/DICOMParser //Value Computed by CMake DIY2_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/diy2/vtkdiy2 //Value Computed by CMake DIY2_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/diy2/vtkdiy2 //Path to a library. EXECINFO_LIB:FILEPATH=EXECINFO_LIB-NOTFOUND //Disable compiler warnings EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON //Path to Eigen install. Eigen_DIR:FILEPATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/SciberQuestToolKit/eigen-3.0.3/eigen-eigen-3.0.3 //Additional URL templates for the ExternalData CMake script to // look for testing data. E.g. //\nfile:///var/bigharddrive/%(algo)/%(hash) ExternalData_URL_TEMPLATES:STRING= //Dependencies for the target EyeDomeLightingView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkEyeDomeLighting;general;vtkEyeDomeLightingCS;general;vtkEyeDomeLighting; //Value Computed by CMake EyeDomeLighting_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/EyeDomeLighting //Value Computed by CMake EyeDomeLighting_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/EyeDomeLighting //Value Computed by CMake FmmMesh_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/GeodesicMeasurementPlugin/FmmMesh //Dependencies for target FmmMesh_LIB_DEPENDS:STATIC= //Value Computed by CMake FmmMesh_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/GeodesicMeasurementPlugin/FmmMesh //Git command line client GIT_EXECUTABLE:FILEPATH=GIT_EXECUTABLE-NOTFOUND //The directory containing gmvread.c, gmvread.h and gmvrayread.h GMVReader_GMVREAD_LIB_DIR:PATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Utilities/VisItBridge/databases/GMV //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Calculate minimum and maximum of data arrays in RequestInformation // calls. //\n A feature inherited from AVSucdReader, but it seems this // information is //\n never queried by ParaView. GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS:BOOL=OFF //Value Computed by CMake GeodesicMeasurementPlugin_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/GeodesicMeasurementPlugin //Value Computed by CMake GeodesicMeasurementPlugin_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/GeodesicMeasurementPlugin //Dependencies for the target GeodesicMeasurement_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;FmmMesh; //Dependencies for the target H5PartReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Value Computed by CMake HDF5_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/hdf5/vtkhdf5 //Build Static Executabless HDF5_BUILD_STATIC_EXECS:BOOL=OFF //Enable all warnings HDF5_ENABLE_ALL_WARNINGS:BOOL=OFF //Turn on debugging in all packages HDF5_ENABLE_DEBUG_APIS:BOOL=OFF //Build the Direct I/O Virtual File Driver HDF5_ENABLE_DIRECT_VFD:BOOL=ON //embed library info into executables HDF5_ENABLE_EMBEDDED_LIBINFO:BOOL=ON //Enable group five warnings HDF5_ENABLE_GROUPFIVE_WARNINGS:BOOL=OFF //Enable group four warnings HDF5_ENABLE_GROUPFOUR_WARNINGS:BOOL=OFF //Enable group one warnings HDF5_ENABLE_GROUPONE_WARNINGS:BOOL=OFF //Enable group three warnings HDF5_ENABLE_GROUPTHREE_WARNINGS:BOOL=OFF //Enable group two warnings HDF5_ENABLE_GROUPTWO_WARNINGS:BOOL=OFF //Enable group zero warnings HDF5_ENABLE_GROUPZERO_WARNINGS:BOOL=OFF //Value Computed by CMake HDF5_HL_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SRC_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //Value Computed by CMake HDF5_HL_SRC_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //CPACK - Disable packaging HDF5_NO_PACKAGES:BOOL=OFF //Package the HDF5 Library Examples Compressed File HDF5_PACK_EXAMPLES:BOOL=OFF //Value Computed by CMake HDF5_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/hdf5/vtkhdf5 //Value Computed by CMake HDF5_SRC_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/hdf5/vtkhdf5/src //Value Computed by CMake HDF5_SRC_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/hdf5/vtkhdf5/src //Enable folder grouping of projects in IDEs. HDF5_USE_FOLDERS:BOOL=ON //Value Computed by CMake ICET_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/ThirdParty/IceT/vtkicet //Sets the preferred `k' value for the radix-k algorithm. This // is the amount of simultaneous messages each process receives. // A value of 8 is generally good on most architectures, but in // others that have slower computation with respect to network // (such as BlueGene), a larger value may give better performance. ICET_MAGIC_K:STRING=8 //Sets the preferred number of times an image may be split. Some // image compositing algorithms prefer to partition the images // such that each process gets a piece. Too many partitions, though, // and you end up spending more time collecting them than you save // balancing the compositing. ICET_MAX_IMAGE_SPLIT:STRING=512 //Value Computed by CMake ICET_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ThirdParty/IceT/vtkicet //Use MPE to trace MPI communications. This is helpful for developers // trying to measure the performance of parallel compositing algorithms. ICET_USE_MPE:BOOL=OFF //Build MPI communication layer for IceT. ICET_USE_MPI:BOOL=ON //Build OpenGL support layer for IceT. ICET_USE_OPENGL:BOOL=ON //Installation directory for executables INSTALL_BIN_DIR:PATH=/home/bd/.local/bin //Installation directory for headers INSTALL_INC_DIR:PATH=/home/bd/.local/include //Installation directory for libraries INSTALL_LIB_DIR:PATH=/home/bd/.local/lib //Installation directory for manual pages INSTALL_MAN_DIR:PATH=/home/bd/.local/share/man //Installation directory for pkgconfig (.pc) files INSTALL_PKGCONFIG_DIR:PATH=/home/bd/.local/share/pkgconfig //Dependencies for the target IceTCore_LIB_DEPENDS:STATIC=general;m;general;m; //Dependencies for the target IceTGL_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake LZ4_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/ThirdParty/lz4/vtklz4 //Value Computed by CMake LZ4_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ThirdParty/lz4/vtklz4 //Executable for running MPI programs. MPIEXEC:FILEPATH=MPIEXEC-NOTFOUND //Maximum number of processors available to run MPI applications. MPIEXEC_MAX_NUMPROCS:STRING=2 //Flag used by MPI to specify the number of processes for MPIEXEC; // the next option will be the number of processes. MPIEXEC_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIEXEC. MPIEXEC_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by MPIEXEC. MPIEXEC_PREFLAGS:STRING= //Path to a program. MPI_CXX_COMPILER:FILEPATH=/usr/bin/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING= //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=/usr/lib/libmpi_cxx.so;/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= //Path to a program. MPI_C_COMPILER:FILEPATH=/usr/bin/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING= //MPI C include path MPI_C_INCLUDE_PATH:STRING=/usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi //MPI C libraries to link against MPI_C_LIBRARIES:STRING=/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so //MPI C linking flags MPI_C_LINK_FLAGS:STRING= //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so //MPI library to link against MPI_LIBRARY:FILEPATH=/usr/lib/libmpi_cxx.so //Poisson Surface reconstruction from unorganized points Module_PoissonReconstruction:BOOL=OFF //Request building Pygments Module_Pygments:BOOL=OFF //Request building VisItLib Module_VisItLib:BOOL=OFF //A collection of examples that illustrate how to use VTK. Module_WikiExamples:BOOL=OFF //Request building pqApplicationComponents Module_pqApplicationComponents:BOOL=OFF //Request building pqComponents Module_pqComponents:BOOL=OFF //Request building pqCore Module_pqCore:BOOL=OFF //Request building pqDeprecated Module_pqDeprecated:BOOL=OFF //Request building pqPython Module_pqPython:BOOL=OFF //Request building pqWidgets Module_pqWidgets:BOOL=OFF //Request building vtkAcceleratorsDax Module_vtkAcceleratorsDax:BOOL=OFF //Request building vtkAcceleratorsPiston Module_vtkAcceleratorsPiston:BOOL=OFF //Slicer additions to vtk Module_vtkAddon:BOOL=OFF //Request building vtkCosmoHaloFinder Module_vtkCosmoHaloFinder:BOOL=OFF //Dicom classes and utilities Module_vtkDICOM:BOOL=OFF //Request building vtkDomainsMicroscopy Module_vtkDomainsMicroscopy:BOOL=OFF //Request building vtkFiltersMatlab Module_vtkFiltersMatlab:BOOL=OFF //Request building vtkFiltersReebGraph Module_vtkFiltersReebGraph:BOOL=OFF //Request building vtkFiltersSMP Module_vtkFiltersSMP:BOOL=OFF //Request building vtkFiltersSelection Module_vtkFiltersSelection:BOOL=OFF //Request building vtkFiltersStatisticsGnuR Module_vtkFiltersStatisticsGnuR:BOOL=OFF //Request building vtkGUISupportQt Module_vtkGUISupportQt:BOOL=OFF //Request building vtkGUISupportQtOpenGL Module_vtkGUISupportQtOpenGL:BOOL=OFF //Request building vtkGUISupportQtSQL Module_vtkGUISupportQtSQL:BOOL=OFF //Request building vtkGUISupportQtWebkit Module_vtkGUISupportQtWebkit:BOOL=OFF //Request building vtkGeovisCore Module_vtkGeovisCore:BOOL=OFF //Request building vtkIOADIOS Module_vtkIOADIOS:BOOL=OFF //Request building vtkIOFFMPEG Module_vtkIOFFMPEG:BOOL=OFF //Request building vtkIOGDAL Module_vtkIOGDAL:BOOL=OFF //Request building vtkIOGeoJSON Module_vtkIOGeoJSON:BOOL=OFF //Request building vtkIOMINC Module_vtkIOMINC:BOOL=OFF //Request building vtkIOMySQL Module_vtkIOMySQL:BOOL=OFF //Request building vtkIOODBC Module_vtkIOODBC:BOOL=OFF //Request building vtkIOPostgreSQL Module_vtkIOPostgreSQL:BOOL=OFF //Request building vtkIOSQL Module_vtkIOSQL:BOOL=OFF //Request building vtkIOTecplotTable Module_vtkIOTecplotTable:BOOL=OFF //Request building vtkIOVideo Module_vtkIOVideo:BOOL=OFF //Request building vtkIOVisItBridge Module_vtkIOVisItBridge:BOOL=OFF //Request building vtkIOXdmf3 Module_vtkIOXdmf3:BOOL=OFF //Request building vtkImagingMath Module_vtkImagingMath:BOOL=OFF //Request building vtkImagingStatistics Module_vtkImagingStatistics:BOOL=OFF //Request building vtkImagingStencil Module_vtkImagingStencil:BOOL=OFF //Request building vtkInfovisBoost Module_vtkInfovisBoost:BOOL=OFF //Request building vtkInfovisBoostGraphAlgorithms Module_vtkInfovisBoostGraphAlgorithms:BOOL=OFF //Request building vtkInfovisLayout Module_vtkInfovisLayout:BOOL=OFF //Request building vtkInfovisParallel Module_vtkInfovisParallel:BOOL=OFF //Request building vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver:BOOL=OFF //Request building vtkPVVTKExtensionsCGNSReader Module_vtkPVVTKExtensionsCGNSReader:BOOL=OFF //Request building vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF //Request building vtkParaViewWebDocumentation Module_vtkParaViewWebDocumentation:BOOL=OFF //Point Cloud processing in VTK Module_vtkPointCloud:BOOL=OFF //Request building vtkRenderingExternal Module_vtkRenderingExternal:BOOL=OFF //Request building vtkRenderingFreeTypeFontConfig Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF //Request building vtkRenderingImage Module_vtkRenderingImage:BOOL=OFF //Request building vtkRenderingOSPRay Module_vtkRenderingOSPRay:BOOL=OFF //Request building vtkRenderingQt Module_vtkRenderingQt:BOOL=OFF //Request building vtkRenderingSceneGraph Module_vtkRenderingSceneGraph:BOOL=OFF //Request building vtkRenderingTk Module_vtkRenderingTk:BOOL=OFF //Request building vtkTclTk Module_vtkTclTk:BOOL=OFF //Request building vtkTestingGenericBridge Module_vtkTestingGenericBridge:BOOL=OFF //Request building vtkTestingIOSQL Module_vtkTestingIOSQL:BOOL=OFF //Request building vtkUtilitiesBenchmarks Module_vtkUtilitiesBenchmarks:BOOL=OFF //Request building vtkUtilitiesColorSeriesToXML Module_vtkUtilitiesColorSeriesToXML:BOOL=OFF //Request building vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON:BOOL=OFF //Request building vtkViewsGeovis Module_vtkViewsGeovis:BOOL=OFF //Request building vtkViewsInfovis Module_vtkViewsInfovis:BOOL=OFF //Request building vtkViewsQt Module_vtkViewsQt:BOOL=OFF //Request building vtkWebApplications Module_vtkWebApplications:BOOL=OFF //Request building vtkWebInstall Module_vtkWebInstall:BOOL=OFF //Request building vtkWrappingJava Module_vtkWrappingJava:BOOL=OFF //Request building vtkWrappingPythonCore Module_vtkWrappingPythonCore:BOOL=ON //Request building vtkWrappingTcl Module_vtkWrappingTcl:BOOL=OFF //Request building vtkglew Module_vtkglew:BOOL=OFF //Request building vtklibproj4 Module_vtklibproj4:BOOL=OFF //Request building vtkqttesting Module_vtkqttesting:BOOL=OFF //Request building vtksqlite Module_vtksqlite:BOOL=OFF //Request building vtkxdmf3 Module_vtkxdmf3:BOOL=OFF //Dependencies for the target Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Specify default maximum number of elements in the file chunk // cache chunk for HDF5 files (should be prime number). NETCDF4_CHUNK_CACHE_NELEMS:STRING=1009 //Specify default file chunk cache preemption policy for HDF5 files // (a number between 0 and 1, inclusive). NETCDF4_CHUNK_CACHE_PREEMPTION:STRING=0.75 //Specify default file cache chunk size for HDF5 files in bytes. NETCDF4_CHUNK_CACHE_SIZE:STRING=4194304 //Specify the number of chunks to store in default per-variable // cache. NETCDF4_DEFAULT_CHUNKS_IN_CACHE:STRING=10 //Specify default size of chunks in bytes. NETCDF4_DEFAULT_CHUNK_SIZE:STRING=4194304 //Specify maximum size (in bytes) for the default per-var chunk // cache. NETCDF4_MAX_DEFAULT_CACHE_SIZE:STRING=67108864 //Disable compiler warnings NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON //Build netcdf C++ API NETCDF_ENABLE_CXX:BOOL=ON //Dependencies for the target NonOrthogonalSource_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //No help, variable specified on the command line. OPENGL_INCLUDE_DIR:UNINITIALIZED=/home/bd/.local//include //No help, variable specified on the command line. OPENGL_gl_LIBRARY:UNINITIALIZED=/home/bd/.local//lib/libOSMesa.so //No help, variable specified on the command line. OPENGL_glu_LIBRARY:UNINITIALIZED=/home/bd/.local//lib/libGLU.so //No help, variable specified on the command line. OSMESA_INCLUDE_DIR:UNINITIALIZED=/home/bd/.local//include //No help, variable specified on the command line. OSMESA_LIBRARY:UNINITIALIZED=/home/bd/.local//lib/libOSMesa.so //Load AcceleratedAlgorithms Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF //Load AnalyzeNIfTIIO Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO:BOOL=OFF //Load ArrowGlyph Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph:BOOL=OFF //Load CDIReader Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_CDIReader:BOOL=OFF //Load EyeDomeLighting Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting:BOOL=OFF //Load GMVReader Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_GMVReader:BOOL=OFF //Load GeodesicMeasurement Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement:BOOL=OFF //Load H5PartReader Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_H5PartReader:BOOL=OFF //Load Moments Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_Moments:BOOL=OFF //Load NonOrthogonalSource Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource:BOOL=OFF //Load PacMan Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_PacMan:BOOL=OFF //Load PointSprite Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_PointSprite:BOOL=OFF //Load RGBZView Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_RGBZView:BOOL=OFF //Load SLACTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SLACTools:BOOL=OFF //Load SciberQuestToolKit Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SciberQuestToolKit:BOOL=OFF //Load SierraPlotTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools:BOOL=OFF //Load StreamingParticles Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles:BOOL=OFF //Load SurfaceLIC Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC:BOOL=OFF //Load ThickenLayeredCells Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells:BOOL=OFF //Load UncertaintyRendering Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_UncertaintyRendering:BOOL=OFF //Build Adaptors for various simulation codes PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF //Build AcceleratedAlgorithms Plugin PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=TRUE //Build AdiosReader Plugin PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=FALSE //Build AnalyzeNIfTIIO Plugin PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=TRUE //Build ArrowGlyph Plugin PARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=TRUE //Build CDIReader Plugin PARAVIEW_BUILD_PLUGIN_CDIReader:BOOL=TRUE //Build EyeDomeLighting Plugin PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=TRUE //Build GMVReader Plugin PARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=TRUE //Build GeodesicMeasurement Plugin PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=TRUE //Build H5PartReader Plugin PARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=TRUE //Build InSituExodus Plugin PARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE //Build MantaView Plugin PARAVIEW_BUILD_PLUGIN_MantaView:BOOL=FALSE //Build Moments Plugin PARAVIEW_BUILD_PLUGIN_Moments:BOOL=TRUE //Build NonOrthogonalSource Plugin PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=TRUE //Build PacMan Plugin PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=TRUE //Build PointSprite Plugin PARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=TRUE //Build RGBZView Plugin PARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=TRUE //Build SLACTools Plugin PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=TRUE //Build SciberQuestToolKit Plugin PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=TRUE //Build SierraPlotTools Plugin PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=TRUE //Build StreamingParticles Plugin PARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=TRUE //Build SurfaceLIC Plugin PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE //Build ThickenLayeredCells Plugin PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells:BOOL=TRUE //Build UncertaintyRendering Plugin PARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=TRUE //Build VaporPlugin Plugin PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE //Enable ParaView Qt-based client PARAVIEW_BUILD_QT_GUI:BOOL=OFF //Enable/Disable web documentation PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF //Exclude test data download from default 'all' target. PARAVIEW_DATA_EXCLUDE_FROM_ALL:BOOL=OFF //Local directory holding ExternalData objects in the layout %(algo)/%(hash). PARAVIEW_DATA_STORE:PATH= //Enable Catalyst CoProcessing modules PARAVIEW_ENABLE_CATALYST:BOOL=ON //Enable the CGNS file reader PARAVIEW_ENABLE_CGNS:BOOL=OFF //Build ParaView command-line tools PARAVIEW_ENABLE_COMMANDLINE_TOOLS:BOOL=ON //Build ParaView with CosmoTools VTK Extensions PARAVIEW_ENABLE_COSMOTOOLS:BOOL=OFF //Enable FFMPEG Support. PARAVIEW_ENABLE_FFMPEG:BOOL=OFF //Enable/Disable Python scripting support PARAVIEW_ENABLE_MATPLOTLIB:BOOL=ON //Enable/Disable Python scripting support PARAVIEW_ENABLE_PYTHON:BOOL=ON //Build ParaView with Qt support (without GUI) PARAVIEW_ENABLE_QT_SUPPORT:BOOL=OFF //Enables markers in the spyplot reader PARAVIEW_ENABLE_SPYPLOT_MARKERS:BOOL=ON //Turn off to avoid ParaView depending on all used VTK modules. PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE //Enable/Disable web support PARAVIEW_ENABLE_WEB:BOOL=ON //Enable Xdmf3 support (requires Boost). PARAVIEW_ENABLE_XDMF3:BOOL=OFF //Semi-colon seperated paths to extrenal plugin directories. PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING= //A list of plugins to autoload (but not built as part of ParaView // itself) PARAVIEW_EXTRA_EXTERNAL_PLUGINS:STRING= //Freeze Python packages/modules into the application. PARAVIEW_FREEZE_PYTHON:BOOL=OFF //Initialize MPI on client-processes by default. Can be overridden // using command line arguments PARAVIEW_INITIALIZE_MPI_ON_CLIENT:BOOL=OFF //When enabled, "make install" will install development files PARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=OFF //Extra paths to search for plugins PARAVIEW_PLUGIN_LOADER_PATHS:STRING= //Link to Cray ATP library to enable debug features on Cray Systems PARAVIEW_USE_ATP:BOOL=OFF //Build ParaView with Dax many-core filters PARAVIEW_USE_DAX:BOOL=OFF //Enable IceT (needed for parallel rendering) PARAVIEW_USE_ICE_T:BOOL=ON //Enable MPI support for parallel computing PARAVIEW_USE_MPI:BOOL=ON //Use MPI synchronous-send commands for communication PARAVIEW_USE_MPI_SSEND:BOOL=OFF //Build ParaView with OSPRay Ray Traced rendering PARAVIEW_USE_OSPRAY:BOOL=OFF //Build ParaView with Piston GPGPU filters PARAVIEW_USE_PISTON:BOOL=OFF //If enabled, Python bindings will back the ClientServer wrapping // implementation PARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF //Build ParaView with VisIt readers. PARAVIEW_USE_VISITBRIDGE:BOOL=OFF //Disable compiler warnings PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON //Command to run after a failed test to cleanup processes. Example: // "killall -9 rsh paraview" PV_TEST_CLEAN_COMMAND:STRING= //Node which serves as the client node, used to connect from the // server side in reverse connection mode. PV_TEST_CLIENT:STRING=localhost //Command to run before a test begins. Multiple commands are separated // by ';'. PV_TEST_INIT_COMMAND:STRING= //Use random port numbers when testing client-server configurations. PV_TEST_USE_RANDOM_PORTS:BOOL=ON //Add module mpi4py.MPE PYTHON_ENABLE_MODULE_mpi4py.MPE:BOOL=ON //Add module mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI:BOOL=ON //Add module mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl:BOOL=ON //Path to a program. PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2 //Extra libraries to link when linking to python (such as "z" for // zlib). Separate multiple libraries with semicolons. PYTHON_EXTRA_LIBS:STRING= //Path to a file. PYTHON_INCLUDE_DIR:PATH=/usr/include/python2.7 //Path to a library. PYTHON_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libpython2.7.so //Add module mpi4py.MPE shared PYTHON_MODULE_mpi4py.MPE_BUILD_SHARED:BOOL=ON //Add module mpi4py.MPI shared PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED:BOOL=ON //Add module mpi4py.dl shared PYTHON_MODULE_mpi4py.dl_BUILD_SHARED:BOOL=ON //Utility library needed for vtkpython PYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libutil.so //Dependencies for the target PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Value Computed by CMake ParaView_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh //Value Computed by CMake PointSpritePlugin_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/PointSprite //Value Computed by CMake PointSpritePlugin_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/PointSprite //Dependencies for the target PointSprite_Plugin_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteGraphicsCS;general;vtkPointSpriteRendering;general;vtkPointSpriteRenderingCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteRendering; //Value Computed by CMake RGBZView_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/RGBZView //Dependencies for the target RGBZView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Value Computed by CMake RGBZView_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/RGBZView //Dependencies for the target SLACTools_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Enable CUDA accelerated filters. SQTK_CUDA:BOOL=OFF //Enable debug output to stderr. SQTK_DEBUG:BOOL=OFF //Explicitly disable SurfaceLIC plugin ctests SURFACELIC_PLUGIN_TESTING:BOOL=ON //Value Computed by CMake SciberQuestToolKit_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/Plugins/SciberQuestToolKit //Dependencies for the target SciberQuestToolKit_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkSciberQuest;general;vtkSciberQuestCS;general;vtkFiltersFlowPaths;general;vtkSciberQuest;general;vtkPVServerManagerDefault;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Value Computed by CMake SciberQuestToolKit_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/Plugins/SciberQuestToolKit //Dependencies for the target StreamingParticles_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Dependencies for the target SurfaceLIC_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Dependencies for the target ThickenLayeredCells_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Use HIDDEN visibility support if available. USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON //Value Computed by CMake VPIC_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/VPIC //Value Computed by CMake VTKEXPAT_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKEXPAT_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKFREETYPE_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFREETYPE_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/oggtheora/vtkoggtheora //Disable assemby optimizations VTKOGGTHEORA_DISABLE_ASM:BOOL=OFF //Disable the use of floating point code in theora VTKOGGTHEORA_DISABLE_FLOAT:BOOL=OFF //Additional linker flags for vtkoggtheora when building as a shared // library VTKOGGTHEORA_SHARED_LINKER_FLAGS:STRING=-Wl,--version-script="/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/oggtheora/vtkoggtheora //Value Computed by CMake VTKPNG_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKPNG_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKTIFF_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake VTKTIFF_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/tiff/vtktiff //Build all vtkObject derived classes with object factory new methods. VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF //Build VTK for Android VTK_ANDROID_BUILD:BOOL=OFF //Value Computed by CMake VTK_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK //Request to build all modules VTK_BUILD_ALL_MODULES:BOOL=OFF //Local directory holding ExternalData objects in the layout %(algo)/%(hash). VTK_DATA_STORE:PATH= //Build leak checking support into VTK. VTK_DEBUG_LEAKS:BOOL=OFF //Include array-of-structs vtkDataArray subclasses in dispatcher. VTK_DISPATCH_AOS_ARRAYS:BOOL=ON //Include struct-of-arrays vtkDataArray subclasses in dispatcher. VTK_DISPATCH_SOA_ARRAYS:BOOL=OFF //Include vtkTypedDataArray subclasses (e.g. old mapped arrays) // in dispatcher. VTK_DISPATCH_TYPED_ARRAYS:BOOL=OFF //Index of the EGL device (graphics card) to use. VTK_EGL_DEVICE_INDEX:STRING=0 //Build VTK using kits instead of modules. VTK_ENABLE_KITS:BOOL=OFF //Enable vtkpython and pvtkpython binaries VTK_ENABLE_VTKPYTHON:BOOL=ON //Add compiler flags to do stricter checking when building debug. VTK_EXTRA_COMPILER_WARNINGS:BOOL=OFF //Do not download source code or data from the network VTK_FORBID_DOWNLOADS:BOOL=OFF //Location of the OpenGL extensions header file (glext.h). VTK_GLEXT_FILE:FILEPATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/ParseOGLExt/headers/glxext.h //Request building Imaging modules VTK_Group_Imaging:BOOL=OFF //Request building MPI modules VTK_Group_MPI:BOOL=OFF //Request building ParaViewCore modules VTK_Group_ParaViewCore:BOOL=ON //Request building ParaViewQt modules VTK_Group_ParaViewQt:BOOL=OFF //Request building ParaViewRendering modules VTK_Group_ParaViewRendering:BOOL=ON //Request building Qt modules VTK_Group_Qt:BOOL=OFF //Request building Rendering modules VTK_Group_Rendering:BOOL=OFF //Request building of all stand alone modules (no external dependencies // required) VTK_Group_StandAlone:BOOL=OFF //Request building Tk modules VTK_Group_Tk:BOOL=OFF //Request building Views modules VTK_Group_Views:BOOL=OFF //Request building Web modules VTK_Group_Web:BOOL=OFF //Enable buggy OpenGL drivers for testing. VTK_IGNORE_GLDRIVER_BUGS:BOOL=OFF //Build vtk.framework for iOS VTK_IOS_BUILD:BOOL=OFF //Remove all legacy code completely. VTK_LEGACY_REMOVE:BOOL=OFF //Silence all legacy code messages. VTK_LEGACY_SILENT:BOOL=OFF //Specify if linker warnings must be considered as errors. VTK_LINKER_FATAL_WARNINGS:BOOL=OFF //Should all modules build instantiators VTK_MAKE_INSTANTIATORS:BOOL=OFF //Max number of threads vktMultiThreader will allocate. VTK_MAX_THREADS:STRING=64 //Disable Python Threads support VTK_NO_PYTHON_THREADS:BOOL=ON //The OpenGL library being used supports off screen Mesa calls VTK_OPENGL_HAS_OSMESA:BOOL=ON //Python version to use: 2, 2.x, 3, 3.x, or empty VTK_PYTHON_VERSION:STRING=2 //enable parallel timers for the 2d line integral convolution VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER:BOOL=OFF //enable parallel timers for the surface lic painter VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER:BOOL=OFF //Choose the rendering backend. VTK_RENDERING_BACKEND:STRING=OpenGL //Enable OpenGL error check and report VTK_REPORT_OPENGL_ERRORS:BOOL=ON //Enable OpenGL error check and reporting in non-debug builds. VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS:BOOL=OFF //Which multi-threaded parallelism implementation to use. Options // are Sequential, OpenMP or TBB VTK_SMP_IMPLEMENTATION_TYPE:STRING=Sequential //Value Computed by CMake VTK_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK //Build VTK with 64 bit ids VTK_USE_64BIT_IDS:BOOL=ON //Build VTK using C++11 features (if available) VTK_USE_CXX11_FEATURES:BOOL=OFF //Use GCC visibility support if available. VTK_USE_GCC_VISIBILITY:BOOL=OFF //Enable tests requiring "large" data VTK_USE_LARGE_DATA:BOOL=OFF //Use off screen calls by default VTK_USE_OFFSCREEN:BOOL=OFF //Use EGL for OpenGL client API for offscreen rendering. VTK_USE_OFFSCREEN_EGL:BOOL=OFF //Use system 'autobahn' Python package VTK_USE_SYSTEM_AUTOBAHN:BOOL=OFF //Use system-installed diy2 VTK_USE_SYSTEM_DIY2:BOOL=OFF //Use system-installed EXPAT VTK_USE_SYSTEM_EXPAT:BOOL=OFF //Use system-installed Freetype VTK_USE_SYSTEM_FREETYPE:BOOL=OFF //Use system-installed GL2PS VTK_USE_SYSTEM_GL2PS:BOOL=OFF //do not use a system glew VTK_USE_SYSTEM_GLEW:BOOL=OFF //Use system-installed HDF5 VTK_USE_SYSTEM_HDF5:BOOL=OFF //Use system-installed icet VTK_USE_SYSTEM_ICET:BOOL=OFF //Use system-installed JPEG VTK_USE_SYSTEM_JPEG:BOOL=OFF //Use system-installed JsonCpp VTK_USE_SYSTEM_JSONCPP:BOOL=OFF //Use the system's libraries by default. VTK_USE_SYSTEM_LIBRARIES:BOOL=OFF //Use system-installed LibXml2 VTK_USE_SYSTEM_LIBXML2:BOOL=OFF //Use system-installed LZ4 VTK_USE_SYSTEM_LZ4:BOOL=OFF //Use system 'mpi4py' Python package VTK_USE_SYSTEM_MPI4PY:BOOL=OFF //Use system-installed NetCDF VTK_USE_SYSTEM_NETCDF:BOOL=OFF //Use system-installed OGGTHEORA VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF //Use system-installed PNG VTK_USE_SYSTEM_PNG:BOOL=OFF //Use system-installed Protobuf VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF //Use system-installed pugixml VTK_USE_SYSTEM_PUGIXML:BOOL=OFF //Use system 'six' Python Module VTK_USE_SYSTEM_SIX:BOOL=OFF //Use system-installed TIFF VTK_USE_SYSTEM_TIFF:BOOL=OFF //Use system 'twisted' Python package VTK_USE_SYSTEM_TWISTED:BOOL=OFF //Use system-installed xdmf2 VTK_USE_SYSTEM_XDMF2:BOOL=OFF //Use system-installed ZLIB VTK_USE_SYSTEM_ZLIB:BOOL=OFF //Use system 'zope' Python package VTK_USE_SYSTEM_ZOPE:BOOL=OFF //Use TDx interaction devices VTK_USE_TDX:BOOL=OFF //Build VTK with Tk support VTK_USE_TK:BOOL=OFF //Use X for VTK render windows VTK_USE_X:BOOL=OFF //Build VPIC with MPI VTK_VPIC_USE_MPI:BOOL=ON //If enabled, vtkArrayDispatch will print a warning when a dispatch // fails. VTK_WARN_ON_DISPATCH_FAILURE:BOOL=OFF //Location of the WGL extensions header file (wglext.h). VTK_WGLEXT_FILE:FILEPATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Wrapping/Tools/hints //Should VTK Java wrapping be built? VTK_WRAP_JAVA:BOOL=OFF //Should VTK Tcl wrapping be built? VTK_WRAP_TCL:BOOL=OFF //Build Xdmf with MPI VTK_XDMF_USE_MPI:BOOL=OFF //XDMF should use MPI XDMF_BUILD_MPI:BOOL=OFF //XDMF has Network Distributed Global Memory (NDGM) XDMF_HAS_NDGM:BOOL=OFF //Path to a file. XDMF_HAVE_FCNTL:PATH=/usr/include //Path to a file. XDMF_HAVE_MMAN:PATH=XDMF_HAVE_MMAN-NOTFOUND //Path to a file. XDMF_HAVE_NETINET:PATH=/usr/include/netinet //Use bzip2 XDMF_USE_BZIP2:BOOL=OFF //Build GZip Compression XDMF_USE_GZIP:BOOL=OFF //Build Support for MySQL DataItems XDMF_USE_MYSQL:BOOL=OFF //Value Computed by CMake alglib_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/alglib //Dependencies for the target mpi4py.MPE_LIB_DEPENDS:STATIC=general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target mpi4py.MPI_LIB_DEPENDS:STATIC=general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;dl; //Dependencies for the target mpi4py.dl_LIB_DEPENDS:STATIC=general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;dl; //Value Computed by CMake mpi4py_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake mpi4py_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake netcdf_cxx_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_cxx_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Dependencies for the target pmpi-mpe_LIB_DEPENDS:STATIC=general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target pmpi-vt-hyb_LIB_DEPENDS:STATIC=general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target pmpi-vt-mpi_LIB_DEPENDS:STATIC=general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target pmpi-vt_LIB_DEPENDS:STATIC=general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/ThirdParty/protobuf/vtkprotobuf //Dependencies for the target protobuf_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ThirdParty/protobuf/vtkprotobuf //Value Computed by CMake verdict_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/verdict/vtkverdict //Dependencies for the target vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD; //Dependencies for the target vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtksys;general;vtkCommonColor;general;vtkInfovisCore; //Dependencies for the target vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;vtkPythonInterpreter;general;vtkWrappingPythonCore; //Dependencies for the target vtkCommonColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD; //Dependencies for the target vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonDataModel; //Dependencies for the target vtkCommonComputationalGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD; //Dependencies for the target vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem; //Dependencies for the target vtkCommonCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore; //Dependencies for the target vtkCommonCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCore; //Dependencies for the target vtkCommonCorePython_LIB_DEPENDS:STATIC=general;vtkCommonCorePythonD; //Dependencies for the target vtkCommonCore_LIB_DEPENDS:STATIC=general;vtksys;general;-lpthread; //Dependencies for the target vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel; //Dependencies for the target vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkCommonDataModel; //Dependencies for the target vtkCommonDataModelPython_LIB_DEPENDS:STATIC=general;vtkCommonDataModelPythonD; //Dependencies for the target vtkCommonDataModel_LIB_DEPENDS:STATIC=general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys; //Dependencies for the target vtkCommonExecutionModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD; //Dependencies for the target vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonDataModel; //Dependencies for the target vtkCommonMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMath; //Dependencies for the target vtkCommonMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMath; //Dependencies for the target vtkCommonMathPython_LIB_DEPENDS:STATIC=general;vtkCommonMathPythonD; //Dependencies for the target vtkCommonMath_LIB_DEPENDS:STATIC=general;vtkCommonCore; //Dependencies for the target vtkCommonMiscCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD; //Dependencies for the target vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonMath; //Dependencies for the target vtkCommonSystemCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonSystem; //Dependencies for the target vtkCommonSystemPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystem; //Dependencies for the target vtkCommonSystemPython_LIB_DEPENDS:STATIC=general;vtkCommonSystemPythonD; //Dependencies for the target vtkCommonSystem_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;general;-lpthread; //Dependencies for the target vtkCommonTransformsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonTransforms; //Dependencies for the target vtkCommonTransformsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransforms; //Dependencies for the target vtkCommonTransformsPython_LIB_DEPENDS:STATIC=general;vtkCommonTransformsPythonD; //Dependencies for the target vtkCommonTransforms_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath; //Dependencies for target vtkDICOMParser_LIB_DEPENDS:STATIC= //Dependencies for the target vtkDomainsChemistryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOXMLPythonD;general;vtkRenderingCorePythonD;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD; //Dependencies for the target vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkIOXML;general;vtkFiltersSources; //Value Computed by CMake vtkExodus2_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/exodusII/vtkexodusII //Dependencies for the target vtkEyeDomeLightingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkEyeDomeLighting; //Dependencies for the target vtkEyeDomeLighting_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkParallelCorePythonD;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD; //Dependencies for the target vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkParallelCore; //Dependencies for the target vtkFiltersCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersCore; //Dependencies for the target vtkFiltersCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCore; //Dependencies for the target vtkFiltersCorePython_LIB_DEPENDS:STATIC=general;vtkFiltersCorePythonD; //Dependencies for the target vtkFiltersCore_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersExtractionCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersExtraction; //Dependencies for the target vtkFiltersExtractionPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersExtraction; //Dependencies for the target vtkFiltersExtractionPython_LIB_DEPENDS:STATIC=general;vtkFiltersExtractionPythonD; //Dependencies for the target vtkFiltersExtraction_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersFlowPaths; //Dependencies for the target vtkFiltersFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD;general;vtkFiltersFlowPaths; //Dependencies for the target vtkFiltersFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPathsPythonD; //Dependencies for the target vtkFiltersFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkIOCore; //Dependencies for the target vtkFiltersGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD; //Dependencies for the target vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersCore; //Dependencies for the target vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPython_LIB_DEPENDS:STATIC=general;vtkFiltersGenericPythonD; //Dependencies for the target vtkFiltersGeneric_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersSources; //Dependencies for the target vtkFiltersGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD; //Dependencies for the target vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkFiltersCore; //Dependencies for the target vtkFiltersHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHybrid; //Dependencies for the target vtkFiltersHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkFiltersHybrid; //Dependencies for the target vtkFiltersHybridPython_LIB_DEPENDS:STATIC=general;vtkFiltersHybridPythonD; //Dependencies for the target vtkFiltersHybrid_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkImagingSources;general;vtkRenderingCore; //Dependencies for the target vtkFiltersHyperTreeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD; //Dependencies for the target vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD; //Dependencies for the target vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkImagingGeneral;general;vtkImagingSources; //Dependencies for the target vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPython_LIB_DEPENDS:STATIC=general;vtkFiltersModelingPythonD; //Dependencies for the target vtkFiltersModeling_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkFiltersSources; //Dependencies for the target vtkFiltersParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallel; //Dependencies for the target vtkFiltersParallelDIY2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelDIY2; //Dependencies for the target vtkFiltersParallelDIY2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelDIY2; //Dependencies for the target vtkFiltersParallelDIY2Python_LIB_DEPENDS:STATIC=general;vtkFiltersParallelDIY2PythonD; //Dependencies for the target vtkFiltersParallelDIY2_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersCore;general;vtkParallelMPI;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPathsPythonD; //Dependencies for the target vtkFiltersParallelFlowPaths_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersFlowPaths;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD; //Dependencies for the target vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeometry;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD; //Dependencies for the target vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkImagingCore;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelMPI; //Dependencies for the target vtkFiltersParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelMPI; //Dependencies for the target vtkFiltersParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPIPythonD; //Dependencies for the target vtkFiltersParallelMPI_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkFiltersParallel; //Dependencies for the target vtkFiltersParallelPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelPythonD; //Dependencies for the target vtkFiltersParallelStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelStatistics; //Dependencies for the target vtkFiltersParallelStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelStatistics; //Dependencies for the target vtkFiltersParallelStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatisticsPythonD; //Dependencies for the target vtkFiltersParallelStatistics_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersStatistics;general;vtkParallelCore;general;vtkalglib; //Dependencies for the target vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkParallelCore;general;vtkRenderingCore; //Dependencies for the target vtkFiltersPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPython_LIB_DEPENDS:STATIC=general;vtkFiltersPointsPythonD; //Dependencies for the target vtkFiltersPoints_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD; //Dependencies for the target vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel; //Dependencies for the target vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD; //Dependencies for the target vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;vtkWrappingPythonCore; //Dependencies for the target vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD; //Dependencies for the target vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingFourierPythonD;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD; //Dependencies for the target vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonTransforms;general;vtkImagingFourier;general;vtkalglib; //Dependencies for the target vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD; //Dependencies for the target vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersVerdictCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersVerdict; //Dependencies for the target vtkFiltersVerdictPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersVerdict; //Dependencies for the target vtkFiltersVerdictPython_LIB_DEPENDS:STATIC=general;vtkFiltersVerdictPythonD; //Dependencies for the target vtkFiltersVerdict_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;verdict; //Dependencies for the target vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD; //Dependencies for the target vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys; //Dependencies for the target vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore; //Dependencies for the target vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCore; //Dependencies for the target vtkIOCorePython_LIB_DEPENDS:STATIC=general;vtkIOCorePythonD; //Dependencies for the target vtkIOCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkzlib;general;vtksys; //Dependencies for the target vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD; //Dependencies for the target vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel; //Dependencies for the target vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkIOXMLPythonD;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD; //Dependencies for the target vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkIOXML;general;vtkexoIIc;general;vtksys; //Dependencies for the target vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport; //Dependencies for the target vtkIOExportOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExportOpenGL; //Dependencies for the target vtkIOExportOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOExportPythonD;general;vtkIOExportPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingGL2PSPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOpenGLPythonD;general;vtkIOExportOpenGL; //Dependencies for the target vtkIOExportOpenGLPython_LIB_DEPENDS:STATIC=general;vtkIOExportOpenGLPythonD; //Dependencies for the target vtkIOExportOpenGL_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOExport;general;vtkIOExport;general;vtkRenderingAnnotation;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingGL2PS;general;vtkRenderingLabel;general;vtkRenderingOpenGL;general;vtkgl2ps;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSPythonD;general;vtkIOExport; //Dependencies for the target vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD; //Dependencies for the target vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkImagingCore;general;vtkRenderingCore;general;vtkRenderingGL2PS;general;vtkIOImage;general;vtkFiltersGeometry;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD; //Dependencies for the target vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkzlib;general;vtksys; //Dependencies for the target vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage; //Dependencies for the target vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD;general;vtkIOImage; //Dependencies for the target vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD; //Dependencies for the target vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOCore;general;vtkjpeg;general;vtkpng;general;vtktiff;general;vtkmetaio;general;vtkDICOMParser;general;vtkzlib;general;vtksys; //Dependencies for the target vtkIOImportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImport; //Dependencies for the target vtkIOImportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkIOImagePythonD;general;vtkRenderingCorePythonD;general;vtkIOImport; //Dependencies for the target vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD; //Dependencies for the target vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtksys;general;vtkFiltersSources;general;vtkIOImage; //Dependencies for the target vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkInfovisCorePythonD;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD; //Dependencies for the target vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkInfovisCore;general;vtklibxml2;general;vtksys; //Dependencies for the target vtkIOLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLPythonD;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD; //Dependencies for the target vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkIOXML;general;vtksys; //Dependencies for the target vtkIOLegacyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD; //Dependencies for the target vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtksys; //Dependencies for the target vtkIOMPIImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIImage; //Dependencies for the target vtkIOMPIImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIImage; //Dependencies for the target vtkIOMPIImagePython_LIB_DEPENDS:STATIC=general;vtkIOMPIImagePythonD; //Dependencies for the target vtkIOMPIImage_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkIOImage;general;vtkParallelMPI;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPython_LIB_DEPENDS:STATIC=general;vtkIOMPIParallelPythonD; //Dependencies for the target vtkIOMPIParallel_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOGeometry;general;vtkIOParallel;general;vtkIOParallel;general;vtksys;general;vtkParallelMPI;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD; //Dependencies for the target vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOCore;general;vtkoggtheora; //Dependencies for the target vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD; //Dependencies for the target vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;general;vtkNetCDF;general;vtkNetCDF_cxx; //Dependencies for the target vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOGeometryPythonD;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD; //Dependencies for the target vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkIOGeometry; //Dependencies for the target vtkIOParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallel; //Dependencies for the target vtkIOParallelExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelExodus; //Dependencies for the target vtkIOParallelExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelExodus; //Dependencies for the target vtkIOParallelExodusPython_LIB_DEPENDS:STATIC=general;vtkIOParallelExodusPythonD; //Dependencies for the target vtkIOParallelExodus_LIB_DEPENDS:STATIC=general;vtkIOExodus;general;vtkIOExodus;general;vtkParallelCore;general;vtksys;general;vtkexoIIc; //Dependencies for the target vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkIOLSDynaPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDynaPythonD; //Dependencies for the target vtkIOParallelLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkIOLSDyna;general;vtkParallelCore; //Dependencies for the target vtkIOParallelNetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD; //Dependencies for the target vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelMPI;general;vtkNetCDF;general;vtkNetCDF_cxx;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkIONetCDFPythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkIOParallel; //Dependencies for the target vtkIOParallelPython_LIB_DEPENDS:STATIC=general;vtkIOParallelPythonD; //Dependencies for the target vtkIOParallelXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelXML; //Dependencies for the target vtkIOParallelXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelXML; //Dependencies for the target vtkIOParallelXMLPython_LIB_DEPENDS:STATIC=general;vtkIOParallelXMLPythonD; //Dependencies for the target vtkIOParallelXML_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkIOImage;general;vtkIONetCDF;general;vtkIOXML;general;vtkParallelCore;general;vtkexoIIc;general;vtkjsoncpp;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys; //Dependencies for the target vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC; //Dependencies for the target vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD;general;vtkIOVPIC; //Dependencies for the target vtkIOVPICPython_LIB_DEPENDS:STATIC=general;vtkIOVPICPythonD; //Dependencies for the target vtkIOVPIC_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkParallelCore;general;VPIC; //Dependencies for the target vtkIOXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXML; //Dependencies for the target vtkIOXMLParserCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD; //Dependencies for the target vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkexpat; //Dependencies for the target vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOXMLParserPythonD;general;vtkIOXML; //Dependencies for the target vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD; //Dependencies for the target vtkIOXML_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOXMLParser;general;vtksys; //Dependencies for the target vtkIOXdmf2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXdmf2; //Dependencies for the target vtkIOXdmf2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkIOXdmf2; //Dependencies for the target vtkIOXdmf2Python_LIB_DEPENDS:STATIC=general;vtkIOXdmf2PythonD; //Dependencies for the target vtkIOXdmf2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkIOLegacy;general;vtkIOXML;general;vtksys;general;vtkxdmf2; //Dependencies for the target vtkImagingColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD; //Dependencies for the target vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkImagingCore; //Dependencies for the target vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD; //Dependencies for the target vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkImagingFourierCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD; //Dependencies for the target vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtksys; //Dependencies for the target vtkImagingGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingSourcesPythonD;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD; //Dependencies for the target vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkImagingSources; //Dependencies for the target vtkImagingHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingHybrid; //Dependencies for the target vtkImagingHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkImagingHybrid; //Dependencies for the target vtkImagingHybridPython_LIB_DEPENDS:STATIC=general;vtkImagingHybridPythonD; //Dependencies for the target vtkImagingHybrid_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkImagingCore; //Dependencies for the target vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD; //Dependencies for the target vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkImagingGeneral; //Dependencies for the target vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD; //Dependencies for the target vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkImagingCore; //Dependencies for the target vtkInfovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisCore; //Dependencies for the target vtkInfovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkInfovisCore; //Dependencies for the target vtkInfovisCorePython_LIB_DEPENDS:STATIC=general;vtkInfovisCorePythonD; //Dependencies for the target vtkInfovisCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneral; //Dependencies for the target vtkInteractionImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingColorPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD; //Dependencies for the target vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkRenderingCore;general;vtkRenderingFreeType; //Dependencies for the target vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD; //Dependencies for the target vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkFiltersSources;general;vtkFiltersExtraction; //Dependencies for the target vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPython_LIB_DEPENDS:STATIC=general;vtkInteractionWidgetsPythonD; //Dependencies for the target vtkInteractionWidgets_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume; //Dependencies for the target vtkNetCDF_LIB_DEPENDS:STATIC=general;vtkhdf5_hl;general;vtkhdf5;general;m; //Dependencies for the target vtkNetCDF_cxx_LIB_DEPENDS:STATIC=general;vtkNetCDF; //Dependencies for the target vtkPVAnimationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVAnimation; //Dependencies for the target vtkPVAnimationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOMoviePythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVAnimation; //Dependencies for the target vtkPVAnimationPython_LIB_DEPENDS:STATIC=general;vtkPVAnimationPythonD; //Dependencies for the target vtkPVAnimation_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOMovie;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVCatalystCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD;general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD; //Dependencies for the target vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCorePythonD; //Dependencies for the target vtkPVClientServerCoreCore_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOInfovisPythonD;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD; //Dependencies for the target vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOInfovis; //Dependencies for the target vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering; //Dependencies for the target vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkWebGLExporterPythonD;general;vtkPVClientServerCoreRendering; //Dependencies for the target vtkPVClientServerCoreRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRenderingPythonD; //Dependencies for the target vtkPVClientServerCoreRendering_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkFiltersAMR;general;vtkPVClientServerCoreCore;general;vtkPVVTKExtensionsDefault;general;vtkPVVTKExtensionsRendering;general;vtkRenderingLabel;general;vtkRenderingVolumeAMR;general;vtkRenderingVolumeOpenGL;general;vtkViewsContext2D;general;vtkViewsCore;general;vtkWebGLExporter;general;vtksys;general;vtkzlib;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon; //Dependencies for the target vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD;general;vtkPVCommon; //Dependencies for the target vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD; //Dependencies for the target vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;general;vtkIOXMLParser;general;vtksys; //Dependencies for the target vtkPVPythonCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVPythonCatalyst; //Dependencies for the target vtkPVPythonCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalystPythonD; //Dependencies for the target vtkPVPythonCatalyst_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkPythonInterpreter;general;vtkUtilitiesPythonInitializer; //Dependencies for the target vtkPVServerImplementationCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerImplementationCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerImplementationCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCorePythonD; //Dependencies for the target vtkPVServerImplementationCore_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;protobuf;general;vtksys; //Dependencies for the target vtkPVServerImplementationRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationRendering; //Dependencies for the target vtkPVServerImplementationRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPVServerImplementationRendering; //Dependencies for the target vtkPVServerImplementationRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRenderingPythonD; //Dependencies for the target vtkPVServerImplementationRendering_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerManagerApplicationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerApplication; //Dependencies for the target vtkPVServerManagerApplicationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelDIY2PythonD;general;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelGeometryPythonD;general;vtkFiltersParallelImagingPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkFiltersProgrammablePythonD;general;vtkFiltersPythonPythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersTexturePythonD;general;vtkFiltersVerdictPythonD;general;vtkIOAMRPythonD;general;vtkIOEnSightPythonD;general;vtkIOExodusPythonD;general;vtkIOExportPythonD;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOLegacyPythonD;general;vtkIOMPIImagePythonD;general;vtkIOMPIParallelPythonD;general;vtkIOMoviePythonD;general;vtkIONetCDFPythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelLSDynaPythonD;general;vtkIOParallelNetCDFPythonD;general;vtkIOVPICPythonD;general;vtkIOXMLPythonD;general;vtkIOXMLPythonD;general;vtkIOXdmf2PythonD;general;vtkImagingCorePythonD;general;vtkImagingFourierPythonD;general;vtkImagingHybridPythonD;general;vtkImagingMorphologicalPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionImagePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVAnimationPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVVTKExtensionsPointsPythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPI4PyPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingLICPythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;general;vtkViewsContext2DPythonD;general;vtkPVServerManagerApplication; //Dependencies for the target vtkPVServerManagerApplicationPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplicationPythonD; //Dependencies for the target vtkPVServerManagerApplication_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonCoreCS;general;vtkCommonMathCS;general;vtkCommonMiscCS;general;vtkCommonSystemCS;general;vtkCommonTransformsCS;general;vtkCommonDataModelCS;general;vtkCommonColorCS;general;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkInfovisCoreCS;general;vtkFiltersGeometryCS;general;vtkFiltersSourcesCS;general;vtkRenderingCoreCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkPythonInterpreterCS;general;vtkIOCoreCS;general;vtkIOGeometryCS;general;vtkIOXMLParserCS;general;vtkIOXMLCS;general;vtkDomainsChemistryCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersAMRCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersGenericCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkFiltersHyperTreeCS;general;vtkImagingGeneralCS;general;vtkFiltersImagingCS;general;vtkFiltersModelingCS;general;vtkFiltersParallelCS;general;vtkParallelMPICS;general;vtkFiltersParallelDIY2CS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelGeometryCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersParallelMPICS;general;vtkFiltersParallelStatisticsCS;general;vtkFiltersPointsCS;general;vtkFiltersProgrammableCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOEnSightCS;general;vtkIOExodusCS;general;vtkIOImageCS;general;vtkImagingHybridCS;general;vtkRenderingOpenGLCS;general;vtkRenderingContextOpenGLCS;general;vtkRenderingGL2PSCS;general;vtkIOExportCS;general;vtkImagingColorCS;general;vtkRenderingAnnotationCS;general;vtkRenderingLabelCS;general;vtkIOExportOpenGLCS;general;vtkIOImportCS;general;vtkIOInfovisCS;general;vtkIOLSDynaCS;general;vtkIOMPIImageCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOMPIParallelCS;general;vtkIOMovieCS;general;vtkIOPLYCS;general;vtkIOParallelExodusCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOParallelXMLCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionStyleCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkInteractionImageCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkRenderingLICCS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkRenderingParallelLICCS;general;vtkRenderingVolumeOpenGLCS;general;vtkRenderingVolumeAMRCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkWebGLExporterCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkPVVTKExtensionsPointsCS;general;vtkParallelMPI4PyCS;general;vtkRenderingLODCS;general;vtkWebCoreCS;general;vtkParaViewWebCoreCS;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCorePythonD; //Dependencies for the target vtkPVServerManagerCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkPVServerImplementationCore;general;vtksys;general;vtkjsoncpp;general;vtkpugixml;general;vtkPythonInterpreter; //Dependencies for the target vtkPVServerManagerDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVServerManagerDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVServerManagerDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefaultPythonD; //Dependencies for the target vtkPVServerManagerDefault_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtksys;general;vtkRenderingVolumeOpenGL;general;vtkTestingRendering;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVServerManagerRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerRendering; //Dependencies for the target vtkPVServerManagerRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerRendering; //Dependencies for the target vtkPVServerManagerRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRenderingPythonD; //Dependencies for the target vtkPVServerManagerRendering_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkPVServerManagerCore;general;vtkPVServerManagerCore;general;vtkCommonColor;general;vtkjsoncpp;general;vtksys; //Dependencies for the target vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore; //Dependencies for the target vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD;general;vtkPVVTKExtensionsCore; //Dependencies for the target vtkPVVTKExtensionsCorePython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCorePythonD; //Dependencies for the target vtkPVVTKExtensionsCore_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkPVCommon;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkPVVTKExtensionsDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsDefault; //Dependencies for the target vtkPVVTKExtensionsDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOMPIImagePythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkPVVTKExtensionsDefault; //Dependencies for the target vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD; //Dependencies for the target vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersGeneral;general;vtkFiltersParallelFlowPaths;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;general;vtkIOMPIImage;general;vtkIOParallel;general;vtkIOParallelExodus;general;vtkIOParallelXML;general;vtkImagingFourier;general;vtkImagingSources;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkPVVTKExtensionsRendering;general;vtkIOInfovis;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys;general;vtkChartsCore;general;vtkIOPLY;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkPVVTKExtensionsPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsPoints; //Dependencies for the target vtkPVVTKExtensionsPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersPointsPythonD;general;vtkPVVTKExtensionsPoints; //Dependencies for the target vtkPVVTKExtensionsPointsPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsPointsPythonD; //Dependencies for the target vtkPVVTKExtensionsPoints_LIB_DEPENDS:STATIC=general;vtkFiltersPoints;general;vtkFiltersCore; //Dependencies for the target vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering; //Dependencies for the target vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonColorPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOExportOpenGLPythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingLICPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkPVVTKExtensionsRendering; //Dependencies for the target vtkPVVTKExtensionsRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRenderingPythonD; //Dependencies for the target vtkPVVTKExtensionsRendering_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkIOExport;general;vtkIOExportOpenGL;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingLIC;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL;general;vtkRenderingParallel;general;vtkRenderingParallelLIC;general;vtkRenderingVolumeAMR;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkzlib;general;vtklz4;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkParaViewWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParaViewWebCore; //Dependencies for the target vtkParaViewWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerDefaultPythonD;general;vtkWebCorePythonD;general;vtkWebGLExporterPythonD;general;vtkParaViewWebCore; //Dependencies for the target vtkParaViewWebCorePython_LIB_DEPENDS:STATIC=general;vtkParaViewWebCorePythonD; //Dependencies for the target vtkParaViewWebCore_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefault;general;vtkWebCore;general;vtkWebGLExporter; //Dependencies for the target vtkParallelCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelCore; //Dependencies for the target vtkParallelCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOLegacyPythonD;general;vtkParallelCore; //Dependencies for the target vtkParallelCorePython_LIB_DEPENDS:STATIC=general;vtkParallelCorePythonD; //Dependencies for the target vtkParallelCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOLegacy;general;vtksys; //Dependencies for the target vtkParallelMPI4PyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkParallelMPIPythonD;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD; //Dependencies for the target vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkParallelMPI;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkParallelCorePythonD;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkParallelCore;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkPointSpriteGraphicsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteGraphics; //Dependencies for the target vtkPointSpriteGraphics_LIB_DEPENDS:STATIC=general;vtkFiltersCore; //Dependencies for the target vtkPointSpriteRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteRendering; //Dependencies for the target vtkPointSpriteRendering_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkRenderingFreeType;general;vtkRenderingOpenGL;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter; //Dependencies for the target vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPythonInterpreter; //Dependencies for the target vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD; //Dependencies for the target vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;vtksys; //Dependencies for the target vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD; //Dependencies for the target vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkRenderingFreeType;general;vtkFiltersSources; //Dependencies for the target vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPython_LIB_DEPENDS:STATIC=general;vtkRenderingContext2DPythonD; //Dependencies for the target vtkRenderingContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContextOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL; //Dependencies for the target vtkRenderingContextOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingContextOpenGL; //Dependencies for the target vtkRenderingContextOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGLPythonD; //Dependencies for the target vtkRenderingContextOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore; //Dependencies for the target vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCore; //Dependencies for the target vtkRenderingCorePython_LIB_DEPENDS:STATIC=general;vtkRenderingCorePythonD; //Dependencies for the target vtkRenderingCore_LIB_DEPENDS:STATIC=general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkFiltersSources;general;vtkFiltersGeometry;general;vtksys; //Dependencies for the target vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD; //Dependencies for the target vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype; //Dependencies for the target vtkRenderingGL2PSCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PS; //Dependencies for the target vtkRenderingGL2PSPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingContextOpenGLPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingGL2PS; //Dependencies for the target vtkRenderingGL2PSPython_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSPythonD; //Dependencies for the target vtkRenderingGL2PS_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;general;vtkgl2ps;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLIC; //Dependencies for the target vtkRenderingLICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingLIC; //Dependencies for the target vtkRenderingLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingLICPythonD; //Dependencies for the target vtkRenderingLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingSources;general;vtkRenderingOpenGL;general;vtksys;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersModelingPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPython_LIB_DEPENDS:STATIC=general;vtkRenderingLODPythonD; //Dependencies for the target vtkRenderingLOD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkRenderingCore; //Dependencies for the target vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD; //Dependencies for the target vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkFiltersExtraction; //Dependencies for the target vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD; //Dependencies for the target vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkPythonInterpreter;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkWrappingPythonCore; //Dependencies for the target vtkRenderingOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL; //Dependencies for the target vtkRenderingOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingHybridPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL; //Dependencies for the target vtkRenderingOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkRenderingOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkImagingHybrid;general;vtksys;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD; //Dependencies for the target vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkParallelMPI;general;vtkRenderingLIC;general;vtkRenderingOpenGL;general;/home/bd/.local//lib/libOSMesa.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD; //Dependencies for the target vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkParallelCore;general;vtkRenderingOpenGL;general;vtkIOImage;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD; //Dependencies for the target vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;vtkRenderingVolumeOpenGL; //Dependencies for the target vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL; //Dependencies for the target vtkRenderingVolumeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL; //Dependencies for the target vtkRenderingVolumeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGLPythonD; //Dependencies for the target vtkRenderingVolumeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;vtkRenderingVolume;general;vtksys;general;vtkFiltersGeneral;general;vtkFiltersSources;general;/home/bd/.local//lib/libOSMesa.so; //Dependencies for the target vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumePython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumePythonD; //Dependencies for the target vtkRenderingVolume_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore; //Dependencies for the target vtkSciberQuestCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkSciberQuest; //Dependencies for the target vtkSciberQuest_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPaths;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtksys;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so;general;/usr/lib/libmpi_cxx.so;general;/usr/lib/libmpi.so;general;/usr/lib/x86_64-linux-gnu/libdl.so;general;/usr/lib/x86_64-linux-gnu/libhwloc.so; //Dependencies for the target vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPython_LIB_DEPENDS:STATIC=general;vtkTestingRenderingPythonD; //Dependencies for the target vtkTestingRendering_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore;general;vtksys;general;vtkIOImage; //Dependencies for the target vtkUtilitiesPythonInitializer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;general;vtkWrappingPythonCore;general;vtkCommonCore; //Dependencies for the target vtkViewsContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkViewsCorePythonD;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD; //Dependencies for the target vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkViewsCore; //Dependencies for the target vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePython_LIB_DEPENDS:STATIC=general;vtkViewsCorePythonD; //Dependencies for the target vtkViewsCore_LIB_DEPENDS:STATIC=general;vtkInteractionWidgets;general;vtkRenderingCore; //Dependencies for the target vtkWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebCore; //Dependencies for the target vtkWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporterPythonD;general;vtkWebCore; //Dependencies for the target vtkWebCorePython_LIB_DEPENDS:STATIC=general;vtkWebCorePythonD; //Dependencies for the target vtkWebCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;general;vtkFiltersGeneral;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;vtkIOCore;general;vtkIOImage;general;vtkRenderingCore;general;vtkParallelCore;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersGeometryPythonD;general;vtkIOExportPythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPython_LIB_DEPENDS:STATIC=general;vtkWebGLExporterPythonD; //Dependencies for the target vtkWebGLExporter_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtksys;general;vtkFiltersGeometry;general;vtkInteractionWidgets;general;vtkRenderingCore; //Dependencies for the target vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/usr/lib/x86_64-linux-gnu/libpython2.7.so;general;vtksys; //Dependencies for target vtkWrappingTools_LIB_DEPENDS:STATIC= //Dependencies for target vtkalglib_LIB_DEPENDS:STATIC= //Dependencies for the target vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF;general;vtkNetCDF_cxx; //Dependencies for target vtkexpat_LIB_DEPENDS:STATIC= //Dependencies for the target vtkfreetype_LIB_DEPENDS:STATIC=general;vtkzlib; //Dependencies for the target vtkgl2ps_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkpng;general;/home/bd/.local//lib/libOSMesa.so;general;m; //Dependencies for the target vtkhdf5_LIB_DEPENDS:STATIC=general;m;general;dl;general;vtkzlib; //Dependencies for the target vtkhdf5_hl_LIB_DEPENDS:STATIC=general;vtkhdf5; //Dependencies for target vtkjpeg_LIB_DEPENDS:STATIC= //Dependencies for target vtkjsoncpp_LIB_DEPENDS:STATIC= //Value Computed by CMake vtklibxml2_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/libxml2/vtklibxml2 //Dependencies for the target vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;general;dl;general;-lpthread;general;dl;general;m; //Value Computed by CMake vtklibxml2_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/libxml2/vtklibxml2 //Dependencies for target vtklz4_LIB_DEPENDS:STATIC= //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for target vtkoggtheora_LIB_DEPENDS:STATIC= //Dependencies for the target vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;general;-lm; //Dependencies for target vtkpugixml_LIB_DEPENDS:STATIC= //Value Computed by CMake vtksys_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtksys_LIB_DEPENDS:STATIC=general;dl;general;dl; //Value Computed by CMake vtksys_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtktiff_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkjpeg;general;-lm; //Dependencies for the target vtkxdmf2_LIB_DEPENDS:STATIC=general;vtklibxml2;general;vtkhdf5_hl;general;vtkhdf5; //Dependencies for target vtkzlib_LIB_DEPENDS:STATIC= //Value Computed by CMake xdmf2_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake zlib_BINARY_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/ThirdParty/zlib/vtkzlib //Value Computed by CMake zlib_SOURCE_DIR:STATIC=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/ThirdParty/zlib/vtkzlib ######################## # INTERNAL cache entries ######################## ALGLIB_SHARED_LIB:INTERNAL=ON //Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN ARCH_TO_BUILD:INTERNAL=Linux //CXX test BOOL_NOTDEFINED:INTERNAL= //ADVANCED property for variable: BUILD_USER_DEFINED_LIBS BUILD_USER_DEFINED_LIBS-ADVANCED:INTERNAL=1 //Have function clock_gettime CLOCK_GETTIME_IN_LIBC:INTERNAL=1 //Have library posix4 CLOCK_GETTIME_IN_LIBPOSIX4:INTERNAL= //Have library rt CLOCK_GETTIME_IN_LIBRT:INTERNAL=1 //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=7 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/home/bd/.local/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/home/bd/.local/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/home/bd/.local/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/home/bd/.local/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //ADVANCED property for variable: CMAKE_Fortran_COMPILER CMAKE_Fortran_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS CMAKE_Fortran_FLAGS-ADVANCED:INTERNAL=1 //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Have symbol pthread_create CMAKE_HAVE_LIBC_CREATE:INTERNAL= //Have library pthreads CMAKE_HAVE_PTHREADS_CREATE:INTERNAL= //Have library pthread CMAKE_HAVE_PTHREAD_CREATE:INTERNAL=1 //Have include pthread.h CMAKE_HAVE_PTHREAD_H:INTERNAL=1 //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //Does the compiler support std::. CMAKE_NO_STD_NAMESPACE:INTERNAL=0 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=241 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Test Support for 64 bit file systems CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/home/bd/.local/share/cmake-3.7 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(unsigned short) CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE CMAKE_STD_NAMESPACE:INTERNAL=TRUE //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_THREAD_LIBS CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Result of TEST_BIG_ENDIAN CMAKE_WORDS_BIGENDIAN:INTERNAL=0 //Compiler support for a deprecated attribute COMPILER_HAS_DEPRECATED:INTERNAL=1 //Test COMPILER_HAS_DEPRECATED_ATTR COMPILER_HAS_DEPRECATED_ATTR:INTERNAL=1 //Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY COMPILER_HAS_HIDDEN_INLINE_VISIBILITY:INTERNAL=1 //Test COMPILER_HAS_HIDDEN_VISIBILITY COMPILER_HAS_HIDDEN_VISIBILITY:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_DEB CPACK_BINARY_DEB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_IFW CPACK_BINARY_IFW-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_NSIS CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_RPM CPACK_BINARY_RPM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_STGZ CPACK_BINARY_STGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TBZ2 CPACK_BINARY_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TGZ CPACK_BINARY_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TXZ CPACK_BINARY_TXZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TZ CPACK_BINARY_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_RPM CPACK_SOURCE_RPM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TBZ2 CPACK_SOURCE_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TGZ CPACK_SOURCE_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TXZ CPACK_SOURCE_TXZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TZ CPACK_SOURCE_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_ZIP CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE CXX_HAVE_OFFSETOF:INTERNAL=TRUE //Result of TRY_COMPILE DEV_T_IS_SCALAR:INTERNAL=TRUE //ADVANCED property for variable: EXECINFO_LIB EXECINFO_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1 EXECUTABLE_OUTPUT_PATH:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/ThirdParty/protobuf/vtkprotobuf/bin //ADVANCED property for variable: EXODUSII_DISABLE_COMPILER_WARNINGS EXODUSII_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //Have include malloc.h EX_HAVE_MALLOC_H:INTERNAL=1 //ADVANCED property for variable: Eigen_DIR Eigen_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ExternalData_URL_TEMPLATES ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1 //Details about finding MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so][/usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/usr/lib/libmpi_cxx.so;/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so][/usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi][v()] //Details about finding OSMesa FIND_PACKAGE_MESSAGE_DETAILS_OSMesa:INTERNAL=[/home/bd/.local//lib/libOSMesa.so][/home/bd/.local//include][v()] //Details about finding PythonInterp FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/usr/bin/python2][v2.7.6()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/usr/lib/x86_64-linux-gnu/libpython2.7.so][/usr/include/python2.7][v()] //Details about finding Threads FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()] //Result of TRY_COMPILE GETTIMEOFDAY_GIVES_TZ:INTERNAL=TRUE //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GMVReader_GMVREAD_LIB_DIR GMVReader_GMVREAD_LIB_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS-ADVANCED:INTERNAL=1 //Define if your system generates wrong code for log2 routine H5_BAD_LOG2_CODE_GENERATED:INTERNAL=0 //Other test H5_CXX_HAVE_OFFSETOF:INTERNAL=1 //Other test H5_DEV_T_IS_SCALAR:INTERNAL=1 //Checking IF overflows normally converting floating-point to integer // values H5_FP_TO_INTEGER_OVERFLOW_WORKS:INTERNAL=1 //Result of TRY_COMPILE H5_FP_TO_INTEGER_OVERFLOW_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN:INTERNAL=0 //Checking IF accurately roundup converting floating-point to unsigned // long long values H5_FP_TO_ULLONG_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_FP_TO_ULLONG_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_ULLONG_ACCURATE_RUN:INTERNAL=0 //Checking IF right maximum converting floating-point to unsigned // long long values H5_FP_TO_ULLONG_RIGHT_MAXIMUM:INTERNAL= //Result of TRY_COMPILE H5_FP_TO_ULLONG_RIGHT_MAXIMUM_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_FP_TO_ULLONG_RIGHT_MAXIMUM_RUN:INTERNAL=1 //Other test H5_GETTIMEOFDAY_GIVES_TZ:INTERNAL=1 //Have function alarm H5_HAVE_ALARM:INTERNAL=1 //Other test H5_HAVE_ATTRIBUTE:INTERNAL=1 //Other test H5_HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=1 //Other test H5_HAVE_C99_FUNC:INTERNAL=1 //Have symbol tzname H5_HAVE_DECL_TZNAME:INTERNAL=1 //Have function difftime H5_HAVE_DIFFTIME:INTERNAL=1 //Other test H5_HAVE_DIRECT:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h H5_HAVE_DIRENT_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h H5_HAVE_DLFCN_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h H5_HAVE_FEATURES_H:INTERNAL=1 //Have function fork H5_HAVE_FORK:INTERNAL=1 //Have function frexpf H5_HAVE_FREXPF:INTERNAL=1 //Have function frexpl H5_HAVE_FREXPL:INTERNAL=1 //Have function fseeko H5_HAVE_FSEEKO:INTERNAL=1 //Have function fseeko64 H5_HAVE_FSEEKO64:INTERNAL=1 //Have function fstat64 H5_HAVE_FSTAT64:INTERNAL=1 //Have function ftello H5_HAVE_FTELLO:INTERNAL=1 //Have function ftello64 H5_HAVE_FTELLO64:INTERNAL=1 //Have function ftruncate64 H5_HAVE_FTRUNCATE64:INTERNAL=1 //Other test H5_HAVE_FUNCTION:INTERNAL=1 //Have function GetConsoleScreenBufferInfo H5_HAVE_GETCONSOLESCREENBUFFERINFO:INTERNAL= //Have function gethostname H5_HAVE_GETHOSTNAME:INTERNAL=1 //Have function getpwuid H5_HAVE_GETPWUID:INTERNAL=1 //Have function getrusage H5_HAVE_GETRUSAGE:INTERNAL=1 //Have function gettextinfo H5_HAVE_GETTEXTINFO:INTERNAL= //H5_HAVE_GETTIMEOFDAY H5_HAVE_GETTIMEOFDAY:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;globus/common.h H5_HAVE_GLOBUS_COMMON_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h;inttypes.h H5_HAVE_INTTYPES_H:INTERNAL=1 //Have function ioctl H5_HAVE_IOCTL:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;io.h H5_HAVE_IO_H:INTERNAL= //Have library dl;m H5_HAVE_LIBDL:INTERNAL=1 //Have library m; H5_HAVE_LIBM:INTERNAL=1 //Have library socket;m;dl H5_HAVE_LIBSOCKET:INTERNAL= //Have library ucb;m;dl H5_HAVE_LIBUCB:INTERNAL= //Have library ws2_32;m;dl H5_HAVE_LIBWS2_32:INTERNAL= //Have library wsock32;m;dl H5_HAVE_LIBWSOCK32:INTERNAL= //Have function longjmp H5_HAVE_LONGJMP:INTERNAL=1 //Have function lseek64 H5_HAVE_LSEEK64:INTERNAL=1 //Have function lstat H5_HAVE_LSTAT:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;mach/mach_time.h H5_HAVE_MACH_MACH_TIME_H:INTERNAL= //Have symbol sigsetjmp H5_HAVE_MACRO_SIGSETJMP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h H5_HAVE_MEMORY_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h;memory.h;dlfcn.h;inttypes.h;netinet/in.h H5_HAVE_NETINET_IN_H:INTERNAL=1 //Other test H5_HAVE_OFF64_T:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pdb.h H5_HAVE_PDB_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h H5_HAVE_PTHREAD_H:INTERNAL=1 //Have function random H5_HAVE_RANDOM:INTERNAL=1 //Have function rand_r H5_HAVE_RAND_R:INTERNAL=1 //Have function setjmp H5_HAVE_SETJMP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h H5_HAVE_SETJMP_H:INTERNAL=1 //Have function setsysinfo H5_HAVE_SETSYSINFO:INTERNAL= //Have function sigaction H5_HAVE_SIGACTION:INTERNAL=1 //Have function siglongjmp H5_HAVE_SIGLONGJMP:INTERNAL=1 //Have function signal H5_HAVE_SIGNAL:INTERNAL=1 //Have function sigprocmask H5_HAVE_SIGPROCMASK:INTERNAL=1 //Have function sigsetjmp H5_HAVE_SIGSETJMP:INTERNAL= //Have function snprintf H5_HAVE_SNPRINTF:INTERNAL=1 //Other test H5_HAVE_SOCKLEN_T:INTERNAL=1 //Have function srandom H5_HAVE_SRANDOM:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;srbclient.h H5_HAVE_SRBCLIENT_H:INTERNAL= //Have function stat64 H5_HAVE_STAT64:INTERNAL=1 //Other test H5_HAVE_STAT64_STRUCT:INTERNAL=1 //Other test H5_HAVE_STAT_ST_BLOCKS:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h H5_HAVE_STDDEF_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h H5_HAVE_STDINT_H:INTERNAL=1 //Have include stdint.h H5_HAVE_STDINT_H_CXX:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h;stdlib.h H5_HAVE_STDLIB_H:INTERNAL=1 //Have function strdup H5_HAVE_STRDUP:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h H5_HAVE_STRINGS_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h H5_HAVE_STRING_H:INTERNAL=1 //Other test H5_HAVE_STRUCT_TEXT_INFO:INTERNAL= //Other test H5_HAVE_STRUCT_TIMEZONE:INTERNAL=1 //Other test H5_HAVE_STRUCT_TM_TM_ZONE:INTERNAL=1 //Other test H5_HAVE_STRUCT_VIDEOCONFIG:INTERNAL= //Have function symlink H5_HAVE_SYMLINK:INTERNAL=1 //Have function system H5_HAVE_SYSTEM:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h H5_HAVE_SYS_IOCTL_H:INTERNAL=1 H5_HAVE_SYS_PROC_H:INTERNAL= //Have include ;sys/resource.h H5_HAVE_SYS_RESOURCE_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h H5_HAVE_SYS_SOCKET_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h H5_HAVE_SYS_STAT_H:INTERNAL=1 H5_HAVE_SYS_SYSINFO_H:INTERNAL= //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h H5_HAVE_SYS_TIMEB_H:INTERNAL=1 //H5_HAVE_SYS_TIME_GETTIMEOFDAY H5_HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=1 //Have include sys/resource.h;sys/time.h H5_HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h H5_HAVE_SYS_TYPES_H:INTERNAL=1 //Other test H5_HAVE_TIMEZONE:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;sys/timeb.h;pthread.h;string.h;strings.h;time.h H5_HAVE_TIME_H:INTERNAL=1 //Have symbol TIOCGETD H5_HAVE_TIOCGETD:INTERNAL=1 //Have symbol TIOCGWINSZ H5_HAVE_TIOCGWINSZ:INTERNAL=1 //Other test H5_HAVE_TM_GMTOFF:INTERNAL=1 //Other test H5_HAVE_TM_ZONE:INTERNAL=1 //Have include sys/resource.h;sys/time.h;unistd.h H5_HAVE_UNISTD_H:INTERNAL=1 //Have function vasprintf H5_HAVE_VASPRINTF:INTERNAL=1 //Have function vsnprintf H5_HAVE_VSNPRINTF:INTERNAL=1 //Have function waitpid H5_HAVE_WAITPID:INTERNAL=1 //Have includes sys/resource.h;sys/time.h;unistd.h;sys/ioctl.h;sys/stat.h;sys/socket.h;sys/types.h;stddef.h;setjmp.h;features.h;dirent.h;stdint.h;winsock2.h H5_HAVE_WINSOCK2_H:INTERNAL= //Have function _getvideoconfig H5_HAVE__GETVIDEOCONFIG:INTERNAL= //Have function _scrsize H5_HAVE__SCRSIZE:INTERNAL= //Other test H5_HAVE___TM_GMTOFF:INTERNAL= //Other test H5_INLINE_TEST___inline:INTERNAL=1 //Other test H5_INLINE_TEST___inline__:INTERNAL=1 //Other test H5_INLINE_TEST_inline:INTERNAL=1 //checking IF accurately converting from integers to long double H5_INTEGER_TO_LDOUBLE_ACCURATE:INTERNAL=1 //checking IF converting from long double to integers is accurate H5_LDOUBLE_TO_INTEGER_ACCURATE:INTERNAL=1 //Checking IF converting from long double to integers works H5_LDOUBLE_TO_INTEGER_WORKS:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_INTEGER_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_INTEGER_WORKS_RUN:INTERNAL=0 //Checking IF correctly converting long double to (unsigned) long // long values H5_LDOUBLE_TO_LLONG_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_LLONG_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_LLONG_ACCURATE_RUN:INTERNAL=0 //Define if your system converts long double to (unsigned) long // values with special algorithm H5_LDOUBLE_TO_LONG_SPECIAL:INTERNAL=0 //Checking IF correctly converting long double to unsigned int // values H5_LDOUBLE_TO_UINT_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_LDOUBLE_TO_UINT_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LDOUBLE_TO_UINT_ACCURATE_RUN:INTERNAL=0 //Use Legacy Names for Libraries and Programs H5_LEGACY_NAMING:INTERNAL=ON //Checking IF compiling long long to floating-point typecasts work H5_LLONG_TO_FP_CAST_WORKS:INTERNAL=1 //Checking IF correctly converting (unsigned) long long to long // double values H5_LLONG_TO_LDOUBLE_CORRECT:INTERNAL=1 //Result of TRY_COMPILE H5_LLONG_TO_LDOUBLE_CORRECT_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_LLONG_TO_LDOUBLE_CORRECT_RUN:INTERNAL=0 //Other test H5_LONE_COLON:INTERNAL=1 //Define if your system can convert (unsigned) long to long double // values with special algorithm H5_LONG_TO_LDOUBLE_SPECIAL:INTERNAL=0 //Checking IF alignment restrictions are strictly enforced H5_NO_ALIGNMENT_RESTRICTIONS:INTERNAL=1 //Result of TRY_COMPILE H5_NO_ALIGNMENT_RESTRICTIONS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_NO_ALIGNMENT_RESTRICTIONS_RUN:INTERNAL=0 //CXX test H5_NO_NAMESPACE:INTERNAL= //CXX test H5_NO_STD:INTERNAL= //Width for printf for type `long long' or `__int64', us. `ll H5_PRINTF_LL_WIDTH:INTERNAL="l" //CHECK_TYPE_SIZE: sizeof(char) H5_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) H5_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) H5_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) H5_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int16_t) H5_SIZEOF_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int32_t) H5_SIZEOF_INT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int64_t) H5_SIZEOF_INT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int8_t) H5_SIZEOF_INT8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int_fast16_t) H5_SIZEOF_INT_FAST16_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast32_t) H5_SIZEOF_INT_FAST32_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast64_t) H5_SIZEOF_INT_FAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_fast8_t) H5_SIZEOF_INT_FAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int_least16_t) H5_SIZEOF_INT_LEAST16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int_least32_t) H5_SIZEOF_INT_LEAST32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int_least64_t) H5_SIZEOF_INT_LEAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(int_least8_t) H5_SIZEOF_INT_LEAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(long) H5_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long double) H5_SIZEOF_LONG_DOUBLE:INTERNAL=16 //CHECK_TYPE_SIZE: sizeof(long long) H5_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off64_t) H5_SIZEOF_OFF64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off_t) H5_SIZEOF_OFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ptrdiff_t) H5_SIZEOF_PTRDIFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) H5_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(size_t) H5_SIZEOF_SIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ssize_t) H5_SIZEOF_SSIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint16_t) H5_SIZEOF_UINT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint32_t) H5_SIZEOF_UINT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(uint64_t) H5_SIZEOF_UINT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint8_t) H5_SIZEOF_UINT8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(uint_fast16_t) H5_SIZEOF_UINT_FAST16_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast32_t) H5_SIZEOF_UINT_FAST32_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast64_t) H5_SIZEOF_UINT_FAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_fast8_t) H5_SIZEOF_UINT_FAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(uint_least16_t) H5_SIZEOF_UINT_LEAST16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint_least32_t) H5_SIZEOF_UINT_LEAST32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(uint_least64_t) H5_SIZEOF_UINT_LEAST64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(uint_least8_t) H5_SIZEOF_UINT_LEAST8_T:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(unsigned) H5_SIZEOF_UNSIGNED:INTERNAL=4 //SizeOf for __int64 H5_SIZEOF___INT64:INTERNAL=0 //Other test H5_STDC_HEADERS:INTERNAL=1 //Other test H5_SYSTEM_SCOPE_THREADS:INTERNAL=1 //Other test H5_TIME_WITH_SYS_TIME:INTERNAL=1 //Checking IF compiling unsigned long long to floating-point typecasts // work H5_ULLONG_TO_FP_CAST_WORKS:INTERNAL=1 //Checking IF converting unsigned long long to long double with // precision H5_ULLONG_TO_LDOUBLE_PRECISION:INTERNAL=1 //Result of TRY_COMPILE H5_ULLONG_TO_LDOUBLE_PRECISION_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_ULLONG_TO_LDOUBLE_PRECISION_RUN:INTERNAL=0 //Checking IF accurately converting unsigned long to float values H5_ULONG_TO_FLOAT_ACCURATE:INTERNAL=1 //Result of TRY_COMPILE H5_ULONG_TO_FLOAT_ACCURATE_COMPILE:INTERNAL=TRUE //Result of TRY_RUN H5_ULONG_TO_FLOAT_ACCURATE_RUN:INTERNAL=0 //Other test H5_VSNPRINTF_WORKS:INTERNAL=1 //Result of TEST_BIG_ENDIAN H5_WORDS_BIGENDIAN:INTERNAL=0 HASH_MAP_CLASS:INTERNAL=unordered_map HASH_MAP_H:INTERNAL=tr1/unordered_map HASH_NAMESPACE:INTERNAL=std::tr1 HASH_SET_CLASS:INTERNAL=unordered_set HASH_SET_H:INTERNAL=tr1/unordered_set //Have symbol alloca HAVE_ALLOCA:INTERNAL=1 //Have include ;alloca.h HAVE_ALLOCA_H:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h HAVE_ANSIDECL_H:INTERNAL= //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h HAVE_ARPA_INET_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h HAVE_ARPA_NAMESER_H:INTERNAL=1 //Have include assert.h HAVE_ASSERT_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_ATTRIBUTE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_C99_FUNC:INTERNAL=TRUE //Have variable CLOCK_MONOTONIC HAVE_CLOCK_MONOTONIC:INTERNAL= //Result of TRY_COMPILE HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h HAVE_CTYPE_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_DIRECT:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h HAVE_DIRENT_H:INTERNAL=1 //Have include dlfcn.h HAVE_DLFCN_H:INTERNAL=1 //Have library dl;-lpthread;dl;m HAVE_DLOPEN:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;dl.h HAVE_DL_H:INTERNAL= //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h HAVE_ERRNO_H:INTERNAL=1 //Have include fcntl.h HAVE_FCNTL_H:INTERNAL=1 //Have include fenv.h HAVE_FENV_H:INTERNAL=1 //Have symbol finite HAVE_FINITE:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h HAVE_FLOAT_H:INTERNAL=1 //Have function floor HAVE_FLOOR:INTERNAL= //Have symbol fpclass HAVE_FPCLASS:INTERNAL= //Have symbol fprintf HAVE_FPRINTF:INTERNAL=1 //Have symbol fp_class HAVE_FP_CLASS:INTERNAL= //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;fp_class.h HAVE_FP_CLASS_H:INTERNAL= //Have function fseeko HAVE_FSEEKO:INTERNAL=1 //Have symbol ftime HAVE_FTIME:INTERNAL=1 //NetCDF test HAVE_FTRUNCATE:INTERNAL=1 //Result of TRY_COMPILE HAVE_FUNCTION:INTERNAL=TRUE //Test HAVE_GCC_ERROR_RETURN_TYPE HAVE_GCC_ERROR_RETURN_TYPE:INTERNAL=1 //Test HAVE_GCC_VISIBILITY HAVE_GCC_VISIBILITY:INTERNAL=1 //Result of TRY_COMPILE HAVE_GETADDRINFO_COMPILED:INTERNAL=TRUE //Have function getopt HAVE_GETOPT:INTERNAL=1 //Have symbol gettimeofday HAVE_GETTIMEOFDAY:INTERNAL=1 //Result of TRY_COMPILE HAVE_H5_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_FAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_INT_LEAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_OFF64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_OFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_PTRDIFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_SSIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_FAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UINT_LEAST8_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF_UNSIGNED:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_H5_SIZEOF___INT64:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_H5_WORDS_BIGENDIAN:INTERNAL=TRUE HAVE_HASH_MAP:INTERNAL=1 HAVE_HASH_SET:INTERNAL=1 //Result of TRY_COMPILE HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF___INT64:INTERNAL=FALSE //Have includes ieeefp.h HAVE_IEEEFP_H:INTERNAL= //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have function isascii HAVE_ISASCII:INTERNAL=1 //Have library dl; HAVE_LIBDL:INTERNAL=1 //Have include limits.h HAVE_LIMITS_H:INTERNAL=1 //Have symbol localtime HAVE_LOCALTIME:INTERNAL=1 //Have include malloc.h HAVE_MALLOC_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h HAVE_MATH_H:INTERNAL=1 //Have function memmove HAVE_MEMMOVE:INTERNAL=1 //Have include memory.h HAVE_MEMORY_H:INTERNAL=1 //Have function memset HAVE_MEMSET:INTERNAL=1 //Have function mmap HAVE_MMAP:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;nan.h HAVE_NAN_H:INTERNAL= //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;ndir.h HAVE_NDIR_H:INTERNAL= //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h HAVE_NETDB_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h HAVE_NETINET_IN_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_OFF64_T:INTERNAL=TRUE //Have function pow HAVE_POW:INTERNAL= //Have symbol printf HAVE_PRINTF:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h HAVE_PTHREAD_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h HAVE_RESOLV_H:INTERNAL=1 //Have include search.h HAVE_SEARCH_H:INTERNAL=1 //Have library dld;dl HAVE_SHLLOAD:INTERNAL= //Have symbol signal HAVE_SIGNAL:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h HAVE_SIGNAL_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_OFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SSIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UCHAR:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF__BOOL:INTERNAL=TRUE //Have symbol snprintf HAVE_SNPRINTF:INTERNAL=1 //Result of TRY_COMPILE HAVE_SOCKLEN_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SOCKLEN_T_COMPILED:INTERNAL=TRUE //Have symbol sprintf HAVE_SPRINTF:INTERNAL=1 //Have function sqrt HAVE_SQRT:INTERNAL= //Have symbol sscanf HAVE_SSCANF:INTERNAL=1 //Have symbol stat HAVE_STAT:INTERNAL=1 //Result of TRY_COMPILE HAVE_STAT64_STRUCT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STAT_ST_BLOCKS:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h HAVE_STDARG_H:INTERNAL=1 //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h;stdbool.h HAVE_STDBOOL_H:INTERNAL=1 //Have include stddef.h HAVE_STDDEF_H:INTERNAL=1 //Have include stdint.h HAVE_STDINT_H:INTERNAL=1 //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h HAVE_STDIO_H:INTERNAL=1 //Have include alloca.h;stdlib.h HAVE_STDLIB_H:INTERNAL=1 //Have function strcasecmp HAVE_STRCASECMP:INTERNAL=1 //Have function strchr HAVE_STRCHR:INTERNAL=1 //Have symbol strdup HAVE_STRDUP:INTERNAL=1 //Have symbol strerror HAVE_STRERROR:INTERNAL=1 //Have symbol strftime HAVE_STRFTIME:INTERNAL=1 //Have include strings.h HAVE_STRINGS_H:INTERNAL=1 //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h HAVE_STRING_H:INTERNAL=1 //Have symbol strndup HAVE_STRNDUP:INTERNAL=1 //Have function strrchr HAVE_STRRCHR:INTERNAL=1 //Have function strstr HAVE_STRSTR:INTERNAL=1 //Have function strtol HAVE_STRTOL:INTERNAL=1 //Have function strtoll HAVE_STRTOLL:INTERNAL=1 //Have function strtoul HAVE_STRTOUL:INTERNAL=1 //Result of TRY_COMPILE HAVE_STRUCT_TEXT_INFO:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_STRUCT_TIMEZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STRUCT_TM_TM_ZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_STRUCT_VIDEOCONFIG:INTERNAL=FALSE //NetCDF test HAVE_ST_BLKSIZE:INTERNAL=1 //Result of TRY_COMPILE HAVE_SYS_DIR_H_COMPILED:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h HAVE_SYS_MMAN_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h HAVE_SYS_SELECT_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h HAVE_SYS_SOCKET_H:INTERNAL=1 //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h HAVE_SYS_STAT_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h;sys/timeb.h HAVE_SYS_TIMEB_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=TRUE //Have include sys/time.h HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/types.h HAVE_SYS_TYPES_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_TIMEZONE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_TIME_GETTIMEOFDAY:INTERNAL=FALSE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h HAVE_TIME_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_TM_GMTOFF:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_TM_ZONE:INTERNAL=TRUE //Have include unistd.h HAVE_UNISTD_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_VA_COPY_COMPILED:INTERNAL=TRUE //Have symbol vfprintf HAVE_VFPRINTF:INTERNAL=1 //Have symbol vsnprintf HAVE_VSNPRINTF:INTERNAL=1 //Have symbol vsprintf HAVE_VSPRINTF:INTERNAL=1 //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_UINT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_UINT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_U_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_U_INT32_T:INTERNAL=TRUE //Have includes windows.h HAVE_WINDOWS_H:INTERNAL= //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_SHORT:INTERNAL=TRUE //Have symbol _stat HAVE__STAT:INTERNAL= //Result of TRY_COMPILE HAVE___TM_GMTOFF:INTERNAL=FALSE //Result of TRY_COMPILE HAVE___VA_COPY_COMPILED:INTERNAL=TRUE //Allow External Library Building (NO SVN TGZ) HDF5_ALLOW_EXTERNAL_SUPPORT:INTERNAL=OFF //Build HDF5 C++ Library HDF5_BUILD_CPP_LIB:INTERNAL=OFF //Build HIGH Level HDF5 Library HDF5_BUILD_HL_LIB:INTERNAL=ON //ADVANCED property for variable: HDF5_BUILD_STATIC_EXECS HDF5_BUILD_STATIC_EXECS-ADVANCED:INTERNAL=1 //Disable compiler warnings HDF5_DISABLE_COMPILER_WARNINGS:INTERNAL=ON //ADVANCED property for variable: HDF5_ENABLE_ALL_WARNINGS HDF5_ENABLE_ALL_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_CODESTACK HDF5_ENABLE_CODESTACK-ADVANCED:INTERNAL=1 //Enable the function stack tracing (for developer debugging). HDF5_ENABLE_CODESTACK:INTERNAL=OFF //Enable code coverage for Libraries and Programs HDF5_ENABLE_COVERAGE:INTERNAL=OFF //ADVANCED property for variable: HDF5_ENABLE_DEBUG_APIS HDF5_ENABLE_DEBUG_APIS-ADVANCED:INTERNAL=1 //Enable deprecated public API symbols HDF5_ENABLE_DEPRECATED_SYMBOLS:INTERNAL=ON //ADVANCED property for variable: HDF5_ENABLE_DIRECT_VFD HDF5_ENABLE_DIRECT_VFD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_EMBEDDED_LIBINFO HDF5_ENABLE_EMBEDDED_LIBINFO-ADVANCED:INTERNAL=1 //Enable GPFS hints for the MPI/POSIX file driver HDF5_ENABLE_GPFS:INTERNAL=OFF //ADVANCED property for variable: HDF5_ENABLE_GROUPFIVE_WARNINGS HDF5_ENABLE_GROUPFIVE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPFOUR_WARNINGS HDF5_ENABLE_GROUPFOUR_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPONE_WARNINGS HDF5_ENABLE_GROUPONE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPTHREE_WARNINGS HDF5_ENABLE_GROUPTHREE_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPTWO_WARNINGS HDF5_ENABLE_GROUPTWO_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_ENABLE_GROUPZERO_WARNINGS HDF5_ENABLE_GROUPZERO_WARNINGS-ADVANCED:INTERNAL=1 //Enable datasets larger than memory HDF5_ENABLE_HSIZET:INTERNAL=ON //Enable support for large (64-bit) files on Linux. HDF5_ENABLE_LARGE_FILE:INTERNAL=ON //Enable parallel build (requires MPI) HDF5_ENABLE_PARALLEL:INTERNAL=OFF //Use SZip Filter HDF5_ENABLE_SZIP_SUPPORT:INTERNAL=OFF //Enable Threadsafety HDF5_ENABLE_THREADSAFE:INTERNAL=OFF //Enable API tracing capability HDF5_ENABLE_TRACE:INTERNAL=OFF //Indicate that a memory checker is used HDF5_ENABLE_USING_MEMCHECKER:INTERNAL=OFF //Enable Zlib Filters HDF5_ENABLE_Z_LIB_SUPPORT:INTERNAL=ON //ADVANCED property for variable: HDF5_Enable_Clear_File_Buffers HDF5_Enable_Clear_File_Buffers-ADVANCED:INTERNAL=1 //Securely clear file buffers before writing to file HDF5_Enable_Clear_File_Buffers:INTERNAL=ON //Instrument The library HDF5_Enable_Instrument:INTERNAL=OFF //Used to pass variables between directories HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5;vtkhdf5_hl //ADVANCED property for variable: HDF5_METADATA_TRACE_FILE HDF5_METADATA_TRACE_FILE-ADVANCED:INTERNAL=1 //Enable metadata trace file collection HDF5_METADATA_TRACE_FILE:INTERNAL=OFF //ADVANCED property for variable: HDF5_NO_PACKAGES HDF5_NO_PACKAGES-ADVANCED:INTERNAL=1 //CPACK - include external libraries HDF5_PACKAGE_EXTLIBS:INTERNAL=OFF //ADVANCED property for variable: HDF5_PACK_EXAMPLES HDF5_PACK_EXAMPLES-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HDF5_PRINTF_LL_TEST_COMPILE:INTERNAL=TRUE //Result of TRY_RUN HDF5_PRINTF_LL_TEST_RUN:INTERNAL=0 //ADVANCED property for variable: HDF5_STRICT_FORMAT_CHECKS HDF5_STRICT_FORMAT_CHECKS-ADVANCED:INTERNAL=1 //Whether to perform strict file format checks HDF5_STRICT_FORMAT_CHECKS:INTERNAL=OFF //Use the HDF5 1.6.x API by default HDF5_USE_16_API_DEFAULT:INTERNAL=OFF //Use the FLETCHER32 Filter HDF5_USE_FILTER_FLETCHER32:INTERNAL=ON //Use the NBIT Filter HDF5_USE_FILTER_NBIT:INTERNAL=ON //Use the SCALEOFFSET Filter HDF5_USE_FILTER_SCALEOFFSET:INTERNAL=ON //Use the SHUFFLE Filter HDF5_USE_FILTER_SHUFFLE:INTERNAL=ON //ADVANCED property for variable: HDF5_USE_FOLDERS HDF5_USE_FOLDERS-ADVANCED:INTERNAL=1 //Use the PACKED BITS feature in h5dump HDF5_USE_H5DUMP_PACKED_BITS:INTERNAL=ON //ADVANCED property for variable: HDF5_WANT_DATA_ACCURACY HDF5_WANT_DATA_ACCURACY-ADVANCED:INTERNAL=1 //IF data accuracy is guaranteed during data conversions HDF5_WANT_DATA_ACCURACY:INTERNAL=ON //ADVANCED property for variable: HDF5_WANT_DCONV_EXCEPTION HDF5_WANT_DCONV_EXCEPTION-ADVANCED:INTERNAL=1 //exception handling functions is checked during data conversions HDF5_WANT_DCONV_EXCEPTION:INTERNAL=ON ICET_INSTALL_TARGETS:INTERNAL=IceTCore;IceTMPI;IceTGL //ADVANCED property for variable: ICET_MAGIC_K ICET_MAGIC_K-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_MAX_IMAGE_SPLIT ICET_MAX_IMAGE_SPLIT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_MPIRUN_EXE ICET_MPIRUN_EXE-ADVANCED:INTERNAL=1 //This is set from VTK_MPIRUN_EXE. ICET_MPIRUN_EXE:INTERNAL= //ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //This is set from VTK_MPI_MAX_NUMPROCS. ICET_MPI_MAX_NUMPROCS:INTERNAL= //ADVANCED property for variable: ICET_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and // VTK_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG:INTERNAL=; //ADVANCED property for variable: ICET_MPI_POSTFLAGS ICET_MPI_POSTFLAGS-ADVANCED:INTERNAL=1 //This is set from VTK_MPI_POSTFLAGS. ICET_MPI_POSTFLAGS:INTERNAL= //ADVANCED property for variable: ICET_MPI_PREFLAGS ICET_MPI_PREFLAGS-ADVANCED:INTERNAL=1 //This is set from VTK_MPI_PREFLAGS. ICET_MPI_PREFLAGS:INTERNAL= //CHECK_TYPE_SIZE: sizeof(char) ICET_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) ICET_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) ICET_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) ICET_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) ICET_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) ICET_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) ICET_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void*) ICET_SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: __int64 unknown ICET_SIZEOF___INT64:INTERNAL= //ADVANCED property for variable: ICET_USE_MPE ICET_USE_MPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_USE_MPI ICET_USE_MPI-ADVANCED:INTERNAL=1 //Use OffScreen rendering through EGL ICET_USE_OFFSCREEN_EGL:INTERNAL=OFF //ADVANCED property for variable: ICET_USE_OPENGL ICET_USE_OPENGL-ADVANCED:INTERNAL=1 //Use OffScreen Mesa ICET_USE_OSMESA:INTERNAL=TRUE //Result of TRY_COMPILE INLINE_TEST___inline:INTERNAL=TRUE //Result of TRY_COMPILE INLINE_TEST___inline__:INTERNAL=TRUE //Result of TRY_COMPILE INLINE_TEST_inline:INTERNAL=TRUE //ADVANCED property for variable: INSTALL_BIN_DIR INSTALL_BIN_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_INC_DIR INSTALL_INC_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_LIB_DIR INSTALL_LIB_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_MAN_DIR INSTALL_MAN_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_PKGCONFIG_DIR INSTALL_PKGCONFIG_DIR-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_ATOLL_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_ATOL_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_BACKTRACE_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE //Have include cxxabi.h KWSYS_CXX_HAS_CXXABIH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_CXXABI_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_DLADDR_COMPILED:INTERNAL=TRUE //Have include dlfcn.h KWSYS_CXX_HAS_DLFCNH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H_COMPILED:INTERNAL=FALSE //Have include execinfo.h KWSYS_CXX_HAS_EXECINFOH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_GETLOADAVG_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_RLIMIT64_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_SETENV_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UNSETENV_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UTIMENSAT_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UTIMES_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS__ATOI64_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_HAS___INT64_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_STAT_HAS_ST_MTIMESPEC_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=TRUE //Result of TRY_RUN KWSYS_LFS_WORKS:INTERNAL=0 //Result of TRY_COMPILE KWSYS_LFS_WORKS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE //Have include sys/types.h;ifaddrs.h KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=1 //ADVANCED property for variable: LIBRARY_OUTPUT_PATH LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1 LIBRARY_OUTPUT_PATH:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/ThirdParty/protobuf/vtkprotobuf/bin //Result of TRY_COMPILE LONE_COLON:INTERNAL=TRUE //ADVANCED property for variable: MPIEXEC MPIEXEC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_POSTFLAGS MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_PREFLAGS MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILER MPI_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_INCLUDE_PATH MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LIBRARIES MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LINK_FLAGS MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILER MPI_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILE_FLAGS MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_INCLUDE_PATH MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=0 //ADVANCED property for variable: MPI_C_LIBRARIES MPI_C_LIBRARIES-ADVANCED:INTERNAL=0 //ADVANCED property for variable: MPI_C_LINK_FLAGS MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_EXTRA_LIBRARY MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=1 //Scratch variable for MPI header detection MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND //Scratch variable for MPI lib detection MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND //ADVANCED property for variable: MPI_LIBRARY MPI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_AutobahnPython Module_AutobahnPython-ADVANCED:INTERNAL=1 //Request building AutobahnPython Module_AutobahnPython:INTERNAL=OFF //ADVANCED property for variable: Module_PoissonReconstruction Module_PoissonReconstruction-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_Pygments Module_Pygments-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_SixPython Module_SixPython-ADVANCED:INTERNAL=1 //Request building SixPython Module_SixPython:INTERNAL=OFF //ADVANCED property for variable: Module_Twisted Module_Twisted-ADVANCED:INTERNAL=1 //Request building Twisted Module_Twisted:INTERNAL=OFF //ADVANCED property for variable: Module_VisItLib Module_VisItLib-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_WikiExamples Module_WikiExamples-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_ZopeInterface Module_ZopeInterface-ADVANCED:INTERNAL=1 //Request building ZopeInterface Module_ZopeInterface:INTERNAL=OFF //ADVANCED property for variable: Module_pqApplicationComponents Module_pqApplicationComponents-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqComponents Module_pqComponents-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqCore Module_pqCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqDeprecated Module_pqDeprecated-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqPython Module_pqPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqWidgets Module_pqWidgets-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_smTestDriver Module_smTestDriver-ADVANCED:INTERNAL=1 //Request building smTestDriver Module_smTestDriver:INTERNAL=OFF //ADVANCED property for variable: Module_vtkAcceleratorsDax Module_vtkAcceleratorsDax-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkAcceleratorsPiston Module_vtkAcceleratorsPiston-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkAddon Module_vtkAddon-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkChartsCore Module_vtkChartsCore-ADVANCED:INTERNAL=1 //Request building vtkChartsCore Module_vtkChartsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkClientServer Module_vtkClientServer-ADVANCED:INTERNAL=1 //Request building vtkClientServer Module_vtkClientServer:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonColor Module_vtkCommonColor-ADVANCED:INTERNAL=1 //Request building vtkCommonColor Module_vtkCommonColor:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonComputationalGeometry Module_vtkCommonComputationalGeometry-ADVANCED:INTERNAL=1 //Request building vtkCommonComputationalGeometry Module_vtkCommonComputationalGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonCore Module_vtkCommonCore-ADVANCED:INTERNAL=1 //Request building vtkCommonCore Module_vtkCommonCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonDataModel Module_vtkCommonDataModel-ADVANCED:INTERNAL=1 //Request building vtkCommonDataModel Module_vtkCommonDataModel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonExecutionModel Module_vtkCommonExecutionModel-ADVANCED:INTERNAL=1 //Request building vtkCommonExecutionModel Module_vtkCommonExecutionModel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonMath Module_vtkCommonMath-ADVANCED:INTERNAL=1 //Request building vtkCommonMath Module_vtkCommonMath:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonMisc Module_vtkCommonMisc-ADVANCED:INTERNAL=1 //Request building vtkCommonMisc Module_vtkCommonMisc:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonSystem Module_vtkCommonSystem-ADVANCED:INTERNAL=1 //Request building vtkCommonSystem Module_vtkCommonSystem:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonTransforms Module_vtkCommonTransforms-ADVANCED:INTERNAL=1 //Request building vtkCommonTransforms Module_vtkCommonTransforms:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCosmoHaloFinder Module_vtkCosmoHaloFinder-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkDICOM Module_vtkDICOM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkDICOMParser Module_vtkDICOMParser-ADVANCED:INTERNAL=1 //Request building vtkDICOMParser Module_vtkDICOMParser:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsChemistry Module_vtkDomainsChemistry-ADVANCED:INTERNAL=1 //Request building vtkDomainsChemistry Module_vtkDomainsChemistry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsChemistryOpenGL2 Module_vtkDomainsChemistryOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkDomainsChemistryOpenGL2 Module_vtkDomainsChemistryOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsMicroscopy Module_vtkDomainsMicroscopy-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersAMR Module_vtkFiltersAMR-ADVANCED:INTERNAL=1 //Request building vtkFiltersAMR Module_vtkFiltersAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersCore Module_vtkFiltersCore-ADVANCED:INTERNAL=1 //Request building vtkFiltersCore Module_vtkFiltersCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersExtraction Module_vtkFiltersExtraction-ADVANCED:INTERNAL=1 //Request building vtkFiltersExtraction Module_vtkFiltersExtraction:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersFlowPaths Module_vtkFiltersFlowPaths-ADVANCED:INTERNAL=1 //Request building vtkFiltersFlowPaths Module_vtkFiltersFlowPaths:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeneral Module_vtkFiltersGeneral-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeneral Module_vtkFiltersGeneral:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeneric Module_vtkFiltersGeneric-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeneric Module_vtkFiltersGeneric:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeometry Module_vtkFiltersGeometry-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeometry Module_vtkFiltersGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersHybrid Module_vtkFiltersHybrid-ADVANCED:INTERNAL=1 //Request building vtkFiltersHybrid Module_vtkFiltersHybrid:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersHyperTree Module_vtkFiltersHyperTree-ADVANCED:INTERNAL=1 //Request building vtkFiltersHyperTree Module_vtkFiltersHyperTree:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersImaging Module_vtkFiltersImaging-ADVANCED:INTERNAL=1 //Request building vtkFiltersImaging Module_vtkFiltersImaging:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersMatlab Module_vtkFiltersMatlab-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersModeling Module_vtkFiltersModeling-ADVANCED:INTERNAL=1 //Request building vtkFiltersModeling Module_vtkFiltersModeling:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallel Module_vtkFiltersParallel-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallel Module_vtkFiltersParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelDIY2 Module_vtkFiltersParallelDIY2-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelDIY2 Module_vtkFiltersParallelDIY2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelImaging Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelImaging Module_vtkFiltersParallelImaging:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelMPI Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelMPI Module_vtkFiltersParallelMPI:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersPoints Module_vtkFiltersPoints-ADVANCED:INTERNAL=1 //Request building vtkFiltersPoints Module_vtkFiltersPoints:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersProgrammable Module_vtkFiltersProgrammable-ADVANCED:INTERNAL=1 //Request building vtkFiltersProgrammable Module_vtkFiltersProgrammable:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersPython Module_vtkFiltersPython-ADVANCED:INTERNAL=1 //Request building vtkFiltersPython Module_vtkFiltersPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersReebGraph Module_vtkFiltersReebGraph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSMP Module_vtkFiltersSMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSelection Module_vtkFiltersSelection-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSources Module_vtkFiltersSources-ADVANCED:INTERNAL=1 //Request building vtkFiltersSources Module_vtkFiltersSources:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersStatistics Module_vtkFiltersStatistics-ADVANCED:INTERNAL=1 //Request building vtkFiltersStatistics Module_vtkFiltersStatistics:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersStatisticsGnuR Module_vtkFiltersStatisticsGnuR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersTexture Module_vtkFiltersTexture-ADVANCED:INTERNAL=1 //Request building vtkFiltersTexture Module_vtkFiltersTexture:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersVerdict Module_vtkFiltersVerdict-ADVANCED:INTERNAL=1 //Request building vtkFiltersVerdict Module_vtkFiltersVerdict:INTERNAL=OFF //ADVANCED property for variable: Module_vtkGUISupportQt Module_vtkGUISupportQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGUISupportQtOpenGL Module_vtkGUISupportQtOpenGL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGUISupportQtSQL Module_vtkGUISupportQtSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGUISupportQtWebkit Module_vtkGUISupportQtWebkit-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGeovisCore Module_vtkGeovisCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOADIOS Module_vtkIOADIOS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOAMR Module_vtkIOAMR-ADVANCED:INTERNAL=1 //Request building vtkIOAMR Module_vtkIOAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOCore Module_vtkIOCore-ADVANCED:INTERNAL=1 //Request building vtkIOCore Module_vtkIOCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOEnSight Module_vtkIOEnSight-ADVANCED:INTERNAL=1 //Request building vtkIOEnSight Module_vtkIOEnSight:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExodus Module_vtkIOExodus-ADVANCED:INTERNAL=1 //Request building vtkIOExodus Module_vtkIOExodus:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExport Module_vtkIOExport-ADVANCED:INTERNAL=1 //Request building vtkIOExport Module_vtkIOExport:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExportOpenGL Module_vtkIOExportOpenGL-ADVANCED:INTERNAL=1 //Request building vtkIOExportOpenGL Module_vtkIOExportOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExportOpenGL2 Module_vtkIOExportOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkIOExportOpenGL2 Module_vtkIOExportOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOFFMPEG Module_vtkIOFFMPEG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGDAL Module_vtkIOGDAL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGeoJSON Module_vtkIOGeoJSON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGeometry Module_vtkIOGeometry-ADVANCED:INTERNAL=1 //Request building vtkIOGeometry Module_vtkIOGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOImage Module_vtkIOImage-ADVANCED:INTERNAL=1 //Request building vtkIOImage Module_vtkIOImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOImport Module_vtkIOImport-ADVANCED:INTERNAL=1 //Request building vtkIOImport Module_vtkIOImport:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOInfovis Module_vtkIOInfovis-ADVANCED:INTERNAL=1 //Request building vtkIOInfovis Module_vtkIOInfovis:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOLSDyna Module_vtkIOLSDyna-ADVANCED:INTERNAL=1 //Request building vtkIOLSDyna Module_vtkIOLSDyna:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOLegacy Module_vtkIOLegacy-ADVANCED:INTERNAL=1 //Request building vtkIOLegacy Module_vtkIOLegacy:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMINC Module_vtkIOMINC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOMPIImage Module_vtkIOMPIImage-ADVANCED:INTERNAL=1 //Request building vtkIOMPIImage Module_vtkIOMPIImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMPIParallel Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1 //Request building vtkIOMPIParallel Module_vtkIOMPIParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMovie Module_vtkIOMovie-ADVANCED:INTERNAL=1 //Request building vtkIOMovie Module_vtkIOMovie:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMySQL Module_vtkIOMySQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIONetCDF Module_vtkIONetCDF-ADVANCED:INTERNAL=1 //Request building vtkIONetCDF Module_vtkIONetCDF:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOODBC Module_vtkIOODBC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOPLY Module_vtkIOPLY-ADVANCED:INTERNAL=1 //Request building vtkIOPLY Module_vtkIOPLY:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallel Module_vtkIOParallel-ADVANCED:INTERNAL=1 //Request building vtkIOParallel Module_vtkIOParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelExodus Module_vtkIOParallelExodus-ADVANCED:INTERNAL=1 //Request building vtkIOParallelExodus Module_vtkIOParallelExodus:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelLSDyna Module_vtkIOParallelLSDyna-ADVANCED:INTERNAL=1 //Request building vtkIOParallelLSDyna Module_vtkIOParallelLSDyna:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelNetCDF Module_vtkIOParallelNetCDF-ADVANCED:INTERNAL=1 //Request building vtkIOParallelNetCDF Module_vtkIOParallelNetCDF:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelXML Module_vtkIOParallelXML-ADVANCED:INTERNAL=1 //Request building vtkIOParallelXML Module_vtkIOParallelXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOPostgreSQL Module_vtkIOPostgreSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOSQL Module_vtkIOSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOTecplotTable Module_vtkIOTecplotTable-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOVPIC Module_vtkIOVPIC-ADVANCED:INTERNAL=1 //Request building vtkIOVPIC Module_vtkIOVPIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOVideo Module_vtkIOVideo-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOVisItBridge Module_vtkIOVisItBridge-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOXML Module_vtkIOXML-ADVANCED:INTERNAL=1 //Request building vtkIOXML Module_vtkIOXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXMLParser Module_vtkIOXMLParser-ADVANCED:INTERNAL=1 //Request building vtkIOXMLParser Module_vtkIOXMLParser:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXdmf2 Module_vtkIOXdmf2-ADVANCED:INTERNAL=1 //Request building vtkIOXdmf2 Module_vtkIOXdmf2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXdmf3 Module_vtkIOXdmf3-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingColor Module_vtkImagingColor-ADVANCED:INTERNAL=1 //Request building vtkImagingColor Module_vtkImagingColor:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingCore Module_vtkImagingCore-ADVANCED:INTERNAL=1 //Request building vtkImagingCore Module_vtkImagingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingFourier Module_vtkImagingFourier-ADVANCED:INTERNAL=1 //Request building vtkImagingFourier Module_vtkImagingFourier:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingGeneral Module_vtkImagingGeneral-ADVANCED:INTERNAL=1 //Request building vtkImagingGeneral Module_vtkImagingGeneral:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingHybrid Module_vtkImagingHybrid-ADVANCED:INTERNAL=1 //Request building vtkImagingHybrid Module_vtkImagingHybrid:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingMath Module_vtkImagingMath-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingMorphological Module_vtkImagingMorphological-ADVANCED:INTERNAL=1 //Request building vtkImagingMorphological Module_vtkImagingMorphological:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingSources Module_vtkImagingSources-ADVANCED:INTERNAL=1 //Request building vtkImagingSources Module_vtkImagingSources:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingStatistics Module_vtkImagingStatistics-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingStencil Module_vtkImagingStencil-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisBoost Module_vtkInfovisBoost-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisBoostGraphAlgorithms Module_vtkInfovisBoostGraphAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisCore Module_vtkInfovisCore-ADVANCED:INTERNAL=1 //Request building vtkInfovisCore Module_vtkInfovisCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInfovisLayout Module_vtkInfovisLayout-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisParallel Module_vtkInfovisParallel-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInteractionImage Module_vtkInteractionImage-ADVANCED:INTERNAL=1 //Request building vtkInteractionImage Module_vtkInteractionImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInteractionStyle Module_vtkInteractionStyle-ADVANCED:INTERNAL=1 //Request building vtkInteractionStyle Module_vtkInteractionStyle:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInteractionWidgets Module_vtkInteractionWidgets-ADVANCED:INTERNAL=1 //Request building vtkInteractionWidgets Module_vtkInteractionWidgets:INTERNAL=OFF //ADVANCED property for variable: Module_vtkMetaIO Module_vtkMetaIO-ADVANCED:INTERNAL=1 //Request building vtkMetaIO Module_vtkMetaIO:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVAnimation Module_vtkPVAnimation-ADVANCED:INTERNAL=1 //Request building vtkPVAnimation Module_vtkPVAnimation:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCatalyst Module_vtkPVCatalyst-ADVANCED:INTERNAL=1 //Request building vtkPVCatalyst Module_vtkPVCatalyst:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPVClientServerCoreCore Module_vtkPVClientServerCoreCore-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreCore Module_vtkPVClientServerCoreCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVClientServerCoreDefault Module_vtkPVClientServerCoreDefault-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreDefault Module_vtkPVClientServerCoreDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVClientServerCoreRendering Module_vtkPVClientServerCoreRendering-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreRendering Module_vtkPVClientServerCoreRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCommon Module_vtkPVCommon-ADVANCED:INTERNAL=1 //Request building vtkPVCommon Module_vtkPVCommon:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerImplementationCore Module_vtkPVServerImplementationCore-ADVANCED:INTERNAL=1 //Request building vtkPVServerImplementationCore Module_vtkPVServerImplementationCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerImplementationRendering Module_vtkPVServerImplementationRendering-ADVANCED:INTERNAL=1 //Request building vtkPVServerImplementationRendering Module_vtkPVServerImplementationRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerApplication Module_vtkPVServerManagerApplication-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerApplication Module_vtkPVServerManagerApplication:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerCore Module_vtkPVServerManagerCore-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerCore Module_vtkPVServerManagerCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerDefault Module_vtkPVServerManagerDefault-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerDefault Module_vtkPVServerManagerDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerRendering Module_vtkPVServerManagerRendering-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerRendering Module_vtkPVServerManagerRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsCGNSReader Module_vtkPVVTKExtensionsCGNSReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPVVTKExtensionsCore Module_vtkPVVTKExtensionsCore-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsCore Module_vtkPVVTKExtensionsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPVVTKExtensionsDefault Module_vtkPVVTKExtensionsDefault-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsDefault Module_vtkPVVTKExtensionsDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsPoints Module_vtkPVVTKExtensionsPoints-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsPoints Module_vtkPVVTKExtensionsPoints:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsRendering Module_vtkPVVTKExtensionsRendering-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsRendering Module_vtkPVVTKExtensionsRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWeb Module_vtkParaViewWeb-ADVANCED:INTERNAL=1 //Request building vtkParaViewWeb Module_vtkParaViewWeb:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebApplications Module_vtkParaViewWebApplications-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebApplications Module_vtkParaViewWebApplications:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebCore Module_vtkParaViewWebCore-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebCore Module_vtkParaViewWebCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebDocumentation Module_vtkParaViewWebDocumentation-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkParaViewWebPython Module_vtkParaViewWebPython-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebPython Module_vtkParaViewWebPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebWidgets Module_vtkParaViewWebWidgets-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebWidgets Module_vtkParaViewWebWidgets:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelCore Module_vtkParallelCore-ADVANCED:INTERNAL=1 //Request building vtkParallelCore Module_vtkParallelCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelMPI Module_vtkParallelMPI-ADVANCED:INTERNAL=1 //Request building vtkParallelMPI Module_vtkParallelMPI:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelMPI4Py Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1 //Request building vtkParallelMPI4Py Module_vtkParallelMPI4Py:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParseOGLExt Module_vtkParseOGLExt-ADVANCED:INTERNAL=1 //Request building vtkParseOGLExt Module_vtkParseOGLExt:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPointCloud Module_vtkPointCloud-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPython Module_vtkPython-ADVANCED:INTERNAL=1 //Request building vtkPython Module_vtkPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPythonInterpreter Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 //Request building vtkPythonInterpreter Module_vtkPythonInterpreter:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingAnnotation Module_vtkRenderingAnnotation-ADVANCED:INTERNAL=1 //Request building vtkRenderingAnnotation Module_vtkRenderingAnnotation:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContext2D Module_vtkRenderingContext2D-ADVANCED:INTERNAL=1 //Request building vtkRenderingContext2D Module_vtkRenderingContext2D:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContextOpenGL Module_vtkRenderingContextOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingContextOpenGL Module_vtkRenderingContextOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContextOpenGL2 Module_vtkRenderingContextOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingContextOpenGL2 Module_vtkRenderingContextOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingCore Module_vtkRenderingCore-ADVANCED:INTERNAL=1 //Request building vtkRenderingCore Module_vtkRenderingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingExternal Module_vtkRenderingExternal-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingFreeType Module_vtkRenderingFreeType-ADVANCED:INTERNAL=1 //Request building vtkRenderingFreeType Module_vtkRenderingFreeType:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingFreeTypeFontConfig Module_vtkRenderingFreeTypeFontConfig-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingGL2PS Module_vtkRenderingGL2PS-ADVANCED:INTERNAL=1 //Request building vtkRenderingGL2PS Module_vtkRenderingGL2PS:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingGL2PSOpenGL2 Module_vtkRenderingGL2PSOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingGL2PSOpenGL2 Module_vtkRenderingGL2PSOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingImage Module_vtkRenderingImage-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingLIC Module_vtkRenderingLIC-ADVANCED:INTERNAL=1 //Request building vtkRenderingLIC Module_vtkRenderingLIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLICOpenGL2 Module_vtkRenderingLICOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingLICOpenGL2 Module_vtkRenderingLICOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLOD Module_vtkRenderingLOD-ADVANCED:INTERNAL=1 //Request building vtkRenderingLOD Module_vtkRenderingLOD:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLabel Module_vtkRenderingLabel-ADVANCED:INTERNAL=1 //Request building vtkRenderingLabel Module_vtkRenderingLabel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingMatplotlib Module_vtkRenderingMatplotlib-ADVANCED:INTERNAL=1 //Request building vtkRenderingMatplotlib Module_vtkRenderingMatplotlib:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOSPRay Module_vtkRenderingOSPRay-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingOpenGL Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingOpenGL Module_vtkRenderingOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingParallel Module_vtkRenderingParallel-ADVANCED:INTERNAL=1 //Request building vtkRenderingParallel Module_vtkRenderingParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingParallelLIC Module_vtkRenderingParallelLIC-ADVANCED:INTERNAL=1 //Request building vtkRenderingParallelLIC Module_vtkRenderingParallelLIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingQt Module_vtkRenderingQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingSceneGraph Module_vtkRenderingSceneGraph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingTk Module_vtkRenderingTk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingVolume Module_vtkRenderingVolume-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolume Module_vtkRenderingVolume:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeAMR Module_vtkRenderingVolumeAMR-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeAMR Module_vtkRenderingVolumeAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL Module_vtkRenderingVolumeOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeOpenGL Module_vtkRenderingVolumeOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL2 Module_vtkRenderingVolumeOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeOpenGL2 Module_vtkRenderingVolumeOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkTclTk Module_vtkTclTk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingCore Module_vtkTestingCore-ADVANCED:INTERNAL=1 //Request building vtkTestingCore Module_vtkTestingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkTestingGenericBridge Module_vtkTestingGenericBridge-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingIOSQL Module_vtkTestingIOSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingRendering Module_vtkTestingRendering-ADVANCED:INTERNAL=1 //Request building vtkTestingRendering Module_vtkTestingRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesBenchmarks Module_vtkUtilitiesBenchmarks-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkUtilitiesColorSeriesToXML Module_vtkUtilitiesColorSeriesToXML-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkUtilitiesEncodeString Module_vtkUtilitiesEncodeString-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesEncodeString Module_vtkUtilitiesEncodeString:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesHashSource Module_vtkUtilitiesHashSource-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesHashSource Module_vtkUtilitiesHashSource:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkUtilitiesProcessXML Module_vtkUtilitiesProcessXML-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesProcessXML Module_vtkUtilitiesProcessXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesWrapClientServer Module_vtkUtilitiesWrapClientServer-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesWrapClientServer Module_vtkUtilitiesWrapClientServer:INTERNAL=OFF //ADVANCED property for variable: Module_vtkVPIC Module_vtkVPIC-ADVANCED:INTERNAL=1 //Request building vtkVPIC Module_vtkVPIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsContext2D Module_vtkViewsContext2D-ADVANCED:INTERNAL=1 //Request building vtkViewsContext2D Module_vtkViewsContext2D:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsCore Module_vtkViewsCore-ADVANCED:INTERNAL=1 //Request building vtkViewsCore Module_vtkViewsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsGeovis Module_vtkViewsGeovis-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkViewsInfovis Module_vtkViewsInfovis-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkViewsQt Module_vtkViewsQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebApplications Module_vtkWebApplications-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebCore Module_vtkWebCore-ADVANCED:INTERNAL=1 //Request building vtkWebCore Module_vtkWebCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWebGLExporter Module_vtkWebGLExporter-ADVANCED:INTERNAL=1 //Request building vtkWebGLExporter Module_vtkWebGLExporter:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWebInstall Module_vtkWebInstall-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebJavaScript Module_vtkWebJavaScript-ADVANCED:INTERNAL=1 //Request building vtkWebJavaScript Module_vtkWebJavaScript:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWebPython Module_vtkWebPython-ADVANCED:INTERNAL=1 //Request building vtkWebPython Module_vtkWebPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWrappingJava Module_vtkWrappingJava-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingPythonCore Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingTcl Module_vtkWrappingTcl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingTools Module_vtkWrappingTools-ADVANCED:INTERNAL=1 //Request building vtkWrappingTools Module_vtkWrappingTools:INTERNAL=OFF //ADVANCED property for variable: Module_vtkalglib Module_vtkalglib-ADVANCED:INTERNAL=1 //Request building vtkalglib Module_vtkalglib:INTERNAL=OFF //ADVANCED property for variable: Module_vtkdiy2 Module_vtkdiy2-ADVANCED:INTERNAL=1 //Request building vtkdiy2 Module_vtkdiy2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkexodusII Module_vtkexodusII-ADVANCED:INTERNAL=1 //Request building vtkexodusII Module_vtkexodusII:INTERNAL=OFF //ADVANCED property for variable: Module_vtkexpat Module_vtkexpat-ADVANCED:INTERNAL=1 //Request building vtkexpat Module_vtkexpat:INTERNAL=OFF //ADVANCED property for variable: Module_vtkfreetype Module_vtkfreetype-ADVANCED:INTERNAL=1 //Request building vtkfreetype Module_vtkfreetype:INTERNAL=OFF //ADVANCED property for variable: Module_vtkgl2ps Module_vtkgl2ps-ADVANCED:INTERNAL=1 //Request building vtkgl2ps Module_vtkgl2ps:INTERNAL=OFF //ADVANCED property for variable: Module_vtkglew Module_vtkglew-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkhdf5 Module_vtkhdf5-ADVANCED:INTERNAL=1 //Request building vtkhdf5 Module_vtkhdf5:INTERNAL=OFF //ADVANCED property for variable: Module_vtkicet Module_vtkicet-ADVANCED:INTERNAL=1 //Request building vtkicet Module_vtkicet:INTERNAL=OFF //ADVANCED property for variable: Module_vtkjpeg Module_vtkjpeg-ADVANCED:INTERNAL=1 //Request building vtkjpeg Module_vtkjpeg:INTERNAL=OFF //ADVANCED property for variable: Module_vtkjsoncpp Module_vtkjsoncpp-ADVANCED:INTERNAL=1 //Request building vtkjsoncpp Module_vtkjsoncpp:INTERNAL=OFF //ADVANCED property for variable: Module_vtkkwiml Module_vtkkwiml-ADVANCED:INTERNAL=1 //Request building vtkkwiml Module_vtkkwiml:INTERNAL=OFF //ADVANCED property for variable: Module_vtklibproj4 Module_vtklibproj4-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtklibxml2 Module_vtklibxml2-ADVANCED:INTERNAL=1 //Request building vtklibxml2 Module_vtklibxml2:INTERNAL=OFF //ADVANCED property for variable: Module_vtklz4 Module_vtklz4-ADVANCED:INTERNAL=1 //Request building vtklz4 Module_vtklz4:INTERNAL=OFF //ADVANCED property for variable: Module_vtkmpi4py Module_vtkmpi4py-ADVANCED:INTERNAL=1 //Request building vtkmpi4py Module_vtkmpi4py:INTERNAL=OFF //ADVANCED property for variable: Module_vtknetcdf Module_vtknetcdf-ADVANCED:INTERNAL=1 //Request building vtknetcdf Module_vtknetcdf:INTERNAL=OFF //ADVANCED property for variable: Module_vtkoggtheora Module_vtkoggtheora-ADVANCED:INTERNAL=1 //Request building vtkoggtheora Module_vtkoggtheora:INTERNAL=OFF //ADVANCED property for variable: Module_vtkpng Module_vtkpng-ADVANCED:INTERNAL=1 //Request building vtkpng Module_vtkpng:INTERNAL=OFF //ADVANCED property for variable: Module_vtkprotobuf Module_vtkprotobuf-ADVANCED:INTERNAL=1 //Request building vtkprotobuf Module_vtkprotobuf:INTERNAL=OFF //ADVANCED property for variable: Module_vtkpugixml Module_vtkpugixml-ADVANCED:INTERNAL=1 //Request building vtkpugixml Module_vtkpugixml:INTERNAL=OFF //ADVANCED property for variable: Module_vtkqttesting Module_vtkqttesting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtksqlite Module_vtksqlite-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtksys Module_vtksys-ADVANCED:INTERNAL=1 //Request building vtksys Module_vtksys:INTERNAL=OFF //ADVANCED property for variable: Module_vtktiff Module_vtktiff-ADVANCED:INTERNAL=1 //Request building vtktiff Module_vtktiff:INTERNAL=OFF //ADVANCED property for variable: Module_vtkverdict Module_vtkverdict-ADVANCED:INTERNAL=1 //Request building vtkverdict Module_vtkverdict:INTERNAL=OFF //ADVANCED property for variable: Module_vtkxdmf2 Module_vtkxdmf2-ADVANCED:INTERNAL=1 //Request building vtkxdmf2 Module_vtkxdmf2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkxdmf3 Module_vtkxdmf3-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkzlib Module_vtkzlib-ADVANCED:INTERNAL=1 //Request building vtkzlib Module_vtkzlib:INTERNAL=OFF //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_NELEMS NETCDF4_CHUNK_CACHE_NELEMS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_PREEMPTION NETCDF4_CHUNK_CACHE_PREEMPTION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_SIZE NETCDF4_CHUNK_CACHE_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNKS_IN_CACHE NETCDF4_DEFAULT_CHUNKS_IN_CACHE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNK_SIZE NETCDF4_DEFAULT_CHUNK_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_MAX_DEFAULT_CACHE_SIZE NETCDF4_MAX_DEFAULT_CACHE_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF_ENABLE_CXX NETCDF_ENABLE_CXX-ADVANCED:INTERNAL=1 //Have library c NOT_NEED_LIBNSL:INTERNAL=1 //CXX test NO_STATIC_CAST:INTERNAL= //CHECK_TYPE_SIZE: sizeof(off64_t) OFF64_T:INTERNAL=8 //CXX test OLD_HEADER_FILENAME:INTERNAL= //ADVANCED property for variable: OSMESA_INCLUDE_DIR OSMESA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OSMESA_LIBRARY OSMESA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_CDIReader PARAVIEW_AUTOLOAD_PLUGIN_CDIReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GMVReader PARAVIEW_AUTOLOAD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_H5PartReader PARAVIEW_AUTOLOAD_PLUGIN_H5PartReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_Moments PARAVIEW_AUTOLOAD_PLUGIN_Moments-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_PacMan PARAVIEW_AUTOLOAD_PLUGIN_PacMan-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_PointSprite PARAVIEW_AUTOLOAD_PLUGIN_PointSprite-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_RGBZView PARAVIEW_AUTOLOAD_PLUGIN_RGBZView-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SLACTools PARAVIEW_AUTOLOAD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SciberQuestToolKit PARAVIEW_AUTOLOAD_PLUGIN_SciberQuestToolKit-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_UncertaintyRendering PARAVIEW_AUTOLOAD_PLUGIN_UncertaintyRendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_CATALYST_ADAPTORS PARAVIEW_BUILD_CATALYST_ADAPTORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ArrowGlyph PARAVIEW_BUILD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CDIReader PARAVIEW_BUILD_PLUGIN_CDIReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GMVReader PARAVIEW_BUILD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_H5PartReader PARAVIEW_BUILD_PLUGIN_H5PartReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_InSituExodus PARAVIEW_BUILD_PLUGIN_InSituExodus-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_MantaView PARAVIEW_BUILD_PLUGIN_MantaView-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PointSprite PARAVIEW_BUILD_PLUGIN_PointSprite-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_RGBZView PARAVIEW_BUILD_PLUGIN_RGBZView-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingParticles PARAVIEW_BUILD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_UncertaintyRendering PARAVIEW_BUILD_PLUGIN_UncertaintyRendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_WEB_DOCUMENTATION PARAVIEW_BUILD_WEB_DOCUMENTATION-ADVANCED:INTERNAL=1 //List of modules to CS wrap PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonColor;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkInfovisCore;vtkFiltersGeometry;vtkFiltersSources;vtkRenderingCore;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkPythonInterpreter;vtkIOCore;vtkIOGeometry;vtkIOXMLParser;vtkIOXML;vtkDomainsChemistry;vtkIOLegacy;vtkParallelCore;vtkFiltersAMR;vtkFiltersFlowPaths;vtkFiltersGeneric;vtkImagingSources;vtkFiltersHybrid;vtkFiltersHyperTree;vtkImagingGeneral;vtkFiltersImaging;vtkFiltersModeling;vtkFiltersParallel;vtkParallelMPI;vtkFiltersParallelDIY2;vtkFiltersParallelFlowPaths;vtkFiltersParallelGeometry;vtkFiltersParallelImaging;vtkFiltersParallelMPI;vtkFiltersParallelStatistics;vtkFiltersPoints;vtkFiltersProgrammable;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOEnSight;vtkIOExodus;vtkIOImage;vtkImagingHybrid;vtkRenderingOpenGL;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkIOExport;vtkImagingColor;vtkRenderingAnnotation;vtkRenderingLabel;vtkIOExportOpenGL;vtkIOImport;vtkIOInfovis;vtkIOLSDyna;vtkIOMPIImage;vtkIONetCDF;vtkIOParallel;vtkIOMPIParallel;vtkIOMovie;vtkIOPLY;vtkIOParallelExodus;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOParallelXML;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionStyle;vtkRenderingVolume;vtkInteractionWidgets;vtkInteractionImage;vtkPVCommon;vtkPVVTKExtensionsCore;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkRenderingLIC;vtkRenderingMatplotlib;vtkRenderingParallel;vtkRenderingParallelLIC;vtkRenderingVolumeOpenGL;vtkRenderingVolumeAMR;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkViewsCore;vtkViewsContext2D;vtkWebGLExporter;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkPVVTKExtensionsPoints;vtkParallelMPI4Py;vtkRenderingLOD;vtkPVServerManagerApplication;vtkPVCatalyst;vtkWebCore;vtkParaViewWebCore //ADVANCED property for variable: PARAVIEW_DATA_EXCLUDE_FROM_ALL PARAVIEW_DATA_EXCLUDE_FROM_ALL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_DATA_STORE PARAVIEW_DATA_STORE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_COSMOTOOLS PARAVIEW_ENABLE_COSMOTOOLS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_MATPLOTLIB PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_SPYPLOT_MARKERS PARAVIEW_ENABLE_SPYPLOT_MARKERS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_WEB PARAVIEW_ENABLE_WEB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTRA_EXTERNAL_PLUGINS PARAVIEW_EXTRA_EXTERNAL_PLUGINS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_FREEZE_PYTHON PARAVIEW_FREEZE_PYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_INITIALIZE_MPI_ON_CLIENT PARAVIEW_INITIALIZE_MPI_ON_CLIENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_PLUGIN_LOADER_PATHS PARAVIEW_PLUGIN_LOADER_PATHS-ADVANCED:INTERNAL=1 //Server Manager XMLs PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/Default/settings.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/Animation/animation.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/VTKExtensions/Points/points.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/proxies_mpi.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/proxies_opengl1.xml;/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml //ADVANCED property for variable: PARAVIEW_USE_ATP PARAVIEW_USE_ATP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_ICE_T PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_UNIFIED_BINDINGS PARAVIEW_USE_UNIFIED_BINDINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_CLEAN_COMMAND PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_CLIENT PV_TEST_CLIENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_INIT_COMMAND PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_USE_RANDOM_PORTS PV_TEST_USE_RANDOM_PORTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.MPE PYTHON_ENABLE_MODULE_mpi4py.MPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_EXECUTABLE PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_EXTRA_LIBS PYTHON_EXTRA_LIBS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_INCLUDE_DIR PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_LIBRARY PYTHON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.MPE_BUILD_SHARED PYTHON_MODULE_mpi4py.MPE_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.dl_BUILD_SHARED PYTHON_MODULE_mpi4py.dl_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_UTIL_LIBRARY PYTHON_UTIL_LIBRARY-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off_t) SIZEOF_OFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ptrdiff_t) SIZEOF_PTRDIFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(size_t) SIZEOF_SIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ssize_t) SIZEOF_SSIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: uchar unknown SIZEOF_UCHAR:INTERNAL= //CHECK_TYPE_SIZE: sizeof(void *) SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(_Bool) SIZEOF__BOOL:INTERNAL=1 //ADVANCED property for variable: SQTK_CUDA SQTK_CUDA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SQTK_DEBUG SQTK_DEBUG-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE STDC_HEADERS:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_MAP:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_SET:INTERNAL=TRUE //Result of TRY_COMPILE SUPPORT_IP6_COMPILED:INTERNAL=TRUE //ADVANCED property for variable: SURFACELIC_PLUGIN_TESTING SURFACELIC_PLUGIN_TESTING-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE SYSTEM_SCOPE_THREADS:INTERNAL=TRUE //Result of TRY_COMPILE TEST_DIRECT_VFD_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN TEST_DIRECT_VFD_WORKS_RUN:INTERNAL=0 //Performing TEST_LFS_WORKS TEST_LFS_WORKS:INTERNAL=1 //Result of TRY_COMPILE TEST_LFS_WORKS_COMPILE:INTERNAL=TRUE //Result of TRY_RUN TEST_LFS_WORKS_RUN:INTERNAL=0 //Result of TRY_COMPILE TIME_WITH_SYS_TIME:INTERNAL=TRUE //ADVANCED property for variable: USE_COMPILER_HIDDEN_VISIBILITY USE_COMPILER_HIDDEN_VISIBILITY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VERDICT_BUILD_DOC VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1 //Build the 2007 Verdict User Manual VERDICT_BUILD_DOC:INTERNAL=OFF //ADVANCED property for variable: VERDICT_ENABLE_TESTING VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1 //Should tests of the VERDICT library be built? VERDICT_ENABLE_TESTING:INTERNAL=OFF //ADVANCED property for variable: VERDICT_MANGLE VERDICT_MANGLE-ADVANCED:INTERNAL=1 //Mangle verdict names for inclusion in a larger library? VERDICT_MANGLE:INTERNAL=OFF //A string to prepend to all verdict function names and classes. VERDICT_MANGLE_PREFIX:INTERNAL= //Result of TRY_COMPILE VSNPRINTF_WORKS:INTERNAL=TRUE VTKFTGL_BINARY_DIR:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/VTK/Utilities/ftgl VTKFTGL_SOURCE_DIR:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/VTK/Utilities/ftgl //ADVANCED property for variable: VTKOGGTHEORA_DISABLE_ASM VTKOGGTHEORA_DISABLE_ASM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTKOGGTHEORA_DISABLE_FLOAT VTKOGGTHEORA_DISABLE_FLOAT-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int) VTKOGGTHEORA_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int16_t) VTKOGGTHEORA_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int32_t) VTKOGGTHEORA_INT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int64_t) VTKOGGTHEORA_INT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long) VTKOGGTHEORA_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) VTKOGGTHEORA_LONG_LONG:INTERNAL=8 //ADVANCED property for variable: VTKOGGTHEORA_SHARED_LINKER_FLAGS VTKOGGTHEORA_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(short) VTKOGGTHEORA_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint16_t) VTKOGGTHEORA_UINT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint32_t) VTKOGGTHEORA_UINT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(u_int16_t) VTKOGGTHEORA_U_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(u_int32_t) VTKOGGTHEORA_U_INT32_T:INTERNAL=4 //ADVANCED property for variable: VTK_ALL_NEW_OBJECT_FACTORY VTK_ALL_NEW_OBJECT_FACTORY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ANDROID_BUILD VTK_ANDROID_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_BUILD_ALL_MODULES VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1 //Directory where python modules will be built VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=/home/bd/gohan_mount/bdutta/PARAVIEW/PV_Vignesh/bd_build_mesa/lib/site-packages //Test VTK_CONST_REVERSE_ITERATOR_COMPARISON VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1 //ADVANCED property for variable: VTK_DATA_STORE VTK_DATA_STORE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DEBUG_LEAKS VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_AOS_ARRAYS VTK_DISPATCH_AOS_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_SOA_ARRAYS VTK_DISPATCH_SOA_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_TYPED_ARRAYS VTK_DISPATCH_TYPED_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_EGL_DEVICE_INDEX VTK_EGL_DEVICE_INDEX-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ENABLE_KITS VTK_ENABLE_KITS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ENABLE_VTKPYTHON VTK_ENABLE_VTKPYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_EXTRA_COMPILER_WARNINGS VTK_EXTRA_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_FORBID_DOWNLOADS VTK_FORBID_DOWNLOADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_GLEXT_FILE VTK_GLEXT_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_GLXEXT_FILE VTK_GLXEXT_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Imaging VTK_Group_Imaging-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_MPI VTK_Group_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewCore VTK_Group_ParaViewCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewQt VTK_Group_ParaViewQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewRendering VTK_Group_ParaViewRendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Qt VTK_Group_Qt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Rendering VTK_Group_Rendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_StandAlone VTK_Group_StandAlone-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Tk VTK_Group_Tk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Views VTK_Group_Views-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Web VTK_Group_Web-ADVANCED:INTERNAL=1 //Have symbol feenableexcept VTK_HAS_FEENABLEEXCEPT:INTERNAL=1 //Have symbol finite VTK_HAS_FINITE:INTERNAL=1 //Have symbol isfinite VTK_HAS_ISFINITE:INTERNAL=1 //Have symbol isinf VTK_HAS_ISINF:INTERNAL=1 //Have symbol isnan VTK_HAS_ISNAN:INTERNAL=1 //Test VTK_HAS_STD_ISFINITE VTK_HAS_STD_ISFINITE:INTERNAL=1 //Test VTK_HAS_STD_ISINF VTK_HAS_STD_ISINF:INTERNAL=1 //Test VTK_HAS_STD_ISNAN VTK_HAS_STD_ISNAN:INTERNAL=1 //Support for getsockname with socklen_t VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=1 //Have library socket VTK_HAVE_LIBSOCKET:INTERNAL= //Have symbol SO_REUSEADDR VTK_HAVE_SO_REUSEADDR:INTERNAL=1 //For __sync atomic builtins. VTK_HAVE_SYNC_BUILTINS:INTERNAL=1 //VTK modular always ignores BTX VTK_IGNORE_BTX:INTERNAL=ON //ADVANCED property for variable: VTK_IGNORE_GLDRIVER_BUGS VTK_IGNORE_GLDRIVER_BUGS-ADVANCED:INTERNAL=1 //Directory where python modules will be installed VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-5.0/site-packages //ADVANCED property for variable: VTK_IOS_BUILD VTK_IOS_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_LEGACY_REMOVE VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_LEGACY_SILENT VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_LINKER_FATAL_WARNINGS VTK_LINKER_FATAL_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MAKE_INSTANTIATORS VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MAX_THREADS VTK_MAX_THREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_NO_PYTHON_THREADS VTK_NO_PYTHON_THREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_PYTHON_VERSION VTK_PYTHON_VERSION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_RENDERING_BACKEND VTK_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL2;OpenGL;None //ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS VTK_REPORT_OPENGL_ERRORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;OpenMP;TBB //Result of TRY_COMPILE VTK_TEST_SYNC_BUILTINS_COMPILED:INTERNAL=TRUE //ADVANCED property for variable: VTK_USE_64BIT_IDS VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_CXX11_FEATURES VTK_USE_CXX11_FEATURES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_GCC_VISIBILITY VTK_USE_GCC_VISIBILITY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_LARGE_DATA VTK_USE_LARGE_DATA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_OFFSCREEN VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_OFFSCREEN_EGL VTK_USE_OFFSCREEN_EGL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_AUTOBAHN VTK_USE_SYSTEM_AUTOBAHN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_DIY2 VTK_USE_SYSTEM_DIY2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_GL2PS VTK_USE_SYSTEM_GL2PS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_GLEW VTK_USE_SYSTEM_GLEW-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_HDF5 VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ICET VTK_USE_SYSTEM_ICET-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_JPEG VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_JSONCPP VTK_USE_SYSTEM_JSONCPP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LIBRARIES VTK_USE_SYSTEM_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2 VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LZ4 VTK_USE_SYSTEM_LZ4-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_MPI4PY VTK_USE_SYSTEM_MPI4PY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_NETCDF VTK_USE_SYSTEM_NETCDF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_OGGTHEORA VTK_USE_SYSTEM_OGGTHEORA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PNG VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PROTOBUF VTK_USE_SYSTEM_PROTOBUF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PUGIXML VTK_USE_SYSTEM_PUGIXML-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_SIX VTK_USE_SYSTEM_SIX-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_TIFF VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_TWISTED VTK_USE_SYSTEM_TWISTED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_XDMF2 VTK_USE_SYSTEM_XDMF2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ZOPE VTK_USE_SYSTEM_ZOPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_TDX VTK_USE_TDX-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_TK VTK_USE_TK-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_X VTK_USE_X-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_VPIC_USE_MPI VTK_VPIC_USE_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WARN_ON_DISPATCH_FAILURE VTK_WARN_ON_DISPATCH_FAILURE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WGLEXT_FILE VTK_WGLEXT_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WRAP_HINTS VTK_WRAP_HINTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WRAP_JAVA VTK_WRAP_JAVA-ADVANCED:INTERNAL=1 //Should VTK Python wrapping be built? VTK_WRAP_PYTHON:INTERNAL=ON //ADVANCED property for variable: VTK_WRAP_TCL VTK_WRAP_TCL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_XDMF_USE_MPI VTK_XDMF_USE_MPI-ADVANCED:INTERNAL=1 //Test Wno-unused-result Wno-unused-result:INTERNAL=1 //ADVANCED property for variable: XDMF_BUILD_MPI XDMF_BUILD_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_HAS_NDGM XDMF_HAS_NDGM-ADVANCED:INTERNAL=1 //Whether streams support 64-bit types XDMF_HAVE_64BIT_STREAMS:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_FCNTL XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1 //Have include malloc.h XDMF_HAVE_MALLOC_H:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_MMAN XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_NETINET XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1 XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF XDMF_REGENERATE_YACCLEX:INTERNAL=OFF //CHECK_TYPE_SIZE: sizeof(char) XDMF_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) XDMF_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) XDMF_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) XDMF_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) XDMF_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) XDMF_SIZEOF_SHORT:INTERNAL=2 //ADVANCED property for variable: XDMF_USE_BZIP2 XDMF_USE_BZIP2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_USE_GZIP XDMF_USE_GZIP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_USE_MYSQL XDMF_USE_MYSQL-ADVANCED:INTERNAL=1 XDMF_WRAP_CSHARP:INTERNAL=OFF XDMF_WRAP_PYTHON:INTERNAL=OFF XDMF_WRAP_TCL:INTERNAL=OFF //Have include unistd.h Z_HAVE_UNISTD_H:INTERNAL=1 //ParaView has been configured __paraview_configured:INTERNAL=TRUE protobut_determine_hash_namespace_done:INTERNAL=TRUE protobut_pthread_test_done:INTERNAL=TRUE pthread_test_result:INTERNAL=PTHREAD_CREATE_JOINABLE -------------- next part -------------- A non-text attachment was scrubbed... Name: cone_clip.py Type: text/x-python Size: 1821 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 30 10:35:32 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 30 Mar 2017 10:35:32 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Isn't that simply a sum of all the rows in the output of integrateSqrVarOverSpace filter? If so, that can be done by using another *ProgrammableFilter* with the following *Script*: from numpy import sum for inTable, outTable in zip(inputs[0], output): for aname in inTable.RowData.keys(): outTable.RowData.append(sum(inTable.RowData[aname]), aname) Utkarsh On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: > Sorry, that's not what I wanted. I want to integrate the variable > "integrateSqrVarOverSpace", over time as well. > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Your script worked for me for the most part with ParaView 5.3. All I did >> was added a plot view to show the results (attached). If that what you were >> looking for? >> >> On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: >> >>> They are very large. I believe you should be able to access them through >>> this link >>> >>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s >>> >>> Regards, >>> >>> John R. Haase >>> jhaase1 at nd.edu >>> >>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> John, >>>> >>>> Can you send me the datafiles too (feel free to do it off the mailing >>>> list) so I can figure out what could be going wrong. >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: >>>> >>>>> Hello Paraviewers, >>>>> >>>>> I'm trying to integrate variables over time. I found this thread where >>>>> it had been brought up previously. >>>>> >>>>> http://paraview.markmail.org/search/?q=integral+over+time#qu >>>>> ery:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >>>>> >>>>> However, when I try and open the state file, paraview crashes. So what >>>>> commands do I use to do the integral over time? I'm trying to integrate a >>>>> PlotSelectionOverTime filter (with row data). >>>>> >>>>> I'm doing this programmatically, so attached is the python script. I >>>>> have so far. >>>>> >>>>> Regards, >>>>> >>>>> John R. Haase >>>>> jhaase1 at nd.edu >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhaase1 at nd.edu Thu Mar 30 12:09:02 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 30 Mar 2017 12:09:02 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Exploring 'integrateSqrVarOverSpace', it doesn't have a 'RowData' object. dir(integrateSqrVarOverSpace) ['CellData', 'FieldData', 'FileNameChanged', 'GetCellDataInformation', 'GetDataInformation', 'GetFieldDataInformation', 'GetPointDataInformation', 'GetProperty', 'GetPropertyValue', 'Initialize', 'InitializeFromProxy', 'Input', 'ListProperties', 'Observed', 'ObserverTag', 'OnlyReportSelectionStatistics', 'PointData', 'Port', 'SMProxy', 'Selection', 'SetPropertyWithName', 'UpdatePipeline', 'UpdatePipelineInformation', '_Proxy__ConvertArgumentsAndCall', '_Proxy__GetActiveCamera', '_Proxy__LastAttrName', '_Proxy__Properties', '__class__', '__del__', '__delattr__', '__dict__', '__doc__', '__eq__', '__format__', '__getattr__', '__getattribute__', '__getitem__', '__hash__', '__init__', '__iter__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'add_attribute'] So, using the script you posted, I get the error "IndexError: tuple index out of range". Regards, John R. Haase jhaase1 at nd.edu On Thu, Mar 30, 2017 at 10:35 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Isn't that simply a sum of all the rows in the output of > integrateSqrVarOverSpace filter? > > If so, that can be done by using another *ProgrammableFilter* with the > following *Script*: > > from numpy import sum > for inTable, outTable in zip(inputs[0], output): > > for aname in inTable.RowData.keys(): > > outTable.RowData.append(sum(inTable.RowData[aname]), aname) > > > Utkarsh > > > > > On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: > >> Sorry, that's not what I wanted. I want to integrate the variable >> "integrateSqrVarOverSpace", over time as well. >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Your script worked for me for the most part with ParaView 5.3. All I did >>> was added a plot view to show the results (attached). If that what you were >>> looking for? >>> >>> On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: >>> >>>> They are very large. I believe you should be able to access them >>>> through this link >>>> >>>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s >>>> >>>> Regards, >>>> >>>> John R. Haase >>>> jhaase1 at nd.edu >>>> >>>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit < >>>> utkarsh.ayachit at kitware.com> wrote: >>>> >>>>> John, >>>>> >>>>> Can you send me the datafiles too (feel free to do it off the mailing >>>>> list) so I can figure out what could be going wrong. >>>>> >>>>> Thanks >>>>> Utkarsh >>>>> >>>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: >>>>> >>>>>> Hello Paraviewers, >>>>>> >>>>>> I'm trying to integrate variables over time. I found this thread >>>>>> where it had been brought up previously. >>>>>> >>>>>> http://paraview.markmail.org/search/?q=integral+over+time#qu >>>>>> ery:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >>>>>> >>>>>> However, when I try and open the state file, paraview crashes. So >>>>>> what commands do I use to do the integral over time? I'm trying to >>>>>> integrate a PlotSelectionOverTime filter (with row data). >>>>>> >>>>>> I'm doing this programmatically, so attached is the python script. I >>>>>> have so far. >>>>>> >>>>>> Regards, >>>>>> >>>>>> John R. Haase >>>>>> jhaase1 at nd.edu >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Mar 30 12:32:17 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 30 Mar 2017 12:32:17 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: John, That's the script for a "Programmable Filter", not simply to be added to your script, similar to what you're doing with `squareDiff`. e.g. myfilter = ProgrammableFilter(Input=integrateSqrVarOverSpace) myfilter.Script = "...." # the script I provided. myfilter.UpdatePipeline() ... Utkarsh On Thu, Mar 30, 2017 at 12:09 PM, John Haase wrote: > Exploring 'integrateSqrVarOverSpace', it doesn't have a 'RowData' object. > > dir(integrateSqrVarOverSpace) > > ['CellData', 'FieldData', 'FileNameChanged', 'GetCellDataInformation', > 'GetDataInformation', 'GetFieldDataInformation', 'GetPointDataInformation', > 'GetProperty', 'GetPropertyValue', 'Initialize', 'InitializeFromProxy', > 'Input', 'ListProperties', 'Observed', 'ObserverTag', > 'OnlyReportSelectionStatistics', 'PointData', 'Port', 'SMProxy', > 'Selection', 'SetPropertyWithName', 'UpdatePipeline', > 'UpdatePipelineInformation', '_Proxy__ConvertArgumentsAndCall', > '_Proxy__GetActiveCamera', '_Proxy__LastAttrName', '_Proxy__Properties', > '__class__', '__del__', '__delattr__', '__dict__', '__doc__', '__eq__', > '__format__', '__getattr__', '__getattribute__', '__getitem__', '__hash__', > '__init__', '__iter__', '__module__', '__ne__', '__new__', '__reduce__', > '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', > '__subclasshook__', '__weakref__', 'add_attribute'] > > > So, using the script you posted, I get the error "IndexError: tuple index > out of range". > > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Thu, Mar 30, 2017 at 10:35 AM, Utkarsh Ayachit > wrote: >> >> Isn't that simply a sum of all the rows in the output of >> integrateSqrVarOverSpace filter? >> >> If so, that can be done by using another ProgrammableFilter with the >> following Script: >> >> from numpy import sum >> for inTable, outTable in zip(inputs[0], output): >> >> for aname in inTable.RowData.keys(): >> >> outTable.RowData.append(sum(inTable.RowData[aname]), aname) >> >> >> Utkarsh >> >> >> >> >> On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: >>> >>> Sorry, that's not what I wanted. I want to integrate the variable >>> "integrateSqrVarOverSpace", over time as well. >>> >>> Regards, >>> >>> John R. Haase >>> jhaase1 at nd.edu >>> >>> On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit >>> wrote: >>>> >>>> Your script worked for me for the most part with ParaView 5.3. All I did >>>> was added a plot view to show the results (attached). If that what you were >>>> looking for? >>>> >>>> On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: >>>>> >>>>> They are very large. I believe you should be able to access them >>>>> through this link >>>>> >>>>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s >>>>> >>>>> Regards, >>>>> >>>>> John R. Haase >>>>> jhaase1 at nd.edu >>>>> >>>>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit >>>>> wrote: >>>>>> >>>>>> John, >>>>>> >>>>>> Can you send me the datafiles too (feel free to do it off the mailing >>>>>> list) so I can figure out what could be going wrong. >>>>>> >>>>>> Thanks >>>>>> Utkarsh >>>>>> >>>>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase wrote: >>>>>>> >>>>>>> Hello Paraviewers, >>>>>>> >>>>>>> I'm trying to integrate variables over time. I found this thread >>>>>>> where it had been brought up previously. >>>>>>> >>>>>>> >>>>>>> http://paraview.markmail.org/search/?q=integral+over+time#query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >>>>>>> >>>>>>> However, when I try and open the state file, paraview crashes. So >>>>>>> what commands do I use to do the integral over time? I'm trying to integrate >>>>>>> a PlotSelectionOverTime filter (with row data). >>>>>>> >>>>>>> I'm doing this programmatically, so attached is the python script. I >>>>>>> have so far. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> John R. Haase >>>>>>> jhaase1 at nd.edu >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>> >>>>> >>>> >>> >> > From jhaase1 at nd.edu Thu Mar 30 13:02:43 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 30 Mar 2017 13:02:43 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Utkarsh, Using the script attached, and the same data sets as before. I get the error Traceback (most recent call last): File "", line 22, in File "", line 5, in RequestData File "C:\Program Files\ParaView 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\numpy_interface\dataset_adapter.py", line 660, in append arrLength = narray.shape[0] IndexError: tuple index out of range on the last line. Regards, John R. Haase jhaase1 at nd.edu On Thu, Mar 30, 2017 at 12:32 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > John, > > That's the script for a "Programmable Filter", not simply to be added > to your script, similar to what you're doing with `squareDiff`. > > e.g. > > myfilter = ProgrammableFilter(Input=integrateSqrVarOverSpace) > myfilter.Script = "...." # the script I provided. > myfilter.UpdatePipeline() > ... > > Utkarsh > > On Thu, Mar 30, 2017 at 12:09 PM, John Haase wrote: > > Exploring 'integrateSqrVarOverSpace', it doesn't have a 'RowData' object. > > > > dir(integrateSqrVarOverSpace) > > > > ['CellData', 'FieldData', 'FileNameChanged', 'GetCellDataInformation', > > 'GetDataInformation', 'GetFieldDataInformation', > 'GetPointDataInformation', > > 'GetProperty', 'GetPropertyValue', 'Initialize', 'InitializeFromProxy', > > 'Input', 'ListProperties', 'Observed', 'ObserverTag', > > 'OnlyReportSelectionStatistics', 'PointData', 'Port', 'SMProxy', > > 'Selection', 'SetPropertyWithName', 'UpdatePipeline', > > 'UpdatePipelineInformation', '_Proxy__ConvertArgumentsAndCall', > > '_Proxy__GetActiveCamera', '_Proxy__LastAttrName', '_Proxy__Properties', > > '__class__', '__del__', '__delattr__', '__dict__', '__doc__', '__eq__', > > '__format__', '__getattr__', '__getattribute__', '__getitem__', > '__hash__', > > '__init__', '__iter__', '__module__', '__ne__', '__new__', '__reduce__', > > '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', > > '__subclasshook__', '__weakref__', 'add_attribute'] > > > > > > So, using the script you posted, I get the error "IndexError: tuple index > > out of range". > > > > > > Regards, > > > > John R. Haase > > jhaase1 at nd.edu > > > > On Thu, Mar 30, 2017 at 10:35 AM, Utkarsh Ayachit > > wrote: > >> > >> Isn't that simply a sum of all the rows in the output of > >> integrateSqrVarOverSpace filter? > >> > >> If so, that can be done by using another ProgrammableFilter with the > >> following Script: > >> > >> from numpy import sum > >> for inTable, outTable in zip(inputs[0], output): > >> > >> for aname in inTable.RowData.keys(): > >> > >> outTable.RowData.append(sum(inTable.RowData[aname]), aname) > >> > >> > >> Utkarsh > >> > >> > >> > >> > >> On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: > >>> > >>> Sorry, that's not what I wanted. I want to integrate the variable > >>> "integrateSqrVarOverSpace", over time as well. > >>> > >>> Regards, > >>> > >>> John R. Haase > >>> jhaase1 at nd.edu > >>> > >>> On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit > >>> wrote: > >>>> > >>>> Your script worked for me for the most part with ParaView 5.3. All I > did > >>>> was added a plot view to show the results (attached). If that what > you were > >>>> looking for? > >>>> > >>>> On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: > >>>>> > >>>>> They are very large. I believe you should be able to access them > >>>>> through this link > >>>>> > >>>>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s > >>>>> > >>>>> Regards, > >>>>> > >>>>> John R. Haase > >>>>> jhaase1 at nd.edu > >>>>> > >>>>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit > >>>>> wrote: > >>>>>> > >>>>>> John, > >>>>>> > >>>>>> Can you send me the datafiles too (feel free to do it off the > mailing > >>>>>> list) so I can figure out what could be going wrong. > >>>>>> > >>>>>> Thanks > >>>>>> Utkarsh > >>>>>> > >>>>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase > wrote: > >>>>>>> > >>>>>>> Hello Paraviewers, > >>>>>>> > >>>>>>> I'm trying to integrate variables over time. I found this thread > >>>>>>> where it had been brought up previously. > >>>>>>> > >>>>>>> > >>>>>>> http://paraview.markmail.org/search/?q=integral+over+time# > query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results > >>>>>>> > >>>>>>> However, when I try and open the state file, paraview crashes. So > >>>>>>> what commands do I use to do the integral over time? I'm trying to > integrate > >>>>>>> a PlotSelectionOverTime filter (with row data). > >>>>>>> > >>>>>>> I'm doing this programmatically, so attached is the python script. > I > >>>>>>> have so far. > >>>>>>> > >>>>>>> Regards, > >>>>>>> > >>>>>>> John R. Haase > >>>>>>> jhaase1 at nd.edu > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Powered by www.kitware.com > >>>>>>> > >>>>>>> Visit other Kitware open-source projects at > >>>>>>> http://www.kitware.com/opensource/opensource.html > >>>>>>> > >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>>>>> http://paraview.org/Wiki/ParaView > >>>>>>> > >>>>>>> Search the list archives at: http://markmail.org/search/?q= > ParaView > >>>>>>> > >>>>>>> Follow this link to subscribe/unsubscribe: > >>>>>>> http://public.kitware.com/mailman/listinfo/paraview > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GetR2Error.py Type: application/octet-stream Size: 2135 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Mar 30 15:35:28 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 30 Mar 2017 15:35:28 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Not sure what's going on. The attached script worked just fine for me. On Thu, Mar 30, 2017 at 1:02 PM, John Haase wrote: > Utkarsh, > > Using the script attached, and the same data sets as before. I get the error > > Traceback (most recent call last): > > File "", line 22, in > > File "", line 5, in RequestData > > File "C:\Program Files\ParaView > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\numpy_interface\dataset_adapter.py", > line 660, in append > > arrLength = narray.shape[0] > > IndexError: tuple index out of range > > > on the last line. > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Thu, Mar 30, 2017 at 12:32 PM, Utkarsh Ayachit > wrote: >> >> John, >> >> That's the script for a "Programmable Filter", not simply to be added >> to your script, similar to what you're doing with `squareDiff`. >> >> e.g. >> >> myfilter = ProgrammableFilter(Input=integrateSqrVarOverSpace) >> myfilter.Script = "...." # the script I provided. >> myfilter.UpdatePipeline() >> ... >> >> Utkarsh >> >> On Thu, Mar 30, 2017 at 12:09 PM, John Haase wrote: >> > Exploring 'integrateSqrVarOverSpace', it doesn't have a 'RowData' >> > object. >> > >> > dir(integrateSqrVarOverSpace) >> > >> > ['CellData', 'FieldData', 'FileNameChanged', 'GetCellDataInformation', >> > 'GetDataInformation', 'GetFieldDataInformation', >> > 'GetPointDataInformation', >> > 'GetProperty', 'GetPropertyValue', 'Initialize', 'InitializeFromProxy', >> > 'Input', 'ListProperties', 'Observed', 'ObserverTag', >> > 'OnlyReportSelectionStatistics', 'PointData', 'Port', 'SMProxy', >> > 'Selection', 'SetPropertyWithName', 'UpdatePipeline', >> > 'UpdatePipelineInformation', '_Proxy__ConvertArgumentsAndCall', >> > '_Proxy__GetActiveCamera', '_Proxy__LastAttrName', '_Proxy__Properties', >> > '__class__', '__del__', '__delattr__', '__dict__', '__doc__', '__eq__', >> > '__format__', '__getattr__', '__getattribute__', '__getitem__', >> > '__hash__', >> > '__init__', '__iter__', '__module__', '__ne__', '__new__', '__reduce__', >> > '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', >> > '__subclasshook__', '__weakref__', 'add_attribute'] >> > >> > >> > So, using the script you posted, I get the error "IndexError: tuple >> > index >> > out of range". >> > >> > >> > Regards, >> > >> > John R. Haase >> > jhaase1 at nd.edu >> > >> > On Thu, Mar 30, 2017 at 10:35 AM, Utkarsh Ayachit >> > wrote: >> >> >> >> Isn't that simply a sum of all the rows in the output of >> >> integrateSqrVarOverSpace filter? >> >> >> >> If so, that can be done by using another ProgrammableFilter with the >> >> following Script: >> >> >> >> from numpy import sum >> >> for inTable, outTable in zip(inputs[0], output): >> >> >> >> for aname in inTable.RowData.keys(): >> >> >> >> outTable.RowData.append(sum(inTable.RowData[aname]), aname) >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> >> >> On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: >> >>> >> >>> Sorry, that's not what I wanted. I want to integrate the variable >> >>> "integrateSqrVarOverSpace", over time as well. >> >>> >> >>> Regards, >> >>> >> >>> John R. Haase >> >>> jhaase1 at nd.edu >> >>> >> >>> On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit >> >>> wrote: >> >>>> >> >>>> Your script worked for me for the most part with ParaView 5.3. All I >> >>>> did >> >>>> was added a plot view to show the results (attached). If that what >> >>>> you were >> >>>> looking for? >> >>>> >> >>>> On Wed, Mar 29, 2017 at 12:30 PM, John Haase wrote: >> >>>>> >> >>>>> They are very large. I believe you should be able to access them >> >>>>> through this link >> >>>>> >> >>>>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s >> >>>>> >> >>>>> Regards, >> >>>>> >> >>>>> John R. Haase >> >>>>> jhaase1 at nd.edu >> >>>>> >> >>>>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit >> >>>>> wrote: >> >>>>>> >> >>>>>> John, >> >>>>>> >> >>>>>> Can you send me the datafiles too (feel free to do it off the >> >>>>>> mailing >> >>>>>> list) so I can figure out what could be going wrong. >> >>>>>> >> >>>>>> Thanks >> >>>>>> Utkarsh >> >>>>>> >> >>>>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase >> >>>>>> wrote: >> >>>>>>> >> >>>>>>> Hello Paraviewers, >> >>>>>>> >> >>>>>>> I'm trying to integrate variables over time. I found this thread >> >>>>>>> where it had been brought up previously. >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> http://paraview.markmail.org/search/?q=integral+over+time#query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results >> >>>>>>> >> >>>>>>> However, when I try and open the state file, paraview crashes. So >> >>>>>>> what commands do I use to do the integral over time? I'm trying to >> >>>>>>> integrate >> >>>>>>> a PlotSelectionOverTime filter (with row data). >> >>>>>>> >> >>>>>>> I'm doing this programmatically, so attached is the python script. >> >>>>>>> I >> >>>>>>> have so far. >> >>>>>>> >> >>>>>>> Regards, >> >>>>>>> >> >>>>>>> John R. Haase >> >>>>>>> jhaase1 at nd.edu >> >>>>>>> >> >>>>>>> _______________________________________________ >> >>>>>>> Powered by www.kitware.com >> >>>>>>> >> >>>>>>> Visit other Kitware open-source projects at >> >>>>>>> http://www.kitware.com/opensource/opensource.html >> >>>>>>> >> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >> >>>>>>> http://paraview.org/Wiki/ParaView >> >>>>>>> >> >>>>>>> Search the list archives at: >> >>>>>>> http://markmail.org/search/?q=ParaView >> >>>>>>> >> >>>>>>> Follow this link to subscribe/unsubscribe: >> >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >> >>>>>>> >> >>>>>> >> >>>>> >> >>>> >> >>> >> >> >> > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: GetR2Error.py Type: text/x-python Size: 2150 bytes Desc: not available URL: From jhaase1 at nd.edu Thu Mar 30 18:05:16 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 30 Mar 2017 18:05:16 -0400 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: Okay, I figured it out. I updated my version of Paraview from 5.2.0 to 5.3.0 and that fixed it. Is there a way to only have "aname" loop over "reader[0].ElementVariables"? I tried to replace the line "for aname in inTable.RowData.keys():" with "for aname in " + reader[0].ElementVariables + ":" but that didn't work Regards, John R. Haase jhaase1 at nd.edu On Thu, Mar 30, 2017 at 3:35 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Not sure what's going on. The attached script worked just fine for me. > > On Thu, Mar 30, 2017 at 1:02 PM, John Haase wrote: > > Utkarsh, > > > > Using the script attached, and the same data sets as before. I get the > error > > > > Traceback (most recent call last): > > > > File "", line 22, in > > > > File "", line 5, in RequestData > > > > File "C:\Program Files\ParaView > > 5.2.0-Qt4-OpenGL2-Windows-64bit\bin\lib\site-packages\ > vtk\numpy_interface\dataset_adapter.py", > > line 660, in append > > > > arrLength = narray.shape[0] > > > > IndexError: tuple index out of range > > > > > > on the last line. > > > > Regards, > > > > John R. Haase > > jhaase1 at nd.edu > > > > On Thu, Mar 30, 2017 at 12:32 PM, Utkarsh Ayachit > > wrote: > >> > >> John, > >> > >> That's the script for a "Programmable Filter", not simply to be added > >> to your script, similar to what you're doing with `squareDiff`. > >> > >> e.g. > >> > >> myfilter = ProgrammableFilter(Input=integrateSqrVarOverSpace) > >> myfilter.Script = "...." # the script I provided. > >> myfilter.UpdatePipeline() > >> ... > >> > >> Utkarsh > >> > >> On Thu, Mar 30, 2017 at 12:09 PM, John Haase wrote: > >> > Exploring 'integrateSqrVarOverSpace', it doesn't have a 'RowData' > >> > object. > >> > > >> > dir(integrateSqrVarOverSpace) > >> > > >> > ['CellData', 'FieldData', 'FileNameChanged', 'GetCellDataInformation', > >> > 'GetDataInformation', 'GetFieldDataInformation', > >> > 'GetPointDataInformation', > >> > 'GetProperty', 'GetPropertyValue', 'Initialize', > 'InitializeFromProxy', > >> > 'Input', 'ListProperties', 'Observed', 'ObserverTag', > >> > 'OnlyReportSelectionStatistics', 'PointData', 'Port', 'SMProxy', > >> > 'Selection', 'SetPropertyWithName', 'UpdatePipeline', > >> > 'UpdatePipelineInformation', '_Proxy__ConvertArgumentsAndCall', > >> > '_Proxy__GetActiveCamera', '_Proxy__LastAttrName', > '_Proxy__Properties', > >> > '__class__', '__del__', '__delattr__', '__dict__', '__doc__', > '__eq__', > >> > '__format__', '__getattr__', '__getattribute__', '__getitem__', > >> > '__hash__', > >> > '__init__', '__iter__', '__module__', '__ne__', '__new__', > '__reduce__', > >> > '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', > >> > '__subclasshook__', '__weakref__', 'add_attribute'] > >> > > >> > > >> > So, using the script you posted, I get the error "IndexError: tuple > >> > index > >> > out of range". > >> > > >> > > >> > Regards, > >> > > >> > John R. Haase > >> > jhaase1 at nd.edu > >> > > >> > On Thu, Mar 30, 2017 at 10:35 AM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> Isn't that simply a sum of all the rows in the output of > >> >> integrateSqrVarOverSpace filter? > >> >> > >> >> If so, that can be done by using another ProgrammableFilter with the > >> >> following Script: > >> >> > >> >> from numpy import sum > >> >> for inTable, outTable in zip(inputs[0], output): > >> >> > >> >> for aname in inTable.RowData.keys(): > >> >> > >> >> outTable.RowData.append(sum(inTable.RowData[aname]), aname) > >> >> > >> >> > >> >> Utkarsh > >> >> > >> >> > >> >> > >> >> > >> >> On Wed, Mar 29, 2017 at 1:15 PM, John Haase wrote: > >> >>> > >> >>> Sorry, that's not what I wanted. I want to integrate the variable > >> >>> "integrateSqrVarOverSpace", over time as well. > >> >>> > >> >>> Regards, > >> >>> > >> >>> John R. Haase > >> >>> jhaase1 at nd.edu > >> >>> > >> >>> On Wed, Mar 29, 2017 at 1:05 PM, Utkarsh Ayachit > >> >>> wrote: > >> >>>> > >> >>>> Your script worked for me for the most part with ParaView 5.3. All > I > >> >>>> did > >> >>>> was added a plot view to show the results (attached). If that what > >> >>>> you were > >> >>>> looking for? > >> >>>> > >> >>>> On Wed, Mar 29, 2017 at 12:30 PM, John Haase > wrote: > >> >>>>> > >> >>>>> They are very large. I believe you should be able to access them > >> >>>>> through this link > >> >>>>> > >> >>>>> https://notredame.box.com/s/qy0p9y5jg71jwxtzfey80xiq9i9udk5s > >> >>>>> > >> >>>>> Regards, > >> >>>>> > >> >>>>> John R. Haase > >> >>>>> jhaase1 at nd.edu > >> >>>>> > >> >>>>> On Wed, Mar 29, 2017 at 12:06 PM, Utkarsh Ayachit > >> >>>>> wrote: > >> >>>>>> > >> >>>>>> John, > >> >>>>>> > >> >>>>>> Can you send me the datafiles too (feel free to do it off the > >> >>>>>> mailing > >> >>>>>> list) so I can figure out what could be going wrong. > >> >>>>>> > >> >>>>>> Thanks > >> >>>>>> Utkarsh > >> >>>>>> > >> >>>>>> On Wed, Mar 29, 2017 at 12:01 PM, John Haase > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Hello Paraviewers, > >> >>>>>>> > >> >>>>>>> I'm trying to integrate variables over time. I found this thread > >> >>>>>>> where it had been brought up previously. > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> http://paraview.markmail.org/search/?q=integral+over+time# > query:integral%20over%20time+page:1+mid:z75bede26onth4eu+state:results > >> >>>>>>> > >> >>>>>>> However, when I try and open the state file, paraview crashes. > So > >> >>>>>>> what commands do I use to do the integral over time? I'm trying > to > >> >>>>>>> integrate > >> >>>>>>> a PlotSelectionOverTime filter (with row data). > >> >>>>>>> > >> >>>>>>> I'm doing this programmatically, so attached is the python > script. > >> >>>>>>> I > >> >>>>>>> have so far. > >> >>>>>>> > >> >>>>>>> Regards, > >> >>>>>>> > >> >>>>>>> John R. Haase > >> >>>>>>> jhaase1 at nd.edu > >> >>>>>>> > >> >>>>>>> _______________________________________________ > >> >>>>>>> Powered by www.kitware.com > >> >>>>>>> > >> >>>>>>> Visit other Kitware open-source projects at > >> >>>>>>> http://www.kitware.com/opensource/opensource.html > >> >>>>>>> > >> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: > >> >>>>>>> http://paraview.org/Wiki/ParaView > >> >>>>>>> > >> >>>>>>> Search the list archives at: > >> >>>>>>> http://markmail.org/search/?q=ParaView > >> >>>>>>> > >> >>>>>>> Follow this link to subscribe/unsubscribe: > >> >>>>>>> http://public.kitware.com/mailman/listinfo/paraview > >> >>>>>>> > >> >>>>>> > >> >>>>> > >> >>>> > >> >>> > >> >> > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.borduas at caboma.com Thu Mar 30 23:21:13 2017 From: jonathan.borduas at caboma.com (Jonathan Borduas) Date: Fri, 31 Mar 2017 03:21:13 +0000 Subject: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter Message-ID: Dear ParaViewers, I came across some weird behaviour in ParaView: We have a custom BooleanOperation filter that have two outputs (custom ParaView build). If both outputs are the inputs of an Append Geometry and we update the inputs of the BooleanOperation Filter, the Append Geometry will be moved before the BooleanOperation Filter. I always though that if there was any dependencies in a pipeline, the representation would respect the "arrow of time" that goes from top to bottom. Please look at the picture here attached (same behaviour with a ProgrammableFilter instead of a Append Geometry). Is my comprehension at fault here or is it a bug ? Thank you, Jonathan Borduas -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pipeline problems.png Type: image/png Size: 30000 bytes Desc: pipeline problems.png URL: From utkarsh.ayachit at kitware.com Fri Mar 31 14:25:07 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 31 Mar 2017 14:25:07 -0400 Subject: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter In-Reply-To: References: Message-ID: Jonathan, The arrow is not intended to have a "top/down" direction, just a "back-to-root" direction. It can be interpreted as "ProgrammableFilter1" can be found somewhere on the main trunk. On Thu, Mar 30, 2017 at 11:21 PM, Jonathan Borduas wrote: > > Dear ParaViewers, > > > I came across some weird behaviour in ParaView: We have a custom > BooleanOperation filter that have two outputs (custom ParaView build). > If both outputs are the inputs of an Append Geometry and we update the > inputs of the BooleanOperation Filter, the Append Geometry will be moved > before the BooleanOperation Filter. > > > I always though that if there was any dependencies in a pipeline, the > representation would respect the "arrow of time" that goes from top to > bottom. > Please look at the picture here attached (same behaviour with a > ProgrammableFilter instead of a Append Geometry). > > > Is my comprehension at fault here or is it a bug ? > > > Thank you, > > > Jonathan Borduas > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From jonathan.borduas at caboma.com Fri Mar 31 18:00:47 2017 From: jonathan.borduas at caboma.com (Jonathan Borduas) Date: Fri, 31 Mar 2017 22:00:47 +0000 Subject: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter In-Reply-To: References: Message-ID: Hi Utkarsh, Thank you for your answer. As a user, especially with a complex tree, I found this unpractical. I have the reflex when searching for a filter to scroll down if the filters is "afterward". I do prefer the GitTree representation of ParaViewWeb. My opinion is that a GitTree could be the optimal representation of the pipeline. The GitKraken GitTree could be a good inspiration for a redesigned pipeline browser ?. Best regards Jonathan Borduas -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, March 31, 2017 2:25 PM To: Jonathan Borduas Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter Jonathan, The arrow is not intended to have a "top/down" direction, just a "back-to-root" direction. It can be interpreted as "ProgrammableFilter1" can be found somewhere on the main trunk. On Thu, Mar 30, 2017 at 11:21 PM, Jonathan Borduas wrote: > > Dear ParaViewers, > > > I came across some weird behaviour in ParaView: We have a custom > BooleanOperation filter that have two outputs (custom ParaView build). > If both outputs are the inputs of an Append Geometry and we update the > inputs of the BooleanOperation Filter, the Append Geometry will be > moved before the BooleanOperation Filter. > > > I always though that if there was any dependencies in a pipeline, the > representation would respect the "arrow of time" that goes from top to > bottom. > Please look at the picture here attached (same behaviour with a > ProgrammableFilter instead of a Append Geometry). > > > Is my comprehension at fault here or is it a bug ? > > > Thank you, > > > Jonathan Borduas > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Mar 31 20:27:33 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 31 Mar 2017 20:27:33 -0400 Subject: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter In-Reply-To: References: Message-ID: Totally agreed. The pipeline browser hasn't been updated since early ParaView 3.0 days, I'd guess a 2009. It surely can be made better. In the end, it boils down to the need and time availability. Since it works well for 80/90% of the cases, we (and our customers and contributors) often end up prioritizing other features and bug fixes. We do offer various consulting options , if you're keen on getting it updated ?. Utkarsh On Fri, Mar 31, 2017 at 6:00 PM, Jonathan Borduas < jonathan.borduas at caboma.com> wrote: > Hi Utkarsh, > > Thank you for your answer. As a user, especially with a complex tree, I > found this unpractical. I have the reflex when searching for a filter to > scroll down if the filters is "afterward". > > I do prefer the GitTree representation of ParaViewWeb. My opinion is that > a GitTree could be the optimal representation of the pipeline. > > The GitKraken GitTree could be a good inspiration for a redesigned > pipeline browser ?. > > Best regards > > Jonathan Borduas > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, March 31, 2017 2:25 PM > To: Jonathan Borduas > Cc: paraview at paraview.org > Subject: Re: [Paraview] Pipeline not respecting the arrow of time after > changing the inputs of a filter > > Jonathan, > > The arrow is not intended to have a "top/down" direction, just a > "back-to-root" direction. It can be interpreted as "ProgrammableFilter1" > can be found somewhere on the main trunk. > > On Thu, Mar 30, 2017 at 11:21 PM, Jonathan Borduas < > jonathan.borduas at caboma.com> wrote: > > > > Dear ParaViewers, > > > > > > I came across some weird behaviour in ParaView: We have a custom > > BooleanOperation filter that have two outputs (custom ParaView build). > > If both outputs are the inputs of an Append Geometry and we update the > > inputs of the BooleanOperation Filter, the Append Geometry will be > > moved before the BooleanOperation Filter. > > > > > > I always though that if there was any dependencies in a pipeline, the > > representation would respect the "arrow of time" that goes from top to > > bottom. > > Please look at the picture here attached (same behaviour with a > > ProgrammableFilter instead of a Append Geometry). > > > > > > Is my comprehension at fault here or is it a bug ? > > > > > > Thank you, > > > > > > Jonathan Borduas > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: