From bflandard at gmail.com Wed Feb 1 06:40:09 2017 From: bflandard at gmail.com (Bob Flandard) Date: Wed, 1 Feb 2017 11:40:09 +0000 Subject: [Paraview] Ansys to ParaView Message-ID: Hi Anxo, If you're using Ansys MAPDL aka "Classic", then you have a lot of flexibility to code something in apdl to output mesh and results in a format that suits you (and ParaView). For efficient code you would need to make use of the vectorised functions like *vget, *vfun, *voper etc. If you're only going to want to do this once and therefore can't invest the time, upload your database and solution file and send me a link (or send me your apdl input files) and I'll try to upload something you can open in ParaView, less than 1 million nodes is fine. If you're using Workbench, then I believe it writes the apdl commands to define the mesh, loads and BCs, to the project directory along with the solution file *.rst (extension depends on the physics). Regards, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From bflandard at gmail.com Wed Feb 1 06:45:36 2017 From: bflandard at gmail.com (Bob Flandard) Date: Wed, 1 Feb 2017 11:45:36 +0000 Subject: [Paraview] Ansys to ParaView Message-ID: Hi Anxo, By upload, I mean to your dropbox account, not the ParaView server:) Regards, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From messner at anl.gov Wed Feb 1 10:01:40 2017 From: messner at anl.gov (Messner, Mark Christian) Date: Wed, 1 Feb 2017 15:01:40 +0000 Subject: [Paraview] Silo reader, working with data In-Reply-To: References: Message-ID: Hello, This is a basic question but I wasn't able to find any info by searching the mailing list. I successfully compiled Paraview with VisitBridge and the silo reader and read in my silo data. The actual result arrays are stored as separate cell and point arrays in the multiblock not associated with the mesh (see screenshot). How do I use (for example contour) the data in the cell arrays and point arrays? I tried "Cell Data to Point Data" which was suggested in a previous post but had no luck. Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2017-02-01 08-52-49.png Type: image/png Size: 146023 bytes Desc: Screenshot from 2017-02-01 08-52-49.png URL: From bdutta at vt.edu Wed Feb 1 13:26:48 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Wed, 1 Feb 2017 13:26:48 -0500 Subject: [Paraview] Query on paraview software rendering vs GPU rendering on ubuntu server Message-ID: Hi All, I am setting up paraview in different modes in my university for research and had the below queries on paraview wrt ubuntu. Thanks if anyone can answer them. a) Is it possible to dynamically switch between CPU (mesa software rendering) and GPU rendering (openGL). If so, which Paraview version supports this and the steps. Is not then can paraview binaries be used with some commandline option for the same. b) In ubuntu server version (which has no GUI), can paraview use GPU for graphics acceleration as there is no GUI. I don't get this properly if desktop GUI is must for GPU usage. BR, Bishwajit -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Wed Feb 1 15:28:51 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Wed, 1 Feb 2017 15:28:51 -0500 Subject: [Paraview] Query on paraview software rendering vs GPU rendering on ubuntu server In-Reply-To: References: Message-ID: Bishwajit, On Wed, Feb 1, 2017 at 1:26 PM, Bishwajit Dutta wrote: > Hi All, > > I am setting up paraview in different modes in my university for research > and had the below queries on paraview wrt ubuntu. Thanks if anyone can > answer them. > > a) Is it possible to dynamically switch between CPU (mesa software > rendering) and GPU rendering (openGL). If so, which Paraview version > supports this and the steps. > Not as far as I know. The OpenGL libraries are resolved at configuration and compilation time. > Is not then can paraview binaries be used with some commandline option for > the same. > On the same machine, you could run two servers one that renders in software and one that renders on the GPU. You could save the state, disconnect from one, connect to the other and load the saved state. But this is not really dynamic switching. b) In ubuntu server version (which has no GUI), can paraview use GPU for > graphics acceleration as there is no GUI. > I don't get this properly if desktop GUI is must for GPU usage. > Yes, if the server has an NVidia card and a recent driver it should be possible to use EGL. https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/ > > BR, > Bishwajit > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 nicolas.cedilnik at inria.fr Wed Feb 1 16:19:40 2017 From: nicolas.cedilnik at inria.fr (Nicolas Cedilnik) Date: Wed, 1 Feb 2017 22:19:40 +0100 Subject: [Paraview] "Rotate" look up table Message-ID: Hello, Would it be possible with python scripting to create an animation by "rotating" the look up table in a way that would look like this: https://www.youtube.com/watch?v=qA_vInXwdKM#t=3m25s ? It is a pseudo-animation created by changing the "range" of the LUT. Would paraview be the right tool to do that? I have a vtk file containing a triangular mesh with scalar values assigned to each point. I'm already using paraview and I'm pretty satisfied with the static output. I was wondering how complicated it would be to "pseudo-animate" it. Maybe someone can point me to some documentation or other tools that might do the job... Thanks -- Nicolas Cedilnik From andi3173 at gmail.com Wed Feb 1 18:07:11 2017 From: andi3173 at gmail.com (Andi Hartarto) Date: Thu, 2 Feb 2017 10:07:11 +1100 Subject: [Paraview] Node set and side set in Exodus format at Paraview Message-ID: Dear all, I'd like to have help about node sets and side sets in Paraview. My file is an Exodus file which doesn't have side set and node sets. I'd like to modify the data and add side set and node set. My data file is a cube and visually I can see smooth 6 surfaces. Does anyone know how to do that? Thank you, Andi -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundarg0000 at gmail.com Thu Feb 2 00:22:19 2017 From: sundarg0000 at gmail.com (Sundaresan G) Date: Thu, 2 Feb 2017 10:52:19 +0530 Subject: [Paraview] Fwd: Separate Axes Paraview 5.1.2 In-Reply-To: References: Message-ID: Hi Everyone, In paraview, there is only one set of axes that can be used. In the previous version i.e. 3.6.2, it was possible to use separate set of axes for every filter. But it is not the case in 5.1.2. In my case, I have generated pressure contour around an airfoil. I have applied Outline filter to look at data close to airfoil. I'm trying to apply axes only on the Outline box surrounding airfoil. I have also attached a screenshot. Please help me on applying axis display only on the Outline ignoring the rest. Thanking you Sundar -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 60 with outline.tif Type: image/tiff Size: 168766 bytes Desc: not available URL: From sinan_shabib at yahoo.com Thu Feb 2 05:46:51 2017 From: sinan_shabib at yahoo.com (sinan shabib) Date: Thu, 2 Feb 2017 10:46:51 +0000 (UTC) Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: References: Message-ID: <2096947504.1712063.1486032411095@mail.yahoo.com> Hi Andy, Thanks for your reply. I think you've mixed my question up with someone else?s.I still have the problem with data-visualization (data are read but not visualized). Andy Bauer schrieb am 19:02 Dienstag, 31.Januar 2017: Hi, Please keep the discussion on the mailing list so that anyone can participate (also, stuff gets lost in my Inbox too). The ParaView Catalyst Users Guide at http://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf has information on how to use the Live functionality. It's in Section 2.3. Best, Andy On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon wrote: Hi,?thanks a lot for the quick respons.At least now we know that there?s no point to keep on trying.?I?ll try to build and install it myself then.?Is there any previous thread where I can find out more about the simulation + catalyst linking to a parallel server??Best regards,Simon?From: Andy Bauer [mailto:andy.bauer at kitware.com ] Sent: Donnerstag, 26. Januar 2017 16:22 To: Kohlhase, Simon Cc: paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David Subject: Re: [Paraview] Paraview Live Visualisation C++ Pipeline?Hi,Currently the Live functionality only works when ParaView is built with Python bindings. My suggestion would be to build ParaView yourself. That should be much easier than trying to put in a C++ pipeline that can deal with the Live functionality properly. As for building ParaView, you may want to look into using the ParaView Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/) which will also build all needed dependencies. The dependencies are probably all there though since you've said that ParaView is already installed there.I'm not sure the set up you're looking for but if you want to run with the simulation+Catalyst linking to a parallel pvserver on the cluster which then connects to a client, you may want to use ParaView master. The reason for this is that there was a bug that had all of the simulation+Catalyst nodes only being able to communicate with a single pvserver node (multiple pvserver processes though). If you only want to connect the simulation+Catalyst to the GUI client or pvserver processes on a single node then 5.2 should work fine for you.Best,Andy ?On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon wrote: Hi,?for a University Project we?re trying to run Paraview Live Simulation on the local cluster-network. Unfortunately the network only has a Paraview version without python-binding installed, therefore we would like to run the LiveSimulation with a C++-coded Pipeline Skript.?As far as we understood, to make it work we have to rewrite the following lines from the PythonPipeline Script to C++, which turns out to be quite challenging:?coprocessor.UpdateProducers( datadescription)# Write output data, if appropriate.coprocessor.WriteData( datadescription);# Live Visualization, if enabled.coprocessor. DoLiveVisualization( datadescription, "localhost", 22222)?We tried the following:?//INITIALIZEvtkNew link;vtkSMProxyManager* proxyManager;vtkSMSessionProxyManager* sessionProxyManager;link -> SetInsituPort(22222);link -> SetHostname("localhost");proxyManager = vtkSMProxyManager:: GetProxyManager();sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ;link -> Initialize( sessionProxyManager);?// Initialize returns 1, therefore connection established properly?//Then we tried to coprocess with the following code:vtkNew writer;writer->SetInputConnection( producer->GetOutputPort());vtkSMProxy* proxy = sessionProxyManager->NewProxy( "insitu_writer_parameters"," XMLPImageDataWriter");vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> GetProperty("Input");?//set input of proxy to our writer or datadescription ? DOESN?T WORKwhile(true){? link->InsituUpdate( dataDescription->GetTime(), dataDescription->GetTimeStep() );? //update pipeline? link->InsituPostProcess( dataDescription->GetTime(), dataDescription->GetTimeStep() );? if(link->GetSimulationPaused() ){??? if(link->WaitForLiveChange()){?????break;??? }? } else{??? break;}? }?So how are we supposed to get the data from our simulation into the Proxy?We have been trying and searching the documentation for the right functions, but we can?t figure out how to do it.?We would really appreciate some help ;-)?Best regards,Simon Kohlhase ______________________________ _________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/ opensource/opensource.html Please keep messages on-topic and check the ParaView 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 bflandard at gmail.com Thu Feb 2 06:20:48 2017 From: bflandard at gmail.com (Bob Flandard) Date: Thu, 2 Feb 2017 11:20:48 +0000 Subject: [Paraview] Ansys to ParaView In-Reply-To: References: Message-ID: Hi Anxo, I don't what the capabilities of the Paraview Ansys reader are, but I don't think it can read results data, but that may have changed since I last looked. Try writing the cdb file as "unblocked" and then renaming the extension as *.inp. This may get the mesh in to Paraview but not the results. If your model isn't confidential or too large, you can upload the *.rst file to your Dropbox account and I'll try and convert it for you (*.rst files zip well). I can't give you the apdl scripts to do this as they belong to the company I work for. Regards, Bob On 2 February 2017 at 10:47, Anxo Mart?nez Dom?nguez wrote: > Hi Bob, > > Now, I am working with the ANSYS workbench. I know how to obtain the .cdb > (the model) and the .rst (the result). However, when I load those two files > from ParaView, it do not load anything. It seems strange to me, because > when I try to import the .cdb and .rst files, I choose the ANSYS reader in > ParavieW. > > Thanks! > Regards, > Anxo > > On Wed, Feb 1, 2017 at 12:45 PM, Bob Flandard wrote: > >> Hi Anxo, >> >> By upload, I mean to your dropbox account, not the ParaView server:) >> >> Regards, Bob >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Thu Feb 2 06:42:41 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Thu, 2 Feb 2017 12:42:41 +0100 Subject: [Paraview] Question about data (memory) management Message-ID: Dear all, Would the following construct be safe in terms of proper data handling inside a filter or would I generate some "unpredictable results", like data being copied over other data that is still being used? My purpose is of course to copy data only if it is absolutely required. And I assume that within the different filters, data are again handled correctly. ...::RequestData(...) { // get input and output vtkPolyData* input0 = vtkPolyData::SafeDownCast(info->Get(vtkDataObject::DATA_OBJECT())); vtkPolyData* output = vtkPolyData::SafeDownCast(...); ... // intermediate data storage vtkSmartPointer intermediateData = vtkSmartPointer::New(); // first filter vtkSmartPointer filt1 = vtkSmartPointer::New(); filt1->SetInputData(input0); ... filt1->Update(); intermediateData->ShallowCopy(filt1->GetOutput()); // second filter vtkSmartPointer filt2 = vtkSmartPointer::New(); filt2->SetInputData(intermediateData); ... filt2->Update(); intermediateData->ShallowCopy(filt2->GetOutput()); // !!! actually replacing the input data... // some more filters in the same way as filt2 - with always reusing intermediateData... ... // return the results output->ShallowCopy(intermediateData); } Any comments? Of course I could play safe and 1) replace all "ShallowCopy" with "DeepCopy", and 2) generate an intermediate data object for each and every filter that I am applying but this for sure would blow up my memory enormously! Maybe there is also some document that clearly states what is the proper "behaviour" inside filters like that, some kind of "code of conduct" regarding memory management in VTK? Thanks for any helpful hints! Regards, Cornelis -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Feb 2 08:20:15 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Feb 2017 08:20:15 -0500 Subject: [Paraview] Time Source for Data Arrays In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684379754A@MBX111.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F684379754A@MBX111.d.ethz.ch> Message-ID: Jean, (sorry for the delay) You're of course right :). I created the Python script after the fact, rather then as I was setting up the filter. You can add something like the following to the end of the script to update the timesteps in the UI. (Note, if you use Python Trace to open an data file, you'll see the following lines getting added to it automatically) #==================== # get animation scene animationScene1 = GetAnimationScene() # update animation scene based on data timesteps animationScene1.UpdateAnimationUsingDataTimeSteps() Utkarsh On Wed, Jan 25, 2017 at 11:07 AM, Favre Jean wrote: > I have examined Utkarsh's example because it is similar to one of my > projects. Thanks. > > Yet, I am sorry to say I cannot execute it cleanly, without a small edit. > > I run PV 5.2. > I execute script.py from the Python Shell. An image of the can is > displayed, yet what is not working is that the Information Tab has an empty > set of Timestep index, and Timestep Value. Consequently, the VCR Play > button will go thru timestep values = 0, 0.111, 0.222, 0.333, 0.444 etc.... > > My work-around is to go back to the ProgrammableSource and force > re-execution manually, by simply deleting the first empty line of "Script" > and forcing re-execution. > > This is more than an aesthetic problem. This prevents the correct > execution of time-dependent programmable sources in BATCH mode. I have yet > to manage to get my time-aware analysis working. > > Do you not run into the same problem? > > ----------------- > Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Feb 2 09:05:54 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 2 Feb 2017 09:05:54 -0500 Subject: [Paraview] Fwd: Separate Axes Paraview 5.1.2 In-Reply-To: References: Message-ID: Separate axes per filter are not possible in ParaView 5.1.2 or 5.2.0, but are slated to be be brought back in 5.3: https://gitlab.kitware.com/paraview/paraview/issues/16878 Cory On Thu, Feb 2, 2017 at 12:22 AM, Sundaresan G wrote: > Hi Everyone, > > In paraview, there is only one set of axes that can be used. In the previous > version i.e. 3.6.2, it was possible to use separate set of axes for every > filter. But it is not the case in 5.1.2. > > In my case, I have generated pressure contour around an airfoil. I have > applied Outline filter to look at data close to airfoil. I'm trying to apply > axes only on the Outline box surrounding airfoil. > > I have also attached a screenshot. Please help me on applying axis display > only on the Outline ignoring the rest. > > Thanking you > > Sundar > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Thu Feb 2 09:25:06 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 2 Feb 2017 09:25:06 -0500 Subject: [Paraview] Fwd: Separate Axes Paraview 5.1.2 In-Reply-To: References: Message-ID: Actually, the feature is slated for 5.4, not 5.3. ParaView 5.4 is scheduled to come out in June 2017. Thanks, Cory On Thu, Feb 2, 2017 at 9:05 AM, Cory Quammen wrote: > Separate axes per filter are not possible in ParaView 5.1.2 or 5.2.0, > but are slated to be be brought back in 5.3: > > https://gitlab.kitware.com/paraview/paraview/issues/16878 > > Cory > > On Thu, Feb 2, 2017 at 12:22 AM, Sundaresan G wrote: >> Hi Everyone, >> >> In paraview, there is only one set of axes that can be used. In the previous >> version i.e. 3.6.2, it was possible to use separate set of axes for every >> filter. But it is not the case in 5.1.2. >> >> In my case, I have generated pressure contour around an airfoil. I have >> applied Outline filter to look at data close to airfoil. I'm trying to apply >> axes only on the Outline box surrounding airfoil. >> >> I have also attached a screenshot. Please help me on applying axis display >> only on the Outline ignoring the rest. >> >> Thanking you >> >> Sundar >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 utkarsh.ayachit at kitware.com Thu Feb 2 09:46:08 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Feb 2017 09:46:08 -0500 Subject: [Paraview] Question about data (memory) management In-Reply-To: References: Message-ID: In general (unless I missed something), it looks fine. A couple of notes: 1. You don't need to even shallow copy, you can simply save the output from any of the internal filters (I typically use a vtkSmartPointer to hold on to the reference). e.g. vtkSmartPointer intermediaResult = filt1->GetOutput(); 2. You can connect fil1 and filt2 in a pipeline too, to avoid keeping the intermediate dataset explicitly: filter2->SetInputConnection(filt1->GetOutputPort()); filter2->Update(); output->ShallowCopy(filter2->GetOutput()); On Thu, Feb 2, 2017 at 6:42 AM, Cornelis Bockem?hl < cornelis.bockemuehl at gmail.com> wrote: > Dear all, > > Would the following construct be safe in terms of proper data handling > inside a filter or would I generate some "unpredictable results", like data > being copied over other data that is still being used? > > My purpose is of course to copy data only if it is absolutely required. > And I assume that within the different filters, data are again handled > correctly. > > ...::RequestData(...) > { > // get input and output > vtkPolyData* input0 = vtkPolyData::SafeDownCast( > info->Get(vtkDataObject::DATA_OBJECT())); > vtkPolyData* output = vtkPolyData::SafeDownCast(...); > ... > > // intermediate data storage > vtkSmartPointer intermediateData = > vtkSmartPointer::New(); > > // first filter > vtkSmartPointer filt1 = vtkSmartPointer > ::New(); > filt1->SetInputData(input0); > ... > filt1->Update(); > intermediateData->ShallowCopy(filt1->GetOutput()); > > // second filter > vtkSmartPointer filt2 = vtkSmartPointer< > vtkSomeOtherFilter>::New(); > filt2->SetInputData(intermediateData); > ... > filt2->Update(); > intermediateData->ShallowCopy(filt2->GetOutput()); // !!! actually > replacing the input data... > > // some more filters in the same way as filt2 - with always reusing > intermediateData... > ... > > // return the results > output->ShallowCopy(intermediateData); > } > > Any comments? > > Of course I could play safe and > > 1) replace all "ShallowCopy" with "DeepCopy", and > 2) generate an intermediate data object for each and every filter that I > am applying > > but this for sure would blow up my memory enormously! > > Maybe there is also some document that clearly states what is the proper > "behaviour" inside filters like that, some kind of "code of conduct" > regarding memory management in VTK? > > Thanks for any helpful hints! > > Regards, > Cornelis > > -- > Cornelis Bockem?hl > Basel, Schweiz > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Mark.Olesen at esi-group.com Thu Feb 2 09:51:12 2017 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Thu, 2 Feb 2017 14:51:12 +0000 Subject: [Paraview] ruler filter in paraview-git Message-ID: I don't know if this is a regression or change of feature or what exactly. Using paraview 5.2.0-g332666c (64bit, linux) and the 'ruler' filter only seems to have the following properties: * x/y/z axis enumeration. That's all. In a previous version (5.0.1) there was also the ability to specify the begin/end points and even to select them on an existing mesh point. Now the ruler just seems to display the overall length of the object in a particular axis. Is this a feature or bug? Cheers, /mark From andy.bauer at kitware.com Thu Feb 2 09:59:58 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 2 Feb 2017 09:59:58 -0500 Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: <2096947504.1712063.1486032411095@mail.yahoo.com> References: <2096947504.1712063.1486032411095@mail.yahoo.com> Message-ID: Maybe I didn't understand what you were trying to do. Can you be a bit more specific? On Thu, Feb 2, 2017 at 5:46 AM, sinan shabib wrote: > Hi Andy, > > Thanks for your reply. > > I think you've mixed my question up with someone else?s. > I still have the problem with data-visualization (data are read but not > visualized). > > > > Andy Bauer schrieb am 19:02 Dienstag, 31.Januar > 2017: > > > Hi, > > Please keep the discussion on the mailing list so that anyone can > participate (also, stuff gets lost in my Inbox too). > > The ParaView Catalyst Users Guide at http://www.paraview.org/files/ > catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf has information on how to > use the Live functionality. It's in Section 2.3. > > Best, > Andy > > On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon > wrote: > > Hi, > > thanks a lot for the quick respons. > At least now we know that there?s no point to keep on trying. > > I?ll try to build and install it myself then. > > Is there any previous thread where I can find out more about the > simulation + catalyst linking to a parallel server? > > Best regards, > Simon > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com ] > *Sent:* Donnerstag, 26. Januar 2017 16:22 > *To:* Kohlhase, Simon > *Cc:* paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David < > david.damerow at tum.de> > *Subject:* Re: [Paraview] Paraview Live Visualisation C++ Pipeline > > Hi, > Currently the Live functionality only works when ParaView is built with > Python bindings. My suggestion would be to build ParaView yourself. That > should be much easier than trying to put in a C++ pipeline that can deal > with the Live functionality properly. > As for building ParaView, you may want to look into using the ParaView > Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/ > ) which will > also build all needed dependencies. The dependencies are probably all there > though since you've said that ParaView is already installed there. > I'm not sure the set up you're looking for but if you want to run with the > simulation+Catalyst linking to a parallel pvserver on the cluster which > then connects to a client, you may want to use ParaView master. The reason > for this is that there was a bug that had all of the simulation+Catalyst > nodes only being able to communicate with a single pvserver node (multiple > pvserver processes though). If you only want to connect the > simulation+Catalyst to the GUI client or pvserver processes on a single > node then 5.2 should work fine for you. > Best, > Andy > > On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon > wrote: > > Hi, > > for a University Project we?re trying to run Paraview Live Simulation on > the local cluster-network. Unfortunately the network only has a Paraview > version without python-binding installed, therefore we would like to run > the LiveSimulation with a C++-coded Pipeline Skript. > > As far as we understood, to make it work we have to rewrite the following > lines from the PythonPipeline Script to C++, which turns out to be quite > challenging: > > coprocessor.UpdateProducers( datadescription) > # Write output data, if appropriate. > coprocessor.WriteData( datadescription); > # Live Visualization, if enabled. > coprocessor. DoLiveVisualization( datadescription, "localhost", 22222) > > We tried the following: > > //INITIALIZE > vtkNew link; > vtkSMProxyManager* proxyManager; > vtkSMSessionProxyManager* sessionProxyManager; > link -> SetInsituPort(22222); > link -> SetHostname("localhost"); > proxyManager = vtkSMProxyManager:: GetProxyManager(); > sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ; > link -> Initialize( sessionProxyManager); > > // Initialize returns 1, therefore connection established properly > > //Then we tried to coprocess with the following code: > vtkNew writer; > writer->SetInputConnection( producer->GetOutputPort()); > vtkSMProxy* proxy = sessionProxyManager->NewProxy( > "insitu_writer_parameters"," XMLPImageDataWriter"); > vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> > GetProperty("Input"); > > //set input of proxy to our writer or datadescription ? DOESN?T WORK > while(true){ > link->InsituUpdate( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > //update pipeline > link->InsituPostProcess( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > if(link->GetSimulationPaused() ){ > if(link->WaitForLiveChange()){ > break; > } > } else{ > break; > } > } > > So how are we supposed to get the data from our simulation into the Proxy? > We have been trying and searching the documentation for the right > functions, but we can?t figure out how to do it. > > We would really appreciate some help ;-) > > Best regards, > Simon Kohlhase > > ______________________________ _________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 shawn.waldon at kitware.com Thu Feb 2 09:59:58 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 2 Feb 2017 09:59:58 -0500 Subject: [Paraview] ruler filter in paraview-git In-Reply-To: References: Message-ID: Hi Mark, So the confusion is that there are now two rulers in ParaView. The one under the filters menu is the one you are seeing. It was added so that the user could measure the dataset in each dimension (and possibly it could be extended to selecting other measurements). The older behavior is the Ruler under the Sources menu (it doesn't take an input dataset, but you can freely set its end points). The fact that they are named the same means that the Ctrl-Space search favors the one in the filters menu. Perhaps we could change the name of one of them to make it more clear? HTH, Shawn On Thu, Feb 2, 2017 at 9:51 AM, Mark Olesen wrote: > I don't know if this is a regression or change of feature or what exactly. > Using paraview 5.2.0-g332666c (64bit, linux) and the 'ruler' filter only > seems to have the following properties: > * x/y/z axis enumeration. > > That's all. In a previous version (5.0.1) there was also the ability to > specify the begin/end points and even to select them on an existing mesh > point. Now the ruler just seems to display the overall length of the object > in a particular axis. > > Is this a feature or bug? > > Cheers, > /mark > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 cornelis.bockemuehl at gmail.com Thu Feb 2 10:07:41 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Thu, 2 Feb 2017 16:07:41 +0100 Subject: [Paraview] Question about data (memory) management In-Reply-To: References: Message-ID: Thanks for confirming what I assumed but was not able to fully verify myself! With that first smart pointer I would not have "dared" to go because I would now know whether the output data is already managed by some smart pointer inside the filter. Meaning that the memory would be released once the filter goes out of scope - with the result that the new smart pointer would not really have control of that memory! This is why I felt more "safe" by using one extra data item in my own code. But now I am taking your word that this is not going to happen. Actually the memory for the input and output objects seems to be managed by the caller of RequestData() anyway, no need to manage that memory inside the function. Regards, Cornelis 2017-02-02 15:46 GMT+01:00 Utkarsh Ayachit : > In general (unless I missed something), it looks fine. A couple of notes: > > 1. You don't need to even shallow copy, you can simply save the output > from any of the internal filters (I typically use a vtkSmartPointer to hold > on to the reference). e.g. > > vtkSmartPointer intermediaResult = filt1->GetOutput(); > > 2. You can connect fil1 and filt2 in a pipeline too, to avoid keeping the > intermediate dataset explicitly: > > filter2->SetInputConnection(filt1->GetOutputPort()); > filter2->Update(); > output->ShallowCopy(filter2->GetOutput()); > > > > On Thu, Feb 2, 2017 at 6:42 AM, Cornelis Bockem?hl < > cornelis.bockemuehl at gmail.com> wrote: > >> Dear all, >> >> Would the following construct be safe in terms of proper data handling >> inside a filter or would I generate some "unpredictable results", like data >> being copied over other data that is still being used? >> >> My purpose is of course to copy data only if it is absolutely required. >> And I assume that within the different filters, data are again handled >> correctly. >> >> ...::RequestData(...) >> { >> // get input and output >> vtkPolyData* input0 = vtkPolyData::SafeDownCast(in >> fo->Get(vtkDataObject::DATA_OBJECT())); >> vtkPolyData* output = vtkPolyData::SafeDownCast(...); >> ... >> >> // intermediate data storage >> vtkSmartPointer intermediateData = >> vtkSmartPointer::New(); >> >> // first filter >> vtkSmartPointer filt1 = vtkSmartPointer >> ::New(); >> filt1->SetInputData(input0); >> ... >> filt1->Update(); >> intermediateData->ShallowCopy(filt1->GetOutput()); >> >> // second filter >> vtkSmartPointer filt2 = >> vtkSmartPointer::New(); >> filt2->SetInputData(intermediateData); >> ... >> filt2->Update(); >> intermediateData->ShallowCopy(filt2->GetOutput()); // !!! actually >> replacing the input data... >> >> // some more filters in the same way as filt2 - with always reusing >> intermediateData... >> ... >> >> // return the results >> output->ShallowCopy(intermediateData); >> } >> >> Any comments? >> >> Of course I could play safe and >> >> 1) replace all "ShallowCopy" with "DeepCopy", and >> 2) generate an intermediate data object for each and every filter that I >> am applying >> >> but this for sure would blow up my memory enormously! >> >> Maybe there is also some document that clearly states what is the proper >> "behaviour" inside filters like that, some kind of "code of conduct" >> regarding memory management in VTK? >> >> Thanks for any helpful hints! >> >> Regards, >> Cornelis >> >> -- >> Cornelis Bockem?hl >> Basel, Schweiz >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 >> >> > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From sinan_shabib at yahoo.com Thu Feb 2 10:12:00 2017 From: sinan_shabib at yahoo.com (sinan shabib) Date: Thu, 2 Feb 2017 15:12:00 +0000 (UTC) Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: References: <2096947504.1712063.1486032411095@mail.yahoo.com> Message-ID: <613524816.2096230.1486048320776@mail.yahoo.com> Hi, I apologize,I didn?t explain it well. I?m using: Paraview 5.2.0-RC1 , 64 bit. All fields data are being read but not visualized, that is, I get only one color when I color the data with a specific field.However, when I use "find data" function, I can see the data.This happens only with: velocity & pressure.I?m working on several configurations & the same thing happens with all of them. Is it a bug or VTK has been corrupted or something else ? Thanks in advance. Andy Bauer schrieb am 16:00 Donnerstag, 2.Februar 2017: Maybe I didn't understand what you were trying to do. Can you be a bit more specific? On Thu, Feb 2, 2017 at 5:46 AM, sinan shabib wrote: Hi Andy, Thanks for your reply. I think you've mixed my question up with someone else?s.I still have the problem with data-visualization (data are read but not visualized). Andy Bauer schrieb am 19:02 Dienstag, 31.Januar 2017: Hi, Please keep the discussion on the mailing list so that anyone can participate (also, stuff gets lost in my Inbox too). The ParaView Catalyst Users Guide at http://www.paraview.org/files/ catalyst/docs/ ParaViewCatalystUsersGuide_v2. pdf has information on how to use the Live functionality. It's in Section 2.3. Best, Andy On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon wrote: Hi,?thanks a lot for the quick respons.At least now we know that there?s no point to keep on trying.?I?ll try to build and install it myself then.?Is there any previous thread where I can find out more about the simulation + catalyst linking to a parallel server??Best regards,Simon?From: Andy Bauer [mailto:andy.bauer at kitware.com ] Sent: Donnerstag, 26. Januar 2017 16:22 To: Kohlhase, Simon Cc: paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David Subject: Re: [Paraview] Paraview Live Visualisation C++ Pipeline?Hi,Currently the Live functionality only works when ParaView is built with Python bindings. My suggestion would be to build ParaView yourself. That should be much easier than trying to put in a C++ pipeline that can deal with the Live functionality properly. As for building ParaView, you may want to look into using the ParaView Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/) which will also build all needed dependencies. The dependencies are probably all there though since you've said that ParaView is already installed there.I'm not sure the set up you're looking for but if you want to run with the simulation+Catalyst linking to a parallel pvserver on the cluster which then connects to a client, you may want to use ParaView master. The reason for this is that there was a bug that had all of the simulation+Catalyst nodes only being able to communicate with a single pvserver node (multiple pvserver processes though). If you only want to connect the simulation+Catalyst to the GUI client or pvserver processes on a single node then 5.2 should work fine for you.Best,Andy ?On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon wrote: Hi,?for a University Project we?re trying to run Paraview Live Simulation on the local cluster-network. Unfortunately the network only has a Paraview version without python-binding installed, therefore we would like to run the LiveSimulation with a C++-coded Pipeline Skript.?As far as we understood, to make it work we have to rewrite the following lines from the PythonPipeline Script to C++, which turns out to be quite challenging:?coprocessor.UpdateProducers( datadescription)# Write output data, if appropriate.coprocessor.WriteData( datadescription);# Live Visualization, if enabled.coprocessor. DoLiveVisualization( datadescription, "localhost", 22222)?We tried the following:?//INITIALIZEvtkNew link;vtkSMProxyManager* proxyManager;vtkSMSessionProxyManager* sessionProxyManager;link -> SetInsituPort(22222);link -> SetHostname("localhost");proxyManager = vtkSMProxyManager:: GetProxyManager();sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ;link -> Initialize( sessionProxyManager);?// Initialize returns 1, therefore connection established properly?//Then we tried to coprocess with the following code:vtkNew writer;writer->SetInputConnection( producer->GetOutputPort());vtkSMProxy* proxy = sessionProxyManager->NewProxy( "insitu_writer_parameters"," XMLPImageDataWriter");vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> GetProperty("Input");?//set input of proxy to our writer or datadescription ? DOESN?T WORKwhile(true){? link->InsituUpdate( dataDescription->GetTime(), dataDescription->GetTimeStep() );? //update pipeline? link->InsituPostProcess( dataDescription->GetTime(), dataDescription->GetTimeStep() );? if(link->GetSimulationPaused() ){??? if(link->WaitForLiveChange()){?????break;??? }? } else{??? break;}? }?So how are we supposed to get the data from our simulation into the Proxy?We have been trying and searching the documentation for the right functions, but we can?t figure out how to do it.?We would really appreciate some help ;-)?Best regards,Simon Kohlhase ______________________________ _________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/ opensource/opensource.html Please keep messages on-topic and check the ParaView 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 andy.bauer at kitware.com Thu Feb 2 11:42:42 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 2 Feb 2017 11:42:42 -0500 Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: <613524816.2096230.1486048320776@mail.yahoo.com> References: <2096947504.1712063.1486032411095@mail.yahoo.com> <613524816.2096230.1486048320776@mail.yahoo.com> Message-ID: Hi, Can you share a data set that you are having an issue with? On Thu, Feb 2, 2017 at 10:12 AM, sinan shabib wrote: > Hi, > > I apologize,I didn?t explain it well. > > I?m using: *Paraview 5.2.0-RC1 , 64 bit.* > > All fields data are being read but not visualized, that is, I get only one > color when I color the data with a specific field. > However, when I use "find data" function, I can see the data. > This happens only with: velocity & pressure. > I?m working on several configurations & the same thing happens with all of > them. > > Is it a bug or VTK has been corrupted or something else ? > > Thanks in advance. > > > > > > Andy Bauer schrieb am 16:00 Donnerstag, > 2.Februar 2017: > > > Maybe I didn't understand what you were trying to do. Can you be a bit > more specific? > > On Thu, Feb 2, 2017 at 5:46 AM, sinan shabib > wrote: > > Hi Andy, > > Thanks for your reply. > > I think you've mixed my question up with someone else?s. > I still have the problem with data-visualization (data are read but not > visualized). > > > > Andy Bauer schrieb am 19:02 Dienstag, 31.Januar > 2017: > > > Hi, > > Please keep the discussion on the mailing list so that anyone can > participate (also, stuff gets lost in my Inbox too). > > The ParaView Catalyst Users Guide at http://www.paraview.org/files/ > catalyst/docs/ ParaViewCatalystUsersGuide_v2. pdf > > has information on how to use the Live functionality. It's in Section 2.3. > > Best, > Andy > > On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon > wrote: > > Hi, > > thanks a lot for the quick respons. > At least now we know that there?s no point to keep on trying. > > I?ll try to build and install it myself then. > > Is there any previous thread where I can find out more about the > simulation + catalyst linking to a parallel server? > > Best regards, > Simon > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com ] > *Sent:* Donnerstag, 26. Januar 2017 16:22 > *To:* Kohlhase, Simon > *Cc:* paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David < > david.damerow at tum.de> > *Subject:* Re: [Paraview] Paraview Live Visualisation C++ Pipeline > > Hi, > Currently the Live functionality only works when ParaView is built with > Python bindings. My suggestion would be to build ParaView yourself. That > should be much easier than trying to put in a C++ pipeline that can deal > with the Live functionality properly. > As for building ParaView, you may want to look into using the ParaView > Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/ > ) which will > also build all needed dependencies. The dependencies are probably all there > though since you've said that ParaView is already installed there. > I'm not sure the set up you're looking for but if you want to run with the > simulation+Catalyst linking to a parallel pvserver on the cluster which > then connects to a client, you may want to use ParaView master. The reason > for this is that there was a bug that had all of the simulation+Catalyst > nodes only being able to communicate with a single pvserver node (multiple > pvserver processes though). If you only want to connect the > simulation+Catalyst to the GUI client or pvserver processes on a single > node then 5.2 should work fine for you. > Best, > Andy > > On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon > wrote: > > Hi, > > for a University Project we?re trying to run Paraview Live Simulation on > the local cluster-network. Unfortunately the network only has a Paraview > version without python-binding installed, therefore we would like to run > the LiveSimulation with a C++-coded Pipeline Skript. > > As far as we understood, to make it work we have to rewrite the following > lines from the PythonPipeline Script to C++, which turns out to be quite > challenging: > > coprocessor.UpdateProducers( datadescription) > # Write output data, if appropriate. > coprocessor.WriteData( datadescription); > # Live Visualization, if enabled. > coprocessor. DoLiveVisualization( datadescription, "localhost", 22222) > > We tried the following: > > //INITIALIZE > vtkNew link; > vtkSMProxyManager* proxyManager; > vtkSMSessionProxyManager* sessionProxyManager; > link -> SetInsituPort(22222); > link -> SetHostname("localhost"); > proxyManager = vtkSMProxyManager:: GetProxyManager(); > sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ; > link -> Initialize( sessionProxyManager); > > // Initialize returns 1, therefore connection established properly > > //Then we tried to coprocess with the following code: > vtkNew writer; > writer->SetInputConnection( producer->GetOutputPort()); > vtkSMProxy* proxy = sessionProxyManager->NewProxy( > "insitu_writer_parameters"," XMLPImageDataWriter"); > vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> > GetProperty("Input"); > > //set input of proxy to our writer or datadescription ? DOESN?T WORK > while(true){ > link->InsituUpdate( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > //update pipeline > link->InsituPostProcess( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > if(link->GetSimulationPaused() ){ > if(link->WaitForLiveChange()){ > break; > } > } else{ > break; > } > } > > So how are we supposed to get the data from our simulation into the Proxy? > We have been trying and searching the documentation for the right > functions, but we can?t figure out how to do it. > > We would really appreciate some help ;-) > > Best regards, > Simon Kohlhase > > ______________________________ _________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 Mark.Olesen at esi-group.com Thu Feb 2 12:32:21 2017 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Thu, 2 Feb 2017 17:32:21 +0000 Subject: [Paraview] ruler filter in paraview-git In-Reply-To: References: , Message-ID: Hi Shawn, Thanks for the quick reply. The confusion is indeed unfortunately and might be cause to consider different names before this becomes a FAQ. Beyond that, it is a pleasant surprise to see that the 'old' ruler has improved functionality compared to the 5.0.1 version. The additional Ctrl-1, Ctrl-2 keys for picking the end points make a *very* welcome addition! Cheers, /mark ________________________________________ From: Shawn Waldon Sent: Thursday, February 2, 2017 3:59 PM To: Mark Olesen Cc: paraview at paraview.org Subject: Re: [Paraview] ruler filter in paraview-git Hi Mark, So the confusion is that there are now two rulers in ParaView. The one under the filters menu is the one you are seeing. It was added so that the user could measure the dataset in each dimension (and possibly it could be extended to selecting other measurements). The older behavior is the Ruler under the Sources menu (it doesn't take an input dataset, but you can freely set its end points). The fact that they are named the same means that the Ctrl-Space search favors the one in the filters menu. Perhaps we could change the name of one of them to make it more clear? HTH, Shawn On Thu, Feb 2, 2017 at 9:51 AM, Mark Olesen > wrote: I don't know if this is a regression or change of feature or what exactly. Using paraview 5.2.0-g332666c (64bit, linux) and the 'ruler' filter only seems to have the following properties: * x/y/z axis enumeration. That's all. In a previous version (5.0.1) there was also the ability to specify the begin/end points and even to select them on an existing mesh point. Now the ruler just seems to display the overall length of the object in a particular axis. Is this a feature or bug? Cheers, /mark _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 agsmith424 at gmail.com Thu Feb 2 17:14:27 2017 From: agsmith424 at gmail.com (Andy Smith) Date: Thu, 2 Feb 2017 17:14:27 -0500 Subject: [Paraview] Rendering Backend OpenGL2 & PV 5.2.0-RC4 & SurfaceLic --> Problem... In-Reply-To: References: <84a5a6aa-326f-a1ff-7789-28204a0ee502@DLR.de> Message-ID: I've tested this with the latest ParaView and it does seem to run much faster. I am having a problem when running in parallel though. If one processor does not have anything to display, the rendering hangs. Related to that, what routine actually calls vtkCompositeLICHelper::RenderPiece? The process that does not have anything to display never gets to that function but the other processes do. In that function there are MPI calls where the rendering hangs. As a reply to Chuck: I can use EGL in some instances but unfortunately not all of our machine have GPUs so software rendering is still required. Thanks again for all the help. On Mon, Jan 23, 2017 at 12:45 PM, Ken Martin wrote: > There is a VTK topic now that should fix this regression. With this change > OpenGL2 LIC seems to run much faster (at least 10X). > > https://gitlab.kitware.com/vtk/vtk/merge_requests/2419 > > Hopefully it will test out OK and get merged into VTK and then merged into > ParaView. > > On Mon, Dec 12, 2016 at 11:38 AM, Andy Smith wrote: > >> Ken, >> >> You are correct in your assumption about my dataset; it is multiblock >> unstructured data. Adding a MergeBlocks filter to my slice does improve >> the 5.2.0 with OpenGL2 significantly. >> With that change the performance of 5.2.0 with OpenGL2 is on the same >> order of magnitude as 5.2.0 with OpenGL and with 4.4.0, though the 5.2.0 >> variants are still slower than 4.4.0. >> >> I realized after posting that my comparison is not exactly apples to >> apples - my build of 5.2.0 required updates to mesa (13.0.0) compared with >> the version I used for 4.4.0 (11.2.0). >> I will recompile 4.4.0 with the same mesa version I used with 5.2.0 and >> report back. >> >> Thank you for your input. >> >> -Andy >> >> On Fri, Dec 9, 2016 at 3:44 PM, Ken Martin >> wrote: >> >>> I have not had time to look into this, but my quick guess is that you >>> have a multiblock dataset with a lot of blocks. Can you try merging the >>> blocks all together somehow into one block and see if the rendering speed >>> improves? >>> >>> On Tue, Nov 15, 2016 at 5:35 AM, Stefan Melber >>> wrote: >>> >>>> Hi, >>>> >>>> >>>> i have a problem which is there in all RCs (1-4) of current ParaView: >>>> if i compile the RenderingBackend to "OpenGL2" and use SurfaceLic the >>>> visualization time goes up from a few seconds (with "OpenGL") to many >>>> minutes and the memory consumption from a few GByte to approx 100 GByte. >>>> Switching back to OpenGL any thing is fine. Without SurfaceLIC the OpenGL2 >>>> works although fine for me. >>>> >>>> Has any one tested OpenGL2 with SurfaceLIC-Plugin the last time and has >>>> (the same) problems? >>>> >>>> o Kernel 4.7.6-1 / x86-64 >>>> o Quadro 4000 >>>> o NVidia driver v367.57 >>>> o PV 5.2.0 RC1 - RC4 >>>> >>>> Best regards, >>>> >>>> Stefan >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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 >>>> >>>> >>> >>> >>> -- >>> 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 >>> >>> >> > > > -- > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emrahersanerdogan at gmail.com Thu Feb 2 17:58:17 2017 From: emrahersanerdogan at gmail.com (Emrah Ersan Erdogan) Date: Thu, 2 Feb 2017 23:58:17 +0100 Subject: [Paraview] First trial file does not work-help! Message-ID: Hi, I am a new user of paraview and try to understand .vtu file format. Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. Thanks a bunch! Ersan 2.0 2.0 3.0 1.0 From kevin.dean at decisionsciencescorp.com Thu Feb 2 18:19:43 2017 From: kevin.dean at decisionsciencescorp.com (Dean, Kevin) Date: Thu, 2 Feb 2017 15:19:43 -0800 Subject: [Paraview] Labeling Polydatas Message-ID: Hey Guys, So I understand how to utilize the selection display inspector to visualize a cell id number. However, is there a way to have the labels associated with the polydata (or all inside of an vtkAppendPolyData) so that when I load my .vtp, I automatically see the Cell Ids? -- This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please report the error to the sender by return email and delete this communication from your records. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Feb 2 19:24:01 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 3 Feb 2017 00:24:01 +0000 Subject: [Paraview] First trial file does not work-help! Message-ID: <8AA87C27-EE38-446E-80C4-84E18EA6DCF4@sandia.gov> Did you type this in a text editor? The first thing I notice is that many of the quotes are the fancy open/close characters. Many text editors use a ?smart quotes? feature that replaces the straight quote to a bent open or closed quote. The VTK reader only accepts the straight quotes (ASCII character 34). -Ken On 2/2/17, 5:58 PM, "ParaView on behalf of Emrah Ersan Erdogan" wrote: Hi, I am a new user of paraview and try to understand .vtu file format. Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. Thanks a bunch! Ersan 2.0 2.0 3.0 1.0 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Feb 2 22:51:54 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Feb 2017 22:51:54 -0500 Subject: [Paraview] Silo reader, working with data In-Reply-To: References: Message-ID: Mark, Can you share the data (feel free to do it off the mailing list, if needed)? That will make it easier to understand your problem. Utkarsh On Wed, Feb 1, 2017 at 10:01 AM, Messner, Mark Christian wrote: > > Hello, > > This is a basic question but I wasn't able to find any info by searching > the mailing list. > > I successfully compiled Paraview with VisitBridge and the silo reader and > read in my silo data. The actual result arrays are stored as separate cell > and point arrays in the multiblock not associated with the mesh (see > screenshot). > > How do I use (for example contour) the data in the cell arrays and point > arrays? I tried "Cell Data to Point Data" which was suggested in a > previous post but had no luck. > > Thanks, > > Mark > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 f_magician at mac.com Fri Feb 3 00:53:06 2017 From: f_magician at mac.com (Magician) Date: Fri, 03 Feb 2017 14:53:06 +0900 Subject: [Paraview] Save Programmable VTKImageData as PNG images Message-ID: Hi all, I have some 2D VTKImageData and export them as PNG images using 'Save Data...'. I'm trying to get color values from original sources and convert them to 8 or 16-bit color values with Programmable Filter. But if I apply 'Save Data...' to the results, no PNG images exported and get warnings as below: > Warning: In /Users/kitware/buildbot-slave/b99e1795/source-paraview/VTK/IO/Image/vtkPNGWriter.cxx, line 231 > vtkPNGWriter (0x6000005a8260): PNGWriter only supports unsigned char and unsigned short inputs The attached dataset is a tiny sample. (including no dtype converter, but reproduces same problems) The data type of the PNGImage value of ProgrammableFilter1 should be 'unsigned char', but we may not be able to save it as a PNG image. Is it a bug? Magician -------------- next part -------------- A non-text attachment was scrubbed... Name: ProgrammableImageDataSample.pvsm Type: application/octet-stream Size: 139537 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pvIcon-512x512.png Type: image/png Size: 34431 bytes Desc: not available URL: From nicolas.cedilnik at inria.fr Fri Feb 3 03:47:07 2017 From: nicolas.cedilnik at inria.fr (Nicolas Cedilnik) Date: Fri, 3 Feb 2017 09:47:07 +0100 Subject: [Paraview] "Rotate" look up table In-Reply-To: References: Message-ID: Hi all, I'm replying to my own email because I worked out a solution and wanted to share but also because I believe what I'm doing is FAR from optimal and hope that someone > Would it be possible with python scripting to create an animation by > "rotating" the look up table in a way that would look like this: > https://www.youtube.com/watch?v=qA_vInXwdKM#t=3m25s ? It is a > pseudo-animation created by changing the "range" of the LUT. So I made this python script (see attachment) that generates different meshes with scalar values "rotated" (I don't find a better term to describe what I'm doing). It works and make it easy to play the animation by opening the produced vtk files as a sequence in paraview. However, every vtk file contains both the mesh geometry and the scalar values, but only the latter change. What would be the right way to animate only the scalar values and not the mesh geometry? What data format should I use? How could I import it into an animation in paraview? Thanks for your guidance -- Nicolas -------------- next part -------------- A non-text attachment was scrubbed... Name: rotate_scalar_values.py Type: text/x-python Size: 1287 bytes Desc: not available URL: From sinan_shabib at yahoo.com Fri Feb 3 05:54:53 2017 From: sinan_shabib at yahoo.com (sinan shabib) Date: Fri, 3 Feb 2017 10:54:53 +0000 (UTC) Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: References: <2096947504.1712063.1486032411095@mail.yahoo.com> <613524816.2096230.1486048320776@mail.yahoo.com> Message-ID: <1274303005.358629.1486119293917@mail.yahoo.com> Hi Andy, Could you please tell me, which data set you need ?Because it?s big data. I?m doing (Ensight 6) format. Greetings. Andy Bauer schrieb am 17:42 Donnerstag, 2.Februar 2017: Hi, Can you share a data set that you are having an issue with? On Thu, Feb 2, 2017 at 10:12 AM, sinan shabib wrote: Hi, I apologize,I didn?t explain it well. I?m using: Paraview 5.2.0-RC1 , 64 bit. All fields data are being read but not visualized, that is, I get only one color when I color the data with a specific field.However, when I use "find data" function, I can see the data.This happens only with: velocity & pressure.I?m working on several configurations & the same thing happens with all of them. Is it a bug or VTK has been corrupted or something else ? Thanks in advance. Andy Bauer schrieb am 16:00 Donnerstag, 2.Februar 2017: Maybe I didn't understand what you were trying to do. Can you be a bit more specific? On Thu, Feb 2, 2017 at 5:46 AM, sinan shabib wrote: Hi Andy, Thanks for your reply. I think you've mixed my question up with someone else?s.I still have the problem with data-visualization (data are read but not visualized). Andy Bauer schrieb am 19:02 Dienstag, 31.Januar 2017: Hi, Please keep the discussion on the mailing list so that anyone can participate (also, stuff gets lost in my Inbox too). The ParaView Catalyst Users Guide at http://www.paraview.org/files/ catalyst/docs/ ParaViewCatalystUsersGuide_v2. pdf has information on how to use the Live functionality. It's in Section 2.3. Best, Andy On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon wrote: Hi,?thanks a lot for the quick respons.At least now we know that there?s no point to keep on trying.?I?ll try to build and install it myself then.?Is there any previous thread where I can find out more about the simulation + catalyst linking to a parallel server??Best regards,Simon?From: Andy Bauer [mailto:andy.bauer at kitware.com ] Sent: Donnerstag, 26. Januar 2017 16:22 To: Kohlhase, Simon Cc: paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David Subject: Re: [Paraview] Paraview Live Visualisation C++ Pipeline?Hi,Currently the Live functionality only works when ParaView is built with Python bindings. My suggestion would be to build ParaView yourself. That should be much easier than trying to put in a C++ pipeline that can deal with the Live functionality properly. As for building ParaView, you may want to look into using the ParaView Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/) which will also build all needed dependencies. The dependencies are probably all there though since you've said that ParaView is already installed there.I'm not sure the set up you're looking for but if you want to run with the simulation+Catalyst linking to a parallel pvserver on the cluster which then connects to a client, you may want to use ParaView master. The reason for this is that there was a bug that had all of the simulation+Catalyst nodes only being able to communicate with a single pvserver node (multiple pvserver processes though). If you only want to connect the simulation+Catalyst to the GUI client or pvserver processes on a single node then 5.2 should work fine for you.Best,Andy ?On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon wrote: Hi,?for a University Project we?re trying to run Paraview Live Simulation on the local cluster-network. Unfortunately the network only has a Paraview version without python-binding installed, therefore we would like to run the LiveSimulation with a C++-coded Pipeline Skript.?As far as we understood, to make it work we have to rewrite the following lines from the PythonPipeline Script to C++, which turns out to be quite challenging:?coprocessor.UpdateProducers( datadescription)# Write output data, if appropriate.coprocessor.WriteData( datadescription);# Live Visualization, if enabled.coprocessor. DoLiveVisualization( datadescription, "localhost", 22222)?We tried the following:?//INITIALIZEvtkNew link;vtkSMProxyManager* proxyManager;vtkSMSessionProxyManager* sessionProxyManager;link -> SetInsituPort(22222);link -> SetHostname("localhost");proxyManager = vtkSMProxyManager:: GetProxyManager();sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ;link -> Initialize( sessionProxyManager);?// Initialize returns 1, therefore connection established properly?//Then we tried to coprocess with the following code:vtkNew writer;writer->SetInputConnection( producer->GetOutputPort());vtkSMProxy* proxy = sessionProxyManager->NewProxy( "insitu_writer_parameters"," XMLPImageDataWriter");vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> GetProperty("Input");?//set input of proxy to our writer or datadescription ? DOESN?T WORKwhile(true){? link->InsituUpdate( dataDescription->GetTime(), dataDescription->GetTimeStep() );? //update pipeline? link->InsituPostProcess( dataDescription->GetTime(), dataDescription->GetTimeStep() );? if(link->GetSimulationPaused() ){??? if(link->WaitForLiveChange()){?????break;??? }? } else{??? break;}? }?So how are we supposed to get the data from our simulation into the Proxy?We have been trying and searching the documentation for the right functions, but we can?t figure out how to do it.?We would really appreciate some help ;-)?Best regards,Simon Kohlhase ______________________________ _________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/ opensource/opensource.html Please keep messages on-topic and check the ParaView 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 michel.rasquin at colorado.edu Fri Feb 3 05:57:30 2017 From: michel.rasquin at colorado.edu (Michel Rasquin) Date: Fri, 3 Feb 2017 10:57:30 +0000 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support Message-ID: Hi everyone, I have built ParaViewSuperBuild 5.2 twice on our Linux supercomputer 1) with OSMesa support for CPU compute nodes and 2) with NVDIA OpenGL support for our GPU visualization nodes. The pvserver with NVDIA OpenGL support works fine (I can connect a client and load data successfully). However, it starts to become tricky when I use pvserver with OSMesa support. It appears the resulting pvserver with OSMesa support compiled in Release mode always crashes when I try to load data, The cmake command include in this case the usual options -DCMAKE_BUILD_TYPE_paraview=Release \ -DCMAKE_BUILD_TYPE=Release \ BUT it works well when it is compiled in Debug mode with the following cmake options: -DSUPERBUILD_ALLOW_DEBUG:BOOL=ON \ -DCMAKE_BUILD_TYPE_paraview=Debug \ -DCMAKE_BUILD_TYPE=Debug \ Since pvserver compiled with NVIDIA OpenGL support works fine in Release mode but not pvserver with OSMesa in Release mode, the issue points to OSMesa for now. The pvserver with OSMesa support outputs the following information about my GL and Mesa version when I connect the client: GL_Version: 3.3 (Core Profile) Mesa 13.0.3 Please note also that I am able to run successfully PVSB 5.0.1 with OSMesa support compiled in Release mode. Thank you for your help. Best regards, Michel From emrahersanerdogan at gmail.com Fri Feb 3 07:37:11 2017 From: emrahersanerdogan at gmail.com (Emrah Ersan Erdogan) Date: Fri, 3 Feb 2017 13:37:11 +0100 Subject: [Paraview] First trial file does not work-help! In-Reply-To: <8AA87C27-EE38-446E-80C4-84E18EA6DCF4@sandia.gov> References: <8AA87C27-EE38-446E-80C4-84E18EA6DCF4@sandia.gov> Message-ID: <37CAE98B-42EA-4125-853B-A0BF0AC01B1F@gmail.com> You are a life-saver, literally. That would not have occurred to me for a long time believe me. As a final step, in the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. The problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. And second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? Thank you a lot again. I think this will conclude my problem entirely. Ersan 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 0 1 2 3 4 9 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 2.0 3.0 0.0 3.0 2.0 0.0 0.0 0.0 0.0 1.0 2.0 0.0 2.0 1.0 0.0 0.0 0.0 0.0 5.0 4.0 0.0 4.0 1.0 0.0 0.0 0.0 0.0 3.0 6.0 0.0 6.0 7.0 0.0 0.0 0.0 0.0 > On 3 Feb 2017, at 01:24, Moreland, Kenneth wrote: > > Did you type this in a text editor? The first thing I notice is that many of the quotes are the fancy open/close characters. Many text editors use a ?smart quotes? feature that replaces the straight quote to a bent open or closed quote. The VTK reader only accepts the straight quotes (ASCII character 34). > > -Ken > > > On 2/2/17, 5:58 PM, "ParaView on behalf of Emrah Ersan Erdogan" wrote: > > Hi, > > I am a new user of paraview and try to understand .vtu file format. > Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. > > However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. > > Thanks a bunch! > > Ersan > > > > > > 2.0 2.0 3.0 1.0 > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From emrahersanerdogan at gmail.com Fri Feb 3 07:43:13 2017 From: emrahersanerdogan at gmail.com (Emrah Ersan Erdogan) Date: Fri, 3 Feb 2017 13:43:13 +0100 Subject: [Paraview] Simple problem with point data and geometry definition Message-ID: Hi, I have two small problems and since I am just a newbie I really appreciate any help. In the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. First problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. Second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? Thanks a bunch! Ersan 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 0 1 2 3 4 9 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 2.0 3.0 0.0 3.0 2.0 0.0 0.0 0.0 0.0 1.0 2.0 0.0 2.0 1.0 0.0 0.0 0.0 0.0 5.0 4.0 0.0 4.0 1.0 0.0 0.0 0.0 0.0 3.0 6.0 0.0 6.0 7.0 0.0 0.0 0.0 0.0 From andy.bauer at kitware.com Fri Feb 3 09:39:10 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 3 Feb 2017 09:39:10 -0500 Subject: [Paraview] Paraview Live Visualisation C++ Pipeline In-Reply-To: <1274303005.358629.1486119293917@mail.yahoo.com> References: <2096947504.1712063.1486032411095@mail.yahoo.com> <613524816.2096230.1486048320776@mail.yahoo.com> <1274303005.358629.1486119293917@mail.yahoo.com> Message-ID: I should only need one that demonstrates the problem. On Fri, Feb 3, 2017 at 5:54 AM, sinan shabib wrote: > Hi Andy, > > Could you please tell me, which data set you need ? > Because it?s big data. > I?m doing (Ensight 6) format. > > Greetings. > > > Andy Bauer schrieb am 17:42 Donnerstag, > 2.Februar 2017: > > > Hi, > > Can you share a data set that you are having an issue with? > > On Thu, Feb 2, 2017 at 10:12 AM, sinan shabib > wrote: > > Hi, > > I apologize,I didn?t explain it well. > > I?m using: *Paraview 5.2.0-RC1 , 64 bit.* > > All fields data are being read but not visualized, that is, I get only one > color when I color the data with a specific field. > However, when I use "find data" function, I can see the data. > This happens only with: velocity & pressure. > I?m working on several configurations & the same thing happens with all of > them. > > Is it a bug or VTK has been corrupted or something else ? > > Thanks in advance. > > > > > > Andy Bauer schrieb am 16:00 Donnerstag, > 2.Februar 2017: > > > Maybe I didn't understand what you were trying to do. Can you be a bit > more specific? > > On Thu, Feb 2, 2017 at 5:46 AM, sinan shabib > wrote: > > Hi Andy, > > Thanks for your reply. > > I think you've mixed my question up with someone else?s. > I still have the problem with data-visualization (data are read but not > visualized). > > > > Andy Bauer schrieb am 19:02 Dienstag, 31.Januar > 2017: > > > Hi, > > Please keep the discussion on the mailing list so that anyone can > participate (also, stuff gets lost in my Inbox too). > > The ParaView Catalyst Users Guide at http://www.paraview.org/files/ > catalyst/docs/ ParaViewCatalystUsersGuide_v2. pdf > > has information on how to use the Live functionality. It's in Section 2.3. > > Best, > Andy > > On Thu, Jan 26, 2017 at 12:29 PM, Kohlhase, Simon > wrote: > > Hi, > > thanks a lot for the quick respons. > At least now we know that there?s no point to keep on trying. > > I?ll try to build and install it myself then. > > Is there any previous thread where I can find out more about the > simulation + catalyst linking to a parallel server? > > Best regards, > Simon > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com ] > *Sent:* Donnerstag, 26. Januar 2017 16:22 > *To:* Kohlhase, Simon > *Cc:* paraview at paraview.org; felix.hennerkes at gmail.com; Damerow, David < > david.damerow at tum.de> > *Subject:* Re: [Paraview] Paraview Live Visualisation C++ Pipeline > > Hi, > Currently the Live functionality only works when ParaView is built with > Python bindings. My suggestion would be to build ParaView yourself. That > should be much easier than trying to put in a C++ pipeline that can deal > with the Live functionality properly. > As for building ParaView, you may want to look into using the ParaView > Superbuild (https://gitlab.kitware.com/ paraview/paraview-superbuild/ > ) which will > also build all needed dependencies. The dependencies are probably all there > though since you've said that ParaView is already installed there. > I'm not sure the set up you're looking for but if you want to run with the > simulation+Catalyst linking to a parallel pvserver on the cluster which > then connects to a client, you may want to use ParaView master. The reason > for this is that there was a bug that had all of the simulation+Catalyst > nodes only being able to communicate with a single pvserver node (multiple > pvserver processes though). If you only want to connect the > simulation+Catalyst to the GUI client or pvserver processes on a single > node then 5.2 should work fine for you. > Best, > Andy > > On Thu, Jan 26, 2017 at 9:53 AM, Kohlhase, Simon > wrote: > > Hi, > > for a University Project we?re trying to run Paraview Live Simulation on > the local cluster-network. Unfortunately the network only has a Paraview > version without python-binding installed, therefore we would like to run > the LiveSimulation with a C++-coded Pipeline Skript. > > As far as we understood, to make it work we have to rewrite the following > lines from the PythonPipeline Script to C++, which turns out to be quite > challenging: > > coprocessor.UpdateProducers( datadescription) > # Write output data, if appropriate. > coprocessor.WriteData( datadescription); > # Live Visualization, if enabled. > coprocessor. DoLiveVisualization( datadescription, "localhost", 22222) > > We tried the following: > > //INITIALIZE > vtkNew link; > vtkSMProxyManager* proxyManager; > vtkSMSessionProxyManager* sessionProxyManager; > link -> SetInsituPort(22222); > link -> SetHostname("localhost"); > proxyManager = vtkSMProxyManager:: GetProxyManager(); > sessionProxyManager = proxyManager-> GetActiveSessionProxyManager() ; > link -> Initialize( sessionProxyManager); > > // Initialize returns 1, therefore connection established properly > > //Then we tried to coprocess with the following code: > vtkNew writer; > writer->SetInputConnection( producer->GetOutputPort()); > vtkSMProxy* proxy = sessionProxyManager->NewProxy( > "insitu_writer_parameters"," XMLPImageDataWriter"); > vtkSMInputProperty* property = (vtkSMInputProperty*) proxy -> > GetProperty("Input"); > > //set input of proxy to our writer or datadescription ? DOESN?T WORK > while(true){ > link->InsituUpdate( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > //update pipeline > link->InsituPostProcess( dataDescription->GetTime(), > dataDescription->GetTimeStep() ); > if(link->GetSimulationPaused() ){ > if(link->WaitForLiveChange()){ > break; > } > } else{ > break; > } > } > > So how are we supposed to get the data from our simulation into the Proxy? > We have been trying and searching the documentation for the right > functions, but we can?t figure out how to do it. > > We would really appreciate some help ;-) > > Best regards, > Simon Kohlhase > > ______________________________ _________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 sebastien.jourdain at kitware.com Fri Feb 3 10:10:58 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Fri, 3 Feb 2017 08:10:58 -0700 Subject: [Paraview] "Rotate" look up table In-Reply-To: References: Message-ID: Hi Nicolas, You can create a programmable filter that will alter the scalars based on a "fake" time. I've attached an example on how to create a time based filter. Good luck, Seb PS: I'm not sure, the latest ParaView allow programable filter to be time aware. If not, I've also attached an XML (plugin) that you can load and use for that filter. On Fri, Feb 3, 2017 at 1:47 AM, Nicolas Cedilnik wrote: > Hi all, > > I'm replying to my own email because I worked out a solution and wanted to > share but also because I believe what I'm doing is FAR from optimal and > hope that someone > >> Would it be possible with python scripting to create an animation by >> "rotating" the look up table in a way that would look like this: >> https://www.youtube.com/watch?v=qA_vInXwdKM#t=3m25s ? It is a >> pseudo-animation created by changing the "range" of the LUT. >> > So I made this python script (see attachment) that generates different > meshes with scalar values "rotated" (I don't find a better term to describe > what I'm doing). > It works and make it easy to play the animation by opening the produced > vtk files as a sequence in paraview. > > However, every vtk file contains both the mesh geometry and the scalar > values, but only the latter change. What would be the right way to animate > only the scalar values and not the mesh geometry? What data format should I > use? How could I import it into an animation in paraview? > > Thanks for your guidance > > -- > Nicolas > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 -------------- # ============================================================================= # Request Data # ============================================================================= import vtk executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) req_timestep = outInfo.Get(executive.UPDATE_TIME_STEP()) print req_timestep input = self.GetPolyDataInput() inputCells = input.GetPolys() newCells = vtk.vtkCellArray() # Keep cells in range nbCells = inputCells.GetNumberOfCells() allowedIds = range(int(req_timestep) * (nbCells / 5), (int(req_timestep) + 1) * (nbCells / 5)) cellLocation = 0 ids = vtk.vtkIdList() for cellIdx in range(nbCells): inputCells.GetCell(cellLocation, ids) cellSize = ids.GetNumberOfIds() if cellIdx in allowedIds: newCells.InsertNextCell(ids) cellLocation += cellSize + 1 self.GetPolyDataOutput().ShallowCopy(input) self.GetPolyDataOutput().SetPolys(newCells) # ============================================================================= # Request Informations # ============================================================================= timesteps = range(5) executive = self.GetExecutive() outInfo = executive.GetOutputInformation(0) outInfo.Remove(executive.TIME_STEPS()) for timestep in timesteps: outInfo.Append(executive.TIME_STEPS(), timestep) outInfo.Remove(executive.TIME_RANGE()) outInfo.Append(executive.TIME_RANGE(), timesteps[0]) outInfo.Append(executive.TIME_RANGE(), timesteps[-1]) -------------- next part -------------- A non-text attachment was scrubbed... Name: TemporalPythonProxy.xml Type: text/xml Size: 1023 bytes Desc: not available URL: From cory.quammen at kitware.com Fri Feb 3 11:29:00 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 3 Feb 2017 11:29:00 -0500 Subject: [Paraview] Save Programmable VTKImageData as PNG images In-Reply-To: References: Message-ID: I was able to reproduce the problem you are seeing. That is odd. Would you mind opening an issue on the bug tracker? https://gitlab.kitware.com/paraview/paraview/issues Thanks, Cory On Fri, Feb 3, 2017 at 12:53 AM, Magician wrote: > Hi all, > > > I have some 2D VTKImageData and export them as PNG images using 'Save Data...'. > > I'm trying to get color values from original sources and convert them > to 8 or 16-bit color values with Programmable Filter. > But if I apply 'Save Data...' to the results, no PNG images exported > and get warnings as below: > >> Warning: In /Users/kitware/buildbot-slave/b99e1795/source-paraview/VTK/IO/Image/vtkPNGWriter.cxx, line 231 >> vtkPNGWriter (0x6000005a8260): PNGWriter only supports unsigned char and unsigned short inputs > > The attached dataset is a tiny sample. (including no dtype converter, but reproduces same problems) > The data type of the PNGImage value of ProgrammableFilter1 should be 'unsigned char', > but we may not be able to save it as a PNG image. > > Is it a bug? > > > Magician > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 fabidi89 at vt.edu Fri Feb 3 12:13:16 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Fri, 3 Feb 2017 12:13:16 -0500 Subject: [Paraview] [EXTERNAL] Re: [Paraview-developers] Scripting image compression parameters In-Reply-To: References: Message-ID: Hi Alan, Sorry for a delayed response, but I missed this email somehow. So, I actually have tried the trace function ParaView supports, but unfortunately, it doesn't trace the settings I set for the image compression settings. I guess I'll have to do it manually then, but I would be interested to know if anyone else has tried to script the compression parameters. I am kind of surprised if this is not possible to script. Best, On Mon, Jan 30, 2017 at 4:55 PM, Scott, W Alan wrote: > My best guess would be to try to trace the save screenshot functionality, > and see what is set. Sorry, that?s the best I have... > > > > Alan > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *Faiz Abidi > *Sent:* Monday, January 30, 2017 2:14 PM > *To:* paraview-developers at paraview.org; paraview at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Scripting image > compression parameters > > > > Not having heard back from anyone, I am guessing no one has done this kind > of scripting before? Anyone? > > > > On Wed, Jan 25, 2017 at 9:43 AM, Faiz Abidi wrote: > > Hello ParaView community, > > > > ParaView provides various image compression configuration options > . I > was wondering how to go about scripting this so that I can test setting > various parameters in a script. > > > > I did check some of ParaView modules but couldn't find anything helpful. > > > > Any pointers from anyone would be helpful. > > > > Best, > -- > > 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 Fri Feb 3 12:57:11 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 3 Feb 2017 17:57:11 +0000 Subject: [Paraview] First trial file does not work-help! Message-ID: Trust me, you are not the first person to be burned by smart quotes. (Viva la vim?) I suggest putting each piece in its own vtu file and then create a vtm file that points to the two of them. Here is a simple example of the contents of a vtm file: -Ken On 2/3/17, 6:37 AM, "Emrah Ersan Erdogan" wrote: You are a life-saver, literally. That would not have occurred to me for a long time believe me. As a final step, in the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. The problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. And second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? Thank you a lot again. I think this will conclude my problem entirely. Ersan 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 0 1 2 3 4 9 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 2.0 3.0 0.0 3.0 2.0 0.0 0.0 0.0 0.0 1.0 2.0 0.0 2.0 1.0 0.0 0.0 0.0 0.0 5.0 4.0 0.0 4.0 1.0 0.0 0.0 0.0 0.0 3.0 6.0 0.0 6.0 7.0 0.0 0.0 0.0 0.0 > On 3 Feb 2017, at 01:24, Moreland, Kenneth wrote: > > Did you type this in a text editor? The first thing I notice is that many of the quotes are the fancy open/close characters. Many text editors use a ?smart quotes? feature that replaces the straight quote to a bent open or closed quote. The VTK reader only accepts the straight quotes (ASCII character 34). > > -Ken > > > On 2/2/17, 5:58 PM, "ParaView on behalf of Emrah Ersan Erdogan" wrote: > > Hi, > > I am a new user of paraview and try to understand .vtu file format. > Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. > > However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. > > Thanks a bunch! > > Ersan > > > > > > 2.0 2.0 3.0 1.0 > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From emrahersanerdogan at gmail.com Fri Feb 3 17:02:07 2017 From: emrahersanerdogan at gmail.com (Emrah Ersan Erdogan) Date: Fri, 3 Feb 2017 23:02:07 +0100 Subject: [Paraview] First trial file does not work-help! In-Reply-To: References: Message-ID: Thanks, that works very well. Since I just learn at the moment I prefer to work on text editor. I guess when I integrate it to my FE solver in c++, it will be ok from now on. The only thing is that I think it is not possible to make one show the outline (geometry) and the other gaussian points at the same time in paraview. Do you know any way to do it? Because otherwise I will be forced to work on separate files unfortunately. Best Ersan > On 3 Feb 2017, at 18:57, Moreland, Kenneth wrote: > > Trust me, you are not the first person to be burned by smart quotes. (Viva la vim?) > > I suggest putting each piece in its own vtu file and then create a vtm file that points to the two of them. Here is a simple example of the contents of a vtm file: > > > > > > > > > > > > -Ken > > > On 2/3/17, 6:37 AM, "Emrah Ersan Erdogan" wrote: > > You are a life-saver, literally. That would not have occurred to me for a long time believe me. > > As a final step, in the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. > The problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. > And second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? > > Thank you a lot again. I think this will conclude my problem entirely. > > Ersan > > > > > > > > 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 > > > > > 0 1 2 3 > > > 4 > > > 9 > > > > > > > > > > > 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 > > > > > > > > > > > > > 2.0 3.0 0.0 > 3.0 2.0 0.0 > 0.0 0.0 0.0 > > 1.0 2.0 0.0 > 2.0 1.0 0.0 > 0.0 0.0 0.0 > > 5.0 4.0 0.0 > 4.0 1.0 0.0 > 0.0 0.0 0.0 > > 3.0 6.0 0.0 > 6.0 7.0 0.0 > 0.0 0.0 0.0 > > > > > > > > >> On 3 Feb 2017, at 01:24, Moreland, Kenneth wrote: >> >> Did you type this in a text editor? The first thing I notice is that many of the quotes are the fancy open/close characters. Many text editors use a ?smart quotes? feature that replaces the straight quote to a bent open or closed quote. The VTK reader only accepts the straight quotes (ASCII character 34). >> >> -Ken >> >> >> On 2/2/17, 5:58 PM, "ParaView on behalf of Emrah Ersan Erdogan" wrote: >> >> Hi, >> >> I am a new user of paraview and try to understand .vtu file format. >> Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. >> >> However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. >> >> Thanks a bunch! >> >> Ersan >> >> >> >> >> >> 2.0 2.0 3.0 1.0 >> >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > From f_magician at mac.com Sat Feb 4 10:50:32 2017 From: f_magician at mac.com (Magician) Date: Sun, 05 Feb 2017 00:50:32 +0900 Subject: [Paraview] Save Programmable VTKImageData as PNG images In-Reply-To: References: Message-ID: <9A0B583C-8B1E-4BEC-ABD1-C704490B1B0D@mac.com> Hi Cory, Thanks to your advice. I posted the issue. > Magician > On Feb 4, 2017, at 01:29, Cory Quammen wrote: > > I was able to reproduce the problem you are seeing. That is odd. > > Would you mind opening an issue on the bug tracker? > https://gitlab.kitware.com/paraview/paraview/issues > > Thanks, > Cory > > On Fri, Feb 3, 2017 at 12:53 AM, Magician wrote: >> Hi all, >> >> >> I have some 2D VTKImageData and export them as PNG images using 'Save Data...'. >> >> I'm trying to get color values from original sources and convert them >> to 8 or 16-bit color values with Programmable Filter. >> But if I apply 'Save Data...' to the results, no PNG images exported >> and get warnings as below: >> >>> Warning: In /Users/kitware/buildbot-slave/b99e1795/source-paraview/VTK/IO/Image/vtkPNGWriter.cxx, line 231 >>> vtkPNGWriter (0x6000005a8260): PNGWriter only supports unsigned char and unsigned short inputs >> >> The attached dataset is a tiny sample. (including no dtype converter, but reproduces same problems) >> The data type of the PNGImage value of ProgrammableFilter1 should be 'unsigned char', >> but we may not be able to save it as a PNG image. >> >> Is it a bug? >> >> >> Magician >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> 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 samuelkey at bresnan.net Sun Feb 5 13:32:32 2017 From: samuelkey at bresnan.net (Samuel Key) Date: Sun, 5 Feb 2017 11:32:32 -0700 Subject: [Paraview] Generate IDs In-Reply-To: References: Message-ID: <372d3276-2e63-04d9-74f2-3a6dc50142f2@bresnan.net> Daniel, I am not sure this a solution you will want? I have unstructured meshes that have several (1 to 38) material domains. I use the EnSight gold binary format for my results. This format has a Part-construct. When writing out simulation results, each material domain becomes a distinct Part (distinct displayable graphics object). PV's Extract Block filter allows me to select and display any combination of "Parts." From there, I am pretty sure you can execute the steps you want. Regards, Samuel Key, FMA Development On 1/31/2017 12:20 AM, Daniel Frisch wrote: > Hello, I want to > > - open an unstructured grid, > - view a sub-volume using the Threshold filter that selects a certain > material > - apply some Clip filters to remove unwanted parts > - select everything I am seeing now > - and create an "Extract Selection" filter that can be used for other > vtk files containing the same unstructured grid but other data arrays. > > But the "GenerateIDs" filter removes the material array from the > dataset so I can't apply the Threshold filter anymore. I see the > "Extract Selection" works only with the current IDs anyway that are > different from the original cell IDs due to the Clip filters. > > How can I have a filter that extracts a certain set of cells that I > define and apply it to other .vtk files? > Thank you very much in advance, > Daniel > > > _______________________________________________ > Powered bywww.kitware.com > > Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView > > 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 chuck.atkins at kitware.com Mon Feb 6 11:06:35 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 6 Feb 2017 11:06:35 -0500 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support In-Reply-To: References: Message-ID: Hi Michel, However, it starts to become tricky when I use pvserver with OSMesa support. > It appears the resulting pvserver with OSMesa support compiled in Release > mode always crashes when I try to load data, > Which compiler are you building with and type of CPUs are available on the node you're running on? There is a known issue with llvmpipe and the Intel compiler causing segfaults. If youre CPU is new enough (supports AVX) then you can use the swr driver. See http://www.paraview.org/Wiki/ParaView_And_Mesa_3D#Using_the_llvmpipe_and_swr_drivers for details on switching between llvmpipe and swr drivers and adjusting the number of threads used by each one. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Mon Feb 6 12:18:04 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Mon, 6 Feb 2017 20:18:04 +0300 Subject: [Paraview] Collapse tree view after new child added Message-ID: Hello, Is it possible to collapse tree view after new child(filter) was added? We tried to change the behaviour in pqPipelineBrowserWidget but when the line 124 : QObject::connect(this->PipelineModel, SIGNAL(firstChildAdded(const QModelIndex&)), this,SLOT(expandWithModelIndexTranslation(const QModelIndex&))); was commented Paraview crashed all time. Best Regards, Rustem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Tue Feb 7 07:14:36 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 7 Feb 2017 12:14:36 +0000 Subject: [Paraview] Pipeline update with Catalyst Message-ID: Hello again, I am working on a pipeline using Catalyst that writes data only when features are detected. The idea is to have a 3D contour generated in the pipeline, and when it is big enough, start recording data. There is a long lead-up to when the features appear, and then they disappear rapidly, so I would like to only collect data when the features are present. To that end, my DoCoProcessing() function has something that checks the 'Area' value in the CellData of an IntegrateVariables filter. The full function is below. However, this doesn't ever write any images or data. It also doesn't throw any errors, so I have a feeling the pipeline isn't actually evaluated/updated after the call to UpdateProducers. So, my question -- at what point in the DoCoProcessing function is the pipeline actually evaluated? Do all the filters execute when the UpdatedProducers function is called? Or do they only update when the outputs to which they are connected are called, ie. WriteData and WriteImages? Thanks, Tim def DoCoProcessing(datadescription): "Callback to do co-processing for current timestep" global coprocessor global lastTime global deltaT # Update the coprocessor by providing it the newly generated simulation data. # If the pipeline hasn't been setup yet, this will setup the pipeline. coprocessor.UpdateProducers(datadescription) curTime = datadescription.GetTime() if curTime >= lastTime + deltaT: lastTime = curTime if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: # Write output data, if appropriate. coprocessor.WriteData(datadescription); # Write image capture (Last arg: rescale lookup table), if appropriate. coprocessor.WriteImages(datadescription, rescale_lookuptable=False) # Live Visualization, if enabled. coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Feb 7 07:44:31 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Feb 2017 07:44:31 -0500 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: Message-ID: Hi Tim, The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() before checking for the area. You also may need to use MPI to do the global sum or broadcast of the value since I think that value will either just have local values or maybe just the proper global value on processor 0. You should have access to mpi4py in the Python script in order to do that. The long answer is that ParaView & VTK use a demand-driven pipeline design meaning that until something explicitly tells a pipeline to update it won't. For the Catalyst scripts this is done in the coprocessor.WriteData(), coprocessor.WriteImages() and coprocessor.DoLiveVisualization() calls for each output that is required (e.g. for a writer that is supposed to output at that time step but not for other writers that are not supposed to output at that time step). You can manually force a filter to update by using the UpdatePipeline() method which will update that pipeline along with everything it depends on. It won't update any filters though that don't have an effect on it computing its requested information which means that for the flameArea filter it won't affect any writers or image output stuff which is what you want. There is some information on Catayst script details at https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ but I don't think that contains this information. Cheers, Andy On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Hello again, > > > I am working on a pipeline using Catalyst that writes data only when > features are detected. The idea is to have a 3D contour generated in the > pipeline, and when it is big enough, start recording data. There is a long > lead-up to when the features appear, and then they disappear rapidly, so I > would like to only collect data when the features are present. > > > To that end, my DoCoProcessing() function has something that checks the > 'Area' value in the CellData of an IntegrateVariables filter. The full > function is below. However, this doesn't ever write any images or data. It > also doesn't throw any errors, so I have a feeling the pipeline isn't > actually evaluated/updated after the call to UpdateProducers. > > > So, my question -- at what point in the DoCoProcessing function is the > pipeline actually evaluated? Do all the filters execute when the > UpdatedProducers function is called? Or do they only update when the > outputs to which they are connected are called, ie. WriteData and > WriteImages? > > > Thanks, > > > Tim > > > def DoCoProcessing(datadescription): > "Callback to do co-processing for current timestep" > global coprocessor > global lastTime > global deltaT > > # Update the coprocessor by providing it the newly generated > simulation data. > > > # If the pipeline hasn't been setup yet, this will setup the > pipeline. > > > coprocessor.UpdateProducers(datadescription) > > curTime = datadescription.GetTime() > > if curTime >= lastTime + deltaT: > lastTime = curTime > > if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: > # Write output data, if appropriate. > > > > coprocessor.WriteData(datadescription); > > # Write image capture (Last arg: rescale lookup table), if > appropriate. > > > coprocessor.WriteImages(datadescription, > rescale_lookuptable=False) > > # Live Visualization, if enabled. > > > > coprocessor.DoLiveVisualization(datadescription, "localhost", > 22222) > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 tim.gallagher at gatech.edu Tue Feb 7 07:51:12 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 7 Feb 2017 12:51:12 +0000 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: , Message-ID: Thanks Andy, I had a feeling the pipeline had to be manually updated. I thought maybe the UpdateProducers also updated the pipeline. Thanks for clarifying that. I also have the same concern about the value stored in each block's CellData field. I couldn't find any documentation that indicates how the IntegrateVariables filter distributes the data. But, looking at the block VTK files that are written out, they all contain the same value of Area so I think a global reduction is done in the filter and all blocks have the total values. I could be wrong though. Thanks again, Tim ________________________________ From: Andy Bauer Sent: Tuesday, February 7, 2017 7:44 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst Hi Tim, The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() before checking for the area. You also may need to use MPI to do the global sum or broadcast of the value since I think that value will either just have local values or maybe just the proper global value on processor 0. You should have access to mpi4py in the Python script in order to do that. The long answer is that ParaView & VTK use a demand-driven pipeline design meaning that until something explicitly tells a pipeline to update it won't. For the Catalyst scripts this is done in the coprocessor.WriteData(), coprocessor.WriteImages() and coprocessor.DoLiveVisualization() calls for each output that is required (e.g. for a writer that is supposed to output at that time step but not for other writers that are not supposed to output at that time step). You can manually force a filter to update by using the UpdatePipeline() method which will update that pipeline along with everything it depends on. It won't update any filters though that don't have an effect on it computing its requested information which means that for the flameArea filter it won't affect any writers or image output stuff which is what you want. There is some information on Catayst script details at https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ but I don't think that contains this information. [https://blog.kitware.com/source/files/Small.4_447936566.jpg] Anatomy of a ParaView Catalyst Python Script | The Kitware ... blog.kitware.com Introduction. ParaView Catalyst has yielded some amazing results. Such results include iso-surfacing and generating images with 256K Message Passing Interface (MPI ... Cheers, Andy On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P > wrote: Hello again, I am working on a pipeline using Catalyst that writes data only when features are detected. The idea is to have a 3D contour generated in the pipeline, and when it is big enough, start recording data. There is a long lead-up to when the features appear, and then they disappear rapidly, so I would like to only collect data when the features are present. To that end, my DoCoProcessing() function has something that checks the 'Area' value in the CellData of an IntegrateVariables filter. The full function is below. However, this doesn't ever write any images or data. It also doesn't throw any errors, so I have a feeling the pipeline isn't actually evaluated/updated after the call to UpdateProducers. So, my question -- at what point in the DoCoProcessing function is the pipeline actually evaluated? Do all the filters execute when the UpdatedProducers function is called? Or do they only update when the outputs to which they are connected are called, ie. WriteData and WriteImages? Thanks, Tim def DoCoProcessing(datadescription): "Callback to do co-processing for current timestep" global coprocessor global lastTime global deltaT # Update the coprocessor by providing it the newly generated simulation data. # If the pipeline hasn't been setup yet, this will setup the pipeline. coprocessor.UpdateProducers(datadescription) curTime = datadescription.GetTime() if curTime >= lastTime + deltaT: lastTime = curTime if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: # Write output data, if appropriate. coprocessor.WriteData(datadescription); # Write image capture (Last arg: rescale lookup table), if appropriate. coprocessor.WriteImages(datadescription, rescale_lookuptable=False) # Live Visualization, if enabled. coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 reuben.kraft at gmail.com Tue Feb 7 08:22:39 2017 From: reuben.kraft at gmail.com (Reuben Kraft) Date: Tue, 7 Feb 2017 08:22:39 -0500 Subject: [Paraview] XML tag for naming tensor components Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Feb 7 08:32:20 2017 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 7 Feb 2017 08:32:20 -0500 Subject: [Paraview] Rendering Backend OpenGL2 & PV 5.2.0-RC4 & SurfaceLic --> Problem... In-Reply-To: References: <84a5a6aa-326f-a1ff-7789-28204a0ee502@DLR.de> Message-ID: Thanks Andy, just to make sure I understand the issue. Is the case that one processor has no data, or is it that it has data, but it is outside the current view? Thanks Ken On Thu, Feb 2, 2017 at 5:14 PM, Andy Smith wrote: > I've tested this with the latest ParaView and it does seem to run much > faster. > I am having a problem when running in parallel though. If one processor > does not have anything to display, the rendering hangs. > Related to that, what routine actually calls vtkCompositeLICHelper:: > RenderPiece? > The process that does not have anything to display never gets to that > function but the other processes do. In that function there are MPI calls > where the rendering hangs. > > As a reply to Chuck: I can use EGL in some instances but unfortunately > not all of our machine have GPUs so software rendering is still required. > > Thanks again for all the help. > > On Mon, Jan 23, 2017 at 12:45 PM, Ken Martin > wrote: > >> There is a VTK topic now that should fix this regression. With this >> change OpenGL2 LIC seems to run much faster (at least 10X). >> >> https://gitlab.kitware.com/vtk/vtk/merge_requests/2419 >> >> Hopefully it will test out OK and get merged into VTK and then merged >> into ParaView. >> >> On Mon, Dec 12, 2016 at 11:38 AM, Andy Smith >> wrote: >> >>> Ken, >>> >>> You are correct in your assumption about my dataset; it is multiblock >>> unstructured data. Adding a MergeBlocks filter to my slice does improve >>> the 5.2.0 with OpenGL2 significantly. >>> With that change the performance of 5.2.0 with OpenGL2 is on the same >>> order of magnitude as 5.2.0 with OpenGL and with 4.4.0, though the 5.2.0 >>> variants are still slower than 4.4.0. >>> >>> I realized after posting that my comparison is not exactly apples to >>> apples - my build of 5.2.0 required updates to mesa (13.0.0) compared with >>> the version I used for 4.4.0 (11.2.0). >>> I will recompile 4.4.0 with the same mesa version I used with 5.2.0 and >>> report back. >>> >>> Thank you for your input. >>> >>> -Andy >>> >>> On Fri, Dec 9, 2016 at 3:44 PM, Ken Martin >>> wrote: >>> >>>> I have not had time to look into this, but my quick guess is that you >>>> have a multiblock dataset with a lot of blocks. Can you try merging the >>>> blocks all together somehow into one block and see if the rendering speed >>>> improves? >>>> >>>> On Tue, Nov 15, 2016 at 5:35 AM, Stefan Melber >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> i have a problem which is there in all RCs (1-4) of current ParaView: >>>>> if i compile the RenderingBackend to "OpenGL2" and use SurfaceLic the >>>>> visualization time goes up from a few seconds (with "OpenGL") to many >>>>> minutes and the memory consumption from a few GByte to approx 100 GByte. >>>>> Switching back to OpenGL any thing is fine. Without SurfaceLIC the OpenGL2 >>>>> works although fine for me. >>>>> >>>>> Has any one tested OpenGL2 with SurfaceLIC-Plugin the last time and >>>>> has (the same) problems? >>>>> >>>>> o Kernel 4.7.6-1 / x86-64 >>>>> o Quadro 4000 >>>>> o NVidia driver v367.57 >>>>> o PV 5.2.0 RC1 - RC4 >>>>> >>>>> Best regards, >>>>> >>>>> Stefan >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>>> >>> >> >> >> -- >> 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. >> > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Feb 7 10:05:14 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Feb 2017 10:05:14 -0500 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: Message-ID: The pipeline is update mechanism is often called a lazy update scheme meaning only do the requested work and no more. If the UpdateProducers() method automatically updated all of the filters there would be a lot of unneeded work that would be done. Think about a Catalyst script that branched into 3 separate outputs with a lot of work done in each branch. If only one output was wanted during a time step that could potentially be a lot of extra, unneeded work. As for parallel communication in Catalyst, again it's an efficiency thing meaning that if we can avoid communication we may as well do it. In interactive mode (i.e. through the GUI) it's useful to know things like the total number of points and cells, bounds and field ranges which requires communication. In Catalyst this information isn't usually needed so that's the type of information that would need to be globally communicated. For filters like the Integrate Attributes filter, you should get the same behavior in the GUI as in Catalyst with regard to parallel output since the filter itself does not know how ParaView is running. Some filters (e.g. Resample with Dataset) though only have non-empty results on process 0 so it is definitely safest to check filters like Integrate Attributes in parallel. Cheers, Andy On Tue, Feb 7, 2017 at 7:51 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Thanks Andy, > > > I had a feeling the pipeline had to be manually updated. I thought maybe > the UpdateProducers also updated the pipeline. Thanks for clarifying that. > > > I also have the same concern about the value stored in each block's > CellData field. I couldn't find any documentation that indicates how the > IntegrateVariables filter distributes the data. But, looking at the block > VTK files that are written out, they all contain the same value of Area so > I think a global reduction is done in the filter and all blocks have the > total values. I could be wrong though. > > > Thanks again, > > > Tim > > > ------------------------------ > *From:* Andy Bauer > *Sent:* Tuesday, February 7, 2017 7:44 AM > *To:* Gallagher, Timothy P > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Pipeline update with Catalyst > > Hi Tim, > > The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() > before checking for the area. You also may need to use MPI to do the global > sum or broadcast of the value since I think that value will either just > have local values or maybe just the proper global value on processor 0. You > should have access to mpi4py in the Python script in order to do that. > > The long answer is that ParaView & VTK use a demand-driven pipeline design > meaning that until something explicitly tells a pipeline to update it > won't. For the Catalyst scripts this is done in the > coprocessor.WriteData(), coprocessor.WriteImages() and coprocessor.DoLiveVisualization() > calls for each output that is required (e.g. for a writer that is supposed > to output at that time step but not for other writers that are not supposed > to output at that time step). You can manually force a filter to update by > using the UpdatePipeline() method which will update that pipeline along > with everything it depends on. It won't update any filters though that > don't have an effect on it computing its requested information which means > that for the flameArea filter it won't affect any writers or image output > stuff which is what you want. > > There is some information on Catayst script details at > https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ > but I don't think that contains this information. > > Anatomy of a ParaView Catalyst Python Script | The Kitware ... > > blog.kitware.com > Introduction. ParaView Catalyst has yielded some amazing results. Such > results include iso-surfacing and generating images with 256K Message > Passing Interface (MPI ... > > > Cheers, > Andy > > On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> Hello again, >> >> >> I am working on a pipeline using Catalyst that writes data only when >> features are detected. The idea is to have a 3D contour generated in the >> pipeline, and when it is big enough, start recording data. There is a long >> lead-up to when the features appear, and then they disappear rapidly, so I >> would like to only collect data when the features are present. >> >> >> To that end, my DoCoProcessing() function has something that checks the >> 'Area' value in the CellData of an IntegrateVariables filter. The full >> function is below. However, this doesn't ever write any images or data. It >> also doesn't throw any errors, so I have a feeling the pipeline isn't >> actually evaluated/updated after the call to UpdateProducers. >> >> >> So, my question -- at what point in the DoCoProcessing function is the >> pipeline actually evaluated? Do all the filters execute when the >> UpdatedProducers function is called? Or do they only update when the >> outputs to which they are connected are called, ie. WriteData and >> WriteImages? >> >> >> Thanks, >> >> >> Tim >> >> >> def DoCoProcessing(datadescription): >> "Callback to do co-processing for current timestep" >> global coprocessor >> global lastTime >> global deltaT >> >> # Update the coprocessor by providing it the newly generated >> simulation data. >> >> >> # If the pipeline hasn't been setup yet, this will setup the >> pipeline. >> >> >> coprocessor.UpdateProducers(datadescription) >> >> curTime = datadescription.GetTime() >> >> if curTime >= lastTime + deltaT: >> lastTime = curTime >> >> if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: >> # Write output data, if appropriate. >> >> >> >> coprocessor.WriteData(datadescription); >> >> # Write image capture (Last arg: rescale lookup table), if >> appropriate. >> >> >> coprocessor.WriteImages(datadescription, >> rescale_lookuptable=False) >> >> # Live Visualization, if enabled. >> >> >> >> coprocessor.DoLiveVisualization(datadescription, "localhost", >> 22222) >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 tim.gallagher at gatech.edu Tue Feb 7 10:33:07 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 7 Feb 2017 15:33:07 +0000 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: , Message-ID: Along those lines, is it possible to turn on/off specific data writers based on something other than time step number? I have the data collection based on something from IntegrateVariables (it did require a broadcast from root), but I am creating multiple surfaces and would like to only save the data files when the surface appears. Is there a way to turn on/off the writers through the coprocessor.Pipeline object, or maybe through arguments to WriteData? As always, thanks for your help. Tim ________________________________ From: Andy Bauer Sent: Tuesday, February 7, 2017 10:05 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst The pipeline is update mechanism is often called a lazy update scheme meaning only do the requested work and no more. If the UpdateProducers() method automatically updated all of the filters there would be a lot of unneeded work that would be done. Think about a Catalyst script that branched into 3 separate outputs with a lot of work done in each branch. If only one output was wanted during a time step that could potentially be a lot of extra, unneeded work. As for parallel communication in Catalyst, again it's an efficiency thing meaning that if we can avoid communication we may as well do it. In interactive mode (i.e. through the GUI) it's useful to know things like the total number of points and cells, bounds and field ranges which requires communication. In Catalyst this information isn't usually needed so that's the type of information that would need to be globally communicated. For filters like the Integrate Attributes filter, you should get the same behavior in the GUI as in Catalyst with regard to parallel output since the filter itself does not know how ParaView is running. Some filters (e.g. Resample with Dataset) though only have non-empty results on process 0 so it is definitely safest to check filters like Integrate Attributes in parallel. Cheers, Andy On Tue, Feb 7, 2017 at 7:51 AM, Gallagher, Timothy P > wrote: Thanks Andy, I had a feeling the pipeline had to be manually updated. I thought maybe the UpdateProducers also updated the pipeline. Thanks for clarifying that. I also have the same concern about the value stored in each block's CellData field. I couldn't find any documentation that indicates how the IntegrateVariables filter distributes the data. But, looking at the block VTK files that are written out, they all contain the same value of Area so I think a global reduction is done in the filter and all blocks have the total values. I could be wrong though. Thanks again, Tim ________________________________ From: Andy Bauer > Sent: Tuesday, February 7, 2017 7:44 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst Hi Tim, The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() before checking for the area. You also may need to use MPI to do the global sum or broadcast of the value since I think that value will either just have local values or maybe just the proper global value on processor 0. You should have access to mpi4py in the Python script in order to do that. The long answer is that ParaView & VTK use a demand-driven pipeline design meaning that until something explicitly tells a pipeline to update it won't. For the Catalyst scripts this is done in the coprocessor.WriteData(), coprocessor.WriteImages() and coprocessor.DoLiveVisualization() calls for each output that is required (e.g. for a writer that is supposed to output at that time step but not for other writers that are not supposed to output at that time step). You can manually force a filter to update by using the UpdatePipeline() method which will update that pipeline along with everything it depends on. It won't update any filters though that don't have an effect on it computing its requested information which means that for the flameArea filter it won't affect any writers or image output stuff which is what you want. There is some information on Catayst script details at https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ but I don't think that contains this information. [https://blog.kitware.com/source/files/Small.4_447936566.jpg] Anatomy of a ParaView Catalyst Python Script | The Kitware ... blog.kitware.com Introduction. ParaView Catalyst has yielded some amazing results. Such results include iso-surfacing and generating images with 256K Message Passing Interface (MPI ... Cheers, Andy On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P > wrote: Hello again, I am working on a pipeline using Catalyst that writes data only when features are detected. The idea is to have a 3D contour generated in the pipeline, and when it is big enough, start recording data. There is a long lead-up to when the features appear, and then they disappear rapidly, so I would like to only collect data when the features are present. To that end, my DoCoProcessing() function has something that checks the 'Area' value in the CellData of an IntegrateVariables filter. The full function is below. However, this doesn't ever write any images or data. It also doesn't throw any errors, so I have a feeling the pipeline isn't actually evaluated/updated after the call to UpdateProducers. So, my question -- at what point in the DoCoProcessing function is the pipeline actually evaluated? Do all the filters execute when the UpdatedProducers function is called? Or do they only update when the outputs to which they are connected are called, ie. WriteData and WriteImages? Thanks, Tim def DoCoProcessing(datadescription): "Callback to do co-processing for current timestep" global coprocessor global lastTime global deltaT # Update the coprocessor by providing it the newly generated simulation data. # If the pipeline hasn't been setup yet, this will setup the pipeline. coprocessor.UpdateProducers(datadescription) curTime = datadescription.GetTime() if curTime >= lastTime + deltaT: lastTime = curTime if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: # Write output data, if appropriate. coprocessor.WriteData(datadescription); # Write image capture (Last arg: rescale lookup table), if appropriate. coprocessor.WriteImages(datadescription, rescale_lookuptable=False) # Live Visualization, if enabled. coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 Feb 7 11:03:27 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Feb 2017 11:03:27 -0500 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: Message-ID: Indeed it is possibly to write whenever you choose instead of just based on time step number. If you skip the RegisterWriter() when making a Pipeline object writer and then setting the file name and writing it manually you will get what you want. It would look something like the attached file. Note that I've set the outputfrequency to 1 here since I want to have DoCoProcessing() called every time step. You can put more logic into RequestDataDescription() if you don't want to have to create your grid and have DoCoProcessing() called every time step. Thanks for asking detailed questions! There is a whole lot of flexibility provided by using the Python scripts in Catalyst but it can take a bit of expertise to get exactly what you want. I am glad that you are taking advantage of this. Cheers, Andy On Tue, Feb 7, 2017 at 10:33 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Along those lines, is it possible to turn on/off specific data writers > based on something other than time step number? > > > I have the data collection based on something from IntegrateVariables (it > did require a broadcast from root), but I am creating multiple surfaces and > would like to only save the data files when the surface appears. > > > Is there a way to turn on/off the writers through the coprocessor.Pipeline > object, or maybe through arguments to WriteData? > > > As always, thanks for your help. > > > Tim > > ------------------------------ > *From:* Andy Bauer > *Sent:* Tuesday, February 7, 2017 10:05 AM > > *To:* Gallagher, Timothy P > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Pipeline update with Catalyst > > The pipeline is update mechanism is often called a lazy update scheme > meaning only do the requested work and no more. If the UpdateProducers() > method automatically updated all of the filters there would be a lot of > unneeded work that would be done. Think about a Catalyst script that > branched into 3 separate outputs with a lot of work done in each branch. If > only one output was wanted during a time step that could potentially be a > lot of extra, unneeded work. > > As for parallel communication in Catalyst, again it's an efficiency thing > meaning that if we can avoid communication we may as well do it. In > interactive mode (i.e. through the GUI) it's useful to know things like the > total number of points and cells, bounds and field ranges which requires > communication. In Catalyst this information isn't usually needed so that's > the type of information that would need to be globally communicated. For > filters like the Integrate Attributes filter, you should get the same > behavior in the GUI as in Catalyst with regard to parallel output since the > filter itself does not know how ParaView is running. Some filters (e.g. > Resample with Dataset) though only have non-empty results on process 0 so > it is definitely safest to check filters like Integrate Attributes in > parallel. > > Cheers, > Andy > > > On Tue, Feb 7, 2017 at 7:51 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> Thanks Andy, >> >> >> I had a feeling the pipeline had to be manually updated. I thought maybe >> the UpdateProducers also updated the pipeline. Thanks for clarifying that. >> >> >> I also have the same concern about the value stored in each block's >> CellData field. I couldn't find any documentation that indicates how the >> IntegrateVariables filter distributes the data. But, looking at the block >> VTK files that are written out, they all contain the same value of Area so >> I think a global reduction is done in the filter and all blocks have the >> total values. I could be wrong though. >> >> >> Thanks again, >> >> >> Tim >> >> >> ------------------------------ >> *From:* Andy Bauer >> *Sent:* Tuesday, February 7, 2017 7:44 AM >> *To:* Gallagher, Timothy P >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Pipeline update with Catalyst >> >> Hi Tim, >> >> The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() >> before checking for the area. You also may need to use MPI to do the global >> sum or broadcast of the value since I think that value will either just >> have local values or maybe just the proper global value on processor 0. You >> should have access to mpi4py in the Python script in order to do that. >> >> The long answer is that ParaView & VTK use a demand-driven pipeline >> design meaning that until something explicitly tells a pipeline to update >> it won't. For the Catalyst scripts this is done in the >> coprocessor.WriteData(), coprocessor.WriteImages() and >> coprocessor.DoLiveVisualization() calls for each output that is required >> (e.g. for a writer that is supposed to output at that time step but not for >> other writers that are not supposed to output at that time step). You can >> manually force a filter to update by using the UpdatePipeline() method >> which will update that pipeline along with everything it depends on. It >> won't update any filters though that don't have an effect on it computing >> its requested information which means that for the flameArea filter it >> won't affect any writers or image output stuff which is what you want. >> >> There is some information on Catayst script details at >> https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ >> but I don't think that contains this information. >> >> Anatomy of a ParaView Catalyst Python Script | The Kitware ... >> >> blog.kitware.com >> Introduction. ParaView Catalyst has yielded some amazing results. Such >> results include iso-surfacing and generating images with 256K Message >> Passing Interface (MPI ... >> >> >> Cheers, >> Andy >> >> On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P < >> tim.gallagher at gatech.edu> wrote: >> >>> Hello again, >>> >>> >>> I am working on a pipeline using Catalyst that writes data only when >>> features are detected. The idea is to have a 3D contour generated in the >>> pipeline, and when it is big enough, start recording data. There is a long >>> lead-up to when the features appear, and then they disappear rapidly, so I >>> would like to only collect data when the features are present. >>> >>> >>> To that end, my DoCoProcessing() function has something that checks the >>> 'Area' value in the CellData of an IntegrateVariables filter. The full >>> function is below. However, this doesn't ever write any images or data. It >>> also doesn't throw any errors, so I have a feeling the pipeline isn't >>> actually evaluated/updated after the call to UpdateProducers. >>> >>> >>> So, my question -- at what point in the DoCoProcessing function is the >>> pipeline actually evaluated? Do all the filters execute when the >>> UpdatedProducers function is called? Or do they only update when the >>> outputs to which they are connected are called, ie. WriteData and >>> WriteImages? >>> >>> >>> Thanks, >>> >>> >>> Tim >>> >>> >>> def DoCoProcessing(datadescription): >>> "Callback to do co-processing for current timestep" >>> global coprocessor >>> global lastTime >>> global deltaT >>> >>> # Update the coprocessor by providing it the newly generated >>> simulation data. >>> >>> >>> # If the pipeline hasn't been setup yet, this will setup the >>> pipeline. >>> >>> >>> coprocessor.UpdateProducers(datadescription) >>> >>> curTime = datadescription.GetTime() >>> >>> if curTime >= lastTime + deltaT: >>> lastTime = curTime >>> >>> if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: >>> # Write output data, if appropriate. >>> >>> >>> >>> coprocessor.WriteData(datadescription); >>> >>> # Write image capture (Last arg: rescale lookup table), if >>> appropriate. >>> >>> >>> coprocessor.WriteImages(datadescription, >>> rescale_lookuptable=False) >>> >>> # Live Visualization, if enabled. >>> >>> >>> >>> coprocessor.DoLiveVisualization(datadescription, "localhost", >>> 22222) >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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: gridwriter2.py Type: text/x-python Size: 3245 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Feb 7 11:38:48 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Feb 2017 11:38:48 -0500 Subject: [Paraview] Simple problem with point data and geometry definition In-Reply-To: References: Message-ID: The VTU file format expects all pieces to have exactly the same data arrays. Seems to me what you want is a multiblock dataset, *.vtm, which can have muliple datasets with different arrays. On Fri, Feb 3, 2017 at 7:43 AM, Emrah Ersan Erdogan wrote: > Hi, > > I have two small problems and since I am just a newbie I really appreciate any help. > > In the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. > > First problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. > Second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? > > Thanks a bunch! > > Ersan > > > > > > > > 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 > > > > > 0 1 2 3 > > > 4 > > > 9 > > > > > > > > > > > 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 > > > > > > > > > > > > > 2.0 3.0 0.0 > 3.0 2.0 0.0 > 0.0 0.0 0.0 > > 1.0 2.0 0.0 > 2.0 1.0 0.0 > 0.0 0.0 0.0 > > 5.0 4.0 0.0 > 4.0 1.0 0.0 > 0.0 0.0 0.0 > > 3.0 6.0 0.0 > 6.0 7.0 0.0 > 0.0 0.0 0.0 > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Feb 7 11:40:07 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Feb 2017 11:40:07 -0500 Subject: [Paraview] Labeling Polydatas In-Reply-To: References: Message-ID: Not currently, no. We limit to showing labels for selected data since the label rendering code is not smart enough to avoid overlaps, clutter and can be fairly useless for large data. On Thu, Feb 2, 2017 at 6:19 PM, Dean, Kevin wrote: > Hey Guys, > > So I understand how to utilize the selection display inspector to visualize > a cell id number. However, is there a way to have the labels associated with > the polydata (or all inside of an vtkAppendPolyData) so that when I load my > .vtp, I automatically see the Cell Ids? > > This email and its contents are confidential. If you are not the intended > recipient, please do not disclose or use the information within this email > or its attachments. If you have received this email in error, please report > the error to the sender by return email and delete this communication from > your records. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 tim.gallagher at gatech.edu Tue Feb 7 11:58:36 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 7 Feb 2017 16:58:36 +0000 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: , Message-ID: Okay, I'm solidly impressed now. I know it says all over the place that because Paraview uses Python, you can use Python. But for some reason, I always just look at it as using the grammar/structure of Python to interface with vtk and Paraview -- for some reason it takes me some time to recognize that I can use everything that comes with Python. Not sure why since I use Python every day for a lot of things. I also get stuck on what is a transparent, helper function and what is an opaque interface to some vtk C++ function. For example, it didn't occur to me that the coprocessor.WriteData() function just looped over a list of writers, formatted the file name, and then updated the filter. I thought it was something in C++ that did things that weren't exposed to the Python interface. Now that I'm slowly recognizing those things though, Catalyst is immensely more useful than the way I was using it before. I was sort of pigeonholed into thinking it had to look identical to the output from the generator and the only thing to tweak was in the pipeline. I've got it set up now to track volume integrated variables every fixed unit of time and also to check if different features appear in the solution. If they appear, it writes some different data files and images. I've attached the processing method just to close the loop and provide an example of how to do the things I couldn't figure out (and didn't think was possible). I know there's several things that could probably be done better in it, but it works for me at the moment. Thanks again! Tim ________________________________ From: Andy Bauer Sent: Tuesday, February 7, 2017 11:03 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst Indeed it is possibly to write whenever you choose instead of just based on time step number. If you skip the RegisterWriter() when making a Pipeline object writer and then setting the file name and writing it manually you will get what you want. It would look something like the attached file. Note that I've set the outputfrequency to 1 here since I want to have DoCoProcessing() called every time step. You can put more logic into RequestDataDescription() if you don't want to have to create your grid and have DoCoProcessing() called every time step. Thanks for asking detailed questions! There is a whole lot of flexibility provided by using the Python scripts in Catalyst but it can take a bit of expertise to get exactly what you want. I am glad that you are taking advantage of this. Cheers, Andy On Tue, Feb 7, 2017 at 10:33 AM, Gallagher, Timothy P > wrote: Along those lines, is it possible to turn on/off specific data writers based on something other than time step number? I have the data collection based on something from IntegrateVariables (it did require a broadcast from root), but I am creating multiple surfaces and would like to only save the data files when the surface appears. Is there a way to turn on/off the writers through the coprocessor.Pipeline object, or maybe through arguments to WriteData? As always, thanks for your help. Tim ________________________________ From: Andy Bauer > Sent: Tuesday, February 7, 2017 10:05 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst The pipeline is update mechanism is often called a lazy update scheme meaning only do the requested work and no more. If the UpdateProducers() method automatically updated all of the filters there would be a lot of unneeded work that would be done. Think about a Catalyst script that branched into 3 separate outputs with a lot of work done in each branch. If only one output was wanted during a time step that could potentially be a lot of extra, unneeded work. As for parallel communication in Catalyst, again it's an efficiency thing meaning that if we can avoid communication we may as well do it. In interactive mode (i.e. through the GUI) it's useful to know things like the total number of points and cells, bounds and field ranges which requires communication. In Catalyst this information isn't usually needed so that's the type of information that would need to be globally communicated. For filters like the Integrate Attributes filter, you should get the same behavior in the GUI as in Catalyst with regard to parallel output since the filter itself does not know how ParaView is running. Some filters (e.g. Resample with Dataset) though only have non-empty results on process 0 so it is definitely safest to check filters like Integrate Attributes in parallel. Cheers, Andy On Tue, Feb 7, 2017 at 7:51 AM, Gallagher, Timothy P > wrote: Thanks Andy, I had a feeling the pipeline had to be manually updated. I thought maybe the UpdateProducers also updated the pipeline. Thanks for clarifying that. I also have the same concern about the value stored in each block's CellData field. I couldn't find any documentation that indicates how the IntegrateVariables filter distributes the data. But, looking at the block VTK files that are written out, they all contain the same value of Area so I think a global reduction is done in the filter and all blocks have the total values. I could be wrong though. Thanks again, Tim ________________________________ From: Andy Bauer > Sent: Tuesday, February 7, 2017 7:44 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Pipeline update with Catalyst Hi Tim, The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() before checking for the area. You also may need to use MPI to do the global sum or broadcast of the value since I think that value will either just have local values or maybe just the proper global value on processor 0. You should have access to mpi4py in the Python script in order to do that. The long answer is that ParaView & VTK use a demand-driven pipeline design meaning that until something explicitly tells a pipeline to update it won't. For the Catalyst scripts this is done in the coprocessor.WriteData(), coprocessor.WriteImages() and coprocessor.DoLiveVisualization() calls for each output that is required (e.g. for a writer that is supposed to output at that time step but not for other writers that are not supposed to output at that time step). You can manually force a filter to update by using the UpdatePipeline() method which will update that pipeline along with everything it depends on. It won't update any filters though that don't have an effect on it computing its requested information which means that for the flameArea filter it won't affect any writers or image output stuff which is what you want. There is some information on Catayst script details at https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ but I don't think that contains this information. [https://blog.kitware.com/source/files/Small.4_447936566.jpg] Anatomy of a ParaView Catalyst Python Script | The Kitware ... blog.kitware.com Introduction. ParaView Catalyst has yielded some amazing results. Such results include iso-surfacing and generating images with 256K Message Passing Interface (MPI ... Cheers, Andy On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P > wrote: Hello again, I am working on a pipeline using Catalyst that writes data only when features are detected. The idea is to have a 3D contour generated in the pipeline, and when it is big enough, start recording data. There is a long lead-up to when the features appear, and then they disappear rapidly, so I would like to only collect data when the features are present. To that end, my DoCoProcessing() function has something that checks the 'Area' value in the CellData of an IntegrateVariables filter. The full function is below. However, this doesn't ever write any images or data. It also doesn't throw any errors, so I have a feeling the pipeline isn't actually evaluated/updated after the call to UpdateProducers. So, my question -- at what point in the DoCoProcessing function is the pipeline actually evaluated? Do all the filters execute when the UpdatedProducers function is called? Or do they only update when the outputs to which they are connected are called, ie. WriteData and WriteImages? Thanks, Tim def DoCoProcessing(datadescription): "Callback to do co-processing for current timestep" global coprocessor global lastTime global deltaT # Update the coprocessor by providing it the newly generated simulation data. # If the pipeline hasn't been setup yet, this will setup the pipeline. coprocessor.UpdateProducers(datadescription) curTime = datadescription.GetTime() if curTime >= lastTime + deltaT: lastTime = curTime if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: # Write output data, if appropriate. coprocessor.WriteData(datadescription); # Write image capture (Last arg: rescale lookup table), if appropriate. coprocessor.WriteImages(datadescription, rescale_lookuptable=False) # Live Visualization, if enabled. coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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: processing_method.py Type: text/x-python Size: 3599 bytes Desc: processing_method.py URL: From jfavre at cscs.ch Tue Feb 7 11:58:25 2017 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 7 Feb 2017 16:58:25 +0000 Subject: [Paraview] PlotSelectionOverTime and transient set of particles Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684379AA6F@MBX111.d.ethz.ch> Hi there I have a time-dependent set of particles(stored as 1 cell of type VTK_POLY_VERTEX). Particles are born and die during the simulation. But they have a unique Id. I use it as a "GlobalNodeIds" array. I want to plot the time history of particles based on their Id. Pretty simple, you'd say. (Although it took me 2 days to get the python syntax straight, :-( ). (This has to run in batch mode; millions of particles and thousands of timesteps) so I use a GlobalIDSelectionSource() and a PlotSelectionOverTime(). I am able to save screenshots of my QuartileChartView and save the data in a CSV file. It all works well, if and only if the particle exists from the beginning of Time, even if it dies before EndTime. However, if I give a GlobalID of a particle not yet born at the StartTime, ParaView records all data as 0, vtkValidPointMask is set to 0 (rightly so), but the QuartileChartView draws connected lines with all 0s, then jumps off to the real values at the time the particle is born. My wish would be to *not* draw anything where vtkValidPointMask == 0. Otherwise it throws off all plots. Is there an option to draw "dotted" lines with empty segments where the mask indicates the values are not valid? By the way, these values ought to be NaN (instead of 0). N.B. if particles die before the end, there is no confusion. The CSV files only record data up until the last timestep where the particle exist. Any hint would be appreciated. ----------------- Jean -------------- next part -------------- An HTML attachment was scrubbed... URL: From adershowitz at exponent.com Tue Feb 7 11:58:56 2017 From: adershowitz at exponent.com (Adam Dershowitz) Date: Tue, 7 Feb 2017 16:58:56 +0000 Subject: [Paraview] Paraview crashes with netCDF Message-ID: <12E0D357-BDEC-499D-B545-538EAADDA1A6@exponent.com> I have a geotiff file that I want to view in Paraview. But, Paraview seems to not show the correct offset (0,0 instead of respected the offset). The work around I have been trying is to warp it to the correct location using gdalwarp and to export it as a netCDF. Then Paraview should be able to show it correctly. But, I have run into a crash. If I do this: gdalwarp -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc then I try to open test.nc in Paraview immediately crashes. While, instead if do this: gdalwarp -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc then it opens fine. The difference between these two files is that EPSG 3652 uses feet (which is better for me, for this particular project) while 3651 uses meters. Both appear to be valid NetCDF files. I?ve tried both readers ?CAM NetCDF (Unstructured)? and ?NetCDF files generic and CF conventions? with the same results. I?m running Paraview 5.2.0 64-bit on Mac OS 10.12.3. But, I have seen identical results on an older Mac with a prior OS. I had also tried an older version of Paraview with the same result. Any ideas why this consistently crashes Paraview, or what to do about it? Using netCDF was already a work around, and I willing to try others to view these files. The offset and scale are important because I then need to put in other data that is in the correct location and units. The files are too big for me to send to the mailing list, so I have not posted them. Thanks, -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Feb 7 12:50:22 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Feb 2017 12:50:22 -0500 Subject: [Paraview] Pipeline update with Catalyst In-Reply-To: References: Message-ID: Glad to hear that you've got it working the way you want. As far as the generated script, you are right that it should just be seen as an example. All it really needs is the RequestDataDescription() and DoCoProcessing() methods (you can also have an optional Finalize() method as well that takes in a datasecription object if you want to do something upon exit). What you do in those methods is pretty much up to your knowledge and imagination. Note that you don't even need to use filters to do data processing. Have you looked at the Python data set adaptor blogs? They start at https://blog.kitware.com/improved-vtk-numpy-integration/ and allow you to deal with the data sets in a more Pythonic way and simplify using numpy to do operations. I have trouble myself figuring out what stuff is actual Python code and what stuff is C++ wrapped. From a functionality standpoint it probably doesn't make a difference but from a debugging standpoint it makes it a bit more tough. On Tue, Feb 7, 2017 at 11:58 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Okay, I'm solidly impressed now. > > > I know it says all over the place that because Paraview uses Python, you > can use Python. But for some reason, I always just look at it as using the > grammar/structure of Python to interface with vtk and Paraview -- for some > reason it takes me some time to recognize that I can use everything that > comes with Python. Not sure why since I use Python every day for a lot of > things. > > > I also get stuck on what is a transparent, helper function and what is an > opaque interface to some vtk C++ function. For example, it didn't occur to > me that the coprocessor.WriteData() function just looped over a list of > writers, formatted the file name, and then updated the filter. I thought it > was something in C++ that did things that weren't exposed to the Python > interface. > > > Now that I'm slowly recognizing those things though, Catalyst is immensely > more useful than the way I was using it before. I was sort of pigeonholed > into thinking it had to look identical to the output from the generator and > the only thing to tweak was in the pipeline. > > > I've got it set up now to track volume integrated variables every fixed > unit of time and also to check if different features appear in the > solution. If they appear, it writes some different data files and images. > I've attached the processing method just to close the loop and provide an > example of how to do the things I couldn't figure out (and didn't think was > possible). I know there's several things that could probably be done better > in it, but it works for me at the moment. > > > Thanks again! > > > Tim > > > ------------------------------ > *From:* Andy Bauer > *Sent:* Tuesday, February 7, 2017 11:03 AM > > *To:* Gallagher, Timothy P > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Pipeline update with Catalyst > > Indeed it is possibly to write whenever you choose instead of just based > on time step number. If you skip the RegisterWriter() when making a > Pipeline object writer and then setting the file name and writing it > manually you will get what you want. It would look something like the > attached file. > > Note that I've set the outputfrequency to 1 here since I want to have > DoCoProcessing() called every time step. You can put more logic into > RequestDataDescription() if you don't want to have to create your grid and > have DoCoProcessing() called every time step. > > Thanks for asking detailed questions! There is a whole lot of flexibility > provided by using the Python scripts in Catalyst but it can take a bit of > expertise to get exactly what you want. I am glad that you are taking > advantage of this. > > Cheers, > Andy > > > > On Tue, Feb 7, 2017 at 10:33 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> Along those lines, is it possible to turn on/off specific data writers >> based on something other than time step number? >> >> >> I have the data collection based on something from IntegrateVariables (it >> did require a broadcast from root), but I am creating multiple surfaces and >> would like to only save the data files when the surface appears. >> >> >> Is there a way to turn on/off the writers through the >> coprocessor.Pipeline object, or maybe through arguments to WriteData? >> >> >> As always, thanks for your help. >> >> >> Tim >> >> ------------------------------ >> *From:* Andy Bauer >> *Sent:* Tuesday, February 7, 2017 10:05 AM >> >> *To:* Gallagher, Timothy P >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Pipeline update with Catalyst >> >> The pipeline is update mechanism is often called a lazy update scheme >> meaning only do the requested work and no more. If the UpdateProducers() >> method automatically updated all of the filters there would be a lot of >> unneeded work that would be done. Think about a Catalyst script that >> branched into 3 separate outputs with a lot of work done in each branch. If >> only one output was wanted during a time step that could potentially be a >> lot of extra, unneeded work. >> >> As for parallel communication in Catalyst, again it's an efficiency thing >> meaning that if we can avoid communication we may as well do it. In >> interactive mode (i.e. through the GUI) it's useful to know things like the >> total number of points and cells, bounds and field ranges which requires >> communication. In Catalyst this information isn't usually needed so that's >> the type of information that would need to be globally communicated. For >> filters like the Integrate Attributes filter, you should get the same >> behavior in the GUI as in Catalyst with regard to parallel output since the >> filter itself does not know how ParaView is running. Some filters (e.g. >> Resample with Dataset) though only have non-empty results on process 0 so >> it is definitely safest to check filters like Integrate Attributes in >> parallel. >> >> Cheers, >> Andy >> >> >> On Tue, Feb 7, 2017 at 7:51 AM, Gallagher, Timothy P < >> tim.gallagher at gatech.edu> wrote: >> >>> Thanks Andy, >>> >>> >>> I had a feeling the pipeline had to be manually updated. I thought maybe >>> the UpdateProducers also updated the pipeline. Thanks for clarifying that. >>> >>> >>> I also have the same concern about the value stored in each block's >>> CellData field. I couldn't find any documentation that indicates how the >>> IntegrateVariables filter distributes the data. But, looking at the block >>> VTK files that are written out, they all contain the same value of Area so >>> I think a global reduction is done in the filter and all blocks have the >>> total values. I could be wrong though. >>> >>> >>> Thanks again, >>> >>> >>> Tim >>> >>> >>> ------------------------------ >>> *From:* Andy Bauer >>> *Sent:* Tuesday, February 7, 2017 7:44 AM >>> *To:* Gallagher, Timothy P >>> *Cc:* paraview at paraview.org >>> *Subject:* Re: [Paraview] Pipeline update with Catalyst >>> >>> Hi Tim, >>> >>> The short answer is that you need to do coprocessor.Pipeline.flameArea.UpdatePipeline() >>> before checking for the area. You also may need to use MPI to do the global >>> sum or broadcast of the value since I think that value will either just >>> have local values or maybe just the proper global value on processor 0. You >>> should have access to mpi4py in the Python script in order to do that. >>> >>> The long answer is that ParaView & VTK use a demand-driven pipeline >>> design meaning that until something explicitly tells a pipeline to update >>> it won't. For the Catalyst scripts this is done in the >>> coprocessor.WriteData(), coprocessor.WriteImages() and >>> coprocessor.DoLiveVisualization() calls for each output that is >>> required (e.g. for a writer that is supposed to output at that time step >>> but not for other writers that are not supposed to output at that time >>> step). You can manually force a filter to update by using the >>> UpdatePipeline() method which will update that pipeline along with >>> everything it depends on. It won't update any filters though that don't >>> have an effect on it computing its requested information which means that >>> for the flameArea filter it won't affect any writers or image output stuff >>> which is what you want. >>> >>> There is some information on Catayst script details at >>> https://blog.kitware.com/anatomy-of-a-paraview-catalyst-python-script/ >>> but I don't think that contains this information. >>> >>> Anatomy of a ParaView Catalyst Python Script | The Kitware ... >>> >>> blog.kitware.com >>> Introduction. ParaView Catalyst has yielded some amazing results. Such >>> results include iso-surfacing and generating images with 256K Message >>> Passing Interface (MPI ... >>> >>> >>> Cheers, >>> Andy >>> >>> On Tue, Feb 7, 2017 at 7:14 AM, Gallagher, Timothy P < >>> tim.gallagher at gatech.edu> wrote: >>> >>>> Hello again, >>>> >>>> >>>> I am working on a pipeline using Catalyst that writes data only when >>>> features are detected. The idea is to have a 3D contour generated in the >>>> pipeline, and when it is big enough, start recording data. There is a long >>>> lead-up to when the features appear, and then they disappear rapidly, so I >>>> would like to only collect data when the features are present. >>>> >>>> >>>> To that end, my DoCoProcessing() function has something that checks the >>>> 'Area' value in the CellData of an IntegrateVariables filter. The full >>>> function is below. However, this doesn't ever write any images or data. It >>>> also doesn't throw any errors, so I have a feeling the pipeline isn't >>>> actually evaluated/updated after the call to UpdateProducers. >>>> >>>> >>>> So, my question -- at what point in the DoCoProcessing function is the >>>> pipeline actually evaluated? Do all the filters execute when the >>>> UpdatedProducers function is called? Or do they only update when the >>>> outputs to which they are connected are called, ie. WriteData and >>>> WriteImages? >>>> >>>> >>>> Thanks, >>>> >>>> >>>> Tim >>>> >>>> >>>> def DoCoProcessing(datadescription): >>>> "Callback to do co-processing for current timestep" >>>> global coprocessor >>>> global lastTime >>>> global deltaT >>>> >>>> # Update the coprocessor by providing it the newly generated >>>> simulation data. >>>> >>>> >>>> # If the pipeline hasn't been setup yet, this will setup the >>>> pipeline. >>>> >>>> >>>> coprocessor.UpdateProducers(datadescription) >>>> >>>> curTime = datadescription.GetTime() >>>> >>>> if curTime >= lastTime + deltaT: >>>> lastTime = curTime >>>> >>>> if coprocessor.Pipeline.flameArea.CellData['Area'] > 1e-9: >>>> # Write output data, if appropriate. >>>> >>>> >>>> >>>> coprocessor.WriteData(datadescription); >>>> >>>> # Write image capture (Last arg: rescale lookup table), if >>>> appropriate. >>>> >>>> >>>> coprocessor.WriteImages(datadescription, >>>> rescale_lookuptable=False) >>>> >>>> # Live Visualization, if enabled. >>>> >>>> >>>> >>>> coprocessor.DoLiveVisualization(datadescription, "localhost", >>>> 22222) >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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 kmorel at sandia.gov Tue Feb 7 13:16:45 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 7 Feb 2017 18:16:45 +0000 Subject: [Paraview] First trial file does not work-help! Message-ID: I'm not sure I understand what you are asking. I think you want to show the two blocks with different representations (outline and surface, respectively). If you take a look at the Multi-block Inspector (View ? Multi-block Inspector) you can find controls to add different display properties to different blocks. Unfortunately, you are not able to set different representations on different blocks. Here is a way around the problem though: 1. Add the Outline filter to the reader (Filters ? Alphabetical ? Outline). You will now see geometry, gauss points, and outlines around both. 2. Select the reader in the pipeline browser, go to the Multi-block Inspector, right click on the block for geometry, and select Hide Block. 3. Select the Outline filter in the pipeline browser, go to the Multi-block Inspector, right click on the block for gauss points, and select Hide Block. -Ken -----Original Message----- From: Emrah Ersan Erdogan [mailto:emrahersanerdogan at gmail.com] Sent: Friday, February 3, 2017 3:02 PM To: Moreland, Kenneth Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] First trial file does not work-help! Thanks, that works very well. Since I just learn at the moment I prefer to work on text editor. I guess when I integrate it to my FE solver in c++, it will be ok from now on. The only thing is that I think it is not possible to make one show the outline (geometry) and the other gaussian points at the same time in paraview. Do you know any way to do it? Because otherwise I will be forced to work on separate files unfortunately. Best Ersan > On 3 Feb 2017, at 18:57, Moreland, Kenneth wrote: > > Trust me, you are not the first person to be burned by smart quotes. > (Viva la vim?) > > I suggest putting each piece in its own vtu file and then create a vtm file that points to the two of them. Here is a simple example of the contents of a vtm file: > > byte_order="LittleEndian" header_type="UInt64"> > > > > > > > > > -Ken > > > On 2/3/17, 6:37 AM, "Emrah Ersan Erdogan" wrote: > > You are a life-saver, literally. That would not have occurred to me for a long time believe me. > > As a final step, in the first piece I want to create only the geometry and in the second piece some points (these are gauss points actually) and with some data. > The problem is, paraview does not see ?strain? when it is defined as given below. However, if I swap the point dataset to the first piece it works: on the wrong points of course. > And second, it is apparently not possible to show the geometry and point values at the same time. Do you think I need to define two separate files and "light them up" separately on main paraview screen? > > Thank you a lot again. I think this will conclude my problem entirely. > > Ersan > > > > > > > > 0.00 0.00 0.00 1.00 0.00 0.00 1.00 1.00 0.00 0.00 1.00 0.00 > > > > > 0 1 2 3 > > > 4 > > > 9 > > > > > > > > > > > 0.25 0.25 0.00 0.75 0.25 0.00 0.75 0.75 0.00 0.25 0.75 0.00 > > > > > > > > > > > > > 2.0 3.0 0.0 > 3.0 2.0 0.0 > 0.0 0.0 0.0 > > 1.0 2.0 0.0 > 2.0 1.0 0.0 > 0.0 0.0 0.0 > > 5.0 4.0 0.0 > 4.0 1.0 0.0 > 0.0 0.0 0.0 > > 3.0 6.0 0.0 > 6.0 7.0 0.0 > 0.0 0.0 0.0 > > > > > > > > >> On 3 Feb 2017, at 01:24, Moreland, Kenneth wrote: >> >> Did you type this in a text editor? The first thing I notice is that many of the quotes are the fancy open/close characters. Many text editors use a ?smart quotes? feature that replaces the straight quote to a bent open or closed quote. The VTK reader only accepts the straight quotes (ASCII character 34). >> >> -Ken >> >> >> On 2/2/17, 5:58 PM, "ParaView on behalf of Emrah Ersan Erdogan" wrote: >> >> Hi, >> >> I am a new user of paraview and try to understand .vtu file format. >> Just as a simple test I wanted to create two pieces one solely defines 4 points and a cell with no attributes, hence forming geometry only. And the second piece defines only points with point attributes. >> >> However, it seems I am doing something(s) wrong since paraview reader does not recognize the information. It would be great if somebody tells me what I am doing wrong. Afterwards I can take it off by myself I guess. >> >> Thanks a bunch! >> >> Ersan >> >> >> >> >> >> 2.0 2.0 3.0 1.0 >> >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > From adlinds3 at ncsu.edu Tue Feb 7 14:03:44 2017 From: adlinds3 at ncsu.edu (Alex Lindsay) Date: Tue, 7 Feb 2017 13:03:44 -0600 Subject: [Paraview] Integrate spatially and temporally Message-ID: <6b61f9cc-7a3e-304b-b4a5-bdd43b3258ff@ncsu.edu> Hi all, I have a data set for which I would like perform both spatial and temporal integration. I can easily do the spatial integration with `IntegrateVariables`. I've set up a `PlotSelectionOverTime` filter that allows me to plot the spatially averaged value over time. However, I don't know how to integrate this curve. If I try to derive directly from `PlotSelectionOverTime`, `IntegrateVariables` is grayed out. I've tried doing 1. `TableToPoints` filter using `Time` as one of the coordinates (derive from `PlotSelectionOverTime`) 2. Select all resulting "points" in either the `Render` or `Spreadsheet` views 3. `IntegrateVariables` (no longer grayed out) but this yields `0` for all of my fields. I ran across [this thread](http://marc.info/?l=paraview&m=128804494805006&w=2) from years ago but things aren't panning out for me. I'm using Paraview 5.2.0. Alex From michel.rasquin at colorado.edu Tue Feb 7 14:05:46 2017 From: michel.rasquin at colorado.edu (Michel Rasquin) Date: Tue, 7 Feb 2017 19:05:46 +0000 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support In-Reply-To: References: , Message-ID: Hi Chuck, Thank you for your help. Indeed, I built PVSB 5.2 with the intel 2016.2.181 and intelmpi 5.1.3.181 compilers, then ran the resulting pvserver on Haswell CPU nodes (Intel E5-2680v3) which supports AVX2 instructions. So this fits exactly the known issue you mentioned in your email. Exporting the GALIIUM_DRIVER env variable to swr then leads to an interesting behavior. With the swr driver, the good news is that I can connect my pvserver built in release mode without crashing. For the recollection, the llvmpipe driver compiled in release mode crashes during the client/server connection, whereas the llvmpipe driver compiled in debug mode works fine. However, our PBS scheduling killed quickly my interactive job because the virtual memory was exhausted, which was puzzling. Increasing the number of cores requested for my job and keeping some of them idle allowed me to increase the available memory at the cost of wasted cpu resources. I could then compare the virtual and resident memory of the three following configurations: 1) pvserver using the llvmpipe driver compiled in debug 2) pvserver using swr driver compiled in debug mode 3) pvserver using swr driver compiled in release mode The memory consumption (in MB) of the pvserver before and after the connection to the client is the following: 1) llvmpipe dbg before connection : Virtual 814 - Resident 71 after connection: Virtual 875 - Resident 128 2) swr dbg before connection: Virtual 814 - Resident 93 after connection: Virtual 2407 (!!) - Resident 171 3) swr rls before connection: Virtual 643 - Resident 76 after connection: Virtual 2235 (!!) - Resident 127 As you can see, there is a big jump in terms of virtual memory consumption when the pvserver with the swr driver connects to the client, which is not the case for the pvserver with the llvmpipe driver. Since the maximum virtual memory available per core is around 2670MB minus whatever is needed by the system, it quickly exhausts the available virtual memory as soon as data are loaded (virtual memory keeps increasing). Note also the big gap between the virtual and the resident memory consumption for the swr driver. Have you already observed this behavior and is it possible to reduce the virtual memory consumption of the swr driver? Would you also know if this known issue with the llvmpipe driver will be fixed of PV 5.3 (agreeing on the fact that the swr driver should be faster on intel CPU provided that it does not exhaust the memory consumption). Thank you. Best regards, Michel ________________________________ From: Chuck Atkins Sent: Monday, February 6, 2017 5:06:35 PM To: Michel Rasquin Cc: paraview at paraview.org Subject: Re: [Paraview] Issues with PVSB 5.2 and OSMesa support Hi Michel, However, it starts to become tricky when I use pvserver with OSMesa support. It appears the resulting pvserver with OSMesa support compiled in Release mode always crashes when I try to load data, Which compiler are you building with and type of CPUs are available on the node you're running on? There is a known issue with llvmpipe and the Intel compiler causing segfaults. If youre CPU is new enough (supports AVX) then you can use the swr driver. See http://www.paraview.org/Wiki/ParaView_And_Mesa_3D#Using_the_llvmpipe_and_swr_drivers for details on switching between llvmpipe and swr drivers and adjusting the number of threads used by each one. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Tue Feb 7 16:03:50 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Tue, 7 Feb 2017 16:03:50 -0500 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support In-Reply-To: References: Message-ID: Hi Michel, > Indeed, I built PVSB 5.2 with the intel 2016.2.181 and intelmpi 5.1.3.181 > compilers, then ran the resulting pvserver on Haswell CPU nodes (Intel > E5-2680v3) which supports AVX2 instructions. So this fits exactly the > known issue you mentioned in your email. > Yep, that'll do it. The problem is due to a bug in the Intel compiler performing over-agressive vectorized code generation. I'm not sure if it's fixed in >= 17 or not but I definitely know it's broken in <= 16.x. GALLIUM_DRIVER=SWR is going to give you the best performance in this situation anyways though and is the recommended osmesa driver on x86_64 CPUs. Exporting the GALIIUM_DRIVER env variable to swr then leads to > an interesting behavior. With the swr driver, the good news is that I can > connect my pvserver built in release mode without crashing. > Great! > For the recollection, the llvmpipe driver compiled in release mode crashes > during the client/server connection, whereas the llvmpipe driver compiled > in debug mode works fine. > This lines up with the issue being bad vectorization since the compiler won't be doing m,ost of those optimizations in a debug build. However, our PBS scheduling killed quickly my interactive job because the > virtual memory was exhausted, which was puzzling. Increasing the number > of cores requested for my job and keeping some of them idle allowed me to > increase the available memory at the cost of wasted cpu resources. > I suspect the problem is is a massive oversubscription of threads by swr. The default behavior of swr is to use all available CPU cores on the node. However, when running multiple MPI processes per node, they have no way of knowing about each other. So if you've got 24 cores per node and run 24 pvservers, you'll end up with 24^2 = 576 rendering threads on a nodes; not so great. You can control this with the KNOB_MAX_WORKER_THREADS environment variable. Typically you'll want to set it to the inverse of processes per node your job is running. So if yor node has 24 cores and you run 24 processes per node, then set KNOB_MAX_WORKER_THREADS to 1, but if you're running 4 processes per node, then set it to 6; you get the idea. That should address the virtual memory problem. It's a balance since typically rendering will perform better with fewer ppn and mroe threads per process, but the filters, like Contour, parallelize at the MPI level and work better with a higher ppn. You'll need to find the right balance for your use case depending on whether it's render-heaver or pipeline pricessing heavy. > Would you also know if this known issue with the llvmpipe driver will be > fixed of PV 5.3 (agreeing on the fact that the swr driver should be faster > on intel CPU provided that it does not exhaust the memory consumption). > It's actually an Intel compiler bug and not a ParaView (or even Mesa for that matter) issue, so probably not. It may be fixed in future releases of icc but I wouldn't know withotu testng it. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Tue Feb 7 16:57:32 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 7 Feb 2017 16:57:32 -0500 Subject: [Paraview] [EXTERNAL] Re: [Paraview-developers] Scripting image compression parameters In-Reply-To: <485e1ce5e1b2419db1c4a3387767ae3a@ES01AMSNLNT.srn.sandia.gov> References: <485e1ce5e1b2419db1c4a3387767ae3a@ES01AMSNLNT.srn.sandia.gov> Message-ID: You mean create a bug ticket? Let me try to clarify a bit more on what I am doing. I am using my Ubuntu machine for this. 1. I start the trace just like normal from "Tools -> Start Trace". I choose all properties to track. 2. I go to "Edit -> Settings -> Render View" and select settings from the "Remote/Parallel Rendering Options." 3. I stop trace, but nothing actually gets traced. Does this make sense? I am not sure if this is a bug, or the trace functionality was never meant to trace the settings but only the properties of the scene. If you or anyone has any more insights to this, please do share. I won't mind writing my own scripts to do this if it is even possible. On Mon, Feb 6, 2017 at 9:14 PM, Scott, W Alan wrote: > Sounds like a bug. Mind writing it up? If you want, if you give me step > by step details on what is failing, I can also write it up for you. > > > > Alan > > > > *From:* Faiz Abidi [mailto:fabidi89 at vt.edu] > *Sent:* Friday, February 3, 2017 10:13 AM > *To:* Scott, W Alan > *Cc:* paraview-developers at paraview.org; paraview at paraview.org > *Subject:* Re: [EXTERNAL] Re: [Paraview-developers] Scripting image > compression parameters > > > > Hi Alan, > > > > Sorry for a delayed response, but I missed this email somehow. > > > > So, I actually have tried the trace function ParaView supports, but > unfortunately, it doesn't trace the settings I set for the image > compression settings. > > > > I guess I'll have to do it manually then, but I would be interested to > know if anyone else has tried to script the compression parameters. I am > kind of surprised if this is not possible to script. > > > > Best, > > > > On Mon, Jan 30, 2017 at 4:55 PM, Scott, W Alan wrote: > > My best guess would be to try to trace the save screenshot functionality, > and see what is set. Sorry, that?s the best I have... > > > > Alan > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *Faiz Abidi > *Sent:* Monday, January 30, 2017 2:14 PM > *To:* paraview-developers at paraview.org; paraview at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Scripting image > compression parameters > > > > Not having heard back from anyone, I am guessing no one has done this kind > of scripting before? Anyone? > > > > On Wed, Jan 25, 2017 at 9:43 AM, Faiz Abidi wrote: > > Hello ParaView community, > > > > ParaView provides various image compression configuration options > . I > was wondering how to go about scripting this so that I can test setting > various parameters in a script. > > > > I did check some of ParaView modules but couldn't find anything helpful. > > > > Any pointers from anyone would be helpful. > > > > Best, > -- > > 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 umut.tabak at gmail.com Tue Feb 7 17:04:09 2017 From: umut.tabak at gmail.com (Umut TABAK) Date: Tue, 7 Feb 2017 23:04:09 +0100 Subject: [Paraview] mesh file with a core dump Message-ID: Dear all, 2 or 3 years ago, I coded a simple interface to the commercial finite element code ANSYS. It was working fine at that time. Mainly, it is a simple python interface which generates an ASCII *.vtk file in the legacy format, version 2.0. I tried to use the same interface tonight and with the latest version I can open the file, but if I click apply, paraview aborts with the following message. *** Error in `/home/utabak/external_programs/ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.2/paraview': free(): invalid next size (normal): 0x0000000003255440 *** Aborted (core dumped) I tried on a simpler domain to debug a bit, but the input file seems fine to me. Moreover, I can open the same vtk file in another open source mesh generator, which is quite popular, namely, Gmsh without any errors. So I am wondering the reason for this problem. I also attached the input vtk file for your reference. Any help is appreciated. BR, Umut -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: box.vtk Type: application/octet-stream Size: 6570 bytes Desc: not available URL: From bdutta at vt.edu Tue Feb 7 23:48:25 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Tue, 7 Feb 2017 23:48:25 -0500 Subject: [Paraview] Help needed: Paraview crashing with object has no attribute 'ImageResampling' Message-ID: Hi All, I am new to paraview and need help on the below. Thanks for answering them. a) I am running paraview 4.0.1 installed in ubuntu with python 2.7.6 and one of the scripts (cmdline #pvpython script_name.py) is crashing at call : sampler = paraview.simple.ImageResampling(Input=reader) ------------------log message------------------------ Traceback (most recent call last): File "png-setup.py", line 34, in sampler = paraview.simple.ImageResampling(Input=reader) AttributeError: 'module' object has no attribute 'ImageResampling' ------------------------------------------------------------ I even tried with the latest paraview but it also crashes. b) My system has NVIDIA GPU, how do I know if paraview is using GPU acceleration or its using CPU for rendering? c) Is there any pvpython commandline option to use CPU acceleration or paraview has to be compiled separately for that. BR, Bishwajit -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Wed Feb 8 01:43:24 2017 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 8 Feb 2017 06:43:24 +0000 Subject: [Paraview] mesh file with a core dump In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684379AB8C@MBX111.d.ethz.ch> Dear Umut Your cell index count is wrong. the correct numbers should be CELLS 48 368 N.B. 16*5 + 32*9 = 368 ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdutta at vt.edu Wed Feb 8 02:10:27 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Wed, 8 Feb 2017 02:10:27 -0500 Subject: [Paraview] Query on ccmake for building Paraview Message-ID: Hi All, I had the below query. Thanks to pls help out. I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I need to configure options to build with mesa and I read that this is to be done with ccmake. Now I compiled cmake 2.8.8 and 3.7.0 but I cannot see any ccmake getting compiled in bin folder. Thanks for letting me know a proper version of cmake which has ccmake. BR, Bishwajit Virginia Tech -------------- next part -------------- An HTML attachment was scrubbed... URL: From fredericperez1 at gmail.com Wed Feb 8 05:14:16 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 8 Feb 2017 11:14:16 +0100 Subject: [Paraview] Best way to make a code's output Paraview-ready Message-ID: Hi all, I am part of a development team for a scientific code, and we would like to make our code's output readable by Paraview. Unfortunately, there is no reasonable way we could have our code directly output to VTK formats for various reasons (performance, memory, etc.). Currently, the outputs are in HDF5 and have various structures: 1D to 3D vector fields, 1D to 3D scalar fields, and particle lists. Being new to Paraview and VTK, I have found three options for making our results usable: 1) Write .xmf files that maps each of our individual pieces of data, so that the XDMF reader can import them. 2) Write a plugin that will convert the HDF5 files to VTK files and read. 3) Use Programmable Sources that extract the HDF5 data directly to VTK elements. Which one would you recommend? What are their qualities, especially in terms of versatility and stability? In addition, are they particularly hard to learn? Cheers Fred From michel.rasquin at colorado.edu Wed Feb 8 05:48:38 2017 From: michel.rasquin at colorado.edu (Michel Rasquin) Date: Wed, 8 Feb 2017 10:48:38 +0000 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support In-Reply-To: References: , Message-ID: Hi Chuck, Mea culpa. I forgot to set the KNOB_MAX_WORKER_THREADS env variable in my swr tests. Sorry for this oversight. Your suspicion was right and the large virtual memory consumption was indeed due to a massive oversubscription of threads fired by swr by default. Setting KNOB_MAX_WORKER_THREADS to 1 fixed the oversubscription of threads and the memory consumption issue when the number of mpi processes is equal to the number of cores requested. I have a last question about the performance of the swr library vs the default llvmpipe library. I have found some benchmark of swr vs llvmpipe showing acceleration factor ranging from 30 to 50 depending on the number of tets (http://openswr.org/slides/SWR_Sept15.pdf). But I is not clear to me which part of this acceleration is due to a better threading of the swr library and which part is due to a potential better usage of the AVX* instructions. If I do not allow threading of swr by setting KNOB_MAX_WORKER_THREADS to 1 (basically serial swr vs serial llvmpipe), do you know which performance gain I could still expect by relying only on a potential better usage of the AVX instructions? Thanks a lot for your help. Best regards, Michel Performance: OpenSWR vs MESA LLVMpipe openswr.org Performance: OpenSWR vs MESA* LLVMpipe Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. ________________________________ From: Chuck Atkins Sent: Tuesday, February 7, 2017 10:03:50 PM To: Michel Rasquin Cc: paraview at paraview.org Subject: Re: [Paraview] Issues with PVSB 5.2 and OSMesa support Hi Michel, Indeed, I built PVSB 5.2 with the intel 2016.2.181 and intelmpi 5.1.3.181 compilers, then ran the resulting pvserver on Haswell CPU nodes (Intel E5-2680v3) which supports AVX2 instructions. So this fits exactly the known issue you mentioned in your email. Yep, that'll do it. The problem is due to a bug in the Intel compiler performing over-agressive vectorized code generation. I'm not sure if it's fixed in >= 17 or not but I definitely know it's broken in <= 16.x. GALLIUM_DRIVER=SWR is going to give you the best performance in this situation anyways though and is the recommended osmesa driver on x86_64 CPUs. Exporting the GALIIUM_DRIVER env variable to swr then leads to an interesting behavior. With the swr driver, the good news is that I can connect my pvserver built in release mode without crashing. Great! For the recollection, the llvmpipe driver compiled in release mode crashes during the client/server connection, whereas the llvmpipe driver compiled in debug mode works fine. This lines up with the issue being bad vectorization since the compiler won't be doing m,ost of those optimizations in a debug build. However, our PBS scheduling killed quickly my interactive job because the virtual memory was exhausted, which was puzzling. Increasing the number of cores requested for my job and keeping some of them idle allowed me to increase the available memory at the cost of wasted cpu resources. I suspect the problem is is a massive oversubscription of threads by swr. The default behavior of swr is to use all available CPU cores on the node. However, when running multiple MPI processes per node, they have no way of knowing about each other. So if you've got 24 cores per node and run 24 pvservers, you'll end up with 24^2 = 576 rendering threads on a nodes; not so great. You can control this with the KNOB_MAX_WORKER_THREADS environment variable. Typically you'll want to set it to the inverse of processes per node your job is running. So if yor node has 24 cores and you run 24 processes per node, then set KNOB_MAX_WORKER_THREADS to 1, but if you're running 4 processes per node, then set it to 6; you get the idea. That should address the virtual memory problem. It's a balance since typically rendering will perform better with fewer ppn and mroe threads per process, but the filters, like Contour, parallelize at the MPI level and work better with a higher ppn. You'll need to find the right balance for your use case depending on whether it's render-heaver or pipeline pricessing heavy. Would you also know if this known issue with the llvmpipe driver will be fixed of PV 5.3 (agreeing on the fact that the swr driver should be faster on intel CPU provided that it does not exhaust the memory consumption). It's actually an Intel compiler bug and not a ParaView (or even Mesa for that matter) issue, so probably not. It may be fixed in future releases of icc but I wouldn't know withotu testng it. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.jackson at bluequartz.net Wed Feb 8 07:52:33 2017 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Wed, 08 Feb 2017 07:52:33 -0500 Subject: [Paraview] Best way to make a code's output Paraview-ready In-Reply-To: References: Message-ID: <589B1491.7020409@bluequartz.net> For our project (http://www.github.com/bluequartzsoftware/simpl) we write .xdmf files that reference the hdf5 files that we natively write. We just rolled our own XDMF writer as it is just xml and we knew which of our datasets we wanted to expose in the XDMF file. The docs for the xdmf format are pretty light, especially when you want to hyperslab a dataset, but you can get through it. Just my 2 cents. -- Michael A. Jackson BlueQuartz Software, LLC [e]: mike.jackson at bluequartz.net Frederic Perez wrote: > Hi all, > > I am part of a development team for a scientific code, and we would > like to make our code's output readable by Paraview. Unfortunately, > there is no reasonable way we could have our code directly output to > VTK formats for various reasons (performance, memory, etc.). > Currently, the outputs are in HDF5 and have various structures: 1D to > 3D vector fields, 1D to 3D scalar fields, and particle lists. > > Being new to Paraview and VTK, I have found three options for making > our results usable: > 1) Write .xmf files that maps each of our individual pieces of data, > so that the XDMF reader can import them. > 2) Write a plugin that will convert the HDF5 files to VTK files and read. > 3) Use Programmable Sources that extract the HDF5 data directly to VTK elements. > > Which one would you recommend? What are their qualities, especially in > terms of versatility and stability? In addition, are they particularly > hard to learn? > > Cheers > Fred > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Wed Feb 8 08:27:30 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Wed, 8 Feb 2017 08:27:30 -0500 Subject: [Paraview] Issues with PVSB 5.2 and OSMesa support In-Reply-To: References: Message-ID: Hi Michel, Setting KNOB_MAX_WORKER_THREADS to 1 fixed the oversubscription of threads and the memory consumption issue when the number of mpi processes is equal to the number of cores requested. Great! If I do not allow threading of swr by setting KNOB_MAX_WORKER_THREADS to 1 (basically serial swr vs serial llvmpipe), do you know which performance gain I could still expect by relying only on a potential better usage of the AVX instructions? Short answer: swr is marginally faster because of instruction set optimizations but way faster because of better thread scaling. Long answer: With Mesa 11.x and 12.x, our experimental data showed similar single threaded performance between the two, however, swr in 13.x (currently deployed with 5.2) saw a significant performance increase between 20% - 100% depending on the workload. Multithreaded performance, however, is quite another story. Swr scales nearly linearly on Haswell CPUs for both geometry and pixel operations while llvmpipe scales well up to 16c for pixel operations and is entirely single-threaded for geometry shaders. Coincidentally, most actions in paraview are geometry based (volume rendering being the exception). So, in general, swr will perform better than llvmpipe by a fair amount and if using it in multi-threading mode then by a drastic amount. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Feb 8 08:51:50 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 8 Feb 2017 08:51:50 -0500 Subject: [Paraview] Query on ccmake for building Paraview In-Reply-To: References: Message-ID: <20170208135150.GC12820@megas.kitware.com> On Wed, Feb 08, 2017 at 02:10:27 -0500, Bishwajit Dutta wrote: > I had the below query. Thanks to pls help out. > > I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I need > to > configure options to build with mesa and I read that this is to be done > with ccmake. > > Now I compiled cmake 2.8.8 and 3.7.0 but I cannot see any ccmake getting > compiled in bin folder. > Thanks for letting me know a proper version of cmake which has ccmake. You need to set BUILD_CursesDialog=ON. --Ben From chuck.atkins at kitware.com Wed Feb 8 08:58:19 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Wed, 8 Feb 2017 08:58:19 -0500 Subject: [Paraview] Query on ccmake for building Paraview In-Reply-To: <20170208135150.GC12820@megas.kitware.com> References: <20170208135150.GC12820@megas.kitware.com> Message-ID: Hi Bishwajit, I believe the curses interface will get built by default if it can find ncurses so you're probably missing the ncurses development libraries. Try installing the libncurses-dev package and then re-configuring and building CMake. - Chuck On Wed, Feb 8, 2017 at 8:51 AM, Ben Boeckel wrote: > On Wed, Feb 08, 2017 at 02:10:27 -0500, Bishwajit Dutta wrote: > > I had the below query. Thanks to pls help out. > > > > I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I > need > > to > > configure options to build with mesa and I read that this is to be done > > with ccmake. > > > > Now I compiled cmake 2.8.8 and 3.7.0 but I cannot see any ccmake getting > > compiled in bin folder. > > Thanks for letting me know a proper version of cmake which has ccmake. > > You need to set BUILD_CursesDialog=ON. > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From agsmith424 at gmail.com Wed Feb 8 09:21:38 2017 From: agsmith424 at gmail.com (Andy Smith) Date: Wed, 8 Feb 2017 09:21:38 -0500 Subject: [Paraview] Rendering Backend OpenGL2 & PV 5.2.0-RC4 & SurfaceLic --> Problem... In-Reply-To: References: <84a5a6aa-326f-a1ff-7789-28204a0ee502@DLR.de> Message-ID: Ken, I've attached a small example file and script that demonstrates the problem. The example dataset is a multiblock unstructured grid with two blocks. The script attempts to create two images of slices through the dataset. At the first slice position data from both blocks are in the slice. At the second slice position only data from one block is part of the slice. This works in serial and parallel (two processors) using pvbatch when not using surface LIC and in serial when using surface LIC with the latest ParaView from the git repo. In parallel, the surface LIC hangs when creating the second image. This script works in parallel with surface LIC when using version 4.4.0. As an aside, I call the function to ensure that the surface LIC plugin is loaded at the beginning of the script. When I do this I get warnings about "Replacing existing representation for key: Surface LIC". I assume this is because in my build I turned on the option to load the surface LIC plugin by default. Is there a way in Python to check if a plugin is loaded and skip this step if that is the case? Let me know if I can provide any additional information. -Andy On Tue, Feb 7, 2017 at 8:32 AM, Ken Martin wrote: > Thanks Andy, just to make sure I understand the issue. Is the case that > one processor has no data, or is it that it has data, but it is outside the > current view? > > Thanks > Ken > > On Thu, Feb 2, 2017 at 5:14 PM, Andy Smith wrote: > >> I've tested this with the latest ParaView and it does seem to run much >> faster. >> I am having a problem when running in parallel though. If one processor >> does not have anything to display, the rendering hangs. >> Related to that, what routine actually calls >> vtkCompositeLICHelper::RenderPiece? >> The process that does not have anything to display never gets to that >> function but the other processes do. In that function there are MPI calls >> where the rendering hangs. >> >> As a reply to Chuck: I can use EGL in some instances but unfortunately >> not all of our machine have GPUs so software rendering is still required. >> >> Thanks again for all the help. >> >> On Mon, Jan 23, 2017 at 12:45 PM, Ken Martin >> wrote: >> >>> There is a VTK topic now that should fix this regression. With this >>> change OpenGL2 LIC seems to run much faster (at least 10X). >>> >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/2419 >>> >>> Hopefully it will test out OK and get merged into VTK and then merged >>> into ParaView. >>> >>> On Mon, Dec 12, 2016 at 11:38 AM, Andy Smith >>> wrote: >>> >>>> Ken, >>>> >>>> You are correct in your assumption about my dataset; it is multiblock >>>> unstructured data. Adding a MergeBlocks filter to my slice does improve >>>> the 5.2.0 with OpenGL2 significantly. >>>> With that change the performance of 5.2.0 with OpenGL2 is on the same >>>> order of magnitude as 5.2.0 with OpenGL and with 4.4.0, though the 5.2.0 >>>> variants are still slower than 4.4.0. >>>> >>>> I realized after posting that my comparison is not exactly apples to >>>> apples - my build of 5.2.0 required updates to mesa (13.0.0) compared with >>>> the version I used for 4.4.0 (11.2.0). >>>> I will recompile 4.4.0 with the same mesa version I used with 5.2.0 and >>>> report back. >>>> >>>> Thank you for your input. >>>> >>>> -Andy >>>> >>>> On Fri, Dec 9, 2016 at 3:44 PM, Ken Martin >>>> wrote: >>>> >>>>> I have not had time to look into this, but my quick guess is that you >>>>> have a multiblock dataset with a lot of blocks. Can you try merging the >>>>> blocks all together somehow into one block and see if the rendering speed >>>>> improves? >>>>> >>>>> On Tue, Nov 15, 2016 at 5:35 AM, Stefan Melber >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> i have a problem which is there in all RCs (1-4) of current ParaView: >>>>>> if i compile the RenderingBackend to "OpenGL2" and use SurfaceLic the >>>>>> visualization time goes up from a few seconds (with "OpenGL") to many >>>>>> minutes and the memory consumption from a few GByte to approx 100 GByte. >>>>>> Switching back to OpenGL any thing is fine. Without SurfaceLIC the OpenGL2 >>>>>> works although fine for me. >>>>>> >>>>>> Has any one tested OpenGL2 with SurfaceLIC-Plugin the last time and >>>>>> has (the same) problems? >>>>>> >>>>>> o Kernel 4.7.6-1 / x86-64 >>>>>> o Quadro 4000 >>>>>> o NVidia driver v367.57 >>>>>> o PV 5.2.0 RC1 - RC4 >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Stefan >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> >>>>> >>>> >>> >>> >>> -- >>> 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. >>> >> >> > > > -- > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mixed.xmf Type: application/octet-stream Size: 4601 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: slicing_test.py Type: application/x-download Size: 2719 bytes Desc: not available URL: From agsmith424 at gmail.com Wed Feb 8 09:24:46 2017 From: agsmith424 at gmail.com (Andy Smith) Date: Wed, 8 Feb 2017 09:24:46 -0500 Subject: [Paraview] Best way to make a code's output Paraview-ready In-Reply-To: <589B1491.7020409@bluequartz.net> References: <589B1491.7020409@bluequartz.net> Message-ID: I will second that recommendation. I've used XDMF in this way (writing the HDF5 and XML parts manually) with multiple CFD codes. You may also want to checkout the XDMF API as I'm sure they've made improvements since I started using XDMF 6 or 7 years ago. -Andy On Wed, Feb 8, 2017 at 7:52 AM, Michael Jackson wrote: > For our project (http://www.github.com/bluequartzsoftware/simpl) we write > .xdmf files that reference the hdf5 files that we natively write. We just > rolled our own XDMF writer as it is just xml and we knew which of our > datasets we wanted to expose in the XDMF file. The docs for the xdmf format > are pretty light, especially when you want to hyperslab a dataset, but you > can get through it. > > Just my 2 cents. > -- > Michael A. Jackson > BlueQuartz Software, LLC > [e]: mike.jackson at bluequartz.net > > > > Frederic Perez wrote: > >> Hi all, >> >> I am part of a development team for a scientific code, and we would >> like to make our code's output readable by Paraview. Unfortunately, >> there is no reasonable way we could have our code directly output to >> VTK formats for various reasons (performance, memory, etc.). >> Currently, the outputs are in HDF5 and have various structures: 1D to >> 3D vector fields, 1D to 3D scalar fields, and particle lists. >> >> Being new to Paraview and VTK, I have found three options for making >> our results usable: >> 1) Write .xmf files that maps each of our individual pieces of data, >> so that the XDMF reader can import them. >> 2) Write a plugin that will convert the HDF5 files to VTK files and read. >> 3) Use Programmable Sources that extract the HDF5 data directly to VTK >> elements. >> >> Which one would you recommend? What are their qualities, especially in >> terms of versatility and stability? In addition, are they particularly >> hard to learn? >> >> Cheers >> Fred >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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/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 sujin.philip at kitware.com Wed Feb 8 09:58:45 2017 From: sujin.philip at kitware.com (Sujin Philip) Date: Wed, 8 Feb 2017 09:58:45 -0500 Subject: [Paraview] Help needed: Paraview crashing with object has no attribute 'ImageResampling' In-Reply-To: References: Message-ID: Hi Bishwajit, The filter "ImageResampling" is not available in version 4.0.1. It was introduced in 4.2.0. So you will have to get a newer version of ParaView. You can find ParaView binaries for Linux here: http://www.paraview.org/download/. Since 5.1, "ImageResampling" is deprecated and "ResampleToImage" is its replacement. Please refer to this page for more info about the new filter: https://blog.kitware.com/dataset-resampling-filters/ You can find the driver ParaView is using for rendering in the Help>About menu. The binaries provided in the website mentioned above have support for mesa for rendering using CPU using the --mesa-llvm flag. Please refer to the page for more info: https://blog.kitware.com/paraview-5-0-0-available-for-download/ Hope this helps. Thanks Sujin On Tue, Feb 7, 2017 at 11:48 PM, Bishwajit Dutta wrote: > Hi All, > > I am new to paraview and need help on the below. Thanks for answering them. > > a) > I am running paraview 4.0.1 installed in ubuntu with python 2.7.6 and one > of the scripts (cmdline #pvpython script_name.py) is crashing at call : > sampler = paraview.simple.ImageResampling(Input=reader) > > ------------------log message------------------------ > > Traceback (most recent call last): > File "png-setup.py", line 34, in > sampler = paraview.simple.ImageResampling(Input=reader) > AttributeError: 'module' object has no attribute 'ImageResampling' > ------------------------------------------------------------ > > I even tried with the latest paraview but it also crashes. > > b) My system has NVIDIA GPU, how do I know if paraview is using GPU > acceleration > or its using CPU for rendering? > > c) Is there any pvpython commandline option to use CPU acceleration or > paraview has to be compiled separately for that. > > > > BR, > Bishwajit > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 samuelkey at bresnan.net Wed Feb 8 10:32:30 2017 From: samuelkey at bresnan.net (Samuel Key) Date: Wed, 8 Feb 2017 08:32:30 -0700 Subject: [Paraview] Best way to make a code's output Paraview-ready In-Reply-To: References: Message-ID: Fred, Useful simulation results formats for ParaView depend on the size of the datum set. Here are two formats. For medium to very large massively parallel datum sets, the ExodusII format works. The ExodusII format is binary, current, and well supported in ParaView. It is a no-cost, 3rd-party product ( https://github.com/gsjaardema/seacas ). Another format that works well is the EnSight 'Gold' binary format. Apart from user-defined cell and point numerical identifiers that to me do not appear to be supported by ParaView, it can easily handle 10^6 finite element workstation models. It is well documented by the EnSight organization. For example, ( http://www-vis.lbl.gov/NERSC/Software/ensight/doc/OnlineHelp/UM-C11.pdf ). (The EnSight post-processor is a commercial product that is widely used and your simulation results can then be read by EnSight users as well.) The format supports n-vertex polygons and polyhedrons where n=(1,2,3,...). The EnSight format has a PART-construct that the ParaView Extract Block filter allows one to display any combination of PART's. I have attached an example of the *.case ASCII-formatted meta file that the EnSight format uses to describe the file-set containing the binary data. Hope this helps in your search for a suitable simulation results format for ParaView. Sam Key On 2/8/2017 3:14 AM, Frederic Perez wrote: > Hi all, > > I am part of a development team for a scientific code, and we would > like to make our code's output readable by Paraview. Unfortunately, > there is no reasonable way we could have our code directly output to > VTK formats for various reasons (performance, memory, etc.). > Currently, the outputs are in HDF5 and have various structures: 1D to > 3D vector fields, 1D to 3D scalar fields, and particle lists. > > Being new to Paraview and VTK, I have found three options for making > our results usable: > 1) Write .xmf files that maps each of our individual pieces of data, > so that the XDMF reader can import them. > 2) Write a plugin that will convert the HDF5 files to VTK files and read. > 3) Use Programmable Sources that extract the HDF5 data directly to VTK elements. > > Which one would you recommend? What are their qualities, especially in > terms of versatility and stability? In addition, are they particularly > hard to learn? > > Cheers > Fred > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 -------------- FORMAT type: ensight gold GEOMETRY model: 1 1 fmaego.data.geom change_coords_only VARIABLE vector per node: 1 1 Displacement fmaego.data.ndis vector per node: 1 1 Velocity fmaego.data.nvel vector per node: 1 1 Acceleration fmaego.data.nacc scalar per element: 1 1 Material fmaego.data.emat scalar per element: 1 1 Material-State fmaego.data.esta scalar per element: 1 1 Pressure fmaego.data.eprs scalar per element: 1 1 Bulk-Strain fmaego.data.elnv scalar per element: 1 1 Strain-Energy-Density fmaego.data.esed scalar per element: 1 1 Effective-Stress fmaego.data.edev vector per element: 1 1 Stress*Vel fmaego.data.estv tensor symm per element: 1 1 Stress fmaego.data.estr TIME time set: 1 number of steps: 7 time values: 1.255489315792E-08 2.400086267127E-04 4.800053377343E-04 7.200036715849E-04 9.600081684283E-04 1.200002971217E-03 1.440003995610E-03 FILE file set: 1 number of steps: 7 From info at feacluster.com Wed Feb 8 10:15:36 2017 From: info at feacluster.com (Faraz Hussain) Date: Wed, 08 Feb 2017 10:15:36 -0500 Subject: [Paraview] Installing paraviewweb on a raspberry pi Message-ID: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> I want to be able to manipulate vtk file on my raspberry pi via a web browser anywhere in the world. I believe I need to install paraviewweb and do some reconfiguration of apache and the virtual hosts? Unfortunately, I am not a guru of Linux. So before I attempt it all, is it even possible to do this on a raspberry pi? I am using raspian . From sebastien.jourdain at kitware.com Wed Feb 8 11:25:30 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 8 Feb 2017 09:25:30 -0700 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> Message-ID: Wow, I'm not an expert on raspberry pi but it should be possible. BUT, (and it is a big but) you need some graphics capability for ParaView or good CPUs if you don't have a GPU. Or the rendering will be really slow. The quicker test you can do, is to build ParaView (without Qt) and try to run Visualizer with that ParaView in the command line to see what performance you are getting. If that's reasonable, then all the network setup should be "trivial". ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install Visualizer: https://kitware.github.io/visualizer/ Good luck, Seb On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain wrote: > I want to be able to manipulate vtk file on my raspberry pi via a web > browser anywhere in the world. I believe I need to install paraviewweb and > do some reconfiguration of apache and the virtual hosts? Unfortunately, I > am not a guru of Linux. So before I attempt it all, is it even possible to > do this on a raspberry pi? I am using raspian . > > _______________________________________________ > 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 sebastien.jourdain at kitware.com Wed Feb 8 11:33:52 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 8 Feb 2017 09:33:52 -0700 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> Message-ID: This might give you some information for building ParaView. => https://blog.kitware.com/raspberry-pi-likes-vtk/ On Wed, Feb 8, 2017 at 9:25 AM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Wow, > > I'm not an expert on raspberry pi but it should be possible. > BUT, (and it is a big but) you need some graphics capability for ParaView > or good CPUs if you don't have a GPU. > Or the rendering will be really slow. > > The quicker test you can do, is to build ParaView (without Qt) and try to > run Visualizer with that ParaView in the command line to see what > performance you are getting. If that's reasonable, then all the network > setup should be "trivial". > > ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install > Visualizer: https://kitware.github.io/visualizer/ > > Good luck, > > Seb > > On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain wrote: > >> I want to be able to manipulate vtk file on my raspberry pi via a web >> browser anywhere in the world. I believe I need to install paraviewweb and >> do some reconfiguration of apache and the virtual hosts? Unfortunately, I >> am not a guru of Linux. So before I attempt it all, is it even possible to >> do this on a raspberry pi? I am using raspian . >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 fredericperez1 at gmail.com Wed Feb 8 12:09:34 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 8 Feb 2017 18:09:34 +0100 Subject: [Paraview] Transform time to an additional dimension of the grid Message-ID: Hi, I have a 2D regularly-spaced rectangular grid on which node values vary over time (the grid does not change). Note that this grid has many many scalar fields at the nodes. Not just one. I would like to 1) extract only one of the attributes (one scalar field) 2) append all the grids from each timestep together in order to form a 3D grid 3) plot as a usual "volume" or "surface" and apply slices, thresholds, etc. For now, I have tried to "Group timesteps" (I don't understand what it does) and "Plot selection over time" (it only provides point-by-point plotting on line graphs). Is there a solution? Cheers Fred From daibane at sandia.gov Wed Feb 8 12:44:49 2017 From: daibane at sandia.gov (Ibanez, Daniel Alejandro) Date: Wed, 8 Feb 2017 17:44:49 +0000 Subject: [Paraview] Point Data Threshold misses Cells In-Reply-To: <1486575653810.9528@sandia.gov> References: <1486575653810.9528@sandia.gov> Message-ID: <1486575889062.14123@sandia.gov> Hello, I've got an Unstructured Mesh with a Point Data field, and I'm trying to look at the area with the highest value. Unfortunately, it looks like when I use the Threshold filter on this field, it only selects cells for which *all* adjacent Points match the threshold, and in my case only a single Point has this anomalous value. Is there a way to tell Threshold to select cells for which *any* adjacent Points match the threshold ? I'm using Paraview 5.2.0-RC1 Thanks, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Feb 8 13:20:22 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 8 Feb 2017 13:20:22 -0500 Subject: [Paraview] Point Data Threshold misses Cells In-Reply-To: <1486575889062.14123@sandia.gov> References: <1486575653810.9528@sandia.gov> <1486575889062.14123@sandia.gov> Message-ID: Hi Dan, You an uncheck the All Scalars option in the Threshold filter and that may give you want you want. Other options include using the Spreadsheet view and sorting by the column of your interested array (selection in the Spreadsheet view is linked with the 3D view). You can also use the Find Data tool (under the Edit menu). Under Find select Points and then the array you want should be available in the second row of widgets in that window. Next to that you'll see a "is max" option in the dropd-down widget. Then you can click on Run Selection Query to select the points meeting that criterion. Let us know if this doesn't give you what you want. Cheers, Andy On Wed, Feb 8, 2017 at 12:44 PM, Ibanez, Daniel Alejandro < daibane at sandia.gov> wrote: > Hello, > > > I've got an Unstructured Mesh with a Point Data field, > > and I'm trying to look at the area with the highest value. > > Unfortunately, it looks like when I use the Threshold filter > > on this field, it only selects cells for which *all* adjacent > > Points match the threshold, and in my case only a single > > Point has this anomalous value. > > Is there a way to tell Threshold to select cells for which > > *any* adjacent Points match the threshold ? > > > I'm using Paraview 5.2.0-RC1 > > > Thanks, > > Dan > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 daibane at sandia.gov Wed Feb 8 13:23:56 2017 From: daibane at sandia.gov (Ibanez, Daniel Alejandro) Date: Wed, 8 Feb 2017 18:23:56 +0000 Subject: [Paraview] [EXTERNAL] Re: Point Data Threshold misses Cells In-Reply-To: References: <1486575653810.9528@sandia.gov> <1486575889062.14123@sandia.gov>, Message-ID: <1486578236837.3202@sandia.gov> Perfect ! I think "All Scalars" is what I need.? ________________________________ From: Andy Bauer Sent: Wednesday, February 8, 2017 11:20 AM To: Ibanez, Daniel Alejandro Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Point Data Threshold misses Cells Hi Dan, You an uncheck the All Scalars option in the Threshold filter and that may give you want you want. Other options include using the Spreadsheet view and sorting by the column of your interested array (selection in the Spreadsheet view is linked with the 3D view). You can also use the Find Data tool (under the Edit menu). Under Find select Points and then the array you want should be available in the second row of widgets in that window. Next to that you'll see a "is max" option in the dropd-down widget. Then you can click on Run Selection Query to select the points meeting that criterion. Let us know if this doesn't give you what you want. Cheers, Andy On Wed, Feb 8, 2017 at 12:44 PM, Ibanez, Daniel Alejandro > wrote: Hello, I've got an Unstructured Mesh with a Point Data field, and I'm trying to look at the area with the highest value. Unfortunately, it looks like when I use the Threshold filter on this field, it only selects cells for which *all* adjacent Points match the threshold, and in my case only a single Point has this anomalous value. Is there a way to tell Threshold to select cells for which *any* adjacent Points match the threshold ? I'm using Paraview 5.2.0-RC1 Thanks, Dan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 fredericperez1 at gmail.com Wed Feb 8 15:38:52 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 8 Feb 2017 21:38:52 +0100 Subject: [Paraview] XDMF makes paraview crash with JOIN Message-ID: Hi all, I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. 0.0 0.0 0.3 0.06 mystuff.h5:/0000000002/By mystuff.h5:/0000000007/By mystuff.h5:/0000000012/By mystuff.h5:/0000000017/By mystuff.h5:/0000000022/By mystuff.h5:/0000000027/By mystuff.h5:/0000000032/By mystuff.h5:/0000000037/By mystuff.h5:/0000000042/By mystuff.h5:/0000000047/By However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". Is there a reason for this? Am I doing something wrong? Is there a workaround? Cheers Fred From andrew.j.burns35.ctr at mail.mil Wed Feb 8 16:28:02 2017 From: andrew.j.burns35.ctr at mail.mil (Burns, Andrew J CTR USARMY RDECOM ARL (US)) Date: Wed, 8 Feb 2017 21:28:02 +0000 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: Are you using the Xdmf2 or Xdmf3 reader? 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 Frederic Perez Sent: Wednesday, February 08, 2017 3:39 PM To: paraview at paraview.org Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with JOIN 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. ---- Hi all, I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. 0.0 0.0 0.3 0.06 mystuff.h5:/0000000002/By mystuff.h5:/0000000007/By mystuff.h5:/0000000012/By mystuff.h5:/0000000017/By mystuff.h5:/0000000022/By mystuff.h5:/0000000027/By mystuff.h5:/0000000032/By mystuff.h5:/0000000037/By mystuff.h5:/0000000042/By mystuff.h5:/0000000047/By However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". Is there a reason for this? Am I doing something wrong? Is there a workaround? Cheers Fred _______________________________________________ Powered by Caution-www.kitware.com Visit other Kitware open-source projects at 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 Search the list archives at: Caution-http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview From fredericperez1 at gmail.com Wed Feb 8 16:50:17 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 8 Feb 2017 22:50:17 +0100 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply". Fred 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) : > Are you using the Xdmf2 or Xdmf3 reader? > > 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 Frederic Perez > Sent: Wednesday, February 08, 2017 3:39 PM > To: paraview at paraview.org > Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with JOIN > > 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. > > > > > ---- > > Hi all, > > I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. > > > > > TopologyType="2DCoRectMesh" Dimensions="21 10"/> > > Dimensions="2">0.0 0.0 > Dimensions="2">0.3 0.06 > > > Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10"> > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000002/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000007/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000012/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000017/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000022/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000027/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000032/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000037/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000042/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000047/By > > > > > > > However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". > > Is there a reason for this? Am I doing something wrong? Is there a workaround? > > Cheers > Fred > _______________________________________________ > Powered by Caution-www.kitware.com > > Visit other Kitware open-source projects at 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 > > Search the list archives at: Caution-http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview From andrew.j.burns35.ctr at mail.mil Wed Feb 8 16:54:55 2017 From: andrew.j.burns35.ctr at mail.mil (Burns, Andrew J CTR USARMY RDECOM ARL (US)) Date: Wed, 8 Feb 2017 21:54:55 +0000 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: I think that is because Xdmf3 uses different syntax for concatenation. Try using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader. -Andrew Burns -----Original Message----- From: Frederic Perez [mailto:fredericperez1 at gmail.com] Sent: Wednesday, February 08, 2017 4:50 PM To: Burns, Andrew J CTR USARMY RDECOM ARL (US) Cc: paraview at paraview.org Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash with JOIN I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply". Fred 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) : > Are you using the Xdmf2 or Xdmf3 reader? > > 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 > Frederic Perez > Sent: Wednesday, February 08, 2017 3:39 PM > To: paraview at paraview.org > Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with > JOIN > > 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. > > > > > ---- > > Hi all, > > I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. > > > > > TopologyType="2DCoRectMesh" Dimensions="21 10"/> > > Dimensions="2">0.0 0.0 > Dimensions="2">0.3 0.06 > > > Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10"> > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000002/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000007/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000012/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000017/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000022/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000027/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000032/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000037/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000042/By > Precision="8" Dimensions="21" > Format="HDF">mystuff.h5:/0000000047/By > > > > > > > However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". > > Is there a reason for this? Am I doing something wrong? Is there a workaround? > > Cheers > Fred > _______________________________________________ > Powered by Caution-www.kitware.com > > Visit other Kitware open-source projects at > 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 > > Search the list archives at: > Caution-http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview From fredericperez1 at gmail.com Wed Feb 8 17:24:21 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 8 Feb 2017 23:24:21 +0100 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: I must have done something wrong in my previous attempt with Xdmf3, because it no longer crashes. Note that it works even without your suggestion, as the JOIN() syntax works. Now the problem is that, when I click "Apply", I get the following error: "Failed to locate selected scalars. Will use image scalars by default No scalar values found for texture input!" Note that the same exact file works with Xdmf instead of Xdmf3. Fred 2017-02-08 22:54 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) : > I think that is because Xdmf3 uses different syntax for concatenation. Try using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader. > > -Andrew Burns > > -----Original Message----- > From: Frederic Perez [mailto:fredericperez1 at gmail.com] > Sent: Wednesday, February 08, 2017 4:50 PM > To: Burns, Andrew J CTR USARMY RDECOM ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash with JOIN > > I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply". > > Fred > > 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) > : >> Are you using the Xdmf2 or Xdmf3 reader? >> >> 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 >> Frederic Perez >> Sent: Wednesday, February 08, 2017 3:39 PM >> To: paraview at paraview.org >> Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with >> JOIN >> >> 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. >> >> >> >> >> ---- >> >> Hi all, >> >> I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. >> >> >> >> >> > TopologyType="2DCoRectMesh" Dimensions="21 10"/> >> >> > Dimensions="2">0.0 0.0 >> > Dimensions="2">0.3 0.06 >> >> >> > Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10"> >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000002/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000007/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000012/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000017/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000022/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000027/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000032/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000037/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000042/By >> > Precision="8" Dimensions="21" >> Format="HDF">mystuff.h5:/0000000047/By >> >> >> >> >> >> >> However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". >> >> Is there a reason for this? Am I doing something wrong? Is there a workaround? >> >> Cheers >> Fred >> _______________________________________________ >> Powered by Caution-www.kitware.com >> >> Visit other Kitware open-source projects at >> 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 >> >> Search the list archives at: >> Caution-http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> Caution-http://public.kitware.com/mailman/listinfo/paraview From mathieu.westphal at kitware.com Wed Feb 8 21:48:52 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 9 Feb 2017 03:48:52 +0100 Subject: [Paraview] Support for accentuated and special characters for filepath in ParaView Message-ID: Hello ParaView never supported opening file or directory with special character in their name. Some non-english native speaker have been requesting this for a long time, and we are happy to announce that we now have support for it. It works well in the different system we have been able to test it on, but if anybody can try on other type of alphabet (Chinese, Russian, Korean), please test it, especially on windows. It has just been merged into ParaView master, so be sure to use the last git master of ParaView for testing this. Mathieu Westphal PS : I've CC this mail to a few people who have expressed direct interest to this feature. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Melber at DLR.de Thu Feb 9 04:04:14 2017 From: Stefan.Melber at DLR.de (Stefan Melber) Date: Thu, 9 Feb 2017 10:04:14 +0100 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... Message-ID: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> Hi, during visualization of vortices i found a bug (or feature?) of ParaView: running the case in serial mode the results look fine. However, doing the same in parallel mode (e.g. 8 cores) the picture looks "ugly". Has anyone seen such an effect running in parallel? I am using the current version (v5.2.0) on a Linux 64bit machine with a Quadro 4000 graphics card. Attached there are two pics showing the effect, a picture of the used pipeline and the restart file... The test-data can be send to you for testing - i just need a email-address to send it to. Best regards, Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: pv.png Type: image/png Size: 47368 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rstern_test3.pvsm.zip Type: application/zip Size: 56104 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ser.png Type: image/png Size: 249261 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: par.png Type: image/png Size: 383693 bytes Desc: not available URL: From bdutta at vt.edu Thu Feb 9 04:43:41 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Thu, 9 Feb 2017 04:43:41 -0500 Subject: [Paraview] Query on ccmake for building Paraview In-Reply-To: References: <20170208135150.GC12820@megas.kitware.com> Message-ID: Chuck and Ben, Thank you for responses. I did the below as per your suggestion for cmake 2.8.8 but still I am facing compilation problems. ?1) set BUILD_CursesDialog=ON. 2) installed ? libncurses5-dev 3) Installed qt4 then got compilation error: --------------------------------------------------- loading initial cache file /home/ubuntu/Paraview/cmake-2.8.8/Bootstrap.cmk/InitialCacheFlags.cmake Curses libraries were not found. Curses GUI for CMake will not be built. -- Enable ninja generator. -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found. -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found. -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found. -- Found Qt4: /usr/bin/qmake (found version "4.8.6") -- Performing Test QT4_WORKS -- Performing Test QT4_WORKS - Success CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: CURSES_CURSES_H_PATH used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source used as include directory in directory /home/ubuntu/Paraview/cmake-2.8.8/Source -- Configuring incomplete, errors occurred! --------------------------------------------- Error when bootstrapping CMake: Problem while running initial CMake --------------------------------------------- ---------------------------------------------------- Also with cmake 2.8.8 I am planning to build Paraview 4.2.0 for ARM processor with ubuntu . Do you see any potential problem with this? Thank you. BR, Bishwajit Virginia Tech ================================================================================================ On Wed, Feb 8, 2017 at 8:58 AM, Chuck Atkins wrote: > Hi Bishwajit, > > I believe the curses interface will get built by default if it can find > ncurses so you're probably missing the ncurses development libraries. Try > installing the > ?? > libncurses-dev package and then re-configuring and building CMake. > > - Chuck > > On Wed, Feb 8, 2017 at 8:51 AM, Ben Boeckel > wrote: > >> On Wed, Feb 08, 2017 at 02:10:27 -0500, Bishwajit Dutta wrote: >> > I had the below query. Thanks to pls help out. >> > >> > I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I >> need >> > to >> > configure options to build with mesa and I read that this is to be done >> > with ccmake. >> > >> > Now I compiled cmake 2.8.8 and 3.7.0 but I cannot see any ccmake getting >> > compiled in bin folder. >> > Thanks for letting me know a proper version of cmake which has ccmake. >> >> You need to >> ?? >> set BUILD_CursesDialog=ON. >> >> --Ben >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.rasquin at colorado.edu Thu Feb 9 05:08:36 2017 From: michel.rasquin at colorado.edu (Michel Rasquin) Date: Thu, 9 Feb 2017 10:08:36 +0000 Subject: [Paraview] PVSB 5.2: missing modules and plugins after "make install" Message-ID: Hi everyone, I could successfully build and run (to some extend) PVSB 5.2 (thanks Andy and Chuck for your help!) but I have now noticed an issue with the installation of the PVSB project. Concretely, "make install" in the PVSB 5.2 build directory does not install properly all the expected modules and plugins (SurfaceLIC.so being a good example). All plugins are correctly built and available in my build directory "my_build_directory/install/lib/paraview-5.2" (for instance libSurfaceLIC.so) However, there are missing in my install directory "my_install_directory/lib/paraview-5.2" after "make install". When I connect the pvserver located in "my_install_directory/bin/pvserver" to my client, only one plugin is present in the plugin manager on the remote side under the tools tab, whereas the client include the usual list. The same operation using the pvserver located in "my_build_directory/install/bin/pvserver" shows all expected plugins on both the client and server side. Andy proposed to run a small test which illustrates further the issue with a missing module: > cat test.py from paraview.simple import * w = Wavelet() Show() Render() > mpirun -np 2 my_build_directory/install/bin/pvbatch -display :0.0 test.py returns normally whereas pvbatch from the install directory returns this error: > mpirun -np 2 my_install_directory/bin/pvbatch -display :0.0 test.py Error: Could not import vtkCommonComputationalGeometry Traceback (most recent call last): File "test.py", line 1, in from paraview.simple import * File "my_install_directory/lib/python2.7/site-packages/paraview/simple.py", line 43, in from paraview import servermanager File "my_install_directory/lib/python2.7/site-packages/paraview/servermanager.py", line 53, in from paraview import vtk File "my_install_directory/lib/python2.7/site-packages/paraview/vtk/__init__.py", line 7, in from paraview.vtk.vtkCommonCore import * File "/my_install_directory/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", line 9, in from vtkCommonCorePython import * ImportError: No module named vtkCommonCorePython The current sha key of my PVSB 5.2 source directory is 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16 (Jan 31). Please let me know if I am missing something here. Note also that this "make install" issue is not present for the PV 5.2 project but only for the PVSB 5.2 project. Thank you for your help. Best regards, Michel -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Feb 9 08:18:23 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 9 Feb 2017 08:18:23 -0500 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... In-Reply-To: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> References: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> Message-ID: That's odd. Stefan, can you send me the dataset please? I'll have it looked into. Thanks Utkarsh On Thu, Feb 9, 2017 at 4:04 AM, Stefan Melber wrote: > Hi, > > > during visualization of vortices i found a bug (or feature?) of ParaView: > running the case in serial mode the results look fine. However, doing the > same in parallel mode (e.g. 8 cores) the picture looks "ugly". Has anyone > seen such an effect running in parallel? I am using the current version > (v5.2.0) on a Linux 64bit machine with a Quadro 4000 graphics card. > > Attached there are two pics showing the effect, a picture of the used > pipeline and the restart file... > > The test-data can be send to you for testing - i just need a email-address > to send it to. > > Best regards, > > Stefan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Feb 9 09:26:05 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 9 Feb 2017 09:26:05 -0500 Subject: [Paraview] Problem with exporting spreadsheet view Message-ID: Hello all, I am using Paraview to process data from a simulation output in the Exodus II format. I create an IntegrateVariables object, then put it in a PlotSelectionOverTime object so I have the integrated values at each time step. At this point everything seems fine but, when I choose to Export Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) entry, the data sudden cuts out. The two images attached show what happens. 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: InParaview.PNG Type: image/png Size: 68873 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Exported.PNG Type: image/png Size: 72712 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Feb 9 11:03:20 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 9 Feb 2017 11:03:20 -0500 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... In-Reply-To: References: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> Message-ID: Stefan, Attached is a fixed state file. Since the file didn't have ghost-cell information, the filters like "Compute Derivatives" didn't produce correct result at the process boundary cells. By putting a "Ghost Cell Generator" filter in the pipeline, one can address that issue. Utkarsh On Thu, Feb 9, 2017 at 8:18 AM, Utkarsh Ayachit wrote: > That's odd. Stefan, can you send me the dataset please? I'll have it > looked into. > > Thanks > Utkarsh > > On Thu, Feb 9, 2017 at 4:04 AM, Stefan Melber > wrote: > >> Hi, >> >> >> during visualization of vortices i found a bug (or feature?) of ParaView: >> running the case in serial mode the results look fine. However, doing the >> same in parallel mode (e.g. 8 cores) the picture looks "ugly". Has anyone >> seen such an effect running in parallel? I am using the current version >> (v5.2.0) on a Linux 64bit machine with a Quadro 4000 graphics card. >> >> Attached there are two pics showing the effect, a picture of the used >> pipeline and the restart file... >> >> The test-data can be send to you for testing - i just need a >> email-address to send it to. >> >> Best regards, >> >> Stefan >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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: rstern_test3.fixed-for-parallel.pvsm.zip Type: application/zip Size: 58004 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pipeline.png Type: image/png Size: 27896 bytes Desc: not available URL: From ben.boeckel at kitware.com Thu Feb 9 11:04:29 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 9 Feb 2017 11:04:29 -0500 Subject: [Paraview] Query on ccmake for building Paraview In-Reply-To: References: <20170208135150.GC12820@megas.kitware.com> Message-ID: <20170209160429.GA3588@megas.kitware.com> On Thu, Feb 09, 2017 at 04:43:41 -0500, Bishwajit Dutta wrote: > CMake Error: The following variables are used in this project, but they are > set to NOTFOUND. > Please set them or make sure they are set and tested correctly in the CMake > files: > CURSES_CURSES_H_PATH > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source > used as include directory in directory > /home/ubuntu/Paraview/cmake-2.8.8/Source You're missing the libcurses5-dev package. > -- Configuring incomplete, errors occurred! > --------------------------------------------- > Error when bootstrapping CMake: > Problem while running initial CMake > --------------------------------------------- > ---------------------------------------------------- > > Also with cmake 2.8.8 I am planning to build Paraview 4.2.0 for ARM > processor with ubuntu . Do you see any potential problem with this? ParaView does not receive regular testing on ARM platforms even today, and certainly not in the 4.2.0 days (VTK does, but it is for iOS and Android mainly). --Ben From utkarsh.ayachit at kitware.com Thu Feb 9 11:08:17 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 9 Feb 2017 11:08:17 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: Sounds like a bug. If can provide example dataset and steps to reproduce that will make it easier to track it down. Thanks, Utkarsh On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: > Hello all, > > I am using Paraview to process data from a simulation output in the Exodus > II format. I create an IntegrateVariables object, then put it in a > PlotSelectionOverTime object so I have the integrated values at each time > step. At this point everything seems fine but, when I choose to Export > Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) > entry, the data sudden cuts out. > > The two images attached show what happens. > > 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 Feb 9 11:27:38 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 9 Feb 2017 11:27:38 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: Utkarsh et al., Here are the files. The data file (SteadyState_out.e) is particularly large ~500 MB. https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e Regards, John R. Haase jhaase1 at nd.edu On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Sounds like a bug. If can provide example dataset and steps to reproduce > that will make it easier to track it down. > > Thanks, > Utkarsh > > On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: > >> Hello all, >> >> I am using Paraview to process data from a simulation output in the >> Exodus II format. I create an IntegrateVariables object, then put it in a >> PlotSelectionOverTime object so I have the integrated values at each time >> step. At this point everything seems fine but, when I choose to Export >> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >> entry, the data sudden cuts out. >> >> The two images attached show what happens. >> >> 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 ken.martin at kitware.com Thu Feb 9 11:47:44 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 9 Feb 2017 11:47:44 -0500 Subject: [Paraview] Rendering Backend OpenGL2 & PV 5.2.0-RC4 & SurfaceLic --> Problem... In-Reply-To: References: <84a5a6aa-326f-a1ff-7789-28204a0ee502@DLR.de> Message-ID: Thanks so much for the example. I have a VTK topic that I believe will fix the issue here: https://gitlab.kitware.com/vtk/vtk/merge_requests/2463 It fails three of the current paraview LIC tests but with images that still look reasonable (although one looks dark to me). The changes only impact two files. Your example no longer hangs with these changes. If you have a chance to test it on your real data or other cases that would help me feel more confident about the change. Thanks Ken On Wed, Feb 8, 2017 at 9:21 AM, Andy Smith wrote: > Ken, > > I've attached a small example file and script that demonstrates the > problem. > > The example dataset is a multiblock unstructured grid with two blocks. > The script attempts to create two images of slices through the dataset. At > the first slice position data from both blocks are in the slice. At the > second slice position only data from one block is part of the slice. This > works in serial and parallel (two processors) using pvbatch when not using > surface LIC and in serial when using surface LIC with the latest ParaView > from the git repo. In parallel, the surface LIC hangs when creating the > second image. This script works in parallel with surface LIC when using > version 4.4.0. > > As an aside, I call the function to ensure that the surface LIC plugin is > loaded at the beginning of the script. When I do this I get warnings about > "Replacing existing representation for key: Surface LIC". I assume this is > because in my build I turned on the option to load the surface LIC plugin > by default. Is there a way in Python to check if a plugin is loaded and > skip this step if that is the case? > > Let me know if I can provide any additional information. > > -Andy > > On Tue, Feb 7, 2017 at 8:32 AM, Ken Martin wrote: > >> Thanks Andy, just to make sure I understand the issue. Is the case that >> one processor has no data, or is it that it has data, but it is outside the >> current view? >> >> Thanks >> Ken >> >> On Thu, Feb 2, 2017 at 5:14 PM, Andy Smith wrote: >> >>> I've tested this with the latest ParaView and it does seem to run much >>> faster. >>> I am having a problem when running in parallel though. If one processor >>> does not have anything to display, the rendering hangs. >>> Related to that, what routine actually calls >>> vtkCompositeLICHelper::RenderPiece? >>> The process that does not have anything to display never gets to that >>> function but the other processes do. In that function there are MPI calls >>> where the rendering hangs. >>> >>> As a reply to Chuck: I can use EGL in some instances but unfortunately >>> not all of our machine have GPUs so software rendering is still required. >>> >>> Thanks again for all the help. >>> >>> On Mon, Jan 23, 2017 at 12:45 PM, Ken Martin >>> wrote: >>> >>>> There is a VTK topic now that should fix this regression. With this >>>> change OpenGL2 LIC seems to run much faster (at least 10X). >>>> >>>> https://gitlab.kitware.com/vtk/vtk/merge_requests/2419 >>>> >>>> Hopefully it will test out OK and get merged into VTK and then merged >>>> into ParaView. >>>> >>>> On Mon, Dec 12, 2016 at 11:38 AM, Andy Smith >>>> wrote: >>>> >>>>> Ken, >>>>> >>>>> You are correct in your assumption about my dataset; it is multiblock >>>>> unstructured data. Adding a MergeBlocks filter to my slice does improve >>>>> the 5.2.0 with OpenGL2 significantly. >>>>> With that change the performance of 5.2.0 with OpenGL2 is on the same >>>>> order of magnitude as 5.2.0 with OpenGL and with 4.4.0, though the 5.2.0 >>>>> variants are still slower than 4.4.0. >>>>> >>>>> I realized after posting that my comparison is not exactly apples to >>>>> apples - my build of 5.2.0 required updates to mesa (13.0.0) compared with >>>>> the version I used for 4.4.0 (11.2.0). >>>>> I will recompile 4.4.0 with the same mesa version I used with 5.2.0 >>>>> and report back. >>>>> >>>>> Thank you for your input. >>>>> >>>>> -Andy >>>>> >>>>> On Fri, Dec 9, 2016 at 3:44 PM, Ken Martin >>>>> wrote: >>>>> >>>>>> I have not had time to look into this, but my quick guess is that you >>>>>> have a multiblock dataset with a lot of blocks. Can you try merging the >>>>>> blocks all together somehow into one block and see if the rendering speed >>>>>> improves? >>>>>> >>>>>> On Tue, Nov 15, 2016 at 5:35 AM, Stefan Melber >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>> i have a problem which is there in all RCs (1-4) of current >>>>>>> ParaView: if i compile the RenderingBackend to "OpenGL2" and use SurfaceLic >>>>>>> the visualization time goes up from a few seconds (with "OpenGL") to many >>>>>>> minutes and the memory consumption from a few GByte to approx 100 GByte. >>>>>>> Switching back to OpenGL any thing is fine. Without SurfaceLIC the OpenGL2 >>>>>>> works although fine for me. >>>>>>> >>>>>>> Has any one tested OpenGL2 with SurfaceLIC-Plugin the last time and >>>>>>> has (the same) problems? >>>>>>> >>>>>>> o Kernel 4.7.6-1 / x86-64 >>>>>>> o Quadro 4000 >>>>>>> o NVidia driver v367.57 >>>>>>> o PV 5.2.0 RC1 - RC4 >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Stefan >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> 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 >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> 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. >>>> >>> >>> >> >> >> -- >> 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. >> > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yves.rogez at univ-grenoble-alpes.fr Thu Feb 9 12:09:22 2017 From: yves.rogez at univ-grenoble-alpes.fr (Yves Rogez) Date: Thu, 9 Feb 2017 18:09:22 +0100 Subject: [Paraview] Making a package for Nix system Message-ID: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> 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 / -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Feb 9 15:40:19 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 9 Feb 2017 15:40:19 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: Hi John, I have tried this out with your data on the latest master branch of ParaView and I can't reproduce the bug you are seeing. So this may already be fixed. What version of ParaView are you using? And what OS? Thanks, Shawn On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: > Utkarsh et al., > > Here are the files. The data file (SteadyState_out.e) is particularly > large ~500 MB. > > https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm > > https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Sounds like a bug. If can provide example dataset and steps to reproduce >> that will make it easier to track it down. >> >> Thanks, >> Utkarsh >> >> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >> >>> Hello all, >>> >>> I am using Paraview to process data from a simulation output in the >>> Exodus II format. I create an IntegrateVariables object, then put it in a >>> PlotSelectionOverTime object so I have the integrated values at each time >>> step. At this point everything seems fine but, when I choose to Export >>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>> entry, the data sudden cuts out. >>> >>> The two images attached show what happens. >>> >>> 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 >>> >>> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Feb 9 15:49:08 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 9 Feb 2017 15:49:08 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: Shawn, I'm using 5.2.0 on Windows 10 Regards, John R. Haase jhaase1 at nd.edu On Thu, Feb 9, 2017 at 3:40 PM, Shawn Waldon wrote: > Hi John, > > I have tried this out with your data on the latest master branch of > ParaView and I can't reproduce the bug you are seeing. So this may already > be fixed. What version of ParaView are you using? And what OS? > > Thanks, > Shawn > > On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: > >> Utkarsh et al., >> >> Here are the files. The data file (SteadyState_out.e) is particularly >> large ~500 MB. >> >> https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm >> >> https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Sounds like a bug. If can provide example dataset and steps to reproduce >>> that will make it easier to track it down. >>> >>> Thanks, >>> Utkarsh >>> >>> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >>> >>>> Hello all, >>>> >>>> I am using Paraview to process data from a simulation output in the >>>> Exodus II format. I create an IntegrateVariables object, then put it in a >>>> PlotSelectionOverTime object so I have the integrated values at each time >>>> step. At this point everything seems fine but, when I choose to Export >>>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>>> entry, the data sudden cuts out. >>>> >>>> The two images attached show what happens. >>>> >>>> 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 >>>> >>>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 Thu Feb 9 17:16:04 2017 From: agsmith424 at gmail.com (Andy Smith) Date: Thu, 9 Feb 2017 17:16:04 -0500 Subject: [Paraview] Rendering Backend OpenGL2 & PV 5.2.0-RC4 & SurfaceLic --> Problem... In-Reply-To: References: <84a5a6aa-326f-a1ff-7789-28204a0ee502@DLR.de> Message-ID: Ken, I tested your changes and they are working for my more complicated "production" case. I am currently running more tests and will update you if anything goes wrong. I'm still adjusting my lighting settings from 4.4.0 to 5.x.x to get similar images between the two versions. In the past with 4.4.0 I had noticed that some surface LIC images would seemingly randomly get darker. Perhaps that is what you are seeing as well. -Andy On Thu, Feb 9, 2017 at 11:47 AM, Ken Martin wrote: > Thanks so much for the example. I have a VTK topic that I believe will fix > the issue here: > > https://gitlab.kitware.com/vtk/vtk/merge_requests/2463 > > It fails three of the current paraview LIC tests but with images that > still look reasonable (although one looks dark to me). The changes only > impact two files. Your example no longer hangs with these changes. If you > have a chance to test it on your real data or other cases that would help > me feel more confident about the change. > > Thanks > Ken > > > > > On Wed, Feb 8, 2017 at 9:21 AM, Andy Smith wrote: > >> Ken, >> >> I've attached a small example file and script that demonstrates the >> problem. >> >> The example dataset is a multiblock unstructured grid with two blocks. >> The script attempts to create two images of slices through the dataset. At >> the first slice position data from both blocks are in the slice. At the >> second slice position only data from one block is part of the slice. This >> works in serial and parallel (two processors) using pvbatch when not using >> surface LIC and in serial when using surface LIC with the latest ParaView >> from the git repo. In parallel, the surface LIC hangs when creating the >> second image. This script works in parallel with surface LIC when using >> version 4.4.0. >> >> As an aside, I call the function to ensure that the surface LIC plugin is >> loaded at the beginning of the script. When I do this I get warnings about >> "Replacing existing representation for key: Surface LIC". I assume this is >> because in my build I turned on the option to load the surface LIC plugin >> by default. Is there a way in Python to check if a plugin is loaded and >> skip this step if that is the case? >> >> Let me know if I can provide any additional information. >> >> -Andy >> >> On Tue, Feb 7, 2017 at 8:32 AM, Ken Martin >> wrote: >> >>> Thanks Andy, just to make sure I understand the issue. Is the case that >>> one processor has no data, or is it that it has data, but it is outside the >>> current view? >>> >>> Thanks >>> Ken >>> >>> On Thu, Feb 2, 2017 at 5:14 PM, Andy Smith wrote: >>> >>>> I've tested this with the latest ParaView and it does seem to run much >>>> faster. >>>> I am having a problem when running in parallel though. If one >>>> processor does not have anything to display, the rendering hangs. >>>> Related to that, what routine actually calls >>>> vtkCompositeLICHelper::RenderPiece? >>>> The process that does not have anything to display never gets to that >>>> function but the other processes do. In that function there are MPI calls >>>> where the rendering hangs. >>>> >>>> As a reply to Chuck: I can use EGL in some instances but unfortunately >>>> not all of our machine have GPUs so software rendering is still required. >>>> >>>> Thanks again for all the help. >>>> >>>> On Mon, Jan 23, 2017 at 12:45 PM, Ken Martin >>>> wrote: >>>> >>>>> There is a VTK topic now that should fix this regression. With this >>>>> change OpenGL2 LIC seems to run much faster (at least 10X). >>>>> >>>>> https://gitlab.kitware.com/vtk/vtk/merge_requests/2419 >>>>> >>>>> Hopefully it will test out OK and get merged into VTK and then merged >>>>> into ParaView. >>>>> >>>>> On Mon, Dec 12, 2016 at 11:38 AM, Andy Smith >>>>> wrote: >>>>> >>>>>> Ken, >>>>>> >>>>>> You are correct in your assumption about my dataset; it is multiblock >>>>>> unstructured data. Adding a MergeBlocks filter to my slice does improve >>>>>> the 5.2.0 with OpenGL2 significantly. >>>>>> With that change the performance of 5.2.0 with OpenGL2 is on the same >>>>>> order of magnitude as 5.2.0 with OpenGL and with 4.4.0, though the 5.2.0 >>>>>> variants are still slower than 4.4.0. >>>>>> >>>>>> I realized after posting that my comparison is not exactly apples to >>>>>> apples - my build of 5.2.0 required updates to mesa (13.0.0) compared with >>>>>> the version I used for 4.4.0 (11.2.0). >>>>>> I will recompile 4.4.0 with the same mesa version I used with 5.2.0 >>>>>> and report back. >>>>>> >>>>>> Thank you for your input. >>>>>> >>>>>> -Andy >>>>>> >>>>>> On Fri, Dec 9, 2016 at 3:44 PM, Ken Martin >>>>>> wrote: >>>>>> >>>>>>> I have not had time to look into this, but my quick guess is that >>>>>>> you have a multiblock dataset with a lot of blocks. Can you try merging the >>>>>>> blocks all together somehow into one block and see if the rendering speed >>>>>>> improves? >>>>>>> >>>>>>> On Tue, Nov 15, 2016 at 5:35 AM, Stefan Melber >>>>>> > wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> >>>>>>>> i have a problem which is there in all RCs (1-4) of current >>>>>>>> ParaView: if i compile the RenderingBackend to "OpenGL2" and use SurfaceLic >>>>>>>> the visualization time goes up from a few seconds (with "OpenGL") to many >>>>>>>> minutes and the memory consumption from a few GByte to approx 100 GByte. >>>>>>>> Switching back to OpenGL any thing is fine. Without SurfaceLIC the OpenGL2 >>>>>>>> works although fine for me. >>>>>>>> >>>>>>>> Has any one tested OpenGL2 with SurfaceLIC-Plugin the last time and >>>>>>>> has (the same) problems? >>>>>>>> >>>>>>>> o Kernel 4.7.6-1 / x86-64 >>>>>>>> o Quadro 4000 >>>>>>>> o NVidia driver v367.57 >>>>>>>> o PV 5.2.0 RC1 - RC4 >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Stefan >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> 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. >>>>> >>>> >>>> >>> >>> >>> -- >>> 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. >>> >> >> > > > -- > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Feb 9 17:25:27 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 9 Feb 2017 17:25:27 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: John, I just tried the 5.2.0 binaries on Windows 7 and I didn't see this issue, so it may be some idiosyncrasy of Windows 10 or I'm not following the right steps to reproduce it. I'll try to track down a Windows 10 machine tomorrow, but if you could give me a step-by-step list of how to reproduce this it would help. So far I have: Loaded your state file export spreadsheet scroll down to the 1023rd/1024th line -> it is fine Loaded your state file scroll down to the 1023rd/1024th line export spreadsheet -> again it is fine If I click around on the spreadsheet I sometimes get "..." replacing the entries above or below the 1023/1024 line as it reloads the data for those items, but I never see garbage data. Shawn On Thu, Feb 9, 2017 at 3:49 PM, John Haase wrote: > Shawn, > > I'm using 5.2.0 on Windows 10 > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Thu, Feb 9, 2017 at 3:40 PM, Shawn Waldon > wrote: > >> Hi John, >> >> I have tried this out with your data on the latest master branch of >> ParaView and I can't reproduce the bug you are seeing. So this may already >> be fixed. What version of ParaView are you using? And what OS? >> >> Thanks, >> Shawn >> >> On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: >> >>> Utkarsh et al., >>> >>> Here are the files. The data file (SteadyState_out.e) is particularly >>> large ~500 MB. >>> >>> https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm >>> >>> https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e >>> >>> Regards, >>> >>> John R. Haase >>> jhaase1 at nd.edu >>> >>> On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> Sounds like a bug. If can provide example dataset and steps to >>>> reproduce that will make it easier to track it down. >>>> >>>> Thanks, >>>> Utkarsh >>>> >>>> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >>>> >>>>> Hello all, >>>>> >>>>> I am using Paraview to process data from a simulation output in the >>>>> Exodus II format. I create an IntegrateVariables object, then put it in a >>>>> PlotSelectionOverTime object so I have the integrated values at each time >>>>> step. At this point everything seems fine but, when I choose to Export >>>>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>>>> entry, the data sudden cuts out. >>>>> >>>>> The two images attached show what happens. >>>>> >>>>> 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 >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 Feb 9 20:24:56 2017 From: jhaase1 at nd.edu (John Haase) Date: Thu, 9 Feb 2017 20:24:56 -0500 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: Shawn, I sometimes get the "..." in Paraview as well. The exact steps I follow are 1. Open Paraview 2. Load State File (using File > Load State) 3. Use the "Export spreadsheet" button in Layout 1 4. scroll down to the 1023rd/2001st line -> it is not fine However, I just realized that if I go File > Save Data, I don't encounter the bug Regards, John R. Haase jhaase1 at nd.edu On Thu, Feb 9, 2017 at 5:25 PM, Shawn Waldon wrote: > John, > > I just tried the 5.2.0 binaries on Windows 7 and I didn't see this issue, > so it may be some idiosyncrasy of Windows 10 or I'm not following the right > steps to reproduce it. I'll try to track down a Windows 10 machine > tomorrow, but if you could give me a step-by-step list of how to reproduce > this it would help. So far I have: > > Loaded your state file > export spreadsheet > scroll down to the 1023rd/1024th line -> it is fine > > > Loaded your state file > scroll down to the 1023rd/1024th line > export spreadsheet -> again it is fine > > If I click around on the spreadsheet I sometimes get "..." replacing the > entries above or below the 1023/1024 line as it reloads the data for those > items, but I never see garbage data. > > Shawn > > > > On Thu, Feb 9, 2017 at 3:49 PM, John Haase wrote: > >> Shawn, >> >> I'm using 5.2.0 on Windows 10 >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> On Thu, Feb 9, 2017 at 3:40 PM, Shawn Waldon >> wrote: >> >>> Hi John, >>> >>> I have tried this out with your data on the latest master branch of >>> ParaView and I can't reproduce the bug you are seeing. So this may already >>> be fixed. What version of ParaView are you using? And what OS? >>> >>> Thanks, >>> Shawn >>> >>> On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: >>> >>>> Utkarsh et al., >>>> >>>> Here are the files. The data file (SteadyState_out.e) is particularly >>>> large ~500 MB. >>>> >>>> https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm >>>> >>>> https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e >>>> >>>> Regards, >>>> >>>> John R. Haase >>>> jhaase1 at nd.edu >>>> >>>> On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < >>>> utkarsh.ayachit at kitware.com> wrote: >>>> >>>>> Sounds like a bug. If can provide example dataset and steps to >>>>> reproduce that will make it easier to track it down. >>>>> >>>>> Thanks, >>>>> Utkarsh >>>>> >>>>> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> I am using Paraview to process data from a simulation output in the >>>>>> Exodus II format. I create an IntegrateVariables object, then put it in a >>>>>> PlotSelectionOverTime object so I have the integrated values at each time >>>>>> step. At this point everything seems fine but, when I choose to Export >>>>>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>>>>> entry, the data sudden cuts out. >>>>>> >>>>>> The two images attached show what happens. >>>>>> >>>>>> 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 >>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Thu Feb 9 21:29:22 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 03:29:22 +0100 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: John, FYI, Save Data and Export scene (the bouton on the spreadsheet is a shortcut ot export scene) are different mechanism. Regards, Mathieu Westphal On Fri, Feb 10, 2017 at 2:24 AM, John Haase wrote: > Shawn, > > I sometimes get the "..." in Paraview as well. > > The exact steps I follow are > > 1. Open Paraview > 2. Load State File (using File > Load State) > 3. Use the "Export spreadsheet" button in Layout 1 > 4. scroll down to the 1023rd/2001st line -> it is not fine > > However, I just realized that if I go File > Save Data, I don't encounter > the bug > > > > Regards, > > John R. Haase > jhaase1 at nd.edu > > On Thu, Feb 9, 2017 at 5:25 PM, Shawn Waldon > wrote: > >> John, >> >> I just tried the 5.2.0 binaries on Windows 7 and I didn't see this issue, >> so it may be some idiosyncrasy of Windows 10 or I'm not following the right >> steps to reproduce it. I'll try to track down a Windows 10 machine >> tomorrow, but if you could give me a step-by-step list of how to reproduce >> this it would help. So far I have: >> >> Loaded your state file >> export spreadsheet >> scroll down to the 1023rd/1024th line -> it is fine >> >> >> Loaded your state file >> scroll down to the 1023rd/1024th line >> export spreadsheet -> again it is fine >> >> If I click around on the spreadsheet I sometimes get "..." replacing the >> entries above or below the 1023/1024 line as it reloads the data for those >> items, but I never see garbage data. >> >> Shawn >> >> >> >> On Thu, Feb 9, 2017 at 3:49 PM, John Haase wrote: >> >>> Shawn, >>> >>> I'm using 5.2.0 on Windows 10 >>> >>> Regards, >>> >>> John R. Haase >>> jhaase1 at nd.edu >>> >>> On Thu, Feb 9, 2017 at 3:40 PM, Shawn Waldon >>> wrote: >>> >>>> Hi John, >>>> >>>> I have tried this out with your data on the latest master branch of >>>> ParaView and I can't reproduce the bug you are seeing. So this may already >>>> be fixed. What version of ParaView are you using? And what OS? >>>> >>>> Thanks, >>>> Shawn >>>> >>>> On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: >>>> >>>>> Utkarsh et al., >>>>> >>>>> Here are the files. The data file (SteadyState_out.e) is particularly >>>>> large ~500 MB. >>>>> >>>>> https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm >>>>> >>>>> https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e >>>>> >>>>> Regards, >>>>> >>>>> John R. Haase >>>>> jhaase1 at nd.edu >>>>> >>>>> On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < >>>>> utkarsh.ayachit at kitware.com> wrote: >>>>> >>>>>> Sounds like a bug. If can provide example dataset and steps to >>>>>> reproduce that will make it easier to track it down. >>>>>> >>>>>> Thanks, >>>>>> Utkarsh >>>>>> >>>>>> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> I am using Paraview to process data from a simulation output in the >>>>>>> Exodus II format. I create an IntegrateVariables object, then put it in a >>>>>>> PlotSelectionOverTime object so I have the integrated values at each time >>>>>>> step. At this point everything seems fine but, when I choose to Export >>>>>>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>>>>>> entry, the data sudden cuts out. >>>>>>> >>>>>>> The two images attached show what happens. >>>>>>> >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Thu Feb 9 21:48:31 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 03:48:31 +0100 Subject: [Paraview] Making a package for Nix system In-Reply-To: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> References: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> Message-ID: 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 < yves.rogez at univ-grenoble-alpes.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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yves.rogez at univ-grenoble-alpes.fr Fri Feb 10 03:44:49 2017 From: yves.rogez at univ-grenoble-alpes.fr (Yves Rogez) Date: Fri, 10 Feb 2017 09:44:49 +0100 Subject: [Paraview] Making a package for Nix system In-Reply-To: References: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> Message-ID: <3f314df6-9623-6396-7be3-b3929f8d2164@univ-grenoble-alpes.fr> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.dimitrova at helsinki.fi Fri Feb 10 04:23:22 2017 From: maria.dimitrova at helsinki.fi (Dimitrova, Maria) Date: Fri, 10 Feb 2017 09:23:22 +0000 Subject: [Paraview] Copying representation properties Message-ID: Dear all, Is there a way to copy the properties of the representation that is applied to a filter to another instance of the same filter? In my project I use 3D glyphs with sphere size 0.03 and blue colour. I have tried right-clicking on the existing filter -> Copy, then Paste to the new instance of the filter but the representation is not affected. Also, another part of my project involves applying Surface LIC with a particular colour scheme and colour range, as well as contrast adjustments and antialiasing, all of which are identical for all the files I need to process. It would save some time if I could just make a custom representation. Thank you very much! Best regards, Maria -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Melber at DLR.de Fri Feb 10 05:17:48 2017 From: Stefan.Melber at DLR.de (Stefan Melber) Date: Fri, 10 Feb 2017 11:17:48 +0100 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... In-Reply-To: References: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> Message-ID: Hi Utkarsh, so i assume its finally a problem of the reader (here Ensight) which does not produce the ghost-cells. Ok, for the small testcase it works fine - however for the real one some of the processes fails with an error and ParaView in the end crashes. I then tried instead of using the "Ghost Cell Generator" i use "D31"-filter - and it does its job (seems it produces the ghost cells too because running the ghost-cell filter after D31 there is nothing to do for the filter). However - regarding the error i found with "Ghost Cell Generator" i will send you a bigger (sorry) testcase.Just read in the data and apply the GhostCellGenerator in parallel ... i will crash. Best regards, Stefan > Stefan, > > Attached is a fixed state file. Since the file didn't have ghost-cell > information, the filters like "Compute Derivatives" didn't produce > correct result at the process boundary cells. By putting a "Ghost Cell > Generator" filter in the pipeline, one can address that issue. > > Utkarsh > > On Thu, Feb 9, 2017 at 8:18 AM, Utkarsh Ayachit > > wrote: > > That's odd. Stefan, can you send me the dataset please? I'll have > it looked into. > > Thanks > Utkarsh > > On Thu, Feb 9, 2017 at 4:04 AM, Stefan Melber > > wrote: > > Hi, > > > during visualization of vortices i found a bug (or feature?) > of ParaView: running the case in serial mode the results look > fine. However, doing the same in parallel mode (e.g. 8 cores) > the picture looks "ugly". Has anyone seen such an effect > running in parallel? I am using the current version (v5.2.0) > on a Linux 64bit machine with a Quadro 4000 graphics card. > > Attached there are two pics showing the effect, a picture of > the used pipeline and the restart file... > > The test-data can be send to you for testing - i just need a > email-address to send it to. > > Best regards, > > Stefan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Fri Feb 10 06:44:37 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 12:44:37 +0100 Subject: [Paraview] Copying representation properties In-Reply-To: References: Message-ID: Hello I just checked, to copy->Paste feature is working perfectly on ParaView master git. Which version of ParaView are you using ? Regards, Mathieu Westphal On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria < maria.dimitrova at helsinki.fi> wrote: > Dear all, > > > Is there a way to copy the properties of the representation that is > applied to a filter to another instance of the same filter? In my project I > use 3D glyphs with sphere size 0.03 and blue colour. I have tried > right-clicking on the existing filter -> Copy, then Paste to the new > instance of the filter but the representation is not affected. > > > Also, another part of my project involves applying Surface LIC with a > particular colour scheme and colour range, as well as contrast adjustments > and antialiasing, all of which are identical for all the files I need to > process. It would save some time if I could just make a custom > representation. > > > Thank you very much! > > > Best regards, > > Maria > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 maria.dimitrova at helsinki.fi Fri Feb 10 07:06:50 2017 From: maria.dimitrova at helsinki.fi (Dimitrova, Maria) Date: Fri, 10 Feb 2017 12:06:50 +0000 Subject: [Paraview] Copying representation properties In-Reply-To: References: , Message-ID: Hello, Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL version - 5.2.0-RC4. Best regards, Maria Dimitrova ________________________________ From: Mathieu Westphal Sent: 10 February 2017 13:44:37 To: Dimitrova, Maria Cc: paraview at paraview.org Subject: Re: [Paraview] Copying representation properties Hello I just checked, to copy->Paste feature is working perfectly on ParaView master git. Which version of ParaView are you using ? Regards, Mathieu Westphal On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria > wrote: Dear all, Is there a way to copy the properties of the representation that is applied to a filter to another instance of the same filter? In my project I use 3D glyphs with sphere size 0.03 and blue colour. I have tried right-clicking on the existing filter -> Copy, then Paste to the new instance of the filter but the representation is not affected. Also, another part of my project involves applying Surface LIC with a particular colour scheme and colour range, as well as contrast adjustments and antialiasing, all of which are identical for all the files I need to process. It would save some time if I could just make a custom representation. Thank you very much! Best regards, Maria _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Fri Feb 10 07:15:11 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 13:15:11 +0100 Subject: [Paraview] Copying representation properties In-Reply-To: References: Message-ID: Hello I will not be able to test this version right away, will let you know. Mathieu Westphal On Fri, Feb 10, 2017 at 1:06 PM, Dimitrova, Maria < maria.dimitrova at helsinki.fi> wrote: > Hello, > > > Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL version > - 5.2.0-RC4. > > > Best regards, > > Maria Dimitrova > ------------------------------ > *From:* Mathieu Westphal > *Sent:* 10 February 2017 13:44:37 > *To:* Dimitrova, Maria > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Copying representation properties > > Hello > > I just checked, to copy->Paste feature is working perfectly on ParaView > master git. Which version of ParaView are you using ? > > Regards, > > Mathieu Westphal > > On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria < > maria.dimitrova at helsinki.fi> wrote: > >> Dear all, >> >> >> Is there a way to copy the properties of the representation that is >> applied to a filter to another instance of the same filter? In my project I >> use 3D glyphs with sphere size 0.03 and blue colour. I have tried >> right-clicking on the existing filter -> Copy, then Paste to the new >> instance of the filter but the representation is not affected. >> >> >> Also, another part of my project involves applying Surface LIC with a >> particular colour scheme and colour range, as well as contrast adjustments >> and antialiasing, all of which are identical for all the files I need to >> process. It would save some time if I could just make a custom >> representation. >> >> >> Thank you very much! >> >> >> Best regards, >> >> Maria >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Fri Feb 10 07:34:21 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 13:34:21 +0100 Subject: [Paraview] Problem with exporting spreadsheet view In-Reply-To: References: Message-ID: John, I'm able to reproduce the bug in client/server Could you submit an issue at https://gitlab.kitware.com/paraview/paraview/issues , so we can look into it ? Thanks Mathieu Westphal On Fri, Feb 10, 2017 at 3:29 AM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > John, > FYI, Save Data and Export scene (the bouton on the spreadsheet is a > shortcut ot export scene) are different mechanism. > > Regards, > > Mathieu Westphal > > On Fri, Feb 10, 2017 at 2:24 AM, John Haase wrote: > >> Shawn, >> >> I sometimes get the "..." in Paraview as well. >> >> The exact steps I follow are >> >> 1. Open Paraview >> 2. Load State File (using File > Load State) >> 3. Use the "Export spreadsheet" button in Layout 1 >> 4. scroll down to the 1023rd/2001st line -> it is not fine >> >> However, I just realized that if I go File > Save Data, I don't encounter >> the bug >> >> >> >> Regards, >> >> John R. Haase >> jhaase1 at nd.edu >> >> On Thu, Feb 9, 2017 at 5:25 PM, Shawn Waldon >> wrote: >> >>> John, >>> >>> I just tried the 5.2.0 binaries on Windows 7 and I didn't see this >>> issue, so it may be some idiosyncrasy of Windows 10 or I'm not following >>> the right steps to reproduce it. I'll try to track down a Windows 10 >>> machine tomorrow, but if you could give me a step-by-step list of how to >>> reproduce this it would help. So far I have: >>> >>> Loaded your state file >>> export spreadsheet >>> scroll down to the 1023rd/1024th line -> it is fine >>> >>> >>> Loaded your state file >>> scroll down to the 1023rd/1024th line >>> export spreadsheet -> again it is fine >>> >>> If I click around on the spreadsheet I sometimes get "..." replacing the >>> entries above or below the 1023/1024 line as it reloads the data for those >>> items, but I never see garbage data. >>> >>> Shawn >>> >>> >>> >>> On Thu, Feb 9, 2017 at 3:49 PM, John Haase wrote: >>> >>>> Shawn, >>>> >>>> I'm using 5.2.0 on Windows 10 >>>> >>>> Regards, >>>> >>>> John R. Haase >>>> jhaase1 at nd.edu >>>> >>>> On Thu, Feb 9, 2017 at 3:40 PM, Shawn Waldon >>>> wrote: >>>> >>>>> Hi John, >>>>> >>>>> I have tried this out with your data on the latest master branch of >>>>> ParaView and I can't reproduce the bug you are seeing. So this may already >>>>> be fixed. What version of ParaView are you using? And what OS? >>>>> >>>>> Thanks, >>>>> Shawn >>>>> >>>>> On Thu, Feb 9, 2017 at 11:27 AM, John Haase wrote: >>>>> >>>>>> Utkarsh et al., >>>>>> >>>>>> Here are the files. The data file (SteadyState_out.e) is particularly >>>>>> large ~500 MB. >>>>>> >>>>>> https://dl.dropboxusercontent.com/u/9655539/Integration.pvsm >>>>>> >>>>>> https://dl.dropboxusercontent.com/u/9655539/SteadyState_out.e >>>>>> >>>>>> Regards, >>>>>> >>>>>> John R. Haase >>>>>> jhaase1 at nd.edu >>>>>> >>>>>> On Thu, Feb 9, 2017 at 11:08 AM, Utkarsh Ayachit < >>>>>> utkarsh.ayachit at kitware.com> wrote: >>>>>> >>>>>>> Sounds like a bug. If can provide example dataset and steps to >>>>>>> reproduce that will make it easier to track it down. >>>>>>> >>>>>>> Thanks, >>>>>>> Utkarsh >>>>>>> >>>>>>> On Thu, Feb 9, 2017 at 9:26 AM, John Haase wrote: >>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>> I am using Paraview to process data from a simulation output in the >>>>>>>> Exodus II format. I create an IntegrateVariables object, then put it in a >>>>>>>> PlotSelectionOverTime object so I have the integrated values at each time >>>>>>>> step. At this point everything seems fine but, when I choose to Export >>>>>>>> Spreadsheet, the data gets corrupted or something. After the 1023 (2^10-1) >>>>>>>> entry, the data sudden cuts out. >>>>>>>> >>>>>>>> The two images attached show what happens. >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView 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 Stefan.Melber at DLR.de Fri Feb 10 07:35:36 2017 From: Stefan.Melber at DLR.de (Stefan Melber) Date: Fri, 10 Feb 2017 13:35:36 +0100 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... In-Reply-To: References: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> Message-ID: <0eedc9f6-dd19-7285-7648-80cbe8491be9@DLR.de> Hi, amendment: the test case i send to you also crashes using the D31-filter: Executing with: Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 0 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 23833 RUNNING AT bsastf670os = EXIT CODE: 139 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11) This typically refers to a problem with your application. Please see the FAQ page for debugging suggestions This now looks like a bug ;-) Stefan > Stefan, > > Attached is a fixed state file. Since the file didn't have ghost-cell > information, the filters like "Compute Derivatives" didn't produce > correct result at the process boundary cells. By putting a "Ghost Cell > Generator" filter in the pipeline, one can address that issue. > > Utkarsh > > On Thu, Feb 9, 2017 at 8:18 AM, Utkarsh Ayachit > > wrote: > > That's odd. Stefan, can you send me the dataset please? I'll have > it looked into. > > Thanks > Utkarsh > > On Thu, Feb 9, 2017 at 4:04 AM, Stefan Melber > > wrote: > > Hi, > > > during visualization of vortices i found a bug (or feature?) > of ParaView: running the case in serial mode the results look > fine. However, doing the same in parallel mode (e.g. 8 cores) > the picture looks "ugly". Has anyone seen such an effect > running in parallel? I am using the current version (v5.2.0) > on a Linux 64bit machine with a Quadro 4000 graphics card. > > Attached there are two pics showing the effect, a picture of > the used pipeline and the restart file... > > The test-data can be send to you for testing - i just need a > email-address to send it to. > > Best regards, > > Stefan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Fri Feb 10 09:14:48 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 10 Feb 2017 15:14:48 +0100 Subject: [Paraview] Making a package for Nix system In-Reply-To: <3f314df6-9623-6396-7be3-b3929f8d2164@univ-grenoble-alpes.fr> References: <058bfa21-a6d0-9cc8-6b81-7963f1609261@univ-grenoble-alpes.fr> <3f314df6-9623-6396-7be3-b3929f8d2164@univ-grenoble-alpes.fr> Message-ID: 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 < yves.rogez at univ-grenoble-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 alpes.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> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michalwozniak at live.ca Fri Feb 10 13:34:34 2017 From: michalwozniak at live.ca (michal wozniak) Date: Fri, 10 Feb 2017 18:34:34 +0000 Subject: [Paraview] vtkPythonProgrammableFilter Multiple output port? Message-ID: Hi, Since ParaView 5.2, vtkPythonProgrammableFilter can now accept multiple input ports. Is it possible to also have multiple output port? Thanks, Michal -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at feacluster.com Fri Feb 10 16:25:21 2017 From: info at feacluster.com (Faraz Hussain) Date: Fri, 10 Feb 2017 16:25:21 -0500 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> Message-ID: <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> Thanks for your help in installing Paraview on a raspberry pi. I followed the steps in: http://www.paraview.org/Wiki/ParaView:Build_And_Install However, when I configure ccmake it says QT is needed. I could not figure out if I can ignore that. The "generate" command did not come up. On a side note, it took me a while to find ccmake. I thought it was installed with cmake, but seems I had to install it separately using "sudo apt-get install cmake-curses-gui" . Perhaps the instructions should be updated to reflect this to avoid confusion. Quoting Sebastien Jourdain : > Wow, > > I'm not an expert on raspberry pi but it should be possible. > BUT, (and it is a big but) you need some graphics capability for ParaView > or good CPUs if you don't have a GPU. > Or the rendering will be really slow. > > The quicker test you can do, is to build ParaView (without Qt) and try to > run Visualizer with that ParaView in the command line to see what > performance you are getting. If that's reasonable, then all the network > setup should be "trivial". > > ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install > Visualizer: https://kitware.github.io/visualizer/ > > Good luck, > > Seb > > On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain wrote: > >> I want to be able to manipulate vtk file on my raspberry pi via a web >> browser anywhere in the world. I believe I need to install paraviewweb and >> do some reconfiguration of apache and the virtual hosts? Unfortunately, I >> am not a guru of Linux. So before I attempt it all, is it even possible to >> do this on a raspberry pi? I am using raspian . >> >> _______________________________________________ >> 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 >> From scott.wittenburg at kitware.com Fri Feb 10 16:31:08 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 10 Feb 2017 14:31:08 -0700 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> Message-ID: I would think you'd want to build with: PARAVIEW_BUILD_QT_GUI=OFF Hope this helps, Scott On Fri, Feb 10, 2017 at 2:25 PM, Faraz Hussain wrote: > Thanks for your help in installing Paraview on a raspberry pi. I followed > the steps in: > > http://www.paraview.org/Wiki/ParaView:Build_And_Install > > However, when I configure ccmake it says QT is needed. I could not figure > out if I can ignore that. The "generate" command did not come up. > > On a side note, it took me a while to find ccmake. I thought it was > installed with cmake, but seems I had to install it separately using "sudo > apt-get install cmake-curses-gui" . Perhaps the instructions should be > updated to reflect this to avoid confusion. > > > Quoting Sebastien Jourdain : > > Wow, >> >> I'm not an expert on raspberry pi but it should be possible. >> BUT, (and it is a big but) you need some graphics capability for ParaView >> or good CPUs if you don't have a GPU. >> Or the rendering will be really slow. >> >> The quicker test you can do, is to build ParaView (without Qt) and try to >> run Visualizer with that ParaView in the command line to see what >> performance you are getting. If that's reasonable, then all the network >> setup should be "trivial". >> >> ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install >> Visualizer: https://kitware.github.io/visualizer/ >> >> Good luck, >> >> Seb >> >> On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain >> wrote: >> >> I want to be able to manipulate vtk file on my raspberry pi via a web >>> browser anywhere in the world. I believe I need to install paraviewweb >>> and >>> do some reconfiguration of apache and the virtual hosts? Unfortunately, I >>> am not a guru of Linux. So before I attempt it all, is it even possible >>> to >>> do this on a raspberry pi? I am using raspian . >>> >>> _______________________________________________ >>> 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/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 scott.wittenburg at kitware.com Fri Feb 10 16:33:42 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 10 Feb 2017 14:33:42 -0700 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> Message-ID: Also for paraviewweb, don't forget: PARAVIEW_ENABLE_PYTHON=ON Cheers, Scott On Fri, Feb 10, 2017 at 2:31 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > I would think you'd want to build with: > > PARAVIEW_BUILD_QT_GUI=OFF > > Hope this helps, > > Scott > > On Fri, Feb 10, 2017 at 2:25 PM, Faraz Hussain > wrote: > >> Thanks for your help in installing Paraview on a raspberry pi. I followed >> the steps in: >> >> http://www.paraview.org/Wiki/ParaView:Build_And_Install >> >> However, when I configure ccmake it says QT is needed. I could not figure >> out if I can ignore that. The "generate" command did not come up. >> >> On a side note, it took me a while to find ccmake. I thought it was >> installed with cmake, but seems I had to install it separately using "sudo >> apt-get install cmake-curses-gui" . Perhaps the instructions should be >> updated to reflect this to avoid confusion. >> >> >> Quoting Sebastien Jourdain : >> >> Wow, >>> >>> I'm not an expert on raspberry pi but it should be possible. >>> BUT, (and it is a big but) you need some graphics capability for ParaView >>> or good CPUs if you don't have a GPU. >>> Or the rendering will be really slow. >>> >>> The quicker test you can do, is to build ParaView (without Qt) and try to >>> run Visualizer with that ParaView in the command line to see what >>> performance you are getting. If that's reasonable, then all the network >>> setup should be "trivial". >>> >>> ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install >>> Visualizer: https://kitware.github.io/visualizer/ >>> >>> Good luck, >>> >>> Seb >>> >>> On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain >>> wrote: >>> >>> I want to be able to manipulate vtk file on my raspberry pi via a web >>>> browser anywhere in the world. I believe I need to install paraviewweb >>>> and >>>> do some reconfiguration of apache and the virtual hosts? Unfortunately, >>>> I >>>> am not a guru of Linux. So before I attempt it all, is it even possible >>>> to >>>> do this on a raspberry pi? I am using raspian . >>>> >>>> _______________________________________________ >>>> 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 sebastien.jourdain at kitware.com Fri Feb 10 16:56:01 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Fri, 10 Feb 2017 14:56:01 -0700 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> Message-ID: You need to hit [c](configure) several time before getting the generate. On Fri, Feb 10, 2017 at 2:33 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > Also for paraviewweb, don't forget: > > PARAVIEW_ENABLE_PYTHON=ON > > Cheers, > > Scott > > On Fri, Feb 10, 2017 at 2:31 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> I would think you'd want to build with: >> >> PARAVIEW_BUILD_QT_GUI=OFF >> >> Hope this helps, >> >> Scott >> >> On Fri, Feb 10, 2017 at 2:25 PM, Faraz Hussain >> wrote: >> >>> Thanks for your help in installing Paraview on a raspberry pi. I >>> followed the steps in: >>> >>> http://www.paraview.org/Wiki/ParaView:Build_And_Install >>> >>> However, when I configure ccmake it says QT is needed. I could not >>> figure out if I can ignore that. The "generate" command did not come up. >>> >>> On a side note, it took me a while to find ccmake. I thought it was >>> installed with cmake, but seems I had to install it separately using "sudo >>> apt-get install cmake-curses-gui" . Perhaps the instructions should be >>> updated to reflect this to avoid confusion. >>> >>> >>> Quoting Sebastien Jourdain : >>> >>> Wow, >>>> >>>> I'm not an expert on raspberry pi but it should be possible. >>>> BUT, (and it is a big but) you need some graphics capability for >>>> ParaView >>>> or good CPUs if you don't have a GPU. >>>> Or the rendering will be really slow. >>>> >>>> The quicker test you can do, is to build ParaView (without Qt) and try >>>> to >>>> run Visualizer with that ParaView in the command line to see what >>>> performance you are getting. If that's reasonable, then all the network >>>> setup should be "trivial". >>>> >>>> ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install >>>> Visualizer: https://kitware.github.io/visualizer/ >>>> >>>> Good luck, >>>> >>>> Seb >>>> >>>> On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain >>>> wrote: >>>> >>>> I want to be able to manipulate vtk file on my raspberry pi via a web >>>>> browser anywhere in the world. I believe I need to install paraviewweb >>>>> and >>>>> do some reconfiguration of apache and the virtual hosts? >>>>> Unfortunately, I >>>>> am not a guru of Linux. So before I attempt it all, is it even >>>>> possible to >>>>> do this on a raspberry pi? I am using raspian . >>>>> >>>>> _______________________________________________ >>>>> 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 cory.quammen at kitware.com Sat Feb 11 17:30:58 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Feb 2017 17:30:58 -0500 Subject: [Paraview] Copying representation properties In-Reply-To: References: Message-ID: FWIW, I just tried this with 5.2.0 official binaries on Mac OS X and copy/paste of representation properties worked fine. On Fri, Feb 10, 2017 at 7:15 AM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > Hello > > I will not be able to test this version right away, will let you know. > > Mathieu Westphal > > On Fri, Feb 10, 2017 at 1:06 PM, Dimitrova, Maria < > maria.dimitrova at helsinki.fi> wrote: > >> Hello, >> >> >> Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL >> version - 5.2.0-RC4. >> >> >> Best regards, >> >> Maria Dimitrova >> ------------------------------ >> *From:* Mathieu Westphal >> *Sent:* 10 February 2017 13:44:37 >> *To:* Dimitrova, Maria >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Copying representation properties >> >> Hello >> >> I just checked, to copy->Paste feature is working perfectly on ParaView >> master git. Which version of ParaView are you using ? >> >> Regards, >> >> Mathieu Westphal >> >> On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria < >> maria.dimitrova at helsinki.fi> wrote: >> >>> Dear all, >>> >>> >>> Is there a way to copy the properties of the representation that is >>> applied to a filter to another instance of the same filter? In my project I >>> use 3D glyphs with sphere size 0.03 and blue colour. I have tried >>> right-clicking on the existing filter -> Copy, then Paste to the new >>> instance of the filter but the representation is not affected. >>> >>> >>> Also, another part of my project involves applying Surface LIC with a >>> particular colour scheme and colour range, as well as contrast adjustments >>> and antialiasing, all of which are identical for all the files I need to >>> process. It would save some time if I could just make a custom >>> representation. >>> >>> >>> Thank you very much! >>> >>> >>> Best regards, >>> >>> Maria >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 Sat Feb 11 17:48:27 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Feb 2017 17:48:27 -0500 Subject: [Paraview] PVSB 5.2: missing modules and plugins after "make install" In-Reply-To: References: Message-ID: Ben, Will updating to the current superbuild master address the missing plugins issue Michel is seeing? It looks like there have been some minor changes on plugin handling in linux since 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16. Thanks, Cory On Thu, Feb 9, 2017 at 5:08 AM, Michel Rasquin wrote: > Hi everyone, > > I could successfully build and run (to some extend) PVSB 5.2 (thanks Andy > and Chuck for your help!) but I have now noticed an issue with the > installation of the PVSB project. Concretely, "make install" in the PVSB > 5.2 build directory does not install properly all the expected modules and > plugins (SurfaceLIC.so being a good example). > > All plugins are correctly built and available in my build directory > "my_build_directory/install/lib/paraview-5.2" (for instance > libSurfaceLIC.so) > However, there are missing in my install directory > "my_install_directory/lib/paraview-5.2" after "make install". > > When I connect the pvserver located in "my_install_directory/bin/pvserver" > to my client, only one plugin is present in the plugin manager on the remote > side under the tools tab, whereas the client include the usual list. The > same operation using the pvserver located in > "my_build_directory/install/bin/pvserver" shows all expected plugins on both > the client and server side. > > Andy proposed to run a small test which illustrates further the issue with a > missing module: > >> cat test.py > from paraview.simple import * > w = Wavelet() > Show() > Render() > >> mpirun -np 2 my_build_directory/install/bin/pvbatch -display :0.0 test.py > > returns normally whereas pvbatch from the install directory returns this > error: > >> mpirun -np 2 my_install_directory/bin/pvbatch -display :0.0 test.py > Error: Could not import vtkCommonComputationalGeometry > Traceback (most recent call last): > File "test.py", line 1, in > from paraview.simple import * > File > "my_install_directory/lib/python2.7/site-packages/paraview/simple.py", line > 43, in > from paraview import servermanager > File > "my_install_directory/lib/python2.7/site-packages/paraview/servermanager.py", > line 53, in > from paraview import vtk > File > "my_install_directory/lib/python2.7/site-packages/paraview/vtk/__init__.py", > line 7, in > from paraview.vtk.vtkCommonCore import * > File > "/my_install_directory/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", > line 9, in > from vtkCommonCorePython import * > ImportError: No module named vtkCommonCorePython > > The current sha key of my PVSB 5.2 source directory is > 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16 (Jan 31). > Please let me know if I am missing something here. > Note also that this "make install" issue is not present for the PV 5.2 > project but only for the PVSB 5.2 project. > > Thank you for your help. > > Best regards, > > Michel > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Sat Feb 11 17:56:26 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Feb 2017 17:56:26 -0500 Subject: [Paraview] [EXTERNAL] Re: [Paraview-developers] Scripting image compression parameters In-Reply-To: References: <485e1ce5e1b2419db1c4a3387767ae3a@ES01AMSNLNT.srn.sandia.gov> Message-ID: Faiz, The Python trace is not expected to record application-level settings. For some settings, it could possibly be reasonable to record them in a trace and play them back, but other settings it doesn't make much sense because they require an application restart, for example, or only affect aspects of the user interface. Best, Cory On Tue, Feb 7, 2017 at 4:57 PM, Faiz Abidi wrote: > You mean create a bug ticket? > > Let me try to clarify a bit more on what I am doing. I am using my Ubuntu > machine for this. > > 1. I start the trace just like normal from "Tools -> Start Trace". I choose > all properties to track. > 2. I go to "Edit -> Settings -> Render View" and select settings from the > "Remote/Parallel Rendering Options." > 3. I stop trace, but nothing actually gets traced. > > Does this make sense? I am not sure if this is a bug, or the trace > functionality was never meant to trace the settings but only the properties > of the scene. > > If you or anyone has any more insights to this, please do share. I won't > mind writing my own scripts to do this if it is even possible. > > On Mon, Feb 6, 2017 at 9:14 PM, Scott, W Alan wrote: >> >> Sounds like a bug. Mind writing it up? If you want, if you give me step >> by step details on what is failing, I can also write it up for you. >> >> >> >> Alan >> >> >> >> From: Faiz Abidi [mailto:fabidi89 at vt.edu] >> Sent: Friday, February 3, 2017 10:13 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org; paraview at paraview.org >> Subject: Re: [EXTERNAL] Re: [Paraview-developers] Scripting image >> compression parameters >> >> >> >> Hi Alan, >> >> >> >> Sorry for a delayed response, but I missed this email somehow. >> >> >> >> So, I actually have tried the trace function ParaView supports, but >> unfortunately, it doesn't trace the settings I set for the image compression >> settings. >> >> >> >> I guess I'll have to do it manually then, but I would be interested to >> know if anyone else has tried to script the compression parameters. I am >> kind of surprised if this is not possible to script. >> >> >> >> Best, >> >> >> >> On Mon, Jan 30, 2017 at 4:55 PM, Scott, W Alan wrote: >> >> My best guess would be to try to trace the save screenshot functionality, >> and see what is set. Sorry, that?s the best I have... >> >> >> >> Alan >> >> >> >> From: Paraview-developers >> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Faiz Abidi >> Sent: Monday, January 30, 2017 2:14 PM >> To: paraview-developers at paraview.org; paraview at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Scripting image compression >> parameters >> >> >> >> Not having heard back from anyone, I am guessing no one has done this kind >> of scripting before? Anyone? >> >> >> >> On Wed, Jan 25, 2017 at 9:43 AM, Faiz Abidi wrote: >> >> Hello ParaView community, >> >> >> >> ParaView provides various image compression configuration options. I was >> wondering how to go about scripting this so that I can test setting various >> parameters in a script. >> >> >> >> I did check some of ParaView modules but couldn't find anything helpful. >> >> >> >> Any pointers from anyone would be helpful. >> >> >> >> Best, >> -- >> >> 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 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 fredericperez1 at gmail.com Sat Feb 11 18:02:57 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Sun, 12 Feb 2017 00:02:57 +0100 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: Hi, I have been looking closely into this problem in the past few days, and I have never been able to make the Xdmf3 reader to JOIN any HDF5 data. Neither with the JOIN() syntax nor with the "$0|$1" one. At least to populate an Attribute's DataItem. The Xdmf2 reader works until 10 elements are joined. To go further in this investigation, could someone point me to the source code of the Xdmf3 reader, specifically where the "joining" takes place? Cheers Fred 2017-02-08 23:24 GMT+01:00 Frederic Perez : > I must have done something wrong in my previous attempt with Xdmf3, > because it no longer crashes. Note that it works even without your > suggestion, as the JOIN() syntax works. > > Now the problem is that, when I click "Apply", I get the following error: > "Failed to locate selected scalars. Will use image scalars by default > No scalar values found for texture input!" > > Note that the same exact file works with Xdmf instead of Xdmf3. > > Fred > > > 2017-02-08 22:54 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) > : >> I think that is because Xdmf3 uses different syntax for concatenation. Try using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader. >> >> -Andrew Burns >> >> -----Original Message----- >> From: Frederic Perez [mailto:fredericperez1 at gmail.com] >> Sent: Wednesday, February 08, 2017 4:50 PM >> To: Burns, Andrew J CTR USARMY RDECOM ARL (US) >> Cc: paraview at paraview.org >> Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash with JOIN >> >> I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply". >> >> Fred >> >> 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) >> : >>> Are you using the Xdmf2 or Xdmf3 reader? >>> >>> 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 >>> Frederic Perez >>> Sent: Wednesday, February 08, 2017 3:39 PM >>> To: paraview at paraview.org >>> Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with >>> JOIN >>> >>> 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. >>> >>> >>> >>> >>> ---- >>> >>> Hi all, >>> >>> I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. >>> >>> >>> >>> >>> >> TopologyType="2DCoRectMesh" Dimensions="21 10"/> >>> >>> >> Dimensions="2">0.0 0.0 >>> >> Dimensions="2">0.3 0.06 >>> >>> >>> >> Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10"> >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000002/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000007/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000012/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000017/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000022/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000027/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000032/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000037/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000042/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000047/By >>> >>> >>> >>> >>> >>> >>> However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". >>> >>> Is there a reason for this? Am I doing something wrong? Is there a workaround? >>> >>> Cheers >>> Fred >>> _______________________________________________ >>> Powered by Caution-www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> 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 >>> >>> Search the list archives at: >>> Caution-http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> Caution-http://public.kitware.com/mailman/listinfo/paraview From fabidi89 at vt.edu Sat Feb 11 18:40:33 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Sat, 11 Feb 2017 18:40:33 -0500 Subject: [Paraview] [EXTERNAL] Re: [Paraview-developers] Scripting image compression parameters In-Reply-To: References: <485e1ce5e1b2419db1c4a3387767ae3a@ES01AMSNLNT.srn.sandia.gov> Message-ID: I see your point, and that's what I figured too. The trace is not meant to track those settings. Not sure what path I'll take from here, either try to somehow custom script the image compression parameters or do it manually (a big pain!). Thanks for your help though. On Sat, Feb 11, 2017 at 5:56 PM, Cory Quammen wrote: > Faiz, > > The Python trace is not expected to record application-level settings. > For some settings, it could possibly be reasonable to record them in a > trace and play them back, but other settings it doesn't make much > sense because they require an application restart, for example, or > only affect aspects of the user interface. > > Best, > Cory > > > On Tue, Feb 7, 2017 at 4:57 PM, Faiz Abidi wrote: > > You mean create a bug ticket? > > > > Let me try to clarify a bit more on what I am doing. I am using my Ubuntu > > machine for this. > > > > 1. I start the trace just like normal from "Tools -> Start Trace". I > choose > > all properties to track. > > 2. I go to "Edit -> Settings -> Render View" and select settings from the > > "Remote/Parallel Rendering Options." > > 3. I stop trace, but nothing actually gets traced. > > > > Does this make sense? I am not sure if this is a bug, or the trace > > functionality was never meant to trace the settings but only the > properties > > of the scene. > > > > If you or anyone has any more insights to this, please do share. I won't > > mind writing my own scripts to do this if it is even possible. > > > > On Mon, Feb 6, 2017 at 9:14 PM, Scott, W Alan > wrote: > >> > >> Sounds like a bug. Mind writing it up? If you want, if you give me > step > >> by step details on what is failing, I can also write it up for you. > >> > >> > >> > >> Alan > >> > >> > >> > >> From: Faiz Abidi [mailto:fabidi89 at vt.edu] > >> Sent: Friday, February 3, 2017 10:13 AM > >> To: Scott, W Alan > >> Cc: paraview-developers at paraview.org; paraview at paraview.org > >> Subject: Re: [EXTERNAL] Re: [Paraview-developers] Scripting image > >> compression parameters > >> > >> > >> > >> Hi Alan, > >> > >> > >> > >> Sorry for a delayed response, but I missed this email somehow. > >> > >> > >> > >> So, I actually have tried the trace function ParaView supports, but > >> unfortunately, it doesn't trace the settings I set for the image > compression > >> settings. > >> > >> > >> > >> I guess I'll have to do it manually then, but I would be interested to > >> know if anyone else has tried to script the compression parameters. I am > >> kind of surprised if this is not possible to script. > >> > >> > >> > >> Best, > >> > >> > >> > >> On Mon, Jan 30, 2017 at 4:55 PM, Scott, W Alan > wrote: > >> > >> My best guess would be to try to trace the save screenshot > functionality, > >> and see what is set. Sorry, that?s the best I have... > >> > >> > >> > >> Alan > >> > >> > >> > >> From: Paraview-developers > >> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Faiz > Abidi > >> Sent: Monday, January 30, 2017 2:14 PM > >> To: paraview-developers at paraview.org; paraview at paraview.org > >> Subject: [EXTERNAL] Re: [Paraview-developers] Scripting image > compression > >> parameters > >> > >> > >> > >> Not having heard back from anyone, I am guessing no one has done this > kind > >> of scripting before? Anyone? > >> > >> > >> > >> On Wed, Jan 25, 2017 at 9:43 AM, Faiz Abidi wrote: > >> > >> Hello ParaView community, > >> > >> > >> > >> ParaView provides various image compression configuration options. I was > >> wondering how to go about scripting this so that I can test setting > various > >> parameters in a script. > >> > >> > >> > >> I did check some of ParaView modules but couldn't find anything helpful. > >> > >> > >> > >> Any pointers from anyone would be helpful. > >> > >> > >> > >> Best, > >> -- > >> > >> 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 > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView 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. > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.dimitrova at helsinki.fi Sun Feb 12 07:31:40 2017 From: maria.dimitrova at helsinki.fi (Dimitrova, Maria) Date: Sun, 12 Feb 2017 12:31:40 +0000 Subject: [Paraview] Copying representation properties In-Reply-To: References: , Message-ID: Thank you, maybe the problem only exists in the Windows version. Best regards, Maria Dimitrova ________________________________ From: Cory Quammen Sent: 12 February 2017 00:30:58 To: Mathieu Westphal Cc: Dimitrova, Maria; paraview at paraview.org Subject: Re: [Paraview] Copying representation properties FWIW, I just tried this with 5.2.0 official binaries on Mac OS X and copy/paste of representation properties worked fine. On Fri, Feb 10, 2017 at 7:15 AM, Mathieu Westphal > wrote: Hello I will not be able to test this version right away, will let you know. Mathieu Westphal On Fri, Feb 10, 2017 at 1:06 PM, Dimitrova, Maria > wrote: Hello, Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL version - 5.2.0-RC4. Best regards, Maria Dimitrova ________________________________ From: Mathieu Westphal > Sent: 10 February 2017 13:44:37 To: Dimitrova, Maria Cc: paraview at paraview.org Subject: Re: [Paraview] Copying representation properties Hello I just checked, to copy->Paste feature is working perfectly on ParaView master git. Which version of ParaView are you using ? Regards, Mathieu Westphal On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria > wrote: Dear all, Is there a way to copy the properties of the representation that is applied to a filter to another instance of the same filter? In my project I use 3D glyphs with sphere size 0.03 and blue colour. I have tried right-clicking on the existing filter -> Copy, then Paste to the new instance of the filter but the representation is not affected. Also, another part of my project involves applying Surface LIC with a particular colour scheme and colour range, as well as contrast adjustments and antialiasing, all of which are identical for all the files I need to process. It would save some time if I could just make a custom representation. Thank you very much! Best regards, Maria _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 christophe.mouton at edf.fr Mon Feb 13 04:12:42 2017 From: christophe.mouton at edf.fr (MOUTON Christophe) Date: Mon, 13 Feb 2017 09:12:42 +0000 Subject: [Paraview] Web3D 2017 ACM conference - Papers Deadline Extended to 27 Feb 2017 References: <045f01d2858f$4526e480$cf74ad80$@web3d.org> Message-ID: Dear All, Sorry for multiple postings. The deadline for scientific and technical communications to Web3D 2017 is extended to 27th February 2017. Scientific, medical visualization with VR and/or thanks/on the web are tremendous topics! Submissions of Papers, posters and proposals for workshops and tutorials are very welcomed! Kind regards Christophe CALL FOR PAPERS, POSTERS, TUTORIALS AND WORKSHOPS Papers and Posters Deadline Extended to 27 Feb 2017 Web3D 2017: 22nd International Conference on 3D Web Technology Sponsored by ACM SIGGRAPH in Co-operation with Web3D Consortium Date: 5-7 June 2017 Location: Queensland University of Technology, Brisbane, Australia Website: http://web3d2017.org The 22nd International Conference on 3D Web Technology (Web3D 2017) continues to address an extensive range of research, development, and practice related to Web-based 3D Graphics. 2017 will be a historic year for 3D on the Web. We are seeing the explosion of WebVR and the potential of WebAR just around the corner. With WebGL now widely supported by default in modern browsers, tools such as X3D, X3DOM, Cobweb, three.js, glTF, and A-Frame VR are allowing nearly anyone to create Web3D content. Commercial game engines such as Unity and Unreal are starting to offer ways to export and publish directly to Web3D. The conference will explore topics including: research on simulation and training using Web3D, enabling technology of web-aware, interactive 3D graphics from mobile devices up to high-end immersive environments, and the use of ubiquitous multimedia across a wide range of applications and environments. For example: ? Virtual Reality (VR) ? Mixed Augmented Reality (MAR) ? Cultural and Natural Heritage ? Medical, Telemedicine (eHealth) ? Transportation and Geospatial ? Industry Applications ? Archival Digital Publications ? Human Animation, Motion Capture ? 3D Printing and 3D Scanning ? CAD and Advanced Manufacturing ? Education and E-learning ? Collaboration and Annotation ? Tourism and Accessibility ? Gaming and Entertainment ? Creativity and Digital Art ? Public Sector (Open Government) ? Open Web Platform Integration ? Novel Capabilities For the 2017 conference edition, we welcome works addressing the emerging opportunities and research of portable, integrated information spaces over the web including, but not limited to: ? Emerging WebVR and WebAR capabilities. ? Scalable, interoperable representations and modeling methods for complex geometry, structure, and behaviors. ? 3D similarity search and matching, 3D search interfaces, sketch-based approaches. ? Visualization and exploration of 3D object repositories. ? Scientific and medical visualization, medical simulation and training. ? 3D content creation, analysis tools and pipelines, and 3D classification. ? Annotation, metadata, hyperlinking and Semantic Web for 3D objects and scenes. ? Generative and example-based shape modeling and optimization. ? 3D scanning, 3D reconstruction 3D digitization, and 3D printing. ? Streaming and rendering of large-scale models, animations, and virtual worlds. ? Progressive 3D compression and model optimization. ? Collaborative operation and distributed virtual environments. ? Web-wide human-computer interaction and 3D User Interfaces. ? 3D City Models, Building Information Modeling & Geo-visualization. ? Mixed and Augmented Reality (MAR) including standardization aspects. ? Web3D and associated APIs, toolkits, and frameworks. ? Novel Web3D interaction paradigms for mobile/handheld applications. ? Web based interaction techniques including gesture, pen and voice. ? Agents, animated humanoids, and complex reactive characters. ? Motion capture for composition and streaming of behaviors and expressions. ? Web3D for social networking. ? Script algorithms and programming for lightweight Web3D. ? Network transmission over mobile Internet. ? Server-side 3D engines and cloud-based gaming. ? Architecture support by large Web3D applications for CAD tools and solid modelers. ? Data analysis and intelligent algorithms for big Web3D data. ? Interactive Web 3D applications in all applications and sectors. Papers Submission Instructions: Deadline extended - 27 February 2017 Authors are invited to submit full papers (up to 9 pages, including figures and references) or short papers (up to 4 pages, including figures and references) in PDF format via the Submission Site: http://web3d2017.web3d.org/submissions/papers Papers must be formatted using the document templates for conferences sponsored by ACM SIGGRAPH (see http://www.siggraph.org/learn/instructions-authors). All submissions will be peer-reviewed for quality and contribution by the conference International Program Committee. Poster Submission Instructions: Deadline extended - 27 February 2017 Posters present results of ongoing work in relevant areas of Web3D research and application. The poster format offers the opportunity to interactively present and discuss interesting results to the Web3D community. We particularly encourage contributions that take advantage of the nature of the poster space to present and raise awareness of the work in effective and imaginative ways. Authors submitting posters should provide a poster abstract that gives a concise description of the main idea, its findings, and next steps. The abstract should include supportive data, and a brief discussion of the most relevant related work from the literature and state where the presented work extends. Submissions will be reviewed by the Program Committee for contribution and interest to conference topics. For more information, please see the poster submission instructions at http://web3d2017.web3d.org/submissions/posters Tutorial and Workshop Submission Instructions: Deadline 4 April 2017 Tutorials on specific related topics and panels on challenging areas are encouraged. As in previous years, Web3D 2017 will also feature a number of co-located Workshop sessions. The series of Workshops and Tutorials are intended to provide a forum for researchers and practitioners from both the Web and 3D graphics communities to discuss and exchange positions on current and emergent 3D Web topics. For more details about Workshops: http://web3d2017.web3d.org/submissions/workshops For more details about Tutorials: http://web3d2017.web3d.org/submissions/tutorials H-Anim Competition Deadline: 1 May 2017 This annual competition is dedicated to showing how H-Anim and X3D Graphics standards can be used for creating music videos. This competition is organized by the Korean Standards Association (KSA), Web3D Consortium, and Korean National Radio Research Agency (RRA) with support by the Korea Society for Standards and Standardization (SSS). Each entry is judged on the following: originality, creativity of 3D character animation, creativity of the virtual stage, use of H-Anim ISO/IEC 19774 specification (LOA1, LOA2, LOA3) for character models, and use of the X3D Graphics capabilities. PRIZES: KSA PRIZE (1st place), SSS PRIZE (2nd place), Web3D PRIZE (3rd place) Winners will be announced at 2017 Web3D Conference, Brisbane Australia, 5-7 June 2017. Winners do not need to be in attendance to receive their prize, and will be contacted by Web3D organizers. Prizes will be provided to winners in the form of cash or merchandise valued at approximately $1000 US (tax included). For more details about H-Anim Competition: http://web3d2017.web3d.org/h-anim-competition/ Please send your submission to: competition-submissions at web3.org Important Dates Papers/Posters Submission Deadline: 27 February 2017 (Deadline extended) Papers/Posters Notification: 27 March 2017 Tutorial/Workshop Deadline: 3 March 2017 Tutorial/Workshop Notification: 4 April 2017 Camera-ready Papers/Posters: 4 April 2017 H-Anim Competition Entry: 1 May 2017 Contact Information Program Chairs Vince Marchetti, KShell Analysis & Web3D Consortium, USA Jakub Floty?ski, Pozna? University of Economics and Business, Poland Chris Thorne, Systemic, Australia Tutorials Chairs Sandy Ressler, NIST, USA Erik Champion, Curtin University, Australia Workshop Chairs Tony Huang, University of Tasmania, Australia Sean O?Donoghue, CSIRO & The Garvan Institute, Australia Digital Art Exhibition Chairs June Kim, University of New South Wales, Australia Ina Conradi Chavez, NTU General Chairs Matt Adcock, Commonwealth Scientific and Industrial Research Organisation (CSIRO), Australia Tomasz Bednarz, CSIRO Data61 & Queensland University of Technology, Australia Communications/Outreach Chairs Anita Havele, Web3D Consortium, USA Angela Cheng, Khronos Group, USA Xavier Ho, CSIRO & The University of Sydney, Australia Steering Committee Anita Havele, Executive Director, Web3D Consortium, USA Don Brutzman, Naval Postgraduate School, USA Nicholas F. Polys, Virginia Tech, USA _______________________________________________ Web3d2017-planning mailing list Web3d2017-planning at web3d.org http://web3d.org/mailman/listinfo/web3d2017-planning_web3d.org Ce message et toutes les pi?ces jointes (ci-apr?s le 'Message') sont ?tablis ? l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme ? sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'?tes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez re?u ce Message par erreur, merci de le supprimer de votre syst?me, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions ?galement d'en avertir imm?diatement l'exp?diteur par retour du message. Il est impossible de garantir que les communications par messagerie ?lectronique arrivent en temps utile, sont s?curis?es ou d?nu?es de toute erreur ou virus. ____________________________________________________ This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yzhzhang at ipe.ac.cn Mon Feb 13 05:23:45 2017 From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=) Date: Mon, 13 Feb 2017 18:23:45 +0800 (GMT+08:00) Subject: [Paraview] what is the difference between OpenGL rendering backend and OpenGL2 rendering backend when they communicate with the X Window System? Message-ID: <1fde4ce.ed43.15a36ffeaa2.Coremail.yzhzhang@ipe.ac.cn> Hello, For a long time I have a problem using ParaView 5.2.0 in the client-server mode. However, at the same time, I can use ParaView 4.4.0 in this mode on the same machine. Recently I have built several different versions of ParaView, including 4.3.1, 4.4.0, 5.1.2, 5.2.0, on the same machine and with almost the same compilation options (the only difference among the buildings is the rendering backend), and I found that when built with OpenGL rendering backend, all the versions, including 5.1.2 and 5.2.0, can work normally, in both standalone mode and client-server mode. But when 5.1.2 and 5.2.0 are built with OpenGL2 rendering backend, they can't work. The machine is a node of a HPC system, so I connect to it via realVNC. If I start the paraview execuble by typing ./paraview, I get this output: Segmentation fault (core dumped) If I connect to the node via ssh, and type ./paraview , then I get: paraview: cannot connect to X server I know this is because I didn't start the X for the paraview, this test is just for comparison. If I connect to the node via ssh, and type ./paraview -display :0 , then I get: X Error: GLXBadContext 144 Extension: 135 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x36001bc ERROR: In /root/Desktop/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 629 vtkXOpenGLRenderWindow (0x339c550): GLEW could not be initialized. Segmentation fault (core dumped) If I connect to the node via ssh, and type ./pvserver and connect to it from the paraview GUI on my PC, then I get: Display is not accessible on the server side. Remote rendering will be disabled. This means if I dont't use the rendering feature on the node, other features of the ParaView can be used normally. If I connect to the node via ssh, and type ./pvserver -display :0, and connect to it from the paraview GUI on my PC, then I get lots of errors on the client side, like this: ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x1973c70): Socket error in call to send. Broken pipe. And on the server side, the errors are: X Error of failed request: GLXBadContext Major opcode of failed request: 135 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 28 Current serial number in output stream: 28 >From all the tests, I think it's reasonable to guess that the problem lies in the X Window system and the OpenGL2 rendering backend. The operation system of the node is CentOS 6.3 and the X Window System was installed using "yum groupinstall". The GPU on the node is Tesla C2050 and the driver version is 331.67. The output from "glxinfo | grep OpenGL" is as follow: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Tesla C2050/PCIe/SSE2 OpenGL version string: 4.4.0 NVIDIA 331.67 OpenGL shading language version string: 4.40 NVIDIA via Cg compiler OpenGL extensions: Is there anything wrong with the setting? Why does ParaView with OpenGL rendering backend work on it but that with OpenGL2 not work? Any help or reply is highly appreciated! -Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Mon Feb 13 05:45:10 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Mon, 13 Feb 2017 10:45:10 +0000 Subject: [Paraview] Cataylst pipeline not updating Message-ID: Back with another question! I have a pipeline that has 1 input and 4 outputs. The simplest is a IntegrateVariables filter hooked up to the input. Another branch of the pipeline goes through several PythonCalculator filters and a CellDataToPointData filter and then arrives at the three outputs: 1. The CD2PD filter is connected to a Contour filter with a single level, X. This is then connected to an IntegrateVariables filter (used to compute the area of the Contour) and a Writer. 2. The CD2PD filter is also connected to another Contour filter with a single level Y. This is connected to an IntegrateVariables and Writer just as in 1. 3. The CD2PD filter is sliced two times with each slice in a different render view to save images. I have the coprocessor running every delta_t seconds. The initial IntegrateVariables filter is updated with UpdatePipeline and then the values are saved to disk. This works every step, no issues. I then call UpdatePipeline on both of the Contour and both of the IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the IntegrateVariables exceeds a threshold, and if it does, I save the Contour's to disk as a VTK file. This is not working correctly. If I start the simulation from a point where the Contour's exist in the flow already, then everything works great and the Area field changes in time and it saves the Contour's. However, if the simulation starts without the Contours already in the flow, the Area fields stay zero forever. It's as if the pipeline isn't updating or something. I have attached the DoCoProcessing function used. I don't see anything immediately obvious that would prevent it from updating or getting the correct values for the Area. Am I missing something about how the pipeline or contour filters update? Thanks, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: processing_method.py Type: text/x-python Size: 3599 bytes Desc: processing_method.py URL: From ken.martin at kitware.com Mon Feb 13 08:13:23 2017 From: ken.martin at kitware.com (Ken Martin) Date: Mon, 13 Feb 2017 08:13:23 -0500 Subject: [Paraview] what is the difference between OpenGL rendering backend and OpenGL2 rendering backend when they communicate with the X Window System? In-Reply-To: <1fde4ce.ed43.15a36ffeaa2.Coremail.yzhzhang@ipe.ac.cn> References: <1fde4ce.ed43.15a36ffeaa2.Coremail.yzhzhang@ipe.ac.cn> Message-ID: OPenGL 4.4 is plenty and that card should support the new backend. My first thought would be to try updating the nvidia driver as it is pretty old. On Mon, Feb 13, 2017 at 5:23 AM, ??? wrote: > > > Hello, > > For a long time I have a problem using ParaView 5.2.0 in the client-server > mode. However, at the same time, I can use ParaView 4.4.0 in this mode on > the same machine. Recently I have built several different versions of > ParaView, including 4.3.1, 4.4.0, 5.1.2, 5.2.0, on the same machine and > with almost the same compilation options (the only difference among the > buildings is the rendering backend), and I found that when built with > OpenGL rendering backend, all the versions, including 5.1.2 and 5.2.0, can > work normally, in both standalone mode and client-server mode. But when > 5.1.2 and 5.2.0 are built with OpenGL2 rendering backend, they can't work. > The machine is a node of a HPC system, so I connect to it via realVNC. If I > start the paraview execuble by typing ./paraview, I get this output: > > Segmentation fault (core dumped) > > If I connect to the node via ssh, and type ./paraview , then I get: > > paraview: c annot connect to X server > > I know this is because I didn't start the X for the paraview, this test is > just for comparison. > > If I connect to the node via ssh, and type ./paraview -display :0 , then I > get: > > X Error: GLXBadContext 144 > Extension: 135 (Uknown extension) > Minor opcode: 5 (Unknown request) > Resource id: 0x36001bc > ERROR: In /root/Desktop/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 629 > vtkXOpenGLRenderWindow (0x339c550): GLEW could not be initialized. > > > Segmentation fault (core dumped) > > If I connect to the node via ssh, and type ./pvserver and connect to it > from the paraview GUI on my PC, then I get: > > Display is not accessible on the server side. > > Remote rendering will be disabled. > > > This means if I dont't use the rendering feature on the node, other > features of the ParaView can be used normally. > > > If I connect to the node via ssh, and type ./pvserver -display :0, and > connect to it from the paraview GUI on my PC, then I get lots of errors on > the client side, like this: > > ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash- > linux-shared-release_opengl2_qt4_superbuild/source- > paraview/VTK/Common/System/vtkSocket.cxx, line 572 > vtkClientSocket (0x1973c70): Socket error in call to send. Broken pipe. > > And on the server side, the errors are: > > X Error of failed request: GLXBadContext > Major opcode of failed request: 135 (GLX) > Minor opcode of failed request: 5 (X_GLXMakeCurrent) > Serial number of failed request: 28 > Current serial number in output stream: 28 > > From all the tests, I think it's reasonable to guess that the problem lies > in the X Window system and the OpenGL2 rendering backend. The operation > system of the node is CentOS 6.3 and the X Window System was installed > using "yum groupinstall". The GPU on the node is Tesla C2050 and the driver > version is 331.67. The output from "glxinfo | grep OpenGL" is as follow: > > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: Tesla C2050/PCIe/SSE2 > OpenGL version string: 4.4.0 NVIDIA 331.67 > OpenGL shading language version string: 4.40 NVIDIA via Cg compiler > OpenGL extensions: > > Is there anything wrong with the setting? Why does ParaView with OpenGL > rendering backend work on it but that with OpenGL2 not work? > > Any help or reply is 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 > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.j.burns35.ctr at mail.mil Mon Feb 13 08:41:16 2017 From: andrew.j.burns35.ctr at mail.mil (Burns, Andrew J CTR USARMY RDECOM ARL (US)) Date: Mon, 13 Feb 2017 13:41:16 +0000 Subject: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN In-Reply-To: References: Message-ID: In Xdmf3's reader, the assignment of variables occurs in XdmfArray::populateItem. The evaluation of the function occurs in XdmfFunction "|" denotes XdmfFunction::chunk (effectively concatenate). From there it should be a bunch of XdmfArray::insert calls. Xdmf3's source in Paraview is under Paraview/VTK/ThirdParty/xdmf3. 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 Frederic Perez Sent: Saturday, February 11, 2017 6:03 PM To: paraview at paraview.org Subject: Re: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN 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. ---- Hi, I have been looking closely into this problem in the past few days, and I have never been able to make the Xdmf3 reader to JOIN any HDF5 data. Neither with the JOIN() syntax nor with the "$0|$1" one. At least to populate an Attribute's DataItem. The Xdmf2 reader works until 10 elements are joined. To go further in this investigation, could someone point me to the source code of the Xdmf3 reader, specifically where the "joining" takes place? Cheers Fred 2017-02-08 23:24 GMT+01:00 Frederic Perez : > I must have done something wrong in my previous attempt with Xdmf3, > because it no longer crashes. Note that it works even without your > suggestion, as the JOIN() syntax works. > > Now the problem is that, when I click "Apply", I get the following error: > "Failed to locate selected scalars. Will use image scalars by default > No scalar values found for texture input!" > > Note that the same exact file works with Xdmf instead of Xdmf3. > > Fred > > > 2017-02-08 22:54 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) > : >> I think that is because Xdmf3 uses different syntax for concatenation. Try using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader. >> >> -Andrew Burns >> >> -----Original Message----- >> From: Frederic Perez [Caution-mailto:fredericperez1 at gmail.com] >> Sent: Wednesday, February 08, 2017 4:50 PM >> To: Burns, Andrew J CTR USARMY RDECOM ARL (US) >> >> Cc: paraview at paraview.org >> Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash >> with JOIN >> >> I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply". >> >> Fred >> >> 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) >> : >>> Are you using the Xdmf2 or Xdmf3 reader? >>> >>> Andrew Burns >>> Software Engineer | Parsons >>> Phone: 410-306-0409 >>> ARL DSRC >>> andrew.j.burns35.ctr at mail.mil >>> >>> -----Original Message----- >>> From: ParaView [Caution-mailto:paraview-bounces at paraview.org] On >>> Behalf Of Frederic Perez >>> Sent: Wednesday, February 08, 2017 3:39 PM >>> To: paraview at paraview.org >>> Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with >>> JOIN >>> >>> 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. >>> >>> >>> >>> >>> ---- >>> >>> Hi all, >>> >>> I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files. >>> >>> >>> >>> >>> >> TopologyType="2DCoRectMesh" Dimensions="21 10"/> >>> >>> >> Dimensions="2">0.0 0.0 >>> >> Dimensions="2">0.3 0.06 >>> >>> >>> >> Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10"> >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000002/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000007/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000012/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000017/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000022/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000027/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000032/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000037/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000042/By >>> >> Precision="8" Dimensions="21" >>> Format="HDF">mystuff.h5:/0000000047/By >>> >>> >>> >>> >>> >>> >>> However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply". >>> >>> Is there a reason for this? Am I doing something wrong? Is there a workaround? >>> >>> Cheers >>> Fred >>> _______________________________________________ >>> Powered by Caution-Caution-www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> 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 >>> >>> Search the list archives at: >>> Caution-Caution-http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by Caution-www.kitware.com Visit other Kitware open-source projects at 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 Search the list archives at: Caution-http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview From ben.boeckel at kitware.com Mon Feb 13 09:23:41 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 13 Feb 2017 09:23:41 -0500 Subject: [Paraview] PVSB 5.2: missing modules and plugins after "make install" In-Reply-To: References: Message-ID: <20170213142341.GA31880@megas.kitware.com> On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote: > Will updating to the current superbuild master address the missing > plugins issue Michel is seeing? It looks like there have been some > minor changes on plugin handling in linux since > 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16. Yes, it's possible. If you look at the output of the packaging step, there is probably some set of system libraries being pulled into the package which should not be there. --Ben From andy.bauer at kitware.com Mon Feb 13 10:56:35 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 13 Feb 2017 10:56:35 -0500 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: Message-ID: Hi Tim, Try adding in the current time to the UpdatePipeline() calls, e.g. *.UpdatePipeline(datadescription.GetCurrentTime()) It's tough to tell with RequestDataDescription() missing but I assume that DoCoProcessing() is getting called when you want, correct? Let me know if that doesn't solve the problem. Best, Andy On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Back with another question! > > > I have a pipeline that has 1 input and 4 outputs. The simplest is a > IntegrateVariables filter hooked up to the input. Another branch of the > pipeline goes through several PythonCalculator filters and a > CellDataToPointData filter and then arrives at the three outputs: > > > 1. The CD2PD filter is connected to a Contour filter with a single level, > X. This is then connected to an IntegrateVariables filter (used to compute > the area of the Contour) and a Writer. > > 2. The CD2PD filter is also connected to another Contour filter with a > single level Y. This is connected to an IntegrateVariables and Writer just > as in 1. > > 3. The CD2PD filter is sliced two times with each slice in a different > render view to save images. > > > I have the coprocessor running every delta_t seconds. The initial > IntegrateVariables filter is updated with UpdatePipeline and then the > values are saved to disk. This works every step, no issues. > > > I then call UpdatePipeline on both of the Contour and both of the > IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the > IntegrateVariables exceeds a threshold, and if it does, I save the > Contour's to disk as a VTK file. This is not working correctly. > > > If I start the simulation from a point where the Contour's exist in the > flow already, then everything works great and the Area field changes in > time and it saves the Contour's. > > > However, if the simulation starts without the Contours already in the > flow, the Area fields stay zero forever. It's as if the pipeline isn't > updating or something. I have attached the DoCoProcessing function used. I > don't see anything immediately obvious that would prevent it from updating > or getting the correct values for the Area. > > > Am I missing something about how the pipeline or contour filters update? > > > Thanks, > > > Tim > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Mon Feb 13 10:58:28 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 13 Feb 2017 10:58:28 -0500 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: Message-ID: Oops, datadescription.GetTime() instead of datadescription.GetCurrentTime(). On Mon, Feb 13, 2017 at 10:56 AM, Andy Bauer wrote: > Hi Tim, > > Try adding in the current time to the UpdatePipeline() calls, e.g. > *.UpdatePipeline(datadescription.GetCurrentTime()) > > It's tough to tell with RequestDataDescription() missing but I assume that > DoCoProcessing() is getting called when you want, correct? > > Let me know if that doesn't solve the problem. > > Best, > Andy > > On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> Back with another question! >> >> >> I have a pipeline that has 1 input and 4 outputs. The simplest is a >> IntegrateVariables filter hooked up to the input. Another branch of the >> pipeline goes through several PythonCalculator filters and a >> CellDataToPointData filter and then arrives at the three outputs: >> >> >> 1. The CD2PD filter is connected to a Contour filter with a single level, >> X. This is then connected to an IntegrateVariables filter (used to compute >> the area of the Contour) and a Writer. >> >> 2. The CD2PD filter is also connected to another Contour filter with a >> single level Y. This is connected to an IntegrateVariables and Writer just >> as in 1. >> >> 3. The CD2PD filter is sliced two times with each slice in a different >> render view to save images. >> >> >> I have the coprocessor running every delta_t seconds. The initial >> IntegrateVariables filter is updated with UpdatePipeline and then the >> values are saved to disk. This works every step, no issues. >> >> >> I then call UpdatePipeline on both of the Contour and both of the >> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the >> IntegrateVariables exceeds a threshold, and if it does, I save the >> Contour's to disk as a VTK file. This is not working correctly. >> >> >> If I start the simulation from a point where the Contour's exist in the >> flow already, then everything works great and the Area field changes in >> time and it saves the Contour's. >> >> >> However, if the simulation starts without the Contours already in the >> flow, the Area fields stay zero forever. It's as if the pipeline isn't >> updating or something. I have attached the DoCoProcessing function used. I >> don't see anything immediately obvious that would prevent it from updating >> or getting the correct values for the Area. >> >> >> Am I missing something about how the pipeline or contour filters update? >> >> >> Thanks, >> >> >> Tim >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 tim.gallagher at gatech.edu Mon Feb 13 11:06:17 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Mon, 13 Feb 2017 16:06:17 +0000 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: , Message-ID: The RequestDataDescription is the same as the default output from the script generator, so I didn't include it. The DoCoProcessing gets called every time step and the volumeIntegrals data is updated and written correctly every delta_t, so I'm confident in that part. I will add the calls you suggested and re-run. It takes some time for it to evolve to the point something will happen -- I don't have it saving data frequently enough to run a quick test, I was expecting the pipeline to save it for me! The other thing that occurred to me -- is there something about the Contour filter that turns it off/disables it when the pipeline is built and there is no surface at that contour level? Thanks, Tim ________________________________ From: Andy Bauer Sent: Monday, February 13, 2017 10:56 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Cataylst pipeline not updating Hi Tim, Try adding in the current time to the UpdatePipeline() calls, e.g. *.UpdatePipeline(datadescription.GetCurrentTime()) It's tough to tell with RequestDataDescription() missing but I assume that DoCoProcessing() is getting called when you want, correct? Let me know if that doesn't solve the problem. Best, Andy On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P > wrote: Back with another question! I have a pipeline that has 1 input and 4 outputs. The simplest is a IntegrateVariables filter hooked up to the input. Another branch of the pipeline goes through several PythonCalculator filters and a CellDataToPointData filter and then arrives at the three outputs: 1. The CD2PD filter is connected to a Contour filter with a single level, X. This is then connected to an IntegrateVariables filter (used to compute the area of the Contour) and a Writer. 2. The CD2PD filter is also connected to another Contour filter with a single level Y. This is connected to an IntegrateVariables and Writer just as in 1. 3. The CD2PD filter is sliced two times with each slice in a different render view to save images. I have the coprocessor running every delta_t seconds. The initial IntegrateVariables filter is updated with UpdatePipeline and then the values are saved to disk. This works every step, no issues. I then call UpdatePipeline on both of the Contour and both of the IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the IntegrateVariables exceeds a threshold, and if it does, I save the Contour's to disk as a VTK file. This is not working correctly. If I start the simulation from a point where the Contour's exist in the flow already, then everything works great and the Area field changes in time and it saves the Contour's. However, if the simulation starts without the Contours already in the flow, the Area fields stay zero forever. It's as if the pipeline isn't updating or something. I have attached the DoCoProcessing function used. I don't see anything immediately obvious that would prevent it from updating or getting the correct values for the Area. Am I missing something about how the pipeline or contour filters update? Thanks, Tim _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 w.h.greene at gmail.com Mon Feb 13 11:09:12 2017 From: w.h.greene at gmail.com (Bill Greene) Date: Mon, 13 Feb 2017 11:09:12 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 Message-ID: I have been using Paraview 4 on my windows 7 computer for quite a while now but wanted to upgrade to Paraview 5. Installation appeared to work fine but when I display a model I am seeing a rendering problem that I don't see in Paraview 4. If Representation=Surface and Coloring=Solid Color, the object is black regardless of how the color is defined. If Rep=Surface with Edges, the edges do appear over the black object. If I select one of the results vectors under Coloring, the color bar is displayed and looks correct; but the object remains black. I know that the graphics card in the computer is somewhat old ( the drivers are the latest for the device) but have no idea if that is related to the problem I'm seeing. I'm wondering if others have encountered this problem or if there is some setting I can change to avoid it. Thanks, Bill Greene From cory.quammen at kitware.com Mon Feb 13 11:14:52 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Feb 2017 11:14:52 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 In-Reply-To: References: Message-ID: Hi Bill, It sounds like the rendering backend isn't fully supported on your graphics card/driver combo. What kind of card is it? Are you getting any error messages? Thanks, Cory On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene wrote: > I have been using Paraview 4 on my windows 7 computer for quite a while > now but wanted to upgrade to Paraview 5. > > Installation appeared to work fine but when I display a model I am seeing > a rendering problem that I don't see in Paraview 4. If Representation=Surface > and Coloring=Solid Color, the object is black regardless of how the > color is defined. If Rep=Surface with Edges, the edges do appear over the > black object. If I select one of the results vectors under Coloring, the > color bar is displayed and looks correct; but the object remains black. > > I know that the graphics card in the computer is somewhat old ( the drivers > are the latest for the device) but have no idea if that is related to > the problem > I'm seeing. > > I'm wondering if others have encountered this problem or if there is > some setting I > can change to avoid it. > > Thanks, > > Bill Greene > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 adershowitz at exponent.com Mon Feb 13 11:19:46 2017 From: adershowitz at exponent.com (Adam Dershowitz) Date: Mon, 13 Feb 2017 16:19:46 +0000 Subject: [Paraview] Paraview crashes with netCDF In-Reply-To: <12E0D357-BDEC-499D-B545-538EAADDA1A6@exponent.com> References: <12E0D357-BDEC-499D-B545-538EAADDA1A6@exponent.com> Message-ID: I found a bit more information. When pareview crashes, here is part of the crash log: Application Specific Information: terminating with uncaught exception of type std::out_of_range: basic_string abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fffcb43add6 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fffcb526787 pthread_kill + 90 2 libsystem_c.dylib 0x00007fffcb3a0420 abort + 129 3 libc++abi.dylib 0x00007fffc9efb85a abort_message + 266 4 libc++abi.dylib 0x00007fffc9f20c37 default_terminate_handler() + 243 5 libobjc.A.dylib 0x00007fffcaa2af33 _objc_terminate() + 124 6 libc++abi.dylib 0x00007fffc9f1dd69 std::__terminate(void (*)()) + 8 7 libc++abi.dylib 0x00007fffc9f1d9f2 __cxa_rethrow + 99 8 QtCore 0x000000010db17d2d QEventLoop::exec(QFlags) + 845 9 QtCore 0x000000010db1ad97 QCoreApplication::exec() + 199 10 org.paraview.ParaView 0x000000010b083fd2 main + 386 11 libdyld.dylib 0x00007fffcb30c255 start + 1 Any idea why that happens with one feet, but not meters in an otherwise identical file? -- Adam From: Dershowitz Adam Date: Tuesday, February 7, 2017 at 11:58 AM To: "ParaView at paraview.org" Subject: Paraview crashes with netCDF I have a geotiff file that I want to view in Paraview. But, Paraview seems to not show the correct offset (0,0 instead of respected the offset). The work around I have been trying is to warp it to the correct location using gdalwarp and to export it as a netCDF. Then Paraview should be able to show it correctly. But, I have run into a crash. If I do this: gdalwarp -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc then I try to open test.nc in Paraview immediately crashes. While, instead if do this: gdalwarp -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc then it opens fine. The difference between these two files is that EPSG 3652 uses feet (which is better for me, for this particular project) while 3651 uses meters. Both appear to be valid NetCDF files. I?ve tried both readers ?CAM NetCDF (Unstructured)? and ?NetCDF files generic and CF conventions? with the same results. I?m running Paraview 5.2.0 64-bit on Mac OS 10.12.3. But, I have seen identical results on an older Mac with a prior OS. I had also tried an older version of Paraview with the same result. Any ideas why this consistently crashes Paraview, or what to do about it? Using netCDF was already a work around, and I willing to try others to view these files. The offset and scale are important because I then need to put in other data that is in the correct location and units. The files are too big for me to send to the mailing list, so I have not posted them. Thanks, -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Feb 13 11:30:18 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 13 Feb 2017 11:30:18 -0500 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: Message-ID: Hi Tim, It's possible that there's something funky going on when the data set being passed through parts of the pipeline are empty. I'm hoping for the easy fix with passing in the time since I've know that has caused unexpected behavior before. If that doesn't solve your issue then I'll probably have to do something similar and run it locally to see what's going on. Cheers, Andy On Mon, Feb 13, 2017 at 11:06 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > The RequestDataDescription is the same as the default output from the > script generator, so I didn't include it. The DoCoProcessing gets called > every time step and the volumeIntegrals data is updated and written > correctly every delta_t, so I'm confident in that part. > > > I will add the calls you suggested and re-run. It takes some time for it > to evolve to the point something will happen -- I don't have it saving data > frequently enough to run a quick test, I was expecting the pipeline to save > it for me! > > > The other thing that occurred to me -- is there something about the > Contour filter that turns it off/disables it when the pipeline is built and > there is no surface at that contour level? > > > Thanks, > > > Tim > > > ------------------------------ > *From:* Andy Bauer > *Sent:* Monday, February 13, 2017 10:56 AM > *To:* Gallagher, Timothy P > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Cataylst pipeline not updating > > Hi Tim, > > Try adding in the current time to the UpdatePipeline() calls, e.g. > *.UpdatePipeline(datadescription.GetCurrentTime()) > > It's tough to tell with RequestDataDescription() missing but I assume that > DoCoProcessing() is getting called when you want, correct? > > Let me know if that doesn't solve the problem. > > Best, > Andy > > On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> Back with another question! >> >> >> I have a pipeline that has 1 input and 4 outputs. The simplest is a >> IntegrateVariables filter hooked up to the input. Another branch of the >> pipeline goes through several PythonCalculator filters and a >> CellDataToPointData filter and then arrives at the three outputs: >> >> >> 1. The CD2PD filter is connected to a Contour filter with a single level, >> X. This is then connected to an IntegrateVariables filter (used to compute >> the area of the Contour) and a Writer. >> >> 2. The CD2PD filter is also connected to another Contour filter with a >> single level Y. This is connected to an IntegrateVariables and Writer just >> as in 1. >> >> 3. The CD2PD filter is sliced two times with each slice in a different >> render view to save images. >> >> >> I have the coprocessor running every delta_t seconds. The initial >> IntegrateVariables filter is updated with UpdatePipeline and then the >> values are saved to disk. This works every step, no issues. >> >> >> I then call UpdatePipeline on both of the Contour and both of the >> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the >> IntegrateVariables exceeds a threshold, and if it does, I save the >> Contour's to disk as a VTK file. This is not working correctly. >> >> >> If I start the simulation from a point where the Contour's exist in the >> flow already, then everything works great and the Area field changes in >> time and it saves the Contour's. >> >> >> However, if the simulation starts without the Contours already in the >> flow, the Area fields stay zero forever. It's as if the pipeline isn't >> updating or something. I have attached the DoCoProcessing function used. I >> don't see anything immediately obvious that would prevent it from updating >> or getting the correct values for the Area. >> >> >> Am I missing something about how the pipeline or contour filters update? >> >> >> Thanks, >> >> >> Tim >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 Mon Feb 13 11:33:46 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Feb 2017 11:33:46 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 In-Reply-To: References: Message-ID: Hi Bill, Let's keep the discussion on the mailing list so others can benefit from and contribute to the conversation. Ken, Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa 2010, I believe. It looks like it can support OpenGL 3.2 with Shader 4.1. I'm wondering if there is maybe a subtle shader compilation issue on the ATI hardware? Thanks, Cory On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene wrote: > Thanks for getting back to me so quickly! > > The graphics device is an ATI Radeon HD 4200. > > Nothing is written to the Paraview "Output Messages" window. > Is there someplace else I should look? > > Bill > > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen wrote: >> Hi Bill, >> >> It sounds like the rendering backend isn't fully supported on your >> graphics card/driver combo. What kind of card is it? Are you getting >> any error messages? >> >> Thanks, >> Cory >> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene wrote: >>> I have been using Paraview 4 on my windows 7 computer for quite a while >>> now but wanted to upgrade to Paraview 5. >>> >>> Installation appeared to work fine but when I display a model I am seeing >>> a rendering problem that I don't see in Paraview 4. If Representation=Surface >>> and Coloring=Solid Color, the object is black regardless of how the >>> color is defined. If Rep=Surface with Edges, the edges do appear over the >>> black object. If I select one of the results vectors under Coloring, the >>> color bar is displayed and looks correct; but the object remains black. >>> >>> I know that the graphics card in the computer is somewhat old ( the drivers >>> are the latest for the device) but have no idea if that is related to >>> the problem >>> I'm seeing. >>> >>> I'm wondering if others have encountered this problem or if there is >>> some setting I >>> can change to avoid it. >>> >>> Thanks, >>> >>> Bill Greene >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 cory.quammen at kitware.com Mon Feb 13 11:49:48 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Feb 2017 11:49:48 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download Message-ID: 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. From ken.martin at kitware.com Mon Feb 13 11:54:03 2017 From: ken.martin at kitware.com (Ken Martin) Date: Mon, 13 Feb 2017 11:54:03 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 In-Reply-To: References: Message-ID: That card should be fine. I have seen this type of bug before and updating the driver has fixed it. Specifically updating the driver to the latest from ATI (sometimes computer vendors stop updating their copies). Another way to check what the problem is, is to stick a polydata normals filter in the pipeline and then see if it works. Thanks Ken On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen wrote: > Hi Bill, > > Let's keep the discussion on the mailing list so others can benefit > from and contribute to the conversation. > > Ken, > > Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa > 2010, I believe. It looks like it can support OpenGL 3.2 with Shader > 4.1. I'm wondering if there is maybe a subtle shader compilation issue > on the ATI hardware? > > Thanks, > Cory > > > > On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene > wrote: > > Thanks for getting back to me so quickly! > > > > The graphics device is an ATI Radeon HD 4200. > > > > Nothing is written to the Paraview "Output Messages" window. > > Is there someplace else I should look? > > > > Bill > > > > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen > wrote: > >> Hi Bill, > >> > >> It sounds like the rendering backend isn't fully supported on your > >> graphics card/driver combo. What kind of card is it? Are you getting > >> any error messages? > >> > >> Thanks, > >> Cory > >> > >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene > wrote: > >>> I have been using Paraview 4 on my windows 7 computer for quite a while > >>> now but wanted to upgrade to Paraview 5. > >>> > >>> Installation appeared to work fine but when I display a model I am > seeing > >>> a rendering problem that I don't see in Paraview 4. If > Representation=Surface > >>> and Coloring=Solid Color, the object is black regardless of how the > >>> color is defined. If Rep=Surface with Edges, the edges do appear over > the > >>> black object. If I select one of the results vectors under Coloring, > the > >>> color bar is displayed and looks correct; but the object remains black. > >>> > >>> I know that the graphics card in the computer is somewhat old ( the > drivers > >>> are the latest for the device) but have no idea if that is related to > >>> the problem > >>> I'm seeing. > >>> > >>> I'm wondering if others have encountered this problem or if there is > >>> some setting I > >>> can change to avoid it. > >>> > >>> Thanks, > >>> > >>> Bill Greene > >>> _______________________________________________ > >>> Powered by www.kitware.com > >>> > >>> Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > >>> > >>> Please keep messages on-topic and check the ParaView 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. > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From w.h.greene at gmail.com Mon Feb 13 12:36:38 2017 From: w.h.greene at gmail.com (Bill Greene) Date: Mon, 13 Feb 2017 12:36:38 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 In-Reply-To: References: Message-ID: Thanks for the suggestions! I downloaded the drivers directly from ATI instead of letting Windows do the update and that appears to have fixed the problem I was seeing in Paraview 5.2. Thanks again for the help! Bill On Mon, Feb 13, 2017 at 11:54 AM, Ken Martin wrote: > That card should be fine. I have seen this type of bug before and updating > the driver has fixed it. Specifically updating the driver to the latest from > ATI (sometimes computer vendors stop updating their copies). Another way to > check what the problem is, is to stick a polydata normals filter in the > pipeline and then see if it works. > > Thanks > Ken > > > On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen > wrote: >> >> Hi Bill, >> >> Let's keep the discussion on the mailing list so others can benefit >> from and contribute to the conversation. >> >> Ken, >> >> Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa >> 2010, I believe. It looks like it can support OpenGL 3.2 with Shader >> 4.1. I'm wondering if there is maybe a subtle shader compilation issue >> on the ATI hardware? >> >> Thanks, >> Cory >> >> >> >> On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene >> wrote: >> > Thanks for getting back to me so quickly! >> > >> > The graphics device is an ATI Radeon HD 4200. >> > >> > Nothing is written to the Paraview "Output Messages" window. >> > Is there someplace else I should look? >> > >> > Bill >> > >> > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen >> > wrote: >> >> Hi Bill, >> >> >> >> It sounds like the rendering backend isn't fully supported on your >> >> graphics card/driver combo. What kind of card is it? Are you getting >> >> any error messages? >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene >> >> wrote: >> >>> I have been using Paraview 4 on my windows 7 computer for quite a >> >>> while >> >>> now but wanted to upgrade to Paraview 5. >> >>> >> >>> Installation appeared to work fine but when I display a model I am >> >>> seeing >> >>> a rendering problem that I don't see in Paraview 4. If >> >>> Representation=Surface >> >>> and Coloring=Solid Color, the object is black regardless of how the >> >>> color is defined. If Rep=Surface with Edges, the edges do appear over >> >>> the >> >>> black object. If I select one of the results vectors under Coloring, >> >>> the >> >>> color bar is displayed and looks correct; but the object remains >> >>> black. >> >>> >> >>> I know that the graphics card in the computer is somewhat old ( the >> >>> drivers >> >>> are the latest for the device) but have no idea if that is related to >> >>> the problem >> >>> I'm seeing. >> >>> >> >>> I'm wondering if others have encountered this problem or if there is >> >>> some setting I >> >>> can change to avoid it. >> >>> >> >>> Thanks, >> >>> >> >>> Bill Greene >> >>> _______________________________________________ >> >>> Powered by www.kitware.com >> >>> >> >>> Visit other Kitware open-source projects at >> >>> http://www.kitware.com/opensource/opensource.html >> >>> >> >>> Please keep messages on-topic and check the ParaView 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. > > > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 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. From cory.quammen at kitware.com Mon Feb 13 12:48:03 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Feb 2017 12:48:03 -0500 Subject: [Paraview] Object rendering problem on Windows 7 with Paraview 5.2 In-Reply-To: References: Message-ID: Awesome, thanks for the follow up, Bill. On Mon, Feb 13, 2017 at 12:36 PM, Bill Greene wrote: > Thanks for the suggestions! I downloaded the drivers directly from ATI > instead of letting Windows do the update and that appears to have > fixed the problem I was seeing in Paraview 5.2. > > Thanks again for the help! > > Bill > > On Mon, Feb 13, 2017 at 11:54 AM, Ken Martin wrote: >> That card should be fine. I have seen this type of bug before and updating >> the driver has fixed it. Specifically updating the driver to the latest from >> ATI (sometimes computer vendors stop updating their copies). Another way to >> check what the problem is, is to stick a polydata normals filter in the >> pipeline and then see if it works. >> >> Thanks >> Ken >> >> >> On Mon, Feb 13, 2017 at 11:33 AM, Cory Quammen >> wrote: >>> >>> Hi Bill, >>> >>> Let's keep the discussion on the mailing list so others can benefit >>> from and contribute to the conversation. >>> >>> Ken, >>> >>> Is the ATI Radeon HD 4200 too old for the OpenGL2 backend? It's circa >>> 2010, I believe. It looks like it can support OpenGL 3.2 with Shader >>> 4.1. I'm wondering if there is maybe a subtle shader compilation issue >>> on the ATI hardware? >>> >>> Thanks, >>> Cory >>> >>> >>> >>> On Mon, Feb 13, 2017 at 11:28 AM, Bill Greene >>> wrote: >>> > Thanks for getting back to me so quickly! >>> > >>> > The graphics device is an ATI Radeon HD 4200. >>> > >>> > Nothing is written to the Paraview "Output Messages" window. >>> > Is there someplace else I should look? >>> > >>> > Bill >>> > >>> > On Mon, Feb 13, 2017 at 11:14 AM, Cory Quammen >>> > wrote: >>> >> Hi Bill, >>> >> >>> >> It sounds like the rendering backend isn't fully supported on your >>> >> graphics card/driver combo. What kind of card is it? Are you getting >>> >> any error messages? >>> >> >>> >> Thanks, >>> >> Cory >>> >> >>> >> On Mon, Feb 13, 2017 at 11:09 AM, Bill Greene >>> >> wrote: >>> >>> I have been using Paraview 4 on my windows 7 computer for quite a >>> >>> while >>> >>> now but wanted to upgrade to Paraview 5. >>> >>> >>> >>> Installation appeared to work fine but when I display a model I am >>> >>> seeing >>> >>> a rendering problem that I don't see in Paraview 4. If >>> >>> Representation=Surface >>> >>> and Coloring=Solid Color, the object is black regardless of how the >>> >>> color is defined. If Rep=Surface with Edges, the edges do appear over >>> >>> the >>> >>> black object. If I select one of the results vectors under Coloring, >>> >>> the >>> >>> color bar is displayed and looks correct; but the object remains >>> >>> black. >>> >>> >>> >>> I know that the graphics card in the computer is somewhat old ( the >>> >>> drivers >>> >>> are the latest for the device) but have no idea if that is related to >>> >>> the problem >>> >>> I'm seeing. >>> >>> >>> >>> I'm wondering if others have encountered this problem or if there is >>> >>> some setting I >>> >>> can change to avoid it. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Bill Greene >>> >>> _______________________________________________ >>> >>> Powered by www.kitware.com >>> >>> >>> >>> Visit other Kitware open-source projects at >>> >>> http://www.kitware.com/opensource/opensource.html >>> >>> >>> >>> Please keep messages on-topic and check the ParaView 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. >> >> >> >> >> -- >> Ken Martin PhD >> Chairman & CFO >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> 518 371 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. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From bdutta at vt.edu Mon Feb 13 14:16:03 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Mon, 13 Feb 2017 14:16:03 -0500 Subject: [Paraview] (no subject) Message-ID: Hi All, I am trying to compile Paraview 5.0.0 on Ubuntu 14.04 but I am running into the below compilation issue. My machine is connected to the network (I tested it). Is there something wrong with the kitware URLs? ----------------logs------------------ CMake Error at /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.0.0-source/CMake/ExternalData.cmake:749 (message): Object MD5=b10bd3f7136ef809f1df7ad5c94c553f not found at: http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=b10bd3f7136ef809f1df7ad5c94c553f&algorithm=MD5 ("Couldn't connect to server") http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f ("Couldn't connect to server") Call Stack (most recent call first): /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5.0.0-source/CMake/ExternalData.cmake:771 (_ExternalData_download_object) make[2]: *** [ExternalData/Testing/Data/Baseline/pqCoreBasicApp.png.md5-stamp] Error 1 make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2 make: *** [all] Erro --------------------------------------------------------------------- Also I wanted to run a paraview python script with CPU acceleration. Will this compilation generate pvpython and can I pass it --mesa-llvm for running the script (I assume by default it will use GPU acceleration as I have NVIDIA GPU on my system)? Thank you for this. BR, Bishwajit -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdutta at vt.edu Mon Feb 13 14:18:40 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Mon, 13 Feb 2017 14:18:40 -0500 Subject: [Paraview] (no subject) 5.0.0 Compilation issue Message-ID: Adding subject On Mon, Feb 13, 2017 at 2:16 PM, Bishwajit Dutta wrote: > Hi All, > > I am trying to compile Paraview 5.0.0 on Ubuntu 14.04 but I am running > into the below compilation issue. My machine is connected to the network (I > tested it). > Is there something wrong with the kitware URLs? > > ----------------logs------------------ > > CMake Error at /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5. > 0.0-source/CMake/ExternalData.cmake:749 (message): > Object MD5=b10bd3f7136ef809f1df7ad5c94c553f not found at: > > http://midas3.kitware.com/midas/api/rest?method=midas. > bitstream.download&checksum=b10bd3f7136ef809f1df7ad5c94c553f&algorithm=MD5 > ("Couldn't connect to server") > http://www.paraview.org/files/ExternalData/MD5/ > b10bd3f7136ef809f1df7ad5c94c553f ("Couldn't connect to server") > Call Stack (most recent call first): > /home/bd/gohan_mount/bdutta/PARAVIEW/PV5.0.0/ParaView-v5. > 0.0-source/CMake/ExternalData.cmake:771 (_ExternalData_download_object) > > > make[2]: *** [ExternalData/Testing/Data/Baseline/pqCoreBasicApp.png.md5-stamp] > Error 1 > make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2 > make: *** [all] Erro > > --------------------------------------------------------------------- > > Also I wanted to run a paraview python script with CPU acceleration. Will > this compilation generate > pvpython and can I pass it --mesa-llvm for running the script (I assume > by default it will use GPU acceleration as I have NVIDIA GPU on my system)? > > > Thank you for this. > > BR, > Bishwajit > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Feb 13 14:29:50 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 13 Feb 2017 14:29:50 -0500 Subject: [Paraview] (no subject) In-Reply-To: References: Message-ID: <20170213192950.GA17108@rotor> On Mon, Feb 13, 2017 at 14:16:03 -0500, Bishwajit Dutta wrote: > http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=b10bd3f7136ef809f1df7ad5c94c553f&algorithm=MD5 > ("Couldn't connect to server") > > http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f > ("Couldn't connect to server") This indicates that you can't contact the host. Does it work if you change the URLs to use `https` in CMake/vtkExternalData.cmake? > Also I wanted to run a paraview python script with CPU acceleration. Will > this compilation generate > pvpython and can I pass it --mesa-llvm for running the script (I assume by > default it will use GPU acceleration as I have NVIDIA GPU on my system)? 5.0.0 did not have support for that flag (I think). That flag also assumes certain things about the way ParaView was built (namely that Mesa is available under `lib/paraview-5.x/mesa`). --Ben From cory.quammen at kitware.com Mon Feb 13 15:05:28 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Feb 2017 15:05:28 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: There are a couple known issues in ParaView 5.3.0-RC1 that we plan to address in the next release candidate: * The Mac OS X binary was built and packaged with Qt4 instead of Qt5 * On Mac OS X, the included BDATReader, BDATSeriesReader, and GLGPUVortexFilter will not load (Issue 17170) * On Mac OS X, a crash occurs when adding a source when Auto MPI is enabled (Issue 17171) * Enabling the OSPRay renderer sometimes results in a crash. (Issue 17172) - Cory On Mon, Feb 13, 2017 at 11:49 AM, 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 > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From kmorel at sandia.gov Mon Feb 13 16:01:31 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 13 Feb 2017 21:01:31 +0000 Subject: [Paraview] Paraview crashes with netCDF Message-ID: <4b23bc75c16f48e5b3e9b0f9cdeb54f1@ES08AMSNLNT.srn.sandia.gov> Adam, Was able to replicate your problem. It looks like there are minor issues with both gdalwarp and ParaView that together are causing the crash. The first problem is that gdalwarp is not writing the units attribute correctly when outputting the coordinates in feet. Instead, the units are set to an empty string. This seems wrong. The attribute should be set to ?ft? or ?feet?. When you use gdalwarp to write units of meters, it correctly writes this attribute as ?m?. This is probably a bug, but it shouldn?t cause ParaView to crash. So you probably already see where this is going. NetCDF attributes of empty strings are odd, and the ParaView reader probably has never encountered one before. Lo and behold in this case the reader tries to pull a pointer out of an empty std::string, and std::string throws an exception. I?ve raised a bug for ParaView (https://gitlab.kitware.com/paraview/paraview/issues/17173) and will look into fixing this. I?ll leave it up to you whether you want to contact the GDAL developers about the issue with gdalwarp. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Adam Dershowitz Sent: Monday, February 13, 2017 9:20 AM To: ParaView at paraview.org Subject: [EXTERNAL] Re: [Paraview] Paraview crashes with netCDF I found a bit more information. When pareview crashes, here is part of the crash log: Application Specific Information: terminating with uncaught exception of type std::out_of_range: basic_string abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fffcb43add6 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fffcb526787 pthread_kill + 90 2 libsystem_c.dylib 0x00007fffcb3a0420 abort + 129 3 libc++abi.dylib 0x00007fffc9efb85a abort_message + 266 4 libc++abi.dylib 0x00007fffc9f20c37 default_terminate_handler() + 243 5 libobjc.A.dylib 0x00007fffcaa2af33 _objc_terminate() + 124 6 libc++abi.dylib 0x00007fffc9f1dd69 std::__terminate(void (*)()) + 8 7 libc++abi.dylib 0x00007fffc9f1d9f2 __cxa_rethrow + 99 8 QtCore 0x000000010db17d2d QEventLoop::exec(QFlags) + 845 9 QtCore 0x000000010db1ad97 QCoreApplication::exec() + 199 10 org.paraview.ParaView 0x000000010b083fd2 main + 386 11 libdyld.dylib 0x00007fffcb30c255 start + 1 Any idea why that happens with one feet, but not meters in an otherwise identical file? -- Adam From: Dershowitz Adam > Date: Tuesday, February 7, 2017 at 11:58 AM To: "ParaView at paraview.org" > Subject: Paraview crashes with netCDF I have a geotiff file that I want to view in Paraview. But, Paraview seems to not show the correct offset (0,0 instead of respected the offset). The work around I have been trying is to warp it to the correct location using gdalwarp and to export it as a netCDF. Then Paraview should be able to show it correctly. But, I have run into a crash. If I do this: gdalwarp -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc then I try to open test.nc in Paraview immediately crashes. While, instead if do this: gdalwarp -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc then it opens fine. The difference between these two files is that EPSG 3652 uses feet (which is better for me, for this particular project) while 3651 uses meters. Both appear to be valid NetCDF files. I?ve tried both readers ?CAM NetCDF (Unstructured)? and ?NetCDF files generic and CF conventions? with the same results. I?m running Paraview 5.2.0 64-bit on Mac OS 10.12.3. But, I have seen identical results on an older Mac with a prior OS. I had also tried an older version of Paraview with the same result. Any ideas why this consistently crashes Paraview, or what to do about it? Using netCDF was already a work around, and I willing to try others to view these files. The offset and scale are important because I then need to put in other data that is in the correct location and units. The files are too big for me to send to the mailing list, so I have not posted them. Thanks, -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvan.fournier at free.fr Mon Feb 13 16:31:29 2017 From: yvan.fournier at free.fr (Yvan Fournier) Date: Mon, 13 Feb 2017 22:31:29 +0100 Subject: [Paraview] Automating contour isosurface values in parallel Catalyst Python script Message-ID: <1487021489.6937.2.camel@free.fr> Hello, I'm in the process of migrating some VTK scripts in the Code_Saturne (code- saturne.org) test suite to Catalyst Python scripts, and am having some difficulty automating some cases using contour plots: For time-dependent data, I do not know the value ranges in advance, and would like to query them so as to build an Isosurface values array spanning that range. I can manage to access the point and cell data arrays and ther ranges, but printing the ranges in parallel, it seems I have local values only, while I need a global range. I searched for examples in the documentation, on the Wiki, ..., and found an example for MinMax, but don't seem to ba able to access the correct type of Proxy under Catalyst (the default servermanager is not connected in the usual way. For scalar bar color look-up tables, I can manage with "coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in the coprocessing script, but for a more general case such as thar needed for contour plots, I've been running around in circles in the last hours trying to find and adapt a relevant example. Does anyone have a suggestion ? Thanks in advance, Yvan Fournier From adershowitz at exponent.com Mon Feb 13 16:07:12 2017 From: adershowitz at exponent.com (Adam Dershowitz) Date: Mon, 13 Feb 2017 21:07:12 +0000 Subject: [Paraview] Paraview crashes with netCDF In-Reply-To: <4b23bc75c16f48e5b3e9b0f9cdeb54f1@ES08AMSNLNT.srn.sandia.gov> References: <4b23bc75c16f48e5b3e9b0f9cdeb54f1@ES08AMSNLNT.srn.sandia.gov> Message-ID: Thanks. I actually just created a ticket also, a few minutes after you did: https://gitlab.kitware.com/paraview/paraview/issues/17174 I?ll close mine since it is redundant with yours. -- Adam From: "Moreland, Kenneth" Date: Monday, February 13, 2017 at 4:01 PM To: Dershowitz Adam , "ParaView at paraview.org" Subject: Re: [Paraview] Paraview crashes with netCDF Adam, Was able to replicate your problem. It looks like there are minor issues with both gdalwarp and ParaView that together are causing the crash. The first problem is that gdalwarp is not writing the units attribute correctly when outputting the coordinates in feet. Instead, the units are set to an empty string. This seems wrong. The attribute should be set to ?ft? or ?feet?. When you use gdalwarp to write units of meters, it correctly writes this attribute as ?m?. This is probably a bug, but it shouldn?t cause ParaView to crash. So you probably already see where this is going. NetCDF attributes of empty strings are odd, and the ParaView reader probably has never encountered one before. Lo and behold in this case the reader tries to pull a pointer out of an empty std::string, and std::string throws an exception. I?ve raised a bug for ParaView (https://gitlab.kitware.com/paraview/paraview/issues/17173) and will look into fixing this. I?ll leave it up to you whether you want to contact the GDAL developers about the issue with gdalwarp. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Adam Dershowitz Sent: Monday, February 13, 2017 9:20 AM To: ParaView at paraview.org Subject: [EXTERNAL] Re: [Paraview] Paraview crashes with netCDF I found a bit more information. When pareview crashes, here is part of the crash log: Application Specific Information: terminating with uncaught exception of type std::out_of_range: basic_string abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fffcb43add6 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fffcb526787 pthread_kill + 90 2 libsystem_c.dylib 0x00007fffcb3a0420 abort + 129 3 libc++abi.dylib 0x00007fffc9efb85a abort_message + 266 4 libc++abi.dylib 0x00007fffc9f20c37 default_terminate_handler() + 243 5 libobjc.A.dylib 0x00007fffcaa2af33 _objc_terminate() + 124 6 libc++abi.dylib 0x00007fffc9f1dd69 std::__terminate(void (*)()) + 8 7 libc++abi.dylib 0x00007fffc9f1d9f2 __cxa_rethrow + 99 8 QtCore 0x000000010db17d2d QEventLoop::exec(QFlags) + 845 9 QtCore 0x000000010db1ad97 QCoreApplication::exec() + 199 10 org.paraview.ParaView 0x000000010b083fd2 main + 386 11 libdyld.dylib 0x00007fffcb30c255 start + 1 Any idea why that happens with one feet, but not meters in an otherwise identical file? -- Adam From: Dershowitz Adam > Date: Tuesday, February 7, 2017 at 11:58 AM To: "ParaView at paraview.org" > Subject: Paraview crashes with netCDF I have a geotiff file that I want to view in Paraview. But, Paraview seems to not show the correct offset (0,0 instead of respected the offset). The work around I have been trying is to warp it to the correct location using gdalwarp and to export it as a netCDF. Then Paraview should be able to show it correctly. But, I have run into a crash. If I do this: gdalwarp -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc then I try to open test.nc in Paraview immediately crashes. While, instead if do this: gdalwarp -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc then it opens fine. The difference between these two files is that EPSG 3652 uses feet (which is better for me, for this particular project) while 3651 uses meters. Both appear to be valid NetCDF files. I?ve tried both readers ?CAM NetCDF (Unstructured)? and ?NetCDF files generic and CF conventions? with the same results. I?m running Paraview 5.2.0 64-bit on Mac OS 10.12.3. But, I have seen identical results on an older Mac with a prior OS. I had also tried an older version of Paraview with the same result. Any ideas why this consistently crashes Paraview, or what to do about it? Using netCDF was already a work around, and I willing to try others to view these files. The offset and scale are important because I then need to put in other data that is in the correct location and units. The files are too big for me to send to the mailing list, so I have not posted them. Thanks, -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Tue Feb 14 03:19:17 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 14 Feb 2017 09:19:17 +0100 Subject: [Paraview] Copying representation properties In-Reply-To: References: Message-ID: Works perfectly on ParaView 5.2.0 on Windows 10. you may want to try and reproduce this behavior on other computers/OSes. And let us know how you use this feature. Regards, Mathieu Westphal On Sun, Feb 12, 2017 at 1:31 PM, Dimitrova, Maria < maria.dimitrova at helsinki.fi> wrote: > Thank you, maybe the problem only exists in the Windows version. > > > Best regards, > > Maria Dimitrova > ------------------------------ > *From:* Cory Quammen > *Sent:* 12 February 2017 00:30:58 > *To:* Mathieu Westphal > *Cc:* Dimitrova, Maria; paraview at paraview.org > > *Subject:* Re: [Paraview] Copying representation properties > > FWIW, I just tried this with 5.2.0 official binaries on Mac OS X and > copy/paste of representation properties worked fine. > > On Fri, Feb 10, 2017 at 7:15 AM, Mathieu Westphal < > mathieu.westphal at kitware.com> wrote: > >> Hello >> >> I will not be able to test this version right away, will let you know. >> >> Mathieu Westphal >> >> On Fri, Feb 10, 2017 at 1:06 PM, Dimitrova, Maria < >> maria.dimitrova at helsinki.fi> wrote: >> >>> Hello, >>> >>> >>> Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL >>> version - 5.2.0-RC4. >>> >>> >>> Best regards, >>> >>> Maria Dimitrova >>> ------------------------------ >>> *From:* Mathieu Westphal >>> *Sent:* 10 February 2017 13:44:37 >>> *To:* Dimitrova, Maria >>> *Cc:* paraview at paraview.org >>> *Subject:* Re: [Paraview] Copying representation properties >>> >>> Hello >>> >>> I just checked, to copy->Paste feature is working perfectly on ParaView >>> master git. Which version of ParaView are you using ? >>> >>> Regards, >>> >>> Mathieu Westphal >>> >>> On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria < >>> maria.dimitrova at helsinki.fi> wrote: >>> >>>> Dear all, >>>> >>>> >>>> Is there a way to copy the properties of the representation that is >>>> applied to a filter to another instance of the same filter? In my project I >>>> use 3D glyphs with sphere size 0.03 and blue colour. I have tried >>>> right-clicking on the existing filter -> Copy, then Paste to the new >>>> instance of the filter but the representation is not affected. >>>> >>>> >>>> Also, another part of my project involves applying Surface LIC with a >>>> particular colour scheme and colour range, as well as contrast adjustments >>>> and antialiasing, all of which are identical for all the files I need to >>>> process. It would save some time if I could just make a custom >>>> representation. >>>> >>>> >>>> Thank you very much! >>>> >>>> >>>> Best regards, >>>> >>>> Maria >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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 mathieu.westphal at kitware.com Tue Feb 14 04:27:44 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 14 Feb 2017 10:27:44 +0100 Subject: [Paraview] Copying representation properties In-Reply-To: References: Message-ID: Dear Maria The feature you use ( Copy/Paste of filter ) is indeed broken for now. Cory and me have been talking about another feature, wich can be found in the properties panel, not in the pipeline browser. This feature allows you to copy and paste properties of a filter, representation or view. See attached image. Regards, Mathieu Westphal On Tue, Feb 14, 2017 at 10:06 AM, Dimitrova, Maria < maria.dimitrova at helsinki.fi> wrote: > Dear Mathieu, > > > I recorded my screen and sent the video as attachment. Hope this helps. > > > I do not have access to another Windows computer at the moment. At work we > have Linux desktops but the CPUs are too slow to handle large sets of data, > so I need to use my personal computer. > > > Best regards, > > Maria Dimitrova > ------------------------------ > *From:* Mathieu Westphal > *Sent:* 14 February 2017 10:19:17 > *To:* Dimitrova, Maria > *Cc:* Cory Quammen; paraview at paraview.org > > *Subject:* Re: [Paraview] Copying representation properties > > Works perfectly on ParaView 5.2.0 on Windows 10. you may want to try and > reproduce this behavior on other computers/OSes. And let us know how you > use this feature. > > Regards, > > Mathieu Westphal > > On Sun, Feb 12, 2017 at 1:31 PM, Dimitrova, Maria < > maria.dimitrova at helsinki.fi> wrote: > >> Thank you, maybe the problem only exists in the Windows version. >> >> >> Best regards, >> >> Maria Dimitrova >> ------------------------------ >> *From:* Cory Quammen >> *Sent:* 12 February 2017 00:30:58 >> *To:* Mathieu Westphal >> *Cc:* Dimitrova, Maria; paraview at paraview.org >> >> *Subject:* Re: [Paraview] Copying representation properties >> >> FWIW, I just tried this with 5.2.0 official binaries on Mac OS X and >> copy/paste of representation properties worked fine. >> >> On Fri, Feb 10, 2017 at 7:15 AM, Mathieu Westphal < >> mathieu.westphal at kitware.com> wrote: >> >>> Hello >>> >>> I will not be able to test this version right away, will let you know. >>> >>> Mathieu Westphal >>> >>> On Fri, Feb 10, 2017 at 1:06 PM, Dimitrova, Maria < >>> maria.dimitrova at helsinki.fi> wrote: >>> >>>> Hello, >>>> >>>> >>>> Thank you for the quick reply. I use the Windows 64 bit MPI OpenCL >>>> version - 5.2.0-RC4. >>>> >>>> >>>> Best regards, >>>> >>>> Maria Dimitrova >>>> ------------------------------ >>>> *From:* Mathieu Westphal >>>> *Sent:* 10 February 2017 13:44:37 >>>> *To:* Dimitrova, Maria >>>> *Cc:* paraview at paraview.org >>>> *Subject:* Re: [Paraview] Copying representation properties >>>> >>>> Hello >>>> >>>> I just checked, to copy->Paste feature is working perfectly on ParaView >>>> master git. Which version of ParaView are you using ? >>>> >>>> Regards, >>>> >>>> Mathieu Westphal >>>> >>>> On Fri, Feb 10, 2017 at 10:23 AM, Dimitrova, Maria < >>>> maria.dimitrova at helsinki.fi> wrote: >>>> >>>>> Dear all, >>>>> >>>>> >>>>> Is there a way to copy the properties of the representation that is >>>>> applied to a filter to another instance of the same filter? In my project I >>>>> use 3D glyphs with sphere size 0.03 and blue colour. I have tried >>>>> right-clicking on the existing filter -> Copy, then Paste to the new >>>>> instance of the filter but the representation is not affected. >>>>> >>>>> >>>>> Also, another part of my project involves applying Surface LIC with a >>>>> particular colour scheme and colour range, as well as contrast adjustments >>>>> and antialiasing, all of which are identical for all the files I need to >>>>> process. It would save some time if I could just make a custom >>>>> representation. >>>>> >>>>> >>>>> Thank you very much! >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> Maria >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView 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 -------------- A non-text attachment was scrubbed... Name: 2017-02-14-103655_919x1015_scrot.png Type: image/png Size: 120019 bytes Desc: not available URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Feb 14 05:27:09 2017 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Tue, 14 Feb 2017 13:27:09 +0300 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: Hi Cory, I was trying to install new release candidate from source to test Catalyst module but i am getting following error messages under Linux (CentOS) and with Intel compiler (2016), CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known features for CXX compiler "Intel" version 16.0.1.20151021. Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known features for CXX compiler "Intel" version 16.0.1.20151021. Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) VTK/Common/Math/CMakeLists.txt:40 (vtk_module_library) The previous version 5.2.0 was installed without any problem using same libraries, compiler and server. So, i just wonder that is there any change in configure step related with the compiler definitions? Any suggestion? Regards, --ufuk 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 > From u.utku.turuncoglu at be.itu.edu.tr Tue Feb 14 05:40:35 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 14 Feb 2017 12:40:35 +0200 (EET) Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: <46431.160.75.90.139.1487068835.squirrel@webmail.be.itu.edu.tr> Hi Cory, I was trying to install new release candidate to test Catalyst module but i am getting following error messages under Linux (CentOS) and with Intel compiler (2016), CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known features for CXX compiler "Intel" version 16.0.1.20151021. Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 (target_compile_features): target_compile_features no known features for CXX compiler "Intel" version 16.0.1.20151021. Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) VTK/Common/Math/CMakeLists.txt:40 (vtk_module_library) The previous version 5.2.0 installed without any problem using same libraries and compiler. So, is there any change related with the compiler definitions? Any suggestion? Regards, --ufuk > 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 > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From info at seoaachen.de Tue Feb 14 06:07:52 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Tue, 14 Feb 2017 12:07:52 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> paraview web visualizer does not work in windows: ls: no such file or directory: /Applications ls: no such file or directory: /opt ls: no such file or directory: /usr/local/opt/ Am 13.02.2017 um 17:49 schrieb Cory Quammen: > 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 > From ufdup89 at gmail.com Tue Feb 14 06:32:35 2017 From: ufdup89 at gmail.com (ufdup) Date: Tue, 14 Feb 2017 12:32:35 +0100 Subject: [Paraview] STL files: normal and vertex Message-ID: Dear all, I have a contour in Paraview that I would like to export to Matlab. In the past I?ve been doing this by generating a STL file which could be read in Matlab without any problems. However, now my STL files are quite large and reading in Matlab is really inefficient because of the STL standard way of writing. For my application it would be enough to right only the normals and the vertex of the triangles. I am working with the paraview.simple module and so far I can get the normals using the Filter ComputeNormals followed by a servermanager.Fetch(?.). The vertex, however are still missing?. Does anyone know how can I get this kind of information from Paraview using Python? Best Regards, Tiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From demaio.a at gmail.com Tue Feb 14 09:20:55 2017 From: demaio.a at gmail.com (Alessandro De Maio) Date: Tue, 14 Feb 2017 15:20:55 +0100 Subject: [Paraview] XDMF and nested Grid Collections Message-ID: Hi, I'm trying to export from a parallel MPI CFD code a set of results using xdmf/hdf5 format in order to be read in Paraview. The computational domain is divided into several parts (unstructured polyhedral grid) and the idea is to write a xdmf with a further subdivision to be read in parallel by mpi paraview. So it's a nested subdivision in which the external level is based on different parts of the domain (that should be extractable in Paraview after the reading) and each part is divided into a number of chunks equal to the number of processes of the parallel Paraview execution. With such a subdivision, reading this file with a parallel Paraview execution, each Paraview process loads a fraction of each part and, if all the chunks of each part have the same dimension, all the Paraview processes are balanced. In the following there is an example for two parts and two Paraview processes. I've used nested Grid Collections of type Spatial and it seems that everything is ok but the problem is that in Paraview the names of the first level collection items is lost (in the following example tet_cell1 and tet_cell2) and these items are called "Block 0" and "Block 1". The leaf elements of the tree instead (Grid_01, Grid_02, ...) mantain their correct name. I've tried also to change the GridType of the external level from Collection to Tree (that should be supported in the xdmf data format) but in this case the item in Paraview is empty (0 cells and 0 nodes). Is there any error in my procedure? It's the first time that I use xdmf. Thank you in advance for your help. Alessandro ../positive/xdmf/tet_cell1.h5:Data0 ../positive/xdmf/tet_cell1.h5:Data1 ../positive/xdmf/tet_cell1.h5:Data2 ../negative/xdmf/tet_cell1.h5:Data0 ../negative/xdmf/tet_cell1.h5:Data1 ../negative/xdmf/tet_cell1.h5:Data2 ../positive/xdmf/tet_cell2.h5:Data0 ../positive/xdmf/tet_cell2.h5:Data1 ../positive/xdmf/tet_cell2.h5:Data2 ../negative/xdmf/tet_cell2.h5:Data0 ../negative/xdmf/tet_cell2.h5:Data1 ../negative/xdmf/tet_cell2.h5:Data2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Feb 14 09:27:27 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 14 Feb 2017 09:27:27 -0500 Subject: [Paraview] [vtkusers] Open big *.VTK files with ParaView In-Reply-To: References: Message-ID: Christopher, I'm moving this to the ParaView mailing list. As I recall, Microsoft's runtime requires the use of special file-handling functions for reading files larger than 4 GB, even when running on a 64-bit version of Windows. I do not believe the VTK legacy library does not use these functions, which is likely why you are seeing this behavior in ParaView. I'm not aware of a simple fix, unfortunately. Would you mind posting an Issue to the ParaView bug tracker? https://gitlab.kitware.com/paraview/paraview/issues Thanks, Cory On Tue, Feb 14, 2017 at 2:25 AM, Eischer, Christopher wrote: > Hello together, > > > > I?m having poblems to open big vtk files ( about <4GB) with ParaView. With > smaller files I have no Problems. > > For the big files ParaView says that ? a reader for D:\... could not be > found. Please choose one?.. When I choose the vtk type the files gets loaded > but nothing is visible. > > > > Does somebody know a solution? > > > > My System: > > ParaView 5.2.0 > > Win 7 Ultimate 64 bit > > i7-6700 @ 3.4 Ghz with 32 GB Ram > > > > Thanks for your help. > > > > Greetings Chris > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From joseph.g.hennessey2.ctr at mail.mil Tue Feb 14 09:52:37 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Tue, 14 Feb 2017 14:52:37 +0000 Subject: [Paraview] [Non-DoD Source] XDMF and nested Grid Collections (UNCLASSIFIED) Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E3CBA0@UCOLHPUD.easf.csd.disa.mil> CLASSIFICATION: UNCLASSIFIED Alessandro, This looks like a useful feature to add to the reader, and we will put in our list of things to work on. But, I can not immediately implement this as we have a number of high priority updates such as c++11 support, and an updated base Xdmf library currently pending. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Alessandro De Maio Sent: Tuesday, February 14, 2017 9:21 AM To: paraview at paraview.org Subject: [Non-DoD Source] [Paraview] XDMF and nested Grid Collections 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. ________________________________ Hi, I'm trying to export from a parallel MPI CFD code a set of results using xdmf/hdf5 format in order to be read in Paraview. The computational domain is divided into several parts (unstructured polyhedral grid) and the idea is to write a xdmf with a further subdivision to be read in parallel by mpi paraview. So it's a nested subdivision in which the external level is based on different parts of the domain (that should be extractable in Paraview after the reading) and each part is divided into a number of chunks equal to the number of processes of the parallel Paraview execution. With such a subdivision, reading this file with a parallel Paraview execution, each Paraview process loads a fraction of each part and, if all the chunks of each part have the same dimension, all the Paraview processes are balanced. In the following there is an example for two parts and two Paraview processes. I've used nested Grid Collections of type Spatial and it seems that everything is ok but the problem is that in Paraview the names of the first level collection items is lost (in the following example tet_cell1 and tet_cell2) and these items are called "Block 0" and "Block 1". The leaf elements of the tree instead (Grid_01, Grid_02, ...) mantain their correct name. I've tried also to change the GridType of the external level from Collection to Tree (that should be supported in the xdmf data format) but in this case the item in Paraview is empty (0 cells and 0 nodes). Is there any error in my procedure? It's the first time that I use xdmf. Thank you in advance for your help. Alessandro ../positive/xdmf/tet_cell1.h5:Data0 ../positive/xdmf/tet_cell1.h5:Data1 ../positive/xdmf/tet_cell1.h5:Data2 ../negative/xdmf/tet_cell1.h5:Data0 ../negative/xdmf/tet_cell1.h5:Data1 ../negative/xdmf/tet_cell1.h5:Data2 ../positive/xdmf/tet_cell2.h5:Data0 ../positive/xdmf/tet_cell2.h5:Data1 ../positive/xdmf/tet_cell2.h5:Data2 ../negative/xdmf/tet_cell2.h5:Data0 ../negative/xdmf/tet_cell2.h5:Data1 ../negative/xdmf/tet_cell2.h5:Data2 CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Feb 14 10:04:50 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Feb 2017 10:04:50 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: Chuck, is this a CMake version related issue? Ufuk, which cmake version are you using? Utkarsh On Tue, Feb 14, 2017 at 5:27 AM, Ufuk Utku Turuncoglu (BE) wrote: > Hi Cory, > > I was trying to install new release candidate from source to test Catalyst > module but i am getting following error messages under Linux (CentOS) and > with Intel compiler (2016), > > > CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 > (target_compile_features): > target_compile_features no known features for CXX compiler > > "Intel" > > version 16.0.1.20151021. > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) > VTK/Common/Core/CMakeLists.txt:724 (vtk_module_library) > > > > CMake Error at VTK/CMake/vtkModuleMacros.cmake:549 > (target_compile_features): > target_compile_features no known features for CXX compiler > > "Intel" > > version 16.0.1.20151021. > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:648 (vtk_add_library) > VTK/Common/Math/CMakeLists.txt:40 (vtk_module_library) > > The previous version 5.2.0 was installed without any problem using same > libraries, compiler and server. So, i just wonder that is there any change > in configure step related with the compiler definitions? Any suggestion? > > Regards, > > --ufuk > > 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 Tue Feb 14 10:07:32 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Feb 2017 10:07:32 -0500 Subject: [Paraview] vtkPythonProgrammableFilter Multiple output port? In-Reply-To: References: Message-ID: AFIAK, this is not currently supported. Utkarsh On Fri, Feb 10, 2017 at 1:34 PM, michal wozniak wrote: > Hi, > > > Since ParaView 5.2, vtkPythonProgrammableFilter can now accept multiple > input ports. Is it possible to also have multiple output port? > > > Thanks, > > Michal > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 claire.guilbaud at cea.fr Tue Feb 14 10:17:34 2017 From: claire.guilbaud at cea.fr (GUILBAUD Claire) Date: Tue, 14 Feb 2017 16:17:34 +0100 Subject: [Paraview] ParaView 5.3.0 and VTK-m Message-ID: Hi all, I'm trying to build ParaView 5.3.0 with the last version of VTK-m (sources download today using git clone https://gitlab.kitware.com/vtk/vtk-m.git). I compile VTK-m with TBB backend (version 4.2), gcc 4.9 and -std=c++11 option. I have the following issues a lot of times when compiling : In file included from .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmContour.cxx:30:0: .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h: In member function 'vtkm::cont::internal::Storage& vtkm::cont::internal::Storage::operator=(const vtkm::cont::internal::Storage&)': .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h:69:13: error: 'ErrorControlBadValue' is not a member of 'vtkm::cont' throw vtkm::cont::ErrorControlBadValue( Looking at sources, it seems that vtkm::cont::ErrorControlBadValue has been replaced by vtkm::cont::ErrorBadValue. I can patch all sources, but I think it's not a good idea. So, which version of VTK-m is needed for ParaView 5.3.0 ? Thanks Claire From tim.gallagher at gatech.edu Tue Feb 14 11:00:59 2017 From: tim.gallagher at gatech.edu (Gallagher, Timothy P) Date: Tue, 14 Feb 2017 16:00:59 +0000 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: , Message-ID: Hi Andy, Looks like passing the current time step into the UpdatePipeline calls made it work as expected. Sorry for the delay in reporting, it took a long time for the job to move through the queue! Anyway, looks like it's working properly and I am getting the data as expected. For future reference, should I always just pass the time in? Or are the possibly other, unintended side effects from that as well to watch out for? Thanks again, Tim ________________________________ From: Andy Bauer Sent: Monday, February 13, 2017 11:30 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Cataylst pipeline not updating Hi Tim, It's possible that there's something funky going on when the data set being passed through parts of the pipeline are empty. I'm hoping for the easy fix with passing in the time since I've know that has caused unexpected behavior before. If that doesn't solve your issue then I'll probably have to do something similar and run it locally to see what's going on. Cheers, Andy On Mon, Feb 13, 2017 at 11:06 AM, Gallagher, Timothy P > wrote: The RequestDataDescription is the same as the default output from the script generator, so I didn't include it. The DoCoProcessing gets called every time step and the volumeIntegrals data is updated and written correctly every delta_t, so I'm confident in that part. I will add the calls you suggested and re-run. It takes some time for it to evolve to the point something will happen -- I don't have it saving data frequently enough to run a quick test, I was expecting the pipeline to save it for me! The other thing that occurred to me -- is there something about the Contour filter that turns it off/disables it when the pipeline is built and there is no surface at that contour level? Thanks, Tim ________________________________ From: Andy Bauer > Sent: Monday, February 13, 2017 10:56 AM To: Gallagher, Timothy P Cc: paraview at paraview.org Subject: Re: [Paraview] Cataylst pipeline not updating Hi Tim, Try adding in the current time to the UpdatePipeline() calls, e.g. *.UpdatePipeline(datadescription.GetCurrentTime()) It's tough to tell with RequestDataDescription() missing but I assume that DoCoProcessing() is getting called when you want, correct? Let me know if that doesn't solve the problem. Best, Andy On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P > wrote: Back with another question! I have a pipeline that has 1 input and 4 outputs. The simplest is a IntegrateVariables filter hooked up to the input. Another branch of the pipeline goes through several PythonCalculator filters and a CellDataToPointData filter and then arrives at the three outputs: 1. The CD2PD filter is connected to a Contour filter with a single level, X. This is then connected to an IntegrateVariables filter (used to compute the area of the Contour) and a Writer. 2. The CD2PD filter is also connected to another Contour filter with a single level Y. This is connected to an IntegrateVariables and Writer just as in 1. 3. The CD2PD filter is sliced two times with each slice in a different render view to save images. I have the coprocessor running every delta_t seconds. The initial IntegrateVariables filter is updated with UpdatePipeline and then the values are saved to disk. This works every step, no issues. I then call UpdatePipeline on both of the Contour and both of the IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the IntegrateVariables exceeds a threshold, and if it does, I save the Contour's to disk as a VTK file. This is not working correctly. If I start the simulation from a point where the Contour's exist in the flow already, then everything works great and the Area field changes in time and it saves the Contour's. However, if the simulation starts without the Contours already in the flow, the Area fields stay zero forever. It's as if the pipeline isn't updating or something. I have attached the DoCoProcessing function used. I don't see anything immediately obvious that would prevent it from updating or getting the correct values for the Area. Am I missing something about how the pipeline or contour filters update? Thanks, Tim _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 Feb 14 11:18:07 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 14 Feb 2017 11:18:07 -0500 Subject: [Paraview] Cataylst pipeline not updating In-Reply-To: References: Message-ID: Hi Tim, I'm glad this fixed the issue. You'll want to always pass in the time to UpdatePipeline() for Catalyst. The issue was that the pipeline thought that everything it had was current since the time didn't change and none if the filters' parameters changed and therefore it skipped recomputing what it thought would be the same result. I do wonder if the start of the pipeline should mark that it is modified. I'll have to think about that some more. Even if that were true though you'd still want to pass in the time value to UpdatePipeline(). This is true as well for ParaView Python pipelines in general for time dependent sources. No problem about the delay in reporting -- I was more than happy to let your computers do the proof rather than verifying it myself :) Cheers, Andy On Tue, Feb 14, 2017 at 11:00 AM, Gallagher, Timothy P < tim.gallagher at gatech.edu> wrote: > Hi Andy, > > > Looks like passing the current time step into the UpdatePipeline calls > made it work as expected. Sorry for the delay in reporting, it took a long > time for the job to move through the queue! > > > Anyway, looks like it's working properly and I am getting the data as > expected. > > > For future reference, should I always just pass the time in? Or are the > possibly other, unintended side effects from that as well to watch out for? > > > Thanks again, > > > Tim > > > ------------------------------ > *From:* Andy Bauer > *Sent:* Monday, February 13, 2017 11:30 AM > > *To:* Gallagher, Timothy P > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Cataylst pipeline not updating > > Hi Tim, > > It's possible that there's something funky going on when the data set > being passed through parts of the pipeline are empty. I'm hoping for the > easy fix with passing in the time since I've know that has caused > unexpected behavior before. If that doesn't solve your issue then I'll > probably have to do something similar and run it locally to see what's > going on. > > Cheers, > Andy > > On Mon, Feb 13, 2017 at 11:06 AM, Gallagher, Timothy P < > tim.gallagher at gatech.edu> wrote: > >> The RequestDataDescription is the same as the default output from the >> script generator, so I didn't include it. The DoCoProcessing gets called >> every time step and the volumeIntegrals data is updated and written >> correctly every delta_t, so I'm confident in that part. >> >> >> I will add the calls you suggested and re-run. It takes some time for it >> to evolve to the point something will happen -- I don't have it saving data >> frequently enough to run a quick test, I was expecting the pipeline to save >> it for me! >> >> >> The other thing that occurred to me -- is there something about the >> Contour filter that turns it off/disables it when the pipeline is built and >> there is no surface at that contour level? >> >> >> Thanks, >> >> >> Tim >> >> >> ------------------------------ >> *From:* Andy Bauer >> *Sent:* Monday, February 13, 2017 10:56 AM >> *To:* Gallagher, Timothy P >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Cataylst pipeline not updating >> >> Hi Tim, >> >> Try adding in the current time to the UpdatePipeline() calls, e.g. >> *.UpdatePipeline(datadescription.GetCurrentTime()) >> >> It's tough to tell with RequestDataDescription() missing but I assume >> that DoCoProcessing() is getting called when you want, correct? >> >> Let me know if that doesn't solve the problem. >> >> Best, >> Andy >> >> On Mon, Feb 13, 2017 at 5:45 AM, Gallagher, Timothy P < >> tim.gallagher at gatech.edu> wrote: >> >>> Back with another question! >>> >>> >>> I have a pipeline that has 1 input and 4 outputs. The simplest is a >>> IntegrateVariables filter hooked up to the input. Another branch of the >>> pipeline goes through several PythonCalculator filters and a >>> CellDataToPointData filter and then arrives at the three outputs: >>> >>> >>> 1. The CD2PD filter is connected to a Contour filter with a single >>> level, X. This is then connected to an IntegrateVariables filter (used to >>> compute the area of the Contour) and a Writer. >>> >>> 2. The CD2PD filter is also connected to another Contour filter with a >>> single level Y. This is connected to an IntegrateVariables and Writer just >>> as in 1. >>> >>> 3. The CD2PD filter is sliced two times with each slice in a different >>> render view to save images. >>> >>> >>> I have the coprocessor running every delta_t seconds. The initial >>> IntegrateVariables filter is updated with UpdatePipeline and then the >>> values are saved to disk. This works every step, no issues. >>> >>> >>> I then call UpdatePipeline on both of the Contour and both of the >>> IntegrateVariables filters in 1 and 2. I check if the 'Area' field in the >>> IntegrateVariables exceeds a threshold, and if it does, I save the >>> Contour's to disk as a VTK file. This is not working correctly. >>> >>> >>> If I start the simulation from a point where the Contour's exist in the >>> flow already, then everything works great and the Area field changes in >>> time and it saves the Contour's. >>> >>> >>> However, if the simulation starts without the Contours already in the >>> flow, the Area fields stay zero forever. It's as if the pipeline isn't >>> updating or something. I have attached the DoCoProcessing function used. I >>> don't see anything immediately obvious that would prevent it from updating >>> or getting the correct values for the Area. >>> >>> >>> Am I missing something about how the pipeline or contour filters update? >>> >>> >>> Thanks, >>> >>> >>> Tim >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 Tue Feb 14 11:23:52 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 14 Feb 2017 09:23:52 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> Message-ID: Could you be more explicit regarding the error you encounter as those output are expected on Windows. Did you provide the path to ParaView as the argument of the Visualizer executable? Thanks, Seb On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga wrote: > paraview web visualizer does not work in windows: > > ls: no such file or directory: /Applications > ls: no such file or directory: /opt > ls: no such file or directory: /usr/local/opt/ > > > Am 13.02.2017 um 17:49 schrieb Cory Quammen: > >> 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/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 fabidi89 at vt.edu Tue Feb 14 12:46:28 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 14 Feb 2017 12:46:28 -0500 Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 Message-ID: Hello community, Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? When I install Paraview from source, I get the below error. "/bin/sh: line 0: cd: /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: No such file or directory make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] Error 2" I am not sure if I am missing a dependency. The install works fine without this plugin. Anyone seen this before? -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Feb 14 13:16:43 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 14 Feb 2017 13:16:43 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: <20170214181643.GC7593@megas.kitware.com> On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh Ayachit wrote: > Chuck, is this a CMake version related issue? Ufuk, which cmake > version are you using? It likely is. VTK is now using CMake's C++11 support detection and older versions of CMake do not have the required bits for Intel 16. These appear to have been introduced in 3.8.0, but may have been in 3.7.0 (I'm not completely sure). --Ben From utkarsh.ayachit at kitware.com Tue Feb 14 14:16:20 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Feb 2017 14:16:20 -0500 Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 In-Reply-To: References: Message-ID: Can you post your CMakeCache.txt? I suspect one of the Qt help generation tools was not found/set correctly. Utkarsh On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: > Hello community, > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? When I > install Paraview from source, I get the below error. > > "/bin/sh: line 0: cd: > /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: No > such file or directory > make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 > make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] Error 2" > > I am not sure if I am missing a dependency. The install works fine without > this plugin. > > Anyone seen this before? > -- > 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 joachim.pouderoux at kitware.com Tue Feb 14 14:36:14 2017 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 14 Feb 2017 15:36:14 -0400 Subject: [Paraview] STL files: normal and vertex In-Reply-To: References: Message-ID: Hello Tiago, Using Fetch you should end up with a vtkPolyData object which have accessors to triangle point ids (using GetPolys() then a traversal on the vtkCellArray or directly using GetCellPoints(). Point coordinates can be retrieved using GetPoint() function. So could you be more specific on how you call servermanager.Fetch() and what you are doing next to retrieve your normals? Best, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2017-02-14 7:32 GMT-04:00 ufdup : > Dear all, > > I have a contour in Paraview that I would like to export to Matlab. In the > past I?ve been doing this by generating a STL file which could be read in > Matlab without any problems. > > However, now my STL files are quite large and reading in Matlab is really > inefficient because of the STL standard way of writing. For my application > it would be enough to right only the normals and the vertex of the > triangles. > > I am working with the paraview.simple module and so far I can get the > normals using the Filter ComputeNormals followed by a > servermanager.Fetch(?.). The vertex, however are still missing?. > > Does anyone know how can I get this kind of information from Paraview > using Python? > > Best Regards, > Tiago > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 christophe.trophime at lncmi.cnrs.fr Tue Feb 14 14:32:52 2017 From: christophe.trophime at lncmi.cnrs.fr (Christophe Trophime) Date: Tue, 14 Feb 2017 20:32:52 +0100 (CET) Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 In-Reply-To: References: Message-ID: <181475582.1543787.1487100772876.JavaMail.zimbra@lncmi.cnrs.fr> I had a similar problem on debian export QT_SELECT=qt5 or qt4 before running cmake fix the problem Christophe TROPHIME Research Engineer CNRS - LNCMI 25, rue des Martyrs BP 166 38042 GRENOBLE Cedex 9 FRANCE Tel : +33 (0)4 76 88 90 02 Fax : +33 (0) 4 76 88 10 01 Office U 19 M at il : christophe.trophime at lncmi.cnrs.fr ----- Original Message ----- > From: "Utkarsh Ayachit" > To: "Faiz Abidi" > Cc: "ParaView" > Sent: Tuesday, February 14, 2017 8:16:20 PM > Subject: Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0 > > Can you post your CMakeCache.txt? I suspect one of the Qt help > generation tools was not found/set correctly. > > Utkarsh > > On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: > > Hello community, > > > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? When I > > install Paraview from source, I get the below error. > > > > "/bin/sh: line 0: cd: > > /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: No > > such file or directory > > make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 > > make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] Error 2" > > > > I am not sure if I am missing a dependency. The install works fine without > > this plugin. > > > > Anyone seen this before? > > -- > > 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 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 joachim.pouderoux at kitware.com Tue Feb 14 14:47:38 2017 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 14 Feb 2017 15:47:38 -0400 Subject: [Paraview] ParaView 5.3.0 and VTK-m In-Reply-To: References: Message-ID: Hello Claire, Checking at paraview-superbuild project is generally a good idea to answer this kind of questions. In versions.cmake one can see that it downloads this version: http://www.paraview.org/files/dependencies/vtkm-d32f3457d8049a79cc59fb02c3dfb7879ef90ee3.tar.bz2 This corresponds to the following commit: commit d32f3457d8049a79cc59fb02c3dfb7879ef90ee3 Merge: c1f7a07 c6fdcea Author: Kenneth Moreland Date: *Wed Jan 25* 11:07:39 2017 -0500 And you will find the build options in vtkm.cmake: superbuild_add_project(vtkm DEFAULT_ON DEPENDS tbb cxx11 CMAKE_ARGS -DBUILD_SHARED_LIBS:BOOL=${BUILD_SHARED_LIBS} -DVTKm_ENABLE_TBB:BOOL=${tbb_enabled} -DVTKm_ENABLE_RENDERING:BOOL=OFF -DVTKm_ENABLE_TESTING:BOOL=OFF -DTBB_ROOT:PATH=) Best, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2017-02-14 11:17 GMT-04:00 GUILBAUD Claire : > Hi all, > > I'm trying to build ParaView 5.3.0 with the last version of VTK-m (sources > download today using git clone https://gitlab.kitware.com/vtk/vtk-m.git). > I compile VTK-m with TBB backend (version 4.2), gcc 4.9 and -std=c++11 > option. > > I have the following issues a lot of times when compiling : > > In file included from .../ParaView-v5.3.0-RC1/VTK/Ac > celerators/Vtkm/vtkmContour.cxx:30:0: > .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h: In > member function 'vtkm::cont::internal::Storage tovtkm::vtkAOSArrayContainerTag>& vtkm::cont::internal::Storage tovtkm::vtkAOSArrayContainerTag>::operator=(const > vtkm::cont::internal::Storage g>&)': > .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h:69:13: > error: 'ErrorControlBadValue' is not a member of 'vtkm::cont' > throw vtkm::cont::ErrorControlBadValue( > > Looking at sources, it seems that vtkm::cont::ErrorControlBadValue has > been replaced by vtkm::cont::ErrorBadValue. > > I can patch all sources, but I think it's not a good idea. > > So, which version of VTK-m is needed for ParaView 5.3.0 ? > > Thanks > > Claire > > > _______________________________________________ > 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 joachim.pouderoux at kitware.com Tue Feb 14 15:02:01 2017 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Tue, 14 Feb 2017 16:02:01 -0400 Subject: [Paraview] Automating contour isosurface values in parallel Catalyst Python script In-Reply-To: <1487021489.6937.2.camel@free.fr> References: <1487021489.6937.2.camel@free.fr> Message-ID: Hi Yvan, Regarding MinMax: this filter is indeed not exposed by any standard Catalyst edition but it is easy to add. See for instance in ParaView/Catalyst/Editions/Extras/manifest.json how the PVExtractSelection filter is exposed (line 50 and 247). Just do the same with the MinMax filter (see proxy's declaration at filters.xml:~11725). Best, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2017-02-13 17:31 GMT-04:00 Yvan Fournier : > Hello, > > I'm in the process of migrating some VTK scripts in the Code_Saturne (code- > saturne.org) test suite to Catalyst Python scripts, and am having some > difficulty automating some cases using contour plots: > > For time-dependent data, I do not know the value ranges in advance, and > would > like to query them so as to build an Isosurface values array spanning that > range. > > I can manage to access the point and cell data arrays and ther ranges, but > printing the ranges in parallel, it seems I have local values only, while > I need > a global range. > > I searched for examples in the documentation, on the Wiki, ..., and found > an > example for MinMax, but don't seem to ba able to access the correct type of > Proxy under Catalyst (the default servermanager is not connected in the > usual > way. > > For scalar bar color look-up tables, I can manage with > "coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in > the > coprocessing script, but for a more general case such as thar needed for > contour > plots, I've been running around in circles in the last hours trying to > find and > adapt a relevant example. > > Does anyone have a suggestion ? Thanks in advance, > > Yvan Fournier > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 robert.maynard at kitware.com Tue Feb 14 15:09:26 2017 From: robert.maynard at kitware.com (Robert Maynard) Date: Tue, 14 Feb 2017 15:09:26 -0500 Subject: [Paraview] ParaView 5.3.0 and VTK-m In-Reply-To: References: Message-ID: Hi, As Joachim pointed out currently ParaView requires a specific version of VTK-m to resolve the exception name problem. Yesterday we merged in a fix for this problem to VTK ( https://gitlab.kitware.com/vtk/vtk/merge_requests/2469 ) so soon you will not require a specific version of VTK-m. On Tue, Feb 14, 2017 at 2:47 PM, Joachim Pouderoux wrote: > Hello Claire, > > Checking at paraview-superbuild project is generally a good idea to answer > this kind of questions. > > In versions.cmake one can see that it downloads this version: > > http://www.paraview.org/files/dependencies/vtkm-d32f3457d8049a79cc59fb02c3dfb7879ef90ee3.tar.bz2 > > This corresponds to the following commit: > commit d32f3457d8049a79cc59fb02c3dfb7879ef90ee3 > Merge: c1f7a07 c6fdcea > Author: Kenneth Moreland > Date: Wed Jan 25 11:07:39 2017 -0500 > > > And you will find the build options in vtkm.cmake: > superbuild_add_project(vtkm > DEFAULT_ON > DEPENDS tbb cxx11 > CMAKE_ARGS > -DBUILD_SHARED_LIBS:BOOL=${BUILD_SHARED_LIBS} > -DVTKm_ENABLE_TBB:BOOL=${tbb_enabled} > -DVTKm_ENABLE_RENDERING:BOOL=OFF > -DVTKm_ENABLE_TESTING:BOOL=OFF > -DTBB_ROOT:PATH=) > > Best, > Joachim > > Joachim Pouderoux, PhD > > Technical Expert - Scientific Computing Team > Kitware SAS > > > 2017-02-14 11:17 GMT-04:00 GUILBAUD Claire : >> >> Hi all, >> >> I'm trying to build ParaView 5.3.0 with the last version of VTK-m (sources >> download today using git clone https://gitlab.kitware.com/vtk/vtk-m.git). I >> compile VTK-m with TBB backend (version 4.2), gcc 4.9 and -std=c++11 option. >> >> I have the following issues a lot of times when compiling : >> >> In file included from >> .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmContour.cxx:30:0: >> .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h: In member >> function 'vtkm::cont::internal::Storage> tovtkm::vtkAOSArrayContainerTag>& vtkm::cont::internal::Storage> tovtkm::vtkAOSArrayContainerTag>::operator=(const >> vtkm::cont::internal::Storage> tovtkm::vtkAOSArrayContainerTag>&)': >> .../ParaView-v5.3.0-RC1/VTK/Accelerators/Vtkm/vtkmlib/Storage.h:69:13: >> error: 'ErrorControlBadValue' is not a member of 'vtkm::cont' >> throw vtkm::cont::ErrorControlBadValue( >> >> Looking at sources, it seems that vtkm::cont::ErrorControlBadValue has >> been replaced by vtkm::cont::ErrorBadValue. >> >> I can patch all sources, but I think it's not a good idea. >> >> So, which version of VTK-m is needed for ParaView 5.3.0 ? >> >> Thanks >> >> Claire >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 u.utku.turuncoglu at be.itu.edu.tr Tue Feb 14 15:20:47 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 14 Feb 2017 22:20:47 +0200 (EET) Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <20170214181643.GC7593@megas.kitware.com> References: <20170214181643.GC7593@megas.kitware.com> Message-ID: <61387.88.235.32.169.1487103647.squirrel@webmail.be.itu.edu.tr> Hi, I don't have access to the server right now and I could not check the cake version but probably it is 3.7.x. So, I'll try to test the newer version and i'll get back to you then (probably on Thursday). Thanks for your help. Regards, --ufuk > On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh Ayachit wrote: >> Chuck, is this a CMake version related issue? Ufuk, which cmake >> version are you using? > > It likely is. VTK is now using CMake's C++11 support detection and older > versions of CMake do not have the required bits for Intel 16. These > appear to have been introduced in 3.8.0, but may have been in 3.7.0 (I'm > not completely sure). > > --Ben > From andy.bauer at kitware.com Tue Feb 14 15:27:06 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 14 Feb 2017 15:27:06 -0500 Subject: [Paraview] Automating contour isosurface values in parallel Catalyst Python script In-Reply-To: References: <1487021489.6937.2.camel@free.fr> Message-ID: Hi Yvan, Another option is just to compute it yourself. The reason that the global min and max aren't know in Catalyst is that it requires communication but many times the value isn't needed so in order to make Catalyst more efficient it doesn't compute that value for you automatically. In the Python scripts you can import mpi4py or import vtk and use the vtkMultiProcessController to do the global operation. Note that for my way you'll need to call UpdatePipeline(datadescription.GetTime()) before getting the output and globally determining the value. Then you can set the isosurfaces values array with that information. If you try this out and have issues, please let us know and we can go from there. Cheers, Andy On Tue, Feb 14, 2017 at 3:02 PM, Joachim Pouderoux < joachim.pouderoux at kitware.com> wrote: > Hi Yvan, > > Regarding MinMax: this filter is indeed not exposed by any standard > Catalyst edition but it is > easy to add. See for instance in ParaView/Catalyst/Editions/Extras/manifest.json > how the > PVExtractSelection filter is exposed (line 50 and 247). > Just do the same with the MinMax filter (see proxy's declaration at > filters.xml:~11725). > > Best, > Joachim > > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2017-02-13 17:31 GMT-04:00 Yvan Fournier : > >> Hello, >> >> I'm in the process of migrating some VTK scripts in the Code_Saturne >> (code- >> saturne.org) test suite to Catalyst Python scripts, and am having some >> difficulty automating some cases using contour plots: >> >> For time-dependent data, I do not know the value ranges in advance, and >> would >> like to query them so as to build an Isosurface values array spanning that >> range. >> >> I can manage to access the point and cell data arrays and ther ranges, but >> printing the ranges in parallel, it seems I have local values only, while >> I need >> a global range. >> >> I searched for examples in the documentation, on the Wiki, ..., and found >> an >> example for MinMax, but don't seem to ba able to access the correct type >> of >> Proxy under Catalyst (the default servermanager is not connected in the >> usual >> way. >> >> For scalar bar color look-up tables, I can manage with >> "coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in >> the >> coprocessing script, but for a more general case such as thar needed for >> contour >> plots, I've been running around in circles in the last hours trying to >> find and >> adapt a relevant example. >> >> Does anyone have a suggestion ? Thanks in advance, >> >> Yvan Fournier >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 info at feacluster.com Tue Feb 14 16:55:05 2017 From: info at feacluster.com (Faraz Hussain) Date: Tue, 14 Feb 2017 16:55:05 -0500 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> Message-ID: <20170214165505.Horde.xePVRwV6yG_9EBOJAkUU92V@feacluster.com> Unfortunately, I am not having much luck getting Paraview to build. I keep trying to configure (c), but the generate (g) option does not come. I am wondering if someone would be willing to poke around in my system . I can pay some nominal amount for your time. However , since this is mainly for education my budget is limited ( ~$100 ). Quoting Sebastien Jourdain : > You need to hit [c](configure) several time before getting the generate. > > On Fri, Feb 10, 2017 at 2:33 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> Also for paraviewweb, don't forget: >> >> PARAVIEW_ENABLE_PYTHON=ON >> >> Cheers, >> >> Scott >> >> On Fri, Feb 10, 2017 at 2:31 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> I would think you'd want to build with: >>> >>> PARAVIEW_BUILD_QT_GUI=OFF >>> >>> Hope this helps, >>> >>> Scott >>> >>> On Fri, Feb 10, 2017 at 2:25 PM, Faraz Hussain >>> wrote: >>> >>>> Thanks for your help in installing Paraview on a raspberry pi. I >>>> followed the steps in: >>>> >>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install >>>> >>>> However, when I configure ccmake it says QT is needed. I could not >>>> figure out if I can ignore that. The "generate" command did not come up. >>>> >>>> On a side note, it took me a while to find ccmake. I thought it was >>>> installed with cmake, but seems I had to install it separately using "sudo >>>> apt-get install cmake-curses-gui" . Perhaps the instructions should be >>>> updated to reflect this to avoid confusion. >>>> >>>> >>>> Quoting Sebastien Jourdain : >>>> >>>> Wow, >>>>> >>>>> I'm not an expert on raspberry pi but it should be possible. >>>>> BUT, (and it is a big but) you need some graphics capability for >>>>> ParaView >>>>> or good CPUs if you don't have a GPU. >>>>> Or the rendering will be really slow. >>>>> >>>>> The quicker test you can do, is to build ParaView (without Qt) and try >>>>> to >>>>> run Visualizer with that ParaView in the command line to see what >>>>> performance you are getting. If that's reasonable, then all the network >>>>> setup should be "trivial". >>>>> >>>>> ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install >>>>> Visualizer: https://kitware.github.io/visualizer/ >>>>> >>>>> Good luck, >>>>> >>>>> Seb >>>>> >>>>> On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain >>>>> wrote: >>>>> >>>>> I want to be able to manipulate vtk file on my raspberry pi via a web >>>>>> browser anywhere in the world. I believe I need to install paraviewweb >>>>>> and >>>>>> do some reconfiguration of apache and the virtual hosts? >>>>>> Unfortunately, I >>>>>> am not a guru of Linux. So before I attempt it all, is it even >>>>>> possible to >>>>>> do this on a raspberry pi? I am using raspian . >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> >> From cory.quammen at kitware.com Tue Feb 14 16:57:20 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 14 Feb 2017 16:57:20 -0500 Subject: [Paraview] PV5.2 Scalarbar range error In-Reply-To: References: Message-ID: Hi Bob, This issue has been identified and a fix will be in ParaView 5.3.0. Please see https://gitlab.kitware.com/paraview/paraview/issues/17152 for more information. Thanks, Cory On Thu, Jan 12, 2017 at 11:17 AM, Bob Flandard wrote: > Hi, > > I'm using PV5.2 on Windows 7 64bit. > > When a contour plot has a prescribed range that is quite small (or if the > range of data is small), the scalarbar ignores the upper limit and invents > its own. This was not so in PV5.1, so could be related to the new off-scale > color range feature (which was a most welcome addition - thanks). > > Two state files attached, with error in PV5.2 and no error in PV 5.1. > > Thanks, Bob > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 fabidi89 at vt.edu Tue Feb 14 18:01:04 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 14 Feb 2017 18:01:04 -0500 Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 In-Reply-To: <181475582.1543787.1487100772876.JavaMail.zimbra@lncmi.cnrs.fr> References: <181475582.1543787.1487100772876.JavaMail.zimbra@lncmi.cnrs.fr> Message-ID: Utkarsh - I think I am missing /usr/lib64/qt4/bin/xmlpatterns but that's just a warning. Attached is the CMakeCache file. Christophe - That didn't work for me. But thanks for suggesting. On Tue, Feb 14, 2017 at 2:32 PM, Christophe Trophime < christophe.trophime at lncmi.cnrs.fr> wrote: > I had a similar problem on debian > > export QT_SELECT=qt5 or qt4 > > before running cmake fix the problem > > > > Christophe TROPHIME > Research Engineer > > CNRS - LNCMI > 25, rue des Martyrs > BP 166 > 38042 GRENOBLE Cedex 9 > FRANCE > > Tel : +33 (0)4 76 88 90 02 > Fax : +33 (0) 4 76 88 10 01 > Office U 19 > M at il : christophe.trophime at lncmi.cnrs.fr > > ----- Original Message ----- > > From: "Utkarsh Ayachit" > > To: "Faiz Abidi" > > Cc: "ParaView" > > Sent: Tuesday, February 14, 2017 8:16:20 PM > > Subject: Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0 > > > > Can you post your CMakeCache.txt? I suspect one of the Qt help > > generation tools was not found/set correctly. > > > > Utkarsh > > > > On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: > > > Hello community, > > > > > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? > When I > > > install Paraview from source, I get the below error. > > > > > > "/bin/sh: line 0: cd: > > > /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: > No > > > such file or directory > > > make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 > > > make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] Error > 2" > > > > > > I am not sure if I am missing a dependency. The install works fine > without > > > this plugin. > > > > > > Anyone seen this before? > > > -- > > > 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 > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView 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 -------------- # This is the CMakeCache file. # For build in directory: /home/fabidi89/git/ParaView/build_cmake # It was generated by CMake: /opt/apps/cmake/3.7.2/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 Verdict 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=/opt/apps/gcc/5.2.0/bin/g++ //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=/opt/apps/gcc/5.2.0/bin/gcc //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=/opt/apps/gcc/5.2.0/bin/gfortran //Fortran flags CMAKE_Fortran_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_Fortran_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG -Os //Flags used by the compiler during release builds. CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3 -DNDEBUG -O3 //Flags used by the compiler during release builds with debug info. CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //user executables (bin) CMAKE_INSTALL_BINDIR:PATH=bin //read-only architecture-independent data (DATAROOTDIR) CMAKE_INSTALL_DATADIR:PATH= //read-only architecture-independent data root (share) CMAKE_INSTALL_DATAROOTDIR:PATH=share //documentation root (DATAROOTDIR/doc/PROJECT_NAME) CMAKE_INSTALL_DOCDIR:PATH= //C header files (include) CMAKE_INSTALL_INCLUDEDIR:PATH=include //info documentation (DATAROOTDIR/info) CMAKE_INSTALL_INFODIR:PATH= //object code libraries (lib64) CMAKE_INSTALL_LIBDIR:PATH=lib64 //program executables (libexec) CMAKE_INSTALL_LIBEXECDIR:PATH=libexec //locale-dependent data (DATAROOTDIR/locale) CMAKE_INSTALL_LOCALEDIR:PATH= //modifiable single-machine data (var) CMAKE_INSTALL_LOCALSTATEDIR:PATH=var //man documentation (DATAROOTDIR/man) CMAKE_INSTALL_MANDIR:PATH= //C header files for non-gcc (/usr/include) CMAKE_INSTALL_OLDINCLUDEDIR:PATH=/usr/include //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/home/fabidi89/Paraview-v5.2.0 //system admin executables (sbin) CMAKE_INSTALL_SBINDIR:PATH=sbin //modifiable architecture-independent data (com) CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com //read-only single-machine data (etc) CMAKE_INSTALL_SYSCONFDIR:PATH=etc //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake //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 CatalystScriptGeneratorPlugin_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/Plugins/CatalystScriptGenerator //Dependencies for the target CatalystScriptGeneratorPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;Qt4::QtGui;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;vtkPVServerManagerRendering; //Value Computed by CMake CatalystScriptGeneratorPlugin_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/Plugins/CatalystScriptGenerator //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/Utilities/DICOMParser //Value Computed by CMake DIY2_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/diy2/vtkdiy2 //Value Computed by CMake DIY2_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/diy2/vtkdiy2 //Path to a library. EXECINFO_LIB:FILEPATH=EXECINFO_LIB-NOTFOUND //Disable compiler warnings EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON //Additional URL templates for the ExternalData CMake script to // look for testing data. E.g. //\nfile:///var/bigharddrive/%(algo)/%(hash) ExternalData_URL_TEMPLATES:STRING= //Value Computed by CMake FmmMesh_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/Plugins/GeodesicMeasurementPlugin/FmmMesh //Dependencies for target FmmMesh_LIB_DEPENDS:STATIC= //Value Computed by CMake FmmMesh_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/Plugins/GeodesicMeasurementPlugin/FmmMesh //Git command line client GIT_EXECUTABLE:FILEPATH=/usr/bin/git //The directory containing gmvread.c, gmvread.h and gmvrayread.h GMVReader_GMVREAD_LIB_DIR:PATH=/home/fabidi89/git/ParaView/Utilities/VisItBridge/databases/GMV //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.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/fabidi89/git/ParaView/build_cmake/Plugins/GeodesicMeasurementPlugin //Value Computed by CMake GeodesicMeasurementPlugin_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/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;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //IEEE floating point is available HAVE_IEEEFP:STRING=1 //Value Computed by CMake HDF5_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/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/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SRC_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //Value Computed by CMake HDF5_HL_SRC_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/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/fabidi89/git/ParaView/VTK/ThirdParty/hdf5/vtkhdf5 //Value Computed by CMake HDF5_SRC_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/hdf5/vtkhdf5/src //Value Computed by CMake HDF5_SRC_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/src //Enable folder grouping of projects in IDEs. HDF5_USE_FOLDERS:BOOL=ON //Native CPU bit order HOST_BIG_ENDIAN:STRING=OFF //Native CPU bit order HOST_FILLORDER:STRING=FILLORDER_LSB2MSB //Value Computed by CMake ICET_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/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/fabidi89/git/ParaView/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/fabidi89/Paraview-v5.2.0/bin //Installation directory for headers INSTALL_INC_DIR:PATH=/home/fabidi89/Paraview-v5.2.0/include //Installation directory for libraries INSTALL_LIB_DIR:PATH=/home/fabidi89/Paraview-v5.2.0/lib //Installation directory for manual pages INSTALL_MAN_DIR:PATH=/home/fabidi89/Paraview-v5.2.0/share/man //Installation directory for pkgconfig (.pc) files INSTALL_PKGCONFIG_DIR:PATH=/home/fabidi89/Paraview-v5.2.0/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;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake LZ4_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/ThirdParty/lz4/vtklz4 //Value Computed by CMake LZ4_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/ThirdParty/lz4/vtklz4 //Executable for running MPI programs. MPIEXEC:FILEPATH=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpiexec //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=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING= //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/opt/apps/gcc5_2/mpich/3.1.4/include //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= -Wl,-rpath,/opt/apps/gcc/5.2.0/lib64 -Wl,-rpath -Wl,/opt/apps/gcc5_2/mpich/3.1.4/lib -Wl,--enable-new-dtags //Path to a program. MPI_C_COMPILER:FILEPATH=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING= //MPI C include path MPI_C_INCLUDE_PATH:STRING=/opt/apps/gcc5_2/mpich/3.1.4/include //MPI C libraries to link against MPI_C_LIBRARIES:STRING=/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so //MPI C linking flags MPI_C_LINK_FLAGS:STRING= -Wl,-rpath,/opt/apps/gcc/5.2.0/lib64 -Wl,-rpath -Wl,/opt/apps/gcc5_2/mpich/3.1.4/lib -Wl,--enable-new-dtags //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so //Path to a program. MPI_Fortran_COMPILER:FILEPATH=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpif90 //MPI Fortran compilation flags MPI_Fortran_COMPILE_FLAGS:STRING= //MPI Fortran include path MPI_Fortran_INCLUDE_PATH:STRING=/opt/apps/gcc5_2/mpich/3.1.4/include;/opt/apps/gcc5_2/mpich/3.1.4/include //MPI Fortran libraries to link against MPI_Fortran_LIBRARIES:STRING=/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpifort.so;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so //MPI Fortran linking flags MPI_Fortran_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/opt/apps/gcc5_2/mpich/3.1.4/lib -Wl,--enable-new-dtags //MPI library to link against MPI_LIBRARY:FILEPATH=/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so //Path to a library. M_LIBRARY:FILEPATH=/usr/lib64/libm.so //Poisson Surface reconstruction from unorganized points Module_PoissonReconstruction: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 pqDeprecated Module_pqDeprecated: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 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 vtkIOTRUCHAS Module_vtkIOTRUCHAS: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 vtkImagingOpenGL2 Module_vtkImagingOpenGL2: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 vtkParseOGLExt Module_vtkParseOGLExt: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 vtkRenderingOculus Module_vtkRenderingOculus:BOOL=OFF //Request building vtkRenderingOpenVR Module_vtkRenderingOpenVR: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 vtkViewsGeovis Module_vtkViewsGeovis:BOOL=OFF //Request building vtkViewsInfovis Module_vtkViewsInfovis:BOOL=OFF //Request building vtkViewsQt Module_vtkViewsQt: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 vtklibproj4 Module_vtklibproj4: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;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;pqApplicationComponents; //Path to a file. OPENGL_INCLUDE_DIR:PATH=/usr/include //Path to a library. OPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so //Path to a library. OPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so //Path to a file. OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND //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 CatalystScriptGeneratorPlugin Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin: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 SLACTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SLACTools: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 //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 CatalystScriptGeneratorPlugin Plugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin: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 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 PythonQtPlugin Plugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=FALSE //Build SLACTools Plugin PARAVIEW_BUILD_PLUGIN_SLACTools: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 TemporalParallelismScriptGenerator Plugin PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=FALSE //Build ThickenLayeredCells Plugin PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells:BOOL=TRUE //Build VRPlugin Plugin PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL=FALSE //Build VaporPlugin Plugin PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE //Enable ParaView Qt-based client PARAVIEW_BUILD_QT_GUI:BOOL=ON //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 with CosmoTools VTK Extensions PARAVIEW_ENABLE_COSMOTOOLS:BOOL=OFF //Build the ParaView help menu documentation for ParaView and its // plugins PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION:BOOL=ON //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 //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 //Semicolon separated absolute paths to external directories containing // extra VTK/ParaView modules. PARAVIEW_EXTERNAL_MODULE_ROOTS:STRING= //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= //Select Qt verision to use 4 or 5 PARAVIEW_QT_VERSION:STRING=4 //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 //Use Qt Help infrastructure as needed. PARAVIEW_USE_QTHELP:BOOL=ON //Use Qt WebKit components as needed. PARAVIEW_USE_QTWEBKIT: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=/opt/apps/gcc5_2/python/2.7.10/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=/opt/apps/gcc5_2/python/2.7.10/include/python2.7 //Path to a library. PYTHON_LIBRARY:FILEPATH=/opt/apps/gcc5_2/python/2.7.10/lib/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/lib64/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/fabidi89/git/ParaView/build_cmake //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libarthurplugin.so //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libcontainerextension.so //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libcustomwidgetplugin.so //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=QT_DBUSCPP2XML_EXECUTABLE-NOTFOUND //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=QT_DBUSXML2CPP_EXECUTABLE-NOTFOUND //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/designer //The location of the Qt docs QT_DOC_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/doc //qhelpgenerator used to compile Qt help project files QT_HELP_GENERATOR:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/qhelpgenerator //The location of the Qt imports QT_IMPORTS_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/imports //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/linguist //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/lrelease //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/lupdate //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/moc //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=QT_PHONONWIDGETS_PLUGIN_RELEASE-NOTFOUND //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=QT_PHONON_INCLUDE_DIR-NOTFOUND //The Qt PHONON library QT_PHONON_LIBRARY:STRING= //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=QT_PHONON_LIBRARY_RELEASE-NOTFOUND //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/qcollectiongenerator //Path to a library. QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libqdeclarativeview.so //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/bearer/libqgenericbearer.so //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqgif.so //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/graphicssystems/libqglgraphicssystem.so //Path to a library. QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QICO_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqico.so //Path to a library. QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/codecs/libqjpcodecs.so //Path to a library. QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqjpeg.so //Path to a library. QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/codecs/libqkrcodecs.so //The qmake executable for the Qt installation to use QT_QMAKE_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/qmake //Path to a library. QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QMNG_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqmng.so //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/sqldrivers/libqsqlite.so //Path to a library. QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLPSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/iconengines/libqsvgicon.so //Path to a library. QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqsvg.so //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQt3Support.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQt3Support.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=QT_QT3SUPPORT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQt3Support.so //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/accessible/libqtaccessiblecompatwidgets.so //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCLucene.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCLucene.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=QT_QTCLUCENE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCore.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCore.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=QT_QTCORE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=QT_QTDBUS_INCLUDE_DIR-NOTFOUND //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING= //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=QT_QTDBUS_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTDECLARATIVE_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtDeclarative //The Qt QTDECLARATIVE library QT_QTDECLARATIVE_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDeclarative.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDeclarative.so //Path to a library. QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDeclarative.so //Path to a file. QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesignerComponents.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesignerComponents.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesigner.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesigner.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNER_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtDesigner.so //Path to a library. QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTGA_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqtga.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtGui.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtGui.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=QT_QTGUI_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtHelp.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtHelp.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=QT_QTHELP_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtHelp.so //Path to a library. QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/imageformats/libqtiff.so //Path to a file. QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND //The Qt QTMOTIF library QT_QTMOTIF_LIBRARY:STRING= //Path to a library. QT_QTMOTIF_LIBRARY_DEBUG:FILEPATH=QT_QTMOTIF_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMOTIF_LIBRARY_RELEASE:FILEPATH=QT_QTMOTIF_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtMultimedia //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtMultimedia.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtMultimedia.so //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtMultimedia.so //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtNetwork.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtNetwork.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=QT_QTNETWORK_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtNetwork.so //Path to a file. QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND //The Qt QTNSPLUGIN library QT_QTNSPLUGIN_LIBRARY:STRING= //Path to a library. QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTOPENGL_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtOpenGL.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtOpenGL.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=QT_QTOPENGL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtOpenGL.so //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/graphicssystems/libqtracegraphicssystem.so //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_RELEASE-NOTFOUND //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtScriptTools //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScriptTools.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScriptTools.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScriptTools.so //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtScript //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScript.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScript.so //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtScript.so //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSql.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSql.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=QT_QTSQL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtSvg //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSvg.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSvg.so //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=QT_QTSVG_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtSvg.so //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtTest.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtTest.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=QT_QTTEST_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtUiTools.a;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtUiTools.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTUITOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtUiTools.a //Path to a library. QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/codecs/libqtwcodecs.so //Path to a file. QT_QTWEBKIT_INCLUDE_DIR:PATH=QT_QTWEBKIT_INCLUDE_DIR-NOTFOUND //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING= //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=QT_QTWEBKIT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=QT_QTXMLPATTERNS_INCLUDE_DIR-NOTFOUND //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING= //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/include/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=optimized;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtXml.so;debug;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtXml.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=QT_QTXML_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/lib/libQtXml.so //Path to a library. QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=QT_QWEBVIEW_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_RCC_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/rcc //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libtaskmenuextension.so //Delay between invocation of each testing event. QT_TESTING_EVENT_PLAYBACK_DELAY:STRING=100 //The location of the Qt translations QT_TRANSLATIONS_DIR:PATH=/opt/apps/gcc5_2/qt/4.8.4/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/bin/uic //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=/opt/apps/gcc5_2/qt/4.8.4/plugins/designer/libworldtimeclockplugin.so //xmlpatterns used to generate html from Proxy documentation. QT_XMLPATTERNS_EXECUTABLE:FILEPATH=QT_XMLPATTERNS_EXECUTABLE-NOTFOUND //Value Computed by CMake QtTesting_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target QtTesting_LIB_DEPENDS:STATIC=general;Qt4::QtCore;general;Qt4::QtGui; //Value Computed by CMake QtTesting_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Explicitly disable SurfaceLIC plugin ctests SURFACELIC_PLUGIN_TESTING:BOOL=ON //Dependencies for the target SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault;general;Qt4::QtGui; //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;general;vtkRenderingLICOpenGL2; //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/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/VPIC //Value Computed by CMake VTKEXPAT_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKEXPAT_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKFREETYPE_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFREETYPE_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGLEW_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKGLEW_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/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/fabidi89/git/ParaView/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/oggtheora/vtkoggtheora //Value Computed by CMake VTKPNG_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKPNG_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/png/vtkpng //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/fabidi89/git/ParaView/build_cmake/VTK //Request to build all modules VTK_BUILD_ALL_MODULES:BOOL=OFF //Build the VTK Qt plugin for the Qt Designer. VTK_BUILD_QT_DESIGNER_PLUGIN: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/fabidi89/git/ParaView/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/home/fabidi89/git/ParaView/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 //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 //The full path to mpirun command VTK_MPIRUN_EXE:FILEPATH=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpiexec //Maximum number of processors available to run parallel applications. // (see /home/fabidi89/git/ParaView/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_MAX_NUMPROCS:STRING=2 //Flag used by mpi to specify the number of processes, the next // option will be the number of processes. (see /home/fabidi89/git/ParaView/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIRun.(see /home/fabidi89/git/ParaView/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by VTK_MPIRUN_EXE. (see /home/fabidi89/git/ParaView/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PREFLAGS:STRING= //These flags will be directly before the number of processess // flag (see /home/fabidi89/git/ParaView/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PRENUMPROC_FLAGS:STRING= //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=OFF //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=OpenGL2 //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/fabidi89/git/ParaView/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 //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 //Use system-installed 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 'pygments' Python package VTK_USE_SYSTEM_PYGMENTS:BOOL=OFF //Use system-installed qttesting VTK_USE_SYSTEM_QTTESTING: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 //Build VTK with Tk support VTK_USE_TK:BOOL=OFF //Use X for VTK render windows VTK_USE_X:BOOL=ON //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/fabidi89/git/ParaView/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/home/fabidi89/git/ParaView/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 //Path to a file. X11_ICE_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_ICE_LIB:FILEPATH=/usr/lib64/libICE.so //Path to a file. X11_SM_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_SM_LIB:FILEPATH=/usr/lib64/libSM.so //Path to a file. X11_X11_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_X11_LIB:FILEPATH=/usr/lib64/libX11.so //Path to a file. X11_XRes_INCLUDE_PATH:PATH=X11_XRes_INCLUDE_PATH-NOTFOUND //Path to a library. X11_XRes_LIB:FILEPATH=X11_XRes_LIB-NOTFOUND //Path to a file. X11_XShm_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_XSync_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_XTest_INCLUDE_PATH:PATH=X11_XTest_INCLUDE_PATH-NOTFOUND //Path to a library. X11_XTest_LIB:FILEPATH=X11_XTest_LIB-NOTFOUND //Path to a file. X11_Xaccessrules_INCLUDE_PATH:PATH=X11_Xaccessrules_INCLUDE_PATH-NOTFOUND //Path to a file. X11_Xaccessstr_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xau_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xau_LIB:FILEPATH=/usr/lib64/libXau.so //Path to a file. X11_Xcomposite_INCLUDE_PATH:PATH=X11_Xcomposite_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xcomposite_LIB:FILEPATH=X11_Xcomposite_LIB-NOTFOUND //Path to a file. X11_Xcursor_INCLUDE_PATH:PATH=X11_Xcursor_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xcursor_LIB:FILEPATH=X11_Xcursor_LIB-NOTFOUND //Path to a file. X11_Xdamage_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xdamage_LIB:FILEPATH=/usr/lib64/libXdamage.so //Path to a file. X11_Xdmcp_INCLUDE_PATH:PATH=X11_Xdmcp_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xdmcp_LIB:FILEPATH=X11_Xdmcp_LIB-NOTFOUND //Path to a library. X11_Xext_LIB:FILEPATH=/usr/lib64/libXext.so //Path to a file. X11_Xfixes_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xfixes_LIB:FILEPATH=/usr/lib64/libXfixes.so //Path to a file. X11_Xft_INCLUDE_PATH:PATH=X11_Xft_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xft_LIB:FILEPATH=X11_Xft_LIB-NOTFOUND //Path to a file. X11_Xi_INCLUDE_PATH:PATH=X11_Xi_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xi_LIB:FILEPATH=X11_Xi_LIB-NOTFOUND //Path to a file. X11_Xinerama_INCLUDE_PATH:PATH=X11_Xinerama_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xinerama_LIB:FILEPATH=X11_Xinerama_LIB-NOTFOUND //Path to a file. X11_Xinput_INCLUDE_PATH:PATH=X11_Xinput_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xinput_LIB:FILEPATH=X11_Xinput_LIB-NOTFOUND //Path to a file. X11_Xkb_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xkbfile_INCLUDE_PATH:PATH=X11_Xkbfile_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xkbfile_LIB:FILEPATH=X11_Xkbfile_LIB-NOTFOUND //Path to a file. X11_Xkblib_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xlib_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xmu_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xmu_LIB:FILEPATH=/usr/lib64/libXmu.so //Path to a file. X11_Xpm_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xpm_LIB:FILEPATH=/usr/lib64/libXpm.so //Path to a file. X11_Xrandr_INCLUDE_PATH:PATH=X11_Xrandr_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xrandr_LIB:FILEPATH=X11_Xrandr_LIB-NOTFOUND //Path to a file. X11_Xrender_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xrender_LIB:FILEPATH=/usr/lib64/libXrender.so //Path to a file. X11_Xscreensaver_INCLUDE_PATH:PATH=X11_Xscreensaver_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xscreensaver_LIB:FILEPATH=X11_Xscreensaver_LIB-NOTFOUND //Path to a file. X11_Xshape_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xt_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xt_LIB:FILEPATH=/usr/lib64/libXt.so //Path to a file. X11_Xutil_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xv_INCLUDE_PATH:PATH=X11_Xv_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xv_LIB:FILEPATH=X11_Xv_LIB-NOTFOUND //Path to a library. X11_Xxf86misc_LIB:FILEPATH=X11_Xxf86misc_LIB-NOTFOUND //Path to a library. X11_Xxf86vm_LIB:FILEPATH=/usr/lib64/libXxf86vm.so //Path to a file. X11_dpms_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_xf86misc_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_xf86vmode_INCLUDE_PATH:PATH=/usr/include //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=/usr/include/sys //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/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/alglib //Dependencies for the target mpi4py.MPE_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target mpi4py.MPI_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;dl; //Dependencies for the target mpi4py.dl_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;dl; //Value Computed by CMake mpi4py_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake mpi4py_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake netcdf_cxx_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_cxx_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Dependencies for the target pmpi-mpe_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target pmpi-vt-hyb_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target pmpi-vt-mpi_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target pmpi-vt_LIB_DEPENDS:STATIC=general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkjsoncpp;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;Qt4::QtHelp; //Dependencies for the target pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;vtkjsoncpp;general;Qt4::QtNetwork; //Dependencies for the target pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;general;Qt4::QtHelp; //Dependencies for the target pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;Qt4::QtGui; //Dependencies for the target pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;general;Qt4::QtNetwork;general;Qt4::QtHelp;general;Qt4::QtGui; //Dependencies for the target protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/ThirdParty/protobuf/vtkprotobuf //Dependencies for the target protobuf_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/ThirdParty/protobuf/vtkprotobuf //Value Computed by CMake tiff_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake tiff_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake verdict_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD; //Dependencies for the target vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtksys;general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkInfovisCore; //Dependencies for the target vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD; //Dependencies for the target vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD; //Dependencies for the target vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel; //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;vtkCommonCorePythonD;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;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkCommonMisc;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD; //Dependencies for the target vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //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;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD; //Dependencies for the target vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonCore;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 vtkDomainsChemistryOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkDomainsChemistryPythonD;general;vtkDomainsChemistryPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryOpenGL2PythonD; //Dependencies for the target vtkDomainsChemistryOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkDomainsChemistry;general;vtkDomainsChemistry;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkglew;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLParserPythonD;general;vtkRenderingCorePythonD;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD; //Dependencies for the target vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXMLParser;general;vtkRenderingCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys; //Value Computed by CMake vtkExodus2_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/exodusII/vtkexodusII //Dependencies for the target vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD; //Dependencies for the target vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkIOXML;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkCommonMath;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;vtkCommonCorePythonD;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;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD; //Dependencies for the target vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonComputationalGeometry;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;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;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD; //Dependencies for the target vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkImagingCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkCommonMath;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkImagingCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD; //Dependencies for the target vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonCore;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD; //Dependencies for the target vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersStatistics;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkImagingGeneral; //Dependencies for the target vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;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;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkParallelMPI;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkIOCorePythonD;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;vtkCommonCore;general;vtkFiltersFlowPaths;general;vtkFiltersFlowPaths;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkFiltersCore;general;vtkIOCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD; //Dependencies for the target vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeometry;general;vtkParallelMPI;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkIOLegacy;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD; //Dependencies for the target vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersStatistics;general;vtkImagingGeneral;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkImagingCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOLegacyPythonD;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;vtkFiltersStatistics;general;vtkalglib;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkFiltersSources;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOLegacy;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPython_LIB_DEPENDS:STATIC=general;vtkFiltersPointsPythonD; //Dependencies for the target vtkFiltersPoints_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel; //Dependencies for the target vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD; //Dependencies for the target vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;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;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;vtkCommonCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD; //Dependencies for the target vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonComputationalGeometry;general;vtkCommonCore;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkImagingFourierPythonD;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD; //Dependencies for the target vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkalglib;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkImagingFourier; //Dependencies for the target vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD; //Dependencies for the target vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkInteractionStyle;general;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtGui.so;general;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtNetwork.so;general;/opt/apps/gcc5_2/qt/4.8.4/lib/libQtCore.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so; //Dependencies for the target vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;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;vtkCommonCorePythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtksys;general;vtkzlib; //Dependencies for the target vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD; //Dependencies for the target vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD; //Dependencies for the target vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOXMLParser;general;vtkexoIIc;general;vtkFiltersCore;general;vtksys; //Dependencies for the target vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport; //Dependencies for the target vtkIOExportOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOExportPythonD;general;vtkIOExportPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkIOExportOpenGL2PythonD; //Dependencies for the target vtkIOExportOpenGL2_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkIOExport;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkRenderingCore;general;vtkgl2ps;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkIOExport; //Dependencies for the target vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD; //Dependencies for the target vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkRenderingCore;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeometry;general;vtkIOImage;general;vtkImagingCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD; //Dependencies for the target vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOLegacy;general;vtkCommonCore;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;general;vtkzlib; //Dependencies for the target vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage; //Dependencies for the target vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImage; //Dependencies for the target vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD; //Dependencies for the target vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkDICOMParser;general;vtkmetaio;general;vtkjpeg;general;vtkpng;general;vtksys;general;vtktiff;general;vtkzlib; //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;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;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;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkRenderingCore;general;vtksys;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkIOXMLParserPythonD;general;vtkInfovisCorePythonD;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD; //Dependencies for the target vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXML;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkIOCore;general;vtkIOXMLParser;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD; //Dependencies for the target vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD; //Dependencies for the target vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkCommonMisc;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkParallelCore;general;vtkParallelMPI;general;vtksys;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelMPI;general;vtksys;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD; //Dependencies for the target vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkoggtheora;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //Dependencies for the target vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD; //Dependencies for the target vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys; //Dependencies for the target vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD; //Dependencies for the target vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkCommonDataModel;general;vtkCommonMisc; //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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;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;vtkCommonCore;general;vtkIOExodus;general;vtkIOExodus;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkParallelCore;general;vtkexoIIc;general;vtksys; //Dependencies for the target vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkIOLSDyna;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkParallelMPIPythonD;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD; //Dependencies for the target vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkNetCDF;general;vtkNetCDF_cxx;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkIOCorePythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOLegacyPythonD;general;vtkIONetCDFPythonD;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOGeometry;general;vtkIOImage;general;vtkIOLegacy;general;vtkIONetCDF;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkParallelCore;general;vtkexoIIc;general;vtkjsoncpp;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys; //Dependencies for the target vtkIOTecplotTableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePython_LIB_DEPENDS:STATIC=general;vtkIOTecplotTablePythonD; //Dependencies for the target vtkIOTecplotTable_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;VPIC;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkParallelCore; //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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD; //Dependencies for the target vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkIOCore;general;vtkexpat; //Dependencies for the target vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkIOXML; //Dependencies for the target vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD; //Dependencies for the target vtkIOXML_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;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;vtkIOXMLParserPythonD;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;vtkIOLegacy;general;vtkFiltersExtraction;general;vtkIOXMLParser;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingCorePythonD;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD; //Dependencies for the target vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem; //Dependencies for the target vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD; //Dependencies for the target vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD; //Dependencies for the target vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD; //Dependencies for the target vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOImage;general;vtkImagingCore; //Dependencies for the target vtkImagingMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPython_LIB_DEPENDS:STATIC=general;vtkImagingMathPythonD; //Dependencies for the target vtkImagingMath_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD; //Dependencies for the target vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD; //Dependencies for the target vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD; //Dependencies for the target vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingColor;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD; //Dependencies for the target vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersExtraction;general;vtkFiltersSources; //Dependencies for the target vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingCorePythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkRenderingCore;general;vtkCommonComputationalGeometry;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingColor;general;vtkImagingCore;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;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkIOLegacyPythonD;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;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.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;vtkRenderingVolumeOpenGL2PythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;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;vtkRenderingVolumeOpenGL2;general;vtkViewsContext2D;general;vtkViewsCore;general;vtksys;general;vtkzlib;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkDomainsChemistryOpenGL2PythonD;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;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;vtkIOTecplotTablePythonD;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;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;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;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkCommonColorCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkInteractionStyleCS;general;vtkIOImageCS;general;vtkRenderingOpenGL2CS;general;vtkFiltersModelingCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkParallelMPICS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkIOXMLCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkDomainsChemistryCS;general;vtkFiltersAMRCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkIOMPIImageCS;general;vtkIOPLYCS;general;vtkIOGeometryCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingColorCS;general;vtkImagingGeneralCS;general;vtkImagingHybridCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelMPICS;general;vtkRenderingGL2PSOpenGL2CS;general;vtkIOExportCS;general;vtkIOExportOpenGL2CS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkImagingMathCS;general;vtkRenderingVolumeOpenGL2CS;general;vtkRenderingVolumeAMRCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingLabelCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkDomainsChemistryOpenGL2CS;general;vtkFiltersParallelDIY2CS;general;vtkFiltersParallelGeometryCS;general;vtkFiltersImagingCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOMPIParallelCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOTecplotTableCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;general;vtkFiltersPointsCS;general;vtkPVVTKExtensionsPointsCS;general;vtkParallelMPI4PyCS;general;vtkRenderingLICOpenGL2CS;general;vtkRenderingLODCS;general;vtkRenderingParallelLICCS;general;vtkWebGLExporterCS;general;vtkWebCoreCS;general;vtkParaViewWebCoreCS;general;vtkRenderingContextOpenGL2CS;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;vtkRenderingVolumeOpenGL2PythonD;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;vtkRenderingVolumeOpenGL2;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;vtkFiltersExtractionPythonD;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;vtkFiltersExtraction;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;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOExportOpenGL2PythonD;general;vtkIOImagePythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;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;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkGUISupportQt;general;vtkIOExport;general;vtkIOExportOpenGL2;general;vtkIOImage;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL2;general;vtkRenderingParallel;general;vtkRenderingVolumeAMR;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkglew;general;vtkzlib;general;vtklz4;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkParaViewDocumentation_LIB_DEPENDS:STATIC=general;Qt4::QtGui; //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;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonDataModel;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD; //Dependencies for the target vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;vtkParallelMPI;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelCore;general;vtkCommonDataModel;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.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;/opt/apps/gcc5_2/python/2.7.10/lib/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD; //Dependencies for the target vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkImagingColor;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContextOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL2PythonD; //Dependencies for the target vtkRenderingContextOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingContext2D;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkImagingCore;general;vtkglew;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkCommonColor;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersSources;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkCommonDataModel;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingGL2PSOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSOpenGL2PythonD; //Dependencies for the target vtkRenderingGL2PSOpenGL2_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2;general;vtkRenderingOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkgl2ps;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingLICOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingLICOpenGL2PythonD; //Dependencies for the target vtkRenderingLICOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtkglew;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;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;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersModeling; //Dependencies for the target vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD; //Dependencies for the target vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD; //Dependencies for the target vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkRenderingFreeType;general;vtkRenderingFreeType;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkImagingCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;vtkRenderingCore;general;vtkWrappingPythonCore; //Dependencies for the target vtkRenderingOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2PythonD; //Dependencies for the target vtkRenderingOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOImage;general;vtkImagingCore;general;vtkglew;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so;general;/usr/lib64/libXt.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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD; //Dependencies for the target vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkRenderingLICOpenGL2;general;vtkRenderingOpenGL2;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;general;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so; //Dependencies for the target vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD; //Dependencies for the target vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkglew;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersParallel;general;vtkIOImage;general;vtkImagingCore;general;vtkParallelCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD; //Dependencies for the target vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingVolume;general;vtkRenderingVolumeOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkRenderingCore; //Dependencies for the target vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumeOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingCorePythonD;general;vtkImagingMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL2PythonD; //Dependencies for the target vtkRenderingVolumeOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkImagingMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingVolume;general;vtkRenderingVolume;general;vtkglew;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOXMLPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOXML;general;vtkImagingCore; //Dependencies for the target vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOImage;general;vtkImagingCore;general;vtksys; //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;vtkCommonCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCorePythonD;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD; //Dependencies for the target vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkViewsCore;general;vtkRenderingContext2D; //Dependencies for the target vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkInteractionWidgets;general;vtkCommonDataModel;general;vtkFiltersGeneral;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;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersGeneral;general;vtkIOCore;general;vtkIOImage;general;vtkParallelCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so;general;vtkRenderingCore;general;vtkWebGLExporter;general;vtksys; //Dependencies for the target vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOCorePythonD;general;vtkIOExportPythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPython_LIB_DEPENDS:STATIC=general;vtkWebGLExporterPythonD; //Dependencies for the target vtkWebGLExporter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOExport;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkFiltersGeometry;general;vtkIOCore;general;vtkInteractionWidgets;general;vtkRenderingAnnotation;general;vtkRenderingCore;general;vtksys; //Dependencies for the target vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/opt/apps/gcc5_2/python/2.7.10/lib/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;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;m; //Dependencies for the target vtkglew_LIB_DEPENDS:STATIC=general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //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/fabidi89/git/ParaView/build_cmake/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/fabidi89/git/ParaView/VTK/ThirdParty/libxml2/vtklibxml2 //Dependencies for target vtklz4_LIB_DEPENDS:STATIC= //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/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/fabidi89/git/ParaView/build_cmake/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/fabidi89/git/ParaView/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtktiff_LIB_DEPENDS:STATIC=general;/usr/lib64/libm.so;general;vtkzlib;general;vtkjpeg; //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/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake zlib_BINARY_DIR:STATIC=/home/fabidi89/git/ParaView/build_cmake/VTK/ThirdParty/zlib/vtkzlib //Value Computed by CMake zlib_SOURCE_DIR:STATIC=/home/fabidi89/git/ParaView/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/fabidi89/git/ParaView/build_cmake //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=2 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/opt/apps/cmake/3.7.2/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/opt/apps/cmake/3.7.2/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/opt/apps/cmake/3.7.2/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=/opt/apps/cmake/3.7.2/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 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_DEBUG CMAKE_Fortran_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_MINSIZEREL CMAKE_Fortran_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELEASE CMAKE_Fortran_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELWITHDEBINFO CMAKE_Fortran_FLAGS_RELWITHDEBINFO-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 function connect CMAKE_HAVE_CONNECT:INTERNAL=1 //Have function gethostbyname CMAKE_HAVE_GETHOSTBYNAME:INTERNAL=1 //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 //Have function remove CMAKE_HAVE_REMOVE:INTERNAL=1 //Have function shmat CMAKE_HAVE_SHMAT:INTERNAL=1 //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/home/fabidi89/git/ParaView //ADVANCED property for variable: CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATADIR CMAKE_INSTALL_DATADIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATAROOTDIR CMAKE_INSTALL_DATAROOTDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DOCDIR CMAKE_INSTALL_DOCDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INCLUDEDIR CMAKE_INSTALL_INCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INFODIR CMAKE_INSTALL_INFODIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LIBDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBEXECDIR CMAKE_INSTALL_LIBEXECDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALEDIR CMAKE_INSTALL_LOCALEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_LOCALSTATEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_MANDIR CMAKE_INSTALL_MANDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_OLDINCLUDEDIR CMAKE_INSTALL_OLDINCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SBINDIR CMAKE_INSTALL_SBINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SHAREDSTATEDIR CMAKE_INSTALL_SHAREDSTATEDIR-ADVANCED:INTERNAL=1 //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0 //ADVANCED property for variable: CMAKE_INSTALL_SYSCONFDIR CMAKE_INSTALL_SYSCONFDIR-ADVANCED:INTERNAL=1 //Have library ICE CMAKE_LIB_ICE_HAS_ICECONNECTIONNUMBER: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=246 //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=/opt/apps/cmake/3.7.2/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=/usr/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 //Test C_FLAG_W C_FLAG_W:INTERNAL=1 //Test C_FLAG_Wall C_FLAG_Wall:INTERNAL=1 //Test C_FLAG_Wdeclaration_after_statement C_FLAG_Wdeclaration_after_statement:INTERNAL=1 //Test C_FLAG_Wdisabled_optimization C_FLAG_Wdisabled_optimization:INTERNAL=1 //Test C_FLAG_Wformat_security C_FLAG_Wformat_security:INTERNAL=1 //Test C_FLAG_Winline C_FLAG_Winline:INTERNAL=1 //Test C_FLAG_Wno_unknown_pragmas C_FLAG_Wno_unknown_pragmas:INTERNAL=1 //Test C_FLAG_Wpointer_arith C_FLAG_Wpointer_arith:INTERNAL=1 //Test C_FLAG_fstrict_aliasing C_FLAG_fstrict_aliasing:INTERNAL=1 //Test C_HAS_inline C_HAS_inline:INTERNAL=1 //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/fabidi89/git/ParaView/build_cmake/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: ExternalData_URL_TEMPLATES ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1 //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v1.8.3.1()] //Details about finding MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so][/opt/apps/gcc5_2/mpich/3.1.4/include][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpicxx.so;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so][/opt/apps/gcc5_2/mpich/3.1.4/include][v()] //Details about finding MPI_Fortran FIND_PACKAGE_MESSAGE_DETAILS_MPI_Fortran:INTERNAL=[/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpifort.so;/opt/apps/gcc5_2/mpich/3.1.4/lib/libmpi.so][/opt/apps/gcc5_2/mpich/3.1.4/include;/opt/apps/gcc5_2/mpich/3.1.4/include][v()] //Details about finding OpenGL FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/usr/lib64/libGL.so][/usr/include][v()] //Details about finding PythonInterp FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/opt/apps/gcc5_2/python/2.7.10/bin/python2][v2.7.10()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/opt/apps/gcc5_2/python/2.7.10/lib/libpython2.7.so][/opt/apps/gcc5_2/python/2.7.10/include/python2.7][v()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/opt/apps/gcc5_2/qt/4.8.4/bin/qmake][/opt/apps/gcc5_2/qt/4.8.4/bin/moc][/opt/apps/gcc5_2/qt/4.8.4/bin/rcc][/opt/apps/gcc5_2/qt/4.8.4/include][/opt/apps/gcc5_2/qt/4.8.4/lib][/opt/apps/gcc5_2/qt/4.8.4/include/QtGui][/opt/apps/gcc5_2/qt/4.8.4/lib/libQtGui.so][/opt/apps/gcc5_2/qt/4.8.4/bin/uic][v4.8.4(4.7)] //Details about finding Threads FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()] //Details about finding X11 FIND_PACKAGE_MESSAGE_DETAILS_X11:INTERNAL=[/usr/lib64/libX11.so][/usr/include] //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 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;ansidecl.h HAVE_ANSIDECL_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;ansidecl.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;ansidecl.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;ansidecl.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;ansidecl.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;ansidecl.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;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h HAVE_FLOAT_H:INTERNAL=1 //Have function floor HAVE_FLOOR:INTERNAL=1 //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;ansidecl.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 //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 //ADVANCED property for variable: HAVE_IEEEFP HAVE_IEEEFP-ADVANCED: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;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;ieeefp.h HAVE_IEEEFP_H:INTERNAL= //Have include inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have include io.h HAVE_IO_H:INTERNAL= //Have function isascii HAVE_ISASCII:INTERNAL=1 //Have function jbg_newlen HAVE_JBG_NEWLEN:INTERNAL= //Test HAVE_LD_VERSION_SCRIPT HAVE_LD_VERSION_SCRIPT:INTERNAL=1 //Have function lfind HAVE_LFIND: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;ansidecl.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;ansidecl.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;ansidecl.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=1 //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;ansidecl.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;ansidecl.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 function setmode HAVE_SETMODE:INTERNAL= //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_SIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_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_UNSIGNED_CHAR_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF__BOOL:INTERNAL=TRUE //Test HAVE_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=1 //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;ansidecl.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 ;stdio.h HAVE_STDIO_H:INTERNAL=1 //Have include 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 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 strtol HAVE_STRTOUL:INTERNAL=1 //Have function strtoull HAVE_STRTOULL: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;ansidecl.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 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;ansidecl.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 //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 //Result of TRY_COMPILE HAVE_bigendian:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_int16:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int32:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int8:INTERNAL=FALSE //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 //Have symbol H5_HAVE_PARALLEL HDF5_IS_PARALLEL:INTERNAL= //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 //ADVANCED property for variable: HOST_BIG_ENDIAN HOST_BIG_ENDIAN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HOST_FILLORDER HOST_FILLORDER-ADVANCED:INTERNAL=1 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 //This is set from VTK_MPIRUN_EXE. ICET_MPIRUN_EXE:INTERNAL=/opt/apps/gcc5_2/mpich/3.1.4/bin/mpiexec //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=2 //This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and // VTK_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np //This is set from VTK_MPI_POSTFLAGS. ICET_MPI_POSTFLAGS:INTERNAL= //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=OFF //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_EXT_STDIO_FILEBUF_H_COMPILED:INTERNAL=TRUE //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/fabidi89/git/ParaView/build_cmake/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 //ADVANCED property for variable: MPI_Fortran_COMPILER MPI_Fortran_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_COMPILE_FLAGS MPI_Fortran_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_INCLUDE_PATH MPI_Fortran_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LIBRARIES MPI_Fortran_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LINK_FLAGS MPI_Fortran_LINK_FLAGS-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: M_LIBRARY M_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 //Request building Pygments Module_Pygments:INTERNAL=OFF //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 //Request building pqApplicationComponents Module_pqApplicationComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqComponents Module_pqComponents-ADVANCED:INTERNAL=1 //Request building pqComponents Module_pqComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqCore Module_pqCore-ADVANCED:INTERNAL=1 //Request building pqCore Module_pqCore:INTERNAL=OFF //ADVANCED property for variable: Module_pqDeprecated Module_pqDeprecated-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqPython Module_pqPython-ADVANCED:INTERNAL=1 //Request building pqPython Module_pqPython:INTERNAL=OFF //ADVANCED property for variable: Module_pqWidgets Module_pqWidgets-ADVANCED:INTERNAL=1 //Request building pqWidgets Module_pqWidgets:INTERNAL=OFF //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 //Request building vtkGUISupportQt Module_vtkGUISupportQt:INTERNAL=OFF //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_vtkIOTRUCHAS Module_vtkIOTRUCHAS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOTecplotTable Module_vtkIOTecplotTable-ADVANCED:INTERNAL=1 //Request building vtkIOTecplotTable Module_vtkIOTecplotTable:INTERNAL=OFF //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 //Request building vtkImagingMath Module_vtkImagingMath:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingMorphological Module_vtkImagingMorphological-ADVANCED:INTERNAL=1 //Request building vtkImagingMorphological Module_vtkImagingMorphological:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingOpenGL2 Module_vtkImagingOpenGL2-ADVANCED:INTERNAL=1 //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_vtkParaViewWebCore Module_vtkParaViewWebCore-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebCore Module_vtkParaViewWebCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebPython Module_vtkParaViewWebPython-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebPython Module_vtkParaViewWebPython: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 //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_vtkRenderingOculus Module_vtkRenderingOculus-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_vtkRenderingOpenVR Module_vtkRenderingOpenVR-ADVANCED:INTERNAL=1 //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 //Request building vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON:INTERNAL=OFF //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_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_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 //Request building vtkglew Module_vtkglew:INTERNAL=OFF //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 //Request building vtkqttesting Module_vtkqttesting:INTERNAL=OFF //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: OPENGL_INCLUDE_DIR OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_gl_LIBRARY OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_glu_LIBRARY OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_xmesa_INCLUDE_DIR OPENGL_xmesa_INCLUDE_DIR-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_CatalystScriptGeneratorPlugin PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin-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_SLACTools PARAVIEW_AUTOLOAD_PLUGIN_SLACTools-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_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_CatalystScriptGeneratorPlugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin-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_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_PythonQtPlugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-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_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_TemporalParallelismScriptGenerator PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-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_VRPlugin PARAVIEW_BUILD_PLUGIN_VRPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1 //List of modules to CS wrap PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkCommonColor;vtkFiltersGeometry;vtkRenderingCore;vtkInteractionStyle;vtkIOImage;vtkRenderingOpenGL2;vtkFiltersModeling;vtkIOCore;vtkIOLegacy;vtkParallelCore;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkPVVTKExtensionsCore;vtkParallelMPI;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkIOXML;vtkInfovisCore;vtkIOInfovis;vtkDomainsChemistry;vtkFiltersAMR;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkFiltersFlowPaths;vtkFiltersParallelFlowPaths;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkIOMPIImage;vtkIOPLY;vtkIOGeometry;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingColor;vtkImagingGeneral;vtkImagingHybrid;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkFiltersGeneric;vtkFiltersHyperTree;vtkFiltersParallelMPI;vtkRenderingGL2PSOpenGL2;vtkIOExport;vtkIOExportOpenGL2;vtkRenderingMatplotlib;vtkRenderingParallel;vtkImagingMath;vtkRenderingVolumeOpenGL2;vtkRenderingVolumeAMR;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingLabel;vtkViewsCore;vtkViewsContext2D;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkDomainsChemistryOpenGL2;vtkFiltersParallelDIY2;vtkFiltersParallelGeometry;vtkFiltersImaging;vtkFiltersParallelImaging;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOMPIParallel;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOTecplotTable;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkFiltersPoints;vtkPVVTKExtensionsPoints;vtkParallelMPI4Py;vtkRenderingLICOpenGL2;vtkRenderingLOD;vtkRenderingParallelLIC;vtkPVServerManagerApplication;vtkPVCatalyst;vtkWebGLExporter;vtkWebCore;vtkParaViewWebCore;vtkRenderingContextOpenGL2 //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_EMBEDDED_DOCUMENTATION PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION-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_MODULE_ROOTS PARAVIEW_EXTERNAL_MODULE_ROOTS-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 //STRINGS property for variable: PARAVIEW_QT_VERSION PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5 //Server Manager XMLs PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/Default/settings.xml;/home/fabidi89/git/ParaView/ParaViewCore/Animation/animation.xml;/home/fabidi89/git/ParaView/ParaViewCore/VTKExtensions/Points/points.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/proxies_mpi.xml;/home/fabidi89/git/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/proxies_opengl2.xml;/home/fabidi89/git/ParaView/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_QTHELP PARAVIEW_USE_QTHELP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_QTWEBKIT PARAVIEW_USE_QTWEBKIT-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 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_BINARY_DIR:INTERNAL=/opt/apps/gcc5_2/qt/4.8.4/bin //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DESIGNER_EXECUTABLE QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DOC_DIR QT_DOC_DIR-ADVANCED:INTERNAL=1 QT_HEADERS_DIR:INTERNAL=/opt/apps/gcc5_2/qt/4.8.4/include //ADVANCED property for variable: QT_HELP_GENERATOR QT_HELP_GENERATOR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_IMPORTS_DIR QT_IMPORTS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LIBRARY_DIR QT_LIBRARY_DIR-ADVANCED:INTERNAL=1 //Qt library dir QT_LIBRARY_DIR:INTERNAL=/opt/apps/gcc5_2/qt/4.8.4/lib //ADVANCED property for variable: QT_LINGUIST_EXECUTABLE QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LRELEASE_EXECUTABLE QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LUPDATE_EXECUTABLE QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MKSPECS_DIR QT_MKSPECS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MOC_EXECUTABLE QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_INCLUDE_DIR QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PLUGINS_DIR QT_PLUGINS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMAKE_EXECUTABLE QT_QMAKE_EXECUTABLE-ADVANCED:INTERNAL=1 QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/opt/apps/gcc5_2/qt/4.8.4/bin/qmake //ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_INCLUDE_DIR QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_DEBUG QT_QTMOTIF_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_RELEASE QT_QTMOTIF_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_INCLUDE_DIR QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_RCC_EXECUTABLE QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TESTING_EVENT_PLAYBACK_DELAY QT_TESTING_EVENT_PLAYBACK_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TRANSLATIONS_DIR QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC3_EXECUTABLE QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC_EXECUTABLE QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_XMLPATTERNS_EXECUTABLE QT_XMLPATTERNS_EXECUTABLE-ADVANCED:INTERNAL=1 //Have symbol Q_WS_MAC Q_WS_MAC:INTERNAL= //Have symbol Q_WS_QWS Q_WS_QWS:INTERNAL= //Have symbol Q_WS_WIN Q_WS_WIN:INTERNAL= //Have symbol Q_WS_X11 Q_WS_X11: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(signed int) SIZEOF_SIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(signed long) SIZEOF_SIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed long long) SIZEOF_SIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed short) SIZEOF_SIGNED_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(unsigned char *) SIZEOF_UNSIGNED_CHAR_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned int) SIZEOF_UNSIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(unsigned long) SIZEOF_UNSIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned long long) SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned short) SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void *) SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(_Bool) SIZEOF__BOOL: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 //Test TM_IN_SYS_TIME TM_IN_SYS_TIME:INTERNAL=1 //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/fabidi89/git/ParaView/build_cmake/VTK/Utilities/ftgl VTKFTGL_SOURCE_DIR:INTERNAL=/home/fabidi89/git/ParaView/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/fabidi89/git/ParaView/build_cmake/lib/site-packages //ADVANCED property for variable: VTK_BUILD_QT_DESIGNER_PLUGIN VTK_BUILD_QT_DESIGNER_PLUGIN-ADVANCED:INTERNAL=1 //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_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 //Directory where python modules will be installed VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-5.2/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_MPIRUN_EXE VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_POSTFLAGS VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PREFLAGS VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS VTK_MPI_PRENUMPROC_FLAGS-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 //STRINGS property for variable: VTK_QT_VERSION VTK_QT_VERSION-STRINGS:INTERNAL=4;5 VTK_QT_VERSION:INTERNAL=4 //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_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_PYGMENTS VTK_USE_SYSTEM_PYGMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_QTTESTING VTK_USE_SYSTEM_QTTESTING-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_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_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: X11_ICE_INCLUDE_PATH X11_ICE_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_ICE_LIB X11_ICE_LIB-ADVANCED:INTERNAL=1 //Have library /usr/lib64/libX11.so;/usr/lib64/libXext.so X11_LIB_X11_SOLO:INTERNAL=1 //ADVANCED property for variable: X11_SM_INCLUDE_PATH X11_SM_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_SM_LIB X11_SM_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_X11_INCLUDE_PATH X11_X11_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_X11_LIB X11_X11_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XRes_INCLUDE_PATH X11_XRes_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XRes_LIB X11_XRes_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XShm_INCLUDE_PATH X11_XShm_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XSync_INCLUDE_PATH X11_XSync_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XTest_INCLUDE_PATH X11_XTest_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XTest_LIB X11_XTest_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xaccessrules_INCLUDE_PATH X11_Xaccessrules_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xaccessstr_INCLUDE_PATH X11_Xaccessstr_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xau_INCLUDE_PATH X11_Xau_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xau_LIB X11_Xau_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcomposite_INCLUDE_PATH X11_Xcomposite_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcomposite_LIB X11_Xcomposite_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcursor_INCLUDE_PATH X11_Xcursor_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcursor_LIB X11_Xcursor_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdamage_INCLUDE_PATH X11_Xdamage_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdamage_LIB X11_Xdamage_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdmcp_INCLUDE_PATH X11_Xdmcp_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdmcp_LIB X11_Xdmcp_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xext_LIB X11_Xext_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xfixes_INCLUDE_PATH X11_Xfixes_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xfixes_LIB X11_Xfixes_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xft_INCLUDE_PATH X11_Xft_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xft_LIB X11_Xft_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xi_INCLUDE_PATH X11_Xi_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xi_LIB X11_Xi_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinerama_INCLUDE_PATH X11_Xinerama_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinerama_LIB X11_Xinerama_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinput_INCLUDE_PATH X11_Xinput_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinput_LIB X11_Xinput_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkb_INCLUDE_PATH X11_Xkb_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkbfile_INCLUDE_PATH X11_Xkbfile_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkbfile_LIB X11_Xkbfile_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkblib_INCLUDE_PATH X11_Xkblib_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xlib_INCLUDE_PATH X11_Xlib_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xmu_INCLUDE_PATH X11_Xmu_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xmu_LIB X11_Xmu_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xpm_INCLUDE_PATH X11_Xpm_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xpm_LIB X11_Xpm_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrandr_INCLUDE_PATH X11_Xrandr_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrandr_LIB X11_Xrandr_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrender_INCLUDE_PATH X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrender_LIB X11_Xrender_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xscreensaver_LIB X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xshape_INCLUDE_PATH X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xt_INCLUDE_PATH X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xt_LIB X11_Xt_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xutil_INCLUDE_PATH X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xv_INCLUDE_PATH X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xv_LIB X11_Xv_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xxf86misc_LIB X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xxf86vm_LIB X11_Xxf86vm_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_dpms_INCLUDE_PATH X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH X11_xf86vmode_INCLUDE_PATH-ADVANCED: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 //CMAKE_INSTALL_PREFIX during last run _GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/home/fabidi89/Paraview-v5.2.0 //ParaView has been configured __paraview_configured:INTERNAL=TRUE //Result of TEST_BIG_ENDIAN bigendian:INTERNAL=0 //CHECK_TYPE_SIZE: INT16 unknown int16:INTERNAL= //CHECK_TYPE_SIZE: INT32 unknown int32:INTERNAL= //CHECK_TYPE_SIZE: INT8 unknown int8:INTERNAL= protobut_determine_hash_namespace_done:INTERNAL=TRUE protobut_pthread_test_done:INTERNAL=TRUE pthread_test_result:INTERNAL=PTHREAD_CREATE_JOINABLE From wascott at sandia.gov Tue Feb 14 18:39:17 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 14 Feb 2017 23:39:17 +0000 Subject: [Paraview] volume vs volume Message-ID: <7ea42c6671824fbfa021461b4437cd59@ES01AMSNLNT.srn.sandia.gov> Hi all, I was trying to find volume for a user, and started wondering if the user wanted volume of the dataset, or volume of each cell. Turns out that there is incorrect information on the list. I believe the following is true: Volume of the dataset: Python Calculator. Expression: volume(inputs[0]). Array Name: totalVolume. Apply. Volume of each cell: Programmable Filter. Script, then Apply: from vtk.numpy_interface import algorithms as algs volume = algs.volume(inputs[0]) output.CellData.append(volume, 'volumeOfEachCell') Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Feb 14 19:09:33 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Feb 2017 19:09:33 -0500 Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 In-Reply-To: References: <181475582.1543787.1487100772876.JavaMail.zimbra@lncmi.cnrs.fr> Message-ID: Set the xmlpatterns executable, if you have it. I am sure that's what's messing the build up. On Tue, Feb 14, 2017 at 6:01 PM, Faiz Abidi wrote: > Utkarsh - I think I am missing /usr/lib64/qt4/bin/xmlpatterns but that's > just a warning. Attached is the CMakeCache file. > > Christophe - That didn't work for me. But thanks for suggesting. > > On Tue, Feb 14, 2017 at 2:32 PM, Christophe Trophime > wrote: >> >> I had a similar problem on debian >> >> export QT_SELECT=qt5 or qt4 >> >> before running cmake fix the problem >> >> >> >> Christophe TROPHIME >> Research Engineer >> >> CNRS - LNCMI >> 25, rue des Martyrs >> BP 166 >> 38042 GRENOBLE Cedex 9 >> FRANCE >> >> Tel : +33 (0)4 76 88 90 02 >> Fax : +33 (0) 4 76 88 10 01 >> Office U 19 >> M at il : christophe.trophime at lncmi.cnrs.fr >> >> ----- Original Message ----- >> > From: "Utkarsh Ayachit" >> > To: "Faiz Abidi" >> > Cc: "ParaView" >> > Sent: Tuesday, February 14, 2017 8:16:20 PM >> > Subject: Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0 >> > >> > Can you post your CMakeCache.txt? I suspect one of the Qt help >> > generation tools was not found/set correctly. >> > >> > Utkarsh >> > >> > On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: >> > > Hello community, >> > > >> > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? >> > > When I >> > > install Paraview from source, I get the below error. >> > > >> > > "/bin/sh: line 0: cd: >> > > /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/SurfaceLIC/doc: >> > > No >> > > such file or directory >> > > make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 >> > > make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] Error >> > > 2" >> > > >> > > I am not sure if I am missing a dependency. The install works fine >> > > without >> > > this plugin. >> > > >> > > Anyone seen this before? >> > > -- >> > > 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 >> > > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView 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 From fabidi89 at vt.edu Tue Feb 14 19:11:25 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 14 Feb 2017 19:11:25 -0500 Subject: [Paraview] Installing paraviewweb on a raspberry pi In-Reply-To: <20170214165505.Horde.xePVRwV6yG_9EBOJAkUU92V@feacluster.com> References: <20170208101536.Horde.H4MZinqQxEJcLjGOorO6eDl@feacluster.com> <20170210162521.Horde.JbrLF9lqXabNc3JY0h3rFS2@feacluster.com> <20170214165505.Horde.xePVRwV6yG_9EBOJAkUU92V@feacluster.com> Message-ID: Hi Faraz, I can look into your system if you can provide me ssh access. I don't promise to fix your issue but have experience with Raspberry Pis and Paraview builds. And I don't need money, I'll do it out of curiosity and in free time :) On Tue, Feb 14, 2017 at 4:55 PM, Faraz Hussain wrote: > Unfortunately, I am not having much luck getting Paraview to build. I keep > trying to configure (c), but the generate (g) option does not come. I am > wondering if someone would be willing to poke around in my system . I can > pay some nominal amount for your time. However , since this is mainly for > education my budget is limited ( ~$100 ). > > > Quoting Sebastien Jourdain : > > You need to hit [c](configure) several time before getting the generate. >> >> On Fri, Feb 10, 2017 at 2:33 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >> Also for paraviewweb, don't forget: >>> >>> PARAVIEW_ENABLE_PYTHON=ON >>> >>> Cheers, >>> >>> Scott >>> >>> On Fri, Feb 10, 2017 at 2:31 PM, Scott Wittenburg < >>> scott.wittenburg at kitware.com> wrote: >>> >>> I would think you'd want to build with: >>>> >>>> PARAVIEW_BUILD_QT_GUI=OFF >>>> >>>> Hope this helps, >>>> >>>> Scott >>>> >>>> On Fri, Feb 10, 2017 at 2:25 PM, Faraz Hussain >>>> wrote: >>>> >>>> Thanks for your help in installing Paraview on a raspberry pi. I >>>>> followed the steps in: >>>>> >>>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install >>>>> >>>>> However, when I configure ccmake it says QT is needed. I could not >>>>> figure out if I can ignore that. The "generate" command did not come >>>>> up. >>>>> >>>>> On a side note, it took me a while to find ccmake. I thought it was >>>>> installed with cmake, but seems I had to install it separately using >>>>> "sudo >>>>> apt-get install cmake-curses-gui" . Perhaps the instructions should be >>>>> updated to reflect this to avoid confusion. >>>>> >>>>> >>>>> Quoting Sebastien Jourdain : >>>>> >>>>> Wow, >>>>> >>>>>> >>>>>> I'm not an expert on raspberry pi but it should be possible. >>>>>> BUT, (and it is a big but) you need some graphics capability for >>>>>> ParaView >>>>>> or good CPUs if you don't have a GPU. >>>>>> Or the rendering will be really slow. >>>>>> >>>>>> The quicker test you can do, is to build ParaView (without Qt) and try >>>>>> to >>>>>> run Visualizer with that ParaView in the command line to see what >>>>>> performance you are getting. If that's reasonable, then all the >>>>>> network >>>>>> setup should be "trivial". >>>>>> >>>>>> ParaView: http://www.paraview.org/Wiki/ParaView:Build_And_Install >>>>>> Visualizer: https://kitware.github.io/visualizer/ >>>>>> >>>>>> Good luck, >>>>>> >>>>>> Seb >>>>>> >>>>>> On Wed, Feb 8, 2017 at 8:15 AM, Faraz Hussain >>>>>> wrote: >>>>>> >>>>>> I want to be able to manipulate vtk file on my raspberry pi via a web >>>>>> >>>>>>> browser anywhere in the world. I believe I need to install >>>>>>> paraviewweb >>>>>>> and >>>>>>> do some reconfiguration of apache and the virtual hosts? >>>>>>> Unfortunately, I >>>>>>> am not a guru of Linux. So before I attempt it all, is it even >>>>>>> possible to >>>>>>> do this on a raspberry pi? I am using raspian . >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> >>>> >>>> >>> > > > _______________________________________________ > 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 > -- 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 Tue Feb 14 19:15:30 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Tue, 14 Feb 2017 19:15:30 -0500 Subject: [Paraview] SurfaceLIC issues with Paraview 5.2.0 In-Reply-To: References: <181475582.1543787.1487100772876.JavaMail.zimbra@lncmi.cnrs.fr> Message-ID: Yeah, I think so too, but the admins who have installed Qt on the HPC clusters here didn't build the xmlpatterns binary. Hence, I don't have it on my system. It is a bit weird though that this should mess with SurfaceLIC plugin unless I misread the Qt docs. I think for now I'll skip this plugin and install Paraview. On Tue, Feb 14, 2017 at 7:09 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Set the xmlpatterns executable, if you have it. I am sure that's > what's messing the build up. > > On Tue, Feb 14, 2017 at 6:01 PM, Faiz Abidi wrote: > > Utkarsh - I think I am missing /usr/lib64/qt4/bin/xmlpatterns but that's > > just a warning. Attached is the CMakeCache file. > > > > Christophe - That didn't work for me. But thanks for suggesting. > > > > On Tue, Feb 14, 2017 at 2:32 PM, Christophe Trophime > > wrote: > >> > >> I had a similar problem on debian > >> > >> export QT_SELECT=qt5 or qt4 > >> > >> before running cmake fix the problem > >> > >> > >> > >> Christophe TROPHIME > >> Research Engineer > >> > >> CNRS - LNCMI > >> 25, rue des Martyrs > >> BP 166 > >> 38042 GRENOBLE Cedex 9 > >> FRANCE > >> > >> Tel : +33 (0)4 76 88 90 02 > >> Fax : +33 (0) 4 76 88 10 01 > >> Office U 19 > >> M at il : christophe.trophime at lncmi.cnrs.fr > >> > >> ----- Original Message ----- > >> > From: "Utkarsh Ayachit" > >> > To: "Faiz Abidi" > >> > Cc: "ParaView" > >> > Sent: Tuesday, February 14, 2017 8:16:20 PM > >> > Subject: Re: [Paraview] SurfaceLIC issues with Paraview 5.2.0 > >> > > >> > Can you post your CMakeCache.txt? I suspect one of the Qt help > >> > generation tools was not found/set correctly. > >> > > >> > Utkarsh > >> > > >> > On Tue, Feb 14, 2017 at 12:46 PM, Faiz Abidi wrote: > >> > > Hello community, > >> > > > >> > > Anyone faced issues with Paraview 5.2.0 and the SurfaceLIC plugin? > >> > > When I > >> > > install Paraview from source, I get the below error. > >> > > > >> > > "/bin/sh: line 0: cd: > >> > > /home/fabidi89/git/ParaView/build_usingCCMake/Plugins/ > SurfaceLIC/doc: > >> > > No > >> > > such file or directory > >> > > make[2]: *** [Plugins/SurfaceLIC/doc/SurfaceLIC.qch] Error 1 > >> > > make[1]: *** [Plugins/SurfaceLIC/CMakeFiles/SurfaceLIC.dir/all] > Error > >> > > 2" > >> > > > >> > > I am not sure if I am missing a dependency. The install works fine > >> > > without > >> > > this plugin. > >> > > > >> > > Anyone seen this before? > >> > > -- > >> > > 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 > >> > > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView 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 > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukas.kresta at gmail.com Wed Feb 15 03:49:27 2017 From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=) Date: Wed, 15 Feb 2017 09:49:27 +0100 Subject: [Paraview] One render view on Paraview Catalyst Message-ID: I generated python script for Catalyst from Paraview. When I run my code with MPI, I get render window for every MPI process. But i want to have only one window for all MPI processes. I already tried have script for view only on root and on another only script for live visualization (without view), but I still get view for every MPI process. Have someone some idea how to "fix" my problem? -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume.jacquenot at gmail.com Wed Feb 15 06:17:05 2017 From: guillaume.jacquenot at gmail.com (Guillaume Jacquenot) Date: Wed, 15 Feb 2017 12:17:05 +0100 Subject: [Paraview] Problem testing PV 5.3.0 RC1 Message-ID: Hello, I am testing ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit. I run into a problem when using PV with a script. When I launch a simple script with the command D:\ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin\paraview.exe --script=testSphere.py I have the following error message in the console, and nothing happens Cannot open data file " \paraview.exe " (:0, ) Below is testSphere.py from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() sphere1 = Sphere() renderView1 = GetActiveViewOrCreate('RenderView') sphere1Display = Show(sphere1, renderView1) renderView1.ResetCamera() My initial goal was to check that the following code works with PV5.3. For version PV 5.2 it failed, whereas previously it succeeded import os import tempfile import numpy as np outputFilename = os.path.join(tempfile.mkdtemp(), 'dummy.npz') varName='Time' np.savez(outputFilename, **{varName:np.random.rand(3,4)}) d = np.load(outputFilename) time = d[varName] d.close() os.remove(outputFilename) print('Success PV can create a NPZ file and read its content : ' + outputFilename) I had reported this bug, http://public.kitware.com/pipermail/paraview/2017-January/038890.html and a bug issue had been opened: https://gitlab.kitware.com/paraview/paraview-superbuild/issues/43 Guillaume Jacquenot -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdutta at vt.edu Wed Feb 15 07:26:18 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Wed, 15 Feb 2017 07:26:18 -0500 Subject: [Paraview] paraview compilation issue Message-ID: Hi All, I configured paraview to compile for CPU rendering with the below option on ubuntu 14.04 and Python 2.7.6: 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 Now I am getting the below compilation error: ----------------------------LOGs------------------------------------- #make ................ ............... CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function `PyVTKTemplate_Keys(_object*, _object*)': PyVTKTemplate.cxx:(.text+0x1511): undefined reference to `PyArg_ParseTuple' PyVTKTemplate.cxx:(.text+0x1527): undefined reference to `PyModule_GetDict' PyVTKTemplate.cxx:(.text+0x1534): undefined reference to `PyList_New' PyVTKTemplate.cxx:(.text+0x156c): undefined reference to `PyDict_Next' PyVTKTemplate.cxx:(.text+0x1597): undefined reference to `PyList_Append' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function `PyVTKTemplate_Size(_object*)': PyVTKTemplate.cxx:(.text+0x15c5): undefined reference to `PyModule_GetDict' PyVTKTemplate.cxx:(.text+0x160c): undefined reference to `PyDict_Next' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function `PyVTKTemplate_New': PyVTKTemplate.cxx:(.text+0x1679): undefined reference to `PyType_Ready' PyVTKTemplate.cxx:(.text+0x1691): undefined reference to `PyTuple_New' PyVTKTemplate.cxx:(.text+0x169c): undefined reference to `PyString_FromString' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function `PyVTKTemplate_AddItem': PyVTKTemplate.cxx:(.text+0x172c): undefined reference to `PyModule_GetDict' PyVTKTemplate.cxx:(.text+0x173a): undefined reference to `PyDict_SetItemString' PyVTKTemplate.cxx:(.text+0x174a): undefined reference to `PyExc_TypeError' PyVTKTemplate.cxx:(.text+0x1759): undefined reference to `PyErr_SetString' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function `PyVTKTemplate_Repr(_object*)': PyVTKTemplate.cxx:(.text+0x4a): undefined reference to `PyString_FromFormat' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x8): undefined reference to `PyType_Type' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x90): undefined reference to `PyObject_GenericGetAttr' CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x100): undefined reference to `PyModule_Type' CMakeFiles/vtkWrappingPythonCore.dir/vtkSmartPyObject.cxx.o: In function `vtkSmartPyObject::~vtkSmartPyObject()': vtkSmartPyObject.cxx:(.text+0x35): undefined reference to `Py_IsInitialized' collect2: error: ld returned 1 exit status make[2]: *** [lib/libvtkWrappingPython27Core-pv5.0.so.1] Error 1 make[1]: *** [VTK/Wrapping/PythonCore/CMakeFiles/vtkWrappingPythonCore.dir/all] Error 2 make: *** [all] Error 2 -------------------------------------------------------------------------- I have set the python lib and include paths. And also took care to do "apt-get install python-dev". Thank you in advance for help as I am new and running out of ideas. Also do the configuration options look ok for CPU based rendering? BR, Bishwajit -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Wed Feb 15 07:56:12 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 15 Feb 2017 12:56:12 +0000 Subject: [Paraview] volume vs volume Message-ID: Alan, A quick and dirty way to get individual element volumes is to use the mesh refinement filter and set the Quality measure to volume. Then the "Quality" variable in the elements is actually volume. Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Feb 15 08:26:31 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Feb 2017 08:26:31 -0500 Subject: [Paraview] paraview compilation issue In-Reply-To: References: Message-ID: Can you attach your CMakeCache.txt please? Thanks Utkarsh On Wed, Feb 15, 2017 at 7:26 AM, Bishwajit Dutta wrote: > Hi All, > > I configured paraview to compile for CPU rendering with the below option > on ubuntu 14.04 and Python 2.7.6: > > 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 > > Now I am getting the below compilation error: > > ----------------------------LOGs------------------------------------- > #make > ................ > ............... > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function > `PyVTKTemplate_Keys(_object*, _object*)': > PyVTKTemplate.cxx:(.text+0x1511): undefined reference to > `PyArg_ParseTuple' > PyVTKTemplate.cxx:(.text+0x1527): undefined reference to > `PyModule_GetDict' > PyVTKTemplate.cxx:(.text+0x1534): undefined reference to `PyList_New' > PyVTKTemplate.cxx:(.text+0x156c): undefined reference to `PyDict_Next' > PyVTKTemplate.cxx:(.text+0x1597): undefined reference to `PyList_Append' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function > `PyVTKTemplate_Size(_object*)': > PyVTKTemplate.cxx:(.text+0x15c5): undefined reference to > `PyModule_GetDict' > PyVTKTemplate.cxx:(.text+0x160c): undefined reference to `PyDict_Next' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function > `PyVTKTemplate_New': > PyVTKTemplate.cxx:(.text+0x1679): undefined reference to `PyType_Ready' > PyVTKTemplate.cxx:(.text+0x1691): undefined reference to `PyTuple_New' > PyVTKTemplate.cxx:(.text+0x169c): undefined reference to > `PyString_FromString' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function > `PyVTKTemplate_AddItem': > PyVTKTemplate.cxx:(.text+0x172c): undefined reference to > `PyModule_GetDict' > PyVTKTemplate.cxx:(.text+0x173a): undefined reference to > `PyDict_SetItemString' > PyVTKTemplate.cxx:(.text+0x174a): undefined reference to `PyExc_TypeError' > PyVTKTemplate.cxx:(.text+0x1759): undefined reference to `PyErr_SetString' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function > `PyVTKTemplate_Repr(_object*)': > PyVTKTemplate.cxx:(.text+0x4a): undefined reference to > `PyString_FromFormat' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x8): > undefined reference to `PyType_Type' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x90): > undefined reference to `PyObject_GenericGetAttr' > CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x100): > undefined reference to `PyModule_Type' > CMakeFiles/vtkWrappingPythonCore.dir/vtkSmartPyObject.cxx.o: In function > `vtkSmartPyObject::~vtkSmartPyObject()': > vtkSmartPyObject.cxx:(.text+0x35): undefined reference to > `Py_IsInitialized' > collect2: error: ld returned 1 exit status > make[2]: *** [lib/libvtkWrappingPython27Core-pv5.0.so.1] Error 1 > make[1]: *** [VTK/Wrapping/PythonCore/CMakeFiles/vtkWrappingPythonCore.dir/all] > Error 2 > make: *** [all] Error 2 > > -------------------------------------------------------------------------- > > I have set the python lib and include paths. And also took care to do > "apt-get install python-dev". > > Thank you in advance for help as I am new and running out of ideas. > > Also do the configuration options look ok for CPU based rendering? > > BR, > Bishwajit > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 richard.c.angelini.civ at mail.mil Wed Feb 15 08:50:13 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Wed, 15 Feb 2017 13:50:13 +0000 Subject: [Paraview] Superbuild repo change? In-Reply-To: References: Message-ID: I did a fresh pull of the ParaView superbuild repository, and now I can?t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). First, I had to remove the entries for ?qt? and ?scipy" in the CMakeLists.txt: -- Determined source version for paraview: 5.2.0 CMake Error at superbuild/CMakeLists.txt:112 (include): include could not find load file: qt CMake Error at superbuild/CMakeLists.txt:112 (include): include could not find load file: scipy After removing those entries, the cmake completes and the build starts and passes out in qt4. I?m not sure why it?s complaining about OS X 10.7 or later?) [ 19%] Built target boost [ 24%] Built target visitbridge [ 27%] Built target libxml2 [ 29%] Performing build step for 'qt4' clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) make[4]: *** [.obj/release-static/qsimplecodec.o] Error 1 make[4]: *** Waiting for unfinished jobs.... make[4]: *** [.obj/release-static/qlatincodec.o] Error 1 make[4]: *** [.obj/release-static/qisciicodec.o] Error 1 clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) make[4]: *** [.obj/release-static/qtextcodec.o] Error 1 clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) make[4]: *** [.obj/release-static/qtsciicodec.o] Error 1 clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) make[4]: *** [.obj/release-static/qutfcodec.o] Error 1 clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) make[4]: *** [.obj/release-static/qmalloc.o] Error 1 make[4]: *** [.obj/release-static/qglobal.o] Error 1 make[3]: *** [sub-tools-bootstrap-make_default-ordered] Error 2 CMake Error at /Users/angel/PV/Build/superbuild/sb-qt4-build.cmake:43 (message): Failed with exit code 2 make[2]: *** [superbuild/qt4/stamp/qt4-build] Error 1 make[1]: *** [superbuild/CMakeFiles/qt4.dir/all] Error 2 make: *** [all] Error 2 ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From dennis_conklin at goodyear.com Wed Feb 15 09:07:58 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 15 Feb 2017 14:07:58 +0000 Subject: [Paraview] volume vs volume Message-ID: Oops - meant Mesh Quality filter From: Dennis Conklin Sent: Wednesday, February 15, 2017 7:56 AM To: Paraview (paraview at paraview.org) Subject: Re: [Paraview] volume vs volume Alan, A quick and dirty way to get individual element volumes is to use the mesh refinement filter and set the Quality measure to volume. Then the "Quality" variable in the elements is actually volume. Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Wed Feb 15 09:24:29 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Wed, 15 Feb 2017 14:24:29 +0000 Subject: [Paraview] Examples of Field Variables Manipulation for Exodus Multi-block datasets Message-ID: All, I can't find a good example of manipulating Field Variables (Global Variables) in Exodus Multi-block datasets. For instance, I wrote a filter to calculate the total_volume of a mesh. Currently I print this out to the screen. I would like to add a Field variable of Total_volume but I have no idea how to do this. Does anyone have an example of how to access (read) field variables and/or how to add one. Thanks for any hints Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Feb 15 10:00:48 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 15 Feb 2017 10:00:48 -0500 Subject: [Paraview] One render view on Paraview Catalyst In-Reply-To: References: Message-ID: Hi, In the ParaView GUI you can set the Remote Render Threshold (under Edit->Settings...->Render View) to a very large number to ensure that all rendered data gets delivered to the client for rendering. In general this is a bad way to do things though since that can use a lot of bandwidth and memory. If you are trying to just have a single render view in Catalyst with a parallel run, I don't think it's possible to get just a single window. You either need to have a window for each MPI process or no windows at all. For no windows at all you will need to use either OSMesa or EGL for offscreen rendering. --Andy On Wed, Feb 15, 2017 at 3:49 AM, Luk?? Kresta wrote: > I generated python script for Catalyst from Paraview. When I run my code > with MPI, I get render window for every MPI process. But i want to have > only one window for all MPI processes. > > I already tried have script for view only on root and on another only > script for live visualization (without view), but I still get view for > every MPI process. > > Have someone some idea how to "fix" my problem? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Wed Feb 15 10:18:20 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 15 Feb 2017 10:18:20 -0500 Subject: [Paraview] volume vs volume In-Reply-To: References: Message-ID: As a side note, the Mesh Quality filter does not work on all 3D cell types. I think prisms and pyramids are not supported. On Wed, Feb 15, 2017 at 9:07 AM, Dennis Conklin wrote: > Oops ? meant Mesh Quality filter > > > > *From:* Dennis Conklin > *Sent:* Wednesday, February 15, 2017 7:56 AM > *To:* Paraview (paraview at paraview.org) > *Subject:* Re: [Paraview] volume vs volume > > > > Alan, > > > > A quick and dirty way to get individual element volumes is to use the mesh > refinement filter and set the Quality measure to volume. Then the > ?Quality? variable in the elements is actually volume. > > > > 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 ben.boeckel at kitware.com Wed Feb 15 11:34:09 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 15 Feb 2017 11:34:09 -0500 Subject: [Paraview] Superbuild repo change? In-Reply-To: References: Message-ID: <20170215163409.GA8112@megas.kitware.com> On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a fresh pull of the ParaView superbuild repository, and now I can?t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for ?qt? and ?scipy" in the > CMakeLists.txt: You need to run `git submodule update` to update the common-superbuild bits. > After removing those entries, the cmake completes and the build starts and > passes out in qt4. > I?m not sure why it?s complaining about OS X 10.7 or later?) What version of Xcode are you using? --Ben From richard.c.angelini.civ at mail.mil Wed Feb 15 11:56:27 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Wed, 15 Feb 2017 16:56:27 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <20170215163409.GA8112@megas.kitware.com> References: <20170215163409.GA8112@megas.kitware.com> Message-ID: Duh. ?git submodule update? seems to fix things related to the qt and scipy issue. My Mac has Xcode version 6.2 ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel Reply-To: "ben.boeckel at kitware.com" Date: Wednesday, February 15, 2017 at 11:34 AM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a fresh pull of the ParaView superbuild repository, and now I >can?t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for ?qt? and ?scipy" in the > CMakeLists.txt: You need to run `git submodule update` to update the common-superbuild bits. > After removing those entries, the cmake completes and the build starts >and > passes out in qt4. > I?m not sure why it?s complaining about OS X 10.7 or later?) What version of Xcode are you using? --Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From bdutta at vt.edu Wed Feb 15 14:25:41 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Wed, 15 Feb 2017 14:25:41 -0500 Subject: [Paraview] paraview compilation issue In-Reply-To: References: Message-ID: Hi Utkarsh, Pls find it attached. Thank you so much. -Bishwajit On Wed, Feb 15, 2017 at 8:26 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Can you attach your CMakeCache.txt please? > > Thanks > Utkarsh > > On Wed, Feb 15, 2017 at 7:26 AM, Bishwajit Dutta wrote: > >> Hi All, >> >> I configured paraview to compile for CPU rendering with the below option >> on ubuntu 14.04 and Python 2.7.6: >> >> 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 >> >> Now I am getting the below compilation error: >> >> ----------------------------LOGs------------------------------------- >> #make >> ................ >> ............... >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >> `PyVTKTemplate_Keys(_object*, _object*)': >> PyVTKTemplate.cxx:(.text+0x1511): undefined reference to >> `PyArg_ParseTuple' >> PyVTKTemplate.cxx:(.text+0x1527): undefined reference to >> `PyModule_GetDict' >> PyVTKTemplate.cxx:(.text+0x1534): undefined reference to `PyList_New' >> PyVTKTemplate.cxx:(.text+0x156c): undefined reference to `PyDict_Next' >> PyVTKTemplate.cxx:(.text+0x1597): undefined reference to `PyList_Append' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >> `PyVTKTemplate_Size(_object*)': >> PyVTKTemplate.cxx:(.text+0x15c5): undefined reference to >> `PyModule_GetDict' >> PyVTKTemplate.cxx:(.text+0x160c): undefined reference to `PyDict_Next' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >> `PyVTKTemplate_New': >> PyVTKTemplate.cxx:(.text+0x1679): undefined reference to `PyType_Ready' >> PyVTKTemplate.cxx:(.text+0x1691): undefined reference to `PyTuple_New' >> PyVTKTemplate.cxx:(.text+0x169c): undefined reference to >> `PyString_FromString' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >> `PyVTKTemplate_AddItem': >> PyVTKTemplate.cxx:(.text+0x172c): undefined reference to >> `PyModule_GetDict' >> PyVTKTemplate.cxx:(.text+0x173a): undefined reference to >> `PyDict_SetItemString' >> PyVTKTemplate.cxx:(.text+0x174a): undefined reference to >> `PyExc_TypeError' >> PyVTKTemplate.cxx:(.text+0x1759): undefined reference to >> `PyErr_SetString' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >> `PyVTKTemplate_Repr(_object*)': >> PyVTKTemplate.cxx:(.text+0x4a): undefined reference to >> `PyString_FromFormat' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x8): >> undefined reference to `PyType_Type' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x90): >> undefined reference to `PyObject_GenericGetAttr' >> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x100): >> undefined reference to `PyModule_Type' >> CMakeFiles/vtkWrappingPythonCore.dir/vtkSmartPyObject.cxx.o: In function >> `vtkSmartPyObject::~vtkSmartPyObject()': >> vtkSmartPyObject.cxx:(.text+0x35): undefined reference to >> `Py_IsInitialized' >> collect2: error: ld returned 1 exit status >> make[2]: *** [lib/libvtkWrappingPython27Core-pv5.0.so.1] Error 1 >> make[1]: *** [VTK/Wrapping/PythonCore/CMakeFiles/vtkWrappingPythonCore.dir/all] >> Error 2 >> make: *** [all] Error 2 >> >> ------------------------------------------------------------ >> -------------- >> >> I have set the python lib and include paths. And also took care to do >> "apt-get install python-dev". >> >> Thank you in advance for help as I am new and running out of ideas. >> >> Also do the configuration options look ok for CPU based rendering? >> >> BR, >> Bishwajit >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 -------------- # 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=FALSE //No help, variable specified on the command line. BUILD_HSI:UNINITIALIZED=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 //No help, variable specified on the command line. MPI_HEADER_PATH:UNINITIALIZED=/usr/include/mpi/ //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 //No help, variable specified on the command line. PYTHON_INCLUDE_DIRS:UNINITIALIZED=/usr/include/python2.7/ //No help, variable specified on the command line. PYTHON_LIBRARIES:UNINITIALIZED=/usr/lib/python2.7/ //Path to a library. PYTHON_LIBRARY:FILEPATH=/usr/lib/python2.7 //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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7;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/python2.7][/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 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 From utkarsh.ayachit at kitware.com Wed Feb 15 14:38:28 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Feb 2017 14:38:28 -0500 Subject: [Paraview] paraview compilation issue In-Reply-To: References: Message-ID: Your PYTHON_LIBRARY is invalid. Please make sure it points to a libpython2.7.so. On Wed, Feb 15, 2017 at 2:25 PM, Bishwajit Dutta wrote: > Hi Utkarsh, > > Pls find it attached. > > Thank you so much. > > -Bishwajit > > On Wed, Feb 15, 2017 at 8:26 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Can you attach your CMakeCache.txt please? >> >> Thanks >> Utkarsh >> >> On Wed, Feb 15, 2017 at 7:26 AM, Bishwajit Dutta wrote: >> >>> Hi All, >>> >>> I configured paraview to compile for CPU rendering with the below option >>> on ubuntu 14.04 and Python 2.7.6: >>> >>> 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 >>> >>> Now I am getting the below compilation error: >>> >>> ----------------------------LOGs------------------------------------- >>> #make >>> ................ >>> ............... >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >>> `PyVTKTemplate_Keys(_object*, _object*)': >>> PyVTKTemplate.cxx:(.text+0x1511): undefined reference to >>> `PyArg_ParseTuple' >>> PyVTKTemplate.cxx:(.text+0x1527): undefined reference to >>> `PyModule_GetDict' >>> PyVTKTemplate.cxx:(.text+0x1534): undefined reference to `PyList_New' >>> PyVTKTemplate.cxx:(.text+0x156c): undefined reference to `PyDict_Next' >>> PyVTKTemplate.cxx:(.text+0x1597): undefined reference to `PyList_Append' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >>> `PyVTKTemplate_Size(_object*)': >>> PyVTKTemplate.cxx:(.text+0x15c5): undefined reference to >>> `PyModule_GetDict' >>> PyVTKTemplate.cxx:(.text+0x160c): undefined reference to `PyDict_Next' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >>> `PyVTKTemplate_New': >>> PyVTKTemplate.cxx:(.text+0x1679): undefined reference to `PyType_Ready' >>> PyVTKTemplate.cxx:(.text+0x1691): undefined reference to `PyTuple_New' >>> PyVTKTemplate.cxx:(.text+0x169c): undefined reference to >>> `PyString_FromString' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >>> `PyVTKTemplate_AddItem': >>> PyVTKTemplate.cxx:(.text+0x172c): undefined reference to >>> `PyModule_GetDict' >>> PyVTKTemplate.cxx:(.text+0x173a): undefined reference to >>> `PyDict_SetItemString' >>> PyVTKTemplate.cxx:(.text+0x174a): undefined reference to >>> `PyExc_TypeError' >>> PyVTKTemplate.cxx:(.text+0x1759): undefined reference to >>> `PyErr_SetString' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o: In function >>> `PyVTKTemplate_Repr(_object*)': >>> PyVTKTemplate.cxx:(.text+0x4a): undefined reference to >>> `PyString_FromFormat' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x8): >>> undefined reference to `PyType_Type' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x90): >>> undefined reference to `PyObject_GenericGetAttr' >>> CMakeFiles/vtkWrappingPythonCore.dir/PyVTKTemplate.cxx.o:(.data.rel+0x100): >>> undefined reference to `PyModule_Type' >>> CMakeFiles/vtkWrappingPythonCore.dir/vtkSmartPyObject.cxx.o: In >>> function `vtkSmartPyObject::~vtkSmartPyObject()': >>> vtkSmartPyObject.cxx:(.text+0x35): undefined reference to >>> `Py_IsInitialized' >>> collect2: error: ld returned 1 exit status >>> make[2]: *** [lib/libvtkWrappingPython27Core-pv5.0.so.1] Error 1 >>> make[1]: *** [VTK/Wrapping/PythonCore/CMake >>> Files/vtkWrappingPythonCore.dir/all] Error 2 >>> make: *** [all] Error 2 >>> >>> ------------------------------------------------------------ >>> -------------- >>> >>> I have set the python lib and include paths. And also took care to do >>> "apt-get install python-dev". >>> >>> Thank you in advance for help as I am new and running out of ideas. >>> >>> Also do the configuration options look ok for CPU based rendering? >>> >>> BR, >>> Bishwajit >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 Feb 15 16:58:28 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Wed, 15 Feb 2017 22:58:28 +0100 Subject: [Paraview] Superbuild repo change? In-Reply-To: References: Message-ID: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> > I did a fresh pull of the ParaView superbuild repository, and now I can?t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for ?qt? and ?scipy? in the CMakeLists.txt: .. > After removing those entries, the cmake completes and the build starts and passes out in qt4. > I?m not sure why it?s complaining about OS X 10.7 or later?) For recent OS X qt4 is known to not compile. Use qt5 and it works (macOS 10.12) Fabian From fredericperez1 at gmail.com Wed Feb 15 17:10:31 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Wed, 15 Feb 2017 23:10:31 +0100 Subject: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D Message-ID: Hi all, Is there a way to import (any format) a 4D array in paraview, then to slice one of the dimensions (i.e. use only one 3D hyperplane), and plot the remaining 3D array with paraview's volume rendering? I know I could manipulate the data to make it 3D before using it in Paraview, but I was looking for a way to do this directly. Cheers Fred From info at seoaachen.de Thu Feb 16 04:13:02 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Thu, 16 Feb 2017 10:13:02 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> Message-ID: <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> C:\Program Files\ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin>Visualizer --paraview C:/Program Files/ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit/bin/paraview.exe data c:\temp ls: no such file or directory: /Applications ls: no such file or directory: /opt ls: no such file or directory: /usr/local/opt/ Usage: pvw-visualizer-cli [options] ... I also tried without paraview.exe and /bin/paraview.exe with the same result Am 14.02.2017 um 17:23 schrieb Sebastien Jourdain: > Could you be more explicit regarding the error you encounter as those > output are expected on Windows. > > Did you provide the path to ParaView as the argument of the Visualizer > executable? > > Thanks, > > Seb > > On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga > wrote: > > paraview web visualizer does not work in windows: > > ls: no such file or directory: /Applications > ls: no such file or directory: /opt > ls: no such file or directory: /usr/local/opt/ > > > Am 13.02.2017 um 17:49 schrieb Cory Quammen: > > 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Feb 16 09:09:25 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 16 Feb 2017 09:09:25 -0500 Subject: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D In-Reply-To: References: Message-ID: Hi Fred, Nothing built-in comes to mind to handle 4D data this way, but you could potentially write a Programmable Source to read the file and do the slicing. This would be similar to writing an external program to extract a 3D hyperplane, but you could at least refine the hyperplane definition within the Programmable Source and update the results "live" in ParaView. HTH, Cory On Wed, Feb 15, 2017 at 5:10 PM, Frederic Perez wrote: > Hi all, > > Is there a way to import (any format) a 4D array in paraview, then to > slice one of the dimensions (i.e. use only one 3D hyperplane), and > plot the remaining 3D array with paraview's volume rendering? > > I know I could manipulate the data to make it 3D before using it in > Paraview, but I was looking for a way to do this directly. > > Cheers > Fred > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Thu Feb 16 10:36:35 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 16 Feb 2017 08:36:35 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> Message-ID: Hi Daniel, Visualizer is embedded within the ParaView binary distribution. You don't need the "Visualizer" executable. In fact the Visualizer executable is just a helper that aims to find "pvpython" for you from the ParaView root directory provided by the --paraview argument. On Linux and Mac, the helper look into common place so you could eventually skip the --paraview argument. You should be able to run Visualizer using a command line similar to what is described here: http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity Otherwise, you can always try to run visualizer like follow: Visualizer --paraview "C:/Program Files/ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit" --data "c:\temp" On Thu, Feb 16, 2017 at 2:13 AM, Daniel Zuidinga wrote: > C:\Program Files\ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin>Visualizer > --paraview C:/Program Files/ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit/bin/paraview.exe > data c:\temp > ls: no such file or directory: /Applications > ls: no such file or directory: /opt > ls: no such file or directory: /usr/local/opt/ > > Usage: pvw-visualizer-cli [options] > ... > I also tried without paraview.exe and /bin/paraview.exe with the same > result > > > > Am 14.02.2017 um 17:23 schrieb Sebastien Jourdain: > > Could you be more explicit regarding the error you encounter as those > output are expected on Windows. > > Did you provide the path to ParaView as the argument of the Visualizer > executable? > > Thanks, > > Seb > > On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga > wrote: > >> paraview web visualizer does not work in windows: >> >> ls: no such file or directory: /Applications >> ls: no such file or directory: /opt >> ls: no such file or directory: /usr/local/opt/ >> >> >> Am 13.02.2017 um 17:49 schrieb Cory Quammen: >> >>> 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 >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Feb 16 11:00:56 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Feb 2017 11:00:56 -0500 Subject: [Paraview] Problem testing PV 5.3.0 RC1 In-Reply-To: References: Message-ID: Thanks for the report, Guillaume. I've reported the issue here: https://gitlab.kitware.com/paraview/paraview/issues/17189 On Wed, Feb 15, 2017 at 6:17 AM, Guillaume Jacquenot < guillaume.jacquenot at gmail.com> wrote: > Hello, > > I am testing ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit. > > I run into a problem when using PV with a script. When I launch a simple > script with the command > > D:\ParaView-5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin\paraview.exe > --script=testSphere.py > > I have the following error message in the console, and nothing happens > > Cannot open data file " \paraview.exe " (:0, ) > > Below is testSphere.py > > from paraview.simple import * > paraview.simple._DisableFirstRenderCameraReset() > sphere1 = Sphere() > renderView1 = GetActiveViewOrCreate('RenderView') > sphere1Display = Show(sphere1, renderView1) > renderView1.ResetCamera() > > > My initial goal was to check that the following code works with PV5.3. > For version PV 5.2 it failed, whereas previously it succeeded > > import os > import tempfile > import numpy as np > outputFilename = os.path.join(tempfile.mkdtemp(), 'dummy.npz') > varName='Time' > np.savez(outputFilename, **{varName:np.random.rand(3,4)}) > d = np.load(outputFilename) > time = d[varName] > d.close() > os.remove(outputFilename) > print('Success PV can create a NPZ file and read its content : ' + > outputFilename) > > I had reported this bug, > > http://public.kitware.com/pipermail/paraview/2017-January/038890.html > > and a bug issue had been opened: > > https://gitlab.kitware.com/paraview/paraview-superbuild/issues/43 > > > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Thu Feb 16 11:02:29 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Thu, 16 Feb 2017 16:02:29 +0000 Subject: [Paraview] Examples of Field Variables Manipulation for Exodus Multi-block datasets Message-ID: All, I realize I didn't give much detail - I would hopefully like to know how to do this inside a Programmable Filter, since that is where I am calculating the Total Volume. Thanks, Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Thu Feb 16 11:53:55 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Thu, 16 Feb 2017 16:53:55 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> References: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> Message-ID: Fabian - thank you - that was enough of a hint to get me over the hump. Switched my build to qt5 AND based on some information from a previous email thread, I added the following to my CMAKE command: -DCMAKE_OSX_SDK="macosx10.9" \ -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Fabian Wein Date: Wednesday, February 15, 2017 at 4:58 PM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > I did a fresh pull of the ParaView superbuild repository, and now I >can?t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for ?qt? and ?scipy? in the >CMakeLists.txt: .. > After removing those entries, the cmake completes and the build starts >and passes out in qt4. > I?m not sure why it?s complaining about OS X 10.7 or later?) For recent OS X qt4 is known to not compile. Use qt5 and it works (macOS 10.12) Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From info at seoaachen.de Thu Feb 16 13:35:56 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Thu, 16 Feb 2017 19:35:56 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> Message-ID: <90685a13-2db3-63f8-2afa-cb504d900aa1@seoaachen.de> Hi Sebastien, I tried the pvpython way. A log window opens and directly closes. I can't find a log file? The npm based way gives me the error I mentioned before. Am 16.02.2017 um 16:36 schrieb Sebastien Jourdain: > Hi Daniel, > > Visualizer is embedded within the ParaView binary distribution. You > don't need the "Visualizer" executable. > > In fact the Visualizer executable is just a helper that aims to find > "pvpython" for you from the ParaView root directory provided by the > --paraview argument. On Linux and Mac, the helper look into common > place so you could eventually skip the --paraview argument. > > You should be able to run Visualizer using a command line similar to > what is described here: > http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity > > Otherwise, you can always try to run visualizer like follow: > > Visualizer --paraview "C:/Program Files/ParaView > 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit" --data "c:\temp" > > On Thu, Feb 16, 2017 at 2:13 AM, Daniel Zuidinga > wrote: > > C:\Program Files\ParaView > 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin>Visualizer --paraview > C:/Program Files/ParaView > 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit/bin/paraview.exe data c:\temp > ls: no such file or directory: /Applications > ls: no such file or directory: /opt > ls: no such file or directory: /usr/local/opt/ > > Usage: pvw-visualizer-cli [options] > ... > I also tried without paraview.exe and /bin/paraview.exe with the > same result > > > > Am 14.02.2017 um 17:23 schrieb Sebastien Jourdain: >> Could you be more explicit regarding the error you encounter as >> those output are expected on Windows. >> >> Did you provide the path to ParaView as the argument of the >> Visualizer executable? >> >> Thanks, >> >> Seb >> >> On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga >> > wrote: >> >> paraview web visualizer does not work in windows: >> >> ls: no such file or directory: /Applications >> ls: no such file or directory: /opt >> ls: no such file or directory: /usr/local/opt/ >> >> >> Am 13.02.2017 um 17:49 schrieb Cory Quammen: >> >> 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 >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Thu Feb 16 13:44:28 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Thu, 16 Feb 2017 18:44:28 +0000 Subject: [Paraview] Examples of Field Variables Manipulation for Exodus Multi-block datasets Message-ID: All, Sorry, I answered my own question - I was afraid Field Variables were buried in the "meta" like the Block names were. They were actually a little simpler once I found some time to poke around. To add Total_Volume as a Field Variable inside programmable filter: ... output.DeepCopy(inputs[0]) Total_Volume = calc_Total_Volume() FieldData=output.FieldData Tot_Vol_Array=zeros( (1,1) ) #this is the part I didn't understand I needed Tot_Vol_Array.fill(Total_Volume) FieldData.append(Tot_Vol_Array, "Total_Volume") False alarm this time, but I'm sure I'll be back! Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Feb 16 13:45:10 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 16 Feb 2017 11:45:10 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <90685a13-2db3-63f8-2afa-cb504d900aa1@seoaachen.de> References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> <90685a13-2db3-63f8-2afa-cb504d900aa1@seoaachen.de> Message-ID: Does ParaView works? What happen when you run pvpython and the following set of commands, do you get a crash as well? $ pvpython >>> from paraview.simple import * >>> Cone() >>> Show() >>> Render() On Thu, Feb 16, 2017 at 11:35 AM, Daniel Zuidinga wrote: > Hi Sebastien, > > I tried the pvpython way. A log window opens and directly closes. I can't > find a log file? > The npm based way gives me the error I mentioned before. > > > Am 16.02.2017 um 16:36 schrieb Sebastien Jourdain: > > Hi Daniel, > > Visualizer is embedded within the ParaView binary distribution. You don't > need the "Visualizer" executable. > > In fact the Visualizer executable is just a helper that aims to find > "pvpython" for you from the ParaView root directory provided by the > --paraview argument. On Linux and Mac, the helper look into common place so > you could eventually skip the --paraview argument. > > You should be able to run Visualizer using a command line similar to what > is described here: > http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity > > Otherwise, you can always try to run visualizer like follow: > > Visualizer --paraview "C:/Program Files/ParaView > 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit" --data "c:\temp" > > On Thu, Feb 16, 2017 at 2:13 AM, Daniel Zuidinga > wrote: > >> C:\Program Files\ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin>Visualizer >> --paraview C:/Program Files/ParaView 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit/bin/paraview.exe >> data c:\temp >> ls: no such file or directory: /Applications >> ls: no such file or directory: /opt >> ls: no such file or directory: /usr/local/opt/ >> >> Usage: pvw-visualizer-cli [options] >> ... >> I also tried without paraview.exe and /bin/paraview.exe with the same >> result >> >> >> >> Am 14.02.2017 um 17:23 schrieb Sebastien Jourdain: >> >> Could you be more explicit regarding the error you encounter as those >> output are expected on Windows. >> >> Did you provide the path to ParaView as the argument of the Visualizer >> executable? >> >> Thanks, >> >> Seb >> >> On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga >> wrote: >> >>> paraview web visualizer does not work in windows: >>> >>> ls: no such file or directory: /Applications >>> ls: no such file or directory: /opt >>> ls: no such file or directory: /usr/local/opt/ >>> >>> >>> Am 13.02.2017 um 17:49 schrieb Cory Quammen: >>> >>>> 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 >>> >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Feb 16 16:00:49 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 16 Feb 2017 16:00:49 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> Message-ID: <20170216210049.GA17219@rotor> On Thu, Feb 16, 2017 at 16:53:55 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE command: > > -DCMAKE_OSX_SDK="macosx10.9" \ > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M > acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" That shouldn't be necessary for Qt5 (though if it works, that's great). --Ben From info at seoaachen.de Thu Feb 16 17:09:56 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Thu, 16 Feb 2017 23:09:56 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: <79db7108-6318-1023-7153-d227bfbe8cf2@seoaachen.de> <995f0e2a-35f4-aa75-d02c-cc293f25571c@seoaachen.de> <90685a13-2db3-63f8-2afa-cb504d900aa1@seoaachen.de> Message-ID: paraview works and the cone is rendered in a window as it should Am 16.02.2017 um 19:45 schrieb Sebastien Jourdain: > Does ParaView works? > > What happen when you run pvpython and the following set of commands, > do you get a crash as well? > > $ pvpython > >>> from paraview.simple import * > >>> Cone() > >>> Show() > >>> Render() > > > > > On Thu, Feb 16, 2017 at 11:35 AM, Daniel Zuidinga > wrote: > > Hi Sebastien, > > I tried the pvpython way. A log window opens and directly closes. > I can't find a log file? > The npm based way gives me the error I mentioned before. > > > Am 16.02.2017 um 16:36 schrieb Sebastien Jourdain: >> Hi Daniel, >> >> Visualizer is embedded within the ParaView binary distribution. >> You don't need the "Visualizer" executable. >> >> In fact the Visualizer executable is just a helper that aims to >> find "pvpython" for you from the ParaView root directory provided >> by the --paraview argument. On Linux and Mac, the helper look >> into common place so you could eventually skip the --paraview >> argument. >> >> You should be able to run Visualizer using a command line similar >> to what is described here: >> http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity >> >> >> Otherwise, you can always try to run visualizer like follow: >> >> Visualizer --paraview "C:/Program Files/ParaView >> 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit" --data "c:\temp" >> >> On Thu, Feb 16, 2017 at 2:13 AM, Daniel Zuidinga >> > wrote: >> >> C:\Program Files\ParaView >> 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit\bin>Visualizer --paraview >> C:/Program Files/ParaView >> 5.3.0-RC1-Qt5-OpenGL2-Windows-64bit/bin/paraview.exe data c:\temp >> ls: no such file or directory: /Applications >> ls: no such file or directory: /opt >> ls: no such file or directory: /usr/local/opt/ >> >> Usage: pvw-visualizer-cli [options] >> ... >> I also tried without paraview.exe and /bin/paraview.exe with >> the same result >> >> >> >> Am 14.02.2017 um 17:23 schrieb Sebastien Jourdain: >>> Could you be more explicit regarding the error you encounter >>> as those output are expected on Windows. >>> >>> Did you provide the path to ParaView as the argument of the >>> Visualizer executable? >>> >>> Thanks, >>> >>> Seb >>> >>> On Tue, Feb 14, 2017 at 4:07 AM, Daniel Zuidinga >>> > wrote: >>> >>> paraview web visualizer does not work in windows: >>> >>> ls: no such file or directory: /Applications >>> ls: no such file or directory: /opt >>> ls: no such file or directory: /usr/local/opt/ >>> >>> >>> Am 13.02.2017 um 17:49 schrieb Cory Quammen: >>> >>> 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 >>> >>> >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Feb 17 03:42:54 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 17 Feb 2017 10:42:54 +0200 (EET) Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download Message-ID: <51841.78.190.99.135.1487320974.squirrel@webmail.be.itu.edu.tr> Hi, Yes the issue was related with make version. Actually, I was using pretty old one (cmake/3.5.2) and after upgrading it to cmake/3.7.2, the error is gone. Thanks for your help, --ufuk From u.utku.turuncoglu at be.itu.edu.tr Fri Feb 17 04:39:12 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Fri, 17 Feb 2017 11:39:12 +0200 (EET) Subject: [Paraview] issue about deformed and misplaced color bars ... Message-ID: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> Hi, I was using Catalyst with 5.2 and the color bars are shown as tiny and also misplaced when it is compared with ParaView output. I also checked it with 5.3RC1 and the issue is still in there. So, is there any plan to fix it in 5.3. There ware also discussion about it in the mail list and it seems that it is related with following issue but aim not sure. https://gitlab.kitware.com/paraview/paraview/issues/17113 Regards, --ufuk From yvan.fournier at free.fr Fri Feb 17 04:50:04 2017 From: yvan.fournier at free.fr (yvan.fournier at free.fr) Date: Fri, 17 Feb 2017 10:50:04 +0100 (CET) Subject: [Paraview] Automating contour isosurface values in parallel Catalyst Python script In-Reply-To: Message-ID: <564136989.127267434.1487325004576.JavaMail.root@zimbra10-e2> Hi Andy and Joachim, I adapted Andy's suggestions, and my script is now both slightly simpler (no mpi4py or numpy dependencies) and works on both machines. PS. I cc'd the ParaView mailing list, since I started this thread on it, and forgot "reply to all" in one of my own responses... Thanks again for the help, and best regards, Yvan ----- Mail original ----- De: "Andy Bauer" ?: "Yvan Fournier" , "Joachim Pouderoux" Envoy?: Jeudi 16 F?vrier 2017 16:15:03 Objet: Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script Hi Yvan, I inlined some answers below... Best, Andy ps. I cc'ed Joachim since it looks like you meant to cc him but did not. On Thu, Feb 16, 2017 at 6:25 AM, < yvan.fournier at free.fr > wrote: Hi Andy and Joachim, Thanks for your answers. I suspected I would need a solution of this sort. I prefer computing the min and max myself rather than adapting a Catalyst edition, as I often use full/default ParaView with OSMesa instead of Catalyst Editions (I only got a "standard" base + Python + extensions... edition working very recently; with older versions of the editions, some filter was always missing and I could not use Python scripts generated by the Coprocessing Generator plugin). I generally just use the full PV version also. It is only when I need to be very light on memory that I switch to the Catalyst editions. Others have noted that the Catalyst editions are easier to build on HPC systems though and prefer that route. I made good progress, and now have a solution which works with a 1 or 2-week-old build from the master branch, using numpy, but does not work on a build with ParaView 5.1.2 on an older machine due to missing features: - "from paraview.vtk.numpy_interface.algorithms import *" fails, complaining it does not find numpy and tells me to check it was installed properly (it is installed, though might have been installed after the ParaView build) I do not know about this issue as I have not seen it before and was not involved with the integration. Maybe Joachim knows. Otherwise I would suggest going back to the PV mailing list. - using: controller = coprocessing.vtkCompositeMultiProcessController.GetGlobalController() if controller and controller.IsA("vtkMPIController") and controller.GetNumberOfProcesses() > 1: from mpi4py import MPI comm = vtkMPI4PyCommunicator.ConvertToPython(controller.GetCommunicator()) In cases like this I just use: import vtk controller = vtk.vtkMultiProcessController.GetGlobalController() c.AllReduce(, , , vtk.vtkCommunicator.MAX_OP) to get the max values. vtkCommunicator has the named constants for operations. The "global" communicator will be the one that Catalyst uses which may be a subcommunicator of MPI_COMM_WORLD. I'm not sure if mpi4py will be over the Catalyst MPI processes or all of them. Also, you may want to try "from paraview import vtk" instead of just "import vtk". Less VTK Python stuff should be imported then but it may be missing something you want. I don't use vtkMPI4PYCommunicator so I cannot say how well that should work for your needs. I have a "NameError: global name 'vtkMPI4PyCommunicator' is not defined" message In my earlier tests, I tried simply using the AllReduce() method from the controller, with vtkArrays, but I was stuck on finding the correct value for the last argument, which seems to be an integer describing the collective reduction operation (I need min and max). But I was unable to find any examples for this in Python, (whether Googling for examples or printing dict() and (help() of various Python objects). The documentation only specifies some methods may not be available in Python... Are there named constants describing those operations in the Python wrappers of vtkMPIController ? I assume I could find the integer values in the C++ documentation/sources, but I would rather have named constants for readability and in case of future changes. I guess using the vtkMPIController would slightly simplify the code and reduce dependancy to some external Python modules. Thanks for the help, and best regards, Yvan ----- Mail original ----- De: "Andy Bauer" < andy.bauer at kitware.com > ?: "Joachim Pouderoux" < joachim.pouderoux at kitware.com > Cc: "Yvan Fournier" < yvan.fournier at free.fr >, "ParaView" < paraview at paraview.org > Envoy?: Mardi 14 F?vrier 2017 21:27:06 Objet: Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script Hi Yvan, Another option is just to compute it yourself. The reason that the global min and max aren't know in Catalyst is that it requires communication but many times the value isn't needed so in order to make Catalyst more efficient it doesn't compute that value for you automatically. In the Python scripts you can import mpi4py or import vtk and use the vtkMultiProcessController to do the global operation. Note that for my way you'll need to call UpdatePipeline(datadescription.GetTime()) before getting the output and globally determining the value. Then you can set the isosurfaces values array with that information. If you try this out and have issues, please let us know and we can go from there. Cheers, Andy On Tue, Feb 14, 2017 at 3:02 PM, Joachim Pouderoux < joachim.pouderoux at kitware.com > wrote: Hi Yvan, Regarding MinMax: this filter is indeed not exposed by any standard Catalyst edition but it is easy to add. See for instance in ParaView/Catalyst/Editions/Extras/manifest.json how the PVExtractSelection filter is exposed (line 50 and 247). Just do the same with the MinMax filter (see proxy's declaration at filters.xml:~11725). Best, Joachim Joachim Pouderoux , PhD Technical Expert - Scientific Computing Team Kitware SAS 2017-02-13 17:31 GMT-04:00 Yvan Fournier < yvan.fournier at free.fr > : Hello, I'm in the process of migrating some VTK scripts in the Code_Saturne (code- saturne.org ) test suite to Catalyst Python scripts, and am having some difficulty automating some cases using contour plots: For time-dependent data, I do not know the value ranges in advance, and would like to query them so as to build an Isosurface values array spanning that range. I can manage to access the point and cell data arrays and ther ranges, but printing the ranges in parallel, it seems I have local values only, while I need a global range. I searched for examples in the documentation, on the Wiki, ..., and found an example for MinMax, but don't seem to ba able to access the correct type of Proxy under Catalyst (the default servermanager is not connected in the usual way. For scalar bar color look-up tables, I can manage with "coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in the coprocessing script, but for a more general case such as thar needed for contour plots, I've been running around in circles in the last hours trying to find and adapt a relevant example. Does anyone have a suggestion ? Thanks in advance, Yvan Fournier _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 richard.c.angelini.civ at mail.mil Fri Feb 17 07:43:17 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Fri, 17 Feb 2017 12:43:17 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <20170216210049.GA17219@rotor> References: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> <20170216210049.GA17219@rotor> Message-ID: Cmake was complaining about CMAKE_OSX_SDK not being set ? I?m not sure if I needed to set both variables, but I recalled seeing this in a mail thread, so I just set it! 8-) ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel Reply-To: "ben.boeckel at kitware.com" Date: Thursday, February 16, 2017 at 4:00 PM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Thu, Feb 16, 2017 at 16:53:55 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE command: > > -DCMAKE_OSX_SDK="macosx10.9" \ > >-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/ >M > acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" That shouldn't be necessary for Qt5 (though if it works, that's great). --Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From ben.boeckel at kitware.com Fri Feb 17 07:57:13 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 17 Feb 2017 07:57:13 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> <20170216210049.GA17219@rotor> Message-ID: <20170217125713.GA7876@megas.kitware.com> On Fri, Feb 17, 2017 at 12:43:17 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set ? > I?m not sure if I needed to set both variables, but I recalled seeing this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben From michel.rasquin at colorado.edu Fri Feb 17 08:17:37 2017 From: michel.rasquin at colorado.edu (Michel Rasquin) Date: Fri, 17 Feb 2017 13:17:37 +0000 Subject: [Paraview] PVSB 5.2: missing modules and plugins after "make install" In-Reply-To: <20170213142341.GA31880@megas.kitware.com> References: , <20170213142341.GA31880@megas.kitware.com> Message-ID: Hi Cory and Ben, After your email, I updated my PVSB 5.2 version, recompiled from a clean build directory and reinstalled to a fresh directory. Unfortunately, I can still observe the same behavior as before so the latest changes you mentioned in your email did not fix this issue. If this can help, my new sha key is ba573eace90abaeb79247e570ff4509a54e75b76. Has anybody already tested successfully PVSB 5.2 from the install directory without loosing plugins and other module down the road? Thanks. Best regards, Michel ________________________________ From: Ben Boeckel Sent: Monday, February 13, 2017 3:23:41 PM To: Cory Quammen Cc: Michel Rasquin; paraview at paraview.org Subject: Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install" On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote: > Will updating to the current superbuild master address the missing > plugins issue Michel is seeing? It looks like there have been some > minor changes on plugin handling in linux since > 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16. Yes, it's possible. If you look at the output of the packaging step, there is probably some set of system libraries being pulled into the package which should not be there. --Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Feb 17 09:42:41 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 17 Feb 2017 09:42:41 -0500 Subject: [Paraview] PVSB 5.2: missing modules and plugins after "make install" In-Reply-To: References: <20170213142341.GA31880@megas.kitware.com> Message-ID: <20170217144241.GA12031@megas.kitware.com> On Fri, Feb 17, 2017 at 13:17:37 +0000, Michel Rasquin wrote: > Has anybody already tested successfully PVSB 5.2 from the install > directory without loosing plugins and other module down the road? Oh, running from the install directory? That's not really fully supported. The reason is that we have 3 places ParaView ends up during the superbuild: - the build tree - the install tree - the package Getting it to work in all three on all platforms is not really feasible, so we prioritize them as: - the package (because this has to work) - the build tree (so that tests can be run) - the install tree It is best to make the package (ctest -R cpack-paraview-TGZ) and then either run from _CPack_Packages/... or extract the generated tarball somewhere else and run that. There is also `make install`, which should also work just fine (it basically just does the packaging step to a given directory and then doesn't actually make the package). --Ben From andy.bauer at kitware.com Fri Feb 17 10:01:04 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 17 Feb 2017 10:01:04 -0500 Subject: [Paraview] Automating contour isosurface values in parallel Catalyst Python script In-Reply-To: <564136989.127267434.1487325004576.JavaMail.root@zimbra10-e2> References: <564136989.127267434.1487325004576.JavaMail.root@zimbra10-e2> Message-ID: Glad to hear! Also, thanks for replying to the list. On Fri, Feb 17, 2017 at 4:50 AM, wrote: > > Hi Andy and Joachim, > > I adapted Andy's suggestions, and my script is now both slightly simpler > (no mpi4py or numpy dependencies) and works on both machines. > > PS. I cc'd the ParaView mailing list, since I started this thread on it, > and forgot "reply to all" in one of my own responses... > > Thanks again for the help, and best regards, > > Yvan > > ----- Mail original ----- > De: "Andy Bauer" > ?: "Yvan Fournier" , "Joachim Pouderoux" < > joachim.pouderoux at kitware.com> > Envoy?: Jeudi 16 F?vrier 2017 16:15:03 > Objet: Re: [Paraview] Automating contour isosurface values in parallel > Catalyst Python script > > > > Hi Yvan, > > I inlined some answers below... > > Best, > Andy > > ps. I cc'ed Joachim since it looks like you meant to cc him but did not. > > > > > > > > On Thu, Feb 16, 2017 at 6:25 AM, < yvan.fournier at free.fr > wrote: > > > Hi Andy and Joachim, > > Thanks for your answers. I suspected I would need a solution of this sort. > > I prefer computing the min and max myself rather than adapting a Catalyst > edition, as I often use full/default ParaView with OSMesa instead of > Catalyst Editions (I only got a "standard" base + Python + extensions... > edition working very recently; with older versions of the editions, some > filter was always missing and I could not use Python scripts generated by > the Coprocessing Generator plugin). > > > > I generally just use the full PV version also. It is only when I need to > be very light on memory that I switch to the Catalyst editions. Others have > noted that the Catalyst editions are easier to build on HPC systems though > and prefer that route. > > > > > I made good progress, and now have a solution which works with a 1 or > 2-week-old build from the master branch, using numpy, but does not work on > a build with ParaView 5.1.2 on an older machine due to missing features: > > - "from paraview.vtk.numpy_interface.algorithms import *" fails, > complaining it does not find numpy and tells me to check it was installed > properly (it is installed, though might have been installed after the > ParaView build) > > > > I do not know about this issue as I have not seen it before and was not > involved with the integration. Maybe Joachim knows. Otherwise I would > suggest going back to the PV mailing list. > > > > > - using: > controller = coprocessing.vtkCompositeMultiProcessContro > ller.GetGlobalController() > if controller and controller.IsA("vtkMPIController") and controller.GetNumberOfProcesses() > > 1: > from mpi4py import MPI > comm = vtkMPI4PyCommunicator.ConvertToPython(controller.GetCommunicator()) > > > > > In cases like this I just use: > > import vtk > > controller = vtk.vtkMultiProcessController.GetGlobalController() > > c.AllReduce(, , , vtk.vtkCommunicator.MAX_OP) > > > to get the max values. vtkCommunicator has the named constants for > operations. The "global" communicator will be the one that Catalyst uses > which may be a subcommunicator of MPI_COMM_WORLD. I'm not sure if mpi4py > will be over the Catalyst MPI processes or all of them. Also, you may want > to try "from paraview import vtk" instead of just "import vtk". Less VTK > Python stuff should be imported then but it may be missing something you > want. I don't use vtkMPI4PYCommunicator so I cannot say how well that > should work for your needs. > > > > > I have a "NameError: global name 'vtkMPI4PyCommunicator' is not defined" > message > > In my earlier tests, I tried simply using the AllReduce() method from the > controller, with vtkArrays, but I was stuck on finding the correct value > for the last argument, which seems to be an integer describing the > collective reduction operation (I need min and max). But I was unable to > find any examples for this in Python, (whether Googling for examples or > printing dict() and (help() of various Python objects). > The documentation only specifies some methods may not be available in > Python... > > Are there named constants describing those operations in the Python > wrappers of vtkMPIController ? > I assume I could find the integer values in the C++ documentation/sources, > but I would rather have named constants for readability and in case of > future changes. > I guess using the vtkMPIController would slightly simplify the code and > reduce dependancy to some external Python modules. > > Thanks for the help, and best regards, > > Yvan > > ----- Mail original ----- > De: "Andy Bauer" < andy.bauer at kitware.com > > ?: "Joachim Pouderoux" < joachim.pouderoux at kitware.com > > Cc: "Yvan Fournier" < yvan.fournier at free.fr >, "ParaView" < > paraview at paraview.org > > Envoy?: Mardi 14 F?vrier 2017 21:27:06 > Objet: Re: [Paraview] Automating contour isosurface values in parallel > Catalyst Python script > > > > > > > Hi Yvan, > > Another option is just to compute it yourself. The reason that the global > min and max aren't know in Catalyst is that it requires communication but > many times the value isn't needed so in order to make Catalyst more > efficient it doesn't compute that value for you automatically. In the > Python scripts you can import mpi4py or import vtk and use the > vtkMultiProcessController to do the global operation. Note that for my way > you'll need to call UpdatePipeline(datadescription.GetTime()) before > getting the output and globally determining the value. Then you can set the > isosurfaces values array with that information. > > If you try this out and have issues, please let us know and we can go from > there. > > Cheers, > Andy > > > > On Tue, Feb 14, 2017 at 3:02 PM, Joachim Pouderoux < > joachim.pouderoux at kitware.com > wrote: > > > > > > > > > Hi Yvan, > > Regarding MinMax: this filter is indeed not exposed by any standard > Catalyst edition but it is > easy to add. See for instance in ParaView/Catalyst/Editions/Extras/manifest.json > how the > PVExtractSelection filter is exposed (line 50 and 247). > Just do the same with the MinMax filter (see proxy's declaration at > filters.xml:~11725). > > Best, > Joachim > > > > > > > > > > > > > > > Joachim Pouderoux , PhD > > > Technical Expert - Scientific Computing Team > Kitware SAS > > > > > 2017-02-13 17:31 GMT-04:00 Yvan Fournier < yvan.fournier at free.fr > : > > > Hello, > > I'm in the process of migrating some VTK scripts in the Code_Saturne (code- > saturne.org ) test suite to Catalyst Python scripts, and am having some > > > difficulty automating some cases using contour plots: > > For time-dependent data, I do not know the value ranges in advance, and > would > like to query them so as to build an Isosurface values array spanning that > range. > > I can manage to access the point and cell data arrays and ther ranges, but > printing the ranges in parallel, it seems I have local values only, while > I need > a global range. > > I searched for examples in the documentation, on the Wiki, ..., and found > an > example for MinMax, but don't seem to ba able to access the correct type of > Proxy under Catalyst (the default servermanager is not connected in the > usual > way. > > For scalar bar color look-up tables, I can manage with > "coprocessor.WriteImages(datadescription, rescale_lookuptable=True)" in > the > coprocessing script, but for a more general case such as thar needed for > contour > plots, I've been running around in circles in the last hours trying to > find and > adapt a relevant example. > > Does anyone have a suggestion ? Thanks in advance, > > Yvan Fournier > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 andy.bauer at kitware.com Fri Feb 17 11:32:37 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 17 Feb 2017 11:32:37 -0500 Subject: [Paraview] issue about deformed and misplaced color bars ... In-Reply-To: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> References: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> Message-ID: Hi Ufuk, I'm not sure if this fix will make it into the 5.3 release. We'll try but we have a pretty hard deadline for the release. As a workaround, while Trace is not capturing the movement the Python state does. You can use that information to set the desired values in your Catalyst Python script. The example from my Python state is: rTDataLUTColorBar = GetScalarBar(rTDataLUT, renderView1) rTDataLUTColorBar.Position = [0.30443396226415076, 0.7281124807395994] rTDataLUTColorBar.Position2 = [0.43000000000000027, 0.1200000000000001] rTDataLUTColorBar.Orientation = 'Horizontal' rTDataLUTColorBar.Title = 'RTData' rTDataLUTColorBar.ComponentTitle = '' rTDataLUTColorBar.TitleFontSize = 16 rTDataLUTColorBar.LabelBold = 1 rTDataLUTColorBar.LabelItalic = 1 rTDataLUTColorBar.LabelFontSize = 16 Currently there's an issue with the LabelFontSize. I've entered a gitlab issue at https://gitlab.kitware.com/paraview/paraview/issues/17194 Thanks for checking on this. Best, Andy On Fri, Feb 17, 2017 at 4:39 AM, wrote: > Hi, > > I was using Catalyst with 5.2 and the color bars are shown as tiny and > also misplaced when it is compared with ParaView output. I also checked it > with 5.3RC1 and the issue is still in there. So, is there any plan to fix > it in 5.3. There ware also discussion about it in the mail list and it > seems that it is related with following issue but aim not sure. > > https://gitlab.kitware.com/paraview/paraview/issues/17113 > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Fri Feb 17 11:38:35 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Fri, 17 Feb 2017 16:38:35 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <20170217125713.GA7876@megas.kitware.com> References: <9F3AB42C-228E-458D-9DEB-B1E35C4923F2@fau.de> <20170216210049.GA17219@rotor> <20170217125713.GA7876@megas.kitware.com> Message-ID: Ben/Fabian I just did another quick test and it looks like the PVSB 5.2 build on my OS X 10.9 system that this flag was required to get the build to work: -DCMAKE_OSX_SDK="macosx10.9? and this one was apparently optional and not required: -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M acOSX.platform/Developer/SDKs/MacOSX10.9.sdk? Thanks for your help. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel Reply-To: "ben.boeckel at kitware.com" Date: Friday, February 17, 2017 at 7:57 AM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Fri, Feb 17, 2017 at 12:43:17 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set ? > I?m not sure if I needed to set both variables, but I recalled seeing >this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Feb 17 12:05:06 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 17 Feb 2017 12:05:06 -0500 Subject: [Paraview] issue about deformed and misplaced color bars ... In-Reply-To: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> References: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> Message-ID: Ufuk, I believe the issue you're running into is https://gitlab.kitware.com/paraview/paraview/issues/17197, more so than the one your pointed. I have a fix for 17197 on the way: https://gitlab.kitware.com/paraview/paraview/merge_requests/1393 Utkarsh On Fri, Feb 17, 2017 at 4:39 AM, wrote: > Hi, > > I was using Catalyst with 5.2 and the color bars are shown as tiny and > also misplaced when it is compared with ParaView output. I also checked it > with 5.3RC1 and the issue is still in there. So, is there any plan to fix > it in 5.3. There ware also discussion about it in the mail list and it > seems that it is related with following issue but aim not sure. > > https://gitlab.kitware.com/paraview/paraview/issues/17113 > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fredericperez1 at gmail.com Fri Feb 17 12:31:33 2017 From: fredericperez1 at gmail.com (Frederic Perez) Date: Fri, 17 Feb 2017 18:31:33 +0100 Subject: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D In-Reply-To: References: Message-ID: Thank you for this suggestion. I have been looking at programmable sources, and although they are new to me, I think I have found a few issues for my objective: - I seem unable to import a few python packages that I know I can import in a usual python command. - I can't find a way to have this programmable source saved as a file, so that other people can use it. - If people want to have more flexibility using my programmable source, they need to get their hands in the code, which is precisely what I am trying to avoid. Are there solutions to these issues? Or should I simply go make a plugin, instead of a programmable source? Cheers Fred 2017-02-16 15:09 GMT+01:00 Cory Quammen : > Hi Fred, > > Nothing built-in comes to mind to handle 4D data this way, but you > could potentially write a Programmable Source to read the file and do > the slicing. This would be similar to writing an external program to > extract a 3D hyperplane, but you could at least refine the hyperplane > definition within the Programmable Source and update the results > "live" in ParaView. > > HTH, > Cory > > On Wed, Feb 15, 2017 at 5:10 PM, Frederic Perez > wrote: >> Hi all, >> >> Is there a way to import (any format) a 4D array in paraview, then to >> slice one of the dimensions (i.e. use only one 3D hyperplane), and >> plot the remaining 3D array with paraview's volume rendering? >> >> I know I could manipulate the data to make it 3D before using it in >> Paraview, but I was looking for a way to do this directly. >> >> Cheers >> Fred >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 Fri Feb 17 13:37:53 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 17 Feb 2017 13:37:53 -0500 Subject: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D In-Reply-To: References: Message-ID: Fred, A reader plugin would be perfectly reasonable. Distributing a plugin may not be easier than distributing the programmable source file, though, because it needs to be built with the same tools as the ParaView binary. We don't have a ParaView SDK to build against, so you would have to build and distribute both ParaView and your plugin to other folks. It's possible, but a fair amount of work. > - I seem unable to import a few python packages that I know I can > import in a usual python command. More of the standard python packages will be included in 5.3.0, due out early March 2017. A number were not included in 5.2.0. The Programmable Source also provides a way to add to the PYTHONPATH variable if you need to point to other Python modules. Compatibility caveats apply, though. Another option to consider: make an XML plugin out of your Programmable Source. See https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ for details. With this approach, you could distribute an XML file that others load through the Plugin Manager. Any recent version of ParaView would be able to load it - you wouldn't need to build your own ParaView to distribute with it. HTH, Cory On Fri, Feb 17, 2017 at 12:31 PM, Frederic Perez wrote: > Thank you for this suggestion. > > I have been looking at programmable sources, and although they are new > to me, I think I have found a few issues for my objective: > - I seem unable to import a few python packages that I know I can > import in a usual python command. > - I can't find a way to have this programmable source saved as a file, > so that other people can use it. > - If people want to have more flexibility using my programmable > source, they need to get their hands in the code, which is precisely > what I am trying to avoid. > > Are there solutions to these issues? Or should I simply go make a > plugin, instead of a programmable source? > > Cheers > Fred > > > > 2017-02-16 15:09 GMT+01:00 Cory Quammen : >> Hi Fred, >> >> Nothing built-in comes to mind to handle 4D data this way, but you >> could potentially write a Programmable Source to read the file and do >> the slicing. This would be similar to writing an external program to >> extract a 3D hyperplane, but you could at least refine the hyperplane >> definition within the Programmable Source and update the results >> "live" in ParaView. >> >> HTH, >> Cory >> >> On Wed, Feb 15, 2017 at 5:10 PM, Frederic Perez >> wrote: >>> Hi all, >>> >>> Is there a way to import (any format) a 4D array in paraview, then to >>> slice one of the dimensions (i.e. use only one 3D hyperplane), and >>> plot the remaining 3D array with paraview's volume rendering? >>> >>> I know I could manipulate the data to make it 3D before using it in >>> Paraview, but I was looking for a way to do this directly. >>> >>> Cheers >>> Fred >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 utkarsh.ayachit at kitware.com Fri Feb 17 21:21:29 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 17 Feb 2017 21:21:29 -0500 Subject: [Paraview] issue about deformed and misplaced color bars ... In-Reply-To: References: <52286.78.190.99.135.1487324352.squirrel@webmail.be.itu.edu.tr> Message-ID: Ufuk, In any case, both issues are now fixed in `master` and should be available in the next release candidate. Utkarsh On Fri, Feb 17, 2017 at 12:05 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Ufuk, > > I believe the issue you're running into is https://gitlab.kitware.com/ > paraview/paraview/issues/17197, more so than the one your pointed. > > I have a fix for 17197 on the way: https://gitlab.kitware. > com/paraview/paraview/merge_requests/1393 > > Utkarsh > > On Fri, Feb 17, 2017 at 4:39 AM, wrote: > >> Hi, >> >> I was using Catalyst with 5.2 and the color bars are shown as tiny and >> also misplaced when it is compared with ParaView output. I also checked it >> with 5.3RC1 and the issue is still in there. So, is there any plan to fix >> it in 5.3. There ware also discussion about it in the mail list and it >> seems that it is related with following issue but aim not sure. >> >> https://gitlab.kitware.com/paraview/paraview/issues/17113 >> >> 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 >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From archaerolog at mail.ru Sat Feb 18 10:02:09 2017 From: archaerolog at mail.ru (Gena Bug) Date: Sat, 18 Feb 2017 18:02:09 +0300 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: Message-ID: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> 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 > -------------- next part -------------- A non-text attachment was scrubbed... Name: line.52.png Type: image/png Size: 188905 bytes Desc: not available URL: -------------- next part -------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: line.53rc1.png Type: image/png Size: 154934 bytes Desc: not available URL: From mrose81 at gmx.de Sun Feb 19 11:26:05 2017 From: mrose81 at gmx.de (Martin Rose) Date: Sun, 19 Feb 2017 17:26:05 +0100 Subject: [Paraview] polygon rendered incorrectly Message-ID: <53043519-9772-7b05-cb14-dbf1553fda33@gmx.de> Greetings, I have generated a simple vtk file that contains a single polygon. The file is shown below. # vtk DataFile Version 2.0 Output ASCII DATASET UNSTRUCTURED_GRID POINTS 6 float 0.0048265 0.00753943 0 0.0048265 0.00752686 0 0.00485421 0.00752571 0 0.00485266 0.00750789 0 0.00485804 0.00750789 0 0.00485804 0.00753943 0 CELLS 1 7 6 0 1 2 3 4 5 CELL_TYPES 1 7 #end of file After loading the file in paraview, the surface of the polygon is not displayed correctly. It seems that an additional triangle is displayed. However, the wireframe is displayed correctly. I have checked the order of points and confirmed that the order is correct. I also multiplied the coordinates by 100 but the problem persists. If I add the first point of the polygon again, the surface is displayed correctly. The modified lines read: CELLS 1 8 7 0 1 2 3 4 5 0 Unfortunately, that fix does not work for other polygons that show the same problem. Is there something wrong with my vtk file? Greetings, Martin From ken.martin at kitware.com Sun Feb 19 21:03:10 2017 From: ken.martin at kitware.com (Ken Martin) Date: Sun, 19 Feb 2017 21:03:10 -0500 Subject: [Paraview] polygon rendered incorrectly In-Reply-To: <53043519-9772-7b05-cb14-dbf1553fda33@gmx.de> References: <53043519-9772-7b05-cb14-dbf1553fda33@gmx.de> Message-ID: Convex or concave? If concave you need to triangle filter first. More generally, if you have unknown polygons that could be convex, you need to triangle filter first. Just guessing that is the issue. Ken On Sun, Feb 19, 2017 at 11:26 AM, Martin Rose wrote: > Greetings, > > I have generated a simple vtk file that contains a single polygon. The > file is shown below. > > # vtk DataFile Version 2.0 > Output > ASCII > DATASET UNSTRUCTURED_GRID > POINTS 6 float > 0.0048265 0.00753943 0 > 0.0048265 0.00752686 0 > 0.00485421 0.00752571 0 > 0.00485266 0.00750789 0 > 0.00485804 0.00750789 0 > 0.00485804 0.00753943 0 > CELLS 1 7 > 6 0 1 2 3 4 5 > CELL_TYPES 1 > 7 > #end of file > > > After loading the file in paraview, the surface of the polygon is not > displayed correctly. It seems that an additional triangle is displayed. > However, the wireframe is displayed correctly. I have checked the order of > points and confirmed that the order is correct. I also multiplied the > coordinates by 100 but the problem persists. > > If I add the first point of the polygon again, the surface is displayed > correctly. The modified lines read: > CELLS 1 8 > 7 0 1 2 3 4 5 0 > > Unfortunately, that fix does not work for other polygons that show the > same problem. > Is there something wrong with my vtk file? > > Greetings, > Martin > > > _______________________________________________ > 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 > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukas.kresta at gmail.com Mon Feb 20 03:26:15 2017 From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=) Date: Mon, 20 Feb 2017 09:26:15 +0100 Subject: [Paraview] 3 arguments to _CreatePipeline for Catalyst Message-ID: Is somehow possible to send 3. argument to CreatePipeline or it is fixed to have only 2 arguments? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlopezfisica at ciencias.unam.mx Mon Feb 20 06:27:15 2017 From: jlopezfisica at ciencias.unam.mx (=?UTF-8?B?Sm9zw6kgTHVpcyBMw7NwZXogTMOzcGV6?=) Date: Mon, 20 Feb 2017 12:27:15 +0100 Subject: [Paraview] Error writing Paraview on MPI Message-ID: Hi! All, I am writing my VTK files through the server in MPI 32 processors. It seems that it is not writing right my files, does someone has a clue or how to track the bug? for small domains it seems to work fine, Jose -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bug.png Type: image/png Size: 251513 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bug2.png Type: image/png Size: 257788 bytes Desc: not available URL: From andy.bauer at kitware.com Mon Feb 20 10:02:40 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 20 Feb 2017 10:02:40 -0500 Subject: [Paraview] Error writing Paraview on MPI In-Reply-To: References: Message-ID: Hi, You will need to be more specific about what you are exactly doing. Are you writing out your data in VTK or ParaView with 32 processes or some other way? Can you share your data set? That would help diagnose the issue. Andy On Mon, Feb 20, 2017 at 6:27 AM, Jos? Luis L?pez L?pez < jlopezfisica at ciencias.unam.mx> wrote: > Hi! All, > > I am writing my VTK files through the server in MPI 32 processors. It > seems that it is not writing right my files, does someone has a clue or how > to track the bug? > > for small domains it seems to work fine, > > Jose > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Mon Feb 20 10:08:38 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 20 Feb 2017 10:08:38 -0500 Subject: [Paraview] 3 arguments to _CreatePipeline for Catalyst In-Reply-To: References: Message-ID: Hi, If you edit the coprocessing.py script in the ParaView build/install directory you can do that. Maybe an easier way though is to just create global variable that is used in your _CreatePipeline() method. An example is: from paraview.simple import * from paraview import coprocessing myvalue = 0 #-------------------------------------------------------------- # Code generated from cpstate.py to create the CoProcessor. # ParaView 5.1.2-411-gf717569 64 bits # ----------------------- CoProcessor definition ----------------------- def CreateCoProcessor(): def _CreatePipeline(coprocessor, datadescription): class Pipeline: global myvalue print 'myvalue is ', myvalue ... On Mon, Feb 20, 2017 at 3:26 AM, Luk?? Kresta wrote: > Is somehow possible to send 3. argument to CreatePipeline or it is fixed > to have only 2 arguments? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Feb 20 15:48:38 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 20 Feb 2017 15:48:38 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> Message-ID: 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 florian.konrad at tum.de Tue Feb 21 08:20:31 2017 From: florian.konrad at tum.de (Konrad, Florian) Date: Tue, 21 Feb 2017 13:20:31 +0000 Subject: [Paraview] How to increase render quality for exodus mesh file Message-ID: <03aaf41ac5b2438e8eaeece24b4d86e7@BADWLRZ-SW13MB4.ads.mwn.de> Hello everyone, I have a result of a numerical simulation saved in an exodus-file. This file contains an unstructured mesh made of tetrahedral elements and the simulation results as elemental or nodal values. My problem is that the quality of the visualization of my exodus file is not the best. As you can see in the following screenshot the edges of the features look really bad. http://imgur.com/a/SBT4r Is there a way to increase the quality somewhere or does somebody know why it looks like this? The quality of the edges seems to be related to the angle in which I view them. Greetings Florian -------------- next part -------------- An HTML attachment was scrubbed... URL: From tj.corona at kitware.com Tue Feb 21 08:34:13 2017 From: tj.corona at kitware.com (TJ Corona) Date: Tue, 21 Feb 2017 08:34:13 -0500 Subject: [Paraview] How to increase render quality for exodus mesh file In-Reply-To: <03aaf41ac5b2438e8eaeece24b4d86e7@BADWLRZ-SW13MB4.ads.mwn.de> References: <03aaf41ac5b2438e8eaeece24b4d86e7@BADWLRZ-SW13MB4.ads.mwn.de> Message-ID: Hi Florian, Would you be able to send a representative data file (either .vtu or .exo) along with the image? Sincerely, T.J. Thomas J. Corona, Ph.D. Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4443 > On Feb 21, 2017, at 8:20 AM, Konrad, Florian wrote: > > Hello everyone, > I have a result of a numerical simulation saved in an exodus-file. This file contains an unstructured mesh made of tetrahedral elements and the simulation results as elemental or nodal values. > My problem is that the quality of the visualization of my exodus file is not the best. As you can see in the following screenshot the edges of the features look really bad. http://imgur.com/a/SBT4r > Is there a way to increase the quality somewhere or does somebody know why it looks like this? The quality of the edges seems to be related to the angle in which I view them. > Greetings > Florian > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 nabil.ghodbane at gmail.com Tue Feb 21 08:39:06 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 14:39:06 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 Message-ID: dear experts, I am trying to compile Paraview 5.2 with gcc 4.8 + Qt 4.8 + VTK 5.10 + Python 2.7 (available with Miniconda) on a CentOS 7 machine. it compiles well, but I fail to run the Paraview; Paraview starts, but when I try to open a file, I get: ERROR: In /root/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 641 vtkXOpenGLRenderWindow (0x1b85d60): 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. could some expert either point me to some standard approach, I need to use, or point me to the relevant cmake flags to set? thanks for your valuable help Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabil.ghodbane at gmail.com Tue Feb 21 08:41:18 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 14:41:18 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: In additon to my previous message, if I run Vagrind, I get: ERROR: In /root/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 395 vtkShaderProgram (0x434d1f0): 0:39(12): error: extension `GL_EXT_gpu_shader4' unsupported in fragment shader Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 2:39 PM, Nabil Ghodbane wrote: > dear experts, > I am trying to compile Paraview 5.2 with gcc 4.8 + Qt 4.8 + VTK 5.10 + > Python 2.7 (available with Miniconda) on a CentOS 7 machine. > > it compiles well, but I fail to run the Paraview; Paraview starts, but > when I try to open a file, I get: > > ERROR: In /root/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 641 > vtkXOpenGLRenderWindow (0x1b85d60): 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. > > could some expert either point me to some standard approach, I need to > use, or point me to the relevant cmake flags to set? > thanks for your valuable help > > > Nabil Ghodbane (Ph. D. Habil*.*) > Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043> > Mailto: nabil.ghodbane at gmail.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Tue Feb 21 08:42:09 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Tue, 21 Feb 2017 13:42:09 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <20170215163409.GA8112@megas.kitware.com> References: <20170215163409.GA8112@megas.kitware.com> Message-ID: What are the instructions for using PVSB to build the 5.3- RC ? ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel Reply-To: "ben.boeckel at kitware.com" Date: Wednesday, February 15, 2017 at 11:34 AM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a fresh pull of the ParaView superbuild repository, and now I >can?t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for ?qt? and ?scipy" in the > CMakeLists.txt: You need to run `git submodule update` to update the common-superbuild bits. > After removing those entries, the cmake completes and the build starts >and > passes out in qt4. > I?m not sure why it?s complaining about OS X 10.7 or later?) What version of Xcode are you using? --Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From ken.martin at kitware.com Tue Feb 21 08:56:52 2017 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 21 Feb 2017 08:56:52 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: You need OpenGL version 3.2, try updating mesa to version 12 or later. (11.2 should work also if you are not using OSMesa) Thanks Ken On Tue, Feb 21, 2017 at 8:39 AM, Nabil Ghodbane wrote: > dear experts, > I am trying to compile Paraview 5.2 with gcc 4.8 + Qt 4.8 + VTK 5.10 + > Python 2.7 (available with Miniconda) on a CentOS 7 machine. > > it compiles well, but I fail to run the Paraview; Paraview starts, but > when I try to open a file, I get: > > ERROR: In /root/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 641 > vtkXOpenGLRenderWindow (0x1b85d60): 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. > > could some expert either point me to some standard approach, I need to > use, or point me to the relevant cmake flags to set? > thanks for your valuable help > > > Nabil Ghodbane (Ph. D. Habil*.*) > Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043> > Mailto: nabil.ghodbane at gmail.com > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabil.ghodbane at gmail.com Tue Feb 21 09:25:31 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 15:25:31 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: OK many thanks,; I am trying to use the Superbuild now. I can see that it is downloading Python 2.7.11. Is there a particular reason to use this version instead of the 2.7.12? And how can I switch to the latest stable release ? Or is this against the super build approach ? apologize if my question is non sens thanks. Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 2:56 PM, Ken Martin wrote: > You need OpenGL version 3.2, try updating mesa to version 12 or later. > (11.2 should work also if you are not using OSMesa) > > Thanks > Ken > > On Tue, Feb 21, 2017 at 8:39 AM, Nabil Ghodbane > wrote: > >> dear experts, >> I am trying to compile Paraview 5.2 with gcc 4.8 + Qt 4.8 + VTK 5.10 + >> Python 2.7 (available with Miniconda) on a CentOS 7 machine. >> >> it compiles well, but I fail to run the Paraview; Paraview starts, but >> when I try to open a file, I get: >> >> ERROR: In /root/ParaView-v5.2.0/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, >> line 641 >> vtkXOpenGLRenderWindow (0x1b85d60): 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. >> >> could some expert either point me to some standard approach, I need to >> use, or point me to the relevant cmake flags to set? >> thanks for your valuable help >> >> >> Nabil Ghodbane (Ph. D. Habil*.*) >> Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043> >> Mailto: nabil.ghodbane at gmail.com >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Feb 21 10:07:53 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 21 Feb 2017 10:07:53 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: Hi Rick, >From paraview-superbuild master (remember to run 'git submodule update' after updating master), you should be able to set paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build. These directions are distilled from the README.md file in the superbuild directory [1]. Relevant excerpt: "3. Another option is to use a source tarball of a ParaView release. For that, set paraview_SOURCE_SELECTION to the version to build such as 5.2.0. The superbuild offers the lastest stable release as well as release candidate in preparation for the release. This is the best way to build a released version of ParaView." For each release candidate and release, we add an entry under paraview_SOURCE_SELECTION that you can select. Let us know if you run into problems. Thanks, Cory [1] https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > What are the instructions for using PVSB to build the 5.3- RC ? > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Ben Boeckel > Reply-To: "ben.boeckel at kitware.com" > Date: Wednesday, February 15, 2017 at 11:34 AM > To: Rick Angelini > Cc: ParaView > Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > > On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV > USARMY RDECOM ARL (US) wrote: >> I did a fresh pull of the ParaView superbuild repository, and now I >>can?t do >> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). >> >> First, I had to remove the entries for ?qt? and ?scipy" in the >> CMakeLists.txt: > > You need to run `git submodule update` to update the common-superbuild > bits. > >> After removing those entries, the cmake completes and the build starts >>and >> passes out in qt4. >> I?m not sure why it?s complaining about OS X 10.7 or later?) > > What version of Xcode are you using? > > --Ben > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Tue Feb 21 10:07:59 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 21 Feb 2017 10:07:59 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane wrote: > OK many thanks,; I am trying to use the Superbuild now. > I can see that it is downloading Python 2.7.11. Is there a particular reason > to use this version instead of the 2.7.12? You can change the superbuild to use system Python i.e Python on your system. See docs here (https://gitlab.kitware.com/paraview/paraview-superbuild) Setting CMake variable USE_SYSTEM_python to ON will use whatever is instralled on your system. From nabil.ghodbane at gmail.com Tue Feb 21 10:18:48 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 16:18:48 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: ok thanks for the hint. I obviously missed this point. I will try again. I tried with the Python which is downloaded by the Paraview builder and i am hiting a new issue about libQtLucene.so Is this a known issue ? Here are my settings: gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core) ccmake flags: ENABLE_qt4 ON USE_SYSTEM_qt4 OFF Note, that I can see a compilation failure with the following error message: the compilation fails with: /usr/bin/ld: warning: libQtCLucene.so.4, needed by /root/postlabs/build/superbuild/qt4/build/lib/libQtHelp.so, not found (try using -rpath or -rpath-link) /root/postlabs/build/superbuild/qt4/build/lib/libQtHelp.so: undefined reference to `QCLuceneIndexWriter::~QCLuceneIndexWriter()' collect2: error: ld returned 1 exit status gmake[7]: *** [../../../../bin/assistant] Error 1 gmake[6]: *** [sub-assistant-make_default-ordered] Error 2 gmake[5]: *** [sub-tools-make_default-ordered] Error 2 gmake[4]: *** [sub-assistant-make_default-ordered] Error 2 gmake[3]: *** [sub-tools-make_default-ordered] Error 2 CMake Error at /root/postlabs/build/superbuild/sb-qt4-build.cmake:43 (message): Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 4:07 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane > wrote: > > OK many thanks,; I am trying to use the Superbuild now. > > I can see that it is downloading Python 2.7.11. Is there a particular > reason > > to use this version instead of the 2.7.12? > > You can change the superbuild to use system Python i.e Python on your > system. See docs here > (https://gitlab.kitware.com/paraview/paraview-superbuild) > Setting CMake variable USE_SYSTEM_python to ON will use whatever is > instralled on your system. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Feb 21 10:55:02 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 21 Feb 2017 10:55:02 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: Message-ID: <20170221155502.GA15354@megas.kitware.com> > > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane > > wrote: > > > OK many thanks,; I am trying to use the Superbuild now. > > > I can see that it is downloading Python 2.7.11. Is there a particular > > reason > > > to use this version instead of the 2.7.12? Haven't gotten around to updating to 2.7.12 (we're behind in updating dependencies). On Tue, Feb 21, 2017 at 16:18:48 +0100, Nabil Ghodbane wrote: > ok thanks for the hint. I obviously missed this point. I will try again. > I tried with the Python which is downloaded by the Paraview builder and i > am hiting a new issue about libQtLucene.so > Is this a known issue ? There's a flag qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD you can set (it's marked as advanced, so it is hidden by default). Details are here if you're interested: https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/qt4.common.cmake#L5 --Ben From richard.c.angelini.civ at mail.mil Tue Feb 21 11:31:58 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Tue, 21 Feb 2017 16:31:58 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: I did a ?git pull? and ?git submodule update? in the paraview-superbuild directory. I then changed the source flag in my cmake command: -Dparaview_SOURCE_SELECTION="5.3.0-RC1? and I get this error when doing a clean build. -- Detecting CXX compile features - done -- Check size of void* -- Check size of void* - done CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338 (message): The 5.3.0-RC1 source selection for paraview does not exist. Call Stack (most recent call first): versions.cmake:62 (superbuild_set_selectable_source) superbuild/CMakeLists.txt:96 (include) I grepp?ed through the paraview-superbuild directory and I don?t see any references to 5.3. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Cory Quammen Date: Tuesday, February 21, 2017 at 10:07 AM To: Rick Angelini Cc: "ben.boeckel at kitware.com" , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? 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. ---- Hi Rick, >From paraview-superbuild master (remember to run 'git submodule update' after updating master), you should be able to set paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build. These directions are distilled from the README.md file in the superbuild directory [1]. Relevant excerpt: "3. Another option is to use a source tarball of a ParaView release. For that, set paraview_SOURCE_SELECTION to the version to build such as 5.2.0. The superbuild offers the lastest stable release as well as release candidate in preparation for the release. This is the best way to build a released version of ParaView." For each release candidate and release, we add an entry under paraview_SOURCE_SELECTION that you can select. Let us know if you run into problems. Thanks, Cory [1] Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master /README.md On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > What are the instructions for using PVSB to build the 5.3- RC ? > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Ben Boeckel > Reply-To: "ben.boeckel at kitware.com" > Date: Wednesday, February 15, 2017 at 11:34 AM > To: Rick Angelini > Cc: ParaView > Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > > On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV > USARMY RDECOM ARL (US) wrote: >> I did a fresh pull of the ParaView superbuild repository, and now I >>can?t do >> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). >> >> First, I had to remove the entries for ?qt? and ?scipy" in the >> CMakeLists.txt: > > You need to run `git submodule update` to update the common-superbuild > bits. > >> After removing those entries, the cmake completes and the build starts >>and >> passes out in qt4. >> I?m not sure why it?s complaining about OS X 10.7 or later?) > > What version of Xcode are you using? > > --Ben > > _______________________________________________ > Powered by Caution-www.kitware.com > > Visit other Kitware open-source projects at >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 > > Search the list archives at: >Caution-http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From nenadus at gmail.com Tue Feb 21 11:42:37 2017 From: nenadus at gmail.com (Nenad Vujicic) Date: Tue, 21 Feb 2017 17:42:37 +0100 Subject: [Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color Message-ID: Hello everyone, I'm trying to inspect values of "UseBelowRangeColor" and "UseAboveRangeColor" flags from my ParaView exporter plugin by: 1. Retrieving vtkCompositePolyDataMapper2 from currently active view and rendering window, then, 2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor() and GetUseBelowRangeColor(), However, first call (for checking using above range color) always passes and returns some big number and second one (for checking using below range color) always crashes, regardless whether flags are turned ON / OFF in ParaView UI. Any suggestions about this or ideas how I could pick up these values in different way? Thanks in advance! Nenad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabil.ghodbane at gmail.com Tue Feb 21 11:57:37 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 17:57:37 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: <20170221155502.GA15354@megas.kitware.com> References: <20170221155502.GA15354@megas.kitware.com> Message-ID: hi Ben, many thanks for the prompt reply. I should have hit the toggle option :). No i did not give it a try yet. I will try it and send feedback (I am using miniconda) Does this mean that using non embedded python is still experimental ? thanks Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 4:55 PM, Ben Boeckel wrote: > > > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane > > > wrote: > > > > OK many thanks,; I am trying to use the Superbuild now. > > > > I can see that it is downloading Python 2.7.11. Is there a particular > > > reason > > > > to use this version instead of the 2.7.12? > > Haven't gotten around to updating to 2.7.12 (we're behind in updating > dependencies). > > On Tue, Feb 21, 2017 at 16:18:48 +0100, Nabil Ghodbane wrote: > > ok thanks for the hint. I obviously missed this point. I will try again. > > I tried with the Python which is downloaded by the Paraview builder and i > > am hiting a new issue about libQtLucene.so > > Is this a known issue ? > > There's a flag qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD you can set (it's > marked as advanced, so it is hidden by default). Details are here if > you're interested: > > https://gitlab.kitware.com/paraview/common-superbuild/ > blob/master/projects/qt4.common.cmake#L5 > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabil.ghodbane at gmail.com Tue Feb 21 12:14:39 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 18:14:39 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: <20170221155502.GA15354@megas.kitware.com> Message-ID: Hi, did by chance someone hit this additional issue about missing hdf5 target. I checked that the super build script managed to successfully download the archive: hdf5-1.8.13.tar.gz but it seems, it fails Do I have to switch some additional flag, or is this some issue? thanks -- Found PythonInterp: /root//build/install/bin/python2.7 (found version "2.7.11") CMake Error at CommandLineExecutables/CMakeLists.txt:77 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:82 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:77 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:82 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. -- Configuring incomplete, errors occurred! Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 5:57 PM, Nabil Ghodbane wrote: > hi Ben, > many thanks for the prompt reply. I should have hit the toggle option :). > No i did not give it a try yet. I will try it and send feedback (I am using > miniconda) > Does this mean that using non embedded python is still experimental ? > thanks > > Nabil Ghodbane (Ph. D. Habil*.*) > Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043> > Mailto: nabil.ghodbane at gmail.com > > > On Tue, Feb 21, 2017 at 4:55 PM, Ben Boeckel > wrote: > >> > > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane >> > > wrote: >> > > > OK many thanks,; I am trying to use the Superbuild now. >> > > > I can see that it is downloading Python 2.7.11. Is there a >> particular >> > > reason >> > > > to use this version instead of the 2.7.12? >> >> Haven't gotten around to updating to 2.7.12 (we're behind in updating >> dependencies). >> >> On Tue, Feb 21, 2017 at 16:18:48 +0100, Nabil Ghodbane wrote: >> > ok thanks for the hint. I obviously missed this point. I will try again. >> > I tried with the Python which is downloaded by the Paraview builder and >> i >> > am hiting a new issue about libQtLucene.so >> > Is this a known issue ? >> >> There's a flag qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD you can set (it's >> marked as advanced, so it is hidden by default). Details are here if >> you're interested: >> >> https://gitlab.kitware.com/paraview/common-superbuild/blob/ >> master/projects/qt4.common.cmake#L5 >> >> --Ben >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Feb 21 12:38:24 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 21 Feb 2017 12:38:24 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: <20170221155502.GA15354@megas.kitware.com> Message-ID: <20170221173824.GA17894@megas.kitware.com> On Tue, Feb 21, 2017 at 17:57:37 +0100, Nabil Ghodbane wrote: > many thanks for the prompt reply. I should have hit the toggle option :). It's fine, that bug is elusive and a pain to deal with. > No i did not give it a try yet. I will try it and send feedback (I am using > miniconda) > Does this mean that using non embedded python is still experimental ? Using a system Python is fine, it's just that the one in the superbuild hasn't been bumped. --Ben From nabil.ghodbane at gmail.com Tue Feb 21 12:48:37 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Tue, 21 Feb 2017 18:48:37 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: <20170221173824.GA17894@megas.kitware.com> References: <20170221155502.GA15354@megas.kitware.com> <20170221173824.GA17894@megas.kitware.com> Message-ID: Hi, fine, I started a parallel build on another node using Python 2.7.12, it seems to be compiling so far... As I wrote it previously, the first compilation based on Python 2.7.11 shipped by the superbuilder fails with the following message: do you know by chance whether I do have to switch on/off some flag ? Below, the error messages... thanks for your valuable help -- Found PythonInterp: /root//build/install/bin/python2.7 (found version "2.7.11") CMake Error at CommandLineExecutables/CMakeLists.txt:77 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:82 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:77 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. CMake Error at CommandLineExecutables/CMakeLists.txt:82 (get_property): get_property could not find TARGET hdf5. Perhaps it has not yet been created. -- Configuring incomplete, errors occurred! Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 6:38 PM, Ben Boeckel wrote: > On Tue, Feb 21, 2017 at 17:57:37 +0100, Nabil Ghodbane wrote: > > many thanks for the prompt reply. I should have hit the toggle option :). > > It's fine, that bug is elusive and a pain to deal with. > > > No i did not give it a try yet. I will try it and send feedback (I am > using > > miniconda) > > Does this mean that using non embedded python is still experimental ? > > Using a system Python is fine, it's just that the one in the superbuild > hasn't been bumped. > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Feb 21 13:19:06 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 21 Feb 2017 13:19:06 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: <20170221155502.GA15354@megas.kitware.com> <20170221173824.GA17894@megas.kitware.com> Message-ID: <20170221181906.GA2452@rotor.kitware.com> On Tue, Feb 21, 2017 at 18:48:37 +0100, Nabil Ghodbane wrote: > fine, I started a parallel build on another node using Python 2.7.12, it > seems to be compiling so far... > As I wrote it previously, the first compilation based on Python 2.7.11 > shipped by the superbuilder fails with the following message: > do you know by chance whether I do have to switch on/off some flag ? Hmm. This looks like a problem with ParaView itself. What HDF5 settings are you using in the superbuild and what HDF5-related settings are set in `superbuild/paraview/build/CMakeCache.txt`. --Ben From cory.quammen at kitware.com Tue Feb 21 13:36:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 21 Feb 2017 13:36:16 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: Rick, What is the SHA-1 for last commit in your paraview-superbuild directory? The latest commit on master is 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake at line 63, 5.3.0-RC1 should be listed as a version option. Thanks, Cory On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a ?git pull? and ?git submodule update? in the paraview-superbuild > directory. I then changed the source flag in my cmake command: > > -Dparaview_SOURCE_SELECTION="5.3.0-RC1? > > and I get this error when doing a clean build. > > -- Detecting CXX compile features - done > -- Check size of void* > -- Check size of void* - done > CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338 > (message): > The 5.3.0-RC1 source selection for paraview does not exist. > Call Stack (most recent call first): > versions.cmake:62 (superbuild_set_selectable_source) > superbuild/CMakeLists.txt:96 (include) > > > I grepp?ed through the paraview-superbuild directory and I don?t see any > references to 5.3. > > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Cory Quammen > Date: Tuesday, February 21, 2017 at 10:07 AM > To: Rick Angelini > Cc: "ben.boeckel at kitware.com" , ParaView > > Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? > > 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. > > > > > ---- > > Hi Rick, > > From paraview-superbuild master (remember to run 'git submodule > update' after updating master), you should be able to set > paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build. > > These directions are distilled from the README.md file in the > superbuild directory [1]. Relevant excerpt: > > "3. Another option is to use a source tarball of a ParaView release. > For that, set paraview_SOURCE_SELECTION to the version to build such > as 5.2.0. The superbuild offers the lastest stable release as well as > release candidate in preparation for the release. This is the best way > to build a released version of ParaView." > > For each release candidate and release, we add an entry under > paraview_SOURCE_SELECTION that you can select. > > Let us know if you run into problems. > > Thanks, > Cory > > [1] > Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master > /README.md > > On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY > RDECOM ARL (US) wrote: >> What are the instructions for using PVSB to build the 5.3- RC ? >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> -----Original Message----- >> From: Ben Boeckel >> Reply-To: "ben.boeckel at kitware.com" >> Date: Wednesday, February 15, 2017 at 11:34 AM >> To: Rick Angelini >> Cc: ParaView >> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? >> >> On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV >> USARMY RDECOM ARL (US) wrote: >>> I did a fresh pull of the ParaView superbuild repository, and now I >>>can?t do >>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). >>> >>> First, I had to remove the entries for ?qt? and ?scipy" in the >>> CMakeLists.txt: >> >> You need to run `git submodule update` to update the common-superbuild >> bits. >> >>> After removing those entries, the cmake completes and the build starts >>>and >>> passes out in qt4. >>> I?m not sure why it?s complaining about OS X 10.7 or later?) >> >> What version of Xcode are you using? >> >> --Ben >> >> _______________________________________________ >> Powered by Caution-www.kitware.com >> >> Visit other Kitware open-source projects at >>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 >> >> Search the list archives at: >>Caution-http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> Caution-http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From st.vater at web.de Tue Feb 21 15:31:53 2017 From: st.vater at web.de (Stefan Vater) Date: Tue, 21 Feb 2017 21:31:53 +0100 Subject: [Paraview] problems with packaging of superbuild Message-ID: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> Hi, I have some problems when packaging my paraview superbuild (v5.2.0) after building. When I do ctest -VV -R cpack-paraview-TGZ I first get UpdateCTestConfiguration from :/home/paraview/paraview-5.2.0/DartConfiguration.tcl Parse Config file:/home/paraview/paraview-5.2.0/DartConfiguration.tcl Add coverage exclude regular expressions. SetCTestConfiguration:CMakeCommand:/home/cmake-3.7.2-Linux-x86_64/bin/cmake UpdateCTestConfiguration from :/home/paraview/paraview-5.2.0/DartConfiguration.tcl Parse Config file:/home/paraview/paraview-5.2.0/DartConfiguration.tcl Test project /home/paraview/paraview-5.2.0 Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: cpack-paraview-TGZ 1: Test command: /home/cmake-3.7.2-Linux-x86_64/bin/cmake "-Dname=paraview" "-Dcmake_generator=Unix Makefiles" "-Dcpack_generator=TGZ" "-Doutput_directory=/home/paraview/paraview-5.2.0" "-Dsource_directory=/home/paraview/paraview-5.2.0/cpack/paraview/TGZ" "-Dbuild_directory=/home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build" "-P" "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake" 1: Test timeout computed to be: 6400 1: CMake Error at /home/paraview/paraview-superbuild/superbuild/projects/qt4.functions.cmake:53 (message): 1: Unable to find the sqldrivers/libqsqlite plugin from Qt4 under 1: /home/paraview/paraview-5.2.0/install/../plugins. 1: Call Stack (most recent call first): 1: /home/paraview/paraview-superbuild/projects/paraview.bundle.common.cmake:187 (superbuild_install_qt4_plugin_paths) 1: /home/paraview/paraview-superbuild/projects/unix/paraview.bundle.cmake:5 (include) 1: CMakeLists.txt:32 (include) 1: 1: 1: -- Configuring incomplete, errors occurred! 1: See also "/home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/CMakeFiles/CMakeOutput.log". 1: CMake Error at /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake:9 (message): 1: CMake failed with exit code 1 1: 1: 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.01 sec I then changed in superbuild/projects/qt4.functions.cmake set(qt4_plugin_path "${qt4_base_libdir}/../plugins") to set(qt4_plugin_path "${qt4_base_libdir}/plugins") With that I get [...] 1: Test command: /home/cmake-3.7.2-Linux-x86_64/bin/cmake "-Dname=paraview" "-Dcmake_generator=Unix Makefiles" "-Dcpack_generator=TGZ" "-Doutput_directory=/home/paraview/paraview-5.2.0" "-Dsource_directory=/home/paraview/paraview-5.2.0/cpack/paraview/TGZ" "-Dbuild_directory=/home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build" "-P" "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake" 1: Test timeout computed to be: 6400 1: CMake Error at /home/paraview/paraview-superbuild/superbuild/cmake/SuperbuildInstallMacros.cmake:232 (message): 1: Unable to find the libCatalystScriptGeneratorPlugin.so plugin in 1: lib/paraview-5.2 1: Call Stack (most recent call first): 1: /home/paraview/paraview-superbuild/projects/unix/paraview.bundle.unix.cmake:26 (superbuild_unix_install_plugin) 1: /home/paraview/paraview-superbuild/projects/unix/paraview.bundle.cmake:8 (include) 1: CMakeLists.txt:32 (include) 1: 1: 1: -- Configuring incomplete, errors occurred! 1: See also "/home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/CMakeFiles/CMakeOutput.log". 1: CMake Error at /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake:9 (message): 1: CMake failed with exit code 1 1: 1: 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.02 sec Any help is appreciated! Best regards, Stefan From michalwozniak at live.ca Tue Feb 21 16:16:39 2017 From: michalwozniak at live.ca (michal wozniak) Date: Tue, 21 Feb 2017 21:16:39 +0000 Subject: [Paraview] wrong representation of vtkImageData in pipeline Message-ID: Hi, I am creating an Image using a filter and then adding it to the pipeline. In Paraview, it is displaying a weird image like if it was corrupted. To verify that my filter was creating the image correctly, I am using the vtkTIFFWriter to output the image in tiff format. I open the tiff file using a normal picture app and it is correctly displaying it. I can even load that tiff file in ParaView and it will show it correctly. Has anyone had a similar problem? Is there a solution to this problem. thanks Michal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vtkImageError.png Type: image/png Size: 20239 bytes Desc: vtkImageError.png URL: From andy.bauer at kitware.com Tue Feb 21 17:19:33 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 21 Feb 2017 17:19:33 -0500 Subject: [Paraview] Different visualization result using serial or parallel ParaView ... In-Reply-To: <0eedc9f6-dd19-7285-7648-80cbe8491be9@DLR.de> References: <9e0b078e-cd0c-3483-4d85-76a8d4fac1a6@DLR.de> <0eedc9f6-dd19-7285-7648-80cbe8491be9@DLR.de> Message-ID: Hi Stefan, Thanks for the bug issue report. There is a potential fix in VTK at https://gitlab.kitware.com/vtk/vtk/merge_requests/2504 I am optimistic that this will make it into the upcomgin ParaView 5.3 release. Thanks, Andy On Fri, Feb 10, 2017 at 7:35 AM, Stefan Melber wrote: > Hi, > > amendment: the test case i send to you also crashes using the D31-filter: > > Executing with: Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > 0 > > ============================================================ > ======================= > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = PID 23833 RUNNING AT bsastf670os > = EXIT CODE: 139 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > ============================================================ > ======================= > YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault > (signal 11) > This typically refers to a problem with your application. > Please see the FAQ page for debugging suggestions > > This now looks like a bug ;-) > > Stefan > > Stefan, > > Attached is a fixed state file. Since the file didn't have ghost-cell > information, the filters like "Compute Derivatives" didn't produce correct > result at the process boundary cells. By putting a "Ghost Cell Generator" > filter in the pipeline, one can address that issue. > > Utkarsh > > On Thu, Feb 9, 2017 at 8:18 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> That's odd. Stefan, can you send me the dataset please? I'll have it >> looked into. >> >> Thanks >> Utkarsh >> >> On Thu, Feb 9, 2017 at 4:04 AM, Stefan Melber >> wrote: >> >>> Hi, >>> >>> >>> during visualization of vortices i found a bug (or feature?) of >>> ParaView: running the case in serial mode the results look fine. However, >>> doing the same in parallel mode (e.g. 8 cores) the picture looks "ugly". >>> Has anyone seen such an effect running in parallel? I am using the current >>> version (v5.2.0) on a Linux 64bit machine with a Quadro 4000 graphics card. >>> >>> Attached there are two pics showing the effect, a picture of the used >>> pipeline and the restart file... >>> >>> The test-data can be send to you for testing - i just need a >>> email-address to send it to. >>> >>> Best regards, >>> >>> Stefan >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 andy.bauer at kitware.com Tue Feb 21 17:33:10 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 21 Feb 2017 17:33:10 -0500 Subject: [Paraview] 3 arguments to _CreatePipeline for Catalyst In-Reply-To: References: Message-ID: Hi, Please keep the conversations on the mailing list so that all can participate. The best way currently to pass information back and forth between the adaptor (i.e. C++ code) and the Catalyst pipelines is to use the vtkCPDataDescription's UserData member which is a vtkFieldData object ( http://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/classvtkCPDataDescription.html). It is Python wrapped so you can access it in the Python scripts as well. Cheers, Andy On Tue, Feb 21, 2017 at 2:54 AM, Luk?? Kresta wrote: > Thank you. How can I send that argument from adaptor? (I use C++) > > 2017-02-20 16:08 GMT+01:00 Andy Bauer : > >> Hi, >> >> If you edit the coprocessing.py script in the ParaView build/install >> directory you can do that. >> >> Maybe an easier way though is to just create global variable that is used >> in your _CreatePipeline() method. An example is: >> from paraview.simple import * >> from paraview import coprocessing >> >> myvalue = 0 >> #-------------------------------------------------------------- >> # Code generated from cpstate.py to create the CoProcessor. >> # ParaView 5.1.2-411-gf717569 64 bits >> >> >> # ----------------------- CoProcessor definition ----------------------- >> >> def CreateCoProcessor(): >> def _CreatePipeline(coprocessor, datadescription): >> class Pipeline: >> global myvalue >> print 'myvalue is ', myvalue >> ... >> >> >> >> On Mon, Feb 20, 2017 at 3:26 AM, Luk?? Kresta >> wrote: >> >>> Is somehow possible to send 3. argument to CreatePipeline or it is fixed >>> to have only 2 arguments? >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 Feb 21 20:12:11 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 21 Feb 2017 20:12:11 -0500 Subject: [Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color In-Reply-To: References: Message-ID: Where are you getting the vtkLookupTable from? ParaView doesn't use vtkLookupTable directly, is uses vtkPVDiscretizableColorTransferFunction . Utkarsh On Tue, Feb 21, 2017 at 11:42 AM, Nenad Vujicic wrote: > Hello everyone, > > I'm trying to inspect values of "UseBelowRangeColor" and > "UseAboveRangeColor" flags from my ParaView exporter plugin by: > > 1. Retrieving vtkCompositePolyDataMapper2 from currently active view and > rendering window, then, > 2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor() > and GetUseBelowRangeColor(), > > However, first call (for checking using above range color) always passes > and returns some big number and second one (for checking using below range > color) always crashes, regardless whether flags are turned ON / OFF in > ParaView UI. > > Any suggestions about this or ideas how I could pick up these values in > different way? > > Thanks in advance! > Nenad. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 nabil.ghodbane at gmail.com Wed Feb 22 03:37:47 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Wed, 22 Feb 2017 09:37:47 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: <20170221181906.GA2452@rotor.kitware.com> References: <20170221155502.GA15354@megas.kitware.com> <20170221173824.GA17894@megas.kitware.com> <20170221181906.GA2452@rotor.kitware.com> Message-ID: Hi, here is some feedback: - I am requesting USE_SYSTEM_hdf5 = OFF but looking as you suggested in superbuild/paraview/build/CMakeCache.txt, I can see that VTK_USE_SYSTEM_HDF5:BOOL=TRUE Shouldn't this be FALSE ? Find attached, the CMakeCache.txt, How can I workaround this issue? thanks Find below some additional informations: - it works on Ubuntu (I tried my own Python), but I need to stick to an older glibc :( - on a Debian node, it fails if I use my local Python installation, while trying to compile numpy: "/usr/lib/python2.7/distutils/sysconfig.py" Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodbane at gmail.com On Tue, Feb 21, 2017 at 7:19 PM, Ben Boeckel wrote: > On Tue, Feb 21, 2017 at 18:48:37 +0100, Nabil Ghodbane wrote: > > fine, I started a parallel build on another node using Python 2.7.12, it > > seems to be compiling so far... > > As I wrote it previously, the first compilation based on Python 2.7.11 > > shipped by the superbuilder fails with the following message: > > do you know by chance whether I do have to switch on/off some flag ? > > Hmm. This looks like a problem with ParaView itself. What HDF5 settings > are you using in the superbuild and what HDF5-related settings are set > in `superbuild/paraview/build/CMakeCache.txt`. > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /root/postlabs/build/superbuild/paraview/build # It was generated by CMake: /root/cmake/cmake-3.8.0-rc1-Linux-x86_64/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;/root/postlabs/build/install/lib/libz.so; //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 Verdict with shared libraries. BUILD_SHARED_LIBS:BOOL=ON //Build the testing tree. BUILD_TESTING: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 //No help, variable specified on the command line. 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++ //No help, variable specified on the command line. CMAKE_CXX_FLAGS:STRING=-fPIC -std=c++11 //No help, variable specified on the command line. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //No help, variable specified on the command line. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //No help, variable specified on the command line. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //No help, variable specified on the command line. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //No help, variable specified on the command line. CMAKE_CXX_STANDARD:STRING=11 //No help, variable specified on the command line. CMAKE_CXX_STANDARD_REQUIRED:STRING=TRUE //C compiler CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //No help, variable specified on the command line. CMAKE_C_FLAGS:STRING=-fPIC //No help, variable specified on the command line. CMAKE_C_FLAGS_DEBUG:STRING=-g //No help, variable specified on the command line. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //No help, variable specified on the command line. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //No help, variable specified on the command line. 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=/usr/bin/f95 //Fortran flags CMAKE_Fortran_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_Fortran_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG -Os //Flags used by the compiler during release builds. CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3 -DNDEBUG -O3 //Flags used by the compiler during release builds with debug info. CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //User executables (bin) CMAKE_INSTALL_BINDIR:PATH=bin //Read-only architecture-independent data (DATAROOTDIR) CMAKE_INSTALL_DATADIR:PATH= //Read-only architecture-independent data root (share) CMAKE_INSTALL_DATAROOTDIR:PATH=share //Documentation root (DATAROOTDIR/doc/PROJECT_NAME) CMAKE_INSTALL_DOCDIR:PATH= //C header files (include) CMAKE_INSTALL_INCLUDEDIR:PATH=include //Info documentation (DATAROOTDIR/info) CMAKE_INSTALL_INFODIR:PATH= //Object code libraries (lib64) CMAKE_INSTALL_LIBDIR:PATH=lib64 //Program executables (libexec) CMAKE_INSTALL_LIBEXECDIR:PATH=libexec //Locale-dependent data (DATAROOTDIR/locale) CMAKE_INSTALL_LOCALEDIR:PATH= //Modifiable single-machine data (var) CMAKE_INSTALL_LOCALSTATEDIR:PATH=var //Man documentation (DATAROOTDIR/man) CMAKE_INSTALL_MANDIR:PATH= //C header files for non-gcc (/usr/include) CMAKE_INSTALL_OLDINCLUDEDIR:PATH=/usr/include //No help, variable specified on the command line. CMAKE_INSTALL_PREFIX:PATH=/root/postlabs/build/install //System admin executables (sbin) CMAKE_INSTALL_SBINDIR:PATH=sbin //Modifiable architecture-independent data (com) CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com //Read-only single-machine data (etc) CMAKE_INSTALL_SYSCONFDIR:PATH=etc //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake //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 //No help, variable specified on the command line. CMAKE_PREFIX_PATH:PATH=/root/postlabs/build/install //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=ParaView //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //No help, variable specified on the command line. 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 CatalystScriptGeneratorPlugin_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/Plugins/CatalystScriptGenerator //Dependencies for the target CatalystScriptGeneratorPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;Qt4::QtGui;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so;general;vtkPVServerManagerRendering; //Value Computed by CMake CatalystScriptGeneratorPlugin_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/Plugins/CatalystScriptGenerator //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/DICOMParser //Value Computed by CMake DIY2_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/diy2/vtkdiy2 //Value Computed by CMake DIY2_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/diy2/vtkdiy2 //Path to a library. EXECINFO_LIB:FILEPATH=EXECINFO_LIB-NOTFOUND //Disable compiler warnings EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON //Additional URL templates for the ExternalData CMake script to // look for testing data. E.g. //\nfile:///var/bigharddrive/%(algo)/%(hash) ExternalData_URL_TEMPLATES:STRING= //Path to a file. FREETYPE_INCLUDE_DIR_freetype2:PATH=/root/postlabs/build/install/include/freetype2 //Path to a file. FREETYPE_INCLUDE_DIR_ft2build:PATH=/root/postlabs/build/install/include //Path to a library. FREETYPE_LIBRARY_DEBUG:FILEPATH=FREETYPE_LIBRARY_DEBUG-NOTFOUND //Path to a library. FREETYPE_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libfreetype.so //Value Computed by CMake FmmMesh_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/Plugins/GeodesicMeasurementPlugin/FmmMesh //Dependencies for target FmmMesh_LIB_DEPENDS:STATIC= //Value Computed by CMake FmmMesh_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/Plugins/GeodesicMeasurementPlugin/FmmMesh //Git command line client GIT_EXECUTABLE:FILEPATH=/usr/bin/git //The directory containing gmvread.c, gmvread.h and gmvrayread.h GMVReader_GMVREAD_LIB_DIR:PATH=/root/postlabs/build/superbuild/paraview/src/Utilities/VisItBridge/databases/GMV //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.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=/root/postlabs/build/superbuild/paraview/build/Plugins/GeodesicMeasurementPlugin //Value Computed by CMake GeodesicMeasurementPlugin_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/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;hdf5;general;hdf5;general;vtksys;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //IEEE floating point is available HAVE_IEEEFP:STRING=1 //HDF5 C HL library HDF5_C_HL_LIBRARY:PATH=/root/postlabs/build/install/lib/libhdf5_hl.so.1.8.13 //HDF5 C library HDF5_C_LIBRARY:PATH=/root/postlabs/build/install/lib/libhdf5.so.1.8.13 //HDF5 file differencing tool. HDF5_DIFF_EXECUTABLE:FILEPATH=HDF5_DIFF_EXECUTABLE-NOTFOUND //No help, variable specified on the command line. HDF5_DIR:PATH=/root/postlabs/build/install/share/cmake/hdf5 //No help, variable specified on the command line. HDF5_ROOT:PATH=/root/postlabs/build/install //Native CPU bit order HOST_BIG_ENDIAN:STRING=OFF //Native CPU bit order HOST_FILLORDER:STRING=FILLORDER_LSB2MSB //Value Computed by CMake ICET_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/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=/root/postlabs/build/superbuild/paraview/src/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 //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;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/root/postlabs/build/install/lib/libmpi.so; //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Path to a file. LIBXML2_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/libxml2 //Path to a library. LIBXML2_LIBRARIES:FILEPATH=/root/postlabs/build/install/lib/libxml2.so //Path to a program. LIBXML2_XMLLINT_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/xmllint //Value Computed by CMake LZ4_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/ThirdParty/lz4/vtklz4 //Value Computed by CMake LZ4_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/ThirdParty/lz4/vtklz4 //No help, variable specified on the command line. MACOSX_APP_INSTALL_PREFIX:PATH=/root/postlabs/build/install/Applications //Executable for running MPI programs. MPIEXEC:FILEPATH=/root/postlabs/build/install/bin/mpiexec //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=/root/postlabs/build/install/bin/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING= -DNDEBUG -fPIC -DNDEBUG //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/root/postlabs/build/install/include //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=/root/postlabs/build/install/lib/libmpicxx.so;/root/postlabs/build/install/lib/libmpi.so //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/root/postlabs/build/install/lib -Wl,--enable-new-dtags //Path to a program. MPI_C_COMPILER:FILEPATH=/root/postlabs/build/install/bin/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING= -DNDEBUG -fPIC -DNDEBUG //MPI C include path MPI_C_INCLUDE_PATH:STRING=/root/postlabs/build/install/include //MPI C libraries to link against MPI_C_LIBRARIES:STRING=/root/postlabs/build/install/lib/libmpi.so //MPI C linking flags MPI_C_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/root/postlabs/build/install/lib -Wl,--enable-new-dtags //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=/root/postlabs/build/install/lib/libmpi.so //Path to a program. MPI_Fortran_COMPILER:FILEPATH=/usr/lib64/openmpi/bin/mpif90 //MPI Fortran compilation flags MPI_Fortran_COMPILE_FLAGS:STRING= //MPI Fortran include path MPI_Fortran_INCLUDE_PATH:STRING=/usr/lib64/openmpi/lib //MPI Fortran libraries to link against MPI_Fortran_LIBRARIES:STRING=/usr/lib64/openmpi/lib/libmpi_usempi.so;/usr/lib64/openmpi/lib/libmpi_mpifh.so;/root/postlabs/build/install/lib/libmpi.so //MPI Fortran linking flags MPI_Fortran_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/usr/lib64/openmpi/lib -Wl,--enable-new-dtags //MPI library to link against MPI_LIBRARY:FILEPATH=/root/postlabs/build/install/lib/libmpicxx.so //Path to a library. M_LIBRARY:FILEPATH=/usr/lib64/libm.so //Request building AutobahnPython Module_AutobahnPython:BOOL=OFF //Poisson Surface reconstruction from unorganized points Module_PoissonReconstruction:BOOL=OFF //Request building SixPython Module_SixPython:BOOL=OFF //Request building Twisted Module_Twisted: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 ZopeInterface Module_ZopeInterface:BOOL=OFF //Request building pqDeprecated Module_pqDeprecated:BOOL=OFF //Request building vtkAcceleratorsDax Module_vtkAcceleratorsDax:BOOL=OFF //Request building vtkAcceleratorsPiston Module_vtkAcceleratorsPiston:BOOL=OFF //No help, variable specified on the command line. Module_vtkAcceleratorsVTKm:BOOL=TRUE //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 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= //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 vtkIOTRUCHAS Module_vtkIOTRUCHAS: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 vtkImagingOpenGL2 Module_vtkImagingOpenGL2: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 vtkParseOGLExt Module_vtkParseOGLExt: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 vtkRenderingOculus Module_vtkRenderingOculus:BOOL=OFF //Request building vtkRenderingOpenVR Module_vtkRenderingOpenVR: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 vtkViewsGeovis Module_vtkViewsGeovis:BOOL=OFF //Request building vtkViewsInfovis Module_vtkViewsInfovis:BOOL=OFF //Request building vtkViewsQt Module_vtkViewsQt:BOOL=OFF //Request building vtkWebCore Module_vtkWebCore:BOOL=OFF //Request building vtkWebGLExporter Module_vtkWebGLExporter:BOOL=OFF //Request building vtkWebPython Module_vtkWebPython: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 vtklibproj4 Module_vtklibproj4: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;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;pqApplicationComponents; //Path to a file. OPENGL_INCLUDE_DIR:PATH=/usr/include //Path to a library. OPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so //Path to a library. OPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so //Path to a file. OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND //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 CatalystScriptGeneratorPlugin Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin: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 SLACTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SLACTools: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 //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 CatalystScriptGeneratorPlugin Plugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=TRUE //No help, variable specified on the command line. PARAVIEW_BUILD_PLUGIN_CoProcessingScriptGenerator:BOOL=ON //No help, variable specified on the command line. PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON //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 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 PythonQtPlugin Plugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=FALSE //Build SLACTools Plugin PARAVIEW_BUILD_PLUGIN_SLACTools: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 TemporalParallelismScriptGenerator Plugin PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=FALSE //Build ThickenLayeredCells Plugin PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells:BOOL=TRUE //No help, variable specified on the command line. PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL= //No help, variable specified on the command line. PARAVIEW_BUILD_PLUGIN_VTKmFilters:BOOL=TRUE //Build VaporPlugin Plugin PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE //Enable ParaView Qt-based client PARAVIEW_BUILD_QT_GUI:BOOL=ON //No help, variable specified on the command line. 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= //Build ParaView with CosmoTools VTK Extensions PARAVIEW_ENABLE_COSMOTOOLS:BOOL= //Build the ParaView help menu documentation for ParaView and its // plugins PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION:BOOL=ON //Enable FFMPEG Support. PARAVIEW_ENABLE_FFMPEG:BOOL= //Enable/Disable Python scripting support PARAVIEW_ENABLE_MATPLOTLIB:BOOL=TRUE //Enable/Disable Python scripting support PARAVIEW_ENABLE_PYTHON:BOOL=TRUE //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= //Enable Xdmf3 support (requires Boost). PARAVIEW_ENABLE_XDMF3:BOOL= //Semicolon separated absolute paths to external directories containing // extra VTK/ParaView modules. PARAVIEW_EXTERNAL_MODULE_ROOTS:STRING= //No help, variable specified on the command line. 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=TRUE //Extra paths to search for plugins PARAVIEW_PLUGIN_LOADER_PATHS:STRING= //No help, variable specified on the command line. PARAVIEW_QT_VERSION:STRING=4 //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=TRUE //Use MPI synchronous-send commands for communication PARAVIEW_USE_MPI_SSEND:BOOL=OFF //Build ParaView with OSPRay Ray Traced rendering PARAVIEW_USE_OSPRAY:BOOL= //Build ParaView with Piston GPGPU filters PARAVIEW_USE_PISTON:BOOL=OFF //Use Qt Help infrastructure as needed. PARAVIEW_USE_QTHELP:BOOL=ON //Use Qt WebKit components as needed. PARAVIEW_USE_QTWEBKIT: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= //No help, variable specified on the command line. PARAVIEW_USE_VRPN:BOOL= //No help, variable specified on the command line. PARAVIEW_USE_VTKM:BOOL=TRUE //No help, variable specified on the command line. PARAVIEW_WITH_SUPERBUILD_MESA:BOOL=FALSE //No help, variable specified on the command line. PARAVIEW_WITH_SUPERBUILD_MESA_SWR:BOOL=ON //pkg-config executable PKG_CONFIG_EXECUTABLE:FILEPATH=/usr/bin/pkg-config //Path to a library. PNG_LIBRARY_DEBUG:FILEPATH=PNG_LIBRARY_DEBUG-NOTFOUND //Path to a library. PNG_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libpng.so //Path to a file. PNG_PNG_INCLUDE_DIR:PATH=/root/postlabs/build/install/include //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=/root/postlabs/build/install/bin/python2.7 //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=/root/postlabs/build/install/include/python2.7 //Path to a library. PYTHON_LIBRARY:FILEPATH=/root/postlabs/build/install/lib/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/lib64/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=/root/postlabs/build/superbuild/paraview/build //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=QT_DBUSCPP2XML_EXECUTABLE-NOTFOUND //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=QT_DBUSXML2CPP_EXECUTABLE-NOTFOUND //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/designer //The location of the Qt docs QT_DOC_DIR:PATH=/root/postlabs/build/install/doc //qhelpgenerator used to compile Qt help project files QT_HELP_GENERATOR:FILEPATH=/root/postlabs/build/install/bin/qhelpgenerator //The location of the Qt imports QT_IMPORTS_DIR:PATH=QT_IMPORTS_DIR-NOTFOUND //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/linguist //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/lrelease //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/lupdate //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/root/postlabs/build/install/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/moc //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=QT_PHONONWIDGETS_PLUGIN_RELEASE-NOTFOUND //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=QT_PHONON_INCLUDE_DIR-NOTFOUND //The Qt PHONON library QT_PHONON_LIBRARY:STRING= //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=QT_PHONON_LIBRARY_RELEASE-NOTFOUND //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/root/postlabs/build/install/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/qcollectiongenerator //Path to a library. QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/bearer/libqgenericbearer.so //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqgif.so //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/graphicssystems/libqglgraphicssystem.so //Path to a library. QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QICO_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqico.so //Path to a library. QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/codecs/libqjpcodecs.so //Path to a library. QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqjpeg.so //Path to a library. QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/codecs/libqkrcodecs.so //The qmake executable for the Qt installation to use QT_QMAKE_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/qmake //Path to a library. QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QMNG_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqmng.so //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/sqldrivers/libqsqlite.so //Path to a library. QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLPSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=QT_QSVGICON_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_RELEASE:FILEPATH=QT_QSVG_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQt3Support.so;debug;/root/postlabs/build/install/lib/libQt3Support.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=QT_QT3SUPPORT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQt3Support.so //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/accessible/libqtaccessiblecompatwidgets.so //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtCLucene.so;debug;/root/postlabs/build/install/lib/libQtCLucene.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=QT_QTCLUCENE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtCore.so;debug;/root/postlabs/build/install/lib/libQtCore.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=QT_QTCORE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=QT_QTDBUS_INCLUDE_DIR-NOTFOUND //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING= //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=QT_QTDBUS_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTDECLARATIVE_INCLUDE_DIR:PATH=QT_QTDECLARATIVE_INCLUDE_DIR-NOTFOUND //The Qt QTDECLARATIVE library QT_QTDECLARATIVE_LIBRARY:STRING= //Path to a library. QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=QT_QTDECLARATIVE_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtDesignerComponents.so;debug;/root/postlabs/build/install/lib/libQtDesignerComponents.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtDesigner.so;debug;/root/postlabs/build/install/lib/libQtDesigner.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNER_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtDesigner.so //Path to a library. QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTGA_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqtga.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtGui.so;debug;/root/postlabs/build/install/lib/libQtGui.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=QT_QTGUI_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtHelp.so;debug;/root/postlabs/build/install/lib/libQtHelp.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=QT_QTHELP_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtHelp.so //Path to a library. QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/imageformats/libqtiff.so //Path to a file. QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND //The Qt QTMOTIF library QT_QTMOTIF_LIBRARY:STRING= //Path to a library. QT_QTMOTIF_LIBRARY_DEBUG:FILEPATH=QT_QTMOTIF_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMOTIF_LIBRARY_RELEASE:FILEPATH=QT_QTMOTIF_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=QT_QTMULTIMEDIA_INCLUDE_DIR-NOTFOUND //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING= //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtNetwork.so;debug;/root/postlabs/build/install/lib/libQtNetwork.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=QT_QTNETWORK_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtNetwork.so //Path to a file. QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND //The Qt QTNSPLUGIN library QT_QTNSPLUGIN_LIBRARY:STRING= //Path to a library. QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTOPENGL_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtOpenGL.so;debug;/root/postlabs/build/install/lib/libQtOpenGL.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=QT_QTOPENGL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtOpenGL.so //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/graphicssystems/libqtracegraphicssystem.so //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_RELEASE-NOTFOUND //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=QT_QTSCRIPTTOOLS_INCLUDE_DIR-NOTFOUND //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING= //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=QT_QTSCRIPT_INCLUDE_DIR-NOTFOUND //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING= //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=QT_QTSCRIPT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtSql.so;debug;/root/postlabs/build/install/lib/libQtSql.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=QT_QTSQL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=QT_QTSVG_INCLUDE_DIR-NOTFOUND //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING= //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=QT_QTSVG_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=QT_QTSVG_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtTest.so;debug;/root/postlabs/build/install/lib/libQtTest.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=QT_QTTEST_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtUiTools.a;debug;/root/postlabs/build/install/lib/libQtUiTools.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTUITOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtUiTools.a //Path to a library. QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/root/postlabs/build/install/plugins/codecs/libqtwcodecs.so //Path to a file. QT_QTWEBKIT_INCLUDE_DIR:PATH=QT_QTWEBKIT_INCLUDE_DIR-NOTFOUND //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING= //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=QT_QTWEBKIT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtXmlPatterns //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtXmlPatterns.so;debug;/root/postlabs/build/install/lib/libQtXmlPatterns.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtXmlPatterns.so //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/root/postlabs/build/install/include/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=optimized;/root/postlabs/build/install/lib/libQtXml.so;debug;/root/postlabs/build/install/lib/libQtXml.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=QT_QTXML_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libQtXml.so //Path to a library. QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=QT_QWEBVIEW_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_RCC_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/rcc //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_RELEASE-NOTFOUND //Delay between invocation of each testing event. QT_TESTING_EVENT_PLAYBACK_DELAY:STRING=100 //The location of the Qt translations QT_TRANSLATIONS_DIR:PATH=/root/postlabs/build/install/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/uic //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-NOTFOUND //xmlpatterns used to generate html from Proxy documentation. QT_XMLPATTERNS_EXECUTABLE:FILEPATH=/root/postlabs/build/install/bin/xmlpatterns //Value Computed by CMake QtTesting_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target QtTesting_LIB_DEPENDS:STATIC=general;Qt4::QtCore;general;Qt4::QtGui; //Value Computed by CMake QtTesting_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Explicitly disable SurfaceLIC plugin ctests SURFACELIC_PLUGIN_TESTING:BOOL=ON //Dependencies for the target SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault;general;Qt4::QtGui; //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;general;vtkRenderingLICOpenGL2; //Path to a file. TBB_INCLUDE_DIR:PATH=/root/postlabs/build/install/include //No help, variable specified on the command line. TBB_INCLUDE_DIRS:PATH=/root/postlabs/build/install/include //No help, variable specified on the command line. TBB_LIBRARIES:PATH=/root/postlabs/build/install/lib/libtbb.so* //Path to a library. TBB_LIBRARY_DEBUG:FILEPATH=/root/postlabs/build/install/lib/libtbb_debug.so //Path to a library. TBB_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libtbb.so //Path to a file. TBB_MALLOC_INCLUDE_DIR:PATH=/root/postlabs/build/install/include //No help, variable specified on the command line. TBB_MALLOC_INCLUDE_DIRS:PATH=/root/postlabs/build/install/include //No help, variable specified on the command line. TBB_MALLOC_LIBRARY:FILEPATH=/root/postlabs/build/install/lib/libtbb_malloc.so* //Path to a library. TBB_MALLOC_LIBRARY_DEBUG:FILEPATH=/root/postlabs/build/install/lib/libtbbmalloc_debug.so //Path to a library. TBB_MALLOC_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libtbbmalloc.so //Path to a file. TBB_MALLOC_PROXY_INCLUDE_DIR:PATH=/root/postlabs/build/install/include //Path to a library. TBB_MALLOC_PROXY_LIBRARY_DEBUG:FILEPATH=TBB_MALLOC_PROXY_LIBRARY_DEBUG-NOTFOUND //Path to a library. TBB_MALLOC_PROXY_LIBRARY_RELEASE:FILEPATH=TBB_MALLOC_PROXY_LIBRARY_RELEASE-NOTFOUND //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 //No help, variable specified on the command line. VISIT_BUILD_READER_Boxlib3D:BOOL= //No help, variable specified on the command line. VISIT_BUILD_READER_CGNS:BOOL=OFF //No help, variable specified on the command line. VISIT_BUILD_READER_GMV:BOOL=ON //No help, variable specified on the command line. VISIT_BUILD_READER_Silo:BOOL= //Value Computed by CMake VPIC_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/VPIC //Value Computed by CMake VTKEXPAT_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKEXPAT_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGLEW_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKGLEW_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/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="/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/oggtheora/vtkoggtheora //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=/root/postlabs/build/superbuild/paraview/build/VTK //Request to build all modules VTK_BUILD_ALL_MODULES:BOOL=OFF //Build the VTK Qt plugin for the Qt Designer. VTK_BUILD_QT_DESIGNER_PLUGIN: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=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/root/postlabs/build/superbuild/paraview/src/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 //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=ON //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 //The full path to mpirun command VTK_MPIRUN_EXE:FILEPATH=/root/postlabs/build/install/bin/mpiexec //Maximum number of processors available to run parallel applications. // (see /root/postlabs/build/superbuild/paraview/src/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_MAX_NUMPROCS:STRING=2 //Flag used by mpi to specify the number of processes, the next // option will be the number of processes. (see /root/postlabs/build/superbuild/paraview/src/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIRun.(see /root/postlabs/build/superbuild/paraview/src/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by VTK_MPIRUN_EXE. (see /root/postlabs/build/superbuild/paraview/src/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PREFLAGS:STRING= //These flags will be directly before the number of processess // flag (see /root/postlabs/build/superbuild/paraview/src/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PRENUMPROC_FLAGS:STRING= //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= //No help, variable specified on the command line. VTK_PYTHON_VERSION:STRING=2.7 //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 //No help, variable specified on the command line. VTK_RENDERING_BACKEND:STRING=OpenGL2 //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 //No help, variable specified on the command line. VTK_SMP_IMPLEMENTATION_TYPE:STRING=TBB //Value Computed by CMake VTK_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/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=TRUE //Enable tests requiring "large" data VTK_USE_LARGE_DATA:BOOL=OFF //Use off screen calls by default VTK_USE_OFFSCREEN:BOOL= //Use EGL for OpenGL client API for offscreen rendering. VTK_USE_OFFSCREEN_EGL:BOOL= //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=TRUE //Use system-installed GL2PS VTK_USE_SYSTEM_GL2PS:BOOL=OFF //Use system-installed GLEW VTK_USE_SYSTEM_GLEW:BOOL=OFF //Use system-installed HDF5 VTK_USE_SYSTEM_HDF5:BOOL=TRUE //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=TRUE //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= //Use system-installed OGGTHEORA VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF //Use system-installed PNG VTK_USE_SYSTEM_PNG:BOOL=TRUE //Use system-installed Protobuf VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF //Use system-installed pugixml VTK_USE_SYSTEM_PUGIXML:BOOL=OFF //Use system 'pygments' Python package VTK_USE_SYSTEM_PYGMENTS:BOOL=OFF //Use system-installed qttesting VTK_USE_SYSTEM_QTTESTING:BOOL=OFF //Use system-installed TIFF VTK_USE_SYSTEM_TIFF:BOOL=OFF //Use system-installed xdmf2 VTK_USE_SYSTEM_XDMF2:BOOL=OFF //Use system-installed ZLIB VTK_USE_SYSTEM_ZLIB:BOOL=TRUE //Build VTK with Tk support VTK_USE_TK:BOOL=OFF //Use X for VTK render windows VTK_USE_X:BOOL=ON //Build VPIC with MPI VTK_VPIC_USE_MPI:BOOL=TRUE //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=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/root/postlabs/build/superbuild/paraview/src/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 //No help, variable specified on the command line. VTKm_DIR:PATH=/root/postlabs/build/install/lib //Path to a file. X11_ICE_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_ICE_LIB:FILEPATH=/usr/lib64/libICE.so //Path to a file. X11_SM_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_SM_LIB:FILEPATH=/usr/lib64/libSM.so //Path to a file. X11_X11_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_X11_LIB:FILEPATH=/usr/lib64/libX11.so //Path to a file. X11_XRes_INCLUDE_PATH:PATH=X11_XRes_INCLUDE_PATH-NOTFOUND //Path to a library. X11_XRes_LIB:FILEPATH=X11_XRes_LIB-NOTFOUND //Path to a file. X11_XShm_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_XSync_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_XTest_INCLUDE_PATH:PATH=X11_XTest_INCLUDE_PATH-NOTFOUND //Path to a library. X11_XTest_LIB:FILEPATH=X11_XTest_LIB-NOTFOUND //Path to a file. X11_Xaccessrules_INCLUDE_PATH:PATH=X11_Xaccessrules_INCLUDE_PATH-NOTFOUND //Path to a file. X11_Xaccessstr_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xau_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xau_LIB:FILEPATH=/usr/lib64/libXau.so //Path to a file. X11_Xcomposite_INCLUDE_PATH:PATH=X11_Xcomposite_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xcomposite_LIB:FILEPATH=X11_Xcomposite_LIB-NOTFOUND //Path to a file. X11_Xcursor_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xcursor_LIB:FILEPATH=/usr/lib64/libXcursor.so //Path to a file. X11_Xdamage_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xdamage_LIB:FILEPATH=/usr/lib64/libXdamage.so //Path to a file. X11_Xdmcp_INCLUDE_PATH:PATH=X11_Xdmcp_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xdmcp_LIB:FILEPATH=X11_Xdmcp_LIB-NOTFOUND //Path to a library. X11_Xext_LIB:FILEPATH=/usr/lib64/libXext.so //Path to a file. X11_Xfixes_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xfixes_LIB:FILEPATH=/usr/lib64/libXfixes.so //Path to a file. X11_Xft_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xft_LIB:FILEPATH=/usr/lib64/libXft.so //Path to a file. X11_Xi_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xi_LIB:FILEPATH=/usr/lib64/libXi.so //Path to a file. X11_Xinerama_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xinerama_LIB:FILEPATH=/usr/lib64/libXinerama.so //Path to a file. X11_Xinput_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xinput_LIB:FILEPATH=/usr/lib64/libXi.so //Path to a file. X11_Xkb_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xkbfile_INCLUDE_PATH:PATH=X11_Xkbfile_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xkbfile_LIB:FILEPATH=X11_Xkbfile_LIB-NOTFOUND //Path to a file. X11_Xkblib_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xlib_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xmu_INCLUDE_PATH:PATH=X11_Xmu_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xmu_LIB:FILEPATH=X11_Xmu_LIB-NOTFOUND //Path to a file. X11_Xpm_INCLUDE_PATH:PATH=X11_Xpm_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xpm_LIB:FILEPATH=X11_Xpm_LIB-NOTFOUND //Path to a file. X11_Xrandr_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xrandr_LIB:FILEPATH=/usr/lib64/libXrandr.so //Path to a file. X11_Xrender_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xrender_LIB:FILEPATH=/usr/lib64/libXrender.so //Path to a file. X11_Xscreensaver_INCLUDE_PATH:PATH=X11_Xscreensaver_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xscreensaver_LIB:FILEPATH=X11_Xscreensaver_LIB-NOTFOUND //Path to a file. X11_Xshape_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xt_INCLUDE_PATH:PATH=/usr/include //Path to a library. X11_Xt_LIB:FILEPATH=/usr/lib64/libXt.so //Path to a file. X11_Xutil_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_Xv_INCLUDE_PATH:PATH=X11_Xv_INCLUDE_PATH-NOTFOUND //Path to a library. X11_Xv_LIB:FILEPATH=X11_Xv_LIB-NOTFOUND //Path to a library. X11_Xxf86misc_LIB:FILEPATH=X11_Xxf86misc_LIB-NOTFOUND //Path to a library. X11_Xxf86vm_LIB:FILEPATH=/usr/lib64/libXxf86vm.so //Path to a file. X11_dpms_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_xf86misc_INCLUDE_PATH:PATH=/usr/include //Path to a file. X11_xf86vmode_INCLUDE_PATH:PATH=/usr/include //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=/usr/include/sys //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 //Path to a file. ZLIB_INCLUDE_DIR:PATH=/root/postlabs/build/install/include //Path to a library. ZLIB_LIBRARY_DEBUG:FILEPATH=ZLIB_LIBRARY_DEBUG-NOTFOUND //Path to a library. ZLIB_LIBRARY_RELEASE:FILEPATH=/root/postlabs/build/install/lib/libz.so //Value Computed by CMake alglib_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/alglib //Dependencies for the target mpi4py.MPE_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libpython2.7.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target mpi4py.MPI_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libpython2.7.so;general;/root/postlabs/build/install/lib/libmpi.so;general;dl; //Dependencies for the target mpi4py.dl_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libpython2.7.so;general;dl; //Value Computed by CMake mpi4py_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake mpi4py_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake netcdf_cxx_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_cxx_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Dependencies for the target pmpi-mpe_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target pmpi-vt-hyb_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target pmpi-vt-mpi_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target pmpi-vt_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkjsoncpp;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;Qt4::QtHelp; //Dependencies for the target pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;vtkjsoncpp;general;Qt4::QtNetwork; //Dependencies for the target pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;general;Qt4::QtHelp; //Dependencies for the target pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;/root/postlabs/build/install/lib/libpython2.7.so;general;Qt4::QtGui; //Dependencies for the target pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;general;Qt4::QtNetwork;general;Qt4::QtHelp;general;Qt4::QtGui; //Dependencies for the target protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/ThirdParty/protobuf/vtkprotobuf //Dependencies for the target protobuf_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/ThirdParty/protobuf/vtkprotobuf //Value Computed by CMake tiff_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake tiff_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake verdict_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD; //Dependencies for the target vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtksys;general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkInfovisCore; //Dependencies for the target vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/root/postlabs/build/install/lib/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD; //Dependencies for the target vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD; //Dependencies for the target vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel; //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;optimized;/root/postlabs/build/install/lib/libtbb.so;debug;/root/postlabs/build/install/lib/libtbb_debug.so; //Dependencies for the target vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel; //Dependencies for the target vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;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;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkCommonMisc;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD; //Dependencies for the target vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //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;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD; //Dependencies for the target vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonCore;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 vtkDomainsChemistryOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkDomainsChemistryPythonD;general;vtkDomainsChemistryPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryOpenGL2PythonD; //Dependencies for the target vtkDomainsChemistryOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkDomainsChemistry;general;vtkDomainsChemistry;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkglew;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLParserPythonD;general;vtkRenderingCorePythonD;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD; //Dependencies for the target vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXMLParser;general;vtkRenderingCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys; //Value Computed by CMake vtkExodus2_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/exodusII/vtkexodusII //Dependencies for the target vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD; //Dependencies for the target vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkIOXML;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkCommonMath;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;vtkCommonCorePythonD;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;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD; //Dependencies for the target vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonComputationalGeometry;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;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;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD; //Dependencies for the target vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkImagingCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkCommonMath;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkImagingCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD; //Dependencies for the target vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonCore;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD; //Dependencies for the target vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersStatistics;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkImagingGeneral; //Dependencies for the target vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;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;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkParallelMPI;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkIOCorePythonD;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;vtkCommonCore;general;vtkFiltersFlowPaths;general;vtkFiltersFlowPaths;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkFiltersCore;general;vtkIOCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD; //Dependencies for the target vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeometry;general;vtkParallelMPI;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkIOLegacy;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD; //Dependencies for the target vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersStatistics;general;vtkImagingGeneral;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkImagingCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOLegacyPythonD;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;vtkFiltersStatistics;general;vtkalglib;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkFiltersSources;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOLegacy;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPython_LIB_DEPENDS:STATIC=general;vtkFiltersPointsPythonD; //Dependencies for the target vtkFiltersPoints_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel; //Dependencies for the target vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD; //Dependencies for the target vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;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;/root/postlabs/build/install/lib/libpython2.7.so;general;vtkCommonCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD; //Dependencies for the target vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonComputationalGeometry;general;vtkCommonCore;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkImagingFourierPythonD;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD; //Dependencies for the target vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkalglib;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkImagingFourier; //Dependencies for the target vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD; //Dependencies for the target vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;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;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkInteractionStyle;general;/root/postlabs/build/install/lib/libQtGui.so;general;/root/postlabs/build/install/lib/libQtNetwork.so;general;/root/postlabs/build/install/lib/libQtCore.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so; //Dependencies for the target vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkParallelCore;general;hdf5;general;hdf5;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;vtkCommonCorePythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtksys;general;/root/postlabs/build/install/lib/libz.so; //Dependencies for the target vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD; //Dependencies for the target vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD; //Dependencies for the target vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOXMLParser;general;vtkexoIIc;general;vtkFiltersCore;general;vtksys; //Dependencies for the target vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport; //Dependencies for the target vtkIOExportOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOExportPythonD;general;vtkIOExportPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkIOExportOpenGL2PythonD; //Dependencies for the target vtkIOExportOpenGL2_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkIOExport;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkRenderingCore;general;vtkgl2ps;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkIOExport; //Dependencies for the target vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD; //Dependencies for the target vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkRenderingCore;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeometry;general;vtkIOImage;general;vtkImagingCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD; //Dependencies for the target vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOLegacy;general;vtkCommonCore;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;general;/root/postlabs/build/install/lib/libz.so; //Dependencies for the target vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage; //Dependencies for the target vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImage; //Dependencies for the target vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD; //Dependencies for the target vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkDICOMParser;general;vtkmetaio;general;vtkjpeg;general;/root/postlabs/build/install/lib/libpng.so;general;/root/postlabs/build/install/lib/libz.so;general;vtksys;general;vtktiff;general;/root/postlabs/build/install/lib/libz.so; //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;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;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;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkRenderingCore;general;vtksys;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkIOXMLParserPythonD;general;vtkInfovisCorePythonD;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD; //Dependencies for the target vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXML;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkIOCore;general;vtkIOXMLParser;general;vtkInfovisCore;general;/root/postlabs/build/install/lib/libxml2.so;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD; //Dependencies for the target vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD; //Dependencies for the target vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkCommonMisc;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkParallelCore;general;vtkParallelMPI;general;vtksys;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelMPI;general;vtksys;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD; //Dependencies for the target vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkoggtheora;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //Dependencies for the target vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD; //Dependencies for the target vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys; //Dependencies for the target vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD; //Dependencies for the target vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkCommonDataModel;general;vtkCommonMisc; //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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;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;vtkCommonCore;general;vtkIOExodus;general;vtkIOExodus;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkParallelCore;general;vtkexoIIc;general;vtksys; //Dependencies for the target vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkIOLSDyna;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkParallelMPIPythonD;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD; //Dependencies for the target vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkNetCDF;general;vtkNetCDF_cxx;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkIOCorePythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOLegacyPythonD;general;vtkIONetCDFPythonD;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOGeometry;general;vtkIOImage;general;vtkIOLegacy;general;vtkIONetCDF;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkParallelCore;general;vtkexoIIc;general;vtkjsoncpp;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys; //Dependencies for the target vtkIOTecplotTableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePython_LIB_DEPENDS:STATIC=general;vtkIOTecplotTablePythonD; //Dependencies for the target vtkIOTecplotTable_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOCore;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;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;VPIC;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkParallelCore; //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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD; //Dependencies for the target vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkIOCore;general;vtkexpat; //Dependencies for the target vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkIOXML; //Dependencies for the target vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD; //Dependencies for the target vtkIOXML_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;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;vtkIOXMLParserPythonD;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;vtkIOLegacy;general;vtkFiltersExtraction;general;vtkIOXMLParser;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingCorePythonD;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD; //Dependencies for the target vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem; //Dependencies for the target vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD; //Dependencies for the target vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD; //Dependencies for the target vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD; //Dependencies for the target vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOImage;general;vtkImagingCore; //Dependencies for the target vtkImagingMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPython_LIB_DEPENDS:STATIC=general;vtkImagingMathPythonD; //Dependencies for the target vtkImagingMath_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD; //Dependencies for the target vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD; //Dependencies for the target vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD; //Dependencies for the target vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingColor;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD; //Dependencies for the target vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersExtraction;general;vtkFiltersSources; //Dependencies for the target vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingCorePythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkRenderingCore;general;vtkCommonComputationalGeometry;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingColor;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume; //Dependencies for the target vtkNetCDF_LIB_DEPENDS:STATIC=general;hdf5;general;hdf5;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;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkIOLegacyPythonD;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;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.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;vtkRenderingVolumeOpenGL2PythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;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;vtkRenderingVolumeOpenGL2;general;vtkViewsContext2D;general;vtkViewsCore;general;vtksys;general;/root/postlabs/build/install/lib/libz.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkDomainsChemistryOpenGL2PythonD;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;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;vtkIOTecplotTablePythonD;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;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;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;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkCommonColorCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkInteractionStyleCS;general;vtkIOImageCS;general;vtkRenderingOpenGL2CS;general;vtkFiltersModelingCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkParallelMPICS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkIOXMLCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkDomainsChemistryCS;general;vtkFiltersAMRCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkIOMPIImageCS;general;vtkIOPLYCS;general;vtkIOGeometryCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingColorCS;general;vtkImagingGeneralCS;general;vtkImagingHybridCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelMPICS;general;vtkRenderingGL2PSOpenGL2CS;general;vtkIOExportCS;general;vtkIOExportOpenGL2CS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkImagingMathCS;general;vtkRenderingVolumeOpenGL2CS;general;vtkRenderingVolumeAMRCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingLabelCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkDomainsChemistryOpenGL2CS;general;vtkFiltersParallelDIY2CS;general;vtkFiltersParallelGeometryCS;general;vtkFiltersImagingCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOMPIParallelCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOTecplotTableCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;general;vtkFiltersPointsCS;general;vtkPVVTKExtensionsPointsCS;general;vtkParallelMPI4PyCS;general;vtkRenderingLICOpenGL2CS;general;vtkRenderingLODCS;general;vtkRenderingParallelLICCS;general;vtkRenderingContextOpenGL2CS;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;vtkRenderingVolumeOpenGL2PythonD;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;vtkRenderingVolumeOpenGL2;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;vtkFiltersExtractionPythonD;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;vtkFiltersExtraction;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;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOExportOpenGL2PythonD;general;vtkIOImagePythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;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;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkGUISupportQt;general;vtkIOExport;general;vtkIOExportOpenGL2;general;vtkIOImage;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL2;general;vtkRenderingParallel;general;vtkRenderingVolumeAMR;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkglew;general;/root/postlabs/build/install/lib/libz.so;general;vtklz4;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkParaViewDocumentation_LIB_DEPENDS:STATIC=general;Qt4::QtGui; //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;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonDataModel;general;vtkCommonSystem;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;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD; //Dependencies for the target vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/root/postlabs/build/install/lib/libpython2.7.so;general;vtkParallelMPI;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelCore;general;vtkCommonDataModel;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.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;/root/postlabs/build/install/lib/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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD; //Dependencies for the target vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkImagingColor;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContextOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL2PythonD; //Dependencies for the target vtkRenderingContextOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingContext2D;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkImagingCore;general;vtkglew;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.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;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkCommonColor;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersSources;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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingCore;general;/root/postlabs/build/install/lib/libfreetype.so;general;vtkCommonDataModel;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingGL2PSOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSOpenGL2PythonD; //Dependencies for the target vtkRenderingGL2PSOpenGL2_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2;general;vtkRenderingOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkgl2ps;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingLICOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingLICOpenGL2PythonD; //Dependencies for the target vtkRenderingLICOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtkglew;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;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;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersModeling; //Dependencies for the target vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD; //Dependencies for the target vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD; //Dependencies for the target vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkRenderingFreeType;general;vtkRenderingFreeType;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkImagingCore;general;/root/postlabs/build/install/lib/libpython2.7.so;general;vtkRenderingCore;general;vtkWrappingPythonCore; //Dependencies for the target vtkRenderingOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2PythonD; //Dependencies for the target vtkRenderingOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOImage;general;vtkImagingCore;general;vtkglew;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/usr/lib64/libSM.so;general;/usr/lib64/libICE.so;general;/usr/lib64/libX11.so;general;/usr/lib64/libXext.so;general;/usr/lib64/libXt.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;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD; //Dependencies for the target vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkRenderingLICOpenGL2;general;vtkRenderingOpenGL2;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;/root/postlabs/build/install/lib/libmpi.so;general;/root/postlabs/build/install/lib/libmpicxx.so;general;/root/postlabs/build/install/lib/libmpi.so; //Dependencies for the target vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD; //Dependencies for the target vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkglew;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersParallel;general;vtkIOImage;general;vtkImagingCore;general;vtkParallelCore;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD; //Dependencies for the target vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingVolume;general;vtkRenderingVolumeOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkRenderingCore; //Dependencies for the target vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumeOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingCorePythonD;general;vtkImagingMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL2PythonD; //Dependencies for the target vtkRenderingVolumeOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkImagingMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingVolume;general;vtkRenderingVolume;general;vtkglew;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for the target vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOXMLPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOXML;general;vtkImagingCore; //Dependencies for the target vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;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;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOImage;general;vtkImagingCore;general;vtksys; //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;vtkCommonCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCorePythonD;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD; //Dependencies for the target vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkViewsCore;general;vtkRenderingContext2D; //Dependencies for the target vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;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;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkInteractionWidgets;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingCore; //Dependencies for the target vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/root/postlabs/build/install/lib/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 vtkgl2ps_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libz.so;general;/root/postlabs/build/install/lib/libpng.so;general;/root/postlabs/build/install/lib/libz.so;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;m; //Dependencies for the target vtkglew_LIB_DEPENDS:STATIC=general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so; //Dependencies for target vtkjpeg_LIB_DEPENDS:STATIC= //Dependencies for target vtkjsoncpp_LIB_DEPENDS:STATIC= //Dependencies for target vtklz4_LIB_DEPENDS:STATIC= //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libz.so; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for target vtkoggtheora_LIB_DEPENDS:STATIC= //Dependencies for target vtkpugixml_LIB_DEPENDS:STATIC= //Value Computed by CMake vtksys_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtksys_LIB_DEPENDS:STATIC=general;dl;general;dl; //Value Computed by CMake vtksys_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtktiff_LIB_DEPENDS:STATIC=general;/usr/lib64/libm.so;general;/root/postlabs/build/install/lib/libz.so;general;vtkjpeg; //Dependencies for the target vtkxdmf2_LIB_DEPENDS:STATIC=general;/root/postlabs/build/install/lib/libxml2.so;general;hdf5;general;hdf5; //Value Computed by CMake xdmf2_BINARY_DIR:STATIC=/root/postlabs/build/superbuild/paraview/build/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/root/postlabs/build/superbuild/paraview/src/VTK/ThirdParty/xdmf2/vtkxdmf2 ######################## # INTERNAL cache entries ######################## ALGLIB_SHARED_LIB:INTERNAL=ON //Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN ARCH_TO_BUILD:INTERNAL=Linux //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=/root/postlabs/build/superbuild/paraview/build //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=8 //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=/root/cmake/cmake-3.8.0-rc1-Linux-x86_64/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/root/cmake/cmake-3.8.0-rc1-Linux-x86_64/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/root/cmake/cmake-3.8.0-rc1-Linux-x86_64/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=/root/cmake/cmake-3.8.0-rc1-Linux-x86_64/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 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_DEBUG CMAKE_Fortran_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_MINSIZEREL CMAKE_Fortran_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELEASE CMAKE_Fortran_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELWITHDEBINFO CMAKE_Fortran_FLAGS_RELWITHDEBINFO-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 function connect CMAKE_HAVE_CONNECT:INTERNAL=1 //Have function gethostbyname CMAKE_HAVE_GETHOSTBYNAME:INTERNAL=1 //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 //Have function remove CMAKE_HAVE_REMOVE:INTERNAL=1 //Have function shmat CMAKE_HAVE_SHMAT:INTERNAL=1 //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/root/postlabs/build/superbuild/paraview/src //ADVANCED property for variable: CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATADIR CMAKE_INSTALL_DATADIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATAROOTDIR CMAKE_INSTALL_DATAROOTDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DOCDIR CMAKE_INSTALL_DOCDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INCLUDEDIR CMAKE_INSTALL_INCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INFODIR CMAKE_INSTALL_INFODIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LIBDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBEXECDIR CMAKE_INSTALL_LIBEXECDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALEDIR CMAKE_INSTALL_LOCALEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_LOCALSTATEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_MANDIR CMAKE_INSTALL_MANDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_OLDINCLUDEDIR CMAKE_INSTALL_OLDINCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SBINDIR CMAKE_INSTALL_SBINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SHAREDSTATEDIR CMAKE_INSTALL_SHAREDSTATEDIR-ADVANCED:INTERNAL=1 //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0 //ADVANCED property for variable: CMAKE_INSTALL_SYSCONFDIR CMAKE_INSTALL_SYSCONFDIR-ADVANCED:INTERNAL=1 //Have library ICE CMAKE_LIB_ICE_HAS_ICECONNECTIONNUMBER: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 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=228 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //Platform information initialized CMAKE_PLATFORM_INFO_INITIALIZED: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=/root/cmake/cmake-3.8.0-rc1-Linux-x86_64/share/cmake-3.8 //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 //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=/usr/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 //Test C_FLAG_W C_FLAG_W:INTERNAL=1 //Test C_FLAG_Wall C_FLAG_Wall:INTERNAL=1 //Test C_FLAG_Wdeclaration_after_statement C_FLAG_Wdeclaration_after_statement:INTERNAL=1 //Test C_FLAG_Wdisabled_optimization C_FLAG_Wdisabled_optimization:INTERNAL=1 //Test C_FLAG_Wformat_security C_FLAG_Wformat_security:INTERNAL=1 //Test C_FLAG_Winline C_FLAG_Winline:INTERNAL=1 //Test C_FLAG_Wno_unknown_pragmas C_FLAG_Wno_unknown_pragmas:INTERNAL=1 //Test C_FLAG_Wpointer_arith C_FLAG_Wpointer_arith:INTERNAL=1 //Test C_FLAG_fstrict_aliasing C_FLAG_fstrict_aliasing:INTERNAL=1 //Test C_HAS_inline C_HAS_inline:INTERNAL=1 //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=/root/postlabs/build/superbuild/paraview/build/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: ExternalData_URL_TEMPLATES ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1 //Details about finding Freetype FIND_PACKAGE_MESSAGE_DETAILS_Freetype:INTERNAL=[/root/postlabs/build/install/lib/libfreetype.so][/root/postlabs/build/install/include;/root/postlabs/build/install/include/freetype2][v2.4.8()] //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v1.8.3.1()] //Details about finding HDF5 FIND_PACKAGE_MESSAGE_DETAILS_HDF5:INTERNAL=[hdf5][/root/postlabs/build/install/include][cfound components: C HL ][v1.8.13()] //Details about finding LibXml2 FIND_PACKAGE_MESSAGE_DETAILS_LibXml2:INTERNAL=[/root/postlabs/build/install/lib/libxml2.so][/root/postlabs/build/install/include/libxml2][v2.7.8()] //Details about finding MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/root/postlabs/build/install/lib/libmpi.so][/root/postlabs/build/install/include][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/root/postlabs/build/install/lib/libmpicxx.so;/root/postlabs/build/install/lib/libmpi.so][/root/postlabs/build/install/include][v()] //Details about finding MPI_Fortran FIND_PACKAGE_MESSAGE_DETAILS_MPI_Fortran:INTERNAL=[/usr/lib64/openmpi/lib/libmpi_usempi.so;/usr/lib64/openmpi/lib/libmpi_mpifh.so;/root/postlabs/build/install/lib/libmpi.so][/usr/lib64/openmpi/lib][v()] //Details about finding OpenGL FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/usr/lib64/libGL.so][/usr/include][v()] //Details about finding PNG FIND_PACKAGE_MESSAGE_DETAILS_PNG:INTERNAL=[/root/postlabs/build/install/lib/libpng.so][/root/postlabs/build/install/include][v1.6.23()] //Details about finding PythonInterp FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/root/postlabs/build/install/bin/python2.7][v2.7.11()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/root/postlabs/build/install/lib/libpython2.7.so][/root/postlabs/build/install/include/python2.7][v()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/root/postlabs/build/install/bin/qmake][/root/postlabs/build/install/bin/moc][/root/postlabs/build/install/bin/rcc][/root/postlabs/build/install/include][/root/postlabs/build/install/lib][/root/postlabs/build/install/include/QtGui][/root/postlabs/build/install/lib/libQtGui.so][/root/postlabs/build/install/bin/uic][v4.8.6(4.7)] //Details about finding Threads FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()] //Details about finding X11 FIND_PACKAGE_MESSAGE_DETAILS_X11:INTERNAL=[/usr/lib64/libX11.so][/usr/include] //Details about finding ZLIB FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/root/postlabs/build/install/lib/libz.so][/root/postlabs/build/install/include][v1.2.7()] //ADVANCED property for variable: FREETYPE_INCLUDE_DIR_freetype2 FREETYPE_INCLUDE_DIR_freetype2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_INCLUDE_DIR_ft2build FREETYPE_INCLUDE_DIR_ft2build-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_LIBRARY_DEBUG FREETYPE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_LIBRARY_RELEASE FREETYPE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //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 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 include assert.h HAVE_ASSERT_H:INTERNAL=1 //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 dlfcn.h HAVE_DLFCN_H:INTERNAL=1 //Have include fcntl.h HAVE_FCNTL_H:INTERNAL=1 //Have include fenv.h HAVE_FENV_H:INTERNAL=1 //Have function floor HAVE_FLOOR:INTERNAL=1 //NetCDF test HAVE_FTRUNCATE:INTERNAL=1 //Test HAVE_GCC_ERROR_RETURN_TYPE HAVE_GCC_ERROR_RETURN_TYPE:INTERNAL=1 //Have function getopt HAVE_GETOPT:INTERNAL=1 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 //ADVANCED property for variable: HAVE_IEEEFP HAVE_IEEEFP-ADVANCED:INTERNAL=1 //Have include inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have include io.h HAVE_IO_H:INTERNAL= //Have function isascii HAVE_ISASCII:INTERNAL=1 //Have function jbg_newlen HAVE_JBG_NEWLEN:INTERNAL= //Test HAVE_LD_VERSION_SCRIPT HAVE_LD_VERSION_SCRIPT:INTERNAL=1 //Have function lfind HAVE_LFIND:INTERNAL=1 //Have include limits.h HAVE_LIMITS_H:INTERNAL=1 //Have include malloc.h HAVE_MALLOC_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 function pow HAVE_POW:INTERNAL=1 //Have include search.h HAVE_SEARCH_H:INTERNAL=1 //Have function setmode HAVE_SETMODE:INTERNAL= //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_SIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_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_UNSIGNED_CHAR_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF__BOOL:INTERNAL=TRUE //Test HAVE_SNPRINTF HAVE_SNPRINTF:INTERNAL=1 //Have function sqrt HAVE_SQRT: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 stdlib.h HAVE_STDLIB_H:INTERNAL=1 //Have function strcasecmp HAVE_STRCASECMP:INTERNAL=1 //Have function strchr HAVE_STRCHR:INTERNAL=1 //Have symbol strerror HAVE_STRERROR:INTERNAL=1 //Have include strings.h HAVE_STRINGS_H:INTERNAL=1 //Have include string.h HAVE_STRING_H: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 strtol HAVE_STRTOUL:INTERNAL=1 //Have function strtoull HAVE_STRTOULL:INTERNAL=1 //NetCDF test HAVE_ST_BLKSIZE:INTERNAL=1 //Have include sys/stat.h HAVE_SYS_STAT_H:INTERNAL=1 //Have include sys/time.h HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/types.h HAVE_SYS_TYPES_H:INTERNAL=1 //Have include unistd.h HAVE_UNISTD_H: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 //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 //Result of TRY_COMPILE HAVE_bigendian:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_int16:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int32:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int8:INTERNAL=FALSE //ADVANCED property for variable: HDF5_C_HL_LIBRARY HDF5_C_HL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_C_LIBRARY HDF5_C_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_DIFF_EXECUTABLE HDF5_DIFF_EXECUTABLE-ADVANCED:INTERNAL=1 //Have symbol H5_HAVE_PARALLEL HDF5_IS_PARALLEL:INTERNAL= //ADVANCED property for variable: HOST_BIG_ENDIAN HOST_BIG_ENDIAN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HOST_FILLORDER HOST_FILLORDER-ADVANCED:INTERNAL=1 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 //This is set from VTK_MPIRUN_EXE. ICET_MPIRUN_EXE:INTERNAL=/root/postlabs/build/install/bin/mpiexec //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=2 //This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and // VTK_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np //This is set from VTK_MPI_POSTFLAGS. ICET_MPI_POSTFLAGS:INTERNAL= //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= //ADVANCED property for variable: ICET_USE_OPENGL ICET_USE_OPENGL-ADVANCED:INTERNAL=1 //Use OffScreen Mesa ICET_USE_OSMESA:INTERNAL= //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_EXT_STDIO_FILEBUF_H_COMPILED:INTERNAL=TRUE //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=/root/postlabs/build/superbuild/paraview/build/ThirdParty/protobuf/vtkprotobuf/bin //ADVANCED property for variable: LIBXML2_INCLUDE_DIR LIBXML2_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: LIBXML2_LIBRARIES LIBXML2_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: LIBXML2_XMLLINT_EXECUTABLE LIBXML2_XMLLINT_EXECUTABLE-ADVANCED:INTERNAL=1 //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 //ADVANCED property for variable: MPI_Fortran_COMPILER MPI_Fortran_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_COMPILE_FLAGS MPI_Fortran_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_INCLUDE_PATH MPI_Fortran_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LIBRARIES MPI_Fortran_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LINK_FLAGS MPI_Fortran_LINK_FLAGS-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: M_LIBRARY M_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_AutobahnPython Module_AutobahnPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_PoissonReconstruction Module_PoissonReconstruction-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_Pygments Module_Pygments-ADVANCED:INTERNAL=1 //Request building Pygments Module_Pygments:INTERNAL=OFF //ADVANCED property for variable: Module_SixPython Module_SixPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_Twisted Module_Twisted-ADVANCED:INTERNAL=1 //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 //ADVANCED property for variable: Module_pqApplicationComponents Module_pqApplicationComponents-ADVANCED:INTERNAL=1 //Request building pqApplicationComponents Module_pqApplicationComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqComponents Module_pqComponents-ADVANCED:INTERNAL=1 //Request building pqComponents Module_pqComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqCore Module_pqCore-ADVANCED:INTERNAL=1 //Request building pqCore Module_pqCore:INTERNAL=OFF //ADVANCED property for variable: Module_pqDeprecated Module_pqDeprecated-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqPython Module_pqPython-ADVANCED:INTERNAL=1 //Request building pqPython Module_pqPython:INTERNAL=OFF //ADVANCED property for variable: Module_pqWidgets Module_pqWidgets-ADVANCED:INTERNAL=1 //Request building pqWidgets Module_pqWidgets:INTERNAL=OFF //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 //Request building vtkGUISupportQt Module_vtkGUISupportQt:INTERNAL=OFF //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_vtkIOTRUCHAS Module_vtkIOTRUCHAS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOTecplotTable Module_vtkIOTecplotTable-ADVANCED:INTERNAL=1 //Request building vtkIOTecplotTable Module_vtkIOTecplotTable:INTERNAL=OFF //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 //Request building vtkImagingMath Module_vtkImagingMath:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingMorphological Module_vtkImagingMorphological-ADVANCED:INTERNAL=1 //Request building vtkImagingMorphological Module_vtkImagingMorphological:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingOpenGL2 Module_vtkImagingOpenGL2-ADVANCED:INTERNAL=1 //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_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 //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_vtkRenderingOculus Module_vtkRenderingOculus-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_vtkRenderingOpenVR Module_vtkRenderingOpenVR-ADVANCED:INTERNAL=1 //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 //Request building vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON:INTERNAL=OFF //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_vtkWebCore Module_vtkWebCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebGLExporter Module_vtkWebGLExporter-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebPython Module_vtkWebPython-ADVANCED:INTERNAL=1 //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 //Request building vtkglew Module_vtkglew:INTERNAL=OFF //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 //Request building vtkqttesting Module_vtkqttesting:INTERNAL=OFF //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 //ADVANCED property for variable: OPENGL_INCLUDE_DIR OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_gl_LIBRARY OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_glu_LIBRARY OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OPENGL_xmesa_INCLUDE_DIR OPENGL_xmesa_INCLUDE_DIR-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_CatalystScriptGeneratorPlugin PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin-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_SLACTools PARAVIEW_AUTOLOAD_PLUGIN_SLACTools-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_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_CatalystScriptGeneratorPlugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin-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_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_PythonQtPlugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-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_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_TemporalParallelismScriptGenerator PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-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_VRPlugin PARAVIEW_BUILD_PLUGIN_VRPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1 //List of modules to CS wrap PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkCommonColor;vtkFiltersGeometry;vtkRenderingCore;vtkInteractionStyle;vtkIOImage;vtkRenderingOpenGL2;vtkFiltersModeling;vtkIOCore;vtkIOLegacy;vtkParallelCore;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkPVVTKExtensionsCore;vtkParallelMPI;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkIOXML;vtkInfovisCore;vtkIOInfovis;vtkDomainsChemistry;vtkFiltersAMR;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkFiltersFlowPaths;vtkFiltersParallelFlowPaths;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkIOMPIImage;vtkIOPLY;vtkIOGeometry;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingColor;vtkImagingGeneral;vtkImagingHybrid;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkFiltersGeneric;vtkFiltersHyperTree;vtkFiltersParallelMPI;vtkRenderingGL2PSOpenGL2;vtkIOExport;vtkIOExportOpenGL2;vtkRenderingMatplotlib;vtkRenderingParallel;vtkImagingMath;vtkRenderingVolumeOpenGL2;vtkRenderingVolumeAMR;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingLabel;vtkViewsCore;vtkViewsContext2D;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkDomainsChemistryOpenGL2;vtkFiltersParallelDIY2;vtkFiltersParallelGeometry;vtkFiltersImaging;vtkFiltersParallelImaging;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOMPIParallel;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOTecplotTable;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkFiltersPoints;vtkPVVTKExtensionsPoints;vtkParallelMPI4Py;vtkRenderingLICOpenGL2;vtkRenderingLOD;vtkRenderingParallelLIC;vtkPVServerManagerApplication;vtkPVCatalyst;vtkRenderingContextOpenGL2 //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_EMBEDDED_DOCUMENTATION PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_MATPLOTLIB PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1 //Build ParaView with Qt support (without GUI) PARAVIEW_ENABLE_QT_SUPPORT:INTERNAL=ON //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_MODULE_ROOTS PARAVIEW_EXTERNAL_MODULE_ROOTS-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 //STRINGS property for variable: PARAVIEW_QT_VERSION PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5 //Server Manager XMLs PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/Default/settings.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/Animation/animation.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/VTKExtensions/Points/points.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/proxies_mpi.xml;/root/postlabs/build/superbuild/paraview/src/ParaViewCore/ServerManager/SMApplication/Resources/proxies_opengl2.xml;/root/postlabs/build/superbuild/paraview/src/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_QTHELP PARAVIEW_USE_QTHELP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_QTWEBKIT PARAVIEW_USE_QTWEBKIT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_UNIFIED_BINDINGS PARAVIEW_USE_UNIFIED_BINDINGS-ADVANCED:INTERNAL=1 PC_LIBXML_CFLAGS:INTERNAL=-I/root/postlabs/build/install/include/libxml2 PC_LIBXML_CFLAGS_I:INTERNAL= PC_LIBXML_CFLAGS_OTHER:INTERNAL= PC_LIBXML_FOUND:INTERNAL=1 PC_LIBXML_INCLUDEDIR:INTERNAL=/root/postlabs/build/install/include PC_LIBXML_INCLUDE_DIRS:INTERNAL=/root/postlabs/build/install/include/libxml2 PC_LIBXML_LDFLAGS:INTERNAL=-L/root/postlabs/build/install/lib;-lxml2 PC_LIBXML_LDFLAGS_OTHER:INTERNAL= PC_LIBXML_LIBDIR:INTERNAL=/root/postlabs/build/install/lib PC_LIBXML_LIBRARIES:INTERNAL=xml2 PC_LIBXML_LIBRARY_DIRS:INTERNAL=/root/postlabs/build/install/lib PC_LIBXML_LIBS:INTERNAL= PC_LIBXML_LIBS_L:INTERNAL= PC_LIBXML_LIBS_OTHER:INTERNAL= PC_LIBXML_LIBS_PATHS:INTERNAL= PC_LIBXML_PREFIX:INTERNAL=/root/postlabs/build/install PC_LIBXML_STATIC_CFLAGS:INTERNAL=-I/root/postlabs/build/install/include/libxml2 PC_LIBXML_STATIC_CFLAGS_I:INTERNAL= PC_LIBXML_STATIC_CFLAGS_OTHER:INTERNAL= PC_LIBXML_STATIC_INCLUDE_DIRS:INTERNAL=/root/postlabs/build/install/include/libxml2 PC_LIBXML_STATIC_LDFLAGS:INTERNAL=-L/root/postlabs/build/install/lib;-lxml2;-lz;-lm PC_LIBXML_STATIC_LDFLAGS_OTHER:INTERNAL= PC_LIBXML_STATIC_LIBDIR:INTERNAL= PC_LIBXML_STATIC_LIBRARIES:INTERNAL=xml2;z;m PC_LIBXML_STATIC_LIBRARY_DIRS:INTERNAL=/root/postlabs/build/install/lib PC_LIBXML_STATIC_LIBS:INTERNAL= PC_LIBXML_STATIC_LIBS_L:INTERNAL= PC_LIBXML_STATIC_LIBS_OTHER:INTERNAL= PC_LIBXML_STATIC_LIBS_PATHS:INTERNAL= PC_LIBXML_VERSION:INTERNAL=2.7.8 PC_LIBXML_libxml-2.0_INCLUDEDIR:INTERNAL= PC_LIBXML_libxml-2.0_LIBDIR:INTERNAL= PC_LIBXML_libxml-2.0_PREFIX:INTERNAL= PC_LIBXML_libxml-2.0_VERSION:INTERNAL= //ADVANCED property for variable: PKG_CONFIG_EXECUTABLE PKG_CONFIG_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PNG_LIBRARY_DEBUG PNG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PNG_LIBRARY_RELEASE PNG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PNG_PNG_INCLUDE_DIR PNG_PNG_INCLUDE_DIR-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 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_BINARY_DIR:INTERNAL=/root/postlabs/build/install/bin //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DESIGNER_EXECUTABLE QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DOC_DIR QT_DOC_DIR-ADVANCED:INTERNAL=1 QT_HEADERS_DIR:INTERNAL=/root/postlabs/build/install/include //ADVANCED property for variable: QT_HELP_GENERATOR QT_HELP_GENERATOR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_IMPORTS_DIR QT_IMPORTS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LIBRARY_DIR QT_LIBRARY_DIR-ADVANCED:INTERNAL=1 //Qt library dir QT_LIBRARY_DIR:INTERNAL=/root/postlabs/build/install/lib //ADVANCED property for variable: QT_LINGUIST_EXECUTABLE QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LRELEASE_EXECUTABLE QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LUPDATE_EXECUTABLE QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MKSPECS_DIR QT_MKSPECS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MOC_EXECUTABLE QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_INCLUDE_DIR QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PLUGINS_DIR QT_PLUGINS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMAKE_EXECUTABLE QT_QMAKE_EXECUTABLE-ADVANCED:INTERNAL=1 QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/root/postlabs/build/install/bin/qmake //ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_INCLUDE_DIR QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_DEBUG QT_QTMOTIF_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_RELEASE QT_QTMOTIF_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_INCLUDE_DIR QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_RCC_EXECUTABLE QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TESTING_EVENT_PLAYBACK_DELAY QT_TESTING_EVENT_PLAYBACK_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TRANSLATIONS_DIR QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC3_EXECUTABLE QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC_EXECUTABLE QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_XMLPATTERNS_EXECUTABLE QT_XMLPATTERNS_EXECUTABLE-ADVANCED:INTERNAL=1 //Have symbol Q_WS_MAC Q_WS_MAC:INTERNAL= //Have symbol Q_WS_QWS Q_WS_QWS:INTERNAL= //Have symbol Q_WS_WIN Q_WS_WIN:INTERNAL= //Have symbol Q_WS_X11 Q_WS_X11: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(signed int) SIZEOF_SIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(signed long) SIZEOF_SIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed long long) SIZEOF_SIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed short) SIZEOF_SIGNED_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(unsigned char *) SIZEOF_UNSIGNED_CHAR_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned int) SIZEOF_UNSIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(unsigned long) SIZEOF_UNSIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned long long) SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned short) SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void *) SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(_Bool) SIZEOF__BOOL:INTERNAL=1 //Have include stdlib.h;stdarg.h;string.h;float.h STDC_HEADERS:INTERNAL=1 //Result of TRY_COMPILE SUCCEED:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_MAP:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_SET:INTERNAL=TRUE //ADVANCED property for variable: SURFACELIC_PLUGIN_TESTING SURFACELIC_PLUGIN_TESTING-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_INCLUDE_DIR TBB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY_DEBUG TBB_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY_RELEASE TBB_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_INCLUDE_DIR TBB_MALLOC_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_LIBRARY TBB_MALLOC_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_LIBRARY_DEBUG TBB_MALLOC_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_LIBRARY_RELEASE TBB_MALLOC_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_PROXY_INCLUDE_DIR TBB_MALLOC_PROXY_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_PROXY_LIBRARY_DEBUG TBB_MALLOC_PROXY_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_MALLOC_PROXY_LIBRARY_RELEASE TBB_MALLOC_PROXY_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //Test TIME_WITH_SYS_TIME TIME_WITH_SYS_TIME:INTERNAL=1 //Test TM_IN_SYS_TIME TM_IN_SYS_TIME:INTERNAL=1 //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= VTKFREETYPE_BINARY_DIR:INTERNAL=/root/postlabs/build/superbuild/paraview/build/VTK/Utilities/freetype VTKFREETYPE_SOURCE_DIR:INTERNAL=/root/postlabs/build/superbuild/paraview/src/VTK/Utilities/freetype VTKFTGL_BINARY_DIR:INTERNAL=/root/postlabs/build/superbuild/paraview/build/VTK/Utilities/ftgl VTKFTGL_SOURCE_DIR:INTERNAL=/root/postlabs/build/superbuild/paraview/src/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=/root/postlabs/build/superbuild/paraview/build/lib/site-packages //ADVANCED property for variable: VTK_BUILD_QT_DESIGNER_PLUGIN VTK_BUILD_QT_DESIGNER_PLUGIN-ADVANCED:INTERNAL=1 //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_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 //Directory where python modules will be installed VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-5.2/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_MPIRUN_EXE VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_POSTFLAGS VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PREFLAGS VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS VTK_MPI_PRENUMPROC_FLAGS-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 //STRINGS property for variable: VTK_QT_VERSION VTK_QT_VERSION-STRINGS:INTERNAL=4;5 VTK_QT_VERSION:INTERNAL=4 //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 //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_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_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_PYGMENTS VTK_USE_SYSTEM_PYGMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_QTTESTING VTK_USE_SYSTEM_QTTESTING-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_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_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_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=TRUE //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: X11_ICE_INCLUDE_PATH X11_ICE_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_ICE_LIB X11_ICE_LIB-ADVANCED:INTERNAL=1 //Have library /usr/lib64/libX11.so;/usr/lib64/libXext.so X11_LIB_X11_SOLO:INTERNAL=1 //ADVANCED property for variable: X11_SM_INCLUDE_PATH X11_SM_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_SM_LIB X11_SM_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_X11_INCLUDE_PATH X11_X11_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_X11_LIB X11_X11_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XRes_INCLUDE_PATH X11_XRes_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XRes_LIB X11_XRes_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XShm_INCLUDE_PATH X11_XShm_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XSync_INCLUDE_PATH X11_XSync_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XTest_INCLUDE_PATH X11_XTest_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_XTest_LIB X11_XTest_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xaccessrules_INCLUDE_PATH X11_Xaccessrules_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xaccessstr_INCLUDE_PATH X11_Xaccessstr_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xau_INCLUDE_PATH X11_Xau_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xau_LIB X11_Xau_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcomposite_INCLUDE_PATH X11_Xcomposite_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcomposite_LIB X11_Xcomposite_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcursor_INCLUDE_PATH X11_Xcursor_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xcursor_LIB X11_Xcursor_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdamage_INCLUDE_PATH X11_Xdamage_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdamage_LIB X11_Xdamage_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdmcp_INCLUDE_PATH X11_Xdmcp_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xdmcp_LIB X11_Xdmcp_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xext_LIB X11_Xext_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xfixes_INCLUDE_PATH X11_Xfixes_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xfixes_LIB X11_Xfixes_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xft_INCLUDE_PATH X11_Xft_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xft_LIB X11_Xft_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xi_INCLUDE_PATH X11_Xi_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xi_LIB X11_Xi_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinerama_INCLUDE_PATH X11_Xinerama_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinerama_LIB X11_Xinerama_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinput_INCLUDE_PATH X11_Xinput_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xinput_LIB X11_Xinput_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkb_INCLUDE_PATH X11_Xkb_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkbfile_INCLUDE_PATH X11_Xkbfile_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkbfile_LIB X11_Xkbfile_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xkblib_INCLUDE_PATH X11_Xkblib_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xlib_INCLUDE_PATH X11_Xlib_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xmu_INCLUDE_PATH X11_Xmu_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xmu_LIB X11_Xmu_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xpm_INCLUDE_PATH X11_Xpm_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xpm_LIB X11_Xpm_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrandr_INCLUDE_PATH X11_Xrandr_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrandr_LIB X11_Xrandr_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrender_INCLUDE_PATH X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xrender_LIB X11_Xrender_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xscreensaver_LIB X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xshape_INCLUDE_PATH X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xt_INCLUDE_PATH X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xt_LIB X11_Xt_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xutil_INCLUDE_PATH X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xv_INCLUDE_PATH X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xv_LIB X11_Xv_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xxf86misc_LIB X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_Xxf86vm_LIB X11_Xxf86vm_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_dpms_INCLUDE_PATH X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH X11_xf86vmode_INCLUDE_PATH-ADVANCED: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 //ADVANCED property for variable: ZLIB_INCLUDE_DIR ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY_DEBUG ZLIB_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY_RELEASE ZLIB_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //CMAKE_INSTALL_PREFIX during last run _GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/root/postlabs/build/install //ParaView has been configured __paraview_configured:INTERNAL=TRUE __pkg_config_arguments_PC_LIBXML:INTERNAL=QUIET;libxml-2.0 __pkg_config_checked_PC_LIBXML:INTERNAL=1 //Result of TEST_BIG_ENDIAN bigendian:INTERNAL=0 //CHECK_TYPE_SIZE: INT16 unknown int16:INTERNAL= //CHECK_TYPE_SIZE: INT32 unknown int32:INTERNAL= //CHECK_TYPE_SIZE: INT8 unknown int8:INTERNAL= prefix_result:INTERNAL=/root/postlabs/build/install/lib protobut_determine_hash_namespace_done:INTERNAL=TRUE protobut_pthread_test_done:INTERNAL=TRUE pthread_test_result:INTERNAL=PTHREAD_CREATE_JOINABLE From st.vater at web.de Wed Feb 22 06:33:53 2017 From: st.vater at web.de (Stefan Vater) Date: Wed, 22 Feb 2017 12:33:53 +0100 Subject: [Paraview] problems with packaging of superbuild In-Reply-To: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> References: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> Message-ID: <1754789.rsqZdryCgt@saintvenant.zmaw.de> Hi, it seems that these errors resulted from the fact, that I set an absolute install path. However, now I have the problem that the packaging fails to find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At least this is my guess. The error message is: [...] 1: CPack: Install projects 1: CPack: - Run preinstall target for: cpack-paraview 1: CPack: - Install project: cpack-paraview 1: CPack Verbose: Install configuration: "Release" 1: CMake Error at /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake:45 (message): 1: Failed to install pvdataserver: 1: 1: Traceback (most recent call last): 1: 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 504, in 1: main(sys.argv[1:]) 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 496, in main 1: _install_binary(main_exe, is_excluded, bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 400, in _install_binary 1: deps = binary.dependencies.values() 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 197, in dependencies 1: deplib = Library.create_from_reference(dep, self) 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 258, in create_from_reference 1: paths.extend(cls.default_search_paths()) 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 230, in default_search_paths 1: cls.__search_cache = pipe().split('\n') 1: File "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py", line 22, in __call__ 1: command = subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1: File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1: errread, errwrite) 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child 1: raise child_exception 1: 1: OSError: [Errno 2] No such file or directory 1: 1: 1: 1: CPack Error: Error when generating package: ParaView 1: CMake Error at /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake:21 (message): 1: CPack failed with exit code 1 1: 1: 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.10 sec Any suggestions? Stefan From st.vater at web.de Wed Feb 22 08:04:02 2017 From: st.vater at web.de (Stefan Vater) Date: Wed, 22 Feb 2017 14:04:02 +0100 Subject: [Paraview] problems with packaging of superbuild In-Reply-To: <1754789.rsqZdryCgt@saintvenant.zmaw.de> References: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> <1754789.rsqZdryCgt@saintvenant.zmaw.de> Message-ID: <2215131.DiXl1TVbhV@saintvenant.zmaw.de> Once again... so the old two problems seem to still exist. I made some changes in the camke files to circumvent them, but forgot that they are still there. Stefan Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater: > Hi, > > it seems that these errors resulted from the fact, that I set an absolute > install path. However, now I have the problem that the packaging fails to > find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At > least this is my guess. The error message is: > > [...] > 1: CPack: Install projects > 1: CPack: - Run preinstall target for: cpack-paraview > 1: CPack: - Install project: cpack-paraview > 1: CPack Verbose: Install configuration: "Release" > 1: CMake Error at > /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake: > 45 (message): 1: Failed to install pvdataserver: > 1: > 1: Traceback (most recent call last): > 1: > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 504, in 1: main(sys.argv[1:]) > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 496, in main 1: _install_binary(main_exe, is_excluded, > bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1: > File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 400, in _install_binary 1: deps = > binary.dependencies.values() > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 197, in dependencies 1: deplib = > Library.create_from_reference(dep, self) > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 258, in create_from_reference 1: > paths.extend(cls.default_search_paths()) > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 230, in default_search_paths 1: cls.__search_cache = > pipe().split('\n') > 1: File > "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u > nix.py", line 22, in __call__ 1: command = > subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1: > File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1: > errread, errwrite) > 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child > 1: raise child_exception > 1: > 1: OSError: [Errno 2] No such file or directory > 1: > 1: > 1: > 1: CPack Error: Error when generating package: ParaView > 1: CMake Error at > /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm > ake:21 (message): 1: CPack failed with exit code 1 > 1: > 1: > 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.10 sec > > Any suggestions? > > Stefan > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 -- Stefan Vater Research group "Numerical Methods in Geosciences" CEN - Center for Earth System Research and Sustainability Universit?t Hamburg Grindelberg 5, D-20144 Hamburg, Germany Phone: +49 - 40 - 42838 7746 Fax: +49 - 40 - 42838 7712 Email: stefan.vater at uni-hamburg.de URL: http://www.clisap.de/vater From robertsawko at gmail.com Wed Feb 22 08:12:30 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Wed, 22 Feb 2017 14:12:30 +0100 Subject: [Paraview] Paraview closes with a core dump Message-ID: <20170222131230.GA6970@avignon> Hi, This is Arch Linux user again. Parview no longer opens for me. It just ends with a core dump (attached). It seems it's something to do with Arch Linux forward looking policy of favouring QT5. I have specified in the compilation to build with QT4 (see attached CMakeCache.txt), but on run it still picks libQt5Core.so. I will now try to rebuild with QT5 but there was a perspective issue with that before. Does anyone have any suggestions, please? Thanks, Robert -- Tropics in Cornwall: http://en.wikipedia.org/wiki/Eden_Project -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview_core_dump.tar.gz Type: application/octet-stream Size: 49509 bytes Desc: not available URL: From richard.c.angelini.civ at mail.mil Wed Feb 22 08:10:04 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Wed, 22 Feb 2017 13:10:04 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: Cory - so I did a ?git pull? and ?git submodule update? in my existing paraview-superbuild repository directory and that 5.3.0-RC1 information was not in the versions.cmake file. I did a clean ?git clone? and I then received the correct files. I?m not a git expert - so I?m not sure why I had to do a clean ?git clone?. I thought I ?git pull? should have done a proper update. I must be missing something with my repository update commands ?.. _______________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Cory Quammen Date: Tuesday, February 21, 2017 at 1:36 PM To: Rick Angelini Cc: "ben.boeckel at kitware.com" , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? Rick, What is the SHA-1 for last commit in your paraview-superbuild directory? The latest commit on master is 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake at line 63, 5.3.0-RC1 should be listed as a version option. Thanks, Cory On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a ?git pull? and ?git submodule update? in the paraview-superbuild > directory. I then changed the source flag in my cmake command: > > -Dparaview_SOURCE_SELECTION="5.3.0-RC1? > > and I get this error when doing a clean build. > > -- Detecting CXX compile features - done > -- Check size of void* > -- Check size of void* - done > CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338 > (message): > The 5.3.0-RC1 source selection for paraview does not exist. > Call Stack (most recent call first): > versions.cmake:62 (superbuild_set_selectable_source) > superbuild/CMakeLists.txt:96 (include) > > > I grepp?ed through the paraview-superbuild directory and I don?t see any > references to 5.3. > > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Cory Quammen > Date: Tuesday, February 21, 2017 at 10:07 AM > To: Rick Angelini > Cc: "ben.boeckel at kitware.com" , ParaView > > Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? > > 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. > > > > > ---- > > Hi Rick, > > From paraview-superbuild master (remember to run 'git submodule > update' after updating master), you should be able to set > paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build. > > These directions are distilled from the README.md file in the > superbuild directory [1]. Relevant excerpt: > > "3. Another option is to use a source tarball of a ParaView release. > For that, set paraview_SOURCE_SELECTION to the version to build such > as 5.2.0. The superbuild offers the lastest stable release as well as > release candidate in preparation for the release. This is the best way > to build a released version of ParaView." > > For each release candidate and release, we add an entry under > paraview_SOURCE_SELECTION that you can select. > > Let us know if you run into problems. > > Thanks, > Cory > > [1] > >Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste >r > /README.md > > On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY > RDECOM ARL (US) wrote: >> What are the instructions for using PVSB to build the 5.3- RC ? >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> -----Original Message----- >> From: Ben Boeckel >> Reply-To: "ben.boeckel at kitware.com" >> Date: Wednesday, February 15, 2017 at 11:34 AM >> To: Rick Angelini >> Cc: ParaView >> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? >> >> On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV >> USARMY RDECOM ARL (US) wrote: >>> I did a fresh pull of the ParaView superbuild repository, and now I >>>can?t do >>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). >>> >>> First, I had to remove the entries for ?qt? and ?scipy" in the >>> CMakeLists.txt: >> >> You need to run `git submodule update` to update the common-superbuild >> bits. >> >>> After removing those entries, the cmake completes and the build starts >>>and >>> passes out in qt4. >>> I?m not sure why it?s complaining about OS X 10.7 or later?) >> >> What version of Xcode are you using? >> >> --Ben >> >> _______________________________________________ >> Powered by Caution-www.kitware.com >> >> Visit other Kitware open-source projects at >>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 >> >> Search the list archives at: >>Caution-http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> Caution-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 -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From mathieu.westphal at kitware.com Wed Feb 22 08:28:54 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 22 Feb 2017 14:28:54 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170222131230.GA6970@avignon> References: <20170222131230.GA6970@avignon> Message-ID: Hi ArchLinux user here. Your CMakeCache.txt looks like a QT4 configuration, no occurence of libQt5. I can build with Qt4 without any problem. You may want to : - CleanUp your build directory and configure and build again. Unless specific needs, i suggest you only set PARAVIEW_QT_VERSION to 4 and build - If it stills segfault, run with gdb and report the backtrace - Try with qt5 as well. Regards Mathieu Westphal On Wed, Feb 22, 2017 at 2:12 PM, Robert Sawko wrote: > Hi, > > This is Arch Linux user again. Parview no longer opens for me. It just ends > with a core dump (attached). It seems it's something to do with Arch Linux > forward looking policy of favouring QT5. I have specified in the > compilation > to build with QT4 (see attached CMakeCache.txt), but on run it still picks > libQt5Core.so. > > I will now try to rebuild with QT5 but there was a perspective issue with > that > before. > > Does anyone have any suggestions, please? > > Thanks, > Robert > -- > Tropics in Cornwall: > http://en.wikipedia.org/wiki/Eden_Project > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 robertsawko at gmail.com Wed Feb 22 08:36:26 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Wed, 22 Feb 2017 14:36:26 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: References: <20170222131230.GA6970@avignon> Message-ID: <20170222133626.GA29359@avignon> I was convinced I attached stack trace too. Please see core.dump file. It may be a red herring but there are several references to libQt5Core there. I am rebuilding with Qt5 now, but will also try a more minimal build with Qt4 later. Thanks for quick reply. Robert -- Tropics in Cornwall: http://en.wikipedia.org/wiki/Eden_Project From mathieu.westphal at kitware.com Wed Feb 22 08:34:42 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 22 Feb 2017 14:34:42 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170222133626.GA29359@avignon> References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> Message-ID: You are right, i did not check the core dump. Let me know how it goes. Mathieu Westphal On Wed, Feb 22, 2017 at 2:36 PM, Robert Sawko wrote: > I was convinced I attached stack trace too. Please see core.dump file. It > may > be a red herring but there are several references to libQt5Core there. I am > rebuilding with Qt5 now, but will also try a more minimal build with Qt4 > later. > > Thanks for quick reply. > Robert > -- > Tropics in Cornwall: > http://en.wikipedia.org/wiki/Eden_Project > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenadus at gmail.com Wed Feb 22 09:03:55 2017 From: nenadus at gmail.com (Nenad Vujicic) Date: Wed, 22 Feb 2017 15:03:55 +0100 Subject: [Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color In-Reply-To: References: Message-ID: Utkarsh, Thank you very much! I made mistake by casting vtkScalarsToColors to vtkLookupTable always, without inspecting of other branches! When I put conditional checking if it is maybe vtkPVDiscretizableColorTransferFunction, it started working! Thank you very much for your help! Nenad. On Wed, Feb 22, 2017 at 2:12 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Where are you getting the vtkLookupTable from? ParaView doesn't use > vtkLookupTable directly, is uses vtkPVDiscretizableColorTransferFunction > > . > > Utkarsh > > On Tue, Feb 21, 2017 at 11:42 AM, Nenad Vujicic wrote: > >> Hello everyone, >> >> I'm trying to inspect values of "UseBelowRangeColor" and >> "UseAboveRangeColor" flags from my ParaView exporter plugin by: >> >> 1. Retrieving vtkCompositePolyDataMapper2 from currently active view and >> rendering window, then, >> 2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor() >> and GetUseBelowRangeColor(), >> >> However, first call (for checking using above range color) always passes >> and returns some big number and second one (for checking using below range >> color) always crashes, regardless whether flags are turned ON / OFF in >> ParaView UI. >> >> Any suggestions about this or ideas how I could pick up these values in >> different way? >> >> Thanks in advance! >> Nenad. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 Wed Feb 22 09:04:38 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 22 Feb 2017 09:04:38 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: Rick, Interesting. I would think that should have worked, assuming you are on the 'master' branch, and my local testing suggests it would. What I usually do these days to be be more explicit in my git updates is: git checkout master git fetch origin git merge origin/master 'git pull' does essentially the last two if you are on the 'master' branch. If you are on another branch, FETCH_HEAD may already point to the tip of the remote branch, and so there may be nothing to merge. In any case, a fresh 'git clone' is sure to work, though as you say, you really shouldn't have to. Thanks for testing the release candidate. Best, Cory On Wed, Feb 22, 2017 at 8:10 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cory - so I did a ?git pull? and ?git submodule update? in my existing > paraview-superbuild repository directory and that 5.3.0-RC1 information > was not in the versions.cmake file. I did a clean ?git clone? and I > then received the correct files. I?m not a git expert - so I?m not > sure why I had to do a clean ?git clone?. I thought I ?git pull? should > have done a proper update. I must be missing something with my > repository update commands ?.. > > _______________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Cory Quammen > Date: Tuesday, February 21, 2017 at 1:36 PM > To: Rick Angelini > Cc: "ben.boeckel at kitware.com" , ParaView > > Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? > > Rick, > > What is the SHA-1 for last commit in your paraview-superbuild > directory? The latest commit on master is > 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake > at line 63, 5.3.0-RC1 should be listed as a version option. > > Thanks, > Cory > > On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV > USARMY RDECOM ARL (US) wrote: >> I did a ?git pull? and ?git submodule update? in the paraview-superbuild >> directory. I then changed the source flag in my cmake command: >> >> -Dparaview_SOURCE_SELECTION="5.3.0-RC1? >> >> and I get this error when doing a clean build. >> >> -- Detecting CXX compile features - done >> -- Check size of void* >> -- Check size of void* - done >> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338 >> (message): >> The 5.3.0-RC1 source selection for paraview does not exist. >> Call Stack (most recent call first): >> versions.cmake:62 (superbuild_set_selectable_source) >> superbuild/CMakeLists.txt:96 (include) >> >> >> I grepp?ed through the paraview-superbuild directory and I don?t see any >> references to 5.3. >> >> >> >> >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> -----Original Message----- >> From: Cory Quammen >> Date: Tuesday, February 21, 2017 at 10:07 AM >> To: Rick Angelini >> Cc: "ben.boeckel at kitware.com" , ParaView >> >> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? >> >> 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. >> >> >> >> >> ---- >> >> Hi Rick, >> >> From paraview-superbuild master (remember to run 'git submodule >> update' after updating master), you should be able to set >> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build. >> >> These directions are distilled from the README.md file in the >> superbuild directory [1]. Relevant excerpt: >> >> "3. Another option is to use a source tarball of a ParaView release. >> For that, set paraview_SOURCE_SELECTION to the version to build such >> as 5.2.0. The superbuild offers the lastest stable release as well as >> release candidate in preparation for the release. This is the best way >> to build a released version of ParaView." >> >> For each release candidate and release, we add an entry under >> paraview_SOURCE_SELECTION that you can select. >> >> Let us know if you run into problems. >> >> Thanks, >> Cory >> >> [1] >> >>Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste >>r >> /README.md >> >> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY >> RDECOM ARL (US) wrote: >>> What are the instructions for using PVSB to build the 5.3- RC ? >>> ________________________________ >>> Rick Angelini >>> USArmy Research Laboratory >>> CISD/HPC Architectures Team >>> Phone: 410-278-6266 >>> >>> >>> >>> >>> -----Original Message----- >>> From: Ben Boeckel >>> Reply-To: "ben.boeckel at kitware.com" >>> Date: Wednesday, February 15, 2017 at 11:34 AM >>> To: Rick Angelini >>> Cc: ParaView >>> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? >>> >>> On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) CIV >>> USARMY RDECOM ARL (US) wrote: >>>> I did a fresh pull of the ParaView superbuild repository, and now I >>>>can?t do >>>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). >>>> >>>> First, I had to remove the entries for ?qt? and ?scipy" in the >>>> CMakeLists.txt: >>> >>> You need to run `git submodule update` to update the common-superbuild >>> bits. >>> >>>> After removing those entries, the cmake completes and the build starts >>>>and >>>> passes out in qt4. >>>> I?m not sure why it?s complaining about OS X 10.7 or later?) >>> >>> What version of Xcode are you using? >>> >>> --Ben >>> >>> _______________________________________________ >>> Powered by Caution-www.kitware.com >>> >>> Visit other Kitware open-source projects at >>>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 >>> >>> Search the list archives at: >>>Caution-http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> Caution-http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From ben.boeckel at kitware.com Wed Feb 22 09:04:51 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 22 Feb 2017 09:04:51 -0500 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: <20170222140451.GA22741@megas.kitware.com> On Wed, Feb 22, 2017 at 13:10:04 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cory - so I did a ?git pull? and ?git submodule update? in my existing > paraview-superbuild repository directory and that 5.3.0-RC1 information > was not in the versions.cmake file. I did a clean ?git clone? and I > then received the correct files. I?m not a git expert - so I?m not > sure why I had to do a clean ?git clone?. I thought I ?git pull? should > have done a proper update. I must be missing something with my > repository update commands ?.. What is the output of the following commands: - git config branch.master.remote - git remote show $output_from_previous_command - git remote show origin --Ben From ben.boeckel at kitware.com Wed Feb 22 09:08:32 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 22 Feb 2017 09:08:32 -0500 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: References: <20170221155502.GA15354@megas.kitware.com> <20170221173824.GA17894@megas.kitware.com> <20170221181906.GA2452@rotor.kitware.com> Message-ID: <20170222140832.GB22741@megas.kitware.com> On Wed, Feb 22, 2017 at 09:37:47 +0100, Nabil Ghodbane wrote: > - I am requesting USE_SYSTEM_hdf5 = OFF > but looking as you suggested in superbuild/paraview/build/CMakeCache.txt, I > can see that VTK_USE_SYSTEM_HDF5:BOOL=TRUE > Shouldn't this be FALSE ? >From ParaView's point of view, it is using a "system" HDF5, but it is being provided by the superbuild itself. It looks like it is finding the superbuild's HDF5, so something else is going wrong here :( . > Find attached, the CMakeCache.txt, How can I workaround this issue? It will need investigation. I'll try and get to it this week. > Find below some additional informations: > - it works on Ubuntu (I tried my own Python), but I need to stick to an > older glibc :( > - on a Debian node, it fails if I use my local Python installation, while > trying to compile numpy: "/usr/lib/python2.7/distutils/sysconfig.py" More information is needed to help with this. --Ben From cory.quammen at kitware.com Wed Feb 22 09:14:57 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 22 Feb 2017 09:14:57 -0500 Subject: [Paraview] problems with packaging of superbuild In-Reply-To: <2215131.DiXl1TVbhV@saintvenant.zmaw.de> References: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> <1754789.rsqZdryCgt@saintvenant.zmaw.de> <2215131.DiXl1TVbhV@saintvenant.zmaw.de> Message-ID: Stefan, Are you building from the v5.2.0 tag in paraview-superbuild? If so, I recommend building from current master instead. ParaView 5.2.0 is still the default version in master, but there have been some fixes in the superbuild that may address the problems you have run into since v5.2.0 was tagged in the superbuild. HTH, Cory On Wed, Feb 22, 2017 at 8:04 AM, Stefan Vater wrote: > Once again... > > so the old two problems seem to still exist. I made some changes in the camke > files to circumvent them, but forgot that they are still there. > > Stefan > > Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater: >> Hi, >> >> it seems that these errors resulted from the fact, that I set an absolute >> install path. However, now I have the problem that the packaging fails to >> find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At >> least this is my guess. The error message is: >> >> [...] >> 1: CPack: Install projects >> 1: CPack: - Run preinstall target for: cpack-paraview >> 1: CPack: - Install project: cpack-paraview >> 1: CPack Verbose: Install configuration: "Release" >> 1: CMake Error at >> /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake: >> 45 (message): 1: Failed to install pvdataserver: >> 1: >> 1: Traceback (most recent call last): >> 1: >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 504, in 1: main(sys.argv[1:]) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 496, in main 1: _install_binary(main_exe, is_excluded, >> bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1: >> File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 400, in _install_binary 1: deps = >> binary.dependencies.values() >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 197, in dependencies 1: deplib = >> Library.create_from_reference(dep, self) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 258, in create_from_reference 1: >> paths.extend(cls.default_search_paths()) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 230, in default_search_paths 1: cls.__search_cache = >> pipe().split('\n') >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 22, in __call__ 1: command = >> subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1: >> File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1: >> errread, errwrite) >> 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child >> 1: raise child_exception >> 1: >> 1: OSError: [Errno 2] No such file or directory >> 1: >> 1: >> 1: >> 1: CPack Error: Error when generating package: ParaView >> 1: CMake Error at >> /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm >> ake:21 (message): 1: CPack failed with exit code 1 >> 1: >> 1: >> 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.10 sec >> >> Any suggestions? >> >> Stefan >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 > -- > Stefan Vater > Research group "Numerical Methods in Geosciences" > CEN - Center for Earth System Research and Sustainability > Universit?t Hamburg > Grindelberg 5, D-20144 Hamburg, Germany > Phone: +49 - 40 - 42838 7746 > Fax: +49 - 40 - 42838 7712 > Email: stefan.vater at uni-hamburg.de > URL: http://www.clisap.de/vater > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 adershowitz at exponent.com Wed Feb 22 10:16:44 2017 From: adershowitz at exponent.com (Adam Dershowitz) Date: Wed, 22 Feb 2017 15:16:44 +0000 Subject: [Paraview] Duplicate Renderview Message-ID: <0885637E-AB5E-4083-A3AC-7FEA5AE7AA56@exponent.com> I have a pipeline setup, with a good renderview. I want to then make a split view, that is identical, except for the camera angle. When I try to split my view, or create a new view, they show up empty. I can then start manually turning on, and coloring everything how I want it. But, it seems like there should be an option to ?duplicate current pipeline settings? as a starting point. Then, I could move the camera or make any other changes that I want from there. I did search around in Paraview and on the web, but didn?t find anything. Is there an easy way to do this? I did find a few other discussions about this, with suggested scripts, but those fail for me as well. I?m using Paraview 5.2, although I also looked around briefly for a way to do this in 5.3RC1. Thanks, -- Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Feb 22 10:17:44 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 22 Feb 2017 10:17:44 -0500 Subject: [Paraview] problems with packaging of superbuild In-Reply-To: <1487775492812.96349@lanl.gov> References: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> <1754789.rsqZdryCgt@saintvenant.zmaw.de> <2215131.DiXl1TVbhV@saintvenant.zmaw.de> <1487775492812.96349@lanl.gov> Message-ID: Hi Jennifer, We will tag the superbuild with a v5.3.0 tag after 5.3.0 final is tagged, but we don't plan to tag paraview-superbuild with v5.3.0-RC1 or other release candidate tags. To build 5.3.0-RC1, I recommend using the master branch of paraview-superbuild and setting the 'paraview_SOURCE_SELECTION' CMake variable to '5.3.0-RC1'. This will download the tarball of the ParaView 5.3.0-RC1 source and build it. If you do not have network access on the build machine, you can set 'paraview_SOURCE_SELECTION' to 'source' and set 'paraview_SOURCE_DIR' to the ParaView 5.3.0-RC1 source directory you have set up manually. Details for the different options for acquiring the ParaView source are available in the "Building a specific versoin" section of the README.md file in the top level of paraview-superbuild. You can view this file online at https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md. Please let us know if you have any other questions or run into any problems. Thank you, Cory On Wed, Feb 22, 2017 at 9:58 AM, Green, Jennifer Kathleen wrote: > Are there plans to tag a 5.3.0-rc1 version of the superbuild? Or, is it recommended to modify the superbuild to pull in the ParaView/5.3.0-rc1 version manually? > > 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: ParaView on behalf of Cory Quammen > Sent: Wednesday, February 22, 2017 7:14 AM > To: Stefan Vater > Cc: ParaView > Subject: Re: [Paraview] problems with packaging of superbuild > > Stefan, > > Are you building from the v5.2.0 tag in paraview-superbuild? If so, I > recommend building from current master instead. ParaView 5.2.0 is > still the default version in master, but there have been some fixes in > the superbuild that may address the problems you have run into since > v5.2.0 was tagged in the superbuild. > > HTH, > Cory > > On Wed, Feb 22, 2017 at 8:04 AM, Stefan Vater wrote: >> Once again... >> >> so the old two problems seem to still exist. I made some changes in the camke >> files to circumvent them, but forgot that they are still there. >> >> Stefan >> >> Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater: >>> Hi, >>> >>> it seems that these errors resulted from the fact, that I set an absolute >>> install path. However, now I have the problem that the packaging fails to >>> find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At >>> least this is my guess. The error message is: >>> >>> [...] >>> 1: CPack: Install projects >>> 1: CPack: - Run preinstall target for: cpack-paraview >>> 1: CPack: - Install project: cpack-paraview >>> 1: CPack Verbose: Install configuration: "Release" >>> 1: CMake Error at >>> /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake: >>> 45 (message): 1: Failed to install pvdataserver: >>> 1: >>> 1: Traceback (most recent call last): >>> 1: >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 504, in 1: main(sys.argv[1:]) >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 496, in main 1: _install_binary(main_exe, is_excluded, >>> bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1: >>> File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 400, in _install_binary 1: deps = >>> binary.dependencies.values() >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 197, in dependencies 1: deplib = >>> Library.create_from_reference(dep, self) >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 258, in create_from_reference 1: >>> paths.extend(cls.default_search_paths()) >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 230, in default_search_paths 1: cls.__search_cache = >>> pipe().split('\n') >>> 1: File >>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >>> nix.py", line 22, in __call__ 1: command = >>> subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1: >>> File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1: >>> errread, errwrite) >>> 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child >>> 1: raise child_exception >>> 1: >>> 1: OSError: [Errno 2] No such file or directory >>> 1: >>> 1: >>> 1: >>> 1: CPack Error: Error when generating package: ParaView >>> 1: CMake Error at >>> /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm >>> ake:21 (message): 1: CPack failed with exit code 1 >>> 1: >>> 1: >>> 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.10 sec >>> >>> Any suggestions? >>> >>> Stefan >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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 >> -- >> Stefan Vater >> Research group "Numerical Methods in Geosciences" >> CEN - Center for Earth System Research and Sustainability >> Universit?t Hamburg >> Grindelberg 5, D-20144 Hamburg, Germany >> Phone: +49 - 40 - 42838 7746 >> Fax: +49 - 40 - 42838 7712 >> Email: stefan.vater at uni-hamburg.de >> URL: http://www.clisap.de/vater >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. From jgreen at lanl.gov Wed Feb 22 09:58:13 2017 From: jgreen at lanl.gov (Green, Jennifer Kathleen) Date: Wed, 22 Feb 2017 14:58:13 +0000 Subject: [Paraview] problems with packaging of superbuild In-Reply-To: References: <9746723.XI3uQVO5Bg@saintvenant.zmaw.de> <1754789.rsqZdryCgt@saintvenant.zmaw.de> <2215131.DiXl1TVbhV@saintvenant.zmaw.de>, Message-ID: <1487775492812.96349@lanl.gov> Are there plans to tag a 5.3.0-rc1 version of the superbuild? Or, is it recommended to modify the superbuild to pull in the ParaView/5.3.0-rc1 version manually? 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: ParaView on behalf of Cory Quammen Sent: Wednesday, February 22, 2017 7:14 AM To: Stefan Vater Cc: ParaView Subject: Re: [Paraview] problems with packaging of superbuild Stefan, Are you building from the v5.2.0 tag in paraview-superbuild? If so, I recommend building from current master instead. ParaView 5.2.0 is still the default version in master, but there have been some fixes in the superbuild that may address the problems you have run into since v5.2.0 was tagged in the superbuild. HTH, Cory On Wed, Feb 22, 2017 at 8:04 AM, Stefan Vater wrote: > Once again... > > so the old two problems seem to still exist. I made some changes in the camke > files to circumvent them, but forgot that they are still there. > > Stefan > > Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater: >> Hi, >> >> it seems that these errors resulted from the fact, that I set an absolute >> install path. However, now I have the problem that the packaging fails to >> find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At >> least this is my guess. The error message is: >> >> [...] >> 1: CPack: Install projects >> 1: CPack: - Run preinstall target for: cpack-paraview >> 1: CPack: - Install project: cpack-paraview >> 1: CPack Verbose: Install configuration: "Release" >> 1: CMake Error at >> /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake: >> 45 (message): 1: Failed to install pvdataserver: >> 1: >> 1: Traceback (most recent call last): >> 1: >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 504, in 1: main(sys.argv[1:]) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 496, in main 1: _install_binary(main_exe, is_excluded, >> bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1: >> File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 400, in _install_binary 1: deps = >> binary.dependencies.values() >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 197, in dependencies 1: deplib = >> Library.create_from_reference(dep, self) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 258, in create_from_reference 1: >> paths.extend(cls.default_search_paths()) >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 230, in default_search_paths 1: cls.__search_cache = >> pipe().split('\n') >> 1: File >> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u >> nix.py", line 22, in __call__ 1: command = >> subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1: >> File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1: >> errread, errwrite) >> 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child >> 1: raise child_exception >> 1: >> 1: OSError: [Errno 2] No such file or directory >> 1: >> 1: >> 1: >> 1: CPack Error: Error when generating package: ParaView >> 1: CMake Error at >> /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm >> ake:21 (message): 1: CPack failed with exit code 1 >> 1: >> 1: >> 1/1 Test #1: cpack-paraview-TGZ ...............***Failed 0.10 sec >> >> Any suggestions? >> >> Stefan >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 > -- > Stefan Vater > Research group "Numerical Methods in Geosciences" > CEN - Center for Earth System Research and Sustainability > Universit?t Hamburg > Grindelberg 5, D-20144 Hamburg, Germany > Phone: +49 - 40 - 42838 7746 > Fax: +49 - 40 - 42838 7712 > Email: stefan.vater at uni-hamburg.de > URL: http://www.clisap.de/vater > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From robertsawko at gmail.com Wed Feb 22 11:49:26 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Wed, 22 Feb 2017 17:49:26 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> Message-ID: <20170222164926.GA15369@avignon> Unfortunately even a minimal compilation of ParaView (no options). I am attaching the stack trace. Let me know if you have any ideas. Robert -------------- next part -------------- A non-text attachment was scrubbed... Name: core.dump Type: application/octet-stream Size: 5484 bytes Desc: not available URL: From mathieu.westphal at kitware.com Wed Feb 22 11:53:10 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 22 Feb 2017 17:53:10 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170222164926.GA15369@avignon> References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> Message-ID: Hi Please make sure ParaView is compiled in Debug, run it with gdb, then forward the backtrace. Mathieu Westphal On Wed, Feb 22, 2017 at 5:49 PM, Robert Sawko wrote: > Unfortunately even a minimal compilation of ParaView (no options). I am > attaching the stack trace. Let me know if you have any ideas. > > Robert > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robertsawko at gmail.com Wed Feb 22 12:01:22 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Wed, 22 Feb 2017 18:01:22 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> Message-ID: <20170222170122.GA22001@avignon> Thanks. Here's the gdb output. I did compile in Debug mode. Robert -- Noah's Ark for plants: http://en.wikipedia.org/wiki/Svalbard_Global_Seed_Vault -------------- next part -------------- Starting program: /home/rsa/downloads/software/paraview-5.3/build/bin/paraview [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGABRT, Aborted. 0x00007fffeb68204f in raise () from /usr/lib/libc.so.6 #0 0x00007fffeb68204f in raise () at /usr/lib/libc.so.6 #1 0x00007fffeb68347a in abort () at /usr/lib/libc.so.6 #2 0x00007ffff1e2c874 in vtkXOpenGLRenderWindow::CreateAWindow() (this=0xe082e0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 #3 0x00007ffff1d91bea in vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int, int) (this=0xe082e0, width=300, height=300) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:1970 #4 0x00007ffff1e2dafa in vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int) (this=0xe082e0, width=300, height=300) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:807 #5 0x00007ffff1e2df10 in vtkXOpenGLRenderWindow::Initialize() (this=0xe082e0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:922 #6 0x00007ffff1d9306f in vtkOpenGLRenderWindow::SupportsOpenGL() (this=0xe07080) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2406 #7 0x00007fffea5f3da9 in vtkPVDisplayInformation::SupportsOpenGLLocally() () at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:108 #8 0x00007fffea5f3e2d in vtkPVDisplayInformation::CopyFromObject(vtkObject*) (this=0xe06120) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ClientServerCore/Rendering/vtkPVDisplayInformation.cxx:124 #9 0x00007ffff403b004 in vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) (this=0x8532b0, information=0xe06120, globalid=0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:783 #10 0x00007ffff403b2b9 in vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) (this=0x8532b0, location=4, information=0xe06120, globalid=0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:821 #11 0x00007ffff4036e28 in vtkPVSessionBase::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) (this= 0xc24490, location=4, information=0xe06120, globalid=0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:243 #12 0x00007ffff7a68879 in pqDefaultViewBehavior::onServerCreation(pqServer*) (this=0xc23110, server=0xf242e0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/ApplicationComponents/pqDefaultViewBehavior.cxx:119 #13 0x00007ffff7afa616 in pqDefaultViewBehavior::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0xc23110, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffffd500) at /home/rsa/downloads/software/paraview-5.3/build/Qt/ApplicationComponents/moc_pqDefaultViewBehavior.cxx:54 #14 0x00007ffff2d03c50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #15 0x00007ffff63ce04d in pqServerManagerModel::serverAdded(pqServer*) (this=0x861100, _t1=0xf242e0) at /home/rsa/downloads/software/paraview-5.3/build/Qt/Core/moc_pqServerManagerModel.cxx:218 #16 0x00007ffff639b02a in pqServerManagerModel::onConnectionCreated(long long) (this=0x861100, id=1) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/Core/pqServerManagerModel.cxx:503 #17 0x00007ffff63cde5f in pqServerManagerModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x861100, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffffffd6f0) at /home/rsa/downloads/software/paraview-5.3/build/Qt/Core/moc_pqServerManagerModel.cxx:160 #18 0x00007ffff2d03c50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #19 0x00007ffff63cf1e3 in pqServerManagerObserver::connectionCreated(long long) (this=0x822400, _t1=1) at /home/rsa/downloads/software/paraview-5.3/build/Qt/Core/moc_pqServerManagerObserver.cxx:170 #20 0x00007ffff639eaf1 in pqServerManagerObserver::connectionCreated(vtkObject*, unsigned long, void*, void*) (this=0x822400, callData=0x811870) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/Core/pqServerManagerObserver.cxx:110 #21 0x00007ffff63cee0a in pqServerManagerObserver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x822400, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffffffd8f0) at /home/rsa/downloads/software/paraview-5.3/build/Qt/Core/moc_pqServerManagerObserver.cxx:90 #22 0x00007ffff2d03c50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #23 0x00007ffff33f4fa9 in vtkQtConnection::EmitExecute(vtkObject*, unsigned long, void*, void*, vtkCommand*) (this=0x854f70, _t1=0x811830, _t2=66, _t3=0x0, _t4=0x811870, _t5=0x833560) at /home/rsa/downloads/software/paraview-5.3/build/VTK/GUISupport/Qt/moc_vtkQtConnection.cxx:103 #24 0x00007ffff33e38d6 in vtkQtConnection::Execute(vtkObject*, unsigned long, void*) (this=0x854f70, caller=0x811830, e=66, call_data=0x811870) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/GUISupport/Qt/vtkQtConnection.cxx:72 #25 0x00007ffff33e3874 in vtkQtConnection::DoCallback(vtkObject*, unsigned long, void*, void*) (vtk_obj=0x811830, event=66, client_data=0x854f70, call_data=0x811870) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/GUISupport/Qt/vtkQtConnection.cxx:62 #26 0x00007fffec51a3db in vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) (this=0x833560, caller=0x811830, event=66, callData=0x811870) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Common/Core/vtkCallbackCommand.cxx:42 #27 0x00007fffec60b40c in vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (this=0x85ad20, event=66, callData=0x811870, self=0x811830) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Common/Core/vtkObject.cxx:616 #28 0x00007fffec60b919 in vtkObject::InvokeEvent(unsigned long, void*) (this=0x811830, event=66, callData=0x811870) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/VTK/Common/Core/vtkObject.cxx:785 #29 0x00007ffff38bb826 in vtkProcessModule::RegisterSession(vtkSession*) (this=0x811830, session=0xc24490) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ClientServerCore/Core/vtkProcessModule.cxx:381 #30 0x00007ffff453be79 in vtkSMSession::ConnectToSelf() () at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/ParaViewCore/ServerManager/Core/vtkSMSession.cxx:308 #31 0x00007ffff635d10a in pqObjectBuilder::createServer(pqServerResource const&) (this=0x8098e0, resource=...) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/Core/pqObjectBuilder.cxx:656 #32 0x00007ffff7a28c44 in pqAlwaysConnectedBehavior::serverCheck() (this=0xc21fb0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:81 #33 0x00007ffff7a28ad8 in pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) (this=0xc21fb0, parentObject=0xc1a5c0) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/ApplicationComponents/pqAlwaysConnectedBehavior.cxx:52 #34 0x00007ffff7a993aa in pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) (this=0xc1a5c0, mainWindow=0x83c280, parentObject=0x83c280) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Qt/ApplicationComponents/pqParaViewBehaviors.cxx:157 #35 0x000000000040c884 in ParaViewMainWindow::ParaViewMainWindow() (this=0x83c280) at /home/rsa/downloads/software/paraview-5.3/ParaView-v5.3.0-RC1/Applications/ParaView/ParaViewMainWindow.cxx:249 #36 0x000000000040a8af in pqparaviewInitializer::Initialize(int, char**) (this=0x7fffffffe2d0, argc=1, argv=0x7fffffffe468) at /home/rsa/downloads/software/paraview-5.3/build/Applications/ParaView/pqparaviewInitializer.cxx:125 #37 0x000000000040a182 in main(int, char**) (argc=1, argv=0x7fffffffe468) at /home/rsa/downloads/software/paraview-5.3/build/Applications/ParaView/paraview_main.cxx:115 Undefined command: "exit". Try "help". From mathieu.westphal at kitware.com Wed Feb 22 12:08:24 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 22 Feb 2017 18:08:24 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170222170122.GA22001@avignon> References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> <20170222170122.GA22001@avignon> Message-ID: Looks like a Xorg problem. Please specify : - Is your system up to date ? - Are you running X ? Wayland ? - What DE/WM are you running ? - What graphic card do you have ? With which drivers version ? - What version of opengl is installed ? please provide glxinfo output. - There should be some error message before the segfault, but we can't see any, did you removed them or are they missing ? - Can you check in your source that paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 contains : 6 if (!this->WindowId) 5 { 4 v = this->GetDesiredVisualInfo(); 3 if (!v) 2 { 1 vtkErrorMacro(<< "Could not find a decent visual\n"); 485 abort(); 1 } Regards Mathieu Westphal On Wed, Feb 22, 2017 at 6:01 PM, Robert Sawko wrote: > Thanks. Here's the gdb output. I did compile in Debug mode. > > Robert > -- > Noah's Ark for plants: > http://en.wikipedia.org/wiki/Svalbard_Global_Seed_Vault > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robertsawko at gmail.com Wed Feb 22 12:26:34 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Wed, 22 Feb 2017 18:26:34 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> <20170222170122.GA22001@avignon> Message-ID: <20170222172634.GA28684@avignon> Thanks for looking into it, Mathieu. > - Is your system up to date ? It's quite up to date. See below. $ uname -a Linux avignon 4.9.9-1-ARCH #1 SMP PREEMPT Thu Feb 9 19:07:09 CET 2017 x86_64 GNU/Linux > - Are you running X ? Wayland ? Yes, for X. Never heard of Wayland. > - What DE/WM are you running ? No DE, but Xmonad as WM. > - What graphic card do you have ? With which drivers version ? Nvidia Quadro. I've got nvidia driver version 378.13-1. There's a slightly newer one in the repo. > - What version of opengl is installed ? please provide glxinfo output. $ glxinfo name of display: :0.0 Error: couldn't find RGB GLX visual or fbconfig Oops... that looks like a problem. I could try downgrading opengl. > - There should be some error message before the segfault, but we can't > see any, did you removed them or are they missing ? I haven't removed anything from the gdb output. Running paraview from bash is core-dumps silently. > - Can you check in your source that > paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 contains Yes, these lines are there. Robert From mathieu.westphal at kitware.com Wed Feb 22 12:27:23 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 22 Feb 2017 18:27:23 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170222172634.GA28684@avignon> References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> <20170222170122.GA22001@avignon> <20170222172634.GA28684@avignon> Message-ID: Hi Well, you found it yourself, looks like you have some problem with OpenGL and x windows. Can't help you much more here, let me know when you are able to fix it if paraview still crashes. Also, if glxinfo does not work, i would expect all x application to crash as well. Regards, Mathieu Westphal On Wed, Feb 22, 2017 at 6:26 PM, Robert Sawko wrote: > > Thanks for looking into it, Mathieu. > > > - Is your system up to date ? > It's quite up to date. See below. > $ uname -a > Linux avignon 4.9.9-1-ARCH #1 SMP PREEMPT Thu Feb 9 19:07:09 CET 2017 > x86_64 GNU/Linux > > > - Are you running X ? Wayland ? > Yes, for X. Never heard of Wayland. > > > - What DE/WM are you running ? > No DE, but Xmonad as WM. > > > - What graphic card do you have ? With which drivers version ? > Nvidia Quadro. I've got nvidia driver version 378.13-1. There's a slightly > newer one in the repo. > > > - What version of opengl is installed ? please provide glxinfo output. > > $ glxinfo > name of display: :0.0 > Error: couldn't find RGB GLX visual or fbconfig > > Oops... that looks like a problem. I could try downgrading opengl. > > > - There should be some error message before the segfault, but we can't > > see any, did you removed them or are they missing ? > > I haven't removed anything from the gdb output. Running paraview from bash > is > core-dumps silently. > > > - Can you check in your source that > > paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 > contains > > Yes, these lines are there. > > Robert > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Feb 22 13:40:00 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 22 Feb 2017 18:40:00 +0000 Subject: [Paraview] [EXTERNAL] Re: [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: References: <20170215163409.GA8112@megas.kitware.com> Message-ID: <9fccd1d58b454f05bafa5930dc8d3d70@ES01AMSNLNT.srn.sandia.gov> I am not sure of this, but I believe I also saw this (i.e., git pull and git submodule update not updating Superbuild) a week ago. Will pay more attention. Alan > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cory > Quammen > Sent: Wednesday, February 22, 2017 7:05 AM > To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) > > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] Re: Superbuild repo > change? > > Rick, > > Interesting. I would think that should have worked, assuming you are on the > 'master' branch, and my local testing suggests it would. > > What I usually do these days to be be more explicit in my git updates is: > > git checkout master > git fetch origin > git merge origin/master > > 'git pull' does essentially the last two if you are on the 'master' > branch. If you are on another branch, FETCH_HEAD may already point to the > tip of the remote branch, and so there may be nothing to merge. > > In any case, a fresh 'git clone' is sure to work, though as you say, you really > shouldn't have to. > > Thanks for testing the release candidate. > > Best, > Cory > > On Wed, Feb 22, 2017 at 8:10 AM, Angelini, Richard C (Rick) CIV USARMY > RDECOM ARL (US) wrote: > > Cory - so I did a ?git pull? and ?git submodule update? in my existing > > paraview-superbuild repository directory and that 5.3.0-RC1 information > > was not in the versions.cmake file. I did a clean ?git clone? and I > > then received the correct files. I?m not a git expert - so I?m not > > sure why I had to do a clean ?git clone?. I thought I ?git pull? should > > have done a proper update. I must be missing something with my > > repository update commands ?.. > > > > _______________________________ > > Rick Angelini > > USArmy Research Laboratory > > CISD/HPC Architectures Team > > Phone: 410-278-6266 > > > > > > > > > > -----Original Message----- > > From: Cory Quammen > > Date: Tuesday, February 21, 2017 at 1:36 PM > > To: Rick Angelini > > Cc: "ben.boeckel at kitware.com" , ParaView > > > > Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? > > > > Rick, > > > > What is the SHA-1 for last commit in your paraview-superbuild > > directory? The latest commit on master is > > 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake > > at line 63, 5.3.0-RC1 should be listed as a version option. > > > > Thanks, > > Cory > > > > On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV > > USARMY RDECOM ARL (US) wrote: > >> I did a ?git pull? and ?git submodule update? in the paraview-superbuild > >> directory. I then changed the source flag in my cmake command: > >> > >> -Dparaview_SOURCE_SELECTION="5.3.0-RC1? > >> > >> and I get this error when doing a clean build. > >> > >> -- Detecting CXX compile features - done > >> -- Check size of void* > >> -- Check size of void* - done > >> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338 > >> (message): > >> The 5.3.0-RC1 source selection for paraview does not exist. > >> Call Stack (most recent call first): > >> versions.cmake:62 (superbuild_set_selectable_source) > >> superbuild/CMakeLists.txt:96 (include) > >> > >> > >> I grepp?ed through the paraview-superbuild directory and I don?t see > >> any references to 5.3. > >> > >> > >> > >> > >> ________________________________ > >> Rick Angelini > >> USArmy Research Laboratory > >> CISD/HPC Architectures Team > >> Phone: 410-278-6266 > >> > >> > >> > >> > >> -----Original Message----- > >> From: Cory Quammen > >> Date: Tuesday, February 21, 2017 at 10:07 AM > >> To: Rick Angelini > >> Cc: "ben.boeckel at kitware.com" , ParaView > >> > >> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? > >> > >> 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. > >> > >> > >> > >> > >> ---- > >> > >> Hi Rick, > >> > >> From paraview-superbuild master (remember to run 'git submodule > >> update' after updating master), you should be able to set > >> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and > build. > >> > >> These directions are distilled from the README.md file in the > >> superbuild directory [1]. Relevant excerpt: > >> > >> "3. Another option is to use a source tarball of a ParaView release. > >> For that, set paraview_SOURCE_SELECTION to the version to build such > >> as 5.2.0. The superbuild offers the lastest stable release as well as > >> release candidate in preparation for the release. This is the best > >> way to build a released version of ParaView." > >> > >> For each release candidate and release, we add an entry under > >> paraview_SOURCE_SELECTION that you can select. > >> > >> Let us know if you run into problems. > >> > >> Thanks, > >> Cory > >> > >> [1] > >> > >>Caution-https://gitlab.kitware.com/paraview/paraview- > superbuild/blob/m > >>aste > >>r > >> /README.md > >> > >> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV > >> USARMY RDECOM ARL (US) wrote: > >>> What are the instructions for using PVSB to build the 5.3- RC ? > >>> ________________________________ > >>> Rick Angelini > >>> USArmy Research Laboratory > >>> CISD/HPC Architectures Team > >>> Phone: 410-278-6266 > >>> > >>> > >>> > >>> > >>> -----Original Message----- > >>> From: Ben Boeckel > >>> Reply-To: "ben.boeckel at kitware.com" > >>> Date: Wednesday, February 15, 2017 at 11:34 AM > >>> To: Rick Angelini > >>> Cc: ParaView > >>> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > >>> > >>> On Wed, Feb 15, 2017 at 13:50:13 +0000, Angelini, Richard C (Rick) > >>> CIV USARMY RDECOM ARL (US) wrote: > >>>> I did a fresh pull of the ParaView superbuild repository, and now I > >>>>can?t do a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > >>>> > >>>> First, I had to remove the entries for ?qt? and ?scipy" in the > >>>> CMakeLists.txt: > >>> > >>> You need to run `git submodule update` to update the > >>> common-superbuild bits. > >>> > >>>> After removing those entries, the cmake completes and the build > >>>>starts and passes out in qt4. > >>>> I?m not sure why it?s complaining about OS X 10.7 or later?) > >>> > >>> What version of Xcode are you using? > >>> > >>> --Ben > >>> > >>> _______________________________________________ > >>> Powered by Caution-www.kitware.com > >>> > >>> Visit other Kitware open-source projects at > >>>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 > >>> > >>> Search the list archives at: > >>>Caution-http://markmail.org/search/?q=ParaView > >>> > >>> Follow this link to subscribe/unsubscribe: > >>> Caution-http://public.kitware.com/mailman/listinfo/paraview > >>> > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > > > > > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 nabil.ghodbane at gmail.com Wed Feb 22 14:47:48 2017 From: nabil.ghodbane at gmail.com (Nabil Ghodbane) Date: Wed, 22 Feb 2017 20:47:48 +0100 Subject: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641 In-Reply-To: <20170221181906.GA2452@rotor.kitware.com> References: <20170221155502.GA15354@megas.kitware.com> <20170221173824.GA17894@megas.kitware.com> <20170221181906.GA2452@rotor.kitware.com> Message-ID: Hi Thanks for the reply. Did someone else manage to get this approach based on the superbuilder machinery on a Centos 7 node? As I wrote it previously the installation works nicely on Ubuntu but fails on CentOS. I will appr?ciateur any feedback about it. Thanks On Tuesday, February 21, 2017, Ben Boeckel wrote: > On Tue, Feb 21, 2017 at 18:48:37 +0100, Nabil Ghodbane wrote: > > fine, I started a parallel build on another node using Python 2.7.12, it > > seems to be compiling so far... > > As I wrote it previously, the first compilation based on Python 2.7.11 > > shipped by the superbuilder fails with the following message: > > do you know by chance whether I do have to switch on/off some flag ? > > Hmm. This looks like a problem with ParaView itself. What HDF5 settings > are you using in the superbuild and what HDF5-related settings are set > in `superbuild/paraview/build/CMakeCache.txt`. > > --Ben > -- Nabil Ghodbane (PhD. Habil.) Mailto: nabil.ghodbane at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvan.fournier at free.fr Wed Feb 22 19:00:14 2017 From: yvan.fournier at free.fr (yvan.fournier at free.fr) Date: Thu, 23 Feb 2017 01:00:14 +0100 (CET) Subject: [Paraview] Issues with OpenGL2 support for off-screen Mesa In-Reply-To: <826155065.115518173.1487095501556.JavaMail.root@zimbra10-e2> Message-ID: <1021954010.154657422.1487808014143.JavaMail.root@zimbra10-e2> 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... From fabidi89 at vt.edu Thu Feb 23 12:57:54 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Thu, 23 Feb 2017 12:57:54 -0500 Subject: [Paraview] Paraview server and Paraview client versions Message-ID: Hi community, Quick question - if both compiled from source, what all needs to be same for a client and server to connect and render successfully? More specifically: 1) if the client is compiled with openmpi while the remote server with mpich, will it work? 2) And if both are compiled with openmpi, do the versions of openmpi also need to be same? Thanks in advance! -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Thu Feb 23 13:14:03 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Thu, 23 Feb 2017 13:14:03 -0500 Subject: [Paraview] Issues with OpenGL2 support for off-screen Mesa In-Reply-To: <1021954010.154657422.1487808014143.JavaMail.root@zimbra10-e2> References: <826155065.115518173.1487095501556.JavaMail.root@zimbra10-e2> <1021954010.154657422.1487808014143.JavaMail.root@zimbra10-e2> Message-ID: 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, 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Thu Feb 23 13:21:41 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Thu, 23 Feb 2017 13:21:41 -0500 Subject: [Paraview] Paraview server and Paraview client versions In-Reply-To: References: Message-ID: Hi Faiz, Quick question - if both compiled from source, what all needs to be same > for a client and server to connect and render successfully? > They both need to be the same version of paraview and use the same rendering backend, i.e. OpenGL vs OpenGL2. ParaView now defaults to OpenGL2 so as long as you use the same source tree to build the client and server thenm they should be able to connect to eachother regardless of how they're built. > 1) if the client is compiled with openmpi while the remote server with > mpich, will it work? > Yep. > 2) And if both are compiled with openmpi, do the versions of openmpi also > need to be same? > Nope. You can even build the client without any MPI support and the server with whatever MPI version you want. None of that matters for the client and server to properly communicate. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabidi89 at vt.edu Thu Feb 23 13:27:11 2017 From: fabidi89 at vt.edu (Faiz Abidi) Date: Thu, 23 Feb 2017 13:27:11 -0500 Subject: [Paraview] Paraview server and Paraview client versions In-Reply-To: References: Message-ID: Thanks Chuck! It clarifies some things. On Thu, Feb 23, 2017 at 1:21 PM, Chuck Atkins wrote: > > Hi Faiz, > > Quick question - if both compiled from source, what all needs to be same >> for a client and server to connect and render successfully? >> > > They both need to be the same version of paraview and use the same > rendering backend, i.e. OpenGL vs OpenGL2. ParaView now defaults to > OpenGL2 so as long as you use the same source tree to build the client and > server thenm they should be able to connect to eachother regardless of how > they're built. > > > >> 1) if the client is compiled with openmpi while the remote server with >> mpich, will it work? >> > > Yep. > > > >> 2) And if both are compiled with openmpi, do the versions of openmpi also >> need to be same? >> > > Nope. You can even build the client without any MPI support and the > server with whatever MPI version you want. None of that matters for the > client and server to properly communicate. > > - Chuck > -- Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com | +1-540-998-6636 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Feb 23 14:27:29 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 23 Feb 2017 14:27:29 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download Message-ID: Folks, I am pleased to announce that binaries and source code zip files and tar balls for ParaView 5.3.0 Release Candidate 2 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 richard.c.angelini.civ at mail.mil Thu Feb 23 14:57:48 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Thu, 23 Feb 2017 19:57:48 +0000 Subject: [Paraview] [Non-DoD Source] Re: Superbuild repo change? In-Reply-To: <20170222140451.GA22741@megas.kitware.com> References: <20170215163409.GA8112@megas.kitware.com> <20170222140451.GA22741@megas.kitware.com> Message-ID: ?git pull? and ?git submodule update? seem to have worked for 5.3.0-RC2. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Ben Boeckel Reply-To: "ben.boeckel at kitware.com" Date: Wednesday, February 22, 2017 at 9:04 AM To: Rick Angelini Cc: Cory Quammen , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Wed, Feb 22, 2017 at 13:10:04 +0000, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cory - so I did a ?git pull? and ?git submodule update? in my existing > paraview-superbuild repository directory and that 5.3.0-RC1 information > was not in the versions.cmake file. I did a clean ?git clone? and I > then received the correct files. I?m not a git expert - so I?m not > sure why I had to do a clean ?git clone?. I thought I ?git pull? should > have done a proper update. I must be missing something with my > repository update commands ?.. What is the output of the following commands: - git config branch.master.remote - git remote show $output_from_previous_command - git remote show origin --Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From dan.lipsa at kitware.com Thu Feb 23 15:35:14 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Thu, 23 Feb 2017 15:35:14 -0500 Subject: [Paraview] Duplicate Renderview In-Reply-To: <0885637E-AB5E-4083-A3AC-7FEA5AE7AA56@exponent.com> References: <0885637E-AB5E-4083-A3AC-7FEA5AE7AA56@exponent.com> Message-ID: Adam, You can show the same data in different views. Just click on the eye next to the filter which output you want to see. So for instance, if you show the data from the last filter in one view, clicking on the eye next to that filter will show the same thing in the second view. So, the starting point does exactly what you want. Note that the settings for how data is displayed in a view are stored per (filter, view) pair. You can change those by selecting the filter and the view you want and changing the display settings. I hope this helps, Dan On Wed, Feb 22, 2017 at 10:16 AM, Adam Dershowitz wrote: > I have a pipeline setup, with a good renderview. I want to then make a > split view, that is identical, except for the camera angle. When I try to > split my view, or create a new view, they show up empty. I can then start > manually turning on, and coloring everything how I want it. But, it seems > like there should be an option to ?duplicate current pipeline settings? as > a starting point. Then, I could move the camera or make any other changes > that I want from there. > > I did search around in Paraview and on the web, but didn?t find anything. > Is there an easy way to do this? I did find a few other discussions about > this, with suggested scripts, but those fail for me as well. > > I?m using Paraview 5.2, although I also looked around briefly for a way to > do this in 5.3RC1. > > > > Thanks, > > > > -- Adam > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 info at seoaachen.de Thu Feb 23 17:40:04 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Thu, 23 Feb 2017 23:40:04 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: Message-ID: I still try to get pvwebvisualizer running on win 10: C:\Program Files\ParaView 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 2017-02-23 23:38:18+0100 [-] Log opened. 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): 2017-02-23 23:38:18+0100 [-] File "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 219, in 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, protocol=_VisualizerServer) 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", line 185, in start_webserver 2017-02-23 23:38:18+0100 [-] appSession = protocol(types.ComponentConfig(realm = "vtkweb")) 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", line 13, in __init__ 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, config) 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", line 62, in __init__ 2017-02-23 23:38:18+0100 [-] self.initialize() 2017-02-23 23:38:18+0100 [-] File "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 202, in initialize 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", line 314, in __setattr__ 2017-02-23 23:38:19+0100 [-] "to add this attribute.") 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute Camera3DManipulators 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. Am 23.02.2017 um 20:27 schrieb Cory Quammen: > Folks, > > I am pleased to announce that binaries and source code zip files and > tar balls for ParaView 5.3.0 Release Candidate 2 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 > From cory.quammen at kitware.com Thu Feb 23 17:44:06 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 23 Feb 2017 17:44:06 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: Message-ID: Daniel, We have a fix for that particular error coming for 5.3.0 final. Please see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. Cory On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga wrote: > I still try to get pvwebvisualizer running on win 10: > > C:\Program Files\ParaView > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 > 2017-02-23 23:38:18+0100 [-] Log opened. > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): > 2017-02-23 23:38:18+0100 [-] File > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 219, in > > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, > protocol=_VisualizerServer) > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", > line 185, in start_webserver > 2017-02-23 23:38:18+0100 [-] appSession = > protocol(types.ComponentConfig(realm = "vtkweb")) > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", > line 13, in __init__ > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, config) > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", > line 62, in __init__ > 2017-02-23 23:38:18+0100 [-] self.initialize() > 2017-02-23 23:38:18+0100 [-] File > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 202, in > initialize > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > line 314, in __setattr__ > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute Camera3DManipulators > 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. > > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >> >> Folks, >> >> I am pleased to announce that binaries and source code zip files and >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Thu Feb 23 17:50:57 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 15:50:57 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: Message-ID: Cory, should I change pvw-visualizer.py to use "Camera3DManipulator" instead of " Camera3DManipulators"? Or it was just a mistake? Daniel, you can edit that file in the version you've downloaded and remove the "s" in the following line: interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] Let us know if you have a crash like before. Thanks, Seb On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen wrote: > Daniel, > > We have a fix for that particular error coming for 5.3.0 final. Please > see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. > > Cory > > On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga > wrote: > > I still try to get pvwebvisualizer running on win 10: > > > > C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe > > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content > > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 > > 2017-02-23 23:38:18+0100 [-] Log opened. > > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): > > 2017-02-23 23:38:18+0100 [-] File > > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 219, > in > > > > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, > > protocol=_VisualizerServer) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\ > vtk\web\server.py", > > line 185, in start_webserver > > 2017-02-23 23:38:18+0100 [-] appSession = > > protocol(types.ComponentConfig(realm = "vtkweb")) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\ > paraview\web\wamp.py", > > line 13, in __init__ > > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, > config) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\ > vtk\web\wamp.py", > > line 62, in __init__ > > 2017-02-23 23:38:18+0100 [-] self.initialize() > > 2017-02-23 23:38:18+0100 [-] File > > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 202, > in > > initialize > > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = > > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\ > paraview\servermanager.py", > > line 314, in __setattr__ > > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") > > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute > Camera3DManipulators > > 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. > > > > Am 23.02.2017 um 20:27 schrieb Cory Quammen: > >> > >> Folks, > >> > >> I am pleased to announce that binaries and source code zip files and > >> tar balls for ParaView 5.3.0 Release Candidate 2 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 > >> > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Feb 23 17:55:50 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 23 Feb 2017 17:55:50 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: Message-ID: Seb, It was an unintentional backwards incompatibility break. It has been fixed now, so you won't need to make any changes. Your advice to Daniel for RC2 is sound, though. Cory On Thu, Feb 23, 2017 at 5:50 PM, Sebastien Jourdain wrote: > Cory, > > should I change pvw-visualizer.py to use "Camera3DManipulator" instead of > "Camera3DManipulators"? > > Or it was just a mistake? > > Daniel, you can edit that file in the version you've downloaded and remove > the "s" in the following line: > > interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', 'Pan', > 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] > > Let us know if you have a crash like before. > > Thanks, > > Seb > > On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen > wrote: >> >> Daniel, >> >> We have a fix for that particular error coming for 5.3.0 final. Please >> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >> >> Cory >> >> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >> wrote: >> > I still try to get pvwebvisualizer running on win 10: >> > >> > C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >> > 2017-02-23 23:38:18+0100 [-] Log opened. >> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 219, >> > in >> > >> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >> > protocol=_VisualizerServer) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >> > line 185, in start_webserver >> > 2017-02-23 23:38:18+0100 [-] appSession = >> > protocol(types.ComponentConfig(realm = "vtkweb")) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >> > line 13, in __init__ >> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >> > config) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >> > line 62, in __init__ >> > 2017-02-23 23:38:18+0100 [-] self.initialize() >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line 202, >> > in >> > initialize >> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >> > 'Zoom'] >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >> > line 314, in __setattr__ >> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >> > Camera3DManipulators >> > 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. >> > >> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >> >> >> >> Folks, >> >> >> >> I am pleased to announce that binaries and source code zip files and >> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >> >> >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From info at seoaachen.de Thu Feb 23 18:15:44 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 00:15:44 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: Message-ID: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> works now. Btw the documentation is wrong for windows? It should be .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ --port 8080 here: http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: > Cory, > > should I change pvw-visualizer.py to use "Camera3DManipulator" instead > of "Camera3DManipulators"? > > Or it was just a mistake? > > Daniel, you can edit that file in the version you've downloaded and > remove the "s" in the following line: > > interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', > 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] > > Let us know if you have a crash like before. > > Thanks, > > Seb > > On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen > > wrote: > > Daniel, > > We have a fix for that particular error coming for 5.3.0 final. Please > see > https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 > . > > Cory > > On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga > > wrote: > > I still try to get pvwebvisualizer running on win 10: > > > > C:\Program Files\ParaView > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe > > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content > > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 > > 2017-02-23 23:38:18+0100 [-] Log opened. > > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): > > 2017-02-23 23:38:18+0100 [-] File > > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", > line 219, in > > > > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, > > protocol=_VisualizerServer) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", > > line 185, in start_webserver > > 2017-02-23 23:38:18+0100 [-] appSession = > > protocol(types.ComponentConfig(realm = "vtkweb")) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", > > line 13, in __init__ > > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, > config) > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", > > line 62, in __init__ > > 2017-02-23 23:38:18+0100 [-] self.initialize() > > 2017-02-23 23:38:18+0100 [-] File > > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", > line 202, in > > initialize > > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = > > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', > 'Rotate', 'Zoom'] > > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView > > > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", > > line 314, in __setattr__ > > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") > > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute > Camera3DManipulators > > 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. > > > > Am 23.02.2017 um 20:27 schrieb Cory Quammen: > >> > >> Folks, > >> > >> I am pleased to announce that binaries and source code zip > files and > >> tar balls for ParaView 5.3.0 Release Candidate 2 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 > >> > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at seoaachen.de Thu Feb 23 18:26:59 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 00:26:59 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: my --data-dir parameter is wrong. it must be --data data\ ? but also with this no files are listed Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: > works now. Btw the documentation is wrong for windows? It should be > .\bin\pvpython.exe > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content > share\paraview-5.3\web\visualizer\www\ --data-dir data\ --port 8080 > > here: > http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity > > > Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >> Cory, >> >> should I change pvw-visualizer.py to use "Camera3DManipulator" >> instead of "Camera3DManipulators"? >> >> Or it was just a mistake? >> >> Daniel, you can edit that file in the version you've downloaded and >> remove the "s" in the following line: >> >> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', >> 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >> >> Let us know if you have a crash like before. >> >> Thanks, >> >> Seb >> >> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >> > wrote: >> >> Daniel, >> >> We have a fix for that particular error coming for 5.3.0 final. >> Please >> see >> https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 >> . >> >> Cory >> >> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >> > wrote: >> > I still try to get pvwebvisualizer running on win 10: >> > >> > C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >> --content >> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >> > 2017-02-23 23:38:18+0100 [-] Log opened. >> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >> line 219, in >> > >> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >> > protocol=_VisualizerServer) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >> > line 185, in start_webserver >> > 2017-02-23 23:38:18+0100 [-] appSession = >> > protocol(types.ComponentConfig(realm = "vtkweb")) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >> > line 13, in __init__ >> > 2017-02-23 23:38:18+0100 [-] >> wamp.ServerProtocol.__init__(self, config) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >> > line 62, in __init__ >> > 2017-02-23 23:38:18+0100 [-] self.initialize() >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >> line 202, in >> > initialize >> > 2017-02-23 23:38:18+0100 [-] >> interactionProxy.Camera3DManipulators = >> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', >> 'Rotate', 'Zoom'] >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > >> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >> > line 314, in __setattr__ >> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >> Camera3DManipulators >> > 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. >> > >> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >> >> >> >> Folks, >> >> >> >> I am pleased to announce that binaries and source code zip >> files and >> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >> >> >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> >> > >> > Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 Thu Feb 23 18:28:18 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 16:28:18 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: Must be a full path... What is wrong 5.2 vs 5.3? On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga wrote: > my --data-dir parameter is wrong. it must be --data data\ ? > > but also with this no files are listed > > > > Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: > > works now. Btw the documentation is wrong for windows? It should be > .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py > --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ --port > 8080 > > here: http://kitware.github.io/paraviewweb/docs/architecture. > html#Simplicity > > > Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: > > Cory, > > should I change pvw-visualizer.py to use "Camera3DManipulator" instead of > "Camera3DManipulators"? > > Or it was just a mistake? > > Daniel, you can edit that file in the version you've downloaded and remove > the "s" in the following line: > > interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', 'Pan', > 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] > > Let us know if you have a crash like before. > > Thanks, > > Seb > > On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen > wrote: > >> Daniel, >> >> We have a fix for that particular error coming for 5.3.0 final. Please >> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >> >> Cory >> >> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >> wrote: >> > I still try to get pvwebvisualizer running on win 10: >> > >> > C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >> > 2017-02-23 23:38:18+0100 [-] Log opened. >> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >> 219, in >> > >> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >> > protocol=_VisualizerServer) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >> k\web\server.py", >> > line 185, in start_webserver >> > 2017-02-23 23:38:18+0100 [-] appSession = >> > protocol(types.ComponentConfig(realm = "vtkweb")) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >> raview\web\wamp.py", >> > line 13, in __init__ >> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >> config) >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >> k\web\wamp.py", >> > line 62, in __init__ >> > 2017-02-23 23:38:18+0100 [-] self.initialize() >> > 2017-02-23 23:38:18+0100 [-] File >> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >> 202, in >> > initialize >> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >> 'Zoom'] >> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >> raview\servermanager.py", >> > line 314, in __setattr__ >> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >> Camera3DManipulators >> > 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. >> > >> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >> >> >> >> Folks, >> >> >> >> I am pleased to announce that binaries and source code zip files and >> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >> >> >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 sebastien.jourdain at kitware.com Thu Feb 23 18:29:26 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 16:29:26 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: no \ at the end On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Must be a full path... What is wrong 5.2 vs 5.3? > > On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga > wrote: > >> my --data-dir parameter is wrong. it must be --data data\ ? >> >> but also with this no files are listed >> >> >> >> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >> >> works now. Btw the documentation is wrong for windows? It should be >> .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >> --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ --port >> 8080 >> >> here: http://kitware.github.io/paraviewweb/docs/architecture.html# >> Simplicity >> >> >> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >> >> Cory, >> >> should I change pvw-visualizer.py to use "Camera3DManipulator" instead >> of "Camera3DManipulators"? >> >> Or it was just a mistake? >> >> Daniel, you can edit that file in the version you've downloaded and >> remove the "s" in the following line: >> >> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', 'Pan', >> 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >> >> Let us know if you have a crash like before. >> >> Thanks, >> >> Seb >> >> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >> wrote: >> >>> Daniel, >>> >>> We have a fix for that particular error coming for 5.3.0 final. Please >>> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >>> >>> Cory >>> >>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>> wrote: >>> > I still try to get pvwebvisualizer running on win 10: >>> > >>> > C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >>> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >>> > 2017-02-23 23:38:18+0100 [-] File >>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>> 219, in >>> > >>> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >>> > protocol=_VisualizerServer) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>> k\web\server.py", >>> > line 185, in start_webserver >>> > 2017-02-23 23:38:18+0100 [-] appSession = >>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>> raview\web\wamp.py", >>> > line 13, in __init__ >>> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >>> config) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>> k\web\wamp.py", >>> > line 62, in __init__ >>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>> > 2017-02-23 23:38:18+0100 [-] File >>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>> 202, in >>> > initialize >>> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>> 'Zoom'] >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>> raview\servermanager.py", >>> > line 314, in __setattr__ >>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>> Camera3DManipulators >>> > 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. >>> > >>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>> >> >>> >> Folks, >>> >> >>> >> I am pleased to announce that binaries and source code zip files and >>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>> >> >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Please keep messages on-topic and check the ParaView Wiki at: >>> > http://paraview.org/Wiki/ParaView >>> > >>> > Search the list archives at: http://markmail.org/search/?q=ParaView >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 info at seoaachen.de Thu Feb 23 18:32:31 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 00:32:31 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: i tried --data \data data\ \data\ /data \data c:\temp c:\temp\ etc. nothing is listed also there is no webgl support btw Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: > no \ at the end > > On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain > > wrote: > > Must be a full path... What is wrong 5.2 vs 5.3? > > On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga > > wrote: > > my --data-dir parameter is wrong. it must be --data data\ ? > > but also with this no files are listed > > > > Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >> works now. Btw the documentation is wrong for windows? It >> should be >> .\bin\pvpython.exe >> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >> --content share\paraview-5.3\web\visualizer\www\ --data-dir >> data\ --port 8080 >> >> here: >> http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity >> >> >> >> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>> Cory, >>> >>> should I change pvw-visualizer.py to use >>> "Camera3DManipulator" instead of "Camera3DManipulators"? >>> >>> Or it was just a mistake? >>> >>> Daniel, you can edit that file in the version you've >>> downloaded and remove the "s" in the following line: >>> >>> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', >>> 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>> >>> Let us know if you have a crash like before. >>> >>> Thanks, >>> >>> Seb >>> >>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>> > >>> wrote: >>> >>> Daniel, >>> >>> We have a fix for that particular error coming for 5.3.0 >>> final. Please >>> see >>> https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 >>> . >>> >>> Cory >>> >>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>> > wrote: >>> > I still try to get pvwebvisualizer running on win 10: >>> > >>> > C:\Program Files\ParaView >>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>> > >>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>> --content >>> > share\paraview-5.3\web\visualizer\www\ --data data\ >>> --port 8080 >>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent >>> call last): >>> > 2017-02-23 23:38:18+0100 [-] File >>> > >>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>> line 219, in >>> > >>> > 2017-02-23 23:38:18+0100 [-] >>> server.start_webserver(options=args, >>> > protocol=_VisualizerServer) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>> Files\ParaView >>> > >>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >>> > line 185, in start_webserver >>> > 2017-02-23 23:38:18+0100 [-] appSession = >>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>> Files\ParaView >>> > >>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >>> > line 13, in __init__ >>> > 2017-02-23 23:38:18+0100 [-] >>> wamp.ServerProtocol.__init__(self, config) >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>> Files\ParaView >>> > >>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >>> > line 62, in __init__ >>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>> > 2017-02-23 23:38:18+0100 [-] File >>> > >>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>> line 202, in >>> > initialize >>> > 2017-02-23 23:38:18+0100 [-] >>> interactionProxy.Camera3DManipulators = >>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', >>> 'Zoom', 'Rotate', 'Zoom'] >>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>> Files\ParaView >>> > >>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >>> > line 314, in __setattr__ >>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>> Camera3DManipulators >>> > 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. >>> > >>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>> >> >>> >> Folks, >>> >> >>> >> I am pleased to announce that binaries and source >>> code zip files and >>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>> >> >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> >>> > >>> > Please keep messages on-topic and check the ParaView >>> Wiki at: >>> > http://paraview.org/Wiki/ParaView >>> >>> > >>> > Search the list archives at: >>> http://markmail.org/search/?q=ParaView >>> >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> >>> Please keep messages on-topic and check the ParaView >>> Wiki at: http://paraview.org/Wiki/ParaView >>> >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=ParaView >>> >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >> >> >> >> _______________________________________________ >> Powered bywww.kitware.com >> >> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >> >> >> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >> >> >> 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 sebastien.jourdain at kitware.com Thu Feb 23 18:45:28 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 16:45:28 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: No WebGL support in that version. But you can always take the python+web from old paraview if you want the old visualizer. By python, I mean only the file that is passed as argument to pvpython. The webgl rendering will be using vtk-js but we haven't finished porting it to the ParaViewWeb client/server implementation. On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga wrote: > i tried --data > \data > data\ > \data\ > /data > \data > c:\temp > c:\temp\ > etc. > nothing is listed > also there is no webgl support btw > > > Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: > > no \ at the end > > On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Must be a full path... What is wrong 5.2 vs 5.3? >> >> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >> wrote: >> >>> my --data-dir parameter is wrong. it must be --data data\ ? >>> >>> but also with this no files are listed >>> >>> >>> >>> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>> >>> works now. Btw the documentation is wrong for windows? It should be >>> .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>> --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ >>> --port 8080 >>> >>> here: http://kitware.github.io/paraviewweb/docs/architecture.html# >>> Simplicity >>> >>> >>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>> >>> Cory, >>> >>> should I change pvw-visualizer.py to use "Camera3DManipulator" instead >>> of "Camera3DManipulators"? >>> >>> Or it was just a mistake? >>> >>> Daniel, you can edit that file in the version you've downloaded and >>> remove the "s" in the following line: >>> >>> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', >>> 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>> >>> Let us know if you have a crash like before. >>> >>> Thanks, >>> >>> Seb >>> >>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>> wrote: >>> >>>> Daniel, >>>> >>>> We have a fix for that particular error coming for 5.3.0 final. Please >>>> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >>>> >>>> Cory >>>> >>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>>> wrote: >>>> > I still try to get pvwebvisualizer running on win 10: >>>> > >>>> > C:\Program Files\ParaView >>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >>>> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>> 219, in >>>> > >>>> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >>>> > protocol=_VisualizerServer) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>> k\web\server.py", >>>> > line 185, in start_webserver >>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>> raview\web\wamp.py", >>>> > line 13, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >>>> config) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>> k\web\wamp.py", >>>> > line 62, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>> 202, in >>>> > initialize >>>> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>>> 'Zoom'] >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>> raview\servermanager.py", >>>> > line 314, in __setattr__ >>>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>>> Camera3DManipulators >>>> > 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. >>>> > >>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>> >> >>>> >> Folks, >>>> >> >>>> >> I am pleased to announce that binaries and source code zip files and >>>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>>> >> >>>> > >>>> > _______________________________________________ >>>> > Powered by www.kitware.com >>>> > >>>> > Visit other Kitware open-source projects at >>>> > http://www.kitware.com/opensource/opensource.html >>>> > >>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>> > http://paraview.org/Wiki/ParaView >>>> > >>>> > Search the list archives at: http://markmail.org/search/?q=ParaView >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView 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/ParaV >>> iew 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 sebastien.jourdain at kitware.com Thu Feb 23 18:46:56 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 16:46:56 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: C:\temp should have worked if that directory exist. On Thu, Feb 23, 2017 at 4:45 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > No WebGL support in that version. But you can always take the python+web > from old paraview if you want the old visualizer. By python, I mean only > the file that is passed as argument to pvpython. > > The webgl rendering will be using vtk-js but we haven't finished porting > it to the ParaViewWeb client/server implementation. > > On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga > wrote: > >> i tried --data >> \data >> data\ >> \data\ >> /data >> \data >> c:\temp >> c:\temp\ >> etc. >> nothing is listed >> also there is no webgl support btw >> >> >> Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >> >> no \ at the end >> >> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> Must be a full path... What is wrong 5.2 vs 5.3? >>> >>> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >>> wrote: >>> >>>> my --data-dir parameter is wrong. it must be --data data\ ? >>>> >>>> but also with this no files are listed >>>> >>>> >>>> >>>> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>>> >>>> works now. Btw the documentation is wrong for windows? It should be >>>> .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>> --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ >>>> --port 8080 >>>> >>>> here: http://kitware.github.io/paraviewweb/docs/architecture.html# >>>> Simplicity >>>> >>>> >>>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>> >>>> Cory, >>>> >>>> should I change pvw-visualizer.py to use "Camera3DManipulator" instead >>>> of "Camera3DManipulators"? >>>> >>>> Or it was just a mistake? >>>> >>>> Daniel, you can edit that file in the version you've downloaded and >>>> remove the "s" in the following line: >>>> >>>> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', >>>> 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>>> >>>> Let us know if you have a crash like before. >>>> >>>> Thanks, >>>> >>>> Seb >>>> >>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>> > wrote: >>>> >>>>> Daniel, >>>>> >>>>> We have a fix for that particular error coming for 5.3.0 final. Please >>>>> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >>>>> >>>>> Cory >>>>> >>>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>>>> wrote: >>>>> > I still try to get pvwebvisualizer running on win 10: >>>>> > >>>>> > C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>>> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >>>>> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >>>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>> 219, in >>>>> > >>>>> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >>>>> > protocol=_VisualizerServer) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>> k\web\server.py", >>>>> > line 185, in start_webserver >>>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>> raview\web\wamp.py", >>>>> > line 13, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >>>>> config) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>> k\web\wamp.py", >>>>> > line 62, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>> 202, in >>>>> > initialize >>>>> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >>>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>>>> 'Zoom'] >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>> raview\servermanager.py", >>>>> > line 314, in __setattr__ >>>>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>>>> Camera3DManipulators >>>>> > 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. >>>>> > >>>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>>> >> >>>>> >> Folks, >>>>> >> >>>>> >> I am pleased to announce that binaries and source code zip files and >>>>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>>>> >> >>>>> > >>>>> > _______________________________________________ >>>>> > Powered by www.kitware.com >>>>> > >>>>> > Visit other Kitware open-source projects at >>>>> > http://www.kitware.com/opensource/opensource.html >>>>> > >>>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>>> > http://paraview.org/Wiki/ParaView >>>>> > >>>>> > Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> > >>>>> > Follow this link to subscribe/unsubscribe: >>>>> > http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>>> >>>>> -- >>>>> Cory Quammen >>>>> Staff R&D Engineer >>>>> Kitware, Inc. >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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/ParaV >>>> iew 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 sebastien.jourdain at kitware.com Thu Feb 23 18:47:39 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 16:47:39 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: Are you running from the native command line or cygwin? On Thu, Feb 23, 2017 at 4:46 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > C:\temp should have worked if that directory exist. > > On Thu, Feb 23, 2017 at 4:45 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> No WebGL support in that version. But you can always take the python+web >> from old paraview if you want the old visualizer. By python, I mean only >> the file that is passed as argument to pvpython. >> >> The webgl rendering will be using vtk-js but we haven't finished porting >> it to the ParaViewWeb client/server implementation. >> >> On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga >> wrote: >> >>> i tried --data >>> \data >>> data\ >>> \data\ >>> /data >>> \data >>> c:\temp >>> c:\temp\ >>> etc. >>> nothing is listed >>> also there is no webgl support btw >>> >>> >>> Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >>> >>> no \ at the end >>> >>> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain < >>> sebastien.jourdain at kitware.com> wrote: >>> >>>> Must be a full path... What is wrong 5.2 vs 5.3? >>>> >>>> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >>>> wrote: >>>> >>>>> my --data-dir parameter is wrong. it must be --data data\ ? >>>>> >>>>> but also with this no files are listed >>>>> >>>>> >>>>> >>>>> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>>>> >>>>> works now. Btw the documentation is wrong for windows? It should be >>>>> .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>>> --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ >>>>> --port 8080 >>>>> >>>>> here: http://kitware.github.io/paraviewweb/docs/architecture.html# >>>>> Simplicity >>>>> >>>>> >>>>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>>> >>>>> Cory, >>>>> >>>>> should I change pvw-visualizer.py to use "Camera3DManipulator" >>>>> instead of "Camera3DManipulators"? >>>>> >>>>> Or it was just a mistake? >>>>> >>>>> Daniel, you can edit that file in the version you've downloaded and >>>>> remove the "s" in the following line: >>>>> >>>>> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', >>>>> 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>>>> >>>>> Let us know if you have a crash like before. >>>>> >>>>> Thanks, >>>>> >>>>> Seb >>>>> >>>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen < >>>>> cory.quammen at kitware.com> wrote: >>>>> >>>>>> Daniel, >>>>>> >>>>>> We have a fix for that particular error coming for 5.3.0 final. Please >>>>>> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >>>>>> >>>>>> Cory >>>>>> >>>>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>>>>> wrote: >>>>>> > I still try to get pvwebvisualizer running on win 10: >>>>>> > >>>>>> > C:\Program Files\ParaView >>>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>>>> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>>>> --content >>>>>> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >>>>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >>>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>>> 219, in >>>>>> > >>>>>> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >>>>>> > protocol=_VisualizerServer) >>>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>>> k\web\server.py", >>>>>> > line 185, in start_webserver >>>>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>>>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>>> raview\web\wamp.py", >>>>>> > line 13, in __init__ >>>>>> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >>>>>> config) >>>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>>> k\web\wamp.py", >>>>>> > line 62, in __init__ >>>>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>>> 202, in >>>>>> > initialize >>>>>> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators >>>>>> = >>>>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>>>>> 'Zoom'] >>>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>>> raview\servermanager.py", >>>>>> > line 314, in __setattr__ >>>>>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>>>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>>>>> Camera3DManipulators >>>>>> > 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. >>>>>> > >>>>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>>>> >> >>>>>> >> Folks, >>>>>> >> >>>>>> >> I am pleased to announce that binaries and source code zip files >>>>>> and >>>>>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>>>>> >> >>>>>> > >>>>>> > _______________________________________________ >>>>>> > Powered by www.kitware.com >>>>>> > >>>>>> > Visit other Kitware open-source projects at >>>>>> > http://www.kitware.com/opensource/opensource.html >>>>>> > >>>>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>>>> > http://paraview.org/Wiki/ParaView >>>>>> > >>>>>> > Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> > >>>>>> > Follow this link to subscribe/unsubscribe: >>>>>> > http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cory Quammen >>>>>> Staff R&D Engineer >>>>>> Kitware, Inc. >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView 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/mail >>>>> man/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 info at seoaachen.de Thu Feb 23 18:48:16 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 00:48:16 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: c:\temp does not work I run it from windows command line Am 24.02.2017 um 00:47 schrieb Sebastien Jourdain: > Are you running from the native command line or cygwin? > > On Thu, Feb 23, 2017 at 4:46 PM, Sebastien Jourdain > > wrote: > > C:\temp should have worked if that directory exist. > > On Thu, Feb 23, 2017 at 4:45 PM, Sebastien Jourdain > > wrote: > > No WebGL support in that version. But you can always take the > python+web from old paraview if you want the old visualizer. > By python, I mean only the file that is passed as argument to > pvpython. > > The webgl rendering will be using vtk-js but we haven't > finished porting it to the ParaViewWeb client/server > implementation. > > On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga > > wrote: > > i tried --data > \data > data\ > \data\ > /data > \data > c:\temp > c:\temp\ > etc. > nothing is listed > also there is no webgl support btw > > > Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >> no \ at the end >> >> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain >> > > wrote: >> >> Must be a full path... What is wrong 5.2 vs 5.3? >> >> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >> > wrote: >> >> my --data-dir parameter is wrong. it must be >> --data data\ ? >> >> but also with this no files are listed >> >> >> >> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>> works now. Btw the documentation is wrong for >>> windows? It should be >>> .\bin\pvpython.exe >>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>> --content share\paraview-5.3\web\visualizer\www\ >>> --data-dir data\ --port 8080 >>> >>> here: >>> http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity >>> >>> >>> >>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>> Cory, >>>> >>>> should I change pvw-visualizer.py to use >>>> "Camera3DManipulator" instead of >>>> "Camera3DManipulators"? >>>> >>>> Or it was just a mistake? >>>> >>>> Daniel, you can edit that file in the version >>>> you've downloaded and remove the "s" in the >>>> following line: >>>> >>>> interactionProxy.Camera3DManipulators = >>>> ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', >>>> 'Zoom', 'Rotate', 'Zoom'] >>>> >>>> Let us know if you have a crash like before. >>>> >>>> Thanks, >>>> >>>> Seb >>>> >>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>>> >>> > wrote: >>>> >>>> Daniel, >>>> >>>> We have a fix for that particular error >>>> coming for 5.3.0 final. Please >>>> see >>>> https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 >>>> . >>>> >>>> Cory >>>> >>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel >>>> Zuidinga >>> > wrote: >>>> > I still try to get pvwebvisualizer >>>> running on win 10: >>>> > >>>> > C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>> > >>>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>> --content >>>> > share\paraview-5.3\web\visualizer\www\ >>>> --data data\ --port 8080 >>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>> > 2017-02-23 23:38:18+0100 [-] Traceback >>>> (most recent call last): >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > >>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>> line 219, in >>>> > >>>> > 2017-02-23 23:38:18+0100 [-] >>>> server.start_webserver(options=args, >>>> > protocol=_VisualizerServer) >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> "C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >>>> > line 185, in start_webserver >>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>> > protocol(types.ComponentConfig(realm = >>>> "vtkweb")) >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> "C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >>>> > line 13, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] >>>> wamp.ServerProtocol.__init__(self, config) >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> "C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >>>> > line 62, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] >>>> self.initialize() >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > >>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>> line 202, in >>>> > initialize >>>> > 2017-02-23 23:38:18+0100 [-] >>>> interactionProxy.Camera3DManipulators = >>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', >>>> 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> "C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >>>> > line 314, in __setattr__ >>>> > 2017-02-23 23:38:19+0100 [-] "to add >>>> this attribute.") >>>> > 2017-02-23 23:38:19+0100 [-] >>>> AttributeError: Attribute Camera3DManipulators >>>> > 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. >>>> > >>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>> >> >>>> >> Folks, >>>> >> >>>> >> I am pleased to announce that binaries >>>> and source code zip files and >>>> >> tar balls for ParaView 5.3.0 Release >>>> Candidate 2 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 >>>> >> >>>> > >>>> > >>>> _______________________________________________ >>>> > Powered by www.kitware.com >>>> >>>> > >>>> > Visit other Kitware open-source projects at >>>> > >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> > >>>> > Please keep messages on-topic and check >>>> the ParaView Wiki at: >>>> > http://paraview.org/Wiki/ParaView >>>> >>>> > >>>> > Search the list archives at: >>>> http://markmail.org/search/?q=ParaView >>>> >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> >>>> Please keep messages on-topic and check the >>>> ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=ParaView >>>> >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> >>> 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 info at seoaachen.de Thu Feb 23 18:49:57 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 00:49:57 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: does lightviz also not support webgl (in any version)? can you give any rough estimation on the vtk-js porting? Am 24.02.2017 um 00:45 schrieb Sebastien Jourdain: > No WebGL support in that version. But you can always take the > python+web from old paraview if you want the old visualizer. By > python, I mean only the file that is passed as argument to pvpython. > > The webgl rendering will be using vtk-js but we haven't finished > porting it to the ParaViewWeb client/server implementation. > > On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga > wrote: > > i tried --data > \data > data\ > \data\ > /data > \data > c:\temp > c:\temp\ > etc. > nothing is listed > also there is no webgl support btw > > > Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >> no \ at the end >> >> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain >> > > wrote: >> >> Must be a full path... What is wrong 5.2 vs 5.3? >> >> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >> > wrote: >> >> my --data-dir parameter is wrong. it must be --data data\ ? >> >> but also with this no files are listed >> >> >> >> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>> works now. Btw the documentation is wrong for windows? >>> It should be >>> .\bin\pvpython.exe >>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>> --content share\paraview-5.3\web\visualizer\www\ >>> --data-dir data\ --port 8080 >>> >>> here: >>> http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity >>> >>> >>> >>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>> Cory, >>>> >>>> should I change pvw-visualizer.py to use >>>> "Camera3DManipulator" instead of "Camera3DManipulators"? >>>> >>>> Or it was just a mistake? >>>> >>>> Daniel, you can edit that file in the version you've >>>> downloaded and remove the "s" in the following line: >>>> >>>> interactionProxy.Camera3DManipulators = ['Rotate', >>>> 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>>> 'Zoom'] >>>> >>>> Let us know if you have a crash like before. >>>> >>>> Thanks, >>>> >>>> Seb >>>> >>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>>> >>> > wrote: >>>> >>>> Daniel, >>>> >>>> We have a fix for that particular error coming for >>>> 5.3.0 final. Please >>>> see >>>> https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 >>>> . >>>> >>>> Cory >>>> >>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>>> > wrote: >>>> > I still try to get pvwebvisualizer running on win 10: >>>> > >>>> > C:\Program Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>> > >>>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>> --content >>>> > share\paraview-5.3\web\visualizer\www\ --data >>>> data\ --port 8080 >>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most >>>> recent call last): >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > >>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>> line 219, in >>>> > >>>> > 2017-02-23 23:38:18+0100 [-] >>>> server.start_webserver(options=args, >>>> > protocol=_VisualizerServer) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>>> Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >>>> > line 185, in start_webserver >>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>>> Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >>>> > line 13, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] >>>> wamp.ServerProtocol.__init__(self, config) >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>>> Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >>>> > line 62, in __init__ >>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>> > 2017-02-23 23:38:18+0100 [-] File >>>> > >>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>> line 202, in >>>> > initialize >>>> > 2017-02-23 23:38:18+0100 [-] >>>> interactionProxy.Camera3DManipulators = >>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', >>>> 'Zoom', 'Rotate', 'Zoom'] >>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program >>>> Files\ParaView >>>> > >>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >>>> > line 314, in __setattr__ >>>> > 2017-02-23 23:38:19+0100 [-] "to add this >>>> attribute.") >>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: >>>> Attribute Camera3DManipulators >>>> > 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. >>>> > >>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>> >> >>>> >> Folks, >>>> >> >>>> >> I am pleased to announce that binaries and >>>> source code zip files and >>>> >> tar balls for ParaView 5.3.0 Release Candidate 2 >>>> 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 >>>> >> >>>> > >>>> > _______________________________________________ >>>> > Powered by www.kitware.com >>>> > >>>> > Visit other Kitware open-source projects at >>>> > http://www.kitware.com/opensource/opensource.html >>>> >>>> > >>>> > Please keep messages on-topic and check the >>>> ParaView Wiki at: >>>> > http://paraview.org/Wiki/ParaView >>>> >>>> > >>>> > Search the list archives at: >>>> http://markmail.org/search/?q=ParaView >>>> >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> >>>> Please keep messages on-topic and check the >>>> ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=ParaView >>>> >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> >>> 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 robertsawko at gmail.com Thu Feb 23 18:56:29 2017 From: robertsawko at gmail.com (Robert Sawko) Date: Fri, 24 Feb 2017 00:56:29 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> <20170222170122.GA22001@avignon> <20170222172634.GA28684@avignon> Message-ID: <20170223235629.GA7708@avignon> Mathieu, Turned out that Intel was getting in the way... The integrated card was somehow conflicting with the discrete NVidia card and I had to reconfigure my X settings somewhat as described here: https://bbs.archlinux.org/viewtopic.php?id=223435 This problem developed spontaneously though as I definitely had glxgears, paraview etc working before, so I am not exactly sure core dumps suddenly. But I am pleased that I got some more clarity on the way I am using my system. Thanks for all your earlier suggestions. Best wishes, Robert -- Indian in the mountain http://en.wikipedia.org/wiki/Crazy_Horse_Memorial http://en.wikipedia.org/wiki/Korczak_Ziolkowski From sebastien.jourdain at kitware.com Thu Feb 23 19:02:50 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Feb 2017 17:02:50 -0700 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: lightviz does not have any webgl either. Once we get vtk-js with a ParaViewWeb server, then LightViz and Visualizer will be able to get it, but not before that. Regarding the estimate, it is hard to tell as it is dependent on the funding priorities. So far, I've managed to get most of the features I need in vtk-js (~98%) but then when vtk-js is ready, I will need some dedicated time for revisiting the server side and client side to deal with geometry rendering. I'm hoping 6-12 months but without any guaranty. Unless we get funding specifically for that, in which case it could be way sooner. On Thu, Feb 23, 2017 at 4:49 PM, Daniel Zuidinga wrote: > does lightviz also not support webgl (in any version)? > > can you give any rough estimation on the vtk-js porting? > > Am 24.02.2017 um 00:45 schrieb Sebastien Jourdain: > > No WebGL support in that version. But you can always take the python+web > from old paraview if you want the old visualizer. By python, I mean only > the file that is passed as argument to pvpython. > > The webgl rendering will be using vtk-js but we haven't finished porting > it to the ParaViewWeb client/server implementation. > > On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga > wrote: > >> i tried --data >> \data >> data\ >> \data\ >> /data >> \data >> c:\temp >> c:\temp\ >> etc. >> nothing is listed >> also there is no webgl support btw >> >> >> Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >> >> no \ at the end >> >> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> Must be a full path... What is wrong 5.2 vs 5.3? >>> >>> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >>> wrote: >>> >>>> my --data-dir parameter is wrong. it must be --data data\ ? >>>> >>>> but also with this no files are listed >>>> >>>> >>>> >>>> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>>> >>>> works now. Btw the documentation is wrong for windows? It should be >>>> .\bin\pvpython.exe share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>> --content share\paraview-5.3\web\visualizer\www\ --data-dir data\ >>>> --port 8080 >>>> >>>> here: http://kitware.github.io/paraviewweb/docs/architecture.html# >>>> Simplicity >>>> >>>> >>>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>> >>>> Cory, >>>> >>>> should I change pvw-visualizer.py to use "Camera3DManipulator" instead >>>> of "Camera3DManipulators"? >>>> >>>> Or it was just a mistake? >>>> >>>> Daniel, you can edit that file in the version you've downloaded and >>>> remove the "s" in the following line: >>>> >>>> interactionProxy.Camera3DManipulators = ['Rotate', 'Pan', 'Zoom', >>>> 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>>> >>>> Let us know if you have a crash like before. >>>> >>>> Thanks, >>>> >>>> Seb >>>> >>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>> > wrote: >>>> >>>>> Daniel, >>>>> >>>>> We have a fix for that particular error coming for 5.3.0 final. Please >>>>> see https://gitlab.kitware.com/paraview/paraview/merge_requests/1415. >>>>> >>>>> Cory >>>>> >>>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel Zuidinga >>>>> wrote: >>>>> > I still try to get pvwebvisualizer running on win 10: >>>>> > >>>>> > C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>>> > share\paraview-5.3\web\visualizer\server\pvw-visualizer.py --content >>>>> > share\paraview-5.3\web\visualizer\www\ --data data\ --port 8080 >>>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most recent call last): >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>> 219, in >>>>> > >>>>> > 2017-02-23 23:38:18+0100 [-] server.start_webserver(options=args, >>>>> > protocol=_VisualizerServer) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>> k\web\server.py", >>>>> > line 185, in start_webserver >>>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>>> > protocol(types.ComponentConfig(realm = "vtkweb")) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>> raview\web\wamp.py", >>>>> > line 13, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] wamp.ServerProtocol.__init__(self, >>>>> config) >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vt >>>>> k\web\wamp.py", >>>>> > line 62, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", line >>>>> 202, in >>>>> > initialize >>>>> > 2017-02-23 23:38:18+0100 [-] interactionProxy.Camera3DManipulators = >>>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', 'Rotate', >>>>> 'Zoom'] >>>>> > 2017-02-23 23:38:18+0100 [-] File "C:\Program Files\ParaView >>>>> > 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\pa >>>>> raview\servermanager.py", >>>>> > line 314, in __setattr__ >>>>> > 2017-02-23 23:38:19+0100 [-] "to add this attribute.") >>>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: Attribute >>>>> Camera3DManipulators >>>>> > 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. >>>>> > >>>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>>> >> >>>>> >> Folks, >>>>> >> >>>>> >> I am pleased to announce that binaries and source code zip files and >>>>> >> tar balls for ParaView 5.3.0 Release Candidate 2 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 >>>>> >> >>>>> > >>>>> > _______________________________________________ >>>>> > Powered by www.kitware.com >>>>> > >>>>> > Visit other Kitware open-source projects at >>>>> > http://www.kitware.com/opensource/opensource.html >>>>> > >>>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>>> > http://paraview.org/Wiki/ParaView >>>>> > >>>>> > Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> > >>>>> > Follow this link to subscribe/unsubscribe: >>>>> > http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>>> >>>>> -- >>>>> Cory Quammen >>>>> Staff R&D Engineer >>>>> Kitware, Inc. >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView 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/ParaV >>>> iew 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/ParaV >> iew Search the list archives at: http://markmail.org/search/?q=ParaView >> Follow this link to subscribe/unsubscribe: http://public.kitware.com/mail >> man/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at seoaachen.de Thu Feb 23 19:07:04 2017 From: info at seoaachen.de (Daniel Zuidinga) Date: Fri, 24 Feb 2017 01:07:04 +0100 Subject: [Paraview] ParaView 5.3.0 Release Candidate 2 binaries are available for download In-Reply-To: References: <601bcf91-b3b7-6d97-6129-d12314c687bf@seoaachen.de> Message-ID: <691f3c38-e127-2c50-d585-d5997c3bdb86@seoaachen.de> ok. thanks for your answer. unfortunately I have no money for funding. Also helping with the code seems to be quite complex because one have to understand nearly the whole code Am 24.02.2017 um 01:02 schrieb Sebastien Jourdain: > lightviz does not have any webgl either. > > Once we get vtk-js with a ParaViewWeb server, then LightViz and > Visualizer will be able to get it, but not before that. > > Regarding the estimate, it is hard to tell as it is dependent on the > funding priorities. > So far, I've managed to get most of the features I need in vtk-js > (~98%) but then when vtk-js is ready, > I will need some dedicated time for revisiting the server side and > client side to deal with geometry rendering. > I'm hoping 6-12 months but without any guaranty. Unless we get funding > specifically for that, in which case it could be way sooner. > > On Thu, Feb 23, 2017 at 4:49 PM, Daniel Zuidinga > wrote: > > does lightviz also not support webgl (in any version)? > > can you give any rough estimation on the vtk-js porting? > > Am 24.02.2017 um 00:45 schrieb Sebastien Jourdain: >> No WebGL support in that version. But you can always take the >> python+web from old paraview if you want the old visualizer. By >> python, I mean only the file that is passed as argument to pvpython. >> >> The webgl rendering will be using vtk-js but we haven't finished >> porting it to the ParaViewWeb client/server implementation. >> >> On Thu, Feb 23, 2017 at 4:32 PM, Daniel Zuidinga >> > wrote: >> >> i tried --data >> \data >> data\ >> \data\ >> /data >> \data >> c:\temp >> c:\temp\ >> etc. >> nothing is listed >> also there is no webgl support btw >> >> >> Am 24.02.2017 um 00:29 schrieb Sebastien Jourdain: >>> no \ at the end >>> >>> On Thu, Feb 23, 2017 at 4:28 PM, Sebastien Jourdain >>> >> > wrote: >>> >>> Must be a full path... What is wrong 5.2 vs 5.3? >>> >>> On Thu, Feb 23, 2017 at 4:26 PM, Daniel Zuidinga >>> > wrote: >>> >>> my --data-dir parameter is wrong. it must be --data >>> data\ ? >>> >>> but also with this no files are listed >>> >>> >>> >>> Am 24.02.2017 um 00:15 schrieb Daniel Zuidinga: >>>> works now. Btw the documentation is wrong for >>>> windows? It should be >>>> .\bin\pvpython.exe >>>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>> --content share\paraview-5.3\web\visualizer\www\ >>>> --data-dir data\ --port 8080 >>>> >>>> here: >>>> http://kitware.github.io/paraviewweb/docs/architecture.html#Simplicity >>>> >>>> >>>> >>>> Am 23.02.2017 um 23:50 schrieb Sebastien Jourdain: >>>>> Cory, >>>>> >>>>> should I change pvw-visualizer.py to use >>>>> "Camera3DManipulator" instead of >>>>> "Camera3DManipulators"? >>>>> >>>>> Or it was just a mistake? >>>>> >>>>> Daniel, you can edit that file in the version >>>>> you've downloaded and remove the "s" in the >>>>> following line: >>>>> >>>>> interactionProxy.Camera3DManipulators = ['Rotate', >>>>> 'Pan', 'Zoom', 'Pan', 'Roll', 'Pan', 'Zoom', >>>>> 'Rotate', 'Zoom'] >>>>> >>>>> Let us know if you have a crash like before. >>>>> >>>>> Thanks, >>>>> >>>>> Seb >>>>> >>>>> On Thu, Feb 23, 2017 at 3:44 PM, Cory Quammen >>>>> >>>> > wrote: >>>>> >>>>> Daniel, >>>>> >>>>> We have a fix for that particular error coming >>>>> for 5.3.0 final. Please >>>>> see >>>>> https://gitlab.kitware.com/paraview/paraview/merge_requests/1415 >>>>> . >>>>> >>>>> Cory >>>>> >>>>> On Thu, Feb 23, 2017 at 5:40 PM, Daniel >>>>> Zuidinga >>>> > wrote: >>>>> > I still try to get pvwebvisualizer running >>>>> on win 10: >>>>> > >>>>> > C:\Program Files\ParaView >>>>> > >>>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit>.\bin\pvpython.exe >>>>> > >>>>> share\paraview-5.3\web\visualizer\server\pvw-visualizer.py >>>>> --content >>>>> > share\paraview-5.3\web\visualizer\www\ >>>>> --data data\ --port 8080 >>>>> > 2017-02-23 23:38:18+0100 [-] Log opened. >>>>> > 2017-02-23 23:38:18+0100 [-] Traceback (most >>>>> recent call last): >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > >>>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>>> line 219, in >>>>> > >>>>> > 2017-02-23 23:38:18+0100 [-] >>>>> server.start_webserver(options=args, >>>>> > protocol=_VisualizerServer) >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> "C:\Program Files\ParaView >>>>> > >>>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\server.py", >>>>> > line 185, in start_webserver >>>>> > 2017-02-23 23:38:18+0100 [-] appSession = >>>>> > protocol(types.ComponentConfig(realm = >>>>> "vtkweb")) >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> "C:\Program Files\ParaView >>>>> > >>>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\web\wamp.py", >>>>> > line 13, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] >>>>> wamp.ServerProtocol.__init__(self, config) >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> "C:\Program Files\ParaView >>>>> > >>>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\vtk\web\wamp.py", >>>>> > line 62, in __init__ >>>>> > 2017-02-23 23:38:18+0100 [-] self.initialize() >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> > >>>>> "share\paraview-5.3\web\visualizer\server\pvw-visualizer.py", >>>>> line 202, in >>>>> > initialize >>>>> > 2017-02-23 23:38:18+0100 [-] >>>>> interactionProxy.Camera3DManipulators = >>>>> > ['Rotate', 'Pan', 'Zoom', 'Pan', 'Roll', >>>>> 'Pan', 'Zoom', 'Rotate', 'Zoom'] >>>>> > 2017-02-23 23:38:18+0100 [-] File >>>>> "C:\Program Files\ParaView >>>>> > >>>>> 5.3.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\paraview\servermanager.py", >>>>> > line 314, in __setattr__ >>>>> > 2017-02-23 23:38:19+0100 [-] "to add >>>>> this attribute.") >>>>> > 2017-02-23 23:38:19+0100 [-] AttributeError: >>>>> Attribute Camera3DManipulators >>>>> > 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. >>>>> > >>>>> > Am 23.02.2017 um 20:27 schrieb Cory Quammen: >>>>> >> >>>>> >> Folks, >>>>> >> >>>>> >> I am pleased to announce that binaries and >>>>> source code zip files and >>>>> >> tar balls for ParaView 5.3.0 Release >>>>> Candidate 2 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 >>>>> >> >>>>> > >>>>> > _______________________________________________ >>>>> > Powered by www.kitware.com >>>>> >>>>> > >>>>> > Visit other Kitware open-source projects at >>>>> > >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> > >>>>> > Please keep messages on-topic and check the >>>>> ParaView Wiki at: >>>>> > http://paraview.org/Wiki/ParaView >>>>> >>>>> > >>>>> > Search the list archives at: >>>>> http://markmail.org/search/?q=ParaView >>>>> >>>>> > >>>>> > Follow this link to subscribe/unsubscribe: >>>>> > >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Cory Quammen >>>>> Staff R&D Engineer >>>>> Kitware, Inc. >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> >>>>> Please keep messages on-topic and check the >>>>> ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> >>>>> Search the list archives at: >>>>> http://markmail.org/search/?q=ParaView >>>>> >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered bywww.kitware.com >>>> >>>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>>> >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>>> >>>> >>>> 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 rccm.kyoshimi at gmail.com Fri Feb 24 02:27:58 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Fri, 24 Feb 2017 16:27:58 +0900 Subject: [Paraview] Coloring with vtkBlockColors Message-ID: Hello all, I have a question over making a ParaView plugin. I try to set coloring with "vtkBlockColors" for a multi-block data set by conventional method: ----- vtkPVDataSetAttributesInformation* attrInfo = dataInfo->GetFieldDataInformation(); vtkPVArrayInformation* arrayInfo = attrInfo->GetArrayInformation(name); vtkSMPVRepresentationProxy::SetScalarColoring(repr->getProxy(), "vtkBlockColors", vtkDataObject::FIELD); ----- But the above arrayInfo is always NULL though there exists a "vtkBlockColors" in field selection combo box with ParaView. I'd like to know the right way to do it. Kind regards, yoshimi From mathieu.westphal at kitware.com Fri Feb 24 03:29:48 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 24 Feb 2017 09:29:48 +0100 Subject: [Paraview] Paraview closes with a core dump In-Reply-To: <20170223235629.GA7708@avignon> References: <20170222131230.GA6970@avignon> <20170222133626.GA29359@avignon> <20170222164926.GA15369@avignon> <20170222170122.GA22001@avignon> <20170222172634.GA28684@avignon> <20170223235629.GA7708@avignon> Message-ID: Great, happy to help. Mathieu Westphal On Fri, Feb 24, 2017 at 12:56 AM, Robert Sawko wrote: > Mathieu, > > Turned out that Intel was getting in the way... The integrated card was > somehow > conflicting with the discrete NVidia card and I had to reconfigure my X > settings somewhat as described here: > > https://bbs.archlinux.org/viewtopic.php?id=223435 > > This problem developed spontaneously though as I definitely had glxgears, > paraview etc working before, so I am not exactly sure core dumps suddenly. > But > I am pleased that I got some more clarity on the way I am using my system. > > Thanks for all your earlier suggestions. > > Best wishes, > Robert > -- > Indian in the mountain > http://en.wikipedia.org/wiki/Crazy_Horse_Memorial > http://en.wikipedia.org/wiki/Korczak_Ziolkowski > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.dimitrova at helsinki.fi Fri Feb 24 04:54:18 2017 From: maria.dimitrova at helsinki.fi (Dimitrova, Maria) Date: Fri, 24 Feb 2017 09:54:18 +0000 Subject: [Paraview] Extracting the Cartesian coordinates of points Message-ID: Dear all, I was looking for a way to find the coordinates of a point where I click on and came across this example for a programmable filter. https://xrunhprof.wordpress.com/2012/07/17/display-point-coordinates-in-paraview/ Display point coordinates in Paraview | XRunHProf xrunhprof.wordpress.com Here is how to display point coordinates in Paraview. First create a programmable filter with the following code: Then select points and enable point ... I made the filter for a vti source where there is a 3D array of the x, y and z components of induced currents. I chose Points representation and tried selecting points but no coordinates appear on the screen. It seems that neither of the selection tools can help, even though I see that points are being selected because they get coloured in magenta. Do you have any advise what could be wrong? Paraview 5.2.0 MPI, OpenGL running on Windows 10. Best regards, Maria -------------- next part -------------- An HTML attachment was scrubbed... URL: From archaerolog at mail.ru Fri Feb 24 05:27:02 2017 From: archaerolog at mail.ru (Gena Bug) Date: Fri, 24 Feb 2017 13:27:02 +0300 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> Message-ID: <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> 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 yzhzhang at ipe.ac.cn Fri Feb 24 07:24:28 2017 From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=) Date: Fri, 24 Feb 2017 20:24:28 +0800 (GMT+08:00) Subject: [Paraview] How to save a high-resolution image that contains a selected region of the viewport? Message-ID: <15c95ef.1675.15a70146209.Coremail.yzhzhang@ipe.ac.cn> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Feb 24 11:02:10 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 24 Feb 2017 16:02:10 +0000 Subject: [Paraview] Extracting the Cartesian coordinates of points Message-ID: Maria, I'm not sure if you want nodal coordinates or induced current components but either way you could get them as: Calculator filter - make a vector from your desired components like: Name: coordinates Expression: coords_X*iHat+coords_Y*jHat+coords_Z*kHat Then use Selection Display Inspector to select coordinates as Point Labels. Then Interactive Select Points On and you should get the 3 numbers you want. Hope this helps. Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvan.fournier at free.fr Fri Feb 24 12:25:14 2017 From: yvan.fournier at free.fr (yvan.fournier at free.fr) Date: Fri, 24 Feb 2017 18:25:14 +0100 (CET) Subject: [Paraview] Issues with OpenGL2 support for off-screen Mesa In-Reply-To: Message-ID: <1610574620.163154086.1487957114108.JavaMail.root@zimbra10-e2> 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 wascott at sandia.gov Fri Feb 24 16:53:42 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 24 Feb 2017 21:53:42 +0000 Subject: [Paraview] Current time in the calculator Message-ID: <57ae3090838a4b6bb8395d044ef274e8@ES01AMSNLNT.srn.sandia.gov> >From a customer: Is there any way to use the current time as a scalar in the Calculator field? I have in mind calculating cos( coorX * time) Thanks! Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Sun Feb 26 04:25:22 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Sun, 26 Feb 2017 10:25:22 +0100 Subject: [Paraview] PV 5.3-RC.2 build error on macOS 10.12 Message-ID: I raised the following issue: https://gitlab.kitware.com/paraview/paraview-superbuild/issues/47 First I build the current superbuild master on macOS 10.12 which built PV 5.2 with qt 5.8.0 without problems. Then I switched the source to PV 5.3-RC.2 and got the following error 89%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/moc_pqRepresentation.cpp.o /Users/fwein/code/cfs_paraview/manual_53/build/superbuild/paraview/build/Qt/Core/moc_pqQVTKWidget.cpp:85:8: error: use of undeclared identifier 'QVTKWidget'; did you mean 'pqQVTKWidget'? { &QVTKWidget::staticMetaObject, qt_meta_stringdata_pqQVTKWidget.data, ^~~~~~~~~~ pqQVTKWidget Regards, Fabian From u.utku.turuncoglu at be.itu.edu.tr Sun Feb 26 05:12:07 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Sun, 26 Feb 2017 12:12:07 +0200 (EET) Subject: [Paraview] tracking an object ... Message-ID: <49735.85.110.172.127.1488103927.squirrel@webmail.be.itu.edu.tr> Hi All, I just wonder that is there anybody used following Python code with latest version of the ParaView (5.2) to track object. http://www.paraview.org/Wiki/ParaView/Python/Tracking_an_object_during_animation When i try to run the script under Python shell (after selecting object using ExtractSelection filter), i am getting following error, Traceback (most recent call last): File "", line 28, in File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/servermanager.py", line 308, in __setattr__ "to add this attribute.") AttributeError: Attribute Caching 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. My first impression is that the script can be little bit outdated because article is written in 2011. So, any suggestion might help at this point. Thanks, Regards, --ufuk From utkarsh.ayachit at kitware.com Sun Feb 26 09:51:49 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Feb 2017 09:51:49 -0500 Subject: [Paraview] PV 5.3-RC.2 build error on macOS 10.12 In-Reply-To: References: Message-ID: Is this a clean build? I'd suggest doing a clean build. I suspect the moc file didn't get regenerated or something like that. On Sun, Feb 26, 2017 at 4:25 AM, Fabian Wein wrote: > I raised the following issue: https://gitlab.kitware.com/paraview/paraview-superbuild/issues/47 > > First I build the current superbuild master on macOS 10.12 which built PV 5.2 with qt 5.8.0 without problems. Then I switched the source to PV 5.3-RC.2 and got the following error > > 89%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/moc_pqRepresentation.cpp.o > /Users/fwein/code/cfs_paraview/manual_53/build/superbuild/paraview/build/Qt/Core/moc_pqQVTKWidget.cpp:85:8: error: use of undeclared identifier 'QVTKWidget'; did you mean 'pqQVTKWidget'? > { &QVTKWidget::staticMetaObject, qt_meta_stringdata_pqQVTKWidget.data, > ^~~~~~~~~~ > pqQVTKWidget > > Regards, > > 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 cory.quammen at kitware.com Sun Feb 26 10:00:11 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 26 Feb 2017 10:00:11 -0500 Subject: [Paraview] tracking an object ... In-Reply-To: <49735.85.110.172.127.1488103927.squirrel@webmail.be.itu.edu.tr> References: <49735.85.110.172.127.1488103927.squirrel@webmail.be.itu.edu.tr> Message-ID: The attribute generating the error message is not included in the error, so it is hard to know what the specific problem is with the script (I haven't tried running it myself). Another way to do this is with the following. * View menu -> Animation view * To the right of the blue '+' sign, select Camera, and in the combo box to the right of that, select "Follow Data". Click on the blue '+' sign. * Now run the animation. The camera will be centered on the bounds of the all the data in the scene as the animation progresses. HTH, Cory On Sun, Feb 26, 2017 at 5:12 AM, wrote: > Hi All, > > I just wonder that is there anybody used following Python code with latest > version of the ParaView (5.2) to track object. > > http://www.paraview.org/Wiki/ParaView/Python/Tracking_an_object_during_animation > > When i try to run the script under Python shell (after selecting object > using ExtractSelection filter), i am getting following error, > > Traceback (most recent call last): > File "", line 28, in > File > "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/servermanager.py", > line 308, in __setattr__ > "to add this attribute.") > AttributeError: Attribute Caching 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. > > My first impression is that the script can be little bit outdated because > article is written in 2011. So, any suggestion might help at this point. > 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Sun Feb 26 10:16:35 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Feb 2017 10:16:35 -0500 Subject: [Paraview] Current time in the calculator In-Reply-To: <57ae3090838a4b6bb8395d044ef274e8@ES01AMSNLNT.srn.sandia.gov> References: <57ae3090838a4b6bb8395d044ef274e8@ES01AMSNLNT.srn.sandia.gov> Message-ID: Not in *Calculator*, but with *Python Calculator*, you can use the following expression: cos(inputs[0].Points[:,0] * *time_value*) Utkarsh On Fri, Feb 24, 2017 at 4:53 PM, Scott, W Alan wrote: > From a customer: > > > > > > Is there any way to use the current time as a scalar in the Calculator > field? > > > > I have in mind calculating cos( coorX * time) > > > > > > 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 utkarsh.ayachit at kitware.com Sun Feb 26 12:07:01 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Feb 2017 12:07:01 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> Message-ID: 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 >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: locale.patch Type: text/x-patch Size: 865 bytes Desc: not available URL: From rca19_geek at outlook.com Sun Feb 26 14:42:57 2017 From: rca19_geek at outlook.com (Rick Angelini) Date: Sun, 26 Feb 2017 19:42:57 +0000 Subject: [Paraview] PVSB on Mac OSX 10.12 Message-ID: I'm building PV 5.3-RC2 on a Mac OSX 10.12 and the build is getting hosed. (the build fails while building ParaView, can't find a missing include file). When PVSB configures Paraview, it is setting the cmake flag VTK_USE_SYSTEM_PNG=ON and it should be OFF. In the top level cmake, the value is set to OFF. 292 mac> grep PNG CMakeCache.txt VTK_USE_SYSTEM_PNG:UNINITIALIZED=OFF If I re-run cmake in the paraview build directory and turn off VTK_USE_SYSTEM_PNG, I get a clean build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabian.wein at fau.de Sun Feb 26 15:08:18 2017 From: fabian.wein at fau.de (Fabian Wein) Date: Sun, 26 Feb 2017 21:08:18 +0100 Subject: [Paraview] PV 5.3-RC.2 build error on macOS 10.12 In-Reply-To: References: Message-ID: <501B220D-83F0-4DD8-82CF-7A847BE24F92@fau.de> Works with a clean build, should have checked by myself :( Regards, Fabian > Am 26.02.2017 um 15:51 schrieb Utkarsh Ayachit : > > Is this a clean build? I'd suggest doing a clean build. I suspect the > moc file didn't get regenerated or something like that. > > On Sun, Feb 26, 2017 at 4:25 AM, Fabian Wein wrote: >> I raised the following issue: https://gitlab.kitware.com/paraview/paraview-superbuild/issues/47 >> >> First I build the current superbuild master on macOS 10.12 which built PV 5.2 with qt 5.8.0 without problems. Then I switched the source to PV 5.3-RC.2 and got the following error >> >> 89%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/moc_pqRepresentation.cpp.o >> /Users/fwein/code/cfs_paraview/manual_53/build/superbuild/paraview/build/Qt/Core/moc_pqQVTKWidget.cpp:85:8: error: use of undeclared identifier 'QVTKWidget'; did you mean 'pqQVTKWidget'? >> { &QVTKWidget::staticMetaObject, qt_meta_stringdata_pqQVTKWidget.data, >> ^~~~~~~~~~ >> pqQVTKWidget >> >> Regards, >> >> 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 archaerolog at mail.ru Sun Feb 26 15:11:56 2017 From: archaerolog at mail.ru (Gena Bug) Date: Sun, 26 Feb 2017 23:11:56 +0300 Subject: [Paraview] 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> Message-ID: On 02/26/17 20:07, Utkarsh Ayachit wrote: > Gena, > > Can you please try if the attached patch fixes the issue? Yep! But it'll be only tomorrow.. > > 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 >>>> >>> >> > > > locale.patch > > > diff --git a/CMake/branded_paraview_main.cxx.in b/CMake/branded_paraview_main.cxx.in > index 9af8446..b965f19 100644 > --- a/CMake/branded_paraview_main.cxx.in > +++ b/CMake/branded_paraview_main.cxx.in > @@ -38,6 +38,7 @@ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > > #include > #include > +#include > > #include "pq at BPC_NAME@Initializer.h" > #include "vtkPVConfig.h" > @@ -104,10 +105,8 @@ int main(int argc, char* argv[]) > #endif > #endif > > - // We force LC_NUMERIC to C - it is important as Qt sets locale to the user's > - // environment locale value and this might break some basic features like > - // the calls to atof() that are locale dependent. > - vtksys::SystemTools::PutEnv("LC_NUMERIC=C"); > + std::setlocale(LC_NUMERIC, LC_CTYPE); > + QLocale::setDefault(QLocale::c()); > > QApplication qtapp(argc, argv); > > From bdutta at vt.edu Mon Feb 27 04:34:06 2017 From: bdutta at vt.edu (Bishwajit Dutta) Date: Mon, 27 Feb 2017 04:34:06 -0500 Subject: [Paraview] Query on Paraview CPU vs GPU acceleration Message-ID: Hi All, I am trying to compile and run Paraview 5.0.1 with both CPU and GPU acceleration on ubuntu server with NVIDIA cards. I am able to successfully run a pvpython script. However in both below cases I am able to see CPU power getting consumed when the script is run. I am confused on the accelerator being used. For GPU: ======= I compiled with the below options: 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 For CPU: ======== I compiled mesa, glu libs etc. and the compiled Paraview with the below options I run the script with #pvpython --mesa-llvm 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 Thanks in advance for help on this. If this all is running in CPU then how do I compile it for GPU without x-windows (i.e. on server) BR, Bishwajit -------------- next part -------------- An HTML attachment was scrubbed... URL: From rccm.kyoshimi at gmail.com Mon Feb 27 06:13:58 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Mon, 27 Feb 2017 20:13:58 +0900 Subject: [Paraview] Coloring with vtkBlockColors In-Reply-To: References: Message-ID: Hi, In order to color blocks by "vtkBlockColors", I just need to call SetScalarColoring() like below: vtkSMPVRepresentationProxy::SetScalarColoring(repr->getProxy(), "vtkBlockColors", vtkDataObject::FIELD); This may work even if "vtkBlockColors" array info is not contained in vtkPVDataSetAttributesInformation although I do skip in this case. Thanks, yoshimi > Hello all, > > I have a question over making a ParaView plugin. I try to set coloring > with "vtkBlockColors" for a multi-block data set by conventional > method: > ----- > vtkPVDataSetAttributesInformation* attrInfo = > dataInfo->GetFieldDataInformation(); > vtkPVArrayInformation* arrayInfo = attrInfo->GetArrayInformation(name); > vtkSMPVRepresentationProxy::SetScalarColoring(repr->getProxy(), > "vtkBlockColors", vtkDataObject::FIELD); > ----- > But the above arrayInfo is always NULL though there exists a > "vtkBlockColors" in field selection combo box with ParaView. > > I'd like to know the right way to do it. > > Kind regards, > yoshimi From richard.c.angelini.civ at mail.mil Mon Feb 27 08:24:05 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Mon, 27 Feb 2017 13:24:05 +0000 Subject: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 In-Reply-To: References: Message-ID: A build using the same cmake command completes without the VTK_USE_SYSTEM_PNG problem on an OSX 10.11 system. Both systems are running the Xcode 8.2.1. I tried both cmake 3.6.3 and 3.7.2 on the OX 10.12 system and both versions result in the same cmake configuration problem, so it appears to be an issue specific to OS X 10.12 ? ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 From: ParaView on behalf of Rick Angelini Date: Sunday, February 26, 2017 at 2:42 PM To: "paraview at paraview.org" Subject: [Non-DoD Source] [Paraview] PVSB on Mac OSX 10.12 I'm building PV 5.3-RC2 on a Mac OSX 10.12 and the build is getting hosed. (the build fails while building ParaView, can't find a missing include file). When PVSB configures Paraview, it is setting the cmake flag VTK_USE_SYSTEM_PNG=ON and it should be OFF. In the top level cmake, the value is set to OFF. 292 mac> grep PNG CMakeCache.txt VTK_USE_SYSTEM_PNG:UNINITIALIZED=OFF If I re-run cmake in the paraview build directory and turn off VTK_USE_SYSTEM_PNG, I get a clean build. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From chuck.atkins at kitware.com Mon Feb 27 09:03:26 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 27 Feb 2017 09:03:26 -0500 Subject: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 In-Reply-To: References: Message-ID: Hi Rick, > When PVSB configures Paraview, it is setting the cmake flag > VTK_USE_SYSTEM_PNG=ON and it should be OFF. > When using the superbuild, ParaView should always be using a "system" PNG. The diggerence is whether that will be provided by the OS or the superbuild. Either way, it's external to the paraview subproject. Try explicitly setting -DUSE_SYSTEM_png=OFF when configuring the superbuild. I'll look into why the superbuild doesn't properly handle this in the first palce but explicitl;y setting the option should make your build work. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Feb 27 09:08:55 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 27 Feb 2017 09:08:55 -0500 Subject: [Paraview] Query on Paraview CPU vs GPU acceleration In-Reply-To: References: Message-ID: Hi Bishwajit, > However in both below cases I am able to see CPU power getting consumed > when the script is run. > It looks like your GPU build isn't actually building against the GPU. In order to use the GPU with the NVidia driver, you either need to use an X server or use EGL. -DVTK_USE_X=OFF > In this case, you have disabled X but not enabled EGL so you're left with OSMesa when you really intended to use the GPU instead. See https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/ for more details on configuring ParaView to use EGL. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From adershowitz at exponent.com Mon Feb 27 10:56:04 2017 From: adershowitz at exponent.com (Adam Dershowitz) Date: Mon, 27 Feb 2017 15:56:04 +0000 Subject: [Paraview] Duplicate Renderview In-Reply-To: References: <0885637E-AB5E-4083-A3AC-7FEA5AE7AA56@exponent.com> Message-ID: Maybe my question wasn?t clear. What I want to know is if there is any way to copy the settings from one view to another. For example if I turn on the visibility of a few filters (click on the eye) and then turn off others, and, finally make some other changes such as coloring of object I can set up a view that I like. Next, I want to start from that identical view to the one that I setup, but just move the camera from that view. So, I want to setup things how I want (filter visibility, colors etc) then make a second view that is a copy of that first view. Then, I want to start from that second view to move my camera etc. As you indicate below, I can edit things in a view and change the visibility in each view. But, I already have a view that I like, and now I want to make that into a split view with the identical visibility etc. Do, I have to manually start turning on and off all of the filter visibility etc? What I am looking for is ?copy current pipeline visibility? and then apply that to another view. Or, ?create new view as copy of current view? Then, I can start making changes from that point. I don?t see a way to do that. Thanks, -- Adam From: Dan Lipsa Date: Thursday, February 23, 2017 at 3:35 PM To: Dershowitz Adam Cc: "paraview at paraview.org" Subject: Re: [Paraview] Duplicate Renderview Adam, You can show the same data in different views. Just click on the eye next to the filter which output you want to see. So for instance, if you show the data from the last filter in one view, clicking on the eye next to that filter will show the same thing in the second view. So, the starting point does exactly what you want. Note that the settings for how data is displayed in a view are stored per (filter, view) pair. You can change those by selecting the filter and the view you want and changing the display settings. I hope this helps, Dan On Wed, Feb 22, 2017 at 10:16 AM, Adam Dershowitz > wrote: I have a pipeline setup, with a good renderview. I want to then make a split view, that is identical, except for the camera angle. When I try to split my view, or create a new view, they show up empty. I can then start manually turning on, and coloring everything how I want it. But, it seems like there should be an option to ?duplicate current pipeline settings? as a starting point. Then, I could move the camera or make any other changes that I want from there. I did search around in Paraview and on the web, but didn?t find anything. Is there an easy way to do this? I did find a few other discussions about this, with suggested scripts, but those fail for me as well. I?m using Paraview 5.2, although I also looked around briefly for a way to do this in 5.3RC1. Thanks, -- Adam _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView 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 richard.c.angelini.civ at mail.mil Mon Feb 27 11:01:43 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Mon, 27 Feb 2017 16:01:43 +0000 Subject: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 In-Reply-To: References: Message-ID: Chuck ? I?ll try to force things with the ?DUSE_SYSTEM_PNG=OFF. It is my intention to allow PVSB to build the png libraries ? and it seems to work everywhere except for OS X 10.12 ? I can see in the 10.12 build that PVSB did indeed build the png libraries, and there are png entries in superbuild/install/lib and superbuild/install/include ? but the ParaView cmake is not picking up this information. Why it only fails here (or works everywhere is) is the $10,000 mystery ?. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 From: Chuck Atkins Date: Monday, February 27, 2017 at 9:03 AM To: Rick Angelini Cc: Rick Angelini , "paraview at paraview.org" Subject: Re: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 Hi Rick, > When PVSB configures Paraview, it is setting the cmake flag > VTK_USE_SYSTEM_PNG=ON and it should be OFF. When using the superbuild, ParaView should always be using a "system" PNG. The diggerence is whether that will be provided by the OS or the superbuild. Either way, it's external to the paraview subproject. Try explicitly setting -DUSE_SYSTEM_png=OFF when configuring the superbuild. I'll look into why the superbuild doesn't properly handle this in the first palce but explicitl;y setting the option should make your build work. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From dan.lipsa at kitware.com Mon Feb 27 11:23:14 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 27 Feb 2017 11:23:14 -0500 Subject: [Paraview] Duplicate Renderview In-Reply-To: References: <0885637E-AB5E-4083-A3AC-7FEA5AE7AA56@exponent.com> Message-ID: Adam, No, there is no 'create new view as copy of current view' command. Dan On Mon, Feb 27, 2017 at 10:56 AM, Adam Dershowitz wrote: > Maybe my question wasn?t clear. What I want to know is if there is any > way to copy the settings from one view to another. For example if I turn > on the visibility of a few filters (click on the eye) and then turn off > others, and, finally make some other changes such as coloring of object I > can set up a view that I like. Next, I want to start from that identical > view to the one that I setup, but just move the camera from that view. So, > I want to setup things how I want (filter visibility, colors etc) then make > a second view that is a copy of that first view. Then, I want to start > from that second view to move my camera etc. > > > > As you indicate below, I can edit things in a view and change the > visibility in each view. But, I already have a view that I like, and now I > want to make that into a split view with the identical visibility etc. Do, > I have to manually start turning on and off all of the filter visibility > etc? > > What I am looking for is ?copy current pipeline visibility? and then apply > that to another view. Or, ?create new view as copy of current view? Then, > I can start making changes from that point. > > > > I don?t see a way to do that. > > > > Thanks, > > > > -- Adam > > > > > > *From: *Dan Lipsa > *Date: *Thursday, February 23, 2017 at 3:35 PM > *To: *Dershowitz Adam > *Cc: *"paraview at paraview.org" > *Subject: *Re: [Paraview] Duplicate Renderview > > > > Adam, > > You can show the same data in different views. Just click on the eye next > to the filter which output you want to see. > > > > So for instance, if you show the data from the last filter in one view, > clicking on the eye next to that filter will show the same thing in the > second view. > > > > So, the starting point does exactly what you want. Note that the settings > for how data is displayed in a view are stored per (filter, view) pair. > > You can change those by selecting the filter and the view you want and > changing the display settings. > > > > I hope this helps, > > Dan > > > > > > On Wed, Feb 22, 2017 at 10:16 AM, Adam Dershowitz < > adershowitz at exponent.com> wrote: > > I have a pipeline setup, with a good renderview. I want to then make a > split view, that is identical, except for the camera angle. When I try to > split my view, or create a new view, they show up empty. I can then start > manually turning on, and coloring everything how I want it. But, it seems > like there should be an option to ?duplicate current pipeline settings? as > a starting point. Then, I could move the camera or make any other changes > that I want from there. > > I did search around in Paraview and on the web, but didn?t find anything. > Is there an easy way to do this? I did find a few other discussions about > this, with suggested scripts, but those fail for me as well. > > I?m using Paraview 5.2, although I also looked around briefly for a way to > do this in 5.3RC1. > > > > Thanks, > > > > -- Adam > > > > > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > Please keep messages on-topic and check the ParaView 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 pearse at ucar.edu Mon Feb 27 17:23:55 2017 From: pearse at ucar.edu (Scott Pearse) Date: Mon, 27 Feb 2017 15:23:55 -0700 Subject: [Paraview] PEARC17 Visualization Contest Message-ID: ATTENTION PARAVIEW USERS! The PEARC17 Advanced Research Computing conference is currently accepting entries for its yearly Visualization Contest and Showcase. This exhibition is a chance for researchers to demonstrate the current discoveries that are being revealed through High Performance Computing. The submission deadline is May 1, 2017. PEARC17 is the successor to the yearly XSEDE conference held by the NSF. It will take place in New Orleans, July 9-13, 2017, and is open to professionals and students in advanced research computing. Accepted submissions will be included in the PEARC17 proceedings and displayed during the conference. A visualization showcase will be held where the researchers will be able to discuss the science behind their work, and the tools used to create it. A showcase winner will be announced at the end of the conference. Submissions need to include a movie file up to 250MB in size and a short paper (no more than 3 pages including references) that 1. Describes the key observables illustrated in the movie 2. Explains how this visualization enhances the scientific process 3. Explains what tools, techniques, and resources were used to produce the final product Submissions are being done through EasyChair. Submit your entry here ! More information on the Visualization Showcase can be found here ! Good luck! Scott Pearse - pearse at ucar.edu - (303) 497-2432 NCAR/CISL Software Engineer - www.vapor.ucar.edu Come see me at PEARC17 this year! pearc17.pearc.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rccm.kyoshimi at gmail.com Tue Feb 28 05:02:50 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Tue, 28 Feb 2017 19:02:50 +0900 Subject: [Paraview] Issues viewing PV5.0.0 Filters/Alphabetical submenu In-Reply-To: <470ac372adce4ca985e32c89a98cd2ea@RZJMBX2.jr1.local> References: <470ac372adce4ca985e32c89a98cd2ea@RZJMBX2.jr1.local> Message-ID: Hi, Has this issue been resolved? I think that this might be caused by a bug in Qt 4.8.6: https://bugreports.qt.io/browse/QTBUG-54921 Regards, yoshimi 2016-01-21 18:40 GMT+09:00 Fuerntratt, Hermann : > Hi, > I have built ParaView 5.0.0 > in VS2013, 64 bit > based on Qt 4.8.6, > with OpenGL2 render engine in DEBUG and RELEASE mode > on a Win8.1 64 bit system, > OpenGL version 4.5.0 NVIDIA 355.82, > OpenGL renderer GeForce GTX 970/PCIe/SSE2. > > So far everything looks good except the big submenu item opened after > clicking on Filters/Alphabetical just renders the first column of filters > correctly. > Starting with the second submenu column, only icons are displayed centred > (if available) but no text is shown. > So there is a 3 column submenu with the first column ok, the 2nd column only > with icons and the 3rd column totally empty. > > I tracked void pqProxyGroupMenuManager::populateMenu() method in > \ApplicationComponents\pqProxyGroupMenuManager.cxx > > // Now sort all actions added in temp based on their texts. > qSort(someActions.begin(), someActions.end(), ::actionTextSort); > foreach (QAction* action, someActions) > { > alphabeticalMenu->addAction(action); > > //Check if everything is all right: > auto msg = action->font().family(); > qDebug() << "-----------Adding Action > " << action->text() << " > isVisible= " << action->isVisible() << " Font " << msg; > > } > But all actions have a text and are visible? > Has anyone else experienced the same weird thing??? > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView 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 archaerolog at mail.ru Tue Feb 28 07:53:02 2017 From: archaerolog at mail.ru (Gena Bug) Date: Tue, 28 Feb 2017 15:53:02 +0300 Subject: [Paraview] 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> Message-ID: <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> 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 richard.c.angelini.civ at mail.mil Tue Feb 28 08:12:44 2017 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)) Date: Tue, 28 Feb 2017 13:12:44 +0000 Subject: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 In-Reply-To: References: Message-ID: Chuck ? I ran a clean build on my OS X 10.12 system and added the flag ?-DUSE_SYSTEM_png=OFF? to my top-level cmake command ? and I still get the same failure deep down inside of the ParaView build ? can?t find ?? Cmake must be seeing something in the OS X 10.12 environment that?s different from everywhere else that?s causing a misconfiguration ?. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 From: Chuck Atkins Date: Monday, February 27, 2017 at 9:03 AM To: Rick Angelini Cc: Rick Angelini , "paraview at paraview.org" Subject: Re: [Paraview] [Non-DoD Source] PVSB on Mac OSX 10.12 Hi Rick, > When PVSB configures Paraview, it is setting the cmake flag > VTK_USE_SYSTEM_PNG=ON and it should be OFF. When using the superbuild, ParaView should always be using a "system" PNG. The diggerence is whether that will be provided by the OS or the superbuild. Either way, it's external to the paraview subproject. Try explicitly setting -DUSE_SYSTEM_png=OFF when configuring the superbuild. I'll look into why the superbuild doesn't properly handle this in the first palce but explicitl;y setting the option should make your build work. - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5108 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Feb 28 09:29:59 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 28 Feb 2017 09:29:59 -0500 Subject: [Paraview] Issues viewing PV5.0.0 Filters/Alphabetical submenu In-Reply-To: References: <470ac372adce4ca985e32c89a98cd2ea@RZJMBX2.jr1.local> Message-ID: Hi Yoshimi, Would you mind testing the latest release candidate of ParaView 5.3.0 available at www.paraview.org/download? It is built on Qt 5, FYI. Thanks, Cory On Tue, Feb 28, 2017 at 5:02 AM, kenichiro yoshimi wrote: > Hi, > > Has this issue been resolved? > > I think that this might be caused by a bug in Qt 4.8.6: > https://bugreports.qt.io/browse/QTBUG-54921 > > Regards, > yoshimi > > 2016-01-21 18:40 GMT+09:00 Fuerntratt, Hermann : >> Hi, >> I have built ParaView 5.0.0 >> in VS2013, 64 bit >> based on Qt 4.8.6, >> with OpenGL2 render engine in DEBUG and RELEASE mode >> on a Win8.1 64 bit system, >> OpenGL version 4.5.0 NVIDIA 355.82, >> OpenGL renderer GeForce GTX 970/PCIe/SSE2. >> >> So far everything looks good except the big submenu item opened after >> clicking on Filters/Alphabetical just renders the first column of filters >> correctly. >> Starting with the second submenu column, only icons are displayed centred >> (if available) but no text is shown. >> So there is a 3 column submenu with the first column ok, the 2nd column only >> with icons and the 3rd column totally empty. >> >> I tracked void pqProxyGroupMenuManager::populateMenu() method in >> \ApplicationComponents\pqProxyGroupMenuManager.cxx >> >> // Now sort all actions added in temp based on their texts. >> qSort(someActions.begin(), someActions.end(), ::actionTextSort); >> foreach (QAction* action, someActions) >> { >> alphabeticalMenu->addAction(action); >> >> //Check if everything is all right: >> auto msg = action->font().family(); >> qDebug() << "-----------Adding Action > " << action->text() << " >> isVisible= " << action->isVisible() << " Font " << msg; >> >> } >> But all actions have a text and are visible? >> Has anyone else experienced the same weird thing??? >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView 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 ben.boeckel at kitware.com Tue Feb 28 09:54:47 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 28 Feb 2017 09:54:47 -0500 Subject: [Paraview] Issues viewing PV5.0.0 Filters/Alphabetical submenu In-Reply-To: References: <470ac372adce4ca985e32c89a98cd2ea@RZJMBX2.jr1.local> Message-ID: <20170228145447.GA7658@megas.kitware.com> On Tue, Feb 28, 2017 at 19:02:50 +0900, kenichiro yoshimi wrote: > Has this issue been resolved? > > I think that this might be caused by a bug in Qt 4.8.6: > https://bugreports.qt.io/browse/QTBUG-54921 I think we came to the same conclusion. Windows has used Qt4 4.8.4 since then to avoid the issue. However, as Cory said, Qt5 is now in use, so the bug might have been avoided that way now. --Ben From utkarsh.ayachit at kitware.com Tue Feb 28 09:57:07 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 28 Feb 2017 09:57:07 -0500 Subject: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download In-Reply-To: <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> References: <46f92710-223f-ee36-2617-483f2f4d6dc6@mail.ru> <4f1f5bb3-022f-b93f-5307-90294d384313@mail.ru> <32b41d22-3d88-3bd6-1bc3-7dfa1e480a80@mail.ru> Message-ID: 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 >>>>> >>>>> >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Feb 28 13:41:18 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 28 Feb 2017 18:41:18 +0000 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> Message-ID: <35ae3bd7af38410f9d614c71971478ab@ES01AMSNLNT.srn.sandia.gov> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Feb 28 14:57:03 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 28 Feb 2017 19:57:03 +0000 Subject: [Paraview] 2d image tiling problem Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Tue Feb 28 18:06:33 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 28 Feb 2017 23:06:33 +0000 Subject: [Paraview] 2d image tiling problem Message-ID: <65D78593-72E3-4FA5-8BD7-609D25765E1B@sandia.gov> I cannot think of any existing reader with a format that is similar to what you describe. That said, the VTK/ParaView data structures could hold such a thing no problem. It might be your best bet is to create a reader (or programmable source) that reads in the metafile. -Ken From: ParaView on behalf of Walter Scott Date: Tuesday, February 28, 2017 at 12:57 PM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] 2d image tiling problem 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: